Related
This forum seems to be really negative. And it scares people away. I don't want to start a thread that says "OMG, I love this phone so much" because nobody wants to read that and, well I don't love a phone that much. So I figure why not have a thread that has all the known issues? So people can have a better idea of what to expect.
Well, to start off, I want to say there is no perfect phone in this market. Every phone has issues. Anyway, you will use it for only 18 months and then throw it away. So don't act like you are making a life decision.
1. hardware related
(1) Random shut down.
Possibility: 1/5. Reported by some users. I personally never have this issue.
Solution: exchange for a new one.
(2) Poor battery life.
Possibility: 5/5. Don't have high hopes on battery because it is a huge smart phone. But don't freak out if it only lasts for 5 hours in the first day. It will get better (much better) after several cycles.
Solution: There are tricks all over the internet.
(3) Soft key backlighting isn’t tied to screen timeout
Possibility: 5/5. Soft key backlight time is about 2s. It can't be changed, no matter what the screen timeout is.
Solution: none.
2. software related
(1) Performance Lag.
Possibility: 4/5. As powerful as this phone is, you will feel sluggish once in a while. For example, transition delay, touch response delay. Most annoying: phone freezes when installing apps from the market.
Solution: by using Launch Pro or ADW, you can have a better and smoother experience. But the phone still freezes when installing apps. All you can do is to wait for the installation to finish. Things might get better after the 2.2 update. But there is no official date for Froyo in the US market yet, so I can't say that's a solution.
(2) GPS
Possibility: 4.5/5. Seems like lot of users have this problem. Few users claim theirs are fine.
Solution: None. Samsung promises a fix by the end of Sept.
(3) Sideload apps
Possibility: 5/5. You can't install out-of-market apps.
Solution: You can root. If you don't want to ruin your warranty (I don't), you can use Sideload Wonder Machine. I used it for Genie Widget and Angry Bird. Both worked fine.
(4) Calendar
Possibility: 5/5. When adding an event, the default calendar is the locally "My calendar". And it won't get synced to your online calendar. You have to manually change it to your gmail calendar EVERY TIME.
Solution: none.
(5) Browser brightness setting
Possibility: 5/5. There is a separate brightness setting for browser. It could be annoying when the screen has different level of brightness.
Solution: none.
(6) Music player
Possibility: 4/5. Stock music player doesn't recognize playlist. You might be frustrated to find an alternative one. you may have to pay for a music player.
Solution: I want to say none. You can always find one in the market. But it was not a pleasant experience for me.
(7) status bar trick
Possibility: 2.5/5. You can slide on your status bar to change the brightness. It could be a welcome trick or annoying feature. Screen brightness is so important to your precious battery life, sometimes you don't want to accidentally slide on your status bar.
Solution: none. You can love it or hate it.
I just want to list all the issues that you'll have. Potential buyers can make their own judgement. Please reply if you can think of any other problems. But please don't say things like "you can always root" or "flash your rom", or "there is an fix coming soon".
[update] A lot of the items I listed were not defective issues. But they could be complaints. They could be something you don't like and you can't find a way to change. And i don't care if it's from AT&T or from Samsung or from Google. As long as it might be a problem, I am listing it here.
Calendar:
Does not recognize phone numbers or URLs in any part of calendar event (no click to call or launch web page)
Contacts:
Looking up GAL contact (global address list) only available from compose email screen, and only returns email, not phone number.
Email:
No control over which folders sync (Exchange); No select all option; other minor issues
mwxiao said:
Well, to start off, I want to say there is no perfect phone in this market. Every phone has issues. Anyway, you will use it for only 18 months and then throw it away. So don't act like you are making a life decision.
Click to expand...
Click to collapse
Agreed. Most new phones especially complicated ones have issues. But it would be nice for it to work as advertised.
We don't really know yet if some of these are software or hardware. The GPS issue for one looks like software but may turn out to be hardware. Too soon to tell. Let's hope they have a real fix for it because even though it is not critical, it is a useful multi-purpose tool that many of us rely on daily. I expect it to work. I am patiently waiting for the promised fix but if it doesn't prove reliable, I have to find a different phone.
Random shut downs. I returned one Captivate because of this. Again, hard to tell if its hardware or software but I am assuming hardware and returned mine.
Poor battery life. Not as much an issue as it is a relative expectation. Seems a lot of the faster Android devices and even the IP4 run out of juice pretty quickly. My BB 9700 will last twice as long but maybe that's because the screen is half the size, half the resolution and half the brightness.
Also, a handful of Captivates have a problem getting into recovery/download via the three button method. Only a handful as of now.
As for the software issues... well, let's hope we get plenty of good ROMs from Samsung and plenty of modded ROMs from the smart folks around here!
mwxiao said:
This forum seems to be really negative. And it scares people away. I don't want to start a thread that says "OMG, I love this phone so much" because nobody wants to read that and, well I don't love a phone that much. So I figure why not have a thread that has all the known issues? So people can have a better idea of what to expect.
Well, to start off, I want to say there is no perfect phone in this market. Every phone has issues. Anyway, you will use it for only 18 months and then throw it away. So don't act like you are making a life decision.
1. hardware related
(1) Random shut down.
Possibility: 1/5. Reported by some users. I personally never have this issue.
Solution: exchange for a new one.
(2) Poor battery life.
Possibility: 5/5. Don't have high hopes on battery because it is a huge smart phone. But don't freak out if it only lasts for 5 hours in the first day. It will get better (much better) after several cycles.
Solution: There are tricks all over the internet.
(3) Soft key backlighting isn’t tied to screen timeout
Possibility: 5/5. Soft key backlight time is about 2s. It can't be changed, no matter what the screen timeout is.
Solution: none.
2. software related
(1) Performance Lag.
Possibility: 4/5. As powerful as this phone is, you will feel sluggish once in a while. For example, transition delay, touch response delay. Most annoying: phone freezes when installing apps from the market.
Solution: by using Launch Pro or ADW, you can have a better and smoother experience. But the phone still freezes when installing apps. All you can do is to wait for the installation to finish. Things might get better after the 2.2 update. But there is no official date for Froyo in the US market yet, so I can't say that's a solution.
(2) GPS
Possibility: 4.5/5. Seems like lot of users have this problem. Few users claim theirs are fine.
Solution: None. Samsung promises a fix by the end of Sept.
(3) Sideload apps
Possibility: 5/5. You can't install out-of-market apps.
Solution: You can root. If you don't want to ruin your warranty (I don't), you can use Sideload Wonder Machine. I used it for Genie Widget and Angry Bird. Both worked fine.
(4) Calendar
Possibility: 5/5. When adding an event, the default calendar is the locally "My calendar". And it won't get synced to your online calendar. You have to manually change it to your gmail calendar EVERY TIME.
Solution: none.
(5) Browser brightness setting
Possibility: 5/5. There is a separate brightness setting for browser. It could be annoying when the screen has different level of brightness.
Solution: none.
(6) Music player
Possibility: 4/5. Stock music player doesn't recognize playlist. You might be frustrated to find an alternative one. you may have to pay for a music player.
Solution: I want to say none. You can always find one in the market. But it was not a pleasant experience for me.
(7) status bar trick
Possibility: 2.5/5. You can slide on your status bar to change the brightness. It could be a welcome trick or annoying feature. Screen brightness is so important to your precious battery life, sometimes you don't want to accidentally slide on your status bar.
Solution: none. You can love it or hate it.
I just want to list all the issues that you'll have. Potential buyers can make their own judgement. Please reply if you can think of any other problems. But please don't say things like "you can always root" or "flash your rom", or "there is an fix coming soon".
Click to expand...
Click to collapse
ok well I want to address these one at a time
1) random shutdowns - true, seems very hit or miss on who it affects and how often.
2) poor battery life - I have to strongly disagree with this. almost everyone seems capable of eeking at least a day out of their battery even with heavy usage. if you aren't getting at least a day, either the battery or unit is defective in some astounding way or you're using GPS while streaming videos for 7 hours a day.
3) soft key timeout - this isn't an "issue." if the iPhone 4's antenna thing is a "total non-issue," so is this. it may not be the most sensible decision to have them on different timers (it would be preferred that we could manually set this), but this isn't an "issue," this is just personal preference. I personally don't mind it at all since I rarely press them when I'm using my screen, and if you truly use this phone, it isn't hard to remember where they are
1) performance lag - true, but I'm kind of willing to believe a lot of this will be fixed when froyo is released. to me, it's pretty obvious samsung is working on this since the JH2/JH3 builds are way faster than JF6 without any modifications.
2) GPS - definitely an issue I can agree with. Samsung should have been on this faster (even the Fascinate users are claiming issues already). they should have rolled out of a fix by now considering how many phones they have out there in the world.
3) sideloading apps - seriously? this isn't Samsung, this is AT&T. If you've got an android phone on AT&T, this is what you're going to have to live with without personal modification. don't like it? stop being on AT&T
4) Calendar - can't comment, don't use
5) Browser Brightness - again, a non-issue. you can use the slider bar to change it on the fly (which is a massive improvement over other android phones IMO) or set it to whatever you'd like
6) Music Player - can't comment, replaced with stock 2.1-update1 music player for personal preference
7) status bar trick - I don't see how this is even considered an issue. if you're manually setting your brightness, does it make more sense to do this or go into settings, sounds and display, brightness, and adjusting it there to change it right back moments later? no. I personally think this was a brilliant move on samsung's part. I keep my screen on the lowest brightness almost always, and then I realize I need to turn it up because the sun is too bright, so I can just fix it instantly by pulling it down, turning it up, and then turn it down when I'm done. if you're doing automatic brightness, this "trick" doesn't even work
edit: I'm just saying that if you're going to bash the phone for these issues, let's agree what is actually an issue and what is just user-preference related
Kaik541 said:
edit: I'm just saying that if you're going to bash the phone for these issues, let's agree what is actually an issue and what is just user-preference related
Click to expand...
Click to collapse
I agree - separate bugs that affect 90% of the phones from other variables.
My phone has never rebooted or shutdown on its own, and it is not something 90% of the people are complaining about - unlike GPS.
Battery life is subjective and based on usage. Compared to my iPhone it is about the same. BB - definitely better, but as mentioned the screen is smaller, and BB controls the sync settings - so not a fair compare.
Music player has a workaround for playlists - move music to phone, go to recently added playlist, select all, create new playlist. Not ideal, but a different way to do things. There are free music players too.
Some things - like the soft key lights - are sort of a gray area - is this a feature implementation or a bug? Probably a feature issue. It is easy for one person's feature request to be another person's bug report.
Kaik541 said:
I'm just saying that if you're going to bash the phone for these issues, let's agree what is actually an issue and what is just user-preference related
Click to expand...
Click to collapse
What I am trying to do, is to list the issues (or complaints if you will) that have been posted. The issues I listed might not necessarily be defective of the phone. They were the things that may raise your eyebrow. I tried my best to be objective.
In terms of user-preference, I won't post it if it is really user-preference. The issues I listed, e.g., status-bar trick, brightness setting, they are NOT configurable. If you like them, great. But if not, sorry there is NO way to change them. That's why I list them as issues. I want to list all the potential issues/complaints so that potential buyers have a better idea what to expect.
mwxiao said:
What I am trying to do, is to list the issues (or complaints if you will) that have been posted. The issues I listed might not necessarily be defective of the phone. They were the things that may raise your eyebrow. I tried my best to be objective.
In terms of user-preference, I won't post it if it is really user-preference. The issues I listed, e.g., status-bar trick, brightness setting, they are NOT configurable. If you like them, great. But if not, sorry there is NO way to change them. That's why I list them as issues. I want to list all the potential issues/complaints so that potential buyers have a better idea what to expect.
Click to expand...
Click to collapse
OK, i got you. But some of these issue/complaints are from a vocal minority and I would say they unfairly describe the captivate - especially things like battery life and random shutdowns. Battery life depends on what you do and where you are located. Reboots are probably a hardware issue involving a small group.
IMHO if you are going to mention hardware issues that affect an uncounted minority, then you have to add all the weird stuff people have returned phones for - speaker not working, screen pixel out, volume switch, etc.
alphadog00 said:
IMHO if you are going to mention hardware issues that affect an uncounted minority, then you have to add all the weird stuff people have returned phones for - speaker not working, screen pixel out, volume switch, etc.
Click to expand...
Click to collapse
Well, if there was a loooong thread about screen pixel or speaker, I would have listed them already. Unfortunately, I only see several threads about random shutdown. I did list it as low possibility though, meaning it only happens for a very small percentage of users.
Would there be any merit to posting some of the individual issues as their own thread with a yes/no poll, so that we can see relative numbers about how many people are being affected by a particular problem. Granted, it wouldn't be "scientific data" as the typical poster to those threads would probably be users looking for the info or having the problem, but still...
FWIW, I have a Captivate that is going back today due to the randon shut down problem. Funny enough, the GPS works perfectly.
I installed @dwitherell's TweakStock 1.4 on my Charge about 5 weeks ago, and I've mostly been happy with it. The one problem I kept running into was deteriorating performance over time, leading to frequent hard lockups requiring hard reboots. I'd gotten to the point where I needed to reboot the phone nearly every day. Having multiple active apps also tended to cause problems, for example Cardiotrainer + Rhapsody music.
Sometimes when the lag hit I was able to get a CPU usage report before the phone fully locked up. At such times I'd see kswapd0 eating a large portion of CPU. That suggested memory problems. I tried tweaking my OOM kill thresholds, to no avail.
This morning, based on some research, I took a look through my build.prop and noticed that this ROM's default VM heap size is a whopping 72MB. That sounded very high, compared to my previous phones where it was 24-32MB. I installed the VM Heap tool, knocked the heap size down to 48MB, and rebooted. My phone has been running as smooth as silk since, even with multiple simultaneously active apps running.
I'll keep watching to see how this holds up over time, but the difference even over a few hours is noticeable enough that I thought I'd report my findings right away. Regrettably, XDA discriminates against new members, so I can't post into the TweakStock developer thread as I would prefer. HTH!
thanks for the tip... just installed Eclipse, at its VM is 48MB.
tweakstock was running great for me though, so real problems like you said. my only problem (minor) was my Scrabble app being such a battery and data hog...
Thanks for the tip -- I had noticed this too, will give it a try. Though I'm on a different version of TweakStock I noticed the heap size is 72 here as well. Trying 48 for a while... will chime in if there's improvement.
- A
It is likely set high because it was found that increasing the VM heap size helped curb hot boots on heavily modified ROMs.
Interesting, thanks for the history @imnuts! I did encounter the hot boot issues some months back on earlier iterations of Gingerbread ROMs for the Charge. I will keep an eye out for hot boots to see if my 48Mb VM heap size is too low, or swap lag if it is still too high. Perhaps we will all have to try to find the best heap size for our usage patterns, as there may be no best one-size-fits-all setting.
Can't remember where, but I think I once read something that said 40 MB is the absolute best size to go with for a variety of reasons. For what that's worth...
Back on tweak stock.... can I just edit the build.prop or do I have to download VM heap?
Thanks!
tappin' that....
jco23 said:
Back on tweak stock.... can I just edit the build.prop or do I have to download VM heap?
Thanks!
tappin' that....
Click to expand...
Click to collapse
Just set the value in the build.prop.
jco23 said:
Back on tweak stock.... can I just edit the build.prop or do I have to download VM heap?
Thanks!
tappin' that....
Click to expand...
Click to collapse
Only change back only when you have issue. I currently using 72m since day one and it's working fine, super fast launching apps.
Fwiw stock settings are 64
Was so thrilled to see this recommendation, as I observed that my phone is really struggling to memory, and then kswapd0 kicks in. Tried to change it to 48MB, then to 64MB. Did not see any improvements. It looks like all apps get pre-loaded into memory, and once free memory hits less than ~80MB, the phone becomes sluggish. Once I kill all apps, the phone is back to normal snappy lag-free operation. Free memory at that point is around 135MB. This is even worse when I insert the phone into car dock. Re-draw takes about 5-7 seconds, swiping is about 2-3 seconds. In few moments it becomes ok, but still laggy.
No problems here
Been on TS1.4 w/ PBJ for about a month now, everything is still as snappy as day one. Thought I was having issues at one point but it turned out it was actually an app, Stitcher Radio, that was eating CPU and draining battery (even though I never launched it). I've over/under clocked with SetCPU at various times but never messed with the voltages.
Nonetheless, thanks to OP for this little tidbit, I'll remember it if I ever start experiencing problems.
ddavv said:
Was so thrilled to see this recommendation, as I observed that my phone is really struggling to memory, and then kswapd0 kicks in. Tried to change it to 48MB, then to 64MB. Did not see any improvements. It looks like all apps get pre-loaded into memory, and once free memory hits less than ~80MB, the phone becomes sluggish. Once I kill all apps, the phone is back to normal snappy lag-free operation. Free memory at that point is around 135MB. This is even worse when I insert the phone into car dock. Re-draw takes about 5-7 seconds, swiping is about 2-3 seconds. In few moments it becomes ok, but still laggy.
Click to expand...
Click to collapse
ddavv, sorry it didn't work for you. Some of the other things I've done to my Charge to help with the lag:
Changed io scheduler to bfq (from sio)
Tweaked my memory manager kill thresholds to 6,8,20,28,32,40 (WIP, YMMV!)
Removed some apps that kept heavy services in memory all the time, e.g. Accuweather & Lookout Security, and streaming media services I didn't use much (Last.fm, Slacker)
Turned off Google location services to stop the k3g_wq CPU runaway bug (this may be fixed in Google Maps > 6.4.0)
Switched to ADW.Launcher
Trimmed widgets I wasn't using frequently (down from 20 to 15)
I still do get a bit of lag after the phone has run for a while, so daily reboots are still a good idea for me - but I'm slowly improving my situation. I'm probably going to take a few hours to do a full wipe & reload once the FP1 ROMs start dropping, and be much more careful about indiscriminate app restoring from Titanium Backup this time. Good luck!
I wanted to undervolt my CPU a bit to hopefully get a better battery life. Especially now that I've gotten a tablet (Nexus 7, so nothing to sneeze at) I'm using my phone as a Android device a little less and most of my gaming on it allows for some very low CPU speeds anyway. So to that end, if I can squeeze a little more out of it, it seems like a good idea. I've already taken a LOT of other steps, including minimizing the number of things running all the time (it's actually a little annoying how often things stay running in the background that I just don't need, so Android Assistant is now one of my favorite tools, though I wish its "quick boost" widget and the automatic selections in the process list could stop more apps) and I've even removed a lot of the built in things that run all the time that I don't want like live wallpapers (I really don't understand why it likes to run even if you're not actually using a live wallpaper) and DSP Manager (I want the sound to be unmodifed anyway) among many others. I use SetCPU to set the CPU lower under normal operation with the conservative governor and to even set it extremely low when the screen is off with the powersave governor. WiFi and mobile data stay off when I'm at work and often even at home. Overall battery life is generally quite good, but sometimes it's still going down faster than it really should even just idle with the screen off. If I could just squeeze a little bit more out of it I'd be a lot happier. Plus it also can get fairly hot despite the underclocking on those occasions I do play a game thanks in no small part to the fact that I'm having to use an Otterbox on it (which means not one, not two, but THREE layers of insulation on the back side when Samsung pretty much designed it with one in mind. More heat escapes through the glass at the front than the rear and that's saying something given that glass is a pretty strong insulator... Otterbox truly needs to design these with some sort of thermally conductive material or something.) I don't know that undervolting would help a lot with either since I probably can't go down by much, but it most certainly can't hurt...
Ok, so I grabbed the KT747 kernel for the Verizon SGS3 from here (I got the AOSP Jellybean version, not Touchwiz) and tried to install it using the update function in ClockworkMod then cleared the cache partition and Dalvik cache both immediately after. The moment I hit reboot, the phone got stuck on a black screen or shut off (I couldn't exactly tell which.) I didn't find a convenient CM10 kernel alone, so had to basically just put the full CM10 update which of course was a bit inconvenient since I had to redo a lot of stuff. Is that the incorrect way to install it? So far everywhere I've looked everyone just skips over the part about the actual install process -- they just say to install it. Given that it's distributed as a ZIP complete with the normal stuff one would see in a recovery update ZIP I assumed that was the appropriate way (and it did say it was successful and all.) Well, I've read in that thread and others that sometimes it just doesn't work with some phones, so my assumption is that was the case here, but just in case if I've installed it wrong it would help to try doing it right, lol.
Is there any other kernel I should try with CM10? I don't need any special features (definitely no Voodoo sound or whatever -- again, I like the sound being unmodified anyway) beyond the normal stuff other than the ability to undervolt the CPU by a bit. I'd like to do the undervolting with SetCPU if I could as it overall suits me best of the tools I've tried and even has a "safe mode" ZIP file that can be installed as if it were an update in the recovery menu that would stop it from doing its thing if something goes wrong, thus making it safe even to use the set on boot option (though I suspect that with my current underclocking the CPU will remain stable until I push it at any reasonable undervolt level.) Or am I maybe even missing something and CM10 actually has the ability built in that I just haven't found anywhere? I see options to set the CPU min/max, governor and I/O, but nothing about things like voltage (or overclocking for that matter, where I assume such settings would probably lie.) From my understanding, the fact that SetCPU lacks even a tab for voltage control on here means that it thinks the kernel doesn't support it though.
EDIT: Oops, forgot to mention, but I did do "fix permissions" after clearing both types of cache. Also, the system is definitely on when it just goes black. When I press the power button I get the power LED on green indicating that the battery is nearly full and the hardware button backlights come on.
You're correct on assuming that since SetCPU doesn't have the tab the kernel doesn't support it. Try leankernel. It's what I always run. I don't have the URL handy but it's on rootzwiki. It has a TW and AOSP version so obviously make sure you grab the right one.
Ok, something's odd here. I tried the LeanKernel for Verizon (lk_aosp_jb_vzw-v1.9.zip from http://rootzwiki.com/topic/32286-kernel-aosp-jb-leankernel-minimalistic-kernel-v19-111012/ -- or, more accurately, from what I believe is his official page at http://imoseyon.host4droid.com/s3/#!/view=details/lang=en/sort=na) and again the same thing. Just a black screen. I can get the lights to come on behind the bottom hardware buttons, but it's not working right. It seems it DOES boot up enough to where I can connect with adb thank goodness (I had to pull the battery twice before I thought to see what would happen) and get a shell, so I tried running lkconfig and setting it to not undervolt by default (I don't really understand why so many kernels under/overvolt/clock by default when you can so easily mess with those things via software after it's actually up and running) but even after another reboot or two it still didn't work. Again, I cleared BOTH caches and ran fix permissions after installing the kernel from the zip file. Also, I'm trying TWRP now instead of ClockworkMod as it seems to be quite a lot better (touch interface in the free version, ability to choose WHAT to backup so I don't have to backup data every time -- which is really handy since I lack the free space to backup data and always have to wait for CWM to error out -- and a bunch of other nice little things) and I'm getting the same problem with it.
I even tried waiting a while in case it was doing the "Android is upgrading" thing where I guess it's basically just rebuilding the Dalvik cache, but the screen still wouldn't come on at any point after that even after another reboot. It's worth noting that the adb shell it gave me went straight to root (eg a # sign on the prompt) whereas under a normal bootup it should be at user level first requiring me to run su to get root. Am I just missing something or what?
Hi All,
I know Zombi-POP is still in RC1 so I'm sure there are still quite a few issues. The issue I seem to be having is the tablet is VERY slow once you use it from sleep/sitting for a while. I'm not sure what its doing once I start using it again but it takes about 3-5 minutes to get back to hauling butt. I notice when playing a game that there is performance hit every 2 seconds. I can see the animation lagging so its very noticable and constant. Does anyone know what could be going on?
TF700T:
* ROM2SD on 64GB Sandisk 10. I partitioned it 16/43/1 EXT4. I'm staying away from F2FS since data could corrupt.
* Recommended settings put in place based on install notes on forum.
Governor:Interactive (not like I can change it anyways)
IO scheduler:noop
Thanks for the help. I would post this in the correct area but I'm not allowed to post there yet due to my newbie status .
That sounds as if you have automatic updates in the Play Store active. Turn it off.
And get rid of the FB app if you use it (acess it in browser instead). Any app that feels the need to phone home as soon as the tablet wakes up will make this lag-on-wake worse: weather apps, forum apps, mail... what have you.
For your game you could try to play with the Transition animation and Animator duration scale in Developer Options. Set them to .5 and see if that helps.
You should really give f2fs on internal a whirl. As long as we have been playing with f2fs I still have to hear from a single user who had data loss issues because of it. And anyway - if you keep sensitive data on your portable device you should have a solid backup routine in place no matter what. And if you do data loss is a non-issue
mediaserver is the issue...
I was watching the system for a while during wakeups and found that the mediaserver process is causing this slowdown. I guess its scanning the driver? I'm not sure. All I know is there is a app already created out there that kills the mediaserver process for good. I tried killing it from the terminal but it starts up right afterwards. I'll stick with EXT4 for now. The performance is great for me once that process is gone and I'm more familiar with EXT4.
Thanks!
Andy
berndblb said:
That sounds as if you have automatic updates in the Play Store active. Turn it off.
And get rid of the FB app if you use it (acess it in browser instead). Any app that feels the need to phone home as soon as the tablet wakes up will make this lag-on-wake worse: weather apps, forum apps, mail... what have you.
For your game you could try to play with the Transition animation and Animator duration scale in Developer Options. Set them to .5 and see if that helps.
You should really give f2fs on internal a whirl. As long as we have been playing with f2fs I still have to hear from a single user who had data loss issues because of it. And anyway - if you keep sensitive data on your portable device you should have a solid backup routine in place no matter what. And if you do data loss is a non-issue
Click to expand...
Click to collapse
You should really switch to internal and F2FS - there is no risk of corruption. Rom2sd doesn't play well with zombi.
Hey all, I've had my G7 Power for about 2 years and in the last year or so I have been super frustrated with the handling of background processes, etc.
It can hardly hold a background process. The two worst offenders for me are:
It will kill my music app almost instantly after pausing. This is exceedingly frustrating when an app mutes all other audio and it instantly kills my music.
It will kill my browser when I go to search for a file to upload (for example if I go to upload a PDF to a website I can't because the website has to reload when I come back from finding the file).
In an attempt to solve this I moved from stock to LOS 18.1 and rooted. This was perhaps marginally better, but still overall terrible.
The other day I used this Magisk module to enable the low_ram flag, as well as disabled the Google app (which despite always always hogging RAM also loved to close in the background), which actually kinda solved my problem. It is still not perfect, and I had to find a new weather app, but it's acceptable. HOWEVER, I learned that I cannot use messages for web with this flag on (really Google????), which is kind of a dealbreaker for me.
I happily used stock ROMs on my phones for the last few years and would rather not spend my time making my phone with 3GB of RAM work worse than my older phones that ran MM on 1GB just fine. Any suggestions? Should I go back to Android 9 and never update? I can't even remember if it was better but it seems like it might be.