Related
I was on CM7 then went to AOKP, didnt like it and went back to CM7, now my phone is super laggy.
I have found out it is running at 200mhz almost constantly unless i set my minimum to 800 or 1200, but then my battery would die in minutes.
Nothing seems to fix this. it is SOOO bad that the skateboard cm7 droid dude, lags. the first samsung logo takes like 30 seconds or more, then when it jumps to the skateboard guy it lags and the circle arrow skips frames horribly. not like usual.
The only thing i can think of is when i was on AOKP (ICS) i "v6 super charged it" when i went back could there be remnance of issues?
please help i am pulling my hair out in stress and annoyance.
I have reflashed 5 times, reset with heimdall to stock, then back to CWM recovery RED, (entropy) and back to CM7... no fix. im wondering if a certain file is causing the cpu to underclock.
what file do i delete and reset.
please help
Go back to stock...and then once on stock go to settings>privacy>reset to factory defaults>format USB drive....let it do its thing and you should be good...make sure you back up important data first...this will wipe everything!!!!
Sent from my HTC PH39100 using XDA
is this honestly my only option? seems a bit harsh to wipe everything
Skwerl23 said:
is this honestly my only option? seems a bit harsh to wipe everything
Click to expand...
Click to collapse
Yes...remember you dealing with files...folders...that sometimes leave a trail of stuff....so a good wipe and kill all, reload clears...so being lazy will have it's effect....
My thing if ya gonna do it..do it right, work now, rest/enjoy it later......
all i should have to back up is my titanium, and my pictures i believe.
im not against doing it right, problem is i have reflashed probably 50 times, and this is the first time ive had an issue. its weird.
so when i reset to stock, it boots normal speed. im not so sure its the folders. this is so weird. but im trying this step anyhow
Skwerl23 said:
all i should have to back up is my titanium, and my pictures i believe.
Click to expand...
Click to collapse
Pics should be on your ext sd card...and yes you can back up via tibu your apps only...
usb wiped from stock. no change. am i missing a certain kernel?
fixing permissions helps some what for one boot then back to where it was.
tried going back a month to may 1st of CM7 release. no go.
my wifes infuse is just like mine and works fine. difference is i was on ICS im gonna flash that and see how ICS works.
ive been working on this for around 14 hours, this is insane.
everything i do is no good.
i honestly think supercharger messed it up, but i dont know how. either that or my CPU is some how fried, but it works fine from time to time, and when i set it to 1200 mhz minimum speed
its as if my governor's are jacked up, but it is slow in boot up and recovery as well. which is what really confuses me
just installed ics AOKP Brocolli, and its as smooth as ics has been, i dont like the random crashes and problems i get from ICS so i want to go to CM7
plus this AOKP Broccoli theme is god awful to me.
i think im just to old to look at circuit board designs all day.
I'm having some issues with my S 4g. After leaving my phone alone, such as charging it over night. I'll wake up with it booted in to recovery, or as soon as I go to use it I'll get a lot of force closures. I've tried different ROMS I've tried wipping every thing that can be wiped and doing clean installs and it still happens.
At first I thought it was from my alarm app, so I stopped using it. That didn't help. Thought it might be deep idle, so I stopped using that, still happens. Does anyone have an idea what could be causing this? It's making my phone quite un-usable. I'm current on CM9 nightlies, this first started when I went to the CM9 RC1.
You need to provide more info.
Kernel, clock speeds, voltages etc.
If all else fails, you can always use ODIN to flash factory images of ICS and root from there.
063_XOBX said:
You need to provide more info.
Kernel, clock speeds, voltages etc.
Click to expand...
Click to collapse
I'm still using the kernel that came with CM9. I hadn't flashed a new one on to it. So those would be the stock clock speeds and voltages.
It's really weird, as long as I'm using my phone it's fine, but if I leave it alone for a while it misbehaves.... kinda like my kid.
Delete..........
I tried going back to completely stock, re-rooted my phone and doing a fresh install of cm9. Didn't help anything. Switched to a different Rom and no issues so far
Sent from my Nexus S 4G using Tapatalk 2
After a search, I know other people have had this issue with the MT4GS. I'm currently running Virtuous Inquisition 4.02. I'm pretty sure i've flashed any updates. Also, I don't remember having this issue on any other ROM that I have ran in the past (virtuous unity, CM 7). The issue is the soft keyboard not responding randomly to certain keys. The weirder thing is if i use a different finger, it usually responds, but if i keep using the same finger, it won't. Is this my digitizer going bad, or just a soft keyboard thing? I haven't experienced the issue in any other part of android, just when using the soft keyboard. is there a touchscreen driver to flash or anything i can do to fix this? thank you!
At least someone else has my same problem
anitgandhi said:
After a search, I know other people have had this issue with the MT4GS. I'm currently running Virtuous Inquisition 4.02. I'm pretty sure i've flashed any updates. Also, I don't remember having this issue on any other ROM that I have ran in the past (virtuous unity, CM 7). The issue is the soft keyboard not responding randomly to certain keys. The weirder thing is if i use a different finger, it usually responds, but if i keep using the same finger, it won't. Is this my digitizer going bad, or just a soft keyboard thing? I haven't experienced the issue in any other part of android, just when using the soft keyboard. is there a touchscreen driver to flash or anything i can do to fix this? thank you!
Click to expand...
Click to collapse
It isn't anything related to the digitizer aparently. I say this because it never gave me a problem using stock rom. This usually happens when the phone gets too hot (you can feel this on the touchscreen). It starts lagging from what i could see, i mean my touches are not recognized properly.
If anyone has a screen calibration .zip laying around i would highly appreciate you to share it
ahh ok thanks for the info. after flashing cm 9.1.0 i can definitely tell the phone isn't getting as hot (according to spare parts, on inquisition the battery would go upwards of 35 celsius regularly, with cm it hasn't gone above 25), and the issue isn't happening anymore. thanks for the help!
rafaelrfq said:
It isn't anything related to the digitizer aparently. I say this because it never gave me a problem using stock rom. This usually happens when the phone gets too hot (you can feel this on the touchscreen). It starts lagging from what i could see, i mean my touches are not recognized properly.
If anyone has a screen calibration .zip laying around i would highly appreciate you to share it
Click to expand...
Click to collapse
You won't believe it but I do have something. This will help to increase sensitivity but for the life of me I can't remember where I got it.
anitgandhi said:
ahh ok thanks for the info. after flashing cm 9.1.0 i can definitely tell the phone isn't getting as hot (according to spare parts, on inquisition the battery would go upwards of 35 celsius regularly, with cm it hasn't gone above 25), and the issue isn't happening anymore. thanks for the help!
Click to expand...
Click to collapse
That's something I just can't understand...when people have troubles with Virtual Inquisition, that is. My wife runs it ALWAYS and I will jump back to it at least once a month for a while myself. It's always been one of the most stable, coolest running and longest battery life ROMs in my nandroids of my favorites. ANYway....give that flashable a try & see if it helps. The best I remember, you can reflash it until you achieve the sensitivity you're looking for. Good Luck!
WeekendsR2Short said:
That's something I just can't understand...when people have troubles with Virtual Inquisition, that is. My wife runs it ALWAYS and I will jump back to it at least once a month for a while myself. It's always been one of the most stable, coolest running and longest battery life ROMs in my nandroids of my favorites. ANYway....give that flashable a try & see if it helps. The best I remember, you can reflash it until you achieve the sensitivity you're looking for. Good Luck!
Click to expand...
Click to collapse
inquisition definitely was very stable and had great battery life, there is little doubt about that. i'm guessing i just didn't flash it correctly, and that caused some really high temps. other than that, i had no issues with it...for example, though, when i was running inquisition, if i left the phone in my pocket and forgot about it until say someone texted me/called me/i got a notification, and i checked the temps, it was at 30-35 celsius, and felt burning. again, i'm guessing i didn't flash it right.
also, thanks for the touchscreen fixer zip, if i have the issue again, i will flash it. fingers crossed i don't need it.
side questions about kernel flashing: 1) do i wipe cache and dalvik cache then flash the kernel zip? 2) is there a way to go back to the original kernel without having to flash the rom all over again?
thanks!
anitgandhi said:
inquisition definitely was very stable and had great battery life, there is little doubt about that. i'm guessing i just didn't flash it correctly, and that caused some really high temps. other than that, i had no issues with it...for example, though, when i was running inquisition, if i left the phone in my pocket and forgot about it until say someone texted me/called me/i got a notification, and i checked the temps, it was at 30-35 celsius, and felt burning. again, i'm guessing i didn't flash it right.
also, thanks for the touchscreen fixer zip, if i have the issue again, i will flash it. fingers crossed i don't need it.
side questions about kernel flashing: 1) do i wipe cache and dalvik cache then flash the kernel zip? 2) is there a way to go back to the original kernel without having to flash the rom all over again?
thanks!
Click to expand...
Click to collapse
Wipe user data/cache .....cache....dalvik....battery stats. All of them 3 times. (CWM has some small issues getting everything on the first shot) Then you flash your Rom. Let it set a minute or two. Lastly....Flash your Boot.img. Be sure not to just let windows just show what's in the .zip file and copy it out but highlightit and open it with Winzip (or whatever you use). EXTRACT it to where you flash your files from. If you don't do it like that it will remain partially compressed and you'll forfet the parts of your kernel that are. Once flashed, let it rest for 5 minutes and you should be good to go.
If flashing another ROM ALWAYS follow those rules but if reflashing with another kernel you can forgo clearing user data so you will keep your apps & their placement in your ROM. Just clear everything else reflash your ROM again & then your kernel. It will look just like it did but with the new kernel. If by chance you then have an issue with force closes just go back to recovery & fix permissions & it should straighten that right out.
BTW....If you are unlocked & S-On you will not be able to flash it from recovery in any form or fashion. You will always need to extract the boot.img file and "ADB fastboot flast boot boot.img" from your command window.
WeekendsR2Short said:
Wipe user data/cache .....cache....dalvik....battery stats. All of them 3 times. (CWM has some small issues getting everything on the first shot) Then you flash your Rom. Let it set a minute or two. Lastly....Flash your Boot.img. Be sure not to just let windows just show what's in the .zip file and copy it out but highlightit and open it with Winzip (or whatever you use). EXTRACT it to where you flash your files from. If you don't do it like that it will remain partially compressed and you'll forfet the parts of your kernel that are. Once flashed, let it rest for 5 minutes and you should be good to go.
If flashing another ROM ALWAYS follow those rules but if reflashing with another kernel you can forgo clearing user data so you will keep your apps & their placement in your ROM. Just clear everything else reflash your ROM again & then your kernel. It will look just like it did but with the new kernel. If by chance you then have an issue with force closes just go back to recovery & fix permissions & it should straighten that right out.
BTW....If you are unlocked & S-On you will not be able to flash it from recovery in any form or fashion. You will always need to extract the boot.img file and "ADB fastboot flast boot boot.img" from your command window.
Click to expand...
Click to collapse
i'm s-off so i don't need to worry about the boot.img extraction and all that, but the rest was very helpful, thank you very much!
:good:
anitgandhi said:
it was at 30-35 celsius, and felt burning.
Click to expand...
Click to collapse
Whenever anyone mentions overheating issues with the device - the first questions should always be:
Are you on a stock battery?
If so, then that is your problem.
I've forgotten to manage setcpu and left it running at 1.7 more often then anything, yet very rarely run into overheating issues...unless I go back to a stock battery (even without overclocking)
Blue6IX said:
Whenever anyone mentions overheating issues with the device - the first questions should always be:
Are you on a stock battery?
If so, then that is your problem.
I've forgotten to manage setcpu and left it running at 1.7 more often then anything, yet very rarely run into overheating issues...unless I go back to a stock battery (even without overclocking)
Click to expand...
Click to collapse
i am on stock battery. good to know that it usually causes overheating...glad it's not happening with cm 9.1.0 though
WeekendsR2Short said:
You won't believe it but I do have something. This will help to increase sensitivity but for the life of me I can't remember where I got it.
Click to expand...
Click to collapse
the issue came back (although not as frequently) so i went to flash the zip that you attached... it says it's something relating to beats audio and then it errors out and the installation aborts. i looked at the files inside all have "beats" and "audio" in the filenames...
I am rooted and unlocked. After numerous rom flashes (always fully wiped, never flashed dirty) I started experiencing pretty substantial lag in my daily use. This wasn't choppy lag, but more slow response to touch and general movement, with painfully slow typing. My first reaction was to flash back to stock using Odin. I did this, re-rooted, unlocked, and flashed synergy 1.4. I had previously run this rom for quite some time without an issue. I set my phone up, clean installing all apps. After a day or two my snappy phone became slow again. I wiped (system, cache, dalvik) and flashed bean's build 9. Again the phone started snappy, then after a day or two went slow. I next tried several custom kernels. I overclocked them using setcpu. Initially this fixed the slowdown, but only temporarily. At this point I assumed it was a rouge app. I clean installed my rom, and ran it with only the stock apps. After a day of use its running slow again. If anyone has any idea what steps I might take to solve this, I would greatly appreciate the help. I know the phone is fully capable of running lag free, as I had no issues for weeks prior to this. I almost feel like there are files not being fully purged when I flash stock via odin. I don't know if this is possible, and could really use the expertise of someone more knowledgeable than me.
OneNutShort said:
I am rooted and unlocked. After numerous rom flashes (always fully wiped, never flashed dirty) I started experiencing pretty substantial lag in my daily use. This wasn't choppy lag, but more slow response to touch and general movement, with painfully slow typing. My first reaction was to flash back to stock using Odin. I did this, re-rooted, unlocked, and flashed synergy 1.4. I had previously run this rom for quite some time without an issue. I set my phone up, clean installing all apps. After a day or two my snappy phone became slow again. I wiped (system, cache, dalvik) and flashed bean's build 9. Again the phone started snappy, then after a day or two went slow. I next tried several custom kernels. I overclocked them using setcpu. Initially this fixed the slowdown, but only temporarily. At this point I assumed it was a rouge app. I clean installed my rom, and ran it with only the stock apps. After a day of use its running slow again. If anyone has any idea what steps I might take to solve this, I would greatly appreciate the help. I know the phone is fully capable of running lag free, as I had no issues for weeks prior to this. I almost feel like there are files not being fully purged when I flash stock via odin. I don't know if this is possible, and could really use the expertise of someone more knowledgeable than me.
Click to expand...
Click to collapse
Maybe u got a defected unit
Sent from my EVO using xda premium
luigi311 said:
Maybe u got a defected unit
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Although that's certainly possible, it did work well for weeks, and the lag seemed to come about as a result of my tinkering.
Hi all,
I've been struggling for the past few months with terrible performance issues on my Droid Charge. Things like redrawing the home screen and lag between switching programs I can live with, but when it takes several minutes to pull up the dialer to make a phone call or to answer a text message, my phone kind of stops being useful as a phone.
I started off on stock when I got the phone last year, then I rooted it a few months later. Everything was great until June. Gradually, my phone had become less responsive (taking forever to make calls, view and send texts). That plus something weird was eating >2GB data/month, and I could only identify it as "Android OS/others" via Onavo. I decided to go clean and try Tweaked 2.2w/PBJ. Things were pretty good for a couple of weeks until the major lag started coming back. I stepped back and uninstalled many apps, hoping to find one that was the main culprit, but my phone continues to act like it's trying to calculate a billion values of pi or something.
I tried following the steps from the rootzwiki "5 Steps to Keep Your Phone Snappy/Lagfree" (not allowed to link yet ), which helped somewhat, but it has not eliminated the problem. I often find myself resetting my phone to make phone calls. SwiftKey often doesn't load correctly and requires me to enter and exit applications frequently to get it to allow me to type. I had to wait nearly 2 minutes to get my home screen to display until I removed Holo Launcher and went back to TouchWiz.
Sorry for the essay--I'd be happy to provide additional details if needed. What can I do to a) figure out what's wrong with my phone and b) fix it?
Thanks in advance!
petrivka said:
Hi all,
I've been struggling for the past few months with terrible performance issues on my Droid Charge. Things like redrawing the home screen and lag between switching programs I can live with, but when it takes several minutes to pull up the dialer to make a phone call or to answer a text message, my phone kind of stops being useful as a phone.
I started off on stock when I got the phone last year, then I rooted it a few months later. Everything was great until June. Gradually, my phone had become less responsive (taking forever to make calls, view and send texts). That plus something weird was eating >2GB data/month, and I could only identify it as "Android OS/others" via Onavo. I decided to go clean and try Tweaked 2.2w/PBJ. Things were pretty good for a couple of weeks until the major lag started coming back. I stepped back and uninstalled many apps, hoping to find one that was the main culprit, but my phone continues to act like it's trying to calculate a billion values of pi or something.
I tried following the steps from the rootzwiki "5 Steps to Keep Your Phone Snappy/Lagfree" (not allowed to link yet ), which helped somewhat, but it has not eliminated the problem. I often find myself resetting my phone to make phone calls. SwiftKey often doesn't load correctly and requires me to enter and exit applications frequently to get it to allow me to type. I had to wait nearly 2 minutes to get my home screen to display until I removed Holo Launcher and went back to TouchWiz.
Sorry for the essay--I'd be happy to provide additional details if needed. What can I do to a) figure out what's wrong with my phone and b) fix it?
Thanks in advance!
Click to expand...
Click to collapse
could any number of issues - ranging from a rogue app to the ROM not sticking correctly. when you installed Tweaked, did you do it via CWM or ODIN?
also, did you enable the build.prop tweaks to help with redraws and making calls?
otherwise, I would suggest to try wiping cache and dalvik (sometimes that cleans it up a bit as well rebooting the phone once every few days) to help clear out some of the clutter.
do you have any "force close" messages (such as SyncMLSvc)?
Thanks for the quick reply.
I installed Tweaked through ODIN. I haven't heard about the build.prop tweaks though. Is there a resource you can point me to or a quick process to enabling them? I thought that a lot of these tweaks were "cooked" into the Tweaked ROM.
I've got App Cache Cleaner dejunking me every 4 hours, and I try and hit the davlik every day...I still have issues.
I do have the SyncMLSvc force close on boot. I figured it was a known bug in Tweaked and that it'd be addressed in a later revision. Is it a symptom of something more ominous?
petrivka said:
Thanks for the quick reply.
I installed Tweaked through ODIN. I haven't heard about the build.prop tweaks though. Is there a resource you can point me to or a quick process to enabling them? I thought that a lot of these tweaks were "cooked" into the Tweaked ROM.
I've got App Cache Cleaner dejunking me every 4 hours, and I try and hit the davlik every day...I still have issues.
I do have the SyncMLSvc force close on boot. I figured it was a known bug in Tweaked and that it'd be addressed in a later revision. Is it a symptom of something more ominous?
Click to expand...
Click to collapse
i don't use App cache cleaner, and thus do not have any issues. also, if you have TiBu, you can uninstall that syncmlsvc. see if that does the trick.
regarding the build.prop tweak, remove the # from ro.home_app_adj=1
here is a link to some others: http://www.s3forums.com/forum/galaxy-s3-hacking-mods/474-list-some-build-prop-tweaks.html
Do you have facebook installed? That P.O.S. kills my phone everytime. I install it from time to time just to see if they are coming close to fixing it. Needless to say it gets uninstalled in under 10 minutes.
I know everybody will jump all over me on this but why not try stock rooted FP5 for a couple of days. It will give you a baseline to compare other roms and app impact with. If your phone still acts up it would seem to be pointing to a hardware error IMHO.
What can it hurt?
Still Charged Up
Reilly1812 said:
Do you have facebook installed? That P.O.S. kills my phone everytime. I install it from time to time just to see if they are coming close to fixing it. Needless to say it gets uninstalled in under 10 minutes.
I know everybody will jump all over me on this but why not try stock rooted FP5 for a couple of days. It will give you a baseline to compare other roms and app impact with. If your phone still acts up it would seem to be pointing to a hardware error IMHO.
What can it hurt?
Still Charged Up
Click to expand...
Click to collapse
Apparently Facebook is making their employees switch from ios to android so they finally so something about the app.
Sent from my SCH-I510 using Tapatalk 2
JihadSquad said:
Apparently Facebook is making their employees switch from ios to android so they finally so something about the app.
Sent from my SCH-I510 using Tapatalk 2
Click to expand...
Click to collapse
LOL! They're all too busy dumping their worthless stock to care.
Still Charged Up
Reilly1812 said:
LOL! They're all too busy dumping their worthless stock to care.
Still Charged Up
Click to expand...
Click to collapse
Abandon ship!
Sent from my SCH-I510 using xda premium
I started usin Fast for Facebook. U cant do as much, but its not a battery hog which i think is super important
Sent from my SCH-I510 using xda app-developers app
cnoevl21 said:
I started usin Fast for Facebook. U cant do as much, but its not a battery hog which i think is super important
Sent from my SCH-I510 using xda app-developers app
Click to expand...
Click to collapse
It probably doesn't make you believe your running Froyo again either : crawling and littered with FC's
Still Charged Up
Most importantly out of everything is to always check out your md5's and make sure they match. Also try going back to stock with the pit file too for a full fresh install. But I think the problem is the md5 sums unless you download apps off the internet
Edit: also remember to mount system when flashing roms
Reilly1812 said:
Do you have facebook installed? That P.O.S. kills my phone everytime. I install it from time to time just to see if they are coming close to fixing it. Needless to say it gets uninstalled in under 10 minutes.
I know everybody will jump all over me on this but why not try stock rooted FP5 for a couple of days. It will give you a baseline to compare other roms and app impact with. If your phone still acts up it would seem to be pointing to a hardware error IMHO.
What can it hurt?
Still Charged Up
Click to expand...
Click to collapse
So, an update: I thought it was SwiftKey that was killing my phone, because I was doing better after I removed it. It was crappified even then, even after removing Facebook. I bit the bullet yesterday and went back to stock, updated all the way to FP5. I kept Facebook off (I've mostly moved over to G+ anyways). Everything is great. I put SwiftKey back on, and everything is still great.
I hate to say it, but even though the loss of customization in Tweaked is disappointing, I'm more satisfied with the phone in general with the stock ROM. My battery even lasts more than 3 hours too.
If it ain't broke...
petrivka said:
So, an update: I thought it was SwiftKey that was killing my phone, because I was doing better after I removed it. It was crappified even then, even after removing Facebook. I bit the bullet yesterday and went back to stock, updated all the way to FP5. I kept Facebook off (I've mostly moved over to G+ anyways). Everything is great. I put SwiftKey back on, and everything is still great.
I hate to say it, but even though the loss of customization in Tweaked is disappointing, I'm more satisfied with the phone in general with the stock ROM. My battery even lasts more than 3 hours too.
If it ain't broke...
Click to expand...
Click to collapse
my phone usually has that affect after flashing a new ROM. basically it's the wiping of data and cache/dalvik that helps cleans out the problems.
jco23 said:
my phone usually has that affect after flashing a new ROM. basically it's the wiping of data and cache/dalvik that helps cleans out the problems.
Click to expand...
Click to collapse
Maybe...but I've been wiping the cache/davlik fairly often. I had uninstalled most my apps...maybe some weird bug was still manifesting itself. I don't think my phone has been this responsive even after first going to Tweaked. :-/
petrivka said:
Maybe...but I've been wiping the cache/davlik fairly often. I had uninstalled most my apps...maybe some weird bug was still manifesting itself. I don't think my phone has been this responsive even after first going to Tweaked. :-/
Click to expand...
Click to collapse
Well as long as your happy that's all that really matters. To be fair - there is nothing in Tweaked that should degrade performance at all compared to what is normally seen in stock. The one difference I could see is that Tweaked is deodexed - and many swear the odexed approach is faster/snappier/whatever-adjective-you-want-to-say-that-means-better than the deodexed one. Hopefully things stay functioning well.
dwitherell said:
Well as long as your happy that's all that really matters. To be fair - there is nothing in Tweaked that should degrade performance at all compared to what is normally seen in stock. The one difference I could see is that Tweaked is deodexed - and many swear the odexed approach is faster/snappier/whatever-adjective-you-want-to-say-that-means-better than the deodexed one. Hopefully things stay functioning well.
Click to expand...
Click to collapse
I hear ya. I figure I'll give stock a go for a while, at least until Tweaked comes out of beta. I'm still counting down the days until I can upgrade to something with ICS. Or maybe even a Lumia 920...
petrivka said:
...at least until Tweaked comes out of beta...
Click to expand...
Click to collapse
It's out of beta - check it out here if interested
I tried forever to get PBJ to play nice. RFS & ext4. Gemini App Manager autostart tweaks. MinFree tweaks. All the TweakTool init.d tweaks. The SQL index tweaks. overclocking. Autokiller, other memory apps, JuiceDefender, other build.prop tweaks, etc. I tried it all...
I'm not sure if it was my hardware version or what, but I just could not get it to work well. It always seemed like it ran out of memory and couldn't automatically manage the apps in an overloaded situation. If i manually ran some of the SQL scripts, and killed running apps, it would be ok, but not for long. I had problems losing text messages because I think the text message handler got killed or didn't run in time. I've tried GoSMS and the stock SMS. I ended up relying on Ghostly SMS to help catch the texts I lost.
Once I went back to stock FP1, most of my problems went away. It's been much more stable. So, since then, it's been stock kernel (obviously on RFS). I've been on FP5 with various versions of Tweaked 3 beta/RC and now I'm no the final. All good.
So, as much promise PBJ has or had (who knows what the FP1/FP5 hybrid will turn out like), stock kernel with Tweak 3 is the way to go for me!
CalPolyRock said:
I tried forever to get PBJ to play nice. RFS & ext4. Gemini App Manager autostart tweaks. MinFree tweaks. All the TweakTool init.d tweaks. The SQL index tweaks. overclocking. Autokiller, other memory apps, JuiceDefender, other build.prop tweaks, etc. I tried it all...
I'm not sure if it was my hardware version or what, but I just could not get it to work well. It always seemed like it ran out of memory and couldn't automatically manage the apps in an overloaded situation. If i manually ran some of the SQL scripts, and killed running apps, it would be ok, but not for long. I had problems losing text messages because I think the text message handler got killed or didn't run in time. I've tried GoSMS and the stock SMS. I ended up relying on Ghostly SMS to help catch the texts I lost.
Once I went back to stock FP1, most of my problems went away. It's been much more stable. So, since then, it's been stock kernel (obviously on RFS). I've been on FP5 with various versions of Tweaked 3 beta/RC and now I'm no the final. All good.
So, as much promise PBJ has or had (who knows what the FP1/FP5 hybrid will turn out like), stock kernel with Tweak 3 is the way to go for me!
Click to expand...
Click to collapse
You're 100% correct!!
Please correct me if I'm wrong because I really want to know. The way I see it is, the real improvements over FP1 came from what Samsung did with FP5. Then what Dwitherell did was remove the useless bloat and ugliness then add the useful features and beautify it without changing anything that would hurt the performance.
The first time I upgraded to FP5 stock I noticed the speed increase right off. I checked it out a little and was amazed. But of course it had all of Verizon's bloat garbage in it and none of the awesome tweaks from Dwith. And it had no user installed apps in it at all. It has always seemed like the more apps I install the slower the phone gets.
So am I right?