Related
I know i have seen this mentioned before but in running a search never found a definitive thread on it...so forgive me if this is redundant.
Its my understanding that the same rom build but one being loaded with as many programs as the partition will allow vs. the same rom build with most extra programs taken out should have no noticeable impact on performance as long as you use the task manager to only allow the same essential programs to load at bootup. the down side of a 'light' rom is if you want to add programs later it will not be installed in the partition with the rom....even if there is space..it will take away from storage space.
My question is, if my above assumptions are correct, why do people want light roms? why not have one loaded up with all that can fit...no matter if your talking 2.1 or 3.5 (3.5 giving more space for roms due to the partition being moved).
thanks
Why installing many non needed applications isn't a good idea in ANY PC?
Because..... startup loading .dll, services, reading BIG registry file, crowded windows directory slow down the PC, decreasing available resources and memory.
A WM6 ROM is a swiss knife! Many things, to answer to all user needs... but I have mine . SO you can chose the fast way, flashing a lite rom, of the hardest way (mine), flashing a FULL rom and stopping non needed services, avoid loading uneeded dlls... The same things the chef does before releasing a lite rom . This is the hardest way, you have to know deeply WM6 structure, using a light rom is the easiest way
sergiopi said:
Why installing many non needed applications isn't a good idea in ANY PC?
Because..... startup loading .dll, services, reading BIG registry file, crowded windows directory slow down the PC, decreasing available resources and memory.
A WM6 ROM is a swiss knife! Many things, to answer to all user needs... but I have mine . SO you can chose the fast way, flashing a lite rom, of the hardest way (mine), flashing a FULL rom and stopping non needed services, avoid loading uneeded dlls... The same things the chef does before releasing a lite rom . This is the hardest way, you have to know deeply WM6 structure, using a light rom is the easiest way
Click to expand...
Click to collapse
Stop, stop, stop
My rom is really full, and isnt slower then light roms.
hehe!
There is a difference in available memory with the different SPLs, spl1.2 gives you more storage memory than spl3.5.
That said......
when a rom is loaded with programs it sometimes gives a user problems to install a new build of a said program that was loaded in rom. When you install a newer build and then try to uninstall it you might end up with a "hanged" device (this happened to me multiple times), and the only way to not see that wait cursor is to soft reset, and after soft reset, the program is still there in "remove programs", and if you try to run it after soft reset it won't run, and if you try to install it again you will get the message that the program is already installed and you have to remove it first and when you try to remove it again your device is stuck with the wait cursor again.........after all this, the only way to remove this program that you can't use anymore is to do a hard reset.
this happened to me too many times, this doesn't happen all the time though...some programs got installed over whats built in, like opera9.5 but I ended up with 2 icons in programs.
This is one of the reasons that kicked me away from full roms. I liked full roms before but after these incidents I find that lite roms don't/hardly come with those kind of problems, plus I get more space with spl1.2 to install a good amount of programs that I use regularly and still have more than 100MB left to install more programs that has to be installed to main memory.
Below are things I had said in another post and didn't want to rewrite it, so I just copied and paste (something my friend can't do on his iphone, ha, I still laugh at him about it)
Well really, Lite versions don't really bring much to the table except that it allows me to install only the apps that I need or want without having my programs folder looking like something out of a horror movie , eg. if I use the more robust SoftMake Office 2008 there's really no need for me to have MS Office installed, right?
Lite versions gives me an almost clean OS which gives me the "feeling" that my phone runs faster (even it it isn't running faster and just a subconscious feeling). Plus it installs faster .
Lite Versions are just the courtesy from the chef to us the people who wants the lite version, because the chef cooks in the apps that he wants, so for him to take out all that just for us is real generous....get what I'm trying to say?
It is nothing superior to the full, it doesn't carry the bells and whistles, its just what it is "lite". I have a plethora of cabs and only the ones I use. On a full install I hardly use 50% of the apps that comes with it....actually, I might only use 25%.
For me it all boils down to this......a lite version offers me the option of really customizing my phone, no additives, just the things I put in it.
http://forum.xda-developers.com/showpost.php?p=2536154&postcount=26
I mean no offense to any devs, far from it in fact, but the more I learn about the process behind flashing/updating ROMs on Android the more I have to wonder ...
>> why are ROMs typically released as full/complete .zips rather than just a set of deltas from a known good base?
I'll take SuperClean as the example, which I use and adore; again there is no offense implied here. This is, for the most part, a deodexed stock EB01 ROM with a bunch of files removed and a bunch of files added/replaced, right? Something that one could do by oneself by adding/removing the necessary files via ABD and wiping? I actually did that on my own for my SC 2.7 upgrade from SC 2.6 and managed to avoid all the CWM hassle -- worked great (wiped cache and dalvik, of course).
Putting kernels aside for a moment ... what is the benefit to not providing an essentially static stock deodexed base ROM and implement each iteration as a delta to that base rather than a complete system? I may be way off base here, but it seems like a lot less hassle for the devs to me -- send out a couple delta .zip packages (one for an incremental update from the last version and another for a full update from the base image) rather than every file every time? It seems like a *lot* less downloading and a lot more error proof of a process to me.
I think *most* people that follow these ROMs are likely to be flashing to the bleeding edge as soon as the post goes out (I know I do!). If all that changed in a ROM was the framework .apk and a couple app .apks ... isn't it wasteful for both the dev and the users to create/download/apply a huge .ZIP rather than just CWM a couple hundred kilobytes and (probably) wipe the dalvik cache?
Kernels: As I've learned over time here, the kernels seem to be best suited when not attached to a ROM. I don't know if it's minor hardware differences or how we flash/apply the changes, but obviously not every kernel works well for every device (at least with Galaxy S devices - lol). My opinion would be that the oldest, most stable/compatible kernel be included with a ROM, if one must be provided at all. I think most people that have been able to get a grasp on the flashing/update/rooting process for Android are probably comfortable enough with separate kernel packages.
I'm sorry if I sound like I'm on a soapbox here ... I truly do appreciate the efforts being put forth that I am personally benefitting from I'm just wondering why a delta-based system that doesn't need quite as much care and feeding as full-on system ROM replacements do doesn't seem to be a popular way of doing things. If nothing else, it should greatly reduce the number of people that have issues with their battery stats being wiped out by a full wipe when the device was at 62% or something
Almost forgot ... I have no idea what good "zip aligning" does and perhaps that, or something else I'm too ignorant to understand yet, is the reason behind leaning towards full ROMs. I'm totally cool with being wrong about this -- flame away if you must, but don't be too harsh, my intentions were good ...
djp952 said:
I mean no offense to any devs, far from it in fact, but the more I learn about the process behind flashing/updating ROMs on Android the more I have to wonder ...
>> why are ROMs typically released as full/complete .zips rather than just a set of deltas from a known good base?
I'll take SuperClean as the example, which I use and adore; again there is no offense implied here. This is, for the most part, a deodexed stock EB01 ROM with a bunch of files removed and a bunch of files added/replaced, right? Something that one could do by oneself by adding/removing the necessary files via ABD and wiping? I actually did that on my own for my SC 2.7 upgrade from SC 2.6 and managed to avoid all the CWM hassle -- worked great (wiped cache and dalvik, of course).
Putting kernels aside for a moment ... what is the benefit to not providing an essentially static stock deodexed base ROM and implement each iteration as a delta to that base rather than a complete system? I may be way off base here, but it seems like a lot less hassle for the devs to me -- send out a couple delta .zip packages (one for an incremental update from the last version and another for a full update from the base image) rather than every file every time? It seems like a *lot* less downloading and a lot more error proof of a process to me.
I think *most* people that follow these ROMs are likely to be flashing to the bleeding edge as soon as the post goes out (I know I do!). If all that changed in a ROM was the framework .apk and a couple app .apks ... isn't it wasteful for both the dev and the users to create/download/apply a huge .ZIP rather than just CWM a couple hundred kilobytes and (probably) wipe the dalvik cache?
Kernels: As I've learned over time here, the kernels seem to be best suited when not attached to a ROM. I don't know if it's minor hardware differences or how we flash/apply the changes, but obviously not every kernel works well for every device (at least with Galaxy S devices - lol). My opinion would be that the oldest, most stable/compatible kernel be included with a ROM, if one must be provided at all. I think most people that have been able to get a grasp on the flashing/update/rooting process for Android are probably comfortable enough with separate kernel packages.
I'm sorry if I sound like I'm on a soapbox here ... I truly do appreciate the efforts being put forth that I am personally benefitting from I'm just wondering why a delta-based system that doesn't need quite as much care and feeding as full-on system ROM replacements do doesn't seem to be a popular way of doing things. If nothing else, it should greatly reduce the number of people that have issues with their battery stats being wiped out by a full wipe when the device was at 62% or something
Almost forgot ... I have no idea what good "zip aligning" does and perhaps that, or something else I'm too ignorant to understand yet, is the reason behind leaning towards full ROMs. I'm totally cool with being wrong about this -- flame away if you must, but don't be too harsh, my intentions were good ...
Click to expand...
Click to collapse
I def get what ur saying.. But alot of ppl.don't know how to use adb.... The only reason ppl would know is from other android phones.. Or if they rooted this phone right when it came out.. I think the whole zip is a great idea.. It sux 4 ppl like me cause my internet sux.. But even with the whole zip and the step by step error proof directions ppl still brick there ****.... My god ppl screw up odin n that's stupid easy.... I think the whole package is a simple way to hear less ppl.complaining
Sent from my SCH-I500 using XDA App
I smell what op is steppin' in. And I do update my own rom in that manor by just pulling updated frameworks of files and pushing them or making a cwm zip to flash.
good day.
One reason I can think of. What if you started at SC 2.0 and wanted to go to SC 2.8? That would be 8 or so zip files you'd have to flash, as opposed to just one (two if you want a theme). The same would apply if you went from AOSP, MIUI, or any other ROM back to SuperClean. Also, I feel like it's much easier to package a full ROM for flashing rather than small incremental changes. What if you miss a file in the update zip? It's harder to loose track of files IMO just packing the whole thing.
Also, I do agree with the kernels statement. I'd rather have them seperate, as it would prevent a voodoo user from flashing a NV kernel and the other way around when flashing a ROM. Either way, I package up my own "ROM" that is pre-themed and customized to my liking.
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"
Hello,
Is there a way to make SuperSU/SuperUser less slow? I mean, on a virgin rom it's already not so fast, but after you install your apps, it can takes minutes before the pop-up asking for root rights comes, if it comes..!! So is there a way to "fix" that? It's a pain, having to reboot sometimes cause of that!
Thanks.
goja said:
Hello,
Is there a way to make SuperSU/SuperUser less slow? I mean, on a virgin rom it's already not so fast, but after you install your apps, it can takes minutes before the pop-up asking for root rights comes, if it comes..!! So is there a way to "fix" that? It's a pain, having to reboot sometimes cause of that!
Thanks.
Click to expand...
Click to collapse
Set it to automatically grant permissions and turn notifications off, but remember that this is very insecure way so don't install any untrusted apps.
I've thought of that, but i'm not sure it would help : If it waits, let's say 2minutes, for showing pop-up asking for rights, then it would also wait 2minutes before automatically allowing apps...
2 minutes?? It should show immediately, so there is something wrong in your rom. Try to wipe cache and dalvik cache and fix permissions.
Man, this is not in MY ROM, this is in ANY roms... Seems that the more apps installed (=the more process running) the slower it'll be!
I agree. I have the same problem. I'm running CM13 (Marshmallow) on my old S3 i9300, and I flashed SuperSu (beta) for it. It work well, but its slow to grant permissions even when its meant to do so automatically. I've set it to start at boot, but this hasnt done much. Any fixes??
Same problem also here with every rom that I used it. Root in cm roms is almost instant.
same here on a custom cm12.1 rom
What the heck are you guys talking about? 2 minutes?! That is just plain wrong. I won't say impossible, cause you obviously have problems, but I have never seen that behavior you're talking about, and that is absolutely not caused by SuperSU or Superuser. Even my 7 years old HTC HD2 asks for, or grants root in 2 seconds max. Tell your developers to fix their ROMs.
Sent from my HTC One M9 using Tapatalk
Can it be that "Clean Master" or some other memory management software is pushing SuperSU back. Try uninstalling any memory management software.
never had issue having to wait for 2min either and ive rooted almost 50 diffrent phone from ics to lollipop to my current headache oppo mirror 5 still superSU still doing its job
I can confirm this is a real problem, but can also confirm it goes away with tweaking.
On aosp, it's important to disable the native su in dev options.
In anything else, for instance touch wiz, I have learned that system less root is evil, and mount separate name spaces is the devil.
Now, when installing prerooted rom, kernels etc, it's imperative to get your supersu set up prior to installing your root apps...or it will hit the fan....well..that's dramatic. It'll act oddly and you'll never realize what's causing things to be weird.
First and foremost, uncheck mount separate blah blah and reboot. Then, attempt to install supersu to system. If it fails after reboot, twice, then you must return the check mark to mount name spaces and reboot.
Once rebooted, try the "cleanup for reinstallation" and if that succeeds in allowing you to update/reinstall from play store, try to uncheck the mount name spaces again...then attempt the system install again...should work this time...
EDIT the point of all this is to test the app and the connection with the binary. If the app can't control the binary stuff, you'll probably be seeing lag. By doing all the options and checks that tweak the binary, you will have a good supersu environment, and the lag will disappear.
When you finally get supersu to do the things with its binary without crashing, you'll notice no more lag.
Further more, disabling notifications is an ABSOLUTE MUST. From @Chainfire himself, he suggests turning off notifications to get rid of overhead, and he states that logging does not effect it much, and after HUNDREDS of man hours tweaking and fiddling with supersu in every arena, from system less, to autoroot, I could not agree more.
Throw the man some love, respect, and donations, because he's at the front of the pack, hacking the infinite combinations of phones, to couriers, to software, to user intelligence.
His app is rock solid. The billions of other x factors are to blame
2nd edit mount name spaces will cause all sorts of odd things, so I disable that always, as well as notifications.
It's important to note, you'll always have delay for root requests in the first few minutes after boot, as certain things like scripts and even supersu itself might be denying for the first few minutes.
Enabling supersu at boot might help, actually it will help, but I've never needed it after configuring my root environment properly.
When everything fails, I Uninstaller root completely, and either reflash supersu, or my prerooted kernel of choice
3rd edit. Sigh, sorry. I notice my environment is in need of tweaking nearly 100% of the time when I flash a prerooted kernel, then a prerooted rom. Even flashing the kernel again, as is sometimes required for a rom not tailored for my device, will cause things to get out of wack which I notice instantly, when I got supersu lag
check if any other app stopping it.
I always update su binary, set the access to grant and delete su app.
Its d fastest way.
Read rules before posting questions on development forum¡*
Ur thread will b moved immediately.
BatDroid said:
check if any other app stopping it.
I always update su binary, set the access to grant and delete su app.
Its d fastest way.
Read rules before posting questions on development forum�?�¡*
Ur thread will b moved immediately.
Click to expand...
Click to collapse
â?¦
I don't even know how to process this ?¦ try my way first¦
I'd bet anything the speed will be just as fast¦ and i forgot to mention, i always enable full logging? so full logging, no lag?vs no nothing, no app, security etc
loogielv said:
I can confirm this is a real problem, but can also confirm it goes away with tweaking.
On aosp, it's important to disable the native su in dev options.
In anything else, for instance touch wiz, I have learned that system less root is evil, and mount separate name spaces is the devil.
Now, when installing prerooted rom, kernels etc, it's imperative to get your supersu set up prior to installing your root apps...or it will hit the fan....well..that's dramatic. It'll act oddly and you'll never realize what's causing things to be weird.
First and foremost, uncheck mount separate blah blah and reboot. Then, attempt to install supersu to system. If it fails after reboot, twice, then you must return the check mark to mount name spaces and reboot.
Once rebooted, try the "cleanup for reinstallation" and if that succeeds in allowing you to update/reinstall from play store, try to uncheck the mount name spaces again...then attempt the system install again...should work this time...
EDIT the point of all this is to test the app and the connection with the binary. If the app can't control the binary stuff, you'll probably be seeing lag. By doing all the options and checks that tweak the binary, you will have a good supersu environment, and the lag will disappear.
When you finally get supersu to do the things with its binary without crashing, you'll notice no more lag.
Further more, disabling notifications is an ABSOLUTE MUST. From @Chainfire himself, he suggests turning off notifications to get rid of overhead, and he states that logging does not effect it much, and after HUNDREDS of man hours tweaking and fiddling with supersu in every arena, from system less, to autoroot, I could not agree more.
Throw the man some love, respect, and donations, because he's at the front of the pack, hacking the infinite combinations of phones, to couriers, to software, to user intelligence.
His app is rock solid. The billions of other x factors are to blame
2nd edit mount name spaces will cause all sorts of odd things, so I disable that always, as well as notifications.
It's important to note, you'll always have delay for root requests in the first few minutes after boot, as certain things like scripts and even supersu itself might be denying for the first few minutes.
Enabling supersu at boot might help, actually it will help, but I've never needed it after configuring my root environment properly.
When everything fails, I Uninstaller root completely, and either reflash supersu, or my prerooted kernel of choice
3rd edit. Sigh, sorry. I notice my environment is in need of tweaking nearly 100% of the time when I flash a prerooted kernel, then a prerooted rom. Even flashing the kernel again, as is sometimes required for a rom not tailored for my device, will cause things to get out of wack which I notice instantly, when I got supersu lag
Click to expand...
Click to collapse
As he said i have dissabled notifications and worked, Thanks Man
I've had this problem on a Samsung Galaxy J7 (2016). It was because I disabled the encryption of /data. For details on how to solve it see here. I think there are probably other factors that can cause this, so this solution is probably not for everyone. But I would recommend checking your adb logcat to figure out if something is going on in the background that should not.
Since I installed SuperSu 2.79 on my klte on RR (los, android 7.1.1) the device started lagging, not a lot but enough to be annoying.
Greeting's, I would like to know if there's a way to verify android installation (or image, i'm unsure on which is the correct reference; pardon me.). I own a Nexus 5 (32GB) and my phone recently received 5.1 update. Update process finished normally, there was a reboot and the standard optimizing app's screen. Few days later, when I rebooted my phone; the same optimizing apps process started. I had checked that my 5.1 update was to build LMY47I and there is no further update to this build. At this point, I am bit concerned as to - 1) Why the optimizing application process started? 2) While I did google around a bit, I did not find any definitive way to check integrity of installed android image.
I'm a information security architect and almost all OS's have a way to verify its installed integrity. Windows for PC's have sigverif and SFC commands. Traditional BIOS is being replaced with UEFI which helps verify and maintain boot cycle integrity.
So, in android is there such process or tools or commands to verify integrity of installation?
Thanking you in anticipation,
Parth Maniar
It is doing it because something wiped the cache. There is no way to check at the moment. If it doesn't install properly then it will kernel panic and not boot at all.
zelendel, thank you very much for your reply. I personally did not wipe the cache partition. Also, will this occur every time cache partition is wiped? Because I've at times manually wiped the cache partition but application optimization has never started. Is there a logging mechanism to check why this was invoked? Is there a way I can enable, disable or control logging parameters? For example - In a PC environment, I can log all network traffic using syslog standard or enable logging using group policy in windows. Does android have any such option?
Please don't mind my questioning and don't let that make you feel that I'm doubting your answer. I am just trying to learn. I would like to once again thank you for your prompt answer.
Parth Maniar.
ParthManiar said:
zelendel, thank you very much for your reply. I personally did not wipe the cache partition. Also, will this occur every time cache partition is wiped? Because I've at times manually wiped the cache partition but application optimization has never started. Is there a logging mechanism to check why this was invoked? Is there a way I can enable, disable or control logging parameters? For example - In a PC environment, I can log all network traffic using syslog standard or enable logging using group policy in windows. Does android have any such option?
Please don't mind my questioning and don't let that make you feel that I'm doubting your answer. I am just trying to learn. I would like to once again thank you for your prompt answer.
Parth Maniar.
Click to expand...
Click to collapse
As to why it happened I am not sure. I normally happens when the delvic cache partition its self is wiped. There are some tools that might help with what happened. You could look into logcats and last_kmsg HERE is a great tut on them that might help. There are also a few on device apps like catlog and a few others that might help.
Oh no not at all. I understand completely where you are coming from. Most of the error logging is done in a linux setup and not on device or windows really. It also depends on the device and the distro of android your using.
I'm currently using stock androind (AOSP) on my Nexus 5. One of the reason's that I've never tried running other android built is mainly my lack of understanding. Not that I know how AOSP works but I feel tad bit secure knowing it's the official build. Like your signature say's "Security is an illusion".
I would love to play around with Android but where would you suggest is the best and safest way to start, from the perspective of a clean restore. For example - PC's have virtual environments where I can do testing or even trying to break a software just to learn how it works. What kind of process or tools are used for android.
I have one more question (Pardon me for the question parade ) but how does one verify tools posted on Internet which deal with reseting firmware or even factory flags. I have tried on a test phone resetting LG flag for tampered. I had manually flashed the phone with android 5.0 image which required unlocking the bootloader. So to ensure I can claim warranty i used the temper reset tool. While I truly appreciate the author(s) of that particular and such other tools which assist "hackers" (this would be the correct use of the word) immensely. How can one be sure that no malware code is present.
If you've ever researched on this - There are couple of companies out there giving tools (software) for complete control of the phone. Most of them excel at giving features for Android. While that scares me, it also gives an opportunity to learn on detection and remediation.
ParthManiar said:
I'm currently using stock androind (AOSP) on my Nexus 5. One of the reason's that I've never tried running other android built is mainly my lack of understanding. Not that I know how AOSP works but I feel tad bit secure knowing it's the official build. Like your signature say's "Security is an illusion".
I would love to play around with Android but where would you suggest is the best and safest way to start, from the perspective of a clean restore. For example - PC's have virtual environments where I can do testing or even trying to break a software just to learn how it works. What kind of process or tools are used for android.
I have one more question (Pardon me for the question parade ) but how does one verify tools posted on Internet which deal with reseting firmware or even factory flags. I have tried on a test phone resetting LG flag for tampered. I had manually flashed the phone with android 5.0 image which required unlocking the bootloader. So to ensure I can claim warranty i used the temper reset tool. While I truly appreciate the author(s) of that particular and such other tools which assist "hackers" (this would be the correct use of the word) immensely. How can one be sure that no malware code is present.
If you've ever researched on this - There are couple of companies out there giving tools (software) for complete control of the phone. Most of them excel at giving features for Android. While that scares me, it also gives an opportunity to learn on detection and remediation.
Click to expand...
Click to collapse
You could use a live disc and run Linux which would allow you all the great tools. I would start with the android SDK which allows for virtual devices. I have a dual partition set up to boot up linux so I can download all the source code and go from there. As you have a nexus you have almost complete freedom in that aspect. When dealing with devices like LG, HTC or the worst being Samsung it gets alot harder dealing with resetting flags. They are working harder and harder to lock things like this down. Now that Samsung has given alot of the Knox code to google for use in the base AOSP code it will get harder. Alot of the newer devices with knox cant even have the bootloader unlocked.
As for being sure there is no malware included that gets a bit harder. Most rely on a good malware software. I can not attest to any as I dont use any of that myself, I am just very careful with what I download. Any company that is giving away software that claims to allow you to completely control a device is bound to have some sort of malware involved. I have seen a few and alot of them have ransom ware deeply embedded in them.
Thank you very much again, zelendel. I wanted to correct or better explain what I already mentioned. I was referring to companies which offer hacking services .. I've had couple of run downs with them and they "sell" products, with capabilities well beyond general publishing. I wanted to learn on how to counter them. Sadly, I'm not a programmer and downloading source code will help me little. But i will still setup as you've mentioned. What linux distro do you use? I hate multi boot with UEFI especially since i use a FDE product. Ah, the fun of setting up a lab.
Thank you very much again. Journey in Android begins now.
PS: Have you used any other android build except the AOSP? I would like your take on that too.
ParthManiar said:
Thank you very much again, zelendel. I wanted to correct or better explain what I already mentioned. I was referring to companies which offer hacking services .. I've had couple of run downs with them and they "sell" products, with capabilities well beyond general publishing. I wanted to learn on how to counter them. Sadly, I'm not a programmer and downloading source code will help me little. But i will still setup as you've mentioned. What linux distro do you use? I hate multi boot with UEFI especially since i use a FDE product. Ah, the fun of setting up a lab.
Thank you very much again. Journey in Android begins now.
PS: Have you used any other android build except the AOSP? I would like your take on that too.
Click to expand...
Click to collapse
I personally Use Ubuntu as it is the supported android building setup. It was easy to setup and use for a Linux noob like I was. Oh God I know what you mean with UEFI.
As for countering them. The easiest way would be to pay attention to what gets root access. This would be the only way they could really do anything major. Mainly with the new sandboxing in android 5.1
I have used just about every distro of android available. I have used OEM Roms like HTC Sense, Samsung Touchwiz. I have used all of the AOSP based roms. CM, Slim, AICP, DU (my current), PA. I now avoid CM based builds and stick to builds that work off of AOSP instead of CM based. This is due not only to the companies BS stand on removing Google from android but they have a bad habit of treating others like trash and merging untested code which can cause issues like the recent string of nexus 6 bricks.