Hi Folks
[UPDATE]This is not the only way of getting Dongle's working on the N7, If widgets are your thing and you don't feel confident working with system files etc then you may be better served using the ppp widget form draisberghof.de, these are the folks who piratically wrote the book on getting dongles working on linux and by extension android and members have reported success using it. See this thread [Nexus7 UMTS-Stick extern working] in the general section for the initial find.
[UPDATE]This mod has seen success on ZTE Dongles ( Thanks To NexusPhreak ) See the supported devices list in the second post for a list of the latest tested devices
[UPDATE]It turns out this mod is good for CDMA Dongles as well as GSM - It needs a slight tweak. See this post [ Post #76 ] for details ( Thanks to mailbinoy )[UPDATE]
IMPORTANT: THIS IS A WIP AND NOT READY FOR PRIME TIME - IF YOU HAVE NEVER USED FASTBOOT, ADB, DON'T UNDERSTAND THE FIRST THING ABOUT NETWORKING OR HAVE NEVER SEEN A BASH PROMPT THEN THIS IS PROBABLY NOT FOR YOU
TROUBLESHOOTING: IF YOU ARE HAVING PROBLEMS PLEASE READ THE TROUBLESHOOTING SECTION IN THE SECOND POST - THE MORE INFORMATION YOU CAN PROVIDE THE BETTER AS THIS HELPS GET TO THE ROOT OF THE PROBLEM - THIS INCLUDES MODEL NUMBER OF THE DONGLE, LOGCAT LOGS AND DMESG OUTPUT.
DOUBLY IMPORTANT: PLEASE READ THE FIRST AND SECOND POST TO GET AN UNDERSTANDING OF WHAT WORK HAS BEEN DONE AND HOW THIS FUNCTIONALITY IS IMPLEMENTED
Okay I've seen a lot a thread asking whether using 3G Dongles ( Huawei in particular ) is possible with the nexus 7........ The Answer........ "Of course it is!!!11!! it's Android/Linux Kernel, If we can dream it we can code it! "
I've been working on getting the full connectivity going but so far I've managed to bring up a raw ppp connection which is good for all things google (play, web browsing, gmail ) as the google apps still aren't playing fair with the connectivity manager and they just scoot around that and use web sockets instead!
Normally to enable this functionality we need to compile the usb_wwan.ko and option.ko as kernel module, much to my surprise google/asus have built these in already so we can just usb_modeswitch into modem mode and init our ppp connection. Winner! :good:
STAGE 1 PPP Connections
My test modems where Huawei E173s-1 and E1752Cu and the build I used is my own AOSP 4.1.1 with a kernel version of 3.1.10-g52027f9
Steps to 3G Fun
1. Do a full back up
2. Flash this boot.img through fastboot
3. Download This file ( nexus7-3g.7z ) See post 2 for link
4. unzip the file and adb push to correct directories
5. Turn off Wifi
6. Plug in Dongle
7. Restart
8. In Terminal Emulator of similar run
Code:
su
/system/etc/init_pppd_gprs
If all has worked then your dongle should now be connected!
Detailed Explanation ( Or Why The Hell Am I Doing This? ):
Why The New Boot.img?
The boot image adds service called hotplugd and service called switch_ms_to_3g which handles the usb_modeswitching
The code for hotplugd is here ( github ). if you don't want to flash the new boot image you can always run usb_modeswitch manually pointing to the config file and specifying your vendor id and product id if you do not wish to run hotplugd
Why turn Wifi Off?
We turn wifi off first because otherwise the ppp connection doesn't get assigned properly if wifi is turned off after the event.
Why The Restart?
On My USB OTG cable at least it doesn't seem to get power if I plug it in after power up YMMV.
STAGE 2 - FULL CONNECTIVITY
Obviously the Stage 1 is good. But It's not Great and we can do better. Using a similiar Wifi Only Device as my frame of reference, ( the Motorola Xoom Wifi ) to bring full connectivity ( i.e Mobile Networks Option in the settings and The Signal Icon in the Menu Bar) to the device required modification of the framework-res to allow mobile networks, you can either modify the existing one on the device or if building from source you can modify the config.xml found in the device overlay in the aosp ( device/asus/grouper/overlay/frameworks/base/core/res/res/values/config.xml )
something along the lines of
Code:
<resources>
<string-array translatable="false" name="networkAttributes">
<item>"wifi,1,1,0,-1,true"</item>
<item>"mobile,0,0,1,-1,true"</item>
<item>"mobile_mms,2,0,2,60000,true"</item>
<item>"mobile_supl,3,0,2,60000,true"</item>
<item>"mobile_dun,4,0,5,60000,true"</item>
<item>"mobile_hipri,5,0,3,60000,true"</item>
<item>"bluetooth,7,7,0,-1,true"</item>
<item>"ethernet,9,9,9,-1,true"</item>
<item>"mobile_fota,10,0,2,60000,true"</item>
<item>"mobile_ims,11,0,2,-1,true"</item>
<item>"mobile_cbs,12,0,2,60000,true"</item>
<item>"wifi_p2p,13,1,0,-1,true"</item>
</string-array>
<string-array translatable="false" name="radioAttributes">
<item>"9,1"</item>
<item>"1,1"</item>
<item>"0,1"</item>
<item>"7,1"</item>
</string-array>
</resources>
NOTE: I've not really took the time to fully understand these settings and I've basically Kang'd them from another overlay.
As such they maybe suboptimal. Any further tweaks Improvements or general insight is more than welcome.
This seems to build okay and gives me the above mentioned features,I also set the build.prop default network to
GSM:
Code:
ro.telephony.default_network=3
CDMA:
Code:
ro.telephony.default_network=4
NOTE: Full CDMA Support require more than just this. There are a number of other build properties which affected and I'm currently working out which are the best ones to use.
and added the following files
Code:
/system/bin/rild
/system/lib/libhuaweigeneric-ril.so
/system/etc/permissions/android.hardware.telephony.gsm.xml
/system/etc/permissions/android.hardware.telephony.cdma.xml
I would expect this work and give me full connectivity on the device however it seems to "bork" when trying to load the vendor specific ril , I suspect I may be missing a permission or something similar
PROBLEMS - TROUBLE SHOOTING
If you're having problems, first I would Install busybox which will give you lsusb, this will tell you if your modem is actually recognized.
You can also run netcfg which will tell you if the network interface name ppp1 has been created and is up, then grab dmesg and a logcat, so something like this on adb will give you a good idea of what's going on.
Code:
adb shell netcfg
adb shell lsusb
adb shell dmesg
adb logcat -b main -b system -b events -b radio
* Note if you are running logcat through terminal emulator please run it with superuser permissions
Code:
su -c "logcat -b main -b system -b events -b radio"
Happy Hacking People and Good Luck!
References:
DerArtem Original Work with Huawei Dongles on the Toshiba Folio 100
usb_modeswitch official website
3g-modem.wetpaint.com A great source of information regarding 3G Dongles
Android Device Porting Walkthrough - Android Builder Summit 2012 ( An excellent presentation on device porting )
Hi Folks.
[DISCLAIMER]YOU KNOW THE DRILL.... RESPONSIBILITY FOR DAMAGE, INCURRED COST THROUGH EXCESSIVE DATA USAGE ETC IS NOTHING TO DO WITH ME.[DISCLAIMER]
VITAL : THIS IS STILL A WIP - THERE IS A GOOD CHANCE THAT I'VE DONE SOMETHING WRONG, COPIED A FILE TO THE WRONG DIRECTORY OR SIMPLY MISSED SOMETHING OUT, PLEASE THINK ABOUT WHAT YOU ARE DOING BEFORE BLINDLY FOLLOWING THE INSTRUCTIONS OF SOME MANIAC ON THE INTERNET :laugh:
Right on with the fun!
I haven't had much time to look at this as it wasn't top of my list, However the good news is I now have full 3g connectivity on the nexus 7 using Huawei 3G Dongles. :victory:
The issue turned out to be incorrect permissions on the /dev/ttyUSB* devices nodes which are created by the Huawei Modems, this was fixed by adding the following line to uevent.grouper.rc in the boot.img,
Code:
/dev/ttyUSB* 0660 root radio
simple when you know how!
I've attached a zip file which contains the files needed to enable this. It is a manual installation at present although I plan to make this flashable through recovery at some point but would really like to leave any other modification you may have made in tact. I.e TabletUI etc
The Changes where made to the Stock Factory Image JRO03D with Kernel 3.1.10-g52027f9
I've included the stock Mms app and enabled both voice and sms capability in the framework-res.apk. I left out the Phone.apk as you can only make silent calls because of the lack of Audio Rooting ( A possible future project perhaps ). I also changed the Data Usage to monitor the connection used by the dongle which allows you to impose data limits on your bandwidth ( see screenshots ).
Upon applying this update you should have mobile networks available in "settings/more networks" and the signal strength icon should appear in your status bar
Download the file here ( hotfile )
Please follow the readme in the archive for installation instructions and take note of the notes!
In addition to the steps in the readme, It's worth making sure that everything that needs to be executable still is.
Code:
adb shell chmod 6755 /system/bin/pppd
adb shell chmod 755 /system/xbin/chat
adb shell chmod 755 /system/bin/usb_modeswitch
adb shell chmod 755 /system/bin/rild
adb shell chmod 755 /system/bin/hotplugd
adb shell chmod 755 /system/etc/ppp/init_pppd_gprs
adb shell chmod 755 /system/etc/ppp/ip-up-gprs
adb shell chmod 755 /system/etc/ppp/ip-down-gprs
SUPPORTED DEVICES
The theoretical list of supported devices come from those Huawei devices which are supported by the GSM Modem driver in 3.1.10 kernel.
my testing was on a E1752Cu, E173s-1 and the E1750
Confirmed Devices
Huawei
E1750
E1752Cu
E173s-1
E173-u2 ( Thanks to m3ritum ) Video
E367 ( Thanks to mynamesriz )
E3131s-2 GSM/HSPA+ ( Thanks to radkor )
EC156 CDMA with a couple of tweaks see this post [ Post #76 ] ( Thanks to mailbinoy )
E160E (Thanks to Dragon0501 )
ZTE
MF190J**
MF190**
MF636**
MF626**
** Thanks To NexusPhreak
TROUBLESHOOTING
There are 2 main ways your connection attempt can fail.
1. The UsbStick has not switched to modem mode
2. The ppp connection script failed
Either Way it would be highly useful post the list of system properties, outputs of dmesg and also a full logcat aswell as the vendor/product id from lsusb,
some like this throught the adb
Code:
adb shell getprop
adb shell lsusb
adb shell dmesg
adb logcat -b radio -b system -b main -b events
* Note if you are running logcat through terminal emulator please run it with superuser permissions
Code:
su -c "logcat -b main -b system -b events -b radio"
RESERVED
All sounds very cool, nice one.
looks very promising, do you know if there are any CDMA dongles for 4G phones on Verizon?
Is there a better explanation of how this works ? Would we have to have a data plan to use this or is it just picking up 3g?
Sent from my Nexus 7 using Tapatalk 2
azoller1 said:
looks very promising, do you know if there are any CDMA dongles for 4G phones on Verizon?
Click to expand...
Click to collapse
Not a clue, I'm not in the US and don't really have an understanding of the US celluar network. I'm unsure whether this implementation of the ril library ( the part that talks to android ) can handle CDMA as I've only got GSM dongles to test with.
emarietta said:
Is there a better explanation of how this works ? Would we have to have a data plan to use this or is it just picking up 3g?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Hi
This is using Huawei 3G Dongles ( sometime called mobile broadband ) which were quite popular in the UK and Europe, Something along the lines of this ( linked picked at random ) they normally come with their own sim card, and by extension a data plan, generally on a pay-and-go basis.They are effectively a fast "dialup modem" ( by UK Standards anyway )
The modems are generally carrier branded / locked and are restricted to data and sms only. However the carrier restriction can be removed and voice support can be added via firmware updates if the hardware allows.
My carrier ( 3-UK ), picked this up as tethering when I used my Phone SimCard for testing and as such It is not a method around tethering restrictions your operator may have in place.
I hope the helps shed some light on the topic.
cool idea, ill just use my 4g tether though
Great work mate!!! Just one question:
I will be getting my Nexus 7 in a couple of days and I already own a HP TouchPad running CM9. I want to know can I tether my dongle's internet on my nexus 7 with the HP Touchpad via Wifi or bluetooth?
lovleshgarg said:
Great work mate!!! Just one question:
I will be getting my Nexus 7 in a couple of days and I already own a HP TouchPad running CM9. I want to know can I tether my dongle's internet on my nexus 7 with the HP Touchpad via Wifi or bluetooth?
Click to expand...
Click to collapse
That's a dam fine question . The word FrankenConnection instantly sprung to mind :laugh: I haven't got the tablet in front of me at the moment and off the top of my head I'd say probably not by default.
However, It wouldn't be too difficult to enable on a technical level, it's all about your ip routing tables, they are probably numerous apps on play to do it, although personally i've a little no success with then. Cyanogenmod has it built into to the rom, at least on CM9 on my Sensation and that works a treat. I will have a proper look as It could be crazy enough to work!. :good:
had a go but no luck
using a Huawei E353 dongle with a variation of a 3 sim. has its own APN and a static IP, left over from a work project.
flashed the new boot, copied the new system and made the permissions mod. the various apps show up
under about tablet it shows baseband as unknown and if i try to add an APN it goes through the motions but doesnt add it to the list.
I've attached the logs, i'm no developer but i can follow instructions if any one can suggest any thing. there is every possibility i've messed up in the install so feel free to suggest dumb stuff that i should have known in the first place.
It could just be that the dongle isn't supported in which case we can chalk up a zte MF112 as been a duffer as well (had one kicking about so gave it a go)
laz2336 said:
using a Huawei E353 dongle with a variation of a 3 sim. has its own APN and a static IP, left over from a work project.
flashed the new boot, copied the new system and made the permissions mod. the various apps show up
under about tablet it shows baseband as unknown and if i try to add an APN it goes through the motions but doesnt add it to the list.
I've attached the logs, i'm no developer but i can follow instructions if any one can suggest any thing. there is every possibility i've messed up in the install so feel free to suggest dumb stuff that i should have known in the first place.
It could just be that the dongle isn't supported in which case we can chalk up a zte MF112 as been a duffer as well (had one kicking about so gave it a go)
Click to expand...
Click to collapse
Hi There,
Thanks for trying...... The Logcat proved useful. As many a woman has said to me, "It's not you it's me" :laugh: ..... You need to make the rest of the added files in /system/bin executable.
Code:
adb shell chmod 755 /system/bin/usb_modeswitch
adb shell chmod 755 /system/bin/rild
this line in the logcat explains it all
Code:
E/logwrapper( 842): executing /system/bin/usb_modeswitch failed: Permission denied
Good Luck and thanks for the detailed info...
It Lives!!!
I can see mobile networks, signal strength and all that good stuff. just need to figure out the APN details now for this cranky sim
top job trevd
laz2336 said:
I can see mobile networks, signal strength and all that good stuff. just need to figure out the APN details now for this cranky sim
top job trevd
Click to expand...
Click to collapse
It should pull the apn off the sim automatically.... the Radio Interface Layer may need a bit more tweaking, If you want to post more logcats, I wouldn't mind a cheeky look because that's how I get my kicks
Don't forget to turn your Wifi Off...... And sometimes turning data roaming on helps. especially with t-mobile/orange in the UK
happy to run logs for you. i will say though that this is no run of the mill sim, it sits on top of 3 as a carrier but has its own 3rd party APN, login details and a statip IP address when it is connected. it does pick the apn from the sim and show the default 3 apn settings, i just need to tweak them a bit.
I'll find a hub and get some logs with modem hooked up.
update
wow these logs get big quickly. this one has the modem been removed, reconnected, negotiating with the network and trying to log in. I've removed apn,usernames and passwords and replaced them with <APN> <username> <password>. I can give you the APN name over pm if it helps but for security reasons i can't give out the login details, bit too company specific.
laz2336 said:
happy to run logs for you. i will say though that this is no run of the mill sim, it sits on top of 3 as a carrier but has its own 3rd party APN, login details and a statip IP address when it is connected. it does pick the apn from the sim and show the default 3 apn settings, i just need to tweak them a bit.
I'll find a hub and get some logs with modem hooked up.
Click to expand...
Click to collapse
A Bit like GiffGaff!, Cyanogenmod Rom maintain a hugh list, I think he must have got every carrier in the world, Check it out here ( apns-conf.xml on github )
trevd said:
A Bit like GiffGaff!, Cyanogenmod Rom maintain a hugh list, I think he must have got every carrier in the world, Check it out here ( apns-conf.xml on github )
Click to expand...
Click to collapse
just had a quick search, he aint got mine
bit more of an update, hooked up the ZTE MF112 in the office this morning it seen and sees the network. This dongle is unlocked so i've given it a go with my own vodafone sim from my phone. copied the apn settings across from the phone (just the standard vodafone 'internet' APN), it goes through the the motions of trying to connect but never gets there. I'll fire up the logging a bit later and get you a bit more data.
on a side note so far both these dongles have been able to be connected while the device is turned on and been picked up automaticaly.
I think it may be more permissions
laz2336 said:
bit more of an update, hooked up the ZTE MF112 in the office this morning it seen and sees the network. This dongle is unlocked so i've given it a go with my own vodafone sim from my phone. copied the apn settings across from the phone (just the standard vodafone 'internet' APN), it goes through the the motions of trying to connect but never gets there. I'll fire up the logging a bit later and get you a bit more data.
on a side note so far both these dongles have been able to be connected while the device is turned on and been picked up automaticaly.
Click to expand...
Click to collapse
Hi I had a little sleep on it, it's probably more persmission issues *facepalm*
Code:
adb shell chmod 755 /system/etc/ppp/init_pppd_gprs
adb shell chmod 755 /system/etc/ppp/ip-up-gprs
adb shell chmod 755 /system/etc/ppp/ip-down-gprs
As a test You can try running
Code:
adb shell /system/etc/ppp/init_pppd_gprs
which should start a native connection ( the modem will connect but android won't know about it ), although you can use the built in browser and Gapps ( play , gmail ,youtube etc ) as they don't use androids connectivity service to check for connections
no logs yet but heres the update so far.
set the permissions on those three files and had another go. no difference. do all the files that get put in the ppp directory need to be executable?
trying to start the connection with init_pppd_gprs doesn't manage to connect with either dongle, though the E353 does seem to get further. it moves on to a new line in terminal emulator with out returning any thing. with the MF112 it gets quite vocal about not been able to find the usb device despite it showing as been registered on the network under system properties.
sadly can't put the voda sim in the E353 as the bloddy thing is locked.(did try, though it pulls the APN details it won't see the voda network)
Has anyone else noticed heavy standby drain from Android System?
I spent a couple of hours digging through to find the culprit and it looks like it's actually Qualcomm's IZat location services. Even though you can disable it in the location settings it is still set to scan and report back to Qualcomm's servers via a couple of config files in /etc.
Instead of changing the config files and forgetting which ones I changed I simply disabled the service in location settings then disabled the package that IZat uses and rebooted.
I am already seeing an decrease in battery usage and I have been able to still use GPS.
You can either freeze the app with Titanium Backup or whatever you choose. I did it through adb which I believe is even possible to do without root.
com.qualcomm.location
Code:
adb shell pm disable com.qualcomm.location
I hope this helps someone else out that was having the same issue. I did not get a screen shoot of my battery usage before disabling the service but I have included one with it disabled.
I was losing 15% overnight with a kernel wakelock for the entire night that showed up as LocationManagerServiceEx through GSam
for users with no root:
Code:
adb shell pm hide com.qualcomm.location
I'm going to poke around and try and find the files in /etc you mentioned.. would rather tackle the actual problem in the config files than disable izat entirely. good find though. I'm currently trying to find the source of my Google Play services drain (may be related to pushbullet). you mentioned that it was showing up in your Android system drain so not sure if it'll help with my specific issue but if it does I'll report back.
autoprime said:
for users with no root:
Code:
adb shell pm hide com.qualcomm.location
What is the command to unhide it? I would like to try it but also want to reverse it. Thanks
Click to expand...
Click to collapse
hobbs said:
autoprime said:
for users with no root:
What is the command to unhide it? I would like to try it but also want to reverse it. Thanks
Click to expand...
Click to collapse
adb shell pm unhide com.qualcomm.location
Click to expand...
Click to collapse
autoprime said:
for users with no root:
I'm going to poke around and try and find the files in /etc you mentioned.. would rather tackle the actual problem in the config files than disable izat entirely. good find though. I'm currently trying to find the source of my Google Play services drain (may be related to pushbullet). you mentioned that it was showing up in your Android system drain so not sure if it'll help with my specific issue but if it does I'll report back.
Click to expand...
Click to collapse
I think they were lowi.conf and xtwifi.conf there might have been more but I can't remember at this time.
As for finding what is draining I learned recently (and quickly) how helpful dumpsys is.
KAsp3rd said:
I think they were lowi.conf and xtwifi.conf there might have been more but I can't remember at this time.
As for finding what is draining I learned recently (and quickly) how helpful dumpsys is.
Click to expand...
Click to collapse
ahh thank you. I got sidetracked when trying to pinpoint my drain and never went through all the files. I will check out those 2 files as well as grep around through the rest.
and thanks for the dumpsys tip... never actually used it. I went the easy route and reinstalled BetterBatteryStats. Within 20 minutes a partial waklock stood out... "CmaSystemUpdateService"
A quick google lead me to this reddit: https://www.reddit.com/r/Nexus/comments/4jmw74/cmasystemupdateservice_wakelock/
Made sense... I had blocked OTA updates using the same method Nexus devices use.. as the tmo g5 gets its updates the same way.. instead of using LG's own updater like most of the other variants. As soon as re-enabled "SystemUpdateService" in Google Play Services the wakelock stopped and battery was fine. I'm not sure what needs to be done to stop the wakelock while still blocking OTA updates... more research must be done.
autoprime said:
ahh thank you. I got sidetracked when trying to pinpoint my drain and never went through all the files. I will check out those 2 files as well as grep around through the rest.
and thanks for the dumpsys tip... never actually used it. I went the easy route and reinstalled BetterBatteryStats. Within 20 minutes a partial waklock stood out... "CmaSystemUpdateService"
A quick google lead me to this reddit: https://www.reddit.com/r/Nexus/comments/4jmw74/cmasystemupdateservice_wakelock/
Made sense... I had blocked OTA updates using the same method Nexus devices use.. as the tmo g5 gets its updates the same way.. instead of using LG's own updater like most of the other variants. As soon as re-enabled "SystemUpdateService" in Google Play Services the wakelock stopped and battery was fine. I'm not sure what needs to be done to stop the wakelock while still blocking OTA updates... more research must be done.
Click to expand...
Click to collapse
I had the same drain after disabling updated on my tmo g5. I used app MyAndroidTools to fix it. After you disable system updates open the app and grant root. Open the menu and click on service, broadcast receiver and activity options. In each on goto system then find Google play services and disable anything that says system update then go back and do the same for Google play services framework. After disabling for all three categories restart and your wavelock will be gone. Also you can disable the OTA using this method as well. Seems like when using adb it only disables some of the services but not all which is why it keeps searching for updates. Hope this helps.
I too have this irritating wakelock which prevents the phone from reaching deep sleep (it shows up as LocationManagerServiceEx in betterbatterystats).
When I freeze the com.qualcomm.location app however, GPS actually DOES NOT work the way it is supposed to. Interestingly, it results in the GPS behaving just like the 10A GPS bug--GPS is achieved, but then cuts in and out all the time, making nav near useless. The 10D update fixed this. So maybe the implementation was buggy in the 10a firmware.
Still would be nice to have a more permanent fix for this wakelock issue. I'm not getting the cmasystemupdateservice issue.
autoprime said:
ahh thank you. I got sidetracked when trying to pinpoint my drain and never went through all the files. I will check out those 2 files as well as grep around through the rest.
and thanks for the dumpsys tip... never actually used it. I went the easy route and reinstalled BetterBatteryStats. Within 20 minutes a partial waklock stood out... "CmaSystemUpdateService"
A quick google lead me to this reddit: https://www.reddit.com/r/Nexus/comments/4jmw74/cmasystemupdateservice_wakelock/
Made sense... I had blocked OTA updates using the same method Nexus devices use.. as the tmo g5 gets its updates the same way.. instead of using LG's own updater like most of the other variants. As soon as re-enabled "SystemUpdateService" in Google Play Services the wakelock stopped and battery was fine. I'm not sure what needs to be done to stop the wakelock while still blocking OTA updates... more research must be done.
Click to expand...
Click to collapse
Hi @autoprime,
For some reason, out of the blue, I received the Nougat update notification today. I plan on staying on MM until I retire the device.
I had previously knocked out the OTA update receivers using 3c system tuner, just disabling the receiver elements that matched the 3 ones you listed in your all in one thread.
When I looked at the running receivers, one of them that was still on for some reason (update.systemupdateserviceactivereceiver). I can toggle it off, but it doesn't stick with a reboot. Under services, update.systemupdateservice was still active.
I decided to go the ADB route. I stopped the services using your ADB commands. This fixed the OTA. But then just as you mentioned, the CmaSystemUpdateService wakelock came in.
Did your research come up with any new ways to stop the OTA notification?
jeffsga88 said:
I had the same drain after disabling updated on my tmo g5. I used app MyAndroidTools to fix it. After you disable system updates open the app and grant root. Open the menu and click on service, broadcast receiver and activity options. In each on goto system then find Google play services and disable anything that says system update then go back and do the same for Google play services framework. After disabling for all three categories restart and your wavelock will be gone. Also you can disable the OTA using this method as well. Seems like when using adb it only disables some of the services but not all which is why it keeps searching for updates. Hope this helps.
Click to expand...
Click to collapse
Just saw this post just now. Do you have a more detailed list of what you disabled?
waylo said:
Just saw this post just now. Do you have a more detailed list of what you disabled?
Click to expand...
Click to collapse
Using the app My Android Tools is the easiest way I found. Then do like I said before and go into each category and click on Google play services and search for systemupdate, disable anything the comes up. Then go into Google services framework and search for same thing and disable anything that comes up. I've included some screenshots, hopefully that helps. Maybe when I have more time I'll write each thing down and post list but don't have time right now.
KAsp3rd said:
Has anyone else noticed heavy standby drain from Android System?
I spent a couple of hours digging through to find the culprit and it looks like it's actually Qualcomm's IZat location services. Even though you can disable it in the location settings it is still set to scan and report back to Qualcomm's servers via a couple of config files in /etc.
Instead of changing the config files and forgetting which ones I changed I simply disabled the service in location settings then disabled the package that IZat uses and rebooted.
I am already seeing an decrease in battery usage and I have been able to still use GPS.
You can either freeze the app with Titanium Backup or whatever you choose. I did it through adb which I believe is even possible to do without root.
com.qualcomm.location
Code:
adb shell pm disable com.qualcomm.location
I hope this helps someone else out that was having the same issue. I did not get a screen shoot of my battery usage before disabling the service but I have included one with it disabled.
I was losing 15% overnight with a kernel wakelock for the entire night that showed up as LocationManagerServiceEx through GSam
Click to expand...
Click to collapse
I'm on a unrooted G4 running Nougat but saw this thread and decide to try it, but when I use the above command I get the following error, see grab below, any ideas? thanks
I still have my verizon unlimited data plan. Currently my iphone is jailbroken so I can use the hotspot feature.
I assume the hotspot feature will be off when I get my non-vzw pixel. Is there a way to turn it on without rooting? Its been couple of years since I had an android phone.
polo2883 said:
I still have my verizon unlimited data plan. Currently my iphone is jailbroken so I can use the hotspot feature.
I assume the hotspot feature will be off when I get my non-vzw pixel. Is there a way to turn it on without rooting? Its been couple of years since I had an android phone.
Click to expand...
Click to collapse
There's a workaround in the pixel xl forum and I'm sure this will be implemented better once rom development begins.
I tried to go into the APN settings with Quick Shortcut Maker, but I also have no root and it said something like current user has no access to APN settings. Root is probably required, or at least some kind of workaround.
cntryby429 said:
There's a workaround in the pixel xl forum and I'm sure this will be implemented better once rom development begins.
Click to expand...
Click to collapse
Hopefully root comes out soon and there is a better way. I don't use it much but its extremely convenient when needed.
polo2883 said:
Hopefully root comes out soon and there is a better way. I don't use it much but its extremely convenient when needed.
Click to expand...
Click to collapse
The workaround is extremely simple. You just download Network Signal Refresher and refresh and then on hotspot. Done.
What's the differencedifferent between a Hotspot and a Hotspot? Android comes with a wifi hotspot feature. Why doesn't that work for you?
Sent from my sailfish using XDA Labs
Huh, it's blocked when using Sprint.
Anyone using the Pixel on T-Mobile and able to get native tethering working? My Pixel is still on order so I am wondering if the command *adb shell content query --uri content://settings/global --where "name='tether_dun_required' AND value=0" still works to activate native tethering.
Sent from my Nexus 7 using XDA-Developers mobile app
I was going to test it for the Sprint block but didn't have an up to date version of ADB. I will check it out later today.
lafinjack said:
I was going to test it for the Sprint block but didn't have an up to date version of ADB. I will check it out later today.
Click to expand...
Click to collapse
Great, I hope it works.
Sent from my Nexus 7 using XDA-Developers mobile app
The rumors in the XL forum are saying that while network refresher works, many have it cut out after 10-20 minutes and having to do it again.
Sorry, got busy yesterday and didn't get a chance to test it.
The shell command did not work for me on my Pixel 5. I tried running it while the hotspot was active, then while it was inactive. Using the commands gave no feedback in the command line, just went back to the empty send line, and I'm not sure what a successful edit looks like. As mentioned by others the airplane mode trick did not work for me, and while the refresh app method does work for activating the hotspot, I get no internet access when connecting to it. I also tried messing around with the build.prop file, but as expected I wasn't able to edit it without root access.
For reference, I'm going from this comment that gives the command as
Code:
adb shell content insert --uri content://settings/system --bind name:s:tether_dun_required --bind value:i:0
I found another command that changes it slightly to
Code:
adb shell content insert --uri content://settings/global --bind name:s:tether_dun_required --bind value:i:0
...but this also did not work.
Now that theirs root. What needs to get done to get wifi tethering working
Sent from my iPad using Tapatalk
With root you should be able to get into the APN settings. Check a guide if you're unfamiliar with it, it's buried kinda deep but pretty straightforward. Searching for 'android tether apn dun' should do it. I only learned there's root now from you so I'll go test it out myself. Thanks!
---------- Post added at 09:47 PM ---------- Previous post was at 08:57 PM ----------
Just did it, root will get you functioning hotspot on Sprint, possibly for other people too who were having the same problem after getting the hotpost on. I ran the first code above ( adb shell content insert --uri content://settings/system --bind name:s:tether_dun_required --bind value:i:0 ) while the hotspot happened to be off, and after turning it back on I was able to get internet through it on other devices. If you try this with the hotspot on please report back so we know if it needs to be either particular setting.
Just having root itself has not enabled the normal hotspot switch locations, like in the notification drawer or in the tethering settings, and I still had to use the network refresh trick to get them to work. This may need another command to insert/change the correct protection setting, or something else entirely.
I also went back to the APN settings through the shortcut maker and received the same error I had before, about this user not being able to access them.
On a related note, I saw some people mention that their hotspot would automagically turn off after 10-20 minutes, so I'll post this now and keep an eye on whether it does so here, as I never watched before.
Is this problem US only? Tethering works fine in the UK.
Sent from my Pixel using XDA-Developers mobile app
polo2883 said:
Now that theirs root. What needs to get done to get wifi tethering working
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
has anyone tried adding
Code:
net.tethering.noprovisioning=true
to the /system/build.props file? that used to work on the previous nexus line
subhani said:
Is this problem US only? Tethering works fine in the UK.
Click to expand...
Click to collapse
Seems to be a carrier thing. Some people were able to use hotspot after using a workaround, including Verizon, but it seemed like for Sprint doing that gave hotspot but no internet access.
ghudgins said:
has anyone tried adding
Code:
net.tethering.noprovisioning=true
to the /system/build.props file? that used to work on the previous nexus line
Click to expand...
Click to collapse
Thanks, I am about to head out but I will test this later if nobody else has yet.
lafinjack said:
Seems to be a carrier thing. Some people were able to use hotspot after using a workaround, including Verizon, but it seemed like for Sprint doing that gave hotspot but no internet access.
has anyone tried adding
Thanks, I am about to head out but I will test this later if nobody else has yet.
Click to expand...
Click to collapse
I added it to the build.prop seems to work. I'll be testing it it sticks and connection speeds and reliability.
lafinjack said:
Seems to be a carrier thing. Some people were able to use hotspot after using a workaround, including Verizon, but it seemed like for Sprint doing that gave hotspot but no internet access.
Thanks, I am about to head out but I will test this later if nobody else has yet.
Click to expand...
Click to collapse
The change to the build.prop does work. At least on my Verizon pixel 128gb
Sent from my iPad using Tapatalk
I can confirm that changing the build.prop works as well.
Make sure your bootloader is unlocked and you are rooted.
I used root explorer. Root > System > Long press build.prop > Open in Text Editor
Scroll all the way to the bottom. Type in "net.tethering.noprovisioning=true" .. Then save and exit. Reboot the phone and you're good to go.