Related
Was so looking forward to this. I have some books in Archive that simply fail to download to the HT7, others can take ages to download. Tried removing the app, de-registering on Amazon and re-installing, same issue. Anyone else seeing this ?
Ian
So far my books haved synced fine over Wi-fi. Are you using Wi-Fi or 3G? Do you get any error message?
I'm only attempting this over the WiFi network, it eventually gives up and says failed to download, try again.
The only real possible causes for failed downloads would be loosing wireless connection or Closing the application before the download has completed.
Well I thought this but the iPhone beside me downloads fine over wifi as do my various laptops with the Kindle app installed.
Maybe try de-registering and uninstalling/Reinstalling one more time? Don't know what else to suggest fella.
This is off the amazon website hence why i've quoted it.
Amazon Website said:
Book appears in Kindle Library and Archived Items but download failed.
Possible causes:
Lost wireless connection.
Application closed before download completed.
Confirm wireless connection and retry download
Check wireless data service or Wi-Fi is enabled on the device and that status indicators show an active connection. A wireless connection must be active.
Launch Kindle for Android.
Tap the Menu button, then select "Archived Items."
Select the desired title from the "Archived Items" list.
Leave your wireless connection and Kindle for Android app running until the download completes--do not leave the application.
If your wireless connection is interrupted and the download fails, attempt the steps above again when your wireless connection is re-established and active long enough to complete the download.
Confirm disk space is available
If you see the error message: "There is not enough space available on the media card," free up disk space by deleting videos, pictures, applications, and/or other files you no longer need.
Book is missing or does not appear in Archived Items list.
Possible causes:
Lost wireless connection.
Kindle for Android registered to wrong account.
Confirm wireless connection and relaunch application
Close the Kindle for Windows Phone application.
Check wireless data service or Wi-Fi is enabled on the device and that status indicators show an active connection. A wireless connection must be active.
Launch Kindle for Windows Phone and log in to the Amazon account you used to purchase the book you wish to download if prompted.
Scroll to the menu section in the panorama view and select "Sync" and wait for the sync to complete.
Scroll back to the home section in the panorama view and select “Archived Items.”
If the title still does not appear, follow the steps below to re-register.
Re-register the application
Launch Kindle for Windows Phone on your device.
Scroll to the menu section of the panorama view.
Tap settings.
(If already signed in)
Tap the “deregister this device” button.
Tap “deregister” button.
Enter the same e-mail address and password for your Amazon.com account and select "Register."
Click to expand...
Click to collapse
Edit: Lol just noticed it says Android when talking about books not being in archived items even though its the WP rouble page.
http://www.amazon.com/gp/help/customer/display.html?ie=UTF8&nodeId=200590160
I appreciate the response, thanks. Will try a few things and report back here
konnexion said:
I appreciate the response, thanks. Will try a few things and report back here
Click to expand...
Click to collapse
No problem, Maybe try the Feedback and Support feature which is within the app to send an e-mail.
Case opened with Amazon Kindle Support
Please keep us apprised of the situation.
konnexion said:
I'm only attempting this over the WiFi network, it eventually gives up and says failed to download, try again.
Click to expand...
Click to collapse
Hate to cross post, but I'm having a similar issue on my android device (nook color), as well as two windows pc's. I don't think this issue is isolated to one platform.
Thanks for info. Amazon are still investigating this issue
solved the same problem
I had the same problem. I accessed my app manager and changed the kindle app location from phone to sd card. After that all my queued books downloaded. I think the problem was not enough memory on my phone, or reserved memory on the phone and kindle auto DLs to location the app is installs. (could be wrong, but solved the problem anyway) hope this helps
I have been successfully using the Verizon FIOS remote control app to control my TV FIOS STB and it is much nicer to use than the standard IR remote.
To get it to work originally using a nightly (circa 128), I had to persuade the Nook that it had a phone number as this is registered against one set in the STB. I did this by going into Settings/Call Settings/Additional Settings. This gives a network or SIM card error but when OK'd allow me to manually enter a phone number which then worked fine and continued to work through many nightly updates.
Something has now changed (I am currently on nightly 200) as I find that I have to re-register the FIOS app almost daily to get it to work.
On checking I find that the Phone Number setting gets lost periodically and set back to Unknown and I have to manually enter it again.
Does anybody know whether CM7 behaviour has changed with respect to the storage of the Phone Number? I realise it would normally be on a SIM, but it does seem to stick around for quite a while on the Nook before getting lost.
Any luck with this? I've been trying to figure out a way to do this for a while. I am unable to set a number as you described as all settings are greyed out. I'm also on nightly 200+. Seems like there would be a system file we could edit to fake the number, or something like that. Was thinking about setting up a SIP account to try it, but I doubt that will work.
dgibb2000 said:
Any luck with this? I've been trying to figure out a way to do this for a while. I am unable to set a number as you described as all settings are greyed out. I'm also on nightly 200+. Seems like there would be a system file we could edit to fake the number, or something like that. Was thinking about setting up a SIP account to try it, but I doubt that will work.
Click to expand...
Click to collapse
I have made some progress investigating this but have not got a final solution yet.
First, I can set my phone number up even though it is not a phone. I go into Settings, Call Settings, Additional Settings. The screen blurs and brings up a dialog box saying Call settings Error - Network or SIM card error. If I OK that then I see 3 menu items. The first 2 are grayed out but the 3rd "My Phone Number" is enabled. I select that and can enter a Phone Number. Are you saying you get the error and then all 3 options are grayed out?
Once entered I can view the Phone number via Settings, About Tablet, Status.
So far so good. The phone number setting does not normally survive a reboot, and also typically reverts to Unknown after a couple of days even without a reboot.
I have traced the Phone number setting to be stored in com.android.phone_preferences.xml which is in /data/data/com.android.phone/shared_prefs
But when the Phone number disappears it doesn't disappear from this file so there is some more complex interaction with trying to read a non-existent SIM first. So far I have traced the code involved to MyPhoneNumber.java and MSISDNEditPreference.java which are in the CyanogenMod-android_packages_apps_Phone-5d2764c.
I am still working on understanding this to see if there is some work-around to make the setting stick better. Currently I just have to check the phone number manually and set it again when it disappears.
Hmmm. When I go into call settings, all settings are greyed out except for internet call settings at the very bottom. I see the additional settings field you are speaking of but as its greyed out nothing happens if I click it. Weird.
dgibb2000 said:
Hmmm. When I go into call settings, all settings are greyed out except for internet call settings at the very bottom. I see the additional settings field you are speaking of but as its greyed out nothing happens if I click it. Weird.
Click to expand...
Click to collapse
Yes. That is strange. All my settings in Call Settings are enabled even though most are inapplicable. I don't think I have done anything to explicitly enable them and I'm on a standard Nightly 240 with the updated SystemUI.apk which turns off the phone signal bars. But I've never had these greyed out with any nightly build before.
Anybody else comment on whether their whole Call settings are enabled / disabled?
There is also a setting in build.properties in the system folder with a key called
keyguard.no_require_sim
I think this may have effect on how the OS treats calls which access the SIM. On my system this is currently set to 1. I might try playing with other values like true, 0 to see what effect that has.
Another theory as to why your call settings may be greyed out is that it they may get disabled in airplane mode.
Now this could be an issue even if you have set and subsequently cleared airplane mode as I believe the airplane mode setting doesn't go away entirely and can cause problems.
There is a command line way of clearing this setting completely which I did once when I set airplane mode on. Search for something like airplane sqlite to find the instructions.
That was it. I was stuck in airplane mode, and must have been for a long time. I used Android Assistant to clear the setting and it worked. I'm able to set my number and use fios mobile remote now! Thanks for your help.
Where did you get that updated systemui.apk to clear the cell signal bars? Now that I got the airplane mode off I have the signal strength there for no reason.
I got the SystemUI.apk from here
http://forum.xda-developers.com/show...60542&page=547
I just replaced the one in system/app. If you overwrite then you might get status bar forced close but a system reboot will sort that out and I haven't had signal bars since.
I've now put this in a zip that I can use to install after any nightly update I do as I've now found there is a wifi patch to deal with any remaining SOD issues although I haven't had one of those for a long time now.
Hopefully this stuff will get put into the main build before too long.
Looks like your link got clipped. Getting a page not found error.
Also, do you have any instructions on how to put the .apk into a zip for re-install after you do an upgrade? I'm assuming its not as easy as just ziping the file up?
Updated link
http://forum.xda-developers.com/showthread.php?t=960542&page=547
Yes. It is as easy as zipping the file up, but you have to create a matching folder structure to determine where the file goes. So in the case of the SystemUI file you create a folder called system containing a folder called app, put the file in the app folder and zip it so that system is in the root of the zip.
Correction: I thought that zip method was working but it wasn't. I had manually put the files in anyway and that worked OK. Then I was testing the zip, but it was actually failing.You need to put the files in a zip with the meta-inf etc. I think this link gives instructions
http://alldroid.org/default.aspx?g=posts&t=855
No. That doesn't work either as it uses an older method of scripting no longer supported. Apparently it needs to use Edify scripting now. It looks like some people add files to the gapps package, but I'm not clear yet whether it has to be re-signed, and I don't particularly want to redo gapps just to do this minimal patch.
I think I now understand how to produce an update zip that works.
I first took a gapp zip and stripped out all the existing files under system leaving the meta-inf alone. I put in the patch files in the appropriate folders under system. I then modified the updater-script in the meta-inf tree to just mount system, run package_extract_dir("system", "/system"); and unmount system with changes to the ui_print
I then signed the zip using the win-sign utility available here
http://forum.xda-developers.com/showthread.php?t=629151&highlight=sign+zip+files
I tried this out by first updating to nightly 246 and then applying my patch containing the SystemUI and the wifi driver that fixes SOD and that seemed to work OK.
Hi,
I was using this phone fine, including location services.
Since 2 or 3 Months the network based location service does not work for foreign apps. For none of them. Only google maps still can find my location. All other apps need working GPS signal, so I need to go outdoors.
This is particularly annoying with apps like MyTaxi that require you to have a verified position (hand picked position does not work).
Can anyone tell me what has gone wrong ?
Why did the behaviour of the phone change ?
How do I fix this ?
chippy
SOLVED !
SOLVED :
A bit fiddly to go through the procedure, but I solved it with this :
http://forum.xda-developers.com/showpost.php?p=9576852&postcount=108
Instead " select name from main; " I used " select name from main order by name asc; " this gets a orderes list and all entries beginning with "url:" are together, easier to find the correct entry.
[Fixed] System freeze after playing with "secondary monitor" in Developer options
Hey, I just played around in the developer options and wanted to find out what "second monitor" does.
As far as I remember I set it to 480p and the system froze immdediately.
Rebooting the device shows the bootloader but the animation will stop soon.
I am using LineageOS 14.1 on my Sam S3 mini.
I was able to connect via adb - may be I can fix the problem by myself if someone can tell me where these settings are stored.
Some research here and with google gave no useful results so I just asked here.
--- Edit:
I was able to fix the problem in file /data/system/users/0/settings_global.xml which is not were I expected it to be (Google told me different).
Having ran NetGuard in logging mode for a few days now I've noticed that many of Samsung's in-built services are contacting web services associated at multiple DNS subdomains under:
- *.360.cn
- *.cloud.360safe.com
A lot of them on unsecured HTTP port 80 (some go via HTTPS port 443).
Services I've observed this behaviour so far are:
- Samsung ApexService
- ANT+ HAL Service
- Application installer (com.sec.android.preloadinstaller)
- Assistant Menu
- AirCommandManager (com.samsung.android.aircommandmanager)
- Plus too many other default services to list (most of which cannot be disabled)
Phone's running on stock unbranded SM-N960F build number PPR1.180610.011.N960FXXU2CSA2.
I've scanned the phone using bundled Device Care's McAfee security scan with no findings.
Has anyone else observed this behaviour?
sengork said:
Having ran NetGuard in logging mode for a few days now I've noticed that many of Samsung's in-built services are contacting web services associated at multiple DNS subdomains under:
- *.360.cn
- *.cloud.360safe.com
A lot of them on unsecured HTTP port 80 (some go via HTTPS port 443).
Services I've observed this behaviour so far are:
- Samsung ApexService
- ANT+ HAL Service
- Application installer (com.sec.android.preloadinstaller)
- Assistant Menu
- AirCommandManager (com.samsung.android.aircommandmanager)
- Plus too many other default services to list (most of which cannot be disabled)
Phone's running on stock unbranded SM-N960F build number PPR1.180610.011.N960FXXU2CSA2.
I've scanned the phone using bundled Device Care's McAfee security scan with no findings.
Has anyone else observed this behaviour?
Click to expand...
Click to collapse
I haven't looked at this as closely as you have,but,I'm guessing it's all tied-in from the Device Maintenance section of the phone.
The name of the company Samsung is currently in bed with is QIHOO:
https://en.wikipedia.org/wiki/Qihoo_360
https://seekingalpha.com/article/4165136-cheetah-mobile-lost-samsung-relevant-risks
Remember/heard of Cheetah Mobile (of Clean Master infamy) ?
https://www.prnewswire.com/news-rel...mobile-security-and-innovation-300043298.html
Well,that's who used to be in partnership w/Samsung & the Device Maintenance aka built-in Clean Master to most,if not all Samsung mobile products.
Fast-Forward to present day & we still have the crapware on our phones,likely scraping info & selling it to anyone interested.
Now,it's just with another company,presumably one with friendlier terms for Samsung.
As you've probably noticed,you can't fully disengage/disable/deny all permissions here,less root (or ADB disabling/package disabler apps).
At least you have a phone that's rootable & can cruise the ROM scene for one that leaves this crap off the phone.
If root isn't an option:
Set up your phone & apps,fine-tune as you like for battery optimization on a per app basis/permissions/etc....
Then,either via ADB or a package disabler,disable the apps responsible for the crapware,especially the ones related to Device Maintenance.
https://forum.xda-developers.com/ga...laxy-note-9-bloatware-removal-thread-t3857508
Follow the link in the OP to the S9/S9+ forum/thread,it gives a better idea of what each .apk actually is/ties into.
Here's the app I use to disable crapware/things I don't use:
https://play.google.com/store/apps/details?id=com.wakasoftware.appfreezer
As to which apps to disable,the S9/S9+ thread,while not an exact match,should give you info on what to disable to stop the phone from pinging the 360 mothership & hopefully,not having any ill effects on the apps you want to keep on-board.
If you want a better idea of how each app is interconnected throughout the phone,use these two apps to take a look:
https://play.google.com/store/apps/details?id=com.ubqsoft.sec01
SD Maid (Pro):
https://play.google.com/store/apps/details?id=eu.thedarken.sdm&hl=en_US
(See the App Control & file manager sections of SD Maid for detailed app info).
Anyhoo,back to curbing the nonsense:
Whichever method you use to disable,should you choose to do so,start with this one:
com.samsung.android.lool (Device Maintenance).
This will make the entire Device Maintenance section inaccessible as well.
That is why I suggest disabling vs outright uninstalling (which necessitates a factory reset to get it back).
You may need to access Device Maintenance for whatever reason from time to time,hence the recommendation for disabling vs uninstalling.
Continue monitoring for a day or so & see if the pinging to the Mothership subsides,or hopefully puts a full-stop to it.
Please keep us updated on what,if any actions you take w/the results. :good:
Excellent overview, it's quite an eye opener thanks for the info.
I've disabled and force-stopped "com.samsung.android.lool" (amongst other junkware) and so far NetGuard hasn't shown a single network log entry to any of the 360 domains. I've uninstalled all 4 Facebook packages. Continuing to monitor this closely. My thought is that I can re-enable "com.samsung.android.lool" from time to time whenever maintenance is needed and then disable it again. Even better Adhell3 might be useful for blocking "com.samsung.android.lool" network attempts whilst retaining it for device management purposes however I haven't tried this yet.
For reference, here is my current list of disabled packages:
Code:
package:com.monotype.android.font.rosemary
package:com.samsung.android.app.ledcoverdream
package:com.sec.android.widgetapp.samsungapps
package:com.samsung.android.app.galaxyfinder
package:com.samsung.svoice.sync
package:com.cnn.mobile.android.phone.edgepanel
package:com.samsung.android.easysetup
package:com.samsung.android.provider.stickerprovider
package:com.samsung.android.app.sbrowseredge
package:com.samsung.android.rubin.app
package:com.sec.android.cover.ledcover
package:com.samsung.faceservice
package:com.monotype.android.font.foundation
package:com.sec.android.widgetapp.easymodecontactswidget
package:com.samsung.android.app.settings.bixby
package:com.sec.android.app.billing
package:com.samsung.android.app.selfmotionpanoramaviewer
package:com.samsung.android.game.gamehome
package:com.samsung.daydream.customization
package:com.sec.enterprise.knox.attestation
package:com.samsung.systemui.bixby2
package:com.dsi.ant.service.socket
package:com.microsoft.skydrive
package:com.samsung.SMT
package:com.samsung.android.drivelink.stub
package:com.android.hotwordenrollment.xgoogle
package:com.samsung.android.sm.devicesecurity
package:com.dsi.ant.sample.acquirechannels
package:com.samsung.android.aircommandmanager
package:com.samsung.android.bixby.service
package:com.samsung.android.smartface
package:com.android.egg
package:com.samsung.android.emojiupdater
package:com.samsung.android.bixby.agent
package:com.android.printspooler
package:com.android.hotwordenrollment.okgoogle
package:com.samsung.android.hmt.vrsvc
package:com.samsung.storyservice
package:com.android.dreams.basic
package:com.android.bips
package:com.samsung.android.game.gametools
package:com.samsung.android.app.simplesharing
package:com.samsung.android.service.peoplestripe
package:com.samsung.android.da.daagent
package:com.dsi.ant.plugins.antplus
package:com.samsung.android.app.taskedge
package:com.google.android.webview
package:com.samsung.android.app.mirrorlink
package:com.dsi.ant.server
package:com.samsung.android.allshare.service.fileshare
package:com.samsung.android.universalswitch
package:com.sec.android.app.apex
package:flipboard.boxer.app
package:com.google.android.printservice.recommendation
package:com.monotype.android.font.chococooky
package:com.android.dreams.phototable
package:com.samsung.android.bixbyvision.framework
package:com.samsung.android.game.gos
package:com.android.wallpaper.livepicker
package:com.samsung.android.beaconmanager
package:com.sec.enterprise.mdm.services.simpin
package:com.samsung.android.stickercenter
package:com.samsung.android.bixby.wakeup
package:com.samsung.android.samsungpass
package:com.samsung.android.spayfw
package:com.linkedin.android
package:com.samsung.android.lool
package:com.samsung.android.knox.analytics.uploader
package:com.samsung.android.sm.policy
package:com.sec.android.emergencylauncher
package:com.samsung.android.visionintelligence
package:com.samsung.android.app.watchmanagerstub
package:com.samsung.android.svoiceime
package:com.samsung.android.mateagent
package:com.enhance.gameservice
package:com.google.vr.vrcore
package:com.hiya.star
package:com.sec.enterprise.knox.cloudmdm.smdms
package:com.samsung.android.app.appsedge
package:com.samsung.android.samsungpassautofill
package:com.monotype.android.font.cooljazz
package:com.samsung.android.allshare.service.mediashare
package:com.samsung.android.app.clipboardedge
package:com.samsung.android.app.motionpanoramaviewer
package:com.samsung.android.bio.face.service
package:com.samsung.android.bixby.agent.dummy
sengork said:
Excellent overview, it's quite an eye opener thanks for the info.
I've disabled and force-stopped "com.samsung.android.lool" (amongst other junkware) and so far NetGuard hasn't shown a single network log entry to any of the 360 domains. I've uninstalled all 4 Facebook packages. Continuing to monitor this closely. My thought is that I can re-enable "com.samsung.android.lool" from time to time whenever maintenance is needed and then disable it again. Even better Adhell3 might be useful for blocking "com.samsung.android.lool" network attempts whilst retaining it for device management purposes however I haven't tried this yet.
For reference, here is my current list of disabled packages:
Code:
package:com.monotype.android.font.rosemary
package:com.samsung.android.app.ledcoverdream
package:com.sec.android.widgetapp.samsungapps
package:com.samsung.android.app.galaxyfinder
package:com.samsung.svoice.sync
package:com.cnn.mobile.android.phone.edgepanel
package:com.samsung.android.easysetup
package:com.samsung.android.provider.stickerprovider
package:com.samsung.android.app.sbrowseredge
package:com.samsung.android.rubin.app
package:com.sec.android.cover.ledcover
package:com.samsung.faceservice
package:com.monotype.android.font.foundation
package:com.sec.android.widgetapp.easymodecontactswidget
package:com.samsung.android.app.settings.bixby
package:com.sec.android.app.billing
package:com.samsung.android.app.selfmotionpanoramaviewer
package:com.samsung.android.game.gamehome
package:com.samsung.daydream.customization
package:com.sec.enterprise.knox.attestation
package:com.samsung.systemui.bixby2
package:com.dsi.ant.service.socket
package:com.microsoft.skydrive
package:com.samsung.SMT
package:com.samsung.android.drivelink.stub
package:com.android.hotwordenrollment.xgoogle
package:com.samsung.android.sm.devicesecurity
package:com.dsi.ant.sample.acquirechannels
package:com.samsung.android.aircommandmanager
package:com.samsung.android.bixby.service
package:com.samsung.android.smartface
package:com.android.egg
package:com.samsung.android.emojiupdater
package:com.samsung.android.bixby.agent
package:com.android.printspooler
package:com.android.hotwordenrollment.okgoogle
package:com.samsung.android.hmt.vrsvc
package:com.samsung.storyservice
package:com.android.dreams.basic
package:com.android.bips
package:com.samsung.android.game.gametools
package:com.samsung.android.app.simplesharing
package:com.samsung.android.service.peoplestripe
package:com.samsung.android.da.daagent
package:com.dsi.ant.plugins.antplus
package:com.samsung.android.app.taskedge
package:com.google.android.webview
package:com.samsung.android.app.mirrorlink
package:com.dsi.ant.server
package:com.samsung.android.allshare.service.fileshare
package:com.samsung.android.universalswitch
package:com.sec.android.app.apex
package:flipboard.boxer.app
package:com.google.android.printservice.recommendation
package:com.monotype.android.font.chococooky
package:com.android.dreams.phototable
package:com.samsung.android.bixbyvision.framework
package:com.samsung.android.game.gos
package:com.android.wallpaper.livepicker
package:com.samsung.android.beaconmanager
package:com.sec.enterprise.mdm.services.simpin
package:com.samsung.android.stickercenter
package:com.samsung.android.bixby.wakeup
package:com.samsung.android.samsungpass
package:com.samsung.android.spayfw
package:com.linkedin.android
package:com.samsung.android.lool
package:com.samsung.android.knox.analytics.uploader
package:com.samsung.android.sm.policy
package:com.sec.android.emergencylauncher
package:com.samsung.android.visionintelligence
package:com.samsung.android.app.watchmanagerstub
package:com.samsung.android.svoiceime
package:com.samsung.android.mateagent
package:com.enhance.gameservice
package:com.google.vr.vrcore
package:com.hiya.star
package:com.sec.enterprise.knox.cloudmdm.smdms
package:com.samsung.android.app.appsedge
package:com.samsung.android.samsungpassautofill
package:com.monotype.android.font.cooljazz
package:com.samsung.android.allshare.service.mediashare
package:com.samsung.android.app.clipboardedge
package:com.samsung.android.app.motionpanoramaviewer
package:com.samsung.android.bio.face.service
package:com.samsung.android.bixby.agent.dummy
Click to expand...
Click to collapse
:good: THX for the update,much appreciated! :good:
I was gonna post this in a bit (just noticed it myself this afternoon,LOL) ,but,it looks like you have added the other two .apks to your disabled list:
https://forum.xda-developers.com/showpost.php?p=78103170&postcount=123
It'a a shame the mfgs aren't required to be more up-front & state ,in common use language where the print is larger than a gnat's ass, the exact nature of the .apks & even more control over the services installed on them.
KOLIOSIS said:
It'a a shame the mfgs aren't required to be more up-front & state ,in common use language where the print is larger than a gnat's ass, the exact nature of the .apks & even more control over the services installed on them.
Click to expand...
Click to collapse
The closest to a manufacturer application list I came across was:
- https://support.samsungknox.com/hc/en-us/articles/115015195728-Common-Criteria-Mode
- For example https://docs.samsungknox.com/CCMode/N960F_O.pdf
This seems to relate to computer security certification known as Common Criteria:
- https://en.wikipedia.org/wiki/Common_Criteria
So the dial home behaviour seems to have passed this security certification (or perhaps the network flows were not part of the certification process). We can only guess...
I've had to reenable the following items to get APK installs to function (either through Play Store or locally stored APKs):
Code:
com.samsung.android.sm.policy
com.samsung.android.sm.devicesecurity
https://forum.xda-developers.com/ga...val-thread-t3857508/post78744845#post78744845
Continuing to monitor with NetGuard. So far ~1hr I haven't seen the packets repeat.
sengork said:
I've had to reenable the following items to get APK installs to function (either through Play Store or locally stored APKs):
https://forum.xda-developers.com/ga...val-thread-t3857508/post78744845#post78744845
Continuing to monitor with NetGuard. So far ~1hr I haven't seen the packets repeat.
Click to expand...
Click to collapse
IIRC,something like this was mentioned in the S9/S9+ debloat thread.
I didn't mention it earlier as you hadn't reported any issues,but,glad you were able to figure it out/find the same info I'd stumbled upon.
Well after a day of usage I can say that battery life is poorer without "com.samsung.android.lool". I've enabled it again now and blocked its domains via Adhell 3:
Code:
360.cn
360safe.com
*.360.cn
*.360safe.com
Furthermore I have disabled its WiFi and Mobile network access in Adhell 3. However this block is bypassed whenever applications using Android's native VPN facility are switched on so its not absolutely fool proof. Similar blocking can be done using NetGuard itself as long as you keep it switched on and filtering continuously.
I'll keep an eye on which other domains it attempts to contact.
sengork said:
Well after a day of usage I can say that battery life is poorer without "com.samsung.android.lool". I've enabled it again now and blocked its domains via Adhell 3:
Code:
360.cn
360safe.com
*.360.cn
*.360safe.com
Furthermore I have disabled its WiFi and Mobile network access in Adhell 3. However this block is bypassed whenever applications using Android's native VPN facility are switched on so its not absolutely fool proof. Similar blocking can be done using NetGuard itself as long as you keep it switched on and filtering continuously.
I'll keep an eye on which other domains it attempts to contact.
Click to expand...
Click to collapse
How much of a difference in battery life are we talking about?
It felt to be about 20%. Is Pie without Device Maintenance expected to put applications to sleep? I am guessing sleep is the major factor here (opposed to cleaning up caches and other storage capacity functions of Device Maintenance app).
sengork said:
It felt to be about 20%. Is Pie without Device Maintenance expected to put applications to sleep? I am guessing sleep is the major factor here (opposed to cleaning up caches and other storage capacity functions of Device Maintenance app).
Click to expand...
Click to collapse
I would like to think so,hoping Device Maintenance isn't ingrained to the level where it breaks the native Doze feature in Android.
JMHO,Device Maintenance seems to be just like Clean Master,running on top of Android/counterproductive,putting a hat on a hat,so to speak,LOL.
I haven't had a Nexus device since the N6 & never had a Pixel,but,I'm pretty sure none of 'em have DM..................................
Whenever I decide to update to Pie,I'm going to continue as I am now:
Battery Optimize all apps that I don't rely on for auto-updating or push notifications & then disabling Device Maintenance.
If something starts acting up,only then do I re-enable DM,take a look at Battery Optimizing for whatever is affected & again,disabling DM.
Guessing you've just recently updated to Pie.......
If it were me,I'd continue to disable DM & give the new OS upgrade a week or so,see what your battery life looks like then.
Battery life loss could be due to some user-installed apps that aren't playing nice w/Pie & not due to DM being disabled.
You will find the logo or text "powered by 360" on storage screen in Samsung device management app.
KOLIOSIS said:
Battery Optimize all apps that I don't rely on for auto-updating or push notifications & then disabling Device Maintenance.
If something starts acting up,only then do I re-enable DM,take a look at Battery Optimizing for whatever is affected & again,disabling DM.
Click to expand...
Click to collapse
I have taken your advise a few weeks ago and have concluded that removing DM whilst manually optimising all individual apps has resulted in no battery loss (in fact it has probably improved but this is within a margin of error). Thanks for your guidance.
Unless you need to connect to a Chinese domain for whatever reason, just block *. cn for good and forever about it.
hello guys i have bought galaxy note 9 in China and there is not preinstalled google play store app...
can anyone tell me how to install safely ))?? thank you ...
hey thanks for your attention but i dont need to access i have vpn i know how to access i want to know how to install because it is not installed so do you have some ideas ?))) how to do it
sandro comaia said:
hey thanks for your attention but i dont need to access i have vpn i know how to access i want to know how to install because it is not installed so do you have some ideas ?))) how to do it
Click to expand...
Click to collapse
Just side-load this .apk & you should be good to go:
https://www.apkmirror.com/apk/googl...5-22-all-0-pr-254908059-android-apk-download/
Was original poster was the only one who had this issue?
Is this a samsung thing or all androids?
Can this be a security risk?
There was a link to the s9 bloatware thread but it doesn't work
https://forum.xda-developers.com/ga...laxy-note-9-bloatware-removal-thread-t3857508
Says 404 not found for me
Nameduser6 said:
Was original poster was the only one who had this issue?
Is this a samsung thing or all androids?
Can this be a security risk?
There was a link to the s9 bloatware thread but it doesn't work
https://forum.xda-developers.com/ga...laxy-note-9-bloatware-removal-thread-t3857508
Says 404 not found for me
Click to expand...
Click to collapse
Should be only Samsung phones. Interestingly i haven't seen it dial home since my original post and up until i uninstalled the Device Care package. Samsung might have changed the domains the tool dials home to.
Sent from my SM-N960F using Tapatalk