Related
I finally found a perfect ROM for my needs but I'm experiencing a few problems.
1. When syncing live feed on facebook for HTC sense, it just syncs forever. Really annoying, especially when auto-sync is enabled. I tried just turning live feed sync off, but it turned itself back on
2. Get soft reboots sometimes, with no specific reason.
3. Sometimes the statusbar image shifts 7-8 pixels to the right, leaving uncovered space on top left, reboot fixes it, but still, annoying.
4. On the messaging app, when I close the physical keyboard without leaving the conversation page, it leads to reloading of my homescreen and sometimes leads to bug, when launcher bar is on the wrong orientation. (this problem might be caused by the sense 3 lockscreen mod, it said somewhere that it modifies the messaging app)
5. How can I reduce the amount of my homescreens ? I use only 3 and I heard that it helps to free RAM
6. How can I format my partitions into ext4 ?
7. I heard of v6 supercharger script, can anyone help me with a step-to-step guide of how can I setup that and how will I benefit.
Been using this Rom for ages now and don't get these problems. Also, you shouldn't really need super charge to make it fast and smooth. Have you tried wiping and flashing again?
Sent from my HTC Vision using Tapatalk
I just did, let's see if it solves problems 2-4, number 1 is still there.
It is smooth but if the supercharger is going make it even better, why not ? Also I heard it extends battery life which is always good.
And I think I figured out the reason of live feed problem, I usually remove the friendstream stuff, and I think that may cause the trouble.
kkira13 said:
I finally found a perfect ROM for my needs but I'm experiencing a few problems.
1. When syncing live feed on facebook for HTC sense, it just syncs forever. Really annoying, especially when auto-sync is enabled. I tried just turning live feed sync off, but it turned itself back on
5. How can I reduce the amount of my homescreens ? I use only 3 and I heard that it helps to free RAM
6. How can I format my partitions into ext4 ?
7. I heard of v6 supercharger script, can anyone help me with a step-to-step guide of how can I setup that and how will I benefit.
Click to expand...
Click to collapse
1. I usually remove alot of apps and widgets that I don't use when on a Sense ROM. I found that getting rid of FB Chat makes this issue occur. Removing FriendStream widget might also do this too. Try restoring each app one at a time to pinpoint which one is causing the issue.
5. As far as i know, you can't reduce the number of homescreens on a Sense ROM unless the dev has made tweaks
6. Flash either 4EXT Recovery and change the partitions to ext4. Doing this does NOT erase any information on your partitions. Or you can grab SuperwipeG2+ext4 and this will format your phone to a clean slate and format the partitions to ext4 when when using CWM. This WILL erase everything on your phone.
7. I don't use supercharger, so I can't help you there.
I find when I oc too much I have gotten random reboots. Maybe lower oc a touch?
Sent from my HTC Desire Z using Tapatalk
Athrun88 thank you, great response. For 1 and 5 I came to same conclusions and you proved that I assumed right.
for 6 (ext partiotions) can you explain me how will I benefit from doing that ?
shortlived I didn't do any oc but I think it comes oc-ed so I'll try to lower CPU freq, thanks.
I do this when I use this rom:
Full wipe (system,data,cache,dalvik cache)
Flash rom
Flash unityv9 kernel
Mmsfix.zip
Once it boots I install oc/uvbeater2.apk (search google)
I set screen on profile to 1209/245 ondemand & screen off 500ish to lowest setting conservative
Then with 4ext recovery I set up a swap partition of 512mb
After that I run swap_enabler.sh (search google)
Sounds like a lot but it eliminated all my memory issues and laginess. No launcher restarts, performance/battery hits, or usability. As for v6 supercharger, I had nothing but problems, probably cause I never read everything
Sent from my HTC Vision using XDA App
Oh and statusbar... I just swipe up and down on it. Then it returns to normal. I still get that but not a deal breaker
Sent from my HTC Vision using XDA App
I wanted to investigate the sporadic freezing in my Galaxy S2. So, I turned on, show CPU usage under the developer's options in ICS. For reference I'm currently running Jedi Knight's latest rom.
I have attached a picture of my cpu usage while at my home screen. The number I've read to be average loads, and anything over 1.00 means trouble. I'm consistently over 10 for my one, five, and fifteen minutes averages. Also, my red bar which apparently measures time in kernel, sometimes spikes and correlates with a brief moment of unresponsiveness.
I've only seen two other screenshots and both users were under two. I was curious what everyone else's loads were. Also, let me know how frequent you have brief freezes, what kind of background apps you usually run. Include info like how many activities do you allow to run in background, do you force gpu rendering, etc. I can't wait to see other's results.
Sent from my SGH-T989
I got like 9/10/11 on mine. I always suspected that I have unusually bad battery life no matter what ROM I'm on, now I wonder if this has anything to do with it...
I'm on Eugene's Plain Jane ROM, which is an AOSP ICS ROM. The Manage Apps menu shows about 10 processes running. Force GPU is on.
ToastMan12 said:
I got like 9/10/11 on mine. I always suspected that I have unusually bad battery life no matter what ROM I'm on, now I wonder if this has anything to do with it...
I'm on Eugene's Plain Jane ROM, which is an AOSP ICS ROM. The Manage Apps menu shows about 10 processes running. Force GPU is on.
Click to expand...
Click to collapse
Thanks, for the response. Do you ever experience temporary freezes? My goal is to figure out if my mini-freezes are caused my memory or CPU.
Sorry for the bad picture quality. I posted through the android app. Anyway, I've left my phone alone for 15 minutes, and I got 8.7/8.7/8.7. I wonder if this uses a different scale than the Unix scale.
rsromano said:
Thanks, for the response. Do you ever experience temporary freezes? My goal is to figure out if my mini-freezes are caused my memory or CPU.
Sorry for the bad picture quality. I posted through the android app. Anyway, I've left my phone alone for 15 minutes, and I got 8.7/8.7/8.7. I wonder if this uses a different scale than the Unix scale.
Click to expand...
Click to collapse
Well, I wouldn't call them freezes, but sometimes performance seem to degrade for a fraction of a second and I experience like a small stutter. Doesn't seem to be unusual, but I'm not sure...
ToastMan12 said:
Well, I wouldn't call them freezes, but sometimes performance seem to degrade for a fraction of a second and I experience like a small stutter. Doesn't seem to be unusual, but I'm not sure...
Click to expand...
Click to collapse
That's normal. The only roms I know that work 100% smooth are Jelly Bean Roms on OFFICIALLY supported devices like the Nexus S and Galaxy Nexus. (Yes the Nexus S runs smoother than this phone. Not faster, smoother) but what OP is stating isn't normal in the least bit. My advice? Ditch that rom. I've never experienced such high CPU activity on any rom and its bad news. Your phone will eventually overheat and shut down. Never a good thing when the SoC gets no form of cooling.
Sent from my SGH-T989 using xda premium
RushAOZ said:
That's normal. The only roms I know that work 100% smooth are Jelly Bean Roms on OFFICIALLY supported devices like the Nexus S and Galaxy Nexus. (Yes the Nexus S runs smoother than this phone. Not faster, smoother) but what OP is stating isn't normal in the least bit. My advice? Ditch that rom. I've never experienced such high CPU activity on any rom and its bad news. Your phone will eventually overheat and shut down. Never a good thing when the SoC gets no form of cooling.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
So what do you do when CPU activity is still showing well over 1.0 (5-9) even after installing a fresh ROM? I just flashed the latest official CM10 nightly and have not installed anything other then gapps, and cpu usage is showing 9/8/5.
ToastMan12 said:
So what do you do when CPU activity is still showing well over 1.0 (5-9) even after installing a fresh ROM? I just flashed the latest official CM10 nightly and have not installed anything other then gapps, and cpu usage is showing 9/8/5.
Click to expand...
Click to collapse
Whoa.. if changing software doesn't help then you for yourself a hardware issue. If you experience lag and heat issues no matter what call tmo and get that handset replace.
Sent from my SGH-T989 using xda premium
That's the thing. I don't experience any lag and the phone is perfectly cool. It gets hot on intensive use, though.
Sent from my SAMSUNG-SGH-T989 using xda premium
I experience the exact same thing as ToastMan. My device always runs cool except when have multiple, heavy-use apps open for an extended period of time. My cpu usage percentages and used memory is always reasonable. Could it be something like an incompatible kernel? What are some debugging steps we could take? What kind of information would be valuable to you that we could provide?
Sent from my SGH-T989
rsromano said:
I experience the exact same thing as ToastMan. My device always runs cool except when have multiple, heavy-use apps open for an extended period of time. My cpu usage percentages and used memory is always reasonable. Could it be something like an incompatible kernel? What are some debugging steps we could take? What kind of information would be valuable to you that we could provide?
Sent from my SGH-T989
Click to expand...
Click to collapse
Is there a chance that maybe the reading is just wrong? Or maybe normal values on Android are different?
If several other people could just check their results and post them here it will be very helpful.
ToastMan12 said:
Is there a chance that maybe the reading is just wrong? Or maybe normal values on Android are different?
If several other people could just check their results and post them here it will be very helpful.
Click to expand...
Click to collapse
I was also thinking that it could be calibrated differently somehow. Like, if it was off by a factor of ten. My values would be much more reasonable. But I have seem several screenshots in the 1.0 range.
ToastMan12 said:
So what do you do when CPU activity is still showing well over 1.0 (5-9) even after installing a fresh ROM? I just flashed the latest official CM10 nightly and have not installed anything other then gapps, and cpu usage is showing 9/8/5.
Click to expand...
Click to collapse
Min has always been in the area of 9/9/10ish. My screen has never stuttered not even on GB, no rrs or sods on official cm10 so far either. My battery life is an entire day (16hrs) of listening to music/playing emulators nonstop.
Make sure you have the 2 idle processes in your battery. If you don't then your phone doesn't idle which will kill your battery life.
If you are using cwm non-touch make sure you use dark side tools or upgrade to touch recovery (cwm 6.x.x.x or TWRP... my favorite). Reinstall your ROM with a complete wipe, install gapps, boot it up then wait 10 mins before doing any setup.
If you are idling then look at your batt stats again... screen is probably waaaay up there... play with your brightness settings.
Hope this helped
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Relsig said:
Min has always been in the area of 9/9/10ish. My screen has never stuttered not even on GB, no rrs or sods on official cm10 so far either. My battery life is an entire day (16hrs) of listening to music/playing emulators nonstop.
Make sure you have the 2 idle processes in your battery. If you don't then your phone doesn't idle which will kill your battery life.
If you are using cwm non-touch make sure you use dark side tools or upgrade to touch recovery (cwm 6.x.x.x or TWRP... my favorite). Reinstall your ROM with a complete wipe, install gapps, boot it up then wait 10 mins before doing any setup.
Click to expand...
Click to collapse
Can you post a screenshot of your idle processes, please?
rsromano said:
Can you post a screenshot of your idle processes, please?
Click to expand...
Click to collapse
Cell standby, phone idle. They should be higher but I had my screen on several hours more than normal today (hence screen being 55%). Top reads 18 hours on, 21% battery life remaining.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
This post only pertains to Jellytime Sosei/BakedBean 4.1.2 and is for users experiencing problems with their A100, yours may not. This thread is not to debate or argue about the kernels, please keep that in mind
Hey guys, I was originally testing these ROMs for pio, and constantly am changing or tweaking things on the ROM to find what suits our A100 best. Pio was building these blind, so he has no way to thoroughly test the ROMs and such things as build.prop mods/tweaks as well as kernels.
Let me start by saying this, I AM IN NO WAY BASHING ANY DEVELOPER FOR THEIR WORK. I AM IN NO WAY BLAMING OR STATING THAT ANY BUGS/FLAWS ARE A DIRECT RESULT OF THEIR WORK. THE THINGS I AM LISTING ARE ISSUES/PROBLEMS/BUGS THAT I HAVE OBSERVED OR ENCOUNTERED, AND ALL BUGS/FLAWS WERE TESTED AGAINST THEIR EQUAL. EXAMPLE, USING THE godmachine81/linuxsociety KERNEL, THAN REPRODUCING THE SAME ENVIRONMENT, I WOULD RUN THE STOCK KERNEL FOR TESTING AND VERIFYING THE ERROR.
Kernel Observation:SODsEveryone, including myself, tend to automatically flash linuxsociety's GodMachine kernel v2.0, as it really is our only option for JellyBean/CM10/AOSP based ROMs. We do have ezTerry's kernel, but it has not "supposedly" been tweaked for 4.1.x systems. Although it is the base for GodMachine kernels. I've never used ezTerry's kernel,but I may test it like I've been testing GodMachine.
Anyways, for this ROM, I have found that the godmachine kernel performs poorly on Sosei ROM. With GodMachine kernel, I had tons of issues with constant BSOD/SOD. (Sleep of Death) The SODs were worse if you left wireless on, and the SODs were completely random, no matter what I did, if the tablet fell aslepp, it SOD'd on me. Using the stock kernel pio packed with the ROM, resolved much of this issue for me. The only time I have SOD on the stock kernel is when Wifi was left on, and the chances of this happening were 99% LESS LIKELY compared to GodMachine. You can combat this, by sacrificing battery life and using an app that's free on the playstore, WakeLock. If you choose to go this route, the "Partial_Wake_Lock" option consumes the least amount of battery while still preventing SOD. None of the 3 options for forcing wireless to stay on worked for stopping SOD.
RANDOM REBOOTS/CRASHING/FREEZINGI myself did not have many issues with random reboots, but I did have some issues with random app "force closes" and freezing to the point where you'd have the almost force close I call it, where you get an option to close or wait for the app. I have not had this issue using the stock kernel, unless related to the next topic...
GPU/VIDEO INSTABILITY/ODDITIESI, as well as a few others, have reported issues with display. Most users have noticed an issue with flashing lines, tearing, and artifacts on the desktop. I have also had issues when play a THD/HD game, for example Modern Combat 3: Fallen Nation HD, where anytime after about 20-30min, the display would become compltely distored, almost like when you were trying to pick up a TV station using rabbit ear antennas, and the game crashes/freezes, but you do not get an option to force close, so you have to use the Navigation bar HOME button to get yourself out of it, than you need to kill the game anyway you want, but if you don't kill it, it will load you back to that distorted, frozen image.
In the GodMachine kernel, the GPU is overclocked as well as being able to overclock your CPU, but you cannot adjust the GPU yourself with any application. Linuxsociety states: "Stable GPU Overclock @ 450mhz (scales from 300 - 450)"
I do not have these issues with video when using the stock kernel, nor do I notice any lack of GPU performance with lack of GPU overclocking.
In my honest opinion, I STRONGLY RECOMMEND the STOCK KERNEL. Yes it is lacking in some features, but it is capable of being overclocked as well if your interested in doing so. Using the interactive governor provides the smoothest performance and still retains some battery savings. Conservative, OnDemand, userspace, and Performance are offered as well. The I/O Scheduler only has NOOP available, but if you do some reading, NOOP is actually recommended for Flash Devices, like ours.
To get back to pio's stock kernel, you can boot into recovery, wipe cache and dalvik, and dirty flash the ROM.
BUILD.PROP EDITINGI cannot even begin to tell you the amount of hours I invested in testing and editing the build.prop to obtain what I find to be the most stable while still possibly enhancing performance/responsiveness and battery life. I will link you to my FINAL build.prop mod for you to download if you'd like. In all reality this consisted of just commenting out several lines in the original build.prop that our A100 did not like. This will also fix issues with the video camera recording if you have them, as well as improve certain app and system performance and functions. I've also had more reliability and just odd **** happen when I use the TCP/IP buffer enhancement code lines so those have been commented out as well to keep WiFi stable. I really see no performance gains with them other than SpeedTest and there is a reason, I am a Networking IT Student, and don't feel like explaining that now in this thread. lol
Download build.prop.sosei__tweaked
Using a FileExplorer with ROOT LEVEL ACCESS (I recommend ESFileExplorer),
Copy build.prop.sosei__tweaked into the /system folder
Rename current build.prop to build.prop.bak
Rename build.prop.sosei__tweaked to build.prop
Reboot into recovery (TWRP or CWM) and wipe dalvik cache & cache, reboot
make sure you wait ten, reboot and wait 5-10 before you start using your tablet
This is all in my observed, hands-on testing and experience, and everyone's results will vary based upon factors such as user setup, apps install, the way a user even uses their tablet etc
I hope this might help/inform some of you guys.
Very nice, thanks for taking the time to put this together for the users. How did that kernel I built for you do?
Sent from my Galaxy Nexus using Tapatalk 2
pio_masaki said:
Very nice, thanks for taking the time to put this together for the users. How did that kernel I built for you do?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I hadn't flashed it yet as i had gotten my tablet into a perfect state, for me, with this ROM and stock kernel, lol
The changed prob won't stop sod, but in my theroy should correct the video glitches.
I'll try it soon and let you know.
G2x-temasek CM7 Nightly 11/18/12 Build, Trinity ELP Kernel
I'm using/testing this rom along with gm's kernel. I have not had wake SOD issue. It sometime takes a couple if clicks on the power button for it to wake, not sure if this is the issue you're referring to as SOD. Everything seems to work great so far. Netflix, audio, headphone all work well. I have always wanted some aokp flavor on this tab, and now that wish is granted thanks to the awesome work of pio, bb devs and gm.
S-Beamed from my GSIII via xda premium
[email protected] said:
I'm using/testing this rom along with gm's kernel. I have not had wake SOD issue. It sometime takes a couple if clicks on the power button for it to wake, not sure if this is the issue you're referring to as SOD. Everything seems to work great so far. Netflix, audio, headphone all work well. I have always wanted some aokp flavor on this tab, and now that wish is granted thanks to the awesome work of pio, bb devs and gm.
S-Beamed from my GSIII via xda premium
Click to expand...
Click to collapse
No, I had sod constantly. But not slow wake up. I get slow wake sometimes on stock, but atleast it will wake.
Everyone's tablet is not the same, some hate the GM kernel.
Mine seems to be one of those, but had I known how smooth and stable the stock kernel was, I prob would have stopped using GM awhile ago, I've had nothing but issues with it, if you've seen any of my old posts over last couple of months.
G2x-temasek CM7 Nightly 11/18/12 Build, Trinity ELP Kernel
Other than a couple of SOD's I haven't had any other issues with the gm kernel. I have since bumped up the minimum speed to 312 Mhz and that has seemed to fix the SOD issue but I still need more time to conclude that. I'm also getting some impressive quadrant scores with it too (3046) and that's with a fully loaded non-tweaked system. The only reason I like the gm kernel is the variety of I/O schedulers and governors...there is absolutely nothing wrong with the stock kernel. I'm still very happy with the JB ROM, I have it set up almost identical to my Samsung Nexus phone which makes it very convenient.
GM SOD Issue Resolved ( For Me)
I can now safely say after 4 days of testing that raising my minimum speed in the GM kernel to 312 Mhz has completely eliminated the SOD issues. I know that every device acts differently but this is working on mine!
Gulfstream 650 said:
I can now safely say after 4 days of testing that raising my minimum speed in the GM kernel to 312 Mhz has completely eliminated the SOD issues. I know that every device acts differently but this is working on mine!
Click to expand...
Click to collapse
I didn't want to do that myself and lose the extra battery juice.
The point is it should be able to UC down to 216 and hold there with no issues.
The stock kernel does it perfectly well with no ill effects.
I have a modified Godmachine kernel that is unreleased and I will be testing it soon.
G2x-CM7 Nightly 11/18/12 Build, Trinity ELP Kernel
thanks for the tweaks and info! buti have never encountered a SOD. what happens? it just wont wake up after sleeping? if it happens can you just turn off your tablet by holding the power button or do you have to wait for it to die?
Jaydizzle414 said:
thanks for the tweaks and info! buti have never encountered a SOD. what happens? it just wont wake up after sleeping? if it happens can you just turn off your tablet by holding the power button or do you have to wait for it to die?
Click to expand...
Click to collapse
SoD is just a failure to resume from sleep, reset button or hold power will reset it to normal. Some tegra2 devices have it, some don't, even among the same series, like a100s. The best way to combat it is to not sleep, but of course battery sucks.
Sent from my Thrive - Unified B4 - Balthesaur V2.71
justjackyl said:
I didn't want to do that myself and lose the extra battery juice.
The point is it should be able to UC down to 216 and hold there with no issues.
The stock kernel does it perfectly well with no ill effects.
I have a modified Godmachine kernel that is unreleased and I will be testing it soon.
G2x-CM7 Nightly 11/18/12 Build, Trinity ELP Kernel
Click to expand...
Click to collapse
I can understand not wanting to lose the extra battery juice, lots of what we do is to extend it. I did however undervolt the 315 slot to the same as the 216 (750 mV) so there's no addition battery drain. It's a win-win situation! Let us know how the unreleased version works out, I'm always looking for options.
Can you not dowloadd this from your tab? When I tried it said the download was unsuccessful
Sent from my A100 using XDA premium.
Jaydizzle414 said:
Can you not dowloadd this from your tab? When I tried it said the download was unsuccessful
Sent from my A100 using XDA premium.
Click to expand...
Click to collapse
Just try again, even on WiFi it can be hit or miss.
Sent from my Galaxy Nexus using Tapatalk 2
pio_masaki said:
Just try again, even on WiFi it can be hit or miss.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I've tried like a bajillion times lol probably my fault or something. Not that big of a deal though
Sent from my A100 using XDA premium.
Jaydizzle414 said:
I've tried like a bajillion times lol probably my fault or something. Not that big of a deal though
Sent from my A100 using XDA premium.
Click to expand...
Click to collapse
Try clearing the data on the 'download manager' in the settings > apps. Then retrying.
Romman0 said:
Try clearing the data on the 'download manager' in the settings > apps. Then retrying.
Click to expand...
Click to collapse
Didn't work but thanks for helping
Sent from my A100 using XDA premium.
This is what it shows
Sent from my A100 using XDA premium.
Jaydizzle414 said:
This is what it shows
Sent from my A100 using XDA premium.
Click to expand...
Click to collapse
Looks like network traffic or just a router/tab reset needed. Or try later tonight.
Sent from my Galaxy Nexus using Tapatalk 2
pm me ur gmail and ill send it directly
G2x-CM7 Nightly 11/18/12 Build, Trinity ELP Kernel
..
So my phone went from being an unusable, laggy, crashing, ****ty phone in a matter of 30 seconds.
I'll explain more.
I had previously posted a thread about my Nexus' low i/o scores, and since it wasn't rooted, we concluded that the best way (and maybe only way) to fix it was by doing a factory reset. It fixed the problem, but I lost all my stuff, and it was a hassle.
Now it's back. Why? Because I thought the phone could handle having less than 3GB of free space. Boy was I wrong. That 1.6GB video I copied to my phone pushed it over the edge of ****ty i/o performance, never to return without a factory reset. I freed up 6GB+ of space, cleared all caches, even restored from a backup in cwm. The phone still suffers from painfully slow benchmarks (only i/o), and stutters at the simplest tasks.
What can I do? I have to reset again? This is not my vision of a well designed OS with such a flaw.
shao3m said:
So my phone went from being an unusable, laggy, crashing, ****ty phone in a matter of 30 seconds.
I'll explain more.
I had previously posted a thread about my Nexus' low i/o scores, and since it wasn't rooted, we concluded that the best way (and maybe only way) to fix it was by doing a factory reset. It fixed the problem, but I lost all my stuff, and it was a hassle.
Now it's back. Why? Because I thought the phone could handle having less than 3GB of free space. Boy was I wrong. That 1.6GB video I copied to my phone pushed it over the edge of ****ty i/o performance, never to return without a factory reset. I freed up 6GB+ of space, cleared all caches, even restored from a backup in cwm. The phone still suffers from painfully slow benchmarks (only i/o), and stutters at the simplest tasks.
What can I do? I have to reset again? This is not my vision of a well designed OS with such a flaw.
Click to expand...
Click to collapse
It's a problem with the memory chip i guess, my phone runs like a champ, filled the storage to the brim once and it's still pretty fast.
I recommend you go on the Play Store and download a paid app called Seeder.
This app is NOT a placebo effect. It does work.
If you don't want to pay, type in Seeder v1.4 XDA, and you'll be able to get it for free (not pirating, dev posted it up for free on this site. So zip it. Thanks. ^_^)
Why is the developer doing this? I dunno. But the benefit of the play store version is updates. Which is what I recommend.
Let me know how it goes. Made my nexus faster is all I can say.
--------------------------------------------------
If I have helped you.... hit that sexy thanks button. ^_^
Seeder
Just installed Seeder per the recommendation above
...Woah
I don't think Seeder will fix this - worth a try though (the dev states itself it does not have this effect on Android 4+).
I had the same problem (rooted) and only was able fix this issue by completely resetting my device. Very annoying indeed...
I don't know why it occured and thought it was too much playing with different ROMs. Once I found a ROM I'm really happy with and used for months without "playing" with other ROMs (liquidsmooth) it was all great but one day this i/o issue occured again out of nowhere. Only way to fix it -> reset.
I too would be really interested in knowing why this happens and how to avoid it...
why reccomend seeder for this?it's a unrelated thing,and doesn't fix any OP problems.
It helps stop lag. Which makes the phone feel faster. So yes it is related. And it does work on android 4.1.2 for me very well.
I'm clocked at 2xx-729 and have zero lags.
And yes I did factory reset recently and it didnt really help besides giving me faster boots. Seeder helped me ALOT. It may increase the io but it does make it faster since it reduces lag.
--------------------------------------------------
If I have helped you.... hit that sexy thanks button. ^_^
I'm just going to leave this here since it will actually help with the io problems instead of some entropy generator.
http://forum.xda-developers.com/showthread.php?t=2104326
Sent from my Galaxy Nexus using Tapatalk 2
geoffcorey said:
I'm just going to leave this here since it will actually help with the io problems instead of some entropy generator.
http://forum.xda-developers.com/showthread.php?t=2104326
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
:good: THIS. I believe this will, more or less, solve your problem without having to do factory reset
geoffcorey said:
I'm just going to leave this here since it will actually help with the io problems instead of some entropy generator.
http://forum.xda-developers.com/showthread.php?t=2104326
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
YES! This definately helped with my lags! :good:
After 1 month of using my phone, it started to lag again. So I tried Seeder first, which - as expected - didn't solve the problem (I will leave it activated though and observe it).
But using LagFix is now like having a new phone (or at least a fresh install ) and everything is hyperfast again! Thanks for the hint! Really great tool! (Though I would be more happy to not to have to use these kind of tools...)
I'm asking because I'm frequently out of RAM, causing extreme lags and launcher reboots. I know the CPU reserves 300MB, leaving 700MB, but how much do ROMs typically occupy? Any recommendation for leaner ROMs? Or perhaps there are modifications to enable more aggressive task killing (non-background tasks)?
843 said:
I'm asking because I'm frequently out of RAM, causing extreme lags and launcher reboots. I know the CPU reserves 300MB, leaving 700MB, but how much do ROMs typically occupy? Any recommendation for leaner ROMs? Or perhaps there are modifications to enable more aggressive task killing (non-background tasks)?
Click to expand...
Click to collapse
Run out of RAM? never again with this Mod
Gnex Supported! :good::good::good:
http://forum.xda-developers.com/showthread.php?t=2145133
How would that work since my GNex doesn't have an SD card? Isn't everything on the same internal memory?
843 said:
How would that work since my GNex doesn't have an SD card? Isn't everything on the same internal memory?
Click to expand...
Click to collapse
First of all, that mod puts it in /system, /data and/or /cache. So it doesn't even try to use the sd card regardless.
Second, I just thought i would try it out and it throws out an error "incompatible with your device Galaxy Nexus (toro).
I figured maybe i would give swapper 2 a go again. It hasn't been updated in ages, but it seems to work. You can leave it on sdcard (which is just internal memory anyway) or change the directory to any you want. I changed mine to /cache since my sdcard is kind of full. Can even change the swapiness within the app. Only downside is the limit for it is 256mb. So far it seems to be working properly on Verizon Galaxy Nexus stock, rooted, 4.1.1 with lean kernel.
Sent from my Galaxy Nexus using Tapatalk 2
I have done some tinkering. What seems to work for me is limiting background processes to 4 or less. These turn out to be cached processes which keep opened apps open. They eat up your remaining RAM and should ideally be removed if an app you're trying to run demands it. However, the removal process causes significant lag, possibly due to the slow internal memory the GNex has.
I'm running CM10 (4.1.2), and I have 245MB free right now. It has gone down to as low as 150MB, but rarely below. When using 4.2.2 based roms, I get as low as 40-50MB, which causes problems. I don't have high hopes for 4.3 right now.