Showing posts with label Jelly Bean. Show all posts
Showing posts with label Jelly Bean. Show all posts
Friday, March 29, 2013
Labels:
Android
,
Jelly Bean
UPDATE: After re-adding the email settings, it no longer drains my battery. It may be different for other phones, so your mileage may vary. Try re-adding the email account to see what happens. Good luck!
Original post:
On Tuesday night, I received a notification that Verizon published the 4.2.2. update for the Samsung Galaxy Nexus. Having read about the features, I was excited to install the update immediately. The very first thing I noticed was that the phone began getting very hot. I rebooted my phone just before I went to bed, deciding that I would deal with it on Wednesday.
Wednesday was a day of me searching for outlets to keep my phone charged. Within an hour of removing the charging cable, my phone was down to around 10% battery. Looking at the battery usage, "Exchange Services" was eating over 60%! I tried various settings to adjust the sync intervals, all to no avail. Reluctantly, I then removed my corporate email account. I noticed an immediate difference in temperature - or should I say lack thereof; it was no longer burning hot! Monitoring the phone all day Thursday, I can confirm it seems that was the fix.
So, if anyone out there is running a Verizon SCH-i515 Samsung Galaxy Nexus, and your battery drain is as rampant as mine was, delete/remove your corporate email profile.
I haven't tried re-adding it yet. I'll give that a shot Friday and update the post with the test results.
Read More
Verizon's Android 4.2.2 Update and Battery Drain
Original post:
On Tuesday night, I received a notification that Verizon published the 4.2.2. update for the Samsung Galaxy Nexus. Having read about the features, I was excited to install the update immediately. The very first thing I noticed was that the phone began getting very hot. I rebooted my phone just before I went to bed, deciding that I would deal with it on Wednesday.
Wednesday was a day of me searching for outlets to keep my phone charged. Within an hour of removing the charging cable, my phone was down to around 10% battery. Looking at the battery usage, "Exchange Services" was eating over 60%! I tried various settings to adjust the sync intervals, all to no avail. Reluctantly, I then removed my corporate email account. I noticed an immediate difference in temperature - or should I say lack thereof; it was no longer burning hot! Monitoring the phone all day Thursday, I can confirm it seems that was the fix.
So, if anyone out there is running a Verizon SCH-i515 Samsung Galaxy Nexus, and your battery drain is as rampant as mine was, delete/remove your corporate email profile.
I haven't tried re-adding it yet. I'll give that a shot Friday and update the post with the test results.
Tuesday, November 27, 2012
Labels:
Android
,
Google
,
Jelly Bean
Android 4.2 Security: App Signatures
It seems to be common knowledge now among security professionals that the Google Play Store is infiltrated with malware. In an attempt to control the malware surge, Google is stepping up its efforts to clean house via security updates in 4.2.
One central mechanism appears to be signature-based recognition of apk files. When an apk is loaded on a device, the app signature (most likely just a file hash) is uploaded to Google's servers for a reputation check. It's cross-checked against Google's list of known and reported malware, and if found to be bad, the server sends the response to the Android Package Installer to prevent installation. If the reputation states that the app requires suspicious permissions, it'll ask you to confirm that you're comfortable with installing it and list what access it's requesting. ComputerWorld has a more in-depth explanation, for interested parties. The only downside to all this is that unless rooted, we all have to wait on our carriers to release the update through theirvetting marketing process.
This highlights another concept that's rapidly spreading across anyone getting into the software security space: leveraging the user base to protect the cloud. I'll post another note expanding on that concept soon.
Read More
One central mechanism appears to be signature-based recognition of apk files. When an apk is loaded on a device, the app signature (most likely just a file hash) is uploaded to Google's servers for a reputation check. It's cross-checked against Google's list of known and reported malware, and if found to be bad, the server sends the response to the Android Package Installer to prevent installation. If the reputation states that the app requires suspicious permissions, it'll ask you to confirm that you're comfortable with installing it and list what access it's requesting. ComputerWorld has a more in-depth explanation, for interested parties. The only downside to all this is that unless rooted, we all have to wait on our carriers to release the update through their
This highlights another concept that's rapidly spreading across anyone getting into the software security space: leveraging the user base to protect the cloud. I'll post another note expanding on that concept soon.
Subscribe to:
Posts
(
Atom
)
