Related
Hi everybody
Ive been around thousand of threads on xda-dev and couldn't find any official one for Anti-Virus. That's the main reason why I'm starting this new thread and also because Anti-Virus on Pocket PC are growing more and more. Actually we are not safe but we don't care until we get infected and that will be too late, with most of the time the only solution a hard reset.
Let's discuss and compare in this thread the different Anti-Virus SW available on the market today, and bring out positive/negative points based on our experience. It will be benifit for everybody ...
I know everyone hates Norton/Symantec but I was on the beta testing team for Norton Smartphone Security Premier Edition since day one and it is very friendly and easy to use.
http://www.symantec.com/home_homeoffice/beta/overview.jsp?pvid=nssp1beta
Actually I was using Symanter antivirus for handheld on my QTEK 2020i WM2003SE and that's true it is user friendly and worked fine, with virus definitions updates very ofently.
I was unable to install it on my HTC Athena WM6
Do you know is there is any version coming for WM6 Pumpiron?
I checked you link and it's different from what I used to have on my old device.
Ill download this beta and try it.
I'll let you know what I think about it, if it slow down the machine etc ...
It did not on mine and when I uninstalled it, it was gone...no traces..part of the beta testing. I did uninstall from my desktop, not my PPC
I am curios, how does this effect your device speed and performance?
What is the CPU and memory usage (in reality, not what stated on the site)?
I have Symantec on my XP PC and it sucks big time (does the job for the most part, but very slow and heavy).
eTrust came pre-installed on my Jamin, but that is an even bigger atrocity!
Another question - do they have a list for PPC viruses on their site like they do for PC ones?
The only PPC virus I heard of was a harmless proof of concept that could make files display a pop-up message and did not reproduce.
If real viruses for WM systems are already out there (I know its a only matter of time) I would be interested in reading up on them to know what I am facing.
Also, anyone actually caught a virus on a WM machine and can share the experience?
Here are my first impressions:
1 - The Startup time of my Athen after a soft reset has increased by around 20 sec, this because Symantec is loading on the startup.
2 - I didn't noticed a slow down during normal utilization of the device, but it's really early before concluding on that point because I need to try different applications.
3 - When I first connected to the Internet via WiFi, even the connection were established, could not load the pages having an error "page not found"
but after 15sec everything is back to normal and connections to Internet was not a problem at all.
4 - I just suffered a Freeze but not sure it is due to Symantec, because i've been suffering frequent daily freezes on my Athena since I upgraded to WM6.
But the freeze came this time while using the Antivirus SW
5 - The package is composed by an AntiVirus, a Firewall, a Norton Secure Folders utility and a Norton Tools utility.
6 - Also note that after finish installing it, it force you to set a pin code that you will have to enter everytime you soft reset your device. I tried to disable it but it won't let you do it
I'll give more details about the package in a different post after some testing
levenum said:
I am curios, how does this effect your device Another question - do they have a list for PPC viruses on their site like they do for PC ones?
Click to expand...
Click to collapse
You can check the list from the SW installed on the PPC
Just applied live update over WiFi and basically there are 5 in the list:
EICAR-TEST-FILE
WinCE.Duts.A
Backdoor.Brador.A
Trojan.Redbrowser.A!jar
MSIL.Cxover.A
Definitions : 04/06/07 ver 2.0
As promised, here is my feedback on the tools provided in the package:
1 - Norton Antivirus
Very friendly and easy to use, from the menu u can access the options for the Antivirus, the Scans, the AntiSpam, Updates and Proxy config. You can also access the quanrantined files, the activity log and the virus definitions list. Manual scan and automatic scan can be performed.
2 - Norton Firewall
I didn't really understood how we use the Firewall function. Basically when you start it you have a tab showing the security level. It is have different security levels for World (the highest), Office, Home and Open Sapce Networks (the lowest). Also you can not modify them at all. You can access a second tab called Events by severity in last and a third tab "Event list" which show in details all the events that happened on your device, like soft reset, login success .... very weird as we can not reset this list, also we can not change any parameter in the Norton Firewall, everything is set by default
3 - Norton Secure Folders
from what I guessed, this utility allow you to choose folders on your device and set them as secure. I don't know what it does exactly but I think it should encrypt the data inside the folder so it's protected in case you have been attacked by a trojan who collects your data and send it to the pirate.
You click on menu->Add->then you choose from the list Device, Mircrodrive or Storage Card if you have one. Then you type the name of the folder you want to secure.
I did a test, I choosed Device, and kept the folder name blank and clicked on ok. It added the "secure folder" under device. if you try to remove it you will have this warning "Removing the secure folder will destroy all data in the folder. do you really want to remove it?"
4 - Norton Tools
It contains 2 utilities, GetUUID and Lock
GetUUID will display on the screen 2 series of digites
the first one don't know what it is and second one is your IMEI
I guess this info is needed when the final version is released and
you need to register the SW
Lock utility display the following message when u click on it
Encryption may take several minutes. Pls wait for the device to power off.
If you need to soft reset, pls wait until encryption is completed and the
device powers itself off.
I clicked on yes, so the device start encrypting something .... then the screen turned off. I turned it on using the power button and it displayed to me the password screen which I entered. then it displayed the message decrypting for about 30 sec, then I had my normal today screen ...
Im wondering if it does not encrypt/decrypt the secure folders you
already chosen using the "Norton Secure Folders" utility.
Ive wrote to Symantec asking them for a manual or user guide, hopefully they will reply.
I have rated this SW 3/5 on their site, mainly because it is not clear what all utilities does and because Firewall is set by default and noting can be changed.
Hope my feedback will be usefull, and I hope other users will bring to us their experiences with the different Anti-Virus SW they have used on their Pocket PCs.
Just as I suspected, no real viruses just a nice proof of concept that asks you if you want to try it:
WinCE.Duts.A
A back door that needs to be run and does not spread:
Backdoor.Brador.A plus it would be useless if you are on GPRS/EDGE/UMTS or behind a NUT router.
This one seems like it could actually be trouble, if:
a) you leave in Russia
b) you are stupid enough to believe you can get WAP pages through SMS and that it would be cheaper than GPRS
c) you can get it to work on PPC.
Trojan.Redbrowser.A!jar
This one though, I have to admit is rather clever - using .NET to run both on PC and PPC amd is fairly destructive:
MSIL.Cxover.A
It is still unclear, however how its spreads from PC to PC (presumably you have to download and install / run it).
Of course given the fact that many people save their docs on SD and not the default My documents folder and that they do not disable security completely on their WM 5 and up devices (which are becoming majority these days) the effectiveness of this worm is more than questionable.
Well I still think it is too early to actually by this kind of apps. Also I think that as with many other programs the same "heavy" approach that works on PCs with many resources will not work well on PPC (not the way they are today). A different solution to virus protection needs to be found to be useful.
But hey - thats just my opinion...
So from what ive read its still to early to be using a resource draining av on the ppc? If this is the case, how about Spybot S&D? Is spyware more of a threat than viruses? are they really that much different? I find that spybot updates more regularly(when i connnect wifi).
as with virus's i believe that have to be made to support ppc's
in which case maybe due to spyware makers lack of innovation
that market have yet to take off
WingChan: whether to use the software or not is a personal decision - my belief is: given the list of threats it is too early. Also I believe that the method used to protect against viruses on PC is not suitable for PPC because of the resource requirement. Something more efficient needs to be invented, perhaps taking advantage of difference in architecture between WM and desktop - like the fact that system files can not be corrupted but only hidden.
Note that BigDede preformed the test on HTC Advantage which has a 600+ MHz processor if I am not mistaken. I doubt the app would be as unnoticeable on my 200MHz Prophet.
But it is only a matter of time before someone writes a real and damaging virus for this platform as it becomes more and more common. So if you really value the info you have on there you might want to get protection already - although a good and frequent backup would be much better.
I haven't heard of spyware for Windows Mobile, only major one for BB - any one got any news on this?
There is a major difference between spyware and viruses:
Viruses try to cause as much damage as possible and their effects always become visible sooner or later, in many cases almost immediately after infection.
Spyware on the other hand, needs to hide and tries not to interfere in device operation as much as possible and show no sign of activity.
levenum said:
WingChan:
There is a major difference between spyware and viruses:
Viruses try to cause as much damage as possible and their effects always become visible sooner or later, in many cases almost immediately after infection.
Spyware on the other hand, needs to hide and tries not to interfere in device operation as much as possible and show no sign of activity.
Click to expand...
Click to collapse
Very good explanation of the differences between Viruses and Spywares.
I agree also that it is too early today to really worry about having protection, but I prefer to be ready instead of regretting and wishing I had some protection.
Very good remark as well regarding the frequent backup ...
Need Help
Hello Everyone,
I'm not a developer, but I found your thread on this subject via Google and was hoping I could ask a question...
I'm able to download the Norton Smartphone Security Premier Edition Beta version, but when I try to install it (which I assume must be done first to my laptop, followed by sync'ing my laptop with my 8525) a "Self-Extracting Archive" window comes up that says: "Warning, one or more files skipped". This occurs when the installation process reaches "Extracting: SUPPORT\START.ICO 100%".
Does anyone know what I'm doing wrong?
Many thanks for your time!
A. J.
ajbt said:
Hello Everyone,
I'm not a developer, but I found your thread on this subject via Google and was hoping I could ask a question...
I'm able to download the Norton Smartphone Security Premier Edition Beta version, but when I try to install it (which I assume must be done first to my laptop, followed by sync'ing my laptop with my 8525) a "Self-Extracting Archive" window comes up that says: "Warning, one or more files skipped". This occurs when the installation process reaches "Extracting: SUPPORT\START.ICO 100%".
Does anyone know what I'm doing wrong?
Many thanks for your time!
A. J.
Click to expand...
Click to collapse
Hi
Maybe this warning is not a big deal, have you tried to install it by double clicking on the start.exe file ???
G.S./BigDede,
Thanks for the reply. I really appreciate it.
If I understand your recommendation, I don't think that gets me where I need to be. However, it could always be user error on my part.
When I try to "Setup" the file I downloaded (called "NSSPB.exe") from Symantec, a window comes up that contains a button that says "Install". However, after I click on it, it gets to a point in the installation process that shows "Extracting: SUPPORT\START.ICO 100%", and the process simply stops and a small window comes up that says: "Warning, one or more files skipped".
In essence, it appears I have recieved the entire 4.04 MB of program files I downloaded, but something goes askew when I try to extract/install them.
I'm stumped...
Thanks again, A.J.
I'll extract the files and will zip them for you.
Send me via PM your email adress so I can send you the zip file
Cheers
INTRODUCTION
This is a guide made to with help from Xperia X10 users and developers for Xperia X10 users enjoyment but most of the tips contained here are suitable for any phone running Android. The tips contained here focus on WHAT to do to improve the performance of your phone and not HOW to do it, after all, once you know what must be done is to find simple tutorials on how to take these actions.
For some of the tips contained in this guide I assumed that you have just installed a new ROM or formatted / bought your phone recently and have root access but even without these prerequisites this guide can still be useful to most users.
It’s important to say that although most of the tips some are quite basic, some require a little more work and deal with the more delicate parts of your phone, they should be made at your own risk. These more advanced tips often use very specific terminology which you can find more about on XDA Developers or even Google.
Finally I would like to remind that even machines that are made within a few standards can operate in different ways: some phones take better advantage of certain adjustments and settings and not others so it’s impossible to guarantee one hundred percent efficiency for all of you but still I that you make good use of this guide.
Sincerely,
Guilherme "XOT" Oliveira
- Install a good ROM and a good Kernel
Official ROMs are good but custom ROMs are usually faster and in many cases as stable as official ROMs. This is because ROMs are released and thereafter rarely change, custom ROMs are already made by developers who are constantly improving their job to get the most out of your phone. It's very important to research before installing a new ROM, searching always for the one that meets your expectations and relates well with your device since the same ROM can work very well on my x10 but not as well on x10 my brother’s for example.
The same goes for Kernels, but with Kernels take extra care to make sure that the Kernel is compatible with your desired ROM and your phone.
- Keep clean your caches
Caches are good to keep certain information and have access to these faster but with these files and information some "garbage" is stored .
The solutions to this can be pretty basic or advanced, the most basic way is to enter your Application Manager (Settings> Applications> Manage Applications) and clear the cache for each application. It is important to clear the cache only and not application data as these may be important such as the files that resemble your progress in a game. Already the most advanced solution is to clear the Dalvik Cache and Cache Partition through your recovery.
Both solutions don’t need to be made with daily frequency, for example I usually clean my caches every 45 days or when I feel that the phone is getting slow.
- Make a full, but clean, backup
Full backups (full system backup) like those made by recovery or nandroid are great to store complete setups but when they are done with “dirty” files in the the phone’s memory restoring these files may worsen rather than help the situation of your device .
Ideally, do a full backup after completely configure your phone (configure your account, set your homescreens, install the required applications, etc.) but before using it for real.
That way if your phone starts getting slow and nothing works to reverse the situation you can easily go back to your “original” settings without the hassle of customizing everything in its way again.
- Do not touch the CPU / GPU the first day
Like people, phones also take a while to adapt to a new environment, or in our case new ROMs, so during the first 24 hours of use is important to use the settings of CPU and GPU that came with the ROM, no overclock, undervolt and things like that.
Another important step in the process of adaptation to the new ROM is really using and exploring the device in this very first day so it "get used" to the change. Do not mind the battery consumption, that should stabilize after a few days.
It’s also iimportant to remember that some ROMs already comes with overclock, undervolt and improvements in battery usage. In this case there is no problem in using these settings from the first minute because if they are there since the installation of the ROM, it is because they are part of the default settings already programmed and develop on this particular ROM and it will work better this way.
- Use the maximum your battery
Batteries seem to last less and less as time goes on, in part this is because your battery is uncalibrated and there are ways to fix it.
I will not talk much on this subject because it is very easy to find guides that teach you how to calibrate your battery so I’ll just recommend that you take a look at them.
- Applications: less is more
Having millions of apps is the glory and the doom of smartphones, the glory because you can do everything on your device and doom because of the following reasons:
As a computer your phone also slows down the as it becomes full and in most cases you can blame it on the number of apps that you have installed on it. So try to leave installed only the applications you actually use and uninstall the ones that you no longer use so you can have more free memory and consequently a faster device.
Some applications can not be uninstalled because they are system applications; in order to remove those apps you are going to need uninstallers that have root access (ex: RootUninstaller) which are capable of removing these applications but before taking such a measure is necessary to look for a safelist (a list of applications that can be removed without causing system problems).
Keeping a low number of applications but doing so by installing and uninstalling new apps every day also usually let the machine slower so if you find an application for a specific function that fits your needs you should stay with it instead of testing another 10 before returning to it.
PS: A good way to avoid testing several applications before finding the right one is reading reviews and comments before making your choice.
- Repair defective applications
Often the phone is working fine but a certain application or function is not, which can cause slowdowns and FCs (force close); depending on the situation there is not much to do but some of these solutions may take care of the problem:
The first thing to do is to uninstall and reinstall the apps via Play Store to make sure that the problem was not caused by a corrupted file when you downloaded the application, if the problem persists there are some more advanced alternatives: in the advanced settings of your recovery select fix permissions, this function should make sure that every application has the necessary permissions to work properly.
- Keep some free space
Full memory is often a problem on any device, especially in older phones like ours, after all the more files the longer it takes read all these files if it is necessary, so the tip is this: the more free space the better.
This step seems a little redundant since we already talked about having the smallest possible number of applications but this time we are also talking about other files. Anything occupying space on your phone is "bad"; too many photos, songs, text documents, etc.. can make the phone slower and lets be honest, you do not need to carry 150 photos of your last weekend with you all the time.
A solution to this problem is simple, try to keep the memory of your phone as free as possible by eliminating caches, unused files and moving applications to the SD card (Settings> Applications> Manage Applications> choose the application and select Move to SD card or use apps like Link2SD); your SD card should also be kept clean by eliminating unused files and traces left by already uninstalled applications, such traces are sometimes hard to find and applications like SD Maid can help you eliminate much of this "junk".
- Avoid keeping some applications running all the time
It’s very common to close an application and assume that it stopped running on the system but this is not always the case because it actually still cached in the memory of the device, Android makes it to be faster on reopening it later and often the system itself definitively closes the application automatically but that’s not always the case.
Firstly it is important to prevent certain applications from even opening and to do this we use apps known as Startup Managers, there are several options in the Play Store but I particularly like Autostarts. Once inside your Startup Manager you can choose which applications will be opened as the system is started or any action is taken (for example changing the state of your Wi-Fi); the ideal is to minimize the number of self-starting applications, leaving only the truly necessary ones without forgetting to be very careful to avoid stopping system applications because if they are unable to open themselves it can cause instability. Another way to prevent applications from opening or stay on cache all the time is to disable automatic updates of apps such as email clients and social networks but this is a more personal matter that varies from user to user, just remember that the more constant the updates are, the more time these applications will be running in the background and more power (CPU and battery) will be consumed.
Now that we’ve already took care of the self opening apps it’s time to find out when you really need an app to be closed for sure.
It's easy to know when to quit an application completely but it is necessary to first understand a basic concept about the system: applications and processes cached in memory are not always a bad thing, in fact as stated at the beginning of the topic they are a good thing because the application should open faster when launched again (hence the use of Task Killers usually worsens more than help if not done properly) but if you use an application to view the weather every morning and will only use it again the next morning this application can be closed without problems.
In our current official version of Android (2.3) already have a task manager that can be used to do this action (Settings> Applications> Running services > select the desired process and press Stop) but if you want a more advanced option there are several Task Managers that monitor processes and can be used to close them too.
PS: Again about the Task Killers: although its use is discouraged for the day-to-day because of the reasons already explained, if you plan on haevy gaming they can be the great saviors since these games need a lot of free memory to run without lags.
- SMS: clean your inbox
Message apps, both native and third-party tend to take quite some time to open if you have many messages on your mobile because everytime you run your message app it needs to load a large list of conversations, so cleaning your inbox periodically helps performance, the same goes for call log.
A tip for those who want to clear the messages inbox and call log without losing your information is backing up with applications like SMS BackUp + that emails you both your conversations and call logs, all within a specific marker so they won’t end up messing the inbox of your email or if your intention is to save only one or two most important message the native client and most ones available at Play Store have the option of forwarding SMS, simply by holding your finger over until the action menu opens up.
- Give your device a break
Like conventional systems for computers, Android also collects information in its memory and despite the “dumping information system” some of it is left in cache , which ends up requiring more processing on your device.
To end this there is a very simple solution: give a rest to the phone. Once a day or when you feel like the machine is running slow give it a reboot or shut down and leave it off for a minute or two before restarting, it should get rid of the cache and it can boost the speed of the phone, but attention: restart the machine and making it open up various apps on boot has no point so keep your boot clean (see related topic).
- About some specific applications:
Task killers (that goes for any app of this kind) are good for a heavy gaming experience (eg: GTA, Dead Space, Asphalt...) because those games need a lot of free RAM but for everyday use is preferable to don't use task killers and keep some of the apps in the cache so they open faster when they are requested again.
Deep sleep is an important part of the ROM performance when it comes to battery usage, applications like CPU Spy can check if this function is working correctly or No-frills CPU Control which in addition to monitoring provides the ability to adjust the frequencies and governors you want to use in your phone.
Chainfire3D is an useful app to change the way your GPU will work and customize it to gain performance or quality , notice that these values tend to be inversely proportional.
Try always to use the lightest possible applications, it helps in memory. I for one think the galleries and music players of almost all default ROMs are too heavy and prefer apps like QuikPic and UberMusic.
Finally I would like to thank: XDA Users: Oodie, x10forevers, Vasishta Reddy, DiKeJ, 9Lukas5, FeraVolt, alzbac, Websites: lifehacker.com, limitlessdroid.com , doctor-android.com, androidcentral.com for helping with the tips on this guide and say that if you have a tip that is not in this guide feel free to share with us!
PS: I'm sorry if I made some grammar mistakes, English is not my first language and this is a pretty big article.
thanks...nice one..
Dude I screwed my music thing on x10 . Please help . Tried flashing xperia s music player . Now music icon has dissapeared . N power button seem to reboot all the time . Will updating binary files of xrec n then flashing again help ?
Please tel . Desperately.
Rooted x10 2.3.3 stock Rom
Sent from my X10i using xda premium
theMoiz94 said:
Dude I screwed my music thing on x10 . Please help . Tried flashing xperia s music player . Now music icon has dissapeared . N power button seem to reboot all the time . Will updating binary files of xrec n then flashing again help ?
Please tel . Desperately.
Rooted x10 2.3.3 stock Rom
Sent from my X10i using xda premium
Click to expand...
Click to collapse
Hey dude, I don't really know how to help you because I haven't had any similar problems but I'm pretty sure that you should try the basics: clear caches (dalvik included) and fix permissions.
Since I'm not a developer I can't really help you with the binary files but try reaching your ROM's developer and he might help you
I hope you get your phone fixed
Dude u sure that I should clear off dalvik cache ? I tried fixing permission but still nothing . The power button rebooting the phone is more irritating than not having a default music PLAYER . Im asking in this forum but havent got the solution yet :'(
Sent from my X10i using xda premium
Excellent post Buddy . Hope you update the thread with other power users opinions & Tips .
Thanks.
Oodie.
theMoiz94 said:
Dude u sure that I should clear off dalvik cache ? I tried fixing permission but still nothing . The power button rebooting the phone is more irritating than not having a default music PLAYER . Im asking in this forum but havent got the solution yet :'(
Sent from my X10i using xda premium
Click to expand...
Click to collapse
I think that the only people that can help you are the ones on your device's specific forum man, try creating a topic there
Sorry but I really don't know what to do to fix your phone
Some of the tips are a complete waste of time and utter crap (mostly those related to keeping RAM usage low and task killers [EDIT: actually, you contradict yourself on these points], giving the device time to "adapt" to the environment -seriously?- and going for the lighter apps -this obviously applies if you have an outdated device, but it's not a rule).
EDIT: Forgot to say that the rest is good.
GermainZ said:
Some of the tips are a complete waste of time and utter crap (mostly those related to keeping RAM usage low and task killers [EDIT: actually, you contradict yourself on these points], giving the device time to "adapt" to the environment -seriously?- and going for the lighter apps -this obviously applies if you have an outdated device, but it's not a rule).
EDIT: Forgot to say that the rest is good.
Click to expand...
Click to collapse
As I said the guide was wrote based on Xperia X10 user experience so it is kind of an old device.
About the RAM management you won't have any issues with a top device with a lot of free RAM but in our case (old device users) we have about 256mb or less RAM to work with so keeping it well managed is essential if you want your device to run smooth.
The adaptation thing seems like BS but it's not, because your device need to create/edit some files as its being used and that's what this part of the article really means. For example your battery writes a log about its own capacities (making a long story short by recalibrating your battery all you do basically is reset this log)
Thanks for the feedback, hope you found something usefull
GuilhermeXOT said:
As I said the guide was wrote based on Xperia X10 user experience so it is kind of an old device.
About the RAM management you won't have any issues with a top device with a lot of free RAM but in our case (old device users) we have about 256mb or less RAM to work with so keeping it well managed is essential if you want your device to run smooth.
Click to expand...
Click to collapse
No, it's not essential. It's actually bad.
The lifehacker website seems to be down, so I'm giving you a link to this article instead (the article itself links to three more detailed articles; one of them is the lifehacker article I wanted to link; do read them): http://androidandme.com/2011/11/app...lers-still-dont-give-you-better-battery-life/
EDIT: Regarding the battery, draining the battery (to 0% or close) is actually bad for lithium based batteries and should be avoided. A discharge to 15% is usually enough.
GermainZ said:
No, it's not essential. It's actually bad.
The lifehacker website seems to be down, so I'm giving you a link to this article instead (the article itself links to three more detailed articles; one of them is the lifehacker article I wanted to link; do read them): http://androidandme.com/2011/11/app...lers-still-dont-give-you-better-battery-life/
EDIT: Regarding the battery, draining the battery (to 0% or close) is actually bad for lithium based batteries and should be avoided. A discharge to 15% is usually enough.
Click to expand...
Click to collapse
I get your point and I also talk about the same thing as the article in the guide: "the use of Task Killers usually worsens more than help if not done properly" , I just didn't elaborated on this very much.
Now, what I'm saying is that if you are a day-to-day user you don't need a task killer and it's recommended ONLY for a gaming experience, aka heavy games like GTA, Dead Space, etc...
"Task killers (that goes for any app of this kind) are good for a gaming experience but for everyday use is preferable to keep some of the apps in the cache so they open faster when they are requested again."
I'm not a task killer fan myself but if you check any gaming rom (DikeJ's for x10 is a good example) you can see that the developers try to maximize the free RAM because those heavy games use a lot of it.
So in order to avoid this kind of confusion I'll edit the article to solve this misunderstanding thx for the heads up
GuilhermeXOT said:
I get your point and I also talk about the same thing as the article in the guide: "the use of Task Killers usually worsens more than help if not done properly" , I just didn't elaborated on this very much.
Now, what I'm saying is that if you are a day-to-day user you don't need a task killer and it's recommended ONLY for a gaming experience, aka heavy games like GTA, Dead Space, etc...
"Task killers (that goes for any app of this kind) are good for a gaming experience but for everyday use is preferable to keep some of the apps in the cache so they open faster when they are requested again."
I'm not a task killer fan myself but if you check any gaming rom (DikeJ's for x10 is a good example) you can see that the developers try to maximize the free RAM because those heavy games use a lot of it.
So in order to avoid this kind of confusion I'll edit the article to solve this misunderstanding thx for the heads up
Click to expand...
Click to collapse
Cool, thanks for that
Buddy, that guide is awesome written, excellent work. And big thanks for credits - I'm very proud that I could help in that "project" ^^. It's should hit XDA Blog . Cheers .
DiKeJ said:
Buddy, that guide is awesome written, excellent work. And big thanks for credits - I'm very proud that I could help in that "project" ^^. It's should hit XDA Blog . Cheers .
Click to expand...
Click to collapse
I'm the one who have to thank you
People please share your ideas so we can make this guide better!
Can't post in development section, but I think this is very important and torment a lot of people. Temporary solution is for normal user and not perfect. There is a permanent solution, but we can only hope some ROM developers look into this and put the solution to their ROMs.
The "media battery drain on boot" issue is not a VZW SGS3 only problem, it exists in almost all the 4.1.x based ROMs on any kinds of devices. You can search in different sub-forums of XDA to find out. Only in recent, this issue got increasing concern on android googlecode issues page and some project members involved. See here: http://code.google.com/p/android/issues/detail?id=37199. In case you don't want to go through the whole thread, I summarize some important information here:
The reasons causing this issue are twofold:
1. After 4.1.x, the process "android.process.media" will scan every files in your sdcards on boot, this is due to the MTP support (I can't be entirely sure and have no idea why it's necessary). Even with .nomedia in folder, all the files inside are still scanned and indexed, only not shown in galley/ringtones. That's why adding .nomedia file will not help.
2. Even with scanning all files, it shouldn't be that slow. The real problem is the non-optimized matching algorithm for deciding if a file is indexed. The algorithm is slow when dealing with filenames with wildcard character such as "_", and this kind of files commonly exist in photos, cache files of apps etc.
Solution:
An android project member has pointed out that the problem has been mostly fixed in 4.2: https://android.googlesource.com/platform/frameworks/base/+/8ab2dc2f9680307febe997631c2148729f714e3d
But normal users can only wait for ROM developers to merge this fix to their ROMs.
A temporary solution is to look into your sdcards and delete all unnecessary files with name containing wildcard characters, such as "_". Those with media drain issue will find this kind of files very common. Some instant message/social network/maps/gallery apps will cache thumb and media files in this form, as well as the photos taken by camera. Some game data, such as NFS from EA, also contain a large number of such files.
Here is my test and prove:
I used to have about totally 40,000 files in sdcard and extsdcard. After I deleted about 5,000 cache files containing wildcard filename, my reboot indexing time reduced from 18+ mins to 8 mins. I still have about 5,000 wildcard files that I cannot delete, such as photos. The improvement is significant, and I believe if I remove the other 5,000 files, the scanning and indexing time should be similar as in 4.0 and before: around 2 minutes.
Here is a more detailed test: http://rowan.smith.gen.nz/post/37744838003/media-battery-consumption-revisited
Cheers!
I need to wipe two Android Phones that do not have the "encrypt" option. I am selling them very soon so this is important. One phone is running stock Gingerbread, the other is using a custom rom running ICS 4.04.
I attempted a secure wipe on the ICS phone by choosing every wipe option found in TWRP (dalvik, cache,etc), then I did 2 factory resets and flashed a NEW ROM after that. Guess what..? I used the free program "DiskDigger" on my PC and I found THOUSANDS upon THOUSANDS of recoverable files. FULL pictures, not just thumbnails; I found videos, I found zip files, I found voice recordings, I found music, and more!
There is no way in hell I can sell these phones until I know they are CLEAN of my information. What pisses me off is that with iPhone, it's as simple as pressing "Erase All Content And Settings". That takes maybe 5 minutes tops and it works on iPhone's as old as the iPhone 3GS! I thought custom flashing a new rom and wiping cache in TWRP would do the trick but NOPE.
Can anyone help me?
An update for you... I downloaded these two apps and ran them on both phones. Here are the results...
https://play.google.com/store/apps/details?id=com.pinellascodeworks.securewipe&hl=en - Secure Wipe
https://play.google.com/store/apps/details?id=com.aiuspaktyn.secureeraser&hl=en - Secure Eraser
On the stock Gingerbread phone, 3 photos were found by DiskDigger and I was able to preview them and recover them. Recuva found 20 files, the same 3 pictures, plus some overwritten garbage. I ran both apps AGAIN and got the same results, those same 3 photos were still there, intact. So what I then did was click on the photos in Recuva and selected "Secure Overwrite Checked". I ran the scans a THIRD time, Recuva first. It found 15 different files, 11 ignored all labelled as "unrecoverable" or "very poor". Only one photo was from before was found, but there was no preview. I recovered it, but no photo program could open it, so it looks to be successfully overwritten and corrupted.
On the phone running custom ROM ICS: I ran DiskDigger and it found 0 files; Recuva found 3 files after secure wiping. One was in "poor state" and two were in "excellent" state - a .bin file and .M file. I overwrote these files in Recuva and ran the scans a second time. DiskDigger found nothing, Recuva found 3, 14 ignored, all were "unrecoverable".
So I have some peace of mind now. Before running these Secure erase programs, DiskDigger found 99% of the contents on the phone that was running custom ROM ICS. So wiping dalvik cache, other cache, multiple factory resets, and flashing a new ROM did NOTHING!
If anyone has suggestions on other recovery programs, I will do a third check to put my mind at ease.
Wow... very surprised that there is no discussion on this. Do people not care about about the security of their devices?
umirin said:
Wow... very surprised that there is no discussion on this. Do people not care about about the security of their devices?
Click to expand...
Click to collapse
General rule is basically no to sell your old devices and physically destroy them, if you care for privacy. A phone is no different to PC or any other piece of hardware here, so you're either aware of this and don't give/sell your stuff or don't care.
Destroying old equipment is pointless unless you are a career criminal avoiding the police or some other high profile person that a large organization with spend tones on resources on investigate.
Data breaches are far more likely from bad practices during ownership
Quality wipe apps with root access over writing old data multiple times is quite effective..
Greetings,
I am currently working on a 100% Android Marshmallow v6.0.1 variant for the Samsung On5 SM-G550T/1 (T-Mobile).
THIS IS NOT A THREAD ON HOW TO ROOT YOUR PHONE
This thread assumes you have already rooted and installed TWRP on your phone and have basic understanding on to backup and recover your phone.
If you need that sort of help, please see my other thread:
https://goo.gl/jWNVNX
Reasons for Project:
I started this project for two reasons:
- Frustration for the lack of support for an otherwise great phone.
- Stumbling across the Samsung Factory Test Rom doing research for other projects.
This ROM has a a 100% Native Driver Set for Android v6.0.1 on the SM-G550T/1. The driver set is identical for the TMO or MetroPCS variants, but the EFS folder will remain different for each.
I'm going to outright confess that I am not a programmer and this is truthfully the first ROM I am trying to develop on my own. I'm a Project Manager and Software Designer by trade, but I rarely get this deep into ROM developments. I figured it was a good project to take on to learn the nitty griddy of what a truly pure Android Experience looks like. That being said, I'd greatly appreciate any help anyone can contribute and will make all my work freely available to anyone wanting to help provided that everyone participating goes into it with good faith that they have no intent on making substantial gains from this project.
Usage of these ROMs/Files/Programs are subject to the following licenses:
- Google's Android Open Source Project Licnese (AOSP):
https://source.android.com/setup/start/licenses
- Google's Individual Contributor License Agreement:
https://cla.developers.google.com/about/google-individual
- Apache Software License, Version 2.0
http://www.apache.org/licenses/LICENSE-2.0
- Samsung Open Source Release Center (OSRC) License:
http://opensource.samsung.com/reception/
That being said, I believe this remains a good enough device, IMHO, to transition people into Android or to provide to people not requiring a fully featured phone.
KNOX Status:
The Factory Test ROM is mostly clean having all the drivers intact and lacks most Samsung Bloatware "tampering". It *DOES* have some preliminary containers for KNOX installed, but none of it is active and takes up less then 1 MB of total space after cleaning passes to remove as many traces as could be removed without breaking things. It is currently being "managed" by an init.d script that generates the folders. I haven't been able to track down yet.
Known Issues:
- 100% Pure Android Menus.
- Rooted/Super User.
- Sound, Camera, GPS, TMO Modem, Wifi, Bluetooth 100% working.
- 100% Native Tethering.
- Adblocker pre-installed (for both Apps and Websites).
- The smallest amount of KNOX installations outside of Lineage. >1mb of KNOX is present with the only items being present are installer containers.
- I'm trying to track down Init.d files that loads with Android and automatically disables/flushes WIFI.
- By default, the power button is set a 100ms push time to turn off (not show power menu). I'm trying to figure out a work around for this.
- I'm trying to find a compatible Contacts Storage file.
- There is no shutdown menu.
Please note that any released versions of this ROM will have makeshift ways to get around these issues.
Downloads:
Please see the second post in this thread.
How to Install:
#01.) Backup your device.
#02.) Download the zip file for the TWRP backup.
#03.) Unzip the TWRP backup.
#04.) Load the downloaded restore into your TWRP Backup Directory.
#05.) Boot into TWRP Recovery.
#06.) Restore the ROM copied into your TWRP Backup Directory.
#07.) Reboot.
Note: No personal data has been configured.
References:
Update Log:
https://goo.gl/CEGCx9|
Required System Apps for Samsung Phones:
https://goo.gl/emTvgX
Things I Could Use Help On:
- A very good way to figure out what Init.d files are doing what without reading through them.
- A good way to change the PIT so we can move 2 gig from the System Rom into the User Rom space.
- Easy methods for changing key button presses.
- A shutdown menu setup.
- A way to make this into an installer.
Note that all those things I'm working on ALREADY, but suggestions would be helpful.
Thanks in advance for any help anyone offers.
Donations Welcomed:
Dev elopement of this ROM is timely, I appreciate any contributions you wish to provide.
https://goo.gl/esVVqA
DOWNLOAD LINKS:
[2019-03-11] Android (v6.0.1) Build #13 [RC] - Google
https://www.androidfilehost.com/?fid=1395089523397913770
- Note, due to Google Now being installed on this one, I can't configure the home long press as the restart menu.
[2019-03-11] Android (v6.0.1) Build #13 [RC] - Diagnostics
https://www.androidfilehost.com/?fid=1395089523397913771
[2019-03-02] Android [v6.0.0] Build #10F [RC]
https://www.androidfilehost.com/?fid=1395089523397908668
i would love to test this rom
Its been taking a little longer then I expected to get it working correctly --- I've been having trouble tracking down some bugs, but with a little luck, I'll post the Google variant tomorrow.
Here is a "working" version to look at:
https://www.androidfilehost.com/?fid=1395089523397901430
It's a restore for TWRP (not an install).
It has all the aforementioned bugs, but is pretty clean only with a few basic utilities installed on it.
I'm trying to track down a number of things:
How to change the Power Button function:
In my most current build, I have made the power button simply put the device to sleep with a long hold of the home button bringing up the power menu. I can't for the life of me figure out where the power button menu lives at or how to define it.
Normally, you'd go edit /system/usr/keylayout/Generic.kl, however, editing it button 116 (the power button) for "Power" only makes it turn off. I can remap it easily as sleep. I compared several other ROMs who use the exact same parameter.
My current version, I just use an app to remap several of those functions; but I don't feel like that's a "release worthy" fix.
Factory Mode:
I can't figure out how to get this version of the ROM to get out of factory mode. The only real problem this causes is, on bootup, it will display a message saying as such and then disable WIFI and turn off the sound. Both, of which, can be immediately be turned back on. It also disables power saver modes.
At first, I thought this was an Init.d file, but after doing some digging I determined this has to the /efs/factoryapp/factorymode file. I may need to swap elements from another EFS to get this fixed.
Contacts Storage:
This is another one I can't seem to track down, but I have a working idea how to fix it. At current, anything that uses Contact Storage won't work. I wonder if the contact storage I have on the system is simply incompatible for some reason. I'm going to try to pull over those system apps from another working rom.
Storage
I've mapped out all the partitions but am having trouble figuring out how to actually change the partitions. There is a whole 2 GB being wasted on the system partition. I'm actually very surprised that no one has ever released a rom with this fixed.
I've tried using parted, but my ADB Install is messed up something major and I cant track down that problem. Reinstalled ADB hasn't fixed it. Its largely a PC problem on my end; a problem I'm dragging my feat going and trying to fix. This is an issue I REALLY wish I could use PC tools for :-\. I've done these changes a thousand times on Windows based machines, but never on a Linux based OS.
Now that I think about it, maybe I should try doing this from the terminal prompt in TWRP. I just wish the keyboard in TWRP didn't suck :-\.
Other Thoughts:
Beyond those very vexing bugs, I have to honestly say that I feel like this experience on this rom is vastly superior to that of the stock Samsung Experience. Sure, these issues are vexing, but I'm also seeing much less system overhead (CPU usage, RAM usage) with this Rom then anything else outside of Lineage.
Update
Here's an update for everyone who might be interested:
The last couple of week's I spent an ENORMOUS amount of time trying to track down as much as I can to get this ROM to work as intended.
For those interested, I've developed a completely new spreadsheet describing everything that's bloatware versus needed items:
https://goo.gl/emTvgX
This spreadsheet will probably be handy for EVERYONE working on Samsung related devices. When its a little more clean, I'll throw it some place better; but since this is specific towards this device, I'll keep it here for now.
It describes everything in /system/app/ and /system/priv-app/ in Samsung's default install and which of those items are actually needed for a 100% clean Android Experience.
I've also rolled through the architecture and have cleaned a lot of "junk" out of the system. Overall, I've pulled it the system from around 1.3 gb installed all the way down to about 800 mb and still feel confident I can trim more out of it.
I've also made it a point to install as much updated system apps as possible. Its been a game of juggling Google, Samsung and other ROM apps to find what works. In general, there are only one major programs left that are Samsung based in any way and that's the Samsung Phone Service app; which seems like its required to interface with the specific hardware on the phone. I've tracked down a number of native Google teleservice.apk-s and none have worked to date.
I am, sadly, still having the aforementioned problems:
- Contacts won't sync despite being able to connect to the contact services and seeing what backups are available. Manual restores work and updating contacts TO the server works now.
- The Power Button turns off the device immediately. The problem resides in a configuration somewhere that's telling the "Power" function to not bring up the power menu. The power menu is in the system, but appears to be renamed or something. I'm having trouble tracking this down. For documentation sake, in theory you should be able to just go to /system/usr/keylayout/General.kl and edit button 116, but that doesn't work.
- The phone is still locked into "Factory Mode". Various documentation says that if you go to /efs/FactoryData/factorymode and edit the contents to "ON", it should resolve this issue, but it doesn't. I feel that the problem resides in the CSC folder and EFS folder, but I haven't gotten around to testing yet. I suspect if you swap the CSC and EFS folders out and set all the correct permissions it might fix that. As it stands now, however, its only a minor inconvenience.
Overall, there's a lot more junk to sift through on the last two problems. The first problem I am kind of stumped on.
If you want to download the ROM and look at it or run it, you can follow the below link. It's currently setup with my "trouble shooting environment" making key places to tinker with easily accessible.
DOWNLOAD HERE:
https://goo.gl/MuPqE3
@LighthammerX
Im very grateful for this site where we can come and learn from one another. I just wanted to say thanks for taking time to work on this device and then sharing your findings. I've been using my on5 for 2 months now after other device died. I'm in the process of moving now but once I'm done with that I'm going to scope out this bad boy and see if I can figure out a few things. Appreciate you sharing your information with us all. Cheers.
Sent from my on5ltemtr using XDA Labs
Thanks. I'm glad to see there's some interest here. IMHO, with the right setup, this little phone is actually a very nice device today.
I actually took a lot of what I learned from hack this ROM apart and applied it to Super Starz to get it running a lot cleaning as my daily runner until/if I get these few bugs figured out.
Personally, I think the most valuable thing I've been learning is just how bloated Samsung Devices truly are out of the box.
I'm going to go ahead and dump my progress log here too so you guys can see what I've been toiling with in hopes someone has some specific feedback on issues and if I am in the right place or not:
https://goo.gl/CEGCx9
As of the writing of this post, I'm virtually confident any problems I am experiencing has nothing to do with /efs/ or /system/csc/.
I've found some inconsistencies in /etc/ and in a few other directories in /system/.
I still wonder if there isn't a init.d file I haven't tracked down yet, but personally I find folder compares faster and easier to try to normalize then I do init.d files.
When it comes to folder compares, I can do a fast reboot and see if things break. When it comes to lines of code, I have to do a bulk of edits, reboot and hope for the best.
Just as an FYI, I plan on completely rewriting the OP when things are at a place where things work.
For anyone following the thread, the Downloads Section has been updated.
This seems really interesting ? I've been trying to find a good ROM for a while with little success, so hopefully this might be the one. I just have one question: what are the differences between the Google and Diagnostics versions of this ROM?