Hello to everyone;
To start with I suppose I must introduce myself:
My name is Manu from México and I am a proud owner of a Samsung Galaxy Ace since three months ago.
During this time I had played with it and its stock ROM with 2.3.4 from carrier Telcel, I rooted it and removed bloatware from the carrier, the result was really nice; even thou after some apps the internal space run out, and therefore the responsiveness of my phone also got cluttered.
About a week ago or so I decided to go beyond and flashed "CyanogenMod 7.1-cooper-KANG-RC1 Android 2.3.7" so I tested it for a while and even thou I found many improvements, many bugs were unbearable for the phone use I’m used to; so I switched back to a Stock Rom and flashed "S5830SERKPO" with 2.3.5. and my regional modem.
In addition I did this process to Deodex + root "http://forum.xda-developers.com/showthread.php?t=1118048&highlight=DEODEX” the result in my personal opinion is very good, but I’m back to the beginning. IM RUNNING OUT OF SPACE FOR INTERNAL STORAGE AND THE PHONE STARTS TO ACT LAGGY
I have read about s2e, link2sd and darktremor a2sd; where is require to partition your SD (which I already have also done with CMW at no avail) and I have finally ended up with a program called Install Manager 3.5.1 which promises to do move apps to SD (as far as they are executed locally from an .apk file and not market)
So... after this entire intro, and to avoid any flaming against me: I have read many many posts and have ended up overwhelmed and more confused.
¿Can someone please help me into the best way (in terms of stability and performance) to manage my apps to the SD card with a stock ROM?
(If possible a detailed explanation please, remember I have Stock "S5830SERKPO" with 2.3.5. and my regional modem)
Thanks a lot.
Also let me say I had read this post:
http://forum.xda-developers.com/showthread.php?t=1172684
But I get lost into "make sure the rom supports it" and therefore not sure if this applies to S5830SERKPO 2.3.5
Well, seems that my post is getting to much attention yet... still, I have an update; today during the course of the day, two times the phone screen turns off and it does not come back until I remove the battery.
The phone continues to work... (the radio still plays, calls continue, etc) just the screen turns off without any means to turn it on.
Hope someone can guide into how to find a better solution for my need.
Probably the easiest way to fix that is to install a ROM from the dev section (make sure it supports A2SD) Cyanogenmod is not official for our Ace, wich means lots of bugs, but other Customs Roms should be ok for you.
Create a ext4 and swap with CWM in your sd card (reboot into recovery, advanced, create sd partitions) Open the A2SD app and turn the swap on, move applications.
Just a noob sharing some thoughts, hope it can help some other noobs like me.
A no wipe in my book:
Here is how i do a no wipe.
In recovery, mount and storage and choose format system.
Go back and wipe Cache and Dalvik
Install / flash the rom.
A full wipe in my book:
Into recovery, mount and storage and format system, data and cache.
Go back, wipe/ reset data, cache and dalvik.
Install/flash rom
Format of the internal SD:
Here is what i do:
Make a app backup with TB to my external sd
Make a nandroid to my external sd
Make sure i also have a efs backup on my external sd
I only save mods, roms on my internal sd in my download map and this map i move to my external sd.
Then i reboot to recovery.
Mount and storage and format internal sd.
And to be save and have it nice a clean, also format system, data and cache and because i am not only a flashohalic but also a cleanohalic, i then wipe/reset factory reset, cache and dalvik.
Probably a big overkill, but he, done it several times it works for my and it only cause a few seconds.
Then i reboot, skip the setup/registration, move my download map back to my internal sd (don't like flashing from external sd).
Back in cwm, again a full wipe which includes the formats data, system and cache.
Then flash the rom and setting it up.
This way, you have a nice clean fresh S3, but and this is a big BUT.
Backup, backup backup and don't forget a efs backup to your external sd and pc.
Don't think lightly about those backups, when imei is broken and you don't have a backup, your a done, only thing left is a visit to Samsung.
Good luck when you are going for it.
And i know, Aroma installer is also doing some automatic wiping, but i am just a bit old fashion and like to do some stuff manually.
Bootloader.
As you all know, the new bootloader can be a pain in the ass.
But, i am still not sure that Samsung only released the new bootloader just to discourages us to flash custom stuff.
So, if you like flashing stuff and you are on the new bootloader like me, just remember when you entered recovery and you are done flashing stuff, use Triangle Away from Chainfire,
But, for some, like on my wifes phone, the latest version works without problem, but on my S3, i need to use the older version, 2.37, why, don't have a glue.
Not all S3 are the same, although have the same name and using the same chipsets.
But you can also use the old bootloaders, with does, you just have to run Triangle Away just once, when entering recovery, it will not count.
Your own choose.
About Sudden Death.
A lot of threads are open for this.
My 5 cents:
I have the "sudden Death" chips VTU00M chip with 0xf1 on both our phones.
Mine is running since 27 may 2012 without problems, still fast and smooth.
The other is up and running since 31 Augustus 2012 and also still fast and smooth.
Both have been rooted from day one, the only thing i do, is turning the devices off completely for a few minutes 4 to 5 times a week.
Old habit to clear memory, anyway, gives me time to do a good cleaning of my screen.
Here is the code to check your revision and to see from which day you are running your S3 *#12580*369#
Further more, AndreiLux found i string in the ELLA kernels released by Samsung that looks like that it solves the sudden death issue.
So, if indeed if fixes this issue, then off course the latest kernels releases from Sammy has also the fix and not just the custom kernels.
As far as i know, all the custom kernels has the fixes integrated this string by now, but i myself like the stock kernels, Indie puts in the Omega Roms.
Phil3759 has also made a repack of recovery based on CWM touch 6.0.2.7 to get it all safe.
More to come in the future, because i am learning everyday here on XDA and like to share and help others.
Edit, here is quote from AndreiLux about the new bootloader:
http://forum.xda-developers.com/showpost.php?p=37163086&postcount=1298
Do I need any particular Bootloader? No - There is no evidence to suggest this fixes anything
Apparently that's wrong, download mode on the device uses a microkernel from inside the bootloader instead of the full blown Linux kernel. When flashing something via Odin in download mode you'd be using the bootloader's MMC driver and thus be at risk.
All-day users are still safe via recovery and live kernel, but are not advised to flash things in download mode with an older bootloader. This also explains why they updated the bootloader in LLA. The security checks are a mere update to bring it up with what the 9305 and Note 2 users already have in terms of not able to get rid of the exclamation mark.
Personal note:
Maybe i am seeing this wrong, to much thinking in terms of home computers, but here is some thoughts regarding above.
From cold, turned off device,.
Turning the device on, micro kernel inside the bootloader kicks in to send information how to start the device correctly.
If it works this way and you are on the old bootloader, then every time you start the device with the old bootloader, you are at risk?
Some useful links:
My struggle with TA
Omega roms S3
Chris_84 Faq
Triangle Away
http://www.chainfire.eu/articles/118/Triangle_Away_vs_Samsung/
Old bootloader
Philz recovery
https://www.google.nl/search?q=andr...s=org.mozilla:en-US:official&client=firefox-a
https://play.google.com/store/apps/details?id=com.electricsheep.asi&hl=nl
https://play.google.com/store/apps/...sIm5ldC52aW5hZ3JlLmFuZHJvaWQuZW1tY19jaGVjayJd
Here i will post stuff that comes along the road like question about batterystats at recovery.
We used to have a option to wipe the battery stats at recovery, also there are some tools at Play store that claims to give a better battery life by just wiping those stats.
But after reading this excellent article, it comes clear that wiping those stats are bull.
So i am glad that option isn't available anymore and perhaps in time, the questions about those stats will faint away in oblivion
And another one i like to share.
Fast Dormancy.
Here is a great article about it, made by Erica.
For me, my provider is saying it's not supporting FD, but when use the method to check, it is supported.
So i tested it for a few days on and off and found that when it's off, i do get some better battery life, but it's just minor.
Instead of losing 5% battery at 8 hours standby, i lost 6%.
Also, i didn't see any benefits in speeds, so i turn it off every time after a flash of a new rom using gokhanmoral tool.
Another thing i like to add.
Wifi.
I have seen many posts about wifi problems.
Here what always works for me.
Sometimes just a reboot of the router will help.
Also, i find changing from dynamic (default) to static that my connection is faster connecting to my router (always use the never setting at wifi advanced to save battery).
Here is how to do it the easy way.
First set it up using it with the default dynamic settings, this way all will be filled in for you.
To change it to static.
Long press your connection and choose modify network config and check show advanced options.
Scroll down a bit and tap on IP settings and choose Static.
And that is all, now you have changed it to static and there is no more need for ip adress to negotiation any more.
https://www.google.nl/search?q=wifi...s=org.mozilla:en-US:official&client=firefox-a
Also if still having problems, adding some more permissions can solve it.
I use root explorer for this
ETC > Long press wifi folder and choose permissions (remember to change Mount R/W to Mount R/O) and check all nine boxes.
Hit back and go to Data > Misc and again long press wifi folder and again, check all nine boxes.
Space
I know, i am a control freak and i hate it when i see space just vanish.
So did some search and found a thumbnail map with more then 1gb size.
Looked at some submaps and i only saw some old stuff.
So, selected all the submaps and just deleted it without problems and gain more then a gb free space.
Here is where you can find it using root explorer:
storage > sdcard0 > .thumbnails.
Edit:
As bigmo7 pointed out, the thumbnails will be rebuild, but off course not off stuff that isn't present on the S3 anymore.
So, if you are someone that is just making pictures or making / creating movies and never delete then from your S3, there is no point off deleting the thumbnails.
But if you like me, moving, creating copying and deleting this kind off stuff, then you can gain space.
Battery life
Always a hot item.
First all, the S3 is a mini computer and computers need juice, just remember this.
Here are some stuff i always do after flashing a new rom.
If the rom comes with a aroma installer which let you select stuff to install or not install, look careful to the list.
Stuff you don't use, can just eat resources and i myself, just find it a waste.
Next, after flashing and setting up the new rom, you will be presented with the option to use wifi.
I always go to advanced when making a wifi connection to choose Never when phone is in standby.
For me, but this can be different for you, wifi is a bit off a drainer so do some testing, let it run overnight with Always selected and another night with Never and see the difference.
Next you will be present if you want to restore and let google backup your phone.
I always deselect backup my phone, first reason, i am a control freak and i decide when and what i want to backup.
And second it can give you wakelocks and this will cost you battery life.
Next step i do is going into settings and to sounds, i don't like the clicking sounds and i deselect all the system sounds.
Next, location services and deselect GPS and Location and Google search.
I want GPS active only when i need it, some apps like Facebook will activate GPS when running and i don't like this.
And i don't want Google to know where i am all the time.
Some weather apps needs Location and Google search to determine your location, but i use Weather pro and it don't need it.
Next step is going into accounts and look what you have selected for syncing.
I always deselect Google photos, Internet and Picasa web albums.
Stuff i don't need .
Location settings at accounts is also off.
Next step is using the Fast Dormancy toggle to disable Fast Dormancy, although my provider is supporting it, enabled costs me a little more juice. Although it's minor, but a lot off minors things makes it bigger .
Then starting Playstore and at settings, deselect Notifications.
And finally freeze stuff i don't use with Titanium Backup pro.
http://forum.xda-developers.com/showpost.php?p=31576747&postcount=105
All this, is giving me a great battery life, with screen on time between 4 1/2 to 6 1/2 hours, depends what i am doing.
And with the latest JB roms, 1 to 2% battery los in 7 hours standby.
No need for me to toggle Airplane mode, mobiledata or some other powersaving setting or app.
I am also always running the stock insecure kernel that comes with the rom, for me no need for a custom one.
Reserved
KeesStolk said:
I only save mods, roms on my internal sd in my download map and this map i move to my external sd.
Click to expand...
Click to collapse
Hello, when we flash a rom that already has mods ... do you know a way to save them ? (where to find them)
I mean. For example, my rom has a mod (and theme) on the toggles (pandoriam i9305). How can I save that mod ? Do you know a good tutorial to learn (safe) modding ?
thorcyar said:
Hello, when we flash a rom that already has mods ... do you know a way to save them ? (where to find them)
I mean. For example, my rom has a mod (and theme) on the toggles (pandoriam i9305). How can I save that mod ? Do you know a good tutorial to learn (safe) modding ?
Click to expand...
Click to collapse
I never save mods because most of the time when flashing a new rom, it's based on a new build and not every time mods are compatible, just like some themes by the way.
I just safe the mod files and thems, when i am sure they are compatible, i just flash them again.
Indie's Omega roms has already a lot of mods in it by default by the way, but i don't think he was for a 9305.
Good work Kees! Now I'm learning from you.
Chris_84 said:
Good work Kees! Now I'm learning from you.
Click to expand...
Click to collapse
Thank you for your kind words, but it is l who is learning from you every day .
Sent from my GT-I9300 using Tapatalk 2
and why dint i see this , brilliant my friend .... one of the best posts , well explained and really good stuff all at one place
thanks my friend
vegeta1 said:
and why dint i see this , brilliant my friend .... one of the best posts , well explained and really good stuff all at one place
thanks my friend
Click to expand...
Click to collapse
Thank you very much, but from you, Chris, Indie and the rest of the omega team are the ones I learn all this great stuff every day.
Sent from my GT-I9300 using Tapatalk 2
i always feel like a noob when ever i read here
big big thanks my friend for pointing out all this so nicely
Very nice posts KeesStolk. Maybe you should write a manual for us?
I'm about to post this in Q&A (searching for an answer brought me here )
I just (3 days ago) upgraded my Omega ROM to v40. All seemed fine - I did as normal but in v35, my last Omega there wasn't a Full Wipe option. I chose not to wipe and everything went as per usual with Omega. I reinstalled my extras (6 x 5 icons, Loud phone hack, Increasing ring phone, Note2 Keybd) and was back to normal.
Except, now my apps will not update.
I found out the hard way. I had a problem with Play Store - open it and it would flash briefly then close. Tried all I knew of but nothing worked so, logic said, Omega v40 is different enough I need a wipe and that why they put it in there as a choice this time. (I checked the Omega thread and couldn't see anything relevant but I was in the pub at the time and may not have been as thorough as I should have been)
I had a TB backup and Nandroid on my ExtSD from 2 days back and an EFS so I ran the install again and chose Full Wipe - again everything went well... until I tried to download TB so I could restore all my apps and data. Play Store opened and stayed Open (yaaaay!) and TB acts like it is downloading but nothing comes through - it just sits until it times out on an error.
I tried several apps and none would DL but then AuWeather DL'd just fine. I went back to TB - no go.
After much frustration I Restored my Nandroid and got back to where I was (Omega v35) but still I can't DL and update for TB. At least Play Store stays open though. I tried running the v40 update again, installing the Default, just in case, (& I have just finished DL'ing v41) but the DL/Update problem persists.
I'm now on:
AP – I9300XXEMA2
CP – I9300BUELK1
CSC – I9300LBEMA1
RF cal – 2012.6.28
HW Rev – MP 1.100
Any ideas? If I can't DL TB once I have flashed, I can't get my data back so a wipe isn't really an option until I fix the DL issues.
As I said, this will also be in Q&A but you seem to have a good grasp on the basics so I thought maybe...? :fingers-crossed:
So... I tried restoring back to v35 and got the same problem. And yet that version has been running since v35 came out, at least a couple of months. So I did it again but this time used the Android Revolution Wipe zip, then a straight install of v35. I could then load TB from Play Store and restore my apps and data. Phone seems back to normal now although I have lost some logs data from the couple of days between my backup and now - no biggie... I also now can update my apps.
So it seems it is something to do with Omega v40.
I've just DL'd v41 so will give that a try. Any help with what might have gone wrong would be much appreciated.
Thank you for your kind words, just sharing what i know and hoping this info can help others.
And how is it with v41?
Did you tried it with wifi and 3g, any difference?
Also tried removing your google account, reboot and setting it up again?
Hi kees !
Nice idea you've got with this thread but ... I hope it won't turn into another omega q&a thread . I would like to direct people here but it will be quite difficult if they will see Omega issues all over. Please point them out to the correct thread as you already posted the link to it. Just a thought , correct me if I'm wrong
Thanx !
Sent from my GT-I9300 using Tapatalk 2
xanthrax said:
Hi kees !
Nice idea you've got with this thread but ... I hope it won't turn into another omega q&a thread . I would like to direct people here but it will be quite difficult if they will see Omega issues all over. Please point them out to the correct thread as you already posted the link to it. Just a thought , correct me if I'm wrong
Thanx !
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Thanks and you are right, but the main purpose for me, is just help others with the noobish knowledge i have and let people and myself learn and share.
I don't mind which rom people are running, that's everyone his or here's choice and i totally respect that.
I think this thread deserves to be in General, since you're not asking anything. Hit "report" and see what a mod thinks about it
KeesStolk said:
Thanks and you are right, but the main purpose for me, is just help others with the noobish knowledge i have and let people and myself learn and share.
I don't mind which rom people are running, that's everyone his or here's choice and i totally respect that.
Click to expand...
Click to collapse
absolutely !!!
everyone`s choice ! but people must follow proper threads , i`ve got nothing against a certain rom but against disarray when users post or open endless threads about same thing .
some users hates me for this , i know it well , in my thread i always pointed out but somehow is unfair to maintain same topic on more threads .
that`s a bad habit for new users and not only for the rule`s sake but this is the way should be in a human community .
-=-=-
i was thinking as well to open a thread as yours but due to lack of time i didn`t. as soon as i`ll find interesting things i`ll let you know .
i myself am a NOOB !
---------- Post added at 11:28 AM ---------- Previous post was at 11:24 AM ----------
Glebun said:
I think this thread deserves to be in General, since you're not asking anything. Hit "report" and see what a mod thinks about it
Click to expand...
Click to collapse
... and i must agree with you this time ...
Thanks guys.
@xanthrax, i know the feeling, kind off busy family
But i like your comments, just straight forward, the way i like it.
Glebun said:
I think this thread deserves to be in General, since you're not asking anything. Hit "report" and see what a mod thinks about it
Click to expand...
Click to collapse
I think it should stay here as it "Helps" other users. General is more for discussions IMO.
But how about these?
http://forum.xda-developers.com/showthread.php?t=1749214
http://forum.xda-developers.com/showthread.php?t=1827635
http://forum.xda-developers.com/showthread.php?t=1732722
http://forum.xda-developers.com/showthread.php?t=1895737
http://forum.xda-developers.com/showthread.php?t=1946481
http://forum.xda-developers.com/showthread.php?t=2041679
and that's just the first page. all of the above are for "help"
I've recently installed AOKP(Jellybean 4.2.2) Task650 (http://forum.xda-developers.com/showthread.php?t=1808015) and the basic install seemed to go very well. I came from stock 4.0.4 (rooted) and for the record I'm using Recovery 6.0.3.0 and I did a full wipe including format system, data, cache, dalvik etc. I installed the new gapps after the ROM, and later restored apps using Titanium.
I have a few issues I can't quite sort out though, and I'm not sure if they are JB, Nova or AOKP related so I thought I'd start a new thread.
1) Lockscreen doesn't appear. At all. When I wake the tablet up, it just comes straight back on to the previously used screen. I've checked all the standard Security settings (unlock mode set to slide or pattern, lock on power button, etc) and also the fancier AOKP ones, but whatever I do the lockscreen just does not appear. I've re-cleared cache and dalvik.
2) Notifications are not showing in the Notifications area. I can see the AOKP 'Toggles' icons/tiles for wi-fi, bluetooth, GPS, etc; the clock; the battery level; the wi-fi SSID, etc - but no general Notifications at all (e.g. list of any updated apps, any download statuses, Poweramp mini controls, new emails/facebook messages, Samba active display, etc).
When these various notification are issued, I do see them appear briefly in the lower-right corner in a grey rectangular box which covers the clock/battery area of the status bar (so the notifications do appear to be triggering) but as soon as that brief message disappears, I can't see any of the notifications within the pop-up notifications area where they should be.
Does anyone familiar with JB, AOKP or this particular ROM have any suggestions, as I'm as a loss at the moment?
Andre
Ah, no-one with any ideas of where these issues might be coming from then?
I might have to try another full-wipe install, and if that fails just go back to stock 4.0.4 until (if ever) Samsung releases a JB update for the original 10.1 tab.
Andre
andrewilley said:
Ah, no-one with any ideas of where these issues might be coming from then?
I might have to try another full-wipe install, and if that fails just go back to stock 4.0.4 until (if ever) Samsung releases a JB update for the original 10.1 tab.
Andre
Click to expand...
Click to collapse
I'm not familiar with that rom, but there are a few things you can try.
1. Try posting in the development thread, it might be a known issue that has a quick fix.
2. If you really want to stick with that rom try the full wipe again. But since you already started with one I don't know if it will fix the problems.
3. If you want to stay with jb I would recommend Aopk build 6 by djmatt604. It runs smoothly and the dev is pretty active.
Hope this helps even a little.
kilometers4 said:
I'm not familiar with that rom, but there are a few things you can try.
1. Try posting in the development thread, it might be a known issue that has a quick fix.
2. If you really want to stick with that rom try the full wipe again. But since you already started with one I don't know if it will fix the problems.
3. If you want to stay with jb I would recommend Aopk build 6 by djmatt604. It runs smoothly and the dev is pretty active.
Click to expand...
Click to collapse
Many thanks for the reply. I have searched and asked in the dev's thread, but I get the very clear impression that if it works on his hardware and no one else has the same problem, his opinion is that it's 100% up to me to sort it out - which is entirely his prerogative, of course: his ROM, his thread, his rules.
Thanks for the recommendation of another AOPK option (I assume you mean [ROM][P7510][4.2.2][UNOFFICIAL] AOKP Build 6 :: MR1 :: Mar 29 Nightly). I think I might go down that route since, like you, I'm rather dubious that another full-wipe will be any different to the first one.
Andre
andrewilley said:
...
Thanks for the recommendation of another AOPK option (I assume you mean [ROM][P7510][4.2.2][UNOFFICIAL] AOKP Build 6 :: MR1 :: Mar 29 Nightly). I think I might go down that route since, like you, I'm rather dubious that another full-wipe will be any different to the first one.
Andre
Click to expand...
Click to collapse
Yup that's the one. I'd recommend doing a full wipe on the first install to avoid issues. Let me know if you have any other questions.
I went with [ROM][KERNEL][RECOVERY][JB4.2]Infamous AOKP 1.4 (14-Apr-13) in the end, from the same dev you suggested. I added Nova as my launcher and it all works like a charm (well, after I recovered myself from a stupid near-brick when I decided to format the user sdcard in order to clear out any remaining junk from old installs; it cleared out a lot more than I wanted!!!)
Andre
andrewilley said:
I went with [ROM][KERNEL][RECOVERY][JB4.2]Infamous AOKP 1.4 (14-Apr-13) in the end, from the same dev you suggested. I added Nova as my launcher and it all works like a charm (well, after I recovered myself from a stupid near-brick when I decided to format the user sdcard in order to clear out any remaining junk from old installs; it cleared out a lot more than I wanted!!!)
Andre
Click to expand...
Click to collapse
Yeah, I usually just wipe data / Factory reset when doing a full wipe and then go in manually and clean out folders that I don't need to clear space. SD maid is a good app for clearing unused space too.
kilometers4 said:
Yeah, I usually just wipe data / Factory reset when doing a full wipe and then go in manually and clean out folders that I don't need to clear space. SD maid is a good app for clearing unused space too.
Click to expand...
Click to collapse
Yeah, I'm normally the same but I thought I'd be nice and thorough for once and get rid of any remaining legacy ICS stuff which some JB updates shove into hidden folders when you upgrade. In hindsight, I shouldn't have bothered.
Still, at least when I finally did get the system recovered enough to install the new ROM, the free space was amazing!
Andre
I got the same problem...how to solve it bro....
srinuchry said:
I got the same problem...how to solve it bro....
Click to expand...
Click to collapse
I think the problem may have been with something that Titanium Backup restored from my previous setup, but I never found out what. I had to do a factory reset to clear it in the end (although not a full ROM reinstall).
As I'd already gone that far though, rather than risking re-installing apps again I actually chose another ROM anyway - Infamous (see above) - which I'm very happy with, and the devs there seem much happier to talk to you in general. Just my observation anyway, your experiences could well be quite different of course.
Andre
Hi all,
I have worked for a long time with ROMs with different origin (AOSP, Sammy based, CM 10.1, ...) however I'm unable to keep the ROM fresh and sharp for a long time. After a couple of weeks, delays start to occur randomly and the "snappiness" is gone.
In my opinion the apps have nothing to do with it as I restore them immediately after I install a new ROM (with settings).
So the question : do you have any maintenance tasks / tips I should regularly complete ?
DirtyWizard said:
Hi all,
I have worked for a long time with ROMs with different origin (AOSP, Sammy based, CM 10.1, ...) however I'm unable to keep the ROM fresh and sharp for a long time. After a couple of weeks, delays start to occur randomly and the "snappiness" is gone.
In my opinion the apps have nothing to do with it as I restore them immediately after I install a new ROM (with settings).
So the question : do you have any maintenance tasks / tips I should regularly complete ?
Click to expand...
Click to collapse
Why not regularly reflash the original rom or at least its bare bones nandroid and your TB backup .
jje
JJEgan said:
Why not regularly reflash the original rom or at least its bare bones nandroid and your TB backup .
jje
Click to expand...
Click to collapse
Would be an option to consider ! However still not clear to me what causes this .. When I look at the OS on my PC, I do know where the delaying factors are to be found (e.g. disk fragmentation, (uninstalled) software leaving files and registry entries, ...) and I can fix those ! I would like to do the same for my Android ROM.
DirtyWizard said:
Would be an option to consider ! However still not clear to me what causes this .. When I look at the OS on my PC, I do know where the delaying factors are to be found (e.g. disk fragmentation, (uninstalled) software leaving files and registry entries, ...) and I can fix those ! I would like to do the same for my Android ROM.
Click to expand...
Click to collapse
There is this app on the playstore that uses TRIM command called fstrim to flush out unused memory/storage (it's like a disk defrager on windows) thus making the device a little snappier more info about this app here: http://forum.xda-developers.com/showthread.php?t=2104326
You should also regularly clean your app cache (they're like temporary files created by apps just like in windows) by using apps like History Cleaner, Clean Master etc. If you're an advanced user i also recommend the app SD Maid. It cleans various system directories including your ext sdcard (it cleaned around 1gb when i first ran it) so be cautious and do research it's functions too before you use the app.
Without any explanation as to why, I found reflashing kernel keeps thing feeling fresher, and once a month I format everything including internal sd, and re-flash my rom, then restore only minimal system data via xml......txt/logs/WiFi ap etc
The more you modify Samsung Roms, the worse they perform imho
Likewise AOSP Roms, though they are always more snappy but also more bug prone, that is just my opinion though, we all end up with what keeps us happy, tweaked how we want it, so comparisons yet again don't mean a lot, just experience
Thanks for the responses so far .. I'm going to use the Lagfix for new and see how that advances. SD Maid I already use quite some time .. It is a bit sad to see that the OS can slow down so quickly.. although I have to admit I'm constantly experimenting and testing apps but I don't see an actual reason for the returning delay..
I'm afraid I'll have to get used to it or do a regular re-flash..
First few things: I don't know if I'm supposed to be posting this here, idk if the problem is device specific or not... Sorry if I've done anything wrong. I've searched already, can't find any similar threads that actually help. I have the international version. I was running the CM10.2 Rom prior to 'the accident'. I will pay for a resolution if need be - PM me.
There's a bit of a story to this so I'll go over it all - not sure what's relevant.
I've been running out of storage for days, a 64GB SD card is in the mail. I currently have an 8GB one as well as the internal 16GB, both of which were near full, but the external one had relatively more than the internal one, so I decided to use foldermount and link2SD to move some space over. That all went fairly well.
This morning I got invited to the Aviate Beta launcher, which looked interesting. Tried to install, didn't have enough space. So I decided to make a backup of Nova, go into the play store, uninstall nova to free up space and then install Aviate without leaving the playstore. It worked, turns out I don't like Aviate much, so I worked backwards. Uninstalled Aviate, went to install Nova. Not enough space (idk how). Uh oh.
So I deleted some less-necessary apps that I could reinstall later. Not enough storage. Notification comes up in the bar along the lines of "storage critically low, device may malfunction". Now whenever I attempted to enter settings, the process crashed. Great. Simple fix, flash a NANDroid back-up in CWM. I can't remember what the message was, but there was something wrong with the back-up.
Wiped everything and tried to flash CM10.2 from the external SD Card but it wouldn't mount. Data also wouldn't mount. I tried several SD Cards ( ie about 10, different brands, sizes, classes, etc out of hope). So I decided I'll open up and Odin and just re-do everything per /showthread.php?t=2387980.
Turn the phone back on, stock Jelly Bean lockscreen was there, and once unlocked only the notification bar was there (no launcher). So I used different versions of Odin, different cables, downloaded the image several times, etc etc. Nothing fixed it. In fact, it's worse now. after booting past the Samsung logo, the screen just goes black now. smh
Can anyone help? It would be extremely appreciated. It's also a time sensitive issue as I need the device for work on Monday.
Sorry if I've missed anything. Yes I'm a noob, but you great people at XDA have helped a lot of people out before so I'm hoping you can help me.
Thanks!