Hello,
I'm reactivating this thread since I cannot talk with samm every now and then to update the OP from this thread here.
What works:
It is stable for a daily driver but there are definitely things that doesn't work. For starters, the Hero is too small for ICS since we don't have any GPU posibility. Adreno 130 drivers are oh, too small and too bad for animations on ICS, they suck even in GB and Froyo. Still, the statusbar and fling are much smoother than other android releases because that's how ICS is built. It is more RAM friendly and it looks, well, sexy!
Will try and update this rom when it will be possible. We might jump on the bandwagon of 4.0.4 if I can make it to move faster than it moves right now (yes, I have an experimental build).
If one of you want to join me to develop this rom further, send a PM and I will send you some details about what is in the works, how far it is. I know there are few people that can work on builds here on Hero thread but if we work together, we can pull this out one more time.
FLASH THIS AT YOUR OWN RISK. I AM NOT RESPONSIBLE FOR:
- YOUR BRAIN
- YOUR HOUSE
- YOUR PHONE!
ON with the ROM. What has been changed:
Added:
Code:
- Google Music apk (yes, official google music app);
- Explorer.apk
- Latest and greatest LV Kernel 1.2+
- Revert to Evtoolbox back from 4.0.3 builds
- Set the cpu to scale at 352-672 from startup
- Tweaked the build.prop a little (added some experimental lines)
Why this is v3?
Because the memory management inside the kernel (remember, INSIDE THE KERNEL) is tweaked and fixed to nice values in order to allow our hero to better multitasking (you can find these values in my other rom called 1ceCream BEAST Flavor). No need for tweaks in init.d to do the job, no bull****.
Just plain and simple!
If you are texting someone, sending an email, playing a game, doing something, and you are locking the screen, after unlocking you will find that the application is ON the screen, and is not closed how it is in many other roms for hero. The multitasking with my values is so much better, you will definitely like it!
Click to expand...
Click to collapse
The rom moves fast, even if it is ICS, I have the animations on and no force GPU in Developer settings and it is still moving so much fast than the older builds.
Overall, I am happy with this release and I hope you will be too! Post me some of your opinion and tell me if it is fast or am I dreaming!
Some user's feedback:
Loxxy said:
wow 'HeroICS v3' is running on rocket power !!! what the hell
amazing job
Click to expand...
Click to collapse
Carrier Internet connection issue:
- Create Manual APN for provider's internet connection.
DOWNLOAD HeroICS v3
If you make these changes maybe you'll see better performance, the hero can't handle dithering on anything higher than stock GB or Sense froyo and doesn't have enough RAM for 48mb of dalvik heapsize. I may be wrong but these always worked for me in the past altough ICS is supposed to be better on RAM.
dalvik.vm.execution-mode=int:fast
dalvik.vm.heapsize changed to 24m or 32mb
persist.sys.use_dithering=0
Good work. Flashing now.
How about keeping this as lite as possible, only the absolute essentials pre-installed, everything else as optional zips / apk. For instance, I personally have no use for the music player.
I would really like to see a bare bones, fast and stable ics rom where you just add what you need.
---------- Post added at 03:56 AM ---------- Previous post was at 03:16 AM ----------
Unexpected reboot just as I was about to install Opera Mini. Followed by: "New Sim Detected, reboot required." Never seen that before.
I've applied CSL00's values.
Wonder if V6 Supercharger or Auto Memory Manager can improve things.
Play Store is noticeably faster. Unsure if was CSL00's values or the introduction of AMM.
Regarding the error message: 'No more room on this home screen.'
In Play Store app. Menu > Settings > Deselect Auto-add widgets.
Second unexpected reboot, otherwise things are getting faster. No wifi issues, BT still won't pair.
Running AMM on 'Aggressive.'
CSL00 said:
If you make these changes maybe you'll see better performance, the hero can't handle dithering on anything higher than stock GB or Sense froyo and doesn't have enough RAM for 48mb of dalvik heapsize. I may be wrong but these always worked for me in the past altough ICS is supposed to be better on RAM.
dalvik.vm.execution-mode=int:fast
dalvik.vm.heapsize changed to 24m or 32mb
persist.sys.use_dithering=0
Click to expand...
Click to collapse
dalvik execution mode was on fast until I changed it in the last second to "jit".
vm.heapsize was changed to 48 because I was testing 32 mb and I saw that it takes a little while to enter in one application. With 48 mb the time is reduced somehow. Please feel free to change it to 32 mb if you want. Dithering, well here is a mistery, I don't know if this works in ICS. It does look a little better than with it changed to 0 and my phone can suport dithering pretty well.
About the reboots, please install set cpu and set your max cpu frequency to a respectable value such as 691 or lower. I suggest using governor smartassV2.
The whole rom does feel a little snappier but we have an issue when someone calls you and after 20 seconds the call gets interrupted. I'll look into that today after work and see if I can fix it somehow.
I've tried Supercharger, the V8 doesn't wanna start on ICS and when applied V6 with option 6, the phone just got stuck on bootloop.
The reason that I've made it like this with apk.s that you can easly uninstall is that I didn't want you guys to have to flash any other optional zips or anything. But as I said, feel free to do what ever you want and uninstall those unused apps.
Oh, If you want to try supercharger yourself, you have to first delete these scripts from /etc/init.d:
03tweaks
04netspeed
05fixsdcardspeed
06loopy_smoothness_tweak
15cleanup_init_ram
16sqlite_optimize
17speedy_modified
Just to avoid any unexpected issues.
L.E:
CAN SOMEONE PLEASE, make a LOGCAT while you are in a call and save it to a txt? I want to see if we can narrow down the problem of disconnecting. I am unable to make a logcat atm.
1ceb0x, back to using your original build.prop, and Setcpu. Things seem more stable.
I'm looking for a notification toggle (cm-style) that has no icon when running (or only hides it, leaves a space.)
I will make a logcat, but I've tried aLogrec and all it seems to produce is an empty file. Should it not be dumping info on any activity I do?
lost101 said:
1ceb0x, back to using your original build.prop, and Setcpu. Things seem more stable.
I'm looking for a notification toggle (cm-style) that has no icon when running (or only hides it, leaves a space.)
I will make a logcat, but I've tried aLogrec and all it seems to produce is an empty file. Should it not be dumping info on any activity I do?
Click to expand...
Click to collapse
Seems stable than samm000's build.prop?
Glad to hear this.
As for the logcat, you cannot use any of the readers on the market because they will not work on ics. I've tried to make a log using android sdk but it seems that we need a file called 'main' in /dev/logs. I tried to make the file manually but then I've encountered an EOF read error on cmd. I forgot to make permissions for the respective file. Will make it again now and see how it goes.
As for cm notification toggle, I don't know what are you talking about. The notification toggle on ICS is nicer than any other available .
Tell me if you have calls issue (your call is disconnected after some seconds)?
Well it is probably more stable because I reduced the cpu speed.
In a voicecall now, 2mins+. Call lost around 3 mins.
6mins+ this time and still going...
lost101 said:
Well it is probably more stable because I reduced the cpu speed.
In a voicecall now, 2mins+. Call lost around 3 mins.
Click to expand...
Click to collapse
Did you checked the box "Force GPU rendering" in Develop Options?
Is it stable because I've added graphical tweaks and some tweaks to speed...
Yeah, 'Force GPU rendering' is enabled. In a voicecall now, 10mins+.
I ended the call myself at 22mins.
lost101 said:
Yeah, 'Force GPU rendering' is enabled. In a voicecall now, 10mins+
Click to expand...
Click to collapse
10 minutes without disconnecting? What's your settings on network? GSM ONLY, or WCDMA preferred?
(to see this, please go to dialer and dial *#*#4636#*#* , then go to Phone information, scroll down and you will see the value above the button "Turn Off Radio").
as default the version is WCDMA preferred. What Radio firmware are you using?
also, did you installed Habarug's tweak to hide the end button call during a call? (it's in samm000's thread).
this information will be helpful! cheers
WCDMA preferred. Radio: 63.18.55.06PU_6.35.15.11
I have not installed Habarug's tweak.
lost101 said:
WCDMA preferred. Radio: 63.18.55.06PU_6.35.15.11
I have not installed Habarug's tweak.
Click to expand...
Click to collapse
and you had 10 minutes without disconnecting? you were able to end the call normally?
1ceb0x said:
and you had 10 minutes without disconnecting? you were able to end the call normally?
Click to expand...
Click to collapse
It was 22mins when I ended the call myself.
Regarding notification toogle this is what I mean: 15 toggle status bar as implemented in this rom. Check the video.
Very ODD.
I have 63.18.55.06OU_6.35.15.01 on my device with WCDMA preferred but I keep getting call disconnected after 10 seconds or so.... regarding the notification status bar power widget, I don't know what to say. I'm not a dev so...
i'm trying to find a way to make a log cat of the calling issue because I don't really want to change my radio because my version seems to be battery friendly...
thank you for your support
Obviously the notification thing isn't even important right now. I shouldn't really have mentioned it.
I thought this radio was considered one of the best to be using, and find the battery life to be good on it.
Don't know if its the best really. But I've flashed it anyway. Since this will end my calling interrupt, it will be a small price to pay if the battery doesn't play well.
Will test the voice calling. Btw, I am maybe working on RC2, with some new tweaks and fixed latinime.apk keyboard..
can confirm right now that the latinime.apk is fixed.
@Habarug: are you using my mod or sam's rom?
Thanks lost, will try your radio, im on .14 atom
Just to clarify, the radio I am using still has calls dropping with ics. It seems to happen at random times. 1 minute into a call, 3 minutes or not at all. Maybe it's because of the numbers I am ringing. I can't be sure they would not drop anyway. But it sounds like it is doing better than some other radios.
Also, what about having a build based off ics 4.0.4?
lost101 said:
Just to clarify, the radio I am using still has calls dropping with ics. It seems to happen at random times. 1 minute into a call, 3 minutes or not at all. Maybe it's because of the numbers I am ringing. I can't be sure they would not drop anyway. But it sounds like it is doing better than some other radios.
Also, what about having a build based off ics 4.0.4?
Click to expand...
Click to collapse
we have to fix this issues first and then talk about another version. anyhow, 4.0.4 is much laggier than this version. i saw a bit of logcat and some awkwardly errors regarding the "animations" but i was unable to save the log for future use.
I've asked Maclaw, a dev from Galaxy Gio/Fit/Mini who made CM9 possible on those device to look at our build and maybe with some luck he can see something that make this calls drop...
managed to past 3 minutes in call with your radio version lost101. cheers
L.E: I am unable to send PM's. so i cannot ask Maclaw for help.. too bad! I'll just have to post on their op!
Come on people.. test the build!
Related
wifi working with patch.
http://forum.xda-developers.com/attachment.php?attachmentid=325161&d=1273647492
http://forum.xda-developers.com/showthread.php?t=679680
could someone resize it to 240x320 please? cant wait to try this
Heads up! New Kaiser Wifi update: http://forum.xda-developers.com/showpost.php?p=6456191&postcount=33
Old one replaced build.prop with wrong version. Reinstall and use the new Wifi update.
Also to get rid of android-rebooting-problems with GPS Test application do the following:
1. Start terminal emulator
2. su
3. cd system/lib/hw
4. rwsystem
5. rm sensors.msm7k.so
6. rosystem
7. exit
8. exit
9. restart phone
So how is it? I'm too lazy to install it.
Dukenukemx said:
So how is it? I'm too lazy to install it.
Click to expand...
Click to collapse
Seems like a really nice build. I'm using 320x428 with 144 dpi. A bit slow because I'm currently not running in NAND but I would expect it to perform quite well once I go back to running NAND again.
I haven't tested it very much yet as I'm doing some experiments in WinMO at the moment.
just tried
hey
i just downloaded this and i have to say im impressed about this.
as i love the eclair design and everything and the donut speed i have to say this is impressing because it is FAST! not as fast as donut but pretty much the same. that could be due to the 500 mHz OC but i just like that build.
just needs to be optimized a bit, maybe a few apps like astro and others
and as the developer has a new phone we need a new one.
But i have to say its awesome!
i love it already and just tried it for 9 min.
just the OC needs to be removed i noticed right now and is there any way to set another value for the screen sensebility because quiet often it does not react on a touch.
so keep updating this!
nick
nice rom but it chews through battery like crazy. With a full charge battery will drop from 99 to 75(battery fix removed OC and set 1400 value) with just a 10min phone call and a couple txts. I think what we need is a new kernel highly optimized for battery life using the latest patches. Judging from the name alone of the kernel its running right now 2.6.25-01051-gc362ac-dirty and the fact that 2.6.25 was released in jul 2008 i think theres room for tons for improvement.
Does anyone know how to adjust the microphone gain? my friends complain they cant hear me..
The wifi scan interval is set to 15 seconds by default in this release. That will have a negative effect on battery life if you are out of range of a known network and have wifi enabled. I'll put together an update to change this when time allows. I use 120 seconds myself.
kallt_kaffe said:
The wifi scan interval is set to 15 seconds by default in this release. That will have a negative effect on battery life if you are out of range of a known network and have wifi enabled. I'll put together an update to change this when time allows. I use 120 seconds myself.
Click to expand...
Click to collapse
Thanks to update.
It working good on Polaris.
Also i change interval to 180 and density to 120 in .prop
Here's an update that changes the wifi scan delay to 120 seconds and also (not tested yet) changes the model name from Vogue to Kaiser.
i'm still trying to figure out if it's possible, somehow, to flash an update.zip file (to be able to use the cyanogenmod skins) with the nomorootfs we're using, instead of converting the skins to metamorph format
does anyone know if it's possible or how to do it?
Can't get wifi to work with updates, which one should I need?
kallt_kaffe's works for me. If something isn't working like it should, power off the phone and remove the battery. Then hold down the power button to remove any remaining power left. Place batter back in and try again.
Also, make sure to always fix permissions when you apply updates, even for wifi.
Dukenukemx said:
kallt_kaffe's works for me. If something isn't working like it should, power off the phone and remove the battery. Then hold down the power button to remove any remaining power left. Place batter back in and try again.
Also, make sure to always fix permissions when you apply updates, even for wifi.
Click to expand...
Click to collapse
edit: how stupid can I be? I've bought another phone and forgot to add the mac adress.
Certainly think mod needs work. So far the battery meter is off, and all this time I thought it drained less power. A lot of pop ups to force close apps. A lot of apps are running that I don't use.
mssmison didn't say he was going to put any more effort into it either. Hopefully, someone will pick it up.
Dukenukemx said:
Certainly think mod needs work. So far the battery meter is off, and all this time I thought it drained less power.
Click to expand...
Click to collapse
Try deleting /data/system/batterystats.bin. That usually helps when the batterymeter has gone bad.
A lot of pop ups to force close apps. A lot of apps are running that I don't use.
Click to expand...
Click to collapse
Have you removed or renamed /lib/modules/hw/sensors.msm7k.so? After I removed that it runs very stable for me.
kallt_kaffe how do you do it?
I'm new to the androidinstall.tar method. I'm tyring to run from haret but it seems impossible.
You said you where experimenting with something in winmo, so that implies you're using haret? Are you running from haret?
When I try, Polymod, and Mssmission they don't show an install option, when I try myn and incubus I get it installed but I get no sound. It was actually your gps kernel that let me get things installed all other kernels i tried had non-functional dpads within the installer environment. Also, trying another kernel once installed didn't fix the sound issue.
Anyhow just let me know if you're using Haret. I wonder whats up with the sound and missing install option. I tried the install two different ways one with a 2gb fat32 partition, and then another attempt using three primary partitions 1.3gb fat32, 300mb ext, 300mb ext. All installers then would give me options beside's fat, but not all intallers would have an install option.. I'm using radio 1.71.09.01.eMo, model: kais100, os: wm6.5 (shifu v.3)
kallt_kaffe said:
Have you removed or renamed /lib/modules/hw/sensors.msm7k.so? After I removed that it runs very stable for me.
Click to expand...
Click to collapse
I try start Skyforce game, but it forceclose.
It can work after i added "sensors.sapphire.so" into /lib/modules/hw/
I've installed the cyanogenMod updater from the marketplace, but it can only find older versions, no experimental versions, whatever option I set in the program.Anyone?
Dukenukemx said:
Certainly think mod needs work. So far the battery meter is off, and all this time I thought it drained less power. A lot of pop ups to force close apps. A lot of apps are running that I don't use.
Click to expand...
Click to collapse
battery life has been fantastic for me on this build...
although I reverted back to 400mhz and got rid of compcache.
I am sure that OCing to 500 by default is draining the battery faster.
I would rather a usable phone than a fast one...(although it still seems very fast to me)
Sorry that I have to post this here...I don't post much, just am a super power user... any thoughts on how to make this rom perform faster? I push a button and wait for the phone to respond. Especially slow when it comes to the maps app. An seriously contemplating going back to cm9b14 if not all the way back to gingerbread to get the speed I need from a device. I type faster than it is able to display the letters when searching in google. Not wure what feature to turn off or how much more I can overclock the thing.
On install I did a factory reset, total partition format, new sd card format, efs wipe, and ed's ril/gps fix after install.
Not sure how to tweak v6 supercharer. Seems too complicated honestly.
Thoughts?
Thanks...
I just started running Mimicry today and I find it to be quite a snappy ROM right out of the box especially if you picked the V6 Supercharger and the Virtuous OC Daemon from the Aroma installer. I believe doing this automatically increases your clock speed to 1209 Mhz. However if you want to increase the speed of your CPU some more, can modify it through the Performance menu or you can download SetCPU.
http://forum.xda-developers.com/showthread.php?t=505419
Bharakrama said:
I just started running Mimicry today and I find it to be quite a snappy ROM right out of the box especially if you picked the V6 Supercharger and the Virtuous OC Daemon from the Aroma installer. I believe doing this automatically increases your clock speed to 1209 Mhz. However if you want to increase the speed of your CPU some more, can modify it through the Performance menu or you can download SetCPU.
http://forum.xda-developers.com/showthread.php?t=505419
Click to expand...
Click to collapse
I can attest to that, mimicry is pretty fast, no issues so far. only problem I had was when I tried to multitask between navigation, whatsapp, and viber, my navigation froze and i got lost :crying:
toquer said:
Sorry that I have to post this here...I don't post much, just am a super power user... any thoughts on how to make this rom perform faster? I push a button and wait for the phone to respond. Especially slow when it comes to the maps app. An seriously contemplating going back to cm9b14 if not all the way back to gingerbread to get the speed I need from a device. I type faster than it is able to display the letters when searching in google. Not wure what feature to turn off or how much more I can overclock the thing.
On install I did a factory reset, total partition format, new sd card format, efs wipe, and ed's ril/gps fix after install.
Not sure how to tweak v6 supercharer. Seems too complicated honestly.
Thoughts?
Thanks...
Click to expand...
Click to collapse
Make sure your partitions are all ext4. Also, v1.1.1 is out
update
1.1.1 definately fixed a lot of issues i was having. i also removed the option to have the kernel installed and dropped the speed way down on setcpu. seems to be a lot better now.
I'm running Albinoman's JB RC3 ROM, and like it a lot. The only significant problem I have is occasional severe sluggishness. When it happens, I'll open IntelliControl and I notice either of two things going on:
1) I'll see that the max CPU speed has been reset to 664000 or something close to that (it's always the same number, but I don't remember exactly what it is...600-something). Once I crank the max limit back up to 1036800, things are good again. What keeps resetting the CPU limit to such a low level, and how do I stop it from doing that???
2) I'll see that the CPU is maxed out at 1036800, but I can't figure out what's chewing up the CPU. What tool can I use to see what process is consuming all the CPU cycles when that happens?
Thanks for the help...
1. I can't tell you why it happens... but I know it is a common problem on the JB ROMs (on the Dinc). There was quite a lot of discussion about it. I know the devs are aware of the issue and were working on it.
2. I don't know of anything that will graph percentage of cpu cycles, or anything exactly like that. But try hooking the phone up to the PC and run ddms (part of the adb tool set) and see what it is doing (or failing to do). While ddms is running in verbose mode it will give you a running output of everything the phone is doing (along with all the errors and warnings).
MysticCobra said:
I'm running Albinoman's JB RC3 ROM, and like it a lot. The only significant problem I have is occasional severe sluggishness. When it happens, I'll open IntelliControl and I notice either of two things going on:
1) I'll see that the max CPU speed has been reset to 664000 or something close to that (it's always the same number, but I don't remember exactly what it is...600-something). Once I crank the max limit back up to 1036800, things are good again. What keeps resetting the CPU limit to such a low level, and how do I stop it from doing that???
Click to expand...
Click to collapse
That's because he's using an older version of Evervolv's qsd8k-common. It was fixed on Oct 10 with Change I3a0fff83: powerHAL: fix the screen off bug. This is one of the reasons I do nightlys, is to get all the new tweaks. This bug won't be fixed in his ROM till he resyncs his source and recompiles. It's triggered by the screen turning off. There's a workaround with Tasker, but since this bug is no longer in my ROM, I quit looking at it.
MysticCobra said:
2) I'll see that the CPU is maxed out at 1036800, but I can't figure out what's chewing up the CPU. What tool can I use to see what process is consuming all the CPU cycles when that happens?
Click to expand...
Click to collapse
CPUSpy is a pretty good app.
MysticCobra said:
I'm running Albinoman's JB RC3 ROM, and like it a lot. The only significant problem I have is occasional severe sluggishness. When it happens, I'll open IntelliControl and I notice either of two things going on:
1) I'll see that the max CPU speed has been reset to 664000 or something close to that (it's always the same number, but I don't remember exactly what it is...600-something). Once I crank the max limit back up to 1036800, things are good again. What keeps resetting the CPU limit to such a low level, and how do I stop it from doing that???
2) I'll see that the CPU is maxed out at 1036800, but I can't figure out what's chewing up the CPU. What tool can I use to see what process is consuming all the CPU cycles when that happens?
Thanks for the help...
Click to expand...
Click to collapse
For #1, a possible fix could be to use this power.qsd8k.so provided by tiny4579:
http://forum.xda-developers.com/showpost.php?p=32552961&postcount=264
Replacing this file fixed the issue on Pons's ROM, but it may wreak havoc on Albinoman's, I have no way to know. Make sure you have a good nandroid backup before attempting to use it. Or, just wait for Albinoman to release a newer ROM with the problem fixed in the source.
musical_chairs said:
For #1, a possible fix could be to use this power.qsd8k.so provided by tiny4579:
http://forum.xda-developers.com/showpost.php?p=32552961&postcount=264
Replacing this file fixed the issue on Pons's ROM, but it may wreak havoc on Albinoman's, I have no way to know. Make sure you have a good nandroid backup before attempting to use it. Or, just wait for Albinoman to release a newer ROM with the problem fixed in the source.
Click to expand...
Click to collapse
It should work fine on Albinoman's ROM. powerHAL is a generic jellybean feature and should work on all JB ROM's. You won't need the fix however on either of Pon's ROMs whether AOKP or CM10.
I'm finding the same issue on the 11/08 build. I replaced the file with the one you uploaded, yet no change. Still reverts to 614 when the screen is off.
I'm managing it with both Incredicontrol and Juicedefender, so on wake it returns to 1075, and the SAv2 seems much smoother than interactive for me. If there's a fix in the newer builds I may flash one (if I get the time), but for now I'm really impressed by how well this one is running.
Thanks,
...sorry...I was on the phone...
omniatic said:
I'm finding the same issue on the 11/08 build. I replaced the file with the one you uploaded, yet no change. Still reverts to 614 when the screen is off.
I'm managing it with both Incredicontrol and Juicedefender, so on wake it returns to 1075, and the SAv2 seems much smoother than interactive for me. If there's a fix in the newer builds I may flash one (if I get the time), but for now I'm really impressed by how well this one is running.
Thanks,
...sorry...I was on the phone...
Click to expand...
Click to collapse
It's supposed to change to 614 on screen off. The bug was that it would stick at 614 even on screen on.
I don't recommend that lib for cm. It's outdated.
Also I don't use sav2 anymore as it doesn't and won't implement project butter. Also interactive can be more aggressive than sav2 as it can jump frequency on touch via boostpulse which sav2 doesn't have.
Sent from my Galaxy Nexus using Tapatalk 2
Oh, well, then I guess I'll give the interactive another try. Maybe just needs to settle in longer. Got so used to ICS, wasn't sure what to expect from JB. Guess it's time I read back a few pages and see what else I've missed.
...sorry...I was on the phone...
Thanks, guys--appreciate the help!
Maybe its out of topic but since i still cant post on dev sub forum i wanna ask a question here to pons.
Im running your CM10 20121114, whenever i play music with appolo it always reboot my dinc.
Is any other had this problem too?
alph0 said:
Maybe its out of topic but since i still cant post on dev sub forum i wanna ask a question here to pons.
Im running your CM10 20121114, whenever i play music with appolo it always reboot my dinc.
Is any other had this problem too?
Click to expand...
Click to collapse
Yep, just a tad bit off topic.
I haven't had this problem before. Granted, I've never played music off my Inc, but I haven't heard anyone else complain, either. Can you PM a logcat? And it's always preferable to report errors off latest versions (currently 1120).
PonsAsinorem said:
Yep, just a tad bit off topic.
I haven't had this problem before. Granted, I've never played music off my Inc, but I haven't heard anyone else complain, either. Can you PM a logcat? And it's always preferable to report errors off latest versions (currently 1120).
Click to expand...
Click to collapse
Thanks for the reply Pons. Yes i think i will download the latest build sooner and test it again. Hope it (randon reboot with apollo) will not happen again on my dinc. But if it still, i will pm you the logcat.
alph0 said:
Thanks for the reply Pons. Yes i think i will download the latest build sooner and test it again. Hope it (randon reboot with apollo) will not happen again on my dinc. But if it still, i will pm you the logcat.
Click to expand...
Click to collapse
I use Apollo Music regularly on Pons's CM10, it works fine, doesn't reboot.
alph0 said:
Maybe its out of topic but since i still cant post on dev sub forum i wanna ask a question here to pons.
Im running your CM10 20121114, whenever i play music with appolo it always reboot my dinc.
Is any other had this problem too?
Click to expand...
Click to collapse
Try flashing to his newest build. It fixed a few problems for me and is incredibly fast. I had to reflash gapps from goo.im though because play store was force closing. Also, doubletwist is a better music player imo because it has a better interface and has good integration with the lockscreen.
I know, many people here want to have Android 4.x.x on their phones, but unfortunately, because of low-end processor as well as less RAM, these CM10/CM10.1 ROMs are laggy and slow. I am also one of them, but, after using these type of roms since 4 months, I have now got a perfect idea of using them. So, I am sharing the way I use these roms. Many people told that this also helps for CM7 users. So, now I have declared this thread as UNIVERSAL PERFORMANCE THREAD. This method can be used on - Stock | CM7/9/10/10.1.
NOTE : This thread is mainly from galaxy mini forums. But, I have posted it here also, so that Gio users also get its benefits.
NOTE : This method is same for PAC ROMS.. because they are based on CM. So, you can use this on PAC ROMs also.
♦ FINDING STABLE VERSION :
First of all, you will need to find a good stable version of any CM7\CM9\CM10\CM10.1 ROM. Find stable version by asking in general discussion thread of those particular ROM and then download that version. But, do not flash now.. Follow next step.
Note : For CM7 users - Official CM7 is best, but if you want you can try it on custom roms also. If you are using CM7 custom or stock based custom rom, then for scripts n tweaks to work, you must delete all the scripts from init.d so that scripts will not get overridden.
♦ SLIMMING THE ROM :
Slimming means making rom size less by removing unwanted and unnecessary applications from system/app. It reduces system memory use. Here is a chart of cm10.1 apps which are safe to remove - LINK
With reference to that chart you should remove following apps with adding alternatives to them.
Note: Left side apps are to be removed and right side apps are alternatives.
● LatinIME.apk - WP7 Keyboard App
● Browser.apk - Holo Web Browser
● CMFileManager.apk - Root Explorer File Manager
● Trebuchet.apk - Holo Launcher
NOTE: On CM7, default ADW is good, but you can also use Holo Launcher.
Other apps that can be removed without alternatives-
● CalendarProvider.apk - One of the big RAM consuming apps. This app start anytime, you do anything, so it will be a big save of memory removing this app. But, you will get problems with calendar sync..
● GoogleCalendarSyncAdapter.apk - Reomove this only if you do not sync calendar.
● Email.apk - If not in use.
● Gmail.apk - If not in use.
● Talk.apk - If not in use.
● GoogleBackupTransport.apk - It is used in google backups, remove on your own risk. (Not a risk, i always remove it.)
● ChromeBookmarkSyncAdapter - No use.
● HTMLViewer.apk - Never needed.
● UserDictionaryProvider.apk - It is useless without LatinIME.apk.
● VisualizationWallpapers.apk - Wallpapers app. Remove it always.
● CMWallpapers - Remove it always.
● VoiceDialer.apk - Do you really use it?
● LiveWallpapers.apk - Dont you care for your battery?
● QuickSearchBox.apk - If you dont use.
● PicoTTS.apk - Text to speech function.
NOTE: Alternative apps should always be installed in system/app only. For that, I recommend you to remove these apps drectly from rom's zip before flashing.
♦ USE OF SCRIPTS N TWEAKS :
Many people use hard scripts n many tweaks to get good performance. But, it is totally wrong.
Highly recommended to use Activo Speeder. It is the best script for performance. Dont use anyother thing with it- such as ram manager, seeder or anyother script.
(Note: If the above script doesnt work on your device then please find another good script and flash it.)
IT IS RECOMMENDED TO USE SUPERCHARGER ON ICS\JB :
After testing a lot, I found that SuperCharger is the best script which can be used with any ROM to get more performance and for perfect RAM Management. Here are some steps on how to use SuperCharger -
● Here is the original thread for SuperCharger script.
● Script can be downloaded from this download page.
● Download latest script as well as starter package if needed (Read Original Thread).
● Now, for 4.x.x ROMs, you do not need to do anything with services.jar. But, for below 4.x.x, services.jar needs to be patched to get SuperCharger Memory Management working.
● Now, copy script to SDcard and run it with Script Manager as root. For more detailed guide plz prefer the original supercharger thread.
● Now, you are running the script. You will find many options and info on screen. Read it all and choose what you want.
NEW DISCOVERY : SUPERCHARGER + CROSSBREEDER = ULTIMATE PERFORMANCE WITH MAX ENTROPY ! - by Dark Passenger
● LINK FOR THE POST.
Here are some tweaks-
In Build.prop -
●
Code:
ro.ril.disable.power.collapse=0
and change the value from 0 to 1. (Add the line with proper value if does not exist)
This one is for battery saving.
●
Code:
dalvik.vm.heapgrowthlimit=48m
If it already exists then just match the values.
This is a VM Heap management for RAM.
●
Code:
ro.ext4fs = 1
Improves EXT4 performance.
● IMP :
Add following lines below "# Other" in build.prop
Code:
ro.com.google.locationfeatures=0
ro.com.google.networklocation=0
(If exists, just change the values as above).
(Note: This one will remove location feature increasing performance freeing up more RAM. This frees up to 30mb of RAM)
And now remove NetworkLocation.apk from system/app as well as com.android.location.provider.jar from /system/framework.
For further build.prop tweaking, you can use this great guide -> Click Here. Thanks to Dark Passenger for some build.prop tweaks.
This much tweaking and scripting is enough. DONT USE TOO MUCH TWEAKS N SCRIPTS.
♦ BASIC APPS TO USE :
Your rom's performance also depends on the apps which you use. Always look for apps' memory usage and if the app consumes more ram then try to find an alternative app for it. Here are some basic apps which you should use (i always use them).
● Use Root Explorer as file manager, Holo Launcher as Launcher.
● Use Cache Cleaner App. It is must. Clean cache once a day.
● Use Root Cleaner App. A must have app. Do "Quick Cleaning" twice a day. It will regulate your performance.
You can also freeze the apps you are not using at that time, such as DSPManager (Unfreeze it only at the time of listening songs)
Freezing Google Apps will be a great way to reduce RAM consumption.
● Use this amazing app - Autostarts. This app controls the apps that start automatically in your phone. If you want settings which I use then PM me. I will tell you, how to use this app.
CLICK HERE FOR AUTOSTART APP SETTINGS
● ABOUT TASK KILLERS :
Using task killer is good but, it is also bad. Task killing is actually meaningless. Some apps never really get killed. They start again n again. So, use Autostarts instead task killers. But, here is a nice app for killing processes and freeing RAM. This is the original app. I have themed it to look good. Download it here.
Use it as a task killer, press menu button and include system processes and then start killing processes which are useless.
● Try to use apps as system apps.
● If you are using UC Browser then in its settings, check "Clear Data on Exit". If did, you will see UC will take less than 10mb but, if you wont do this, UC will take more than 15mb.
♦ IMPORTANT TIPS AND SETTINGS :
● Always flash rom with a clean wipe and proper flashing method.
● Do not flash gapps again if they are included in the rom.
● Do not flash internal memory scripts as they reduce performance.
● Use Adrenaline Boost. Boost once or twice a day. Boosting much will increase battery consumption.
● Use Root Cleaner app and freeze the apps which you are not using at that time. Freeze Google Play Store, Google Services Framework and other google apps which are always on. Unfreeze them when you want.
● The apps used for Backup purposes should not be installed always. Keep them in your sdcard and install them when you want and uninstall when done with them.
● Basic apps should always be in system/app.
● In Developer Options -
Set all animations scale to .5x
Set Background Process Limit to "Atmost 4 processes", if issues occur then set it back to "Standard Limit".
Enable "Kill App Back Button". Always use this feature to come out of the apps which do not really exit on pressing just back button.
● Do not expect much from our phone as it is not a high-end phone. Dont expect good battery life but, still to gain good battery life. Keep RAM free by using the ProcessKiller app as told above. I always get 170 mb RAM free.
● Do not charge battery until it gets discharged upto 10% or less. While charging do not remove it till it reaches 100% and 20 mins above that.
● Calibrate battery when needed.
● Avoid use of apps which are always running either in background or foreground.
● Press thanks. .
Thanks! I'm definetely going to try this out, even though I'm not running JB but ICS.
Deleting unneeded apps works on every Android version I think, and ActivoSpeeder works on ICS too, so I'm happy!
StiQuezNL said:
Thanks! I'm definetely going to try this out, even though I'm not running JB but ICS. Deleting unneeded apps works on every Android version I think, and ActivoSpeeder works on ICS too, so I'm happy!
Click to expand...
Click to collapse
As I hv mentioned in the title.. this method is for all ROMs.. It is not needed that you should be running JB only.. it is for all...
Noobwithdumbquestions said:
this made everything a lot more laggy and gmail stopped syncing... Also takes about 3 times as long to boot.
No offence, but this is pretty terrible. And after doing some actual research a lot of the "tweaks" you talk about here are never proven effective and frowned upon by actual experts. Even in the article you linked the writer says that something like dalvik heapsize is not something you should or have to change.
I would advice anyone to NOT waste any time on this.
ps: the last part (under tips and settings) is actually some good advice, although the background process limit is not saved in CM10 (and the max.mem tweak doesnt work), so you'll need to do that everytime at startup
Click to expand...
Click to collapse
please dude if you don't know how to tweak you can go i don't use this guide but it's a good one maybe you installed all those thing over a already tweaked rom, this guide if for clean stock, cm7/9/10/10.1
Nice guide...but I think you are wrong about the services.jar. You have to patch it when you use ICS or Jelly Bean, not on GB. And there is no Official CM7 on Gio.
Verstuurd van mijn GT-S5660
Verstuurd van mijn GT-S5660
tcris45 said:
please dude if you don't know how to tweak you can go i don't use this guide but it's a good one maybe you installed all those thing over a already tweaked rom, this guide if for clean stock, cm7/9/10/10.1
Click to expand...
Click to collapse
I applied it on a clean cm10.1 twice, had the same results, twice. I am not trying to talk down on someone elses work, but the fact is that some of the "tweaks" he talks about are never proven and often based on urban myths and the perception of people who applied them and saw improvement (placebo effect). fwiw, OP himself links to an article that busts some of the myths about tweaks, he tells people to apply...
So, maybe my device didnt start to lag more, in fact, it might have been more stable... however, setting the fs.file-max too big (as is one of the many things that activo script does) will make it less responsive, like there is a 100ms sleep between every action... I also experienced that with manual sysctl.
And some other tweaks that do work are still not great for everyone because they got other side effects that are not mentioned anywhere in this article. I got no idea why sync started giving errors and gmail stopped updating (twice) after these tweaks, but they did....
I am completely new to android, and should've done more research before blindly following some article that states to have some magical cure. But I am not new to linux and it seems this community suffers from the same kind of idiosyncrasies at the bottom end, where people constantly try to fix **** that isnt actually broken.
I'm talking about tweaks here obv, removing gapps. bloatware and lowering requirements for the OS is obv fine...
When someone's Gio lags, it's probably because they want to do stuff with it it's not made for, it's a slow device with minimal specs that does the pure core tasks as pda, phone, messenger and email, and as long as you do those it'll be fine. If you want more, buy a better phone. If it's that important to you and you dont have money, learn to appreciate what is actually important in life.
Nuff said.
Noobwithdumbquestions said:
I applied it on a clean cm10.1 twice, had the same results, twice. I am not trying to talk down on someone elses work, but the fact is that some of the "tweaks" he talks about are never proven and often based on urban myths and the perception of people who applied them and saw improvement (placebo effect). fwiw, OP himself links to an article that busts some of the myths about tweaks, he tells people to apply...
So, maybe my device didnt start to lag more, in fact, it might have been more stable... however, setting the fs.file-max too big (as is one of the many things that activo script does) will make it less responsive, like there is a 100ms sleep between every action... I also experienced that with manual sysctl.
And some other tweaks that do work are still not great for everyone because they got other side effects that are not mentioned anywhere in this article. I got no idea why sync started giving errors and gmail stopped updating (twice) after these tweaks, but they did....
I am completely new to android, and should've done more research before blindly following some article that states to have some magical cure. But I am not new to linux and it seems this community suffers from the same kind of idiosyncrasies at the bottom end, where people constantly try to fix **** that isnt actually broken.
I'm talking about tweaks here obv, removing gapps. bloatware and lowering requirements for the OS is obv fine...
When someone's Gio lags, it's probably because they want to do stuff with it it's not made for, it's a slow device with minimal specs that does the pure core tasks as pda, phone, messenger and email, and as long as you do those it'll be fine. If you want more, buy a better phone. If it's that important to you and you dont have money, learn to appreciate what is actually important in life.
Nuff said.
Click to expand...
Click to collapse
Look in signature, this thread is also there for Fit as well as Mini and is getting good response all over.. but you are the first one to complain on this. My advice to you- DO NOT USE THIS DO NOT POST HERE!
Some of your sayings are correct but, still this is the best way to increase performance. You might have did something wrong because this has been researched by me and some other people that this guide is perfect for low activity devices like ace, fit, mini, but if you dont want to use then dont use. I have NO PROBLEM.(I really dont get money or anything for this). lol..
FlemishDroid said:
Nice guide...but I think you are wrong about the services.jar. You have to patch it when you use ICS or Jelly Bean, not on GB. And there is no Official CM7 on Gio.
Verstuurd van mijn GT-S5660
Verstuurd van mijn GT-S5660
Click to expand...
Click to collapse
Yeah services.jar needs to be patched on ics and jellybean only. I didnt knew that official cm7 is not there for gio.. I dont own this device. sorry.
Noobwithdumbquestions said:
I applied it on a clean cm10.1 twice, had the same results, twice. I am not trying to talk down on someone elses work, but the fact is that some of the "tweaks" he talks about are never proven and often based on urban myths and the perception of people who applied them and saw improvement (placebo effect). fwiw, OP himself links to an article that busts some of the myths about tweaks, he tells people to apply...
So, maybe my device didnt start to lag more, in fact, it might have been more stable... however, setting the fs.file-max too big (as is one of the many things that activo script does) will make it less responsive, like there is a 100ms sleep between every action... I also experienced that with manual sysctl.
And some other tweaks that do work are still not great for everyone because they got other side effects that are not mentioned anywhere in this article. I got no idea why sync started giving errors and gmail stopped updating (twice) after these tweaks, but they did....
I am completely new to android, and should've done more research before blindly following some article that states to have some magical cure. But I am not new to linux and it seems this community suffers from the same kind of idiosyncrasies at the bottom end, where people constantly try to fix **** that isnt actually broken.
I'm talking about tweaks here obv, removing gapps. bloatware and lowering requirements for the OS is obv fine...
When someone's Gio lags, it's probably because they want to do stuff with it it's not made for, it's a slow device with minimal specs that does the pure core tasks as pda, phone, messenger and email, and as long as you do those it'll be fine. If you want more, buy a better phone. If it's that important to you and you dont have money, learn to appreciate what is actually important in life.
Nuff said.
Click to expand...
Click to collapse
okay go step by step and tell me what is it that is actually bothering you about the tweaking.(talk only about supercharger method not activ speedo).
yes most of the tweaks are utter bull**** The tweaks in the op(build prop ones are actually proven read the article again).As for dalvik size its recommended to keep a size around 48 so that you processes don't need to split their dalvik heaps into two separate piles thus reducing ram consumption.
Dark Passenger said:
okay go step by step and tell me what is it that is actually bothering you about the tweaking.(talk only about supercharger method not activ speedo).
yes most of the tweaks are utter bull**** The tweaks in the op(build prop ones are actually proven read the article again).As for dalvik size its recommended to keep a size around 48 so that you processes don't need to split their dalvik heaps into two separate piles thus reducing ram consumption.
Click to expand...
Click to collapse
I didnt use the supercharger method... The OP says the activo speedo is recommended, and the supercharger method is proposed as an alternative... I already said what problem I had with it (the response thing, and believe me or not, to me this difference is obvious and makes sense, I was able to reproduce it with just changing some of the same sysctl settings myself) but I wouldnt be surprised if there were more as it seems to do a buttload of things.
As far as the heapsize goes, I am not basing my conclusions on anything other than the OP's own link, which says things like:
dalvik.vm.heapgrowthlimit and dalvik.vm.heapsize - BUSTED,
Click to expand...
Click to collapse
This is one property that has cropped up recently in various build.prop recommendations for ICS. Typical suggested values range from “48m” all the way up to “256m”, likely motivated by the common misconception that more is better. The real purpose of this property is much less obvious than one might initially guess. It is also another one you should probably avoid changing.
Click to expand...
Click to collapse
Should you change this setting? Probably not.
Click to expand...
Click to collapse
Maybe you are right, I dont know all the technical implications, and I got no way to check it other than to test it and I see no difference in ram consumption if I change this property.
The ro.power.dissable thing might shut off wifi when in deep sleep and jumps back to mobile (I think, it happened after applying all tweaks and it seems the most likely thing to do that), but whatever causes that, you should warn people about that sort of thing as it can cost them money..
I didnt use it for long and I'm not an expert, i'm just sharing my findings, people can make up their own mind about it and share their experiences as well..
OJ said:
Look in signature, this thread is also there for Fit as well as Mini and is getting good response all over.. but you are the first one to complain on this. My advice to you- DO NOT USE THIS DO NOT POST HERE!
Some of your sayings are correct but, still this is the best way to increase performance. You might have did something wrong because this has been researched by me and some other people that this guide is perfect for low activity devices like ace, fit, mini, but if you dont want to use then dont use. I have NO PROBLEM.(I really dont get money or anything for this). lol..
Click to expand...
Click to collapse
Sorry, I didnt mean to offend you in any way and appreciate your effort... But telling me to stop posting just because I'm critical seems pretty backwards. If you only want people to say thanks and be greatful all the time, maybe you should start sharing horse pictures on a hello kitty forum...
I'm just sharing my experience and my problems might be related to my rom and it could very well work great on other phones or other roms... But I used a clean cm10.1, the CM10.1 rom almost everyone with a Gio uses, so I'd think it's still important to bring up my findings...
Noobwithdumbquestions said:
I didnt use the supercharger method... The OP says the activo speedo is recommended, and the supercharger method is proposed as an alternative... I already said what problem I had with it (the response thing, and believe me or not, to me this difference is obvious and makes sense, I was able to reproduce it with just changing some of the same sysctl settings myself) but I wouldnt be surprised if there were more as it seems to do a buttload of things.
As far as the heapsize goes, I am not basing my conclusions on anything other than the OP's own link, which says things like:
Maybe you are right, I dont know all the technical implications, and I got no way to check it other than to test it and I see no difference in ram consumption if I change this property.
The ro.power.dissable thing might shut off wifi when in deep sleep and jumps back to mobile (I think, it happened after applying all tweaks and it seems the most likely thing to do that), but whatever causes that, you should warn people about that sort of thing as it can cost them money..
I didnt use it for long and I'm not an expert, i'm just sharing my findings, people can make up their own mind about it and share their experiences as well..
Click to expand...
Click to collapse
the ro.power.disable.ril actually causes the phones radio to go to sleep so if your mobile data is off there is no reason to switch on rather the wifi might switch off(devs already stated so) and again switch back on once you get out of deep sleep.
its a good thing that you are coming back to provide a feedback and is appreciated(at least should be).
the change for dalvik.vm larger than 48 only allows the heap to grow to that value then split into a new heap since we can't/shouldn't/don't use apps with such a large memory footprint the chances of a split occurring post 48mb(gb and below) and 64mb(ics and above) is highly unlikely hence the changing the value to a larger quantity will make no difference.
PS personally even i dont like activo mainly cause i dont know how it works rather i use supercharger and its a much better option in my opinion.
Sorry, I didnt mean to offend you in any way and appreciate your effort... But telling me to stop posting just because I'm critical seems pretty backwards. If you only want people to say thanks and be greatful all the time, maybe you should start sharing horse pictures on a hello kitty forum...
I'm just sharing my experience and my problems might be related to my rom and it could very well work great on other phones or other roms... But I used a clean cm10.1, the CM10.1 rom almost everyone with a Gio uses, so I'd think it's still important to bring up my findings...
Click to expand...
Click to collapse
No, I already told you that many of your ideas are correct but, your way of expressing was not good.
Ex- You said that "Dont waste time on using this guide".
Now, if you think that was correct then please do not post again. If you are providing information then you can but, if you are telling people not to use this then dont post.
In fit's thread, Dark Passenger also wanted to express his ideas and wanted to help me. And I was happy about that. Because the way he helped me was like he really wanted to help. But, you was not polite as him.
You can ask Dark Passenger, there is a lot of information in the thread provided by him and I used that. And he never complained like you.
@Dark Passenger, please explain him.
OJ said:
No, I already told you that many of your ideas are correct but, your way of expressing was not good.
Ex- You said that "Dont waste time on using this guide".
Now, if you think that was correct then please do not post again. If you are providing information then you can but, if you are telling people not to use this then dont post.
Click to expand...
Click to collapse
Yeah, I was frustrated and my first response was not really fair. I agree.
Noobwithdumbquestions said:
Yeah, I was frustrated and my first response was not really fair. I agree.
Click to expand...
Click to collapse
When you use ics or jelly bean you need supercharger script and a patched services.jar (it's easy to do) because any other script don't works 100 % on it.
Sent from my GT-5660 using xda premium
Does this even need an explanation? Lollipop kills apps like it's his hobby.
Even with only a few light (on RAM) user apps running in the background you sometimes find yourself staring at your launcher home screen that, you could've sworn, was just showing a different app a second ago.
Or the times when, after multi-tasking a bit, your phone starts becoming painfully slow. Turns out that some apps are so stubborn that they go on strike (continuously restarting) when LP kills them.
I'm sure many have experienced this. And I have seen some devs address this issue here and there. I though it would be useful to gather the info into one thread, to ease our (or my?) frustration on this issue.
What I wanna know is, what causes it exactly (why didn't it happen on KK?), and is there a solution to this? Or at some way to calm LP down a bit with his killing of innocent apps.
Thanks.
Djalaal said:
Does this even need an explanation? Lollipop kills apps like it's his hobby.
Even with only a few light (on RAM) user apps running in the background you sometimes find yourself staring at your launcher home screen that, you could've sworn, was just showing a different app a second ago.
Or the times when, after multi-tasking a bit, your phone starts becoming painfully slow. Turns out that some apps are so stubborn that they go on strike (continuously restarting) when LP kills them.
I'm sure many have experienced this. And I have seen some devs address this issue here and there. I though it would be useful to gather the info into one thread, to ease our (or my?) frustration on this issue.
What I wanna know is, what causes it exactly (why didn't it happen on KK?), and is there a solution to this? Or at some way to calm LP down a bit with his killing of innocent apps.
Thanks.
Click to expand...
Click to collapse
Im running 1/8 FML with synapse injected R10 kernel on my toro and with ksm and laptop mode enabled in synapse, I haven't had a launcher redraw in days. I don't have anything whitelisted either. However, the trade-off I have at the moment is I cant seem to stream videos on my stock browser. Havent tried a different browser or anything. I just uncheck those two settings and reboot and all is well, but my phone certainly works much better now, and no redraws, with neph settings for LMK
Hope something helps someone!
Thanks
erk1725 said:
Im running 1/8 FML with synapse injected R10 kernel on my toro and with ksm and laptop mode enabled in synapse, I haven't had a launcher redraw in days. I don't have anything whitelisted either. However, the trade-off I have at the moment is I cant seem to stream videos on my stock browser. Havent tried a different browser or anything. I just uncheck those two settings and reboot and all is well, but my phone certainly works much better now, and no redraws, with neph settings for LMK
Hope something helps someone!
Thanks
Click to expand...
Click to collapse
Perhaps you can noobify that a bit, lol. I had to google almost everything you mentioned. As I understand it, this Synapse allows you to tweak the kernel? And this KSM settings can improve this RAM issue? Care to elaborate? And what is laptop mode?
I've read about adjusting the LMK values to calm LP down a little. Any idea though why this was so necessary in LP, but not in KK? Is stock LP 'naturally' more RAM hungry than KK?
Djalaal said:
Perhaps you can noobify that a bit, lol. I had to google almost everything you mentioned. As I understand it, this Synapse allows you to tweak the kernel? And this KSM settings can improve this RAM issue? Care to elaborate? And what is laptop mode?
I've read about adjusting the LMK values to calm LP down a little. Any idea though why this was so necessary in LP, but not in KK? Is stock LP 'naturally' more RAM hungry than KK?
Click to expand...
Click to collapse
I can try to elaborate little bit, as Ive been flashing things and researching xda a lot, but I am still noob in how/why things are the way they are. From what I gather lollipop just handles memory differently then kk did. I think that is some of the reason as to why the "recent apps" persist through reboots now. Remember, our device was not really supposed to run kk and certainly not meant to run lollipop. The developers here are without a doubt amazing in what they know and what they do for us users. A new kernel and driver was necessary to run lollipop on the aging gnex. Now, some of the issues we are experiencing is a google issue and will only seem to get fixed when they get around to it. I know my nexus 7 (old) has some memory issues and lag and redraws from time to time....not as much as I noticed with my gnex before the changes were made I stated in the above post. I recently helped my friend root and upgrade his oneplus one to lollipop and he has the same issues we all have, maybe not as bad, but they are noticeable
A lot of the questions you have, have been discussed recently in bsmitty83 kernel thread, since I asked them. There are links there as to what KSM and laptop mode are and what they do. KSM-kernel same page merging helps with RAM and I believe laptop mode helps to conserve power. A lot of these things are geared at devices with low ram like the aging gnex, but the developers have done a great job at making lollipop a daily driver. Most users I think use trickstermod from playstore to tune kernel settings, and that is ok, however, you must purchase the paid version to tweak low memory settings, which I did. However, synapse, also found on playstore can also be used to tweak kernel settings, but the kernel has to contain UCI support for the synapse app to work. Synapse has more settings available to tweak than trickster does, like KSM and laptop mode, which have helped me very much. The only kernel I'm aware of that has UCI support for synapse is bsmitty83 Full_Auto R10, because osmosis made it work
Hopefully this was rather accurate and helpful and not convoluted! ha.....im sure some more knowledgeable people will come and correct anything I said that may be incorrect, but in the meantime, read through the R10 kernel thread and see what you come up with
What ROM and kernel are you currently using?
Thank you
erk1725 said:
...
The only kernel I'm aware of that has UCI support for synapse is bsmitty83 Full_Auto R10, because osmosis made it work.
...
What ROM and kernel are you currently using?
Click to expand...
Click to collapse
I'm currently using AOSP rom (by freshgimmi) and the Full Auto R10 you mentioned. I'll try injecting the new ramdisk now and see how it goes.
I noticed this issue as well for the first several days . However once I installed the new bootanimation from arter97 the issue doesn't occur anymore. Not sure if it's related but all I did was mount /system as rw and copied into the new lollipop boot animation from here: http://forum.xda-developers.com/android/software/arm-arm64-android-5-0-lollipop-t3032247
Djalaal said:
Does this even need an explanation? Lollipop kills apps like it's his hobby.
Even with only a few light (on RAM) user apps running in the background you sometimes find yourself staring at your launcher home screen that, you could've sworn, was just showing a different app a second ago.
Or the times when, after multi-tasking a bit, your phone starts becoming painfully slow. Turns out that some apps are so stubborn that they go on strike (continuously restarting) when LP kills them.
I'm sure many have experienced this. And I have seen some devs address this issue here and there. I though it would be useful to gather the info into one thread, to ease our (or my?) frustration on this issue.
What I wanna know is, what causes it exactly (why didn't it happen on KK?), and is there a solution to this? Or at some way to calm LP down a bit with his killing of innocent apps.
Thanks.
Click to expand...
Click to collapse
SpideyTheMan said:
I noticed this issue as well for the first several days . However once I installed the new bootanimation from arter97 the issue doesn't occur anymore. Not sure if it's related but all I did was mount /system as rw and copied into the new lollipop boot animation from here: http://forum.xda-developers.com/android/software/arm-arm64-android-5-0-lollipop-t3032247
Click to expand...
Click to collapse
I know about this issue. It is a memory leak during boot. It is a good catch, though all you're changing is the bootanimation.zip. AFAIK, it should not affect your system's performance after boot, once your phone is up and running. My issue is a different thing entirely. I never got bootloops (that is, when not messing around with xposed).
Okay, you're right. As a test last night I switched from FML 5.0.2 to LiquidSmooth's LP ROM and I'm not seeing any aggressive app kills in LiquidSmooth.
Djalaal said:
I know about this issue. It is a memory leak during boot. It is a good catch, though all you're changing is the bootanimation.zip. AFAIK, it should not affect your system's performance after boot, once your phone is up and running. My issue is a different thing entirely. I never got bootloops (that is, when not messing around with xposed).
Click to expand...
Click to collapse
erk1725 said:
Im running 1/8 FML with synapse injected R10 kernel on my toro and with ksm and laptop mode enabled in synapse, I haven't had a launcher redraw in days. I don't have anything whitelisted either. However, the trade-off I have at the moment is I cant seem to stream videos on my stock browser. Havent tried a different browser or anything. I just uncheck those two settings and reboot and all is well, but my phone certainly works much better now, and no redraws, with neph settings for LMK
Hope something helps someone!
Thanks
Click to expand...
Click to collapse
I have got synapse up and running. I AM wondering though, what LMK settings are you using? Cause the neph settings I know of tell me to set empty app to 370, but synapse only allows max 320... If you're following different settings, could you link the post for me?
Djalaal said:
I have got synapse up and running. I AM wondering though, what LMK settings are you using? Cause the neph settings I know of tell me to set empty app to 370, but synapse only allows max 320... If you're following different settings, could you link the post for me?
Click to expand...
Click to collapse
Glad you got everything up and running.....Im using Neph's settings for LMK, and your correct the empty app only goes up to 320 in synapse. There was a post somewhere where Neph said he was still tweaking his LMK values and I believe he mentioned about lower empty app to 330 or something, so I just set it to 320 in synapse and call it a day