My phone had a constant wakelock and it was draining my battery.
After doing more research I found that it is because of a recent update to Google Play Services. The Cyanogenmod fix is here:
http://review.cyanogenmod.org/91021
The workaround I used was to enable the service at startup. Only the receivers should be disabled, the service should remain enabled. See the above link for details.
Here is a workaround I use:
Install Script Manager (SManager) from Play Store. https://play.google.com/store/apps/details?id=os.tools.scriptmanager.
Enable Browse as root in SManager (Advanced > Configuration).
From SManager, create a script in /data/local/ with the name 'startsysupservice'.
Edit the script and put the following line in the file:
su -c "pm enable com.google.android.gms/.update.SystemUpdateService"
Mark the following options: Su, Boot, Bg.
Change the radio button from 'Is script' to 'Is executable'. This may not be required for CarbonRom but was when I tested this on CyanogenMod. If you don't select this, the CPU may be constantly doing something so it will actually be worse than before (this selection may have something to do with what shell is used to execute this).
Hit Save. Reboot the phone.
Whenever the phone boots up, it will start the service which should stop the wakelock. It may take a few minutes before the script is run, but eventually the service will start. You can use the 'Disable Service' app to check that it worked.
NOTE: The correct way is for your ROM maintainer to update the sources with the new patch. Unfortunately, many ROMs are no longer maintained (especially for older devices) so this way is a good way to get around this issue for these ROMs. I originally created this for CarbonRom on my P769. I then switched to CyanogenMod 11 by dhiru1602 and this workaround still worked. It should work on other devices as well.
frostinide said:
My phone had a constant wakelock. After doing more research I found that it is because of a recent update to Google Play Services. The Cyanogenmod fix is here:
http://review.cyanogenmod.org/#/c/91021/
The fix I used was to enable the service at startup. Only the receivers should be disabled, the service should remain enabled. See the above link for details.
Here is a workaround I use:
Install Script Manager (SManager) from Play Store. https://play.google.com/store/apps/details?id=os.tools.scriptmanager.
Enable Browse as root in SManager (Advanced > Configuration).
From SManager, create a script in /data/local/ called 'startsysupservice' with the single line:
su -c "pm enable com.google.android.gms/.update.SystemUpdateService"
Mark the following options: Su, Boot, Bg.
Hit Save. Reboot the phone.
Whenever the phone boots up, it will start the service which should stop the wakelock. It may take a few minutes before the script is run, but eventually the service will start. You can use the 'Disable Service' app to check that it worked.
It would be nice if the Cyanogenmod fix in the link above could be merged into CarbonRom and other ROMs for future releases, but I wanted to share this workaround in the meantime. I have P769 with CarbonRom.
Click to expand...
Click to collapse
Interesting info Frost..
and the script is a good idea. By the time I have Oneplus O2 OS all patched up, it will look worse than Frankenstein and I'll never remember all of the operations.
Frost,
Would you detail the differences between "Only the receivers should be disabled, the service should remain enabled"?
Thanks.
JeffDC said:
Would you detail the differences between "Only the receivers should be disabled, the service should remain enabled"?
Click to expand...
Click to collapse
I got that information from the CyanogenMod link I posted. You can see the patch there and see exactly what lines were changed for this fix.
I suggest you read the Android development documentation if you want to know how it all works.
I also found this link, but I can't vouch for its correctness as I don't have enough knowledge of how Android works: http://stackoverflow.com/questions/14548927/android-broadcast-receiver-vs-service
This is a major problem affecting all CM based custom ROMS. The problem is Carbon is not doing anything about it. If you go on their website, there is no new nightly for Galaxy S3 D2LTE - It has been the same ROM since 2014. When you boot the phone, it disables SystemUpdateService. So the phone never sleeps. Waiting for Carbon to Fix this issue.
So here's the real question...
WHERE is this Code within the CM and CM based ROMS that disables SystemUpdateService at boot?
ocd_amp said:
The problem is Carbon is not doing anything about it.
Click to expand...
Click to collapse
If you go to their website, they say they basically stopped working on KitKat except for certain fixes, and are concentrating on Lollipop.
https://carbonrom.org/on-to-sweeter-things/
You can check on their website for more info or if you want to try and contact them. Although I would say it's not really worth it.
I would just use the workaround that I posted (or any other workaround out there). It's not the cleanest solution, but it gets the job done.
ocd_amp said:
WHERE is this Code within the CM and CM based ROMS that disables SystemUpdateService at boot?
Click to expand...
Click to collapse
Check the link I put to the CyanogenMod fix. It has the patch showing the exact line changes and the files that have changed.
update!
Please check this thread.
[MOD] [v7.0.99] Google Play Services with System Update Wake Lock Fix
http://forum.xda-developers.com/one...mod-google-play-services-update-wake-t3078082
frostinide said:
My phone had a constant wakelock and it was draining my battery. I am using CarbonRom on my P769.
After doing more research I found that it is because of a recent update to Google Play Services. The Cyanogenmod fix is here:
http://review.cyanogenmod.org/91021
The workaround I used was to enable the service at startup. Only the receivers should be disabled, the service should remain enabled. See the above link for details.
Here is a workaround I use:
Install Script Manager (SManager) from Play Store. https://play.google.com/store/apps/details?id=os.tools.scriptmanager.
Enable Browse as root in SManager (Advanced > Configuration).
From SManager, create a script in /data/local/ called 'startsysupservice' with the single line:
su -c "pm enable com.google.android.gms/.update.SystemUpdateService"
Mark the following options: Su, Boot, Bg.
Change the radio button from 'Is script' to 'Is executable'. This may not be required for CarbonRom but was when I tested this on CyanogenMod. If you don't select this, the CPU may be constantly doing something so it will actually be worse than before (this selection may have something to do with what shell is used to execute this).
Hit Save. Reboot the phone.
Whenever the phone boots up, it will start the service which should stop the wakelock. It may take a few minutes before the script is run, but eventually the service will start. You can use the 'Disable Service' app to check that it worked.
It would be nice if the Cyanogenmod fix in the link above could be merged into CarbonRom and other ROMs for future releases, but I wanted to share this workaround in the meantime.
Click to expand...
Click to collapse
Thanks a lot buddy.
From a battery drain of anywhere between 20-45% / hour, went straight to 0.3% / hour since the last 4 hours now ( was sleeping myself, but nonetheless the lower end aka 20% drain used to take place when I was sleeping.
Your fix has restored my battery life ( atleast in this short time I do feel that has happened)
Thanks again.
Hi there,
i got rid of the googleupdateservice wakelock by the above hack.
But now i have the fingerprintscannerwakelock keeping my device awake.
Any suggestions for that??
This is the only method I've found to work on my phone to automate the process upon boot. Thanks!!! I've tried about 10 different other ways, from init.d scripts to autoruns to appOps to modified play service apks to you name it.
frostinide said:
My phone had a constant wakelock and it was draining my battery. I am using CarbonRom on my P769.
After doing more research I found that it is because of a recent update to Google Play Services. The Cyanogenmod fix is here:
http://review.cyanogenmod.org/91021
The workaround I used was to enable the service at startup. Only the receivers should be disabled, the service should remain enabled. See the above link for details.
Here is a workaround I use:
Install Script Manager (SManager) from Play Store. https://play.google.com/store/apps/details?id=os.tools.scriptmanager.
Enable Browse as root in SManager (Advanced > Configuration).
From SManager, create a script in /data/local/ called 'startsysupservice' with the single line:
su -c "pm enable com.google.android.gms/.update.SystemUpdateService"
Mark the following options: Su, Boot, Bg.
Change the radio button from 'Is script' to 'Is executable'. This may not be required for CarbonRom but was when I tested this on CyanogenMod. If you don't select this, the CPU may be constantly doing something so it will actually be worse than before (this selection may have something to do with what shell is used to execute this).
Hit Save. Reboot the phone.
Whenever the phone boots up, it will start the service which should stop the wakelock. It may take a few minutes before the script is run, but eventually the service will start. You can use the 'Disable Service' app to check that it worked.
It would be nice if the Cyanogenmod fix in the link above could be merged into CarbonRom and other ROMs for future releases, but I wanted to share this workaround in the meantime.
Click to expand...
Click to collapse
I don't get what you mean by "with the single line:
su -c "pm enable com.google.android.gms/.update.SystemUpdateService"
How do I do that part? All I get is an option to set the name of the script
noob to android said:
But now i have the fingerprintscannerwakelock keeping my device awake.
Any suggestions for that??
Click to expand...
Click to collapse
Sorry, no idea on that one. You should probably create a new post for that.
wasiq224 said:
I don't get what you mean by "with the single line:
su -c "pm enable com.google.android.gms/.update.SystemUpdateService"
How do I do that part? All I get is an option to set the name of the script
Click to expand...
Click to collapse
Put in 'startsysupservice' as the name of the script. Then edit the script (there is an edit button at the top) and put the following line in there:
su -c "pm enable com.google.android.gms/.update.SystemUpdateService"
After it's saved, edit it again to make sure the contents did actually save. If it doesn't work, you may need to save on your sdcard first and then copy it over manually with a root explorer.
It works but you have to say that this file must have changed permissions.
Thanks a lot.
Dru79 said:
It works but you have to say that this file must have changed permissions.
Thanks a lot.
Click to expand...
Click to collapse
Which are the new permissions for the file?
Related
Hi,
When I go to gPlay on the Q and click on "Apps" I only get like 150,000 results available for download, only a small fraction of the total apps available. When I go there on my computer browser to try to download an app to the Q it says "This app is not compatible with this device" for 90% of the apps. So, no dice with either method.
I have been sideloading apps and most of them work just fine. So I want to get around this gPlay restriction on the Q so I can just download apps directly from gPlay rather than having to sideload them.
(I am fully aware that the reason why gPlay keeps track of which devices are compatible is to avoid more "broken" apps than necessary, but in the case of the Q their own system appears to be broken itself, so I want to get around it.)
So, I bought the Device Spoofer app for $1.50USD
https://play.google.com/store/apps/details?id=com.scheffsblend.devicespoof&hl=en
which, despite the reviews worked just fine for me on both the Nexus 7 and on Nexus Q. It changes your build.prop file to spoof Google Play into thinking you are a different device of your choosing. Note that, as it says in the instructions, you need to spoof the device using the app, reboot, go to gPlay, *download an app* (any app), and from then on gPlay will register your device as a different one.
That works for me -- I select for example "Galaxy Nexus", go thru the steps above, and voila, gPlay in my computer's browser has now replace "Nexus Q" with "Galaxy Nexus". Pretty cool.
HOWEVER, and I am now getting to the point, this doesn't allow me to download any more apps than I had access to before! It still says "This app is not compatible with this device ["Galaxy Nexus"]" for the same apps that were incompatible before. Browsing gPlay on the Q also doesn't yield any new opportunities for downloading apps.
I think what is happening is that even though the build.prop file is being changed, the Q is still reporting to gPlay that it doesn't have, for instance: GPS, phone functionality, etc etc, long list of items. And that means that any apps that require any one of those functionalities is "not compatible" (despite the fact that sideloading many of them means they work just fine).
So, my point is, does anyone know how to spoof gPlay so that the Q reports to gPlay that it has all of the bells and whistles? (GPS, phone functionality, etc etc)
Thanks
I downloaded all the .xml files from my Q's /system/etc/permissions folder and compared them to those downloaded from my Nexus 7. There are about half the number of files and indeed many things are not supported, no surprise.
Is it safe to just copy all the .xml files from my Nexus7 to my NexusQ? (plus a few .jar files that are linked to in the .xml files).
And perhaps then gPlay will show more apps?
OK sorry for multiple posts, but what the heck I just tried it. And can't see any more apps on gPlay. Tried downloading one that was visible as I thought it might only report its permissions at download-time, but nothing changed after the download. Drawing blanks here.
FIGURED IT OUT!
That's right folks, you can now download any app directly onto the Q! No sideloading, no adb.
Followed these instructions for a different device. Basically I was on the right track but needed to change the .xml's file permissions back to rw-r-r and then clear gPlay cache, reboot, etc, then it worked.
Pasting the steps from this page http://www.slatedroid.com/topic/34849-guide-to-fix-market-to-get-more-apps-compatible/ below, with the small modification that I got my .xml files from my Nexus 7, not from his/her link, and I only loaded the tablet_core_hardware.xml so far (I have not attempted loading on any of the Nexus 7's other .xmls but most of them don't seem useful). Thanks go out to bosondehiggs of slatedroid.com. I have made a note in square brackets at which point my Nexus Q gPlay started suddenly showing all apps.
A. Backup /system/etc/permissions (just take a copy with ES file explorer or root explorer.recommended just in case)
B. copy the xmlfiles files into /system/etc/permissions (android.hardware.location.gps.xml, android.hardware.location.xml, com.android.location.provider.xml, tablet_core_hardware.xml) agree to over write all of them
C. Make sure the file permission are rw-r-r (with ES file explorer, long tap then change properties on each file..to help you out all files in that directory need to be rw-r-r)
D. Go to settings->apps->all and tap Google Play Store
E. Click on Clear data
F. REBOOT tablet
market still not working
Go to settings->apps->all Go to “Google Play Store” again
‘Clear Cache’ if it lets you then ‘Force Stop’ — DO NOT Clear data
back and Go to “Google Services Framework”
‘Clear data’ then ‘Force Stop’
REBOOT your machine. [After rebooting, the Nexus Q worked with gPlay just fine!]
Then after reboot market is still not working.. then go into..
settings->apps->all google play store again open it but this time clear data if it lets you..
thats it exit open market up, login and you should now have full market access....Youtube...Facebook....
Click to expand...
Click to collapse
hey, this looks cool I want to give it a try.
do you mind posting the instructions from beginning to end?
and the xml file needed too?
sonikot said:
hey, this looks cool I want to give it a try.
do you mind posting the instructions from beginning to end?
and the xml file needed too?
Click to expand...
Click to collapse
Sure, happy to. I'll include in greater detail than an expert hacker needs, so it's more noob-friendly.
First you need ES File Explorer app (get es_file_explorer_v1_6_1_7.apk or latest version from the publisher at http://www.estrongs.com/en/download.html).
adb connect to your device if not already. Type "adb devices" to check you are connected.
adb install the ES File Explorer .apk, and run it using the Trebuchet launcher.
Press "settings" (see my keyboard page to see how to do that). Scroll down and click Settings and enable "Up to root". Also enable "Root Explorer". OK we're done here for now, we'll use this app later.
Download this file: http://www.davidnhutch.com/tablet_core_hardware.xml. It's one of the .xml permissions files from the Nexus 7. You may also try other .xml files from other devices at your own risk. Or you can try mine, I guess also at your own risk.
Let's go back to adb. "adb shell"
"su"
"mkdir /sdcard/permissionsbackup"
"cat /system/etc/permissions > /sdcard/permissionsbackup"
"exit"
"exit". You should now be out of shell but still in the command window.
"adb push <path-to-that-xml-file>/tablet_core_hardware.xml /sdcard/tablet_core_hardware.xml"
"adb shell"
"su"
"cat /sdcard/tablet_core_hardware.xml > /system/etc/permissions/tablet_core_hardware.xml"
If you want, check it's there: "cd /system/etc/permissions" "ls"
"exit"
"exit"
Next we will change the file permissions for that file we just copied. Open ES File Explorer, click "Up" once to get to the root directory, click System > etc > permissions. Right click or long-press on tablet_core_hardware.xml. Scroll to the bottom of the list that comes up and select Properties. Click the Change button. Select the following boxes, and only the following boxes: User read, User write, Group read, Other read. Click OK, OK. The other files in that directory also need to be rw-r-r, but they should be fine.
Go to Settings > Apps > All > Google Play Store
Click Clear data
Reboot the Q by typing "adb reboot". If you did that using adb-over-wifi, then you'll probably need to do the "adb connect" thing again to reconnect.
Open Google Play. If it's still not working (still shows only a few apps), then continue.
Go to Settings > Apps > All > Google Play Store
Click Clear cache if it lets you, then click Force stop. DO NOT Clear data
Go back once and go to “Google Services Framework”
Click Clear data then Force stop
Reboot the Q again in the same way. After rebooting, my Nexus Q worked with gPlay just fine! However if you still don't see new apps, continue.
Go to Settings > Aapps > All > Google Play Store
Clear Data if it lets you
That's it! Now just Open Google Play, login and you should be able to see and download almost any app either directly on the Q or remotely through a browser on your computer. You may need to download just one app (any app) in order to be able to get the remote download via browser thing working, as Google Play appears to update its knowledge of which devices you have only when you download something.
davidnhutch said:
Sure, happy to. I'll include in greater detail than an expert hacker needs, so it's more noob-friendly.
Click to expand...
Click to collapse
I have now put that list here: http://davidnhutch.com/sandbox/blog/how-to-make-google-play-show-you-more-apps/
I will attempt to maintain the instructions at the above link (in case there are errors, or in case the non-GoogleIO Nexus Q's behave differently to the GoogleIO NexusQ (which I have)).
davidnhutch said:
I have now put that list here: http://davidnhutch.com/sandbox/blog/how-to-make-google-play-show-you-more-apps/
I will attempt to maintain the instructions at the above link (in case there are errors, or in case the non-GoogleIO Nexus Q's behave differently to the GoogleIO NexusQ (which I have)).
Click to expand...
Click to collapse
hey step 3 isnt working on the assumption I know how to lauch trebuchet on Q.
How would I launch trebuchet?
sonikot said:
hey step 3 isnt working on the assumption I know how to lauch trebuchet on Q.
How would I launch trebuchet?
Click to expand...
Click to collapse
bump can somebody upload the file for trebuchet and explain how to run this launcher so we can run .apks
thanks
UKROB86 said:
bump can somebody upload the file for trebuchet and explain how to run this launcher so we can run .apks
thanks
Click to expand...
Click to collapse
Sorry, I assume you have already followed the instructions by kornyone here to root and install a launcher:
http://forum.xda-developers.com/showthread.php?p=28484300
There are other ways of doing this too. Some folks have gotten CM9 working on it.
I just made this quick video which shows Trebuchet and the Google Play showing most apps available, near the middle of this video.
What Can You Do with the Nexus Q? : http://youtu.be/6rb4iQDBom0
Press "settings" (see my keyboard page to see how to do that). Scroll down and click Settings and enable "Up to root". Also enable "Root Explorer". OK we're done here for now, we'll use this app later.
Click to expand...
Click to collapse
Can you provide us with the link to your keyboard page so I can mimic these steps on my Q. Also to navigate around on the Nexus Q does it still require a USB mouse to be plugged in to it? I rooted my Q but I'm in the process of trying to add AOSP's Jelly Bean ROM ( http://forum.xda-developers.com/showthread.php?t=1776202 ) and use CM9's Trebuchet Launcher ( http://forum.xda-developers.com/showthread.php?t=1410674 ).
I don't want to get in a position where its all on there and I can't navigate the damn thing. The goal is to use what you provided along with these other resources and work it wirelessly via an app like tablet remote or droid input type app.
mrjaymillz said:
Can you provide us with the link to your keyboard page so I can mimic these steps on my Q. Also to navigate around on the Nexus Q does it still require a USB mouse to be plugged in to it? I rooted my Q but I'm in the process of trying to add AOSP's Jelly Bean ROM ( http://forum.xda-developers.com/showthread.php?t=1776202 ) and use CM9's Trebuchet Launcher ( http://forum.xda-developers.com/showthread.php?t=1410674 ).
I don't want to get in a position where its all on there and I can't navigate the damn thing. The goal is to use what you provided along with these other resources and work it wirelessly via an app like tablet remote or droid input type app.
Click to expand...
Click to collapse
Sorry, I mean the keyboard page on my website: davidnhutch.com/nexusq, click on Keyboard > Special Keys.
Basically, the "menu" button on android is mapped to the same keycode as the "menu" button on Windows keyboards, which usually has an icon that looks like a drop-down menu with a pointer hovering over it. (http://en.wikipedia.org/wiki/Menu_key)
You also can do all this from the command line without ES File Explorer, I'm just trying to make it a bit more visual, plus, ES is useful.
I am very interested in what you described you are working on, as I am hoping to try the same thing when I get some time. Please post your results and steps!
davidnhutch said:
Sure, happy to. I'll include in greater detail than an expert hacker needs, so it's more noob-friendly.
First you need ES File Explorer app (get es_file_explorer_v1_6_1_7.apk or latest version from the publisher at http://www.estrongs.com/en/download.html).
adb connect to your device if not already. Type "adb devices" to check you are connected.
adb install the ES File Explorer .apk, and run it using the Trebuchet launcher.
Press "settings" (see my keyboard page to see how to do that). Scroll down and click Settings and enable "Up to root". Also enable "Root Explorer". OK we're done here for now, we'll use this app later.
Download this file: http://www.davidnhutch.com/tablet_core_hardware.xml. It's one of the .xml permissions files from the Nexus 7. You may also try other .xml files from other devices at your own risk. Or you can try mine, I guess also at your own risk.
Let's go back to adb. "adb shell"
"su"
"mkdir /sdcard/permissionsbackup"
"cat /system/etc/permissions > /sdcard/permissionsbackup"
"exit"
"exit". You should now be out of shell but still in the command window.
"adb push <path-to-that-xml-file>/tablet_core_hardware.xml /sdcard/tablet_core_hardware.xml"
"adb shell"
"su"
"cat /sdcard/tablet_core_hardware.xml > /system/etc/permissions/tablet_core_hardware.xml"
If you want, check it's there: "cd /system/etc/permissions" "ls"
"exit"
"exit"
Next we will change the file permissions for that file we just copied. Open ES File Explorer, click "Up" once to get to the root directory, click System > etc > permissions. Right click or long-press on tablet_core_hardware.xml. Scroll to the bottom of the list that comes up and select Properties. Click the Change button. Select the following boxes, and only the following boxes: User read, User write, Group read, Other read. Click OK, OK. The other files in that directory also need to be rw-r-r, but they should be fine.
Go to Settings > Apps > All > Google Play Store
Click Clear data
Reboot the Q by typing "adb reboot". If you did that using adb-over-wifi, then you'll probably need to do the "adb connect" thing again to reconnect.
Open Google Play. If it's still not working (still shows only a few apps), then continue.
Go to Settings > Apps > All > Google Play Store
Click Clear cache if it lets you, then click Force stop. DO NOT Clear data
Go back once and go to “Google Services Framework”
Click Clear data then Force stop
Reboot the Q again in the same way. After rebooting, my Nexus Q worked with gPlay just fine! However if you still don't see new apps, continue.
Go to Settings > Aapps > All > Google Play Store
Clear Data if it lets you
That's it! Now just Open Google Play, login and you should be able to see and download almost any app either directly on the Q or remotely through a browser on your computer. You may need to download just one app (any app) in order to be able to get the remote download via browser thing working, as Google Play appears to update its knowledge of which devices you have only when you download something.
Click to expand...
Click to collapse
Hey David, the .xml file you linked isn't downloadable, can you take a look into this? Also can you provide some clarification on steps 6-15 above, do I enter ADB then type su and everything else as one command? Can you provide a command prompt code showing every entry step by step?
Also as a side not I can't open google play on the launcher or a matter of fact I can't even get a keyboard to show up on the screen to sign in to my google account. Any ideas? I am using a wireless mouse to navigate and tablet remote via my nexus 7 for other inputs.
Like the previous post stated... The xml file isn't available. Can someone post theirs please?
Sent from my Galaxy Nexus using xda app-developers app
[Edit]
I went ahead and downloaded an AOSP Nexus 7 ROM and extracted the file for myself. I don't know what Box's limitations are, but here's a link to the tablet_core_hardware.xml
https://www.box.com/s/e5e0da606448340fd736
xMemphisx said:
Like the previous post stated... The xml file isn't available. Can someone post theirs please?
Sent from my Galaxy Nexus using xda app-developers app
[Edit]
I went ahead and downloaded an AOSP Nexus 7 ROM and extracted the file for myself. I don't know what Box's limitations are, but here's a link to the tablet_core_hardware.xml
https://www.box.com/s/e5e0da606448340fd736
Click to expand...
Click to collapse
Thanks for the .xml file, box link works with no issues. By the way would you happen to have any ideas on how to get a keyboard to appear on screen for the nexus q? Currently I can't type/enter any information I can only navigate with my wireless mouse. Clicking on Gmail/Google Play/ Messages/ or anything else that requires a keyboard just seems to close the program within 5 seconds (almost like a force close just without the error message).
mrjaymillz said:
Thanks for the .xml file, box link works with no issues. By the way would you happen to have any ideas on how to get a keyboard to appear on screen for the nexus q? Currently I can't type/enter any information I can only navigate with my wireless mouse. Clicking on Gmail/Google Play/ Messages/ or anything else that requires a keyboard just seems to close the program within 5 seconds (almost like a force close just without the error message).
Click to expand...
Click to collapse
I didn't get a chance to play with it too much yesterday, I would imagine that if you install a 3rd party keyboard and set it to your primary input method it (might) work. I'm going to have a better chance to really look at the Q tonight here in a few hours, so I'll report back with what I can figure out.
[Edit]
I still have had no time to test this yet. The company I work for is at deadline with new software and we have been working 65+ hour weeks here recently, so my Q has just been sitting there. I'm still anxious to test it, but it might still be a few days before work slows back down and I can really get after it again.
mrjaymillz said:
Hey David, the .xml file you linked isn't downloadable, can you take a look into this? Also can you provide some clarification on steps 6-15 above, do I enter ADB then type su and everything else as one command? Can you provide a command prompt code showing every entry step by step?
Also as a side not I can't open google play on the launcher or a matter of fact I can't even get a keyboard to show up on the screen to sign in to my google account. Any ideas? I am using a wireless mouse to navigate and tablet remote via my nexus 7 for other inputs.
Click to expand...
Click to collapse
Hm, weird that two people have said the .xml file is not downloadable -- I tried today and yesterday and it was available both times. Maybe the hosting site was down or something. Anyway it looks like someone else offered the same .xml file at another link so we're all set. I'll leave the .xml file there for a year or so though.
Steps 6-15: Yes, enter everything as quoted. No extra "adb" or "su" or anything is needed, other than what I wrote there. Just follow one step at a time, typing each one and then hitting enter. Shouldn't need a command prompt code entry as it is already, just without the code tags and with extra double-quotation marks. Please let me know if there are any errors though.
As for your last paragraph, it seems there are two issues. 1) Not being able to open gPlay on the launcher. Can you please provide more info? What happens? Does it try to open then crash? Is the gPlay app missing? 2) Can't get a keyboard to show up on the screen. -- You will never have an on-screen keyboard on the Q. You need an external keyboard, plugged into the USB port. If you want mouse + keyboard simultaneously, you need a "unifying mouse and keyboard wireless receiver" -- just search amazon for that -- what it is is a mouse+keyboard with just one USB dongle that serves both.
Don't think this will get off topic, but if Google updates the software to Jellybean and adds all the the things you can do in the video, will this method still work?
On a side note, dont think google will add all the functionality as you showed on the video.
Edit: Why is Trebuchet needed for this?
Sent from my ADR6425LVW using Tapatalk 2
300k said:
Don't think this will get off topic, but if Google updates the software to Jellybean and adds all the the things you can do in the video, will this method still work?
On a side note, dont think google will add all the functionality as you showed on the video.
Edit: Why is Trebuchet needed for this?
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
You're right, you technically don't need Trebuchet. It just makes life easier than launching everything (e.g. gPlay) via "adb shell am start ..." commands from your computer.
Regarding Google updating to JB, perfectly possible. Possible that everything will be standard in the next Q hardware release. However the real questions are, why was this functionality not included in the first place? Why was the hardware so very limited by the software? And the bigger question, why was the public release of the first Nexus Q sales indefinitely postponed? Presumably they are coming out with something better than what they showed at IO. Whether it's much better or just marginally better remains to be seen.
The best app/function in the video is being able to use OnLive (3D streamed games) in my opinion. Now, OnLive is expensive and I did have a few problems with the keyboard mapping, the mouse not working while OnLive was playing, etc, but it works and shows the potential for streamed games. The Q doesn't have to be the core device either, presumably a tablet would work too. I just think they should have done the hardware differently and made an Xbox competitor (Xsphere?) instead of a competitor to precisely no-one.
On steps 8 and 9 I get
sh: cannot create /sdcard/permissionsbackup: Is a directory
I don't think that I am typing it in wrong and I have copied and pasted as well just in case...The directory is made correctly... Thanks for your help.
"mkdir /sdcard/permissionsbackup"
"cat /system/etc/permissions > /sdcard/permissionsbackup"
I have tried following these directions to temporarily get the Advanced menu back for the CM10.2 nightlies so I can enable dock audio. I keep getting the following error:
Error type 3
Error: Activity class {com.cyanogenmod.device/com.cyanogenmod.device.DeviceSettings} does not exist
It seems to work on other VZW Note 2 Android 4.3 based roms, but I cannot get it to work on our nightlies.
Is there an additional file or entry missing somewhere?
Thank you for any assistance.
Hopper8 said:
Ok, for anyone who is missing the 'Device settings' or 'Advanced Settings' menu (since it was left out of CM10.2. See here for more details.) These settings include mDNIE screen settings and backlight control. I for one use them.
Anyway: To get these settings back, follow these steps.
1. Download attached apk (I took it from Rootbox 4.2.2, but it works just the same on 4.3).
2. Paste it into /system/app, set permissions to rw-r--r-- and reboot.
3. Enter terminal Emulator, and type:
Code:
su [enter]
am start -n com.cyanogenmod.settings.device/.DeviceSettings [enter]
(obviously don't type [enter], press the enter key....)
4. Device Settings will open up, set whatever you desire
Note: to re-open the app, you will have to do it throught Terminal Emulator again. There's no other way of launching it that I could find, even Titanium Backup doesn't recognise it as able to run.
Big thanks to Unisexist6969 and Markox89 for helping figure this out
Edit: most users of a launcher such as nova or similar should be able to add a homescreen shortcut using nova activities shortcut. Personally this doesn't work for me, I'm not sure why. The method above will work regardless of using a different launcher, or if someone (like myself) doesn't have the option to add a shortcut, or if they plain don't want a homescreen shortcut (also like myself).
Click to expand...
Click to collapse
mising said:
I have tried following these directions to temporarily get the Advanced menu back for the CM10.2 nightlies so I can enable dock audio. I keep getting the following error:
Error type 3
Error: Activity class {com.cyanogenmod.device/com.cyanogenmod.device.DeviceSettings} does not exist
It seems to work on other VZW Note 2 Android 4.3 based roms, but I cannot get it to work on our nightlies.
Is there an additional file or entry missing somewhere?
Thank you for any assistance.
Click to expand...
Click to collapse
I'm running the Eclipse ROM (which I believe is based off of CM 10.2), and I had this issue before I restarted the phone. After restarting, it fixed the problem. If this issue persists after restarting your phone, maybe someone else can chime in?
Sorry I couldn't be of more assistance.
SonOfUncleSam said:
I'm running the Eclipse ROM (which I believe is based off of CM 10.2), and I had this issue before I restarted the phone. After restarting, it fixed the problem. If this issue persists after restarting your phone, maybe someone else can chime in?
Sorry I couldn't be of more assistance.
Click to expand...
Click to collapse
Rebooting didn't help, I am back on a TW ROM for the moment since I use my dock everyday, but plan on trying Eclipse or PAC this weekend.
Sbrissen said he is going to put the option back in the settings once they figure out where they want to put it, so I just keep flashing the nightlies every few days to check.
Thank you for your input though.
[SIZE=+2]This thread has been created for Questions & Answers/Troubleshooting
Specific to:
And it's components:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/SIZE]
[SIZE=+1]
ArchiDroid 2.X Development Thread
ArchiDroid 1.X Development Thread
Please feel free to share issues, questions and offer help
If you get an answer to your question, don't forget to hit
[/SIZE]
1. Questions/Issues without ArchiDroid version number may/will be ignored. Don't forget to tell us which ArchiDroid (1.X or 2.X) and which version you're using, otherwise don't expect an answer.
2. All battery questions/tips are allowed ONLY with a full BetterBatteryStats log or screenshot from all it's pages AT LEAST after 5 hours of full deep sleep. We're not magicians and we can't help you without proper information.
3. Respect all users.
Helpful users may be rewarded
From Zero To Hero: Complete Installation/Flashing Guide
This guide covers everything you need to do, to unleash full power of your SGS3 with ArchiDroid.
You've obviously heard about "rooting" "flashing" or other strange things. But these tutorials are quite old and it's already much easier to achieve our goals. Instead of flashing old firmwares, using old methods I'll guide you through complete flashing of ArchiDroid.
First of all you obviously need:
- Working Samsung Galaxy S3 GT-I9300 International Version
- Working computer with Windows OS
1) Connect your phone to your pc and give it some time for installing drivers. When it's finished reboot your pc. It's important. After reboot check if windows can "detect" your phone, for example by entering "My Computer" section. It should be available as portable device.
2) Download newest ArchiDroid .zip file and put it on your phone, I strongly suggest your internal memory.
3) Disconnect your phone from the pc.
4) Download attached Odin3 Software and unpack it's content on your pc: View attachment 1879375
5) Click with your right mouse button on Odin3 executable and select "Run as administrator"
6) Download latest PhilZ Touch Recoveryhttp://forum.xda-developers.com/showthread.php?t=2002953 in .tar.md5 format and put it in the odin's folder or somewhere nearby. DON'T UNPACK IT! File should look like this: philz_touch_4.92.8-i9300.tar.md5
7) Click on the "PDA" button in odin and select your recovery in .tar.md5 format. Also untick "Auto Reboot" option. DO NOT TOUCH ANY OTHER BUTTONS OR CHECKBOXES!
8) Turn off your phone
9) Hold Volume Down + Home + Power buttons to enter Download mode. It should say "Downloading, do not turn off target"
10) Connect your phone to your pc. It should be shown in Odin's message log as f.e. "<ID:0/003> Added!!".
11) Hit "Start" button and be patient. It shouldn't take longer than a few seconds. Your phone won't automatically reboot, wait for progress bar to reach the end and move to the next point.
12) Reboot into recovery by holding combination: Vol-Up + Home + Power. Hold it until you see "Samsung Galaxy S3" logo (about 7 seconds).
13) Click on Wipe Data/Factory Reset => Clean to install a new rom. WARNING! From this point you'll be unable to load your current system as it wipes everything available (your internal/external card will remain untouched). Please make sure that you're ready for this step and that you have right .zip file available.
14) After cleaning hit Install zip => Choose zip from sdcard. Then navigate to your location of archidroid.zip file and open it. Now you'll be able to set various options in AROMA "Setup Wizard", just follow the steps and ArchiDroid should properly flash and reboot your system after installation.
15) First boot takes quite longer than usual, I'd say maximum of 5 minutes.
Notice: This procedure is required ONLY for first flash of ArchiDroid. If you want to update ArchiDroid then simply download latest zip, copy it to your phone, reboot into recovery (or by holding combination above) and select "Install zip". Don't forget to select "ArchiDroid Update" mode to avoid wiping of data. No full wipes are required in order to update ArchiDroid.
In case of any weird rare problems, or if you want to start from scratch...
1) Download latest Samsung firmware for i9300, it doesn't have to match your region. Latest = Highest changelist. You can try unofficial Samsung repo for i9300 (with changelist number) or official, without changelist number. It doesn't have to be exactly the newest one but preferably one of the newest (some regions still have firmwares from more than one year ago...). Also try to use XX(EMG4) PDA instead of f.e. UB(EMI1) because XX are international.
2) Unpack .zip file you've got, extract .tar.md5 file from that, ignore kies file.
3) Enter recovery and wipe /data. It can also be done through stock recovery (Factory reset) but it's important to turn off your phone after cleaning instead of rebooting it.
4) Enter download mode after wiping/formatting /data
5) Connect your phone to your PC and load your .tar.md5 file as PDA in Odin, then start flashing. It can take up to 5-10 minutes because it's a big file.
6) Let it boot properly, when you're sure everything works repeat custom recovery & ArchiDroid flashing.
Above steps update low-level parts of your phone, f.e. bootloader, params partition, tz partition and hidden partition. While it's highly unlikely that any of these components would cause problem it's highly proposed to update low-level parts of your phone from time to time, just to ensure everything works properly. Custom roms don't update these partitions, as they're only being flashed during flashing original Samsung firmware via Odin, flashing custom stock roms won't work here. Also you get "maximum" cleaning, because literally you're overwriting everything on your phone.
If you have any further problems or questions feel free to ask them in this thread.
[SIZE=+1]ArchiDroid Core[/SIZE]
Q: When I want to use "Freedom", "AdAway" or other similar app which edits /system/etc/hosts file, it always fails, what's the reason?
A: ArchiDroid uses it's own built-in AdBlock, which is widely described in development thread. Therefore to prevent issues and slowing down the network, hosts file are permanently blocked from any modifications. This has been implemented to ensure that you know what you're doing before you mess with hosts file. In most common situations, you can point your favourite hosts editor (such as AdAway) to ArchiDroid's hosts file - /system/archidroid/etc/hosts, as THIS file should be edited INSTEAD of original hosts file. However if you really know what you're doing, you know that adding rules to original hosts file slows down the network dramatically and your app can't be set to use other hosts file, then you can unlock original hosts file through ArchiDroid app bundled with ArchiDroid. However keep in mind that I don't support this method, as it's deprecated, obsolete, dirty and ineffective method of setting rules. If you want to do it in proper way, use ArchiDroid's enhanced hosts mentioned above.
Q: I get "set_perm_rescursive some changes failed" error during flashing ArchiDroid. What's going on?
A: Simply update your recovery to latest version. Latest CWM, TWRP or PhilZ Touch Recovery work properly. Initial support for this function was added in ClockWorkMod 6.0.4.4.
Q: Whoa! What happened to colors in ArchiDroid, why they're "blacked out", "dimmed"? I want my stock colors back!
A: ArchiDroid in default configuration applies custom MDNIE settings, which change displayed colors. Samsung (and AOSP) uses over-satured, plastic, vivid colors, while ArchiDroid uses balanced and natural colors for our super amoled. It's up to you if you like it or not but if you decide to flash ArchiDroid it will come with natural balanced colors. You can change them very easily in Display Options (ArchiDroid 1.X) or in Advanced Settings (ArchiDroid 2.X).
Q: How to use delta upgrades provided by ArchiDroid?
A: Simply open any terminal, for example Android Terminal Emulator, type "su" and then "adflash" command. You'll be able to set various options and get exactly what you want. Remember that only "git" mode provides delta upgrades.
Q: My ROM reboots instantly after finishing first boot! What is going on?!
A: As you may know ArchiDroid contains two parts. Android (ROM) and ArchiDroid Backend (init.d scripts written from scratch by me), which works "next to" Android itself. ArchiDroid backend applies some good settings for you and if it decides that a hot (or even hard) reboot is required, it performs it. Hot reboot is always required during first boot from full wipe and sometimes it may be needed also after update mode. You don't need to worry about that, it happens only once after flashing and is totally intended. If you want to learn more please read more about "ArchiDroid Backend" in development thread.
Q: Why this ROM doesn't work with dual boot feature, found in Googy Max, Devil and Siyah kernels?
A: It does, but only as 1st ROM. ArchiDroid includes AROMA wizard, which is compatible only with flashing as 1st rom. Luckily you can swap it to the 2nd rom after flashing but you always must flash it as 1st. This is known issue with dual boot, as it doesn't work properly with aroma-based roms. ArchiDroid is not faulty here.
Q: I have a suggestion! Could you please implement it?
A: ArchiDroid focuses on stability, performance, battery life and out-of-box solution. It gives you literally out-of-box well tweaked and ready-to-go system with nearly everything you'd ever need. However I've already implemented many suggestions proposed by a community, so feel free to let me know if you have a nice idea, I'll tell you what I think and if I'm able to implement it.
Q: How can I use my own settings for Yank555 Kernel?
A: You should download full Yank's kernel from his thread and flash it after flashing ArchiDroid. If you select Yank's kernel in aroma then it comes with a preset chosen by me, so you should reflash it on your own.
Q: Which settings are best?
A: ArchiDroid offers you a power of flexibility and respects your choice. All default settings are proposed by me, according to my taste and what I think is "the best" for you. In most scenarios you'll be very satisfied with my settings, even if you won't touch anything during flashing in aroma. However you have a freedom of choice, bunch of options to choose from and even a few presets, which give you full choice between performance and battery. For now I can assure you that default settings are already well tweaked and optimized, so I highly suggest staying with them, unless you know what you want . The same goes with various "magic tweaks" and third-party modifications. I suggest to avoid them or mention them in development thread so I'll tell you what I think about them. Unfortunately most of these "magic tweaks" cause more harm than good.
Q: I have excessive battery drain! What to do?
A: ArchiDroid in default installation gives you BetterBatteryStats app, which is extremely useful for finding out what causes such high battery drain. You should launch BBS app at least one time (to initialize cache) and then reboot your whole OS right before going sleep. After boot enter your pin of course and let your phone literally "sleep" as deep as it can, of course with network turned on, because we want to get as close score as possible but without any useless apps running in the background. After night or at least a few hours in such total deep sleep unlock your phone, launch BBS and save log in .txt format. Attach this log to your post and hope for the best, we'll try to help you. All posts regarding battery drain WITHOUT BBS log will be ignored. If you won't provide at least BBS log then don't expect any help at all. ROM itself does not cause any additional battery drain. It literally loses from 0.1% up to 0.3%/hour in deep sleep, with 2G turned on and Wi-Fi turned off. It's your phone and your ArchiDroid. While I can prepare best rom for you I can't control what you do with it. If you kindly ask for finding battery drain culprit - I'll help. If you blame ArchiDroid for battery drain, I'll tell you to change the rom.
Q: Okay, let me fix it by myself. I can see really big values under RILJ, multipdp and sec.fd.wakelock wakelocks. What to do?
A: In general these wakelocks are attached to 3G connection. ArchiDroid supports "fast dormancy" function, which improves your signal and battery life during 2G/3G connection BUT it also needs to be supported on your provider's side. Basicly you have a few scenarios:
1. Your provider supports FD, and you have FD enabled. That's great, you will get better signal and less battery drain compared to non-FD.
2. Your provider supports FD, but you don't have FD enabled. Expect slightly worse signal and more battery drain compared to above option, but that's not a big problem.
3. Your provider doesn't support FD and you don't have FD enabled. Same as above, however in this situation it's great that you disabled FD, as you're avoiding excessive battery drain.
4. Your provider doesn't support FD but you have FD enabled. This is the worst case because you're wasting battery on FD requests, which are never accepted on the provider's side.
There is no general answer if you should have FD enabled or not. We don't know where you live, we don't know architecture of your city, and we don't know your provider. If you think that 3 wakelocks described above in fact appear in your BBS log then you can try to disable FD and see if situation improved. To disable FD open /system/build.prop through any root explorer and find this part:
# Fast Dormancy toggle. If your provider doesn't support it then it may be better for you to uncomment this line
#ro.config.hw_fast_dormancy=0
Click to expand...
Click to collapse
And then remove bolded # from second line, as showed above. If you'd like to enable fast dormancy once again simply comment it out. Reboot is required after these changes. WARNING! These wakelocks are pretty NORMAL if your phone uses 3G. They won't magically disappear, we're talking about excessive battery drain here. If you use 3G often then obviously it will require much more battery than 2G.
And once again. There's no right answer if you either should or should not have FD enabled. You need to find it out youself.
Q: This rom is awesome! Can I gain access to any beta versions? Weekly build is too old for me!
A: Please read GitHub section in development thread. You'll be more than satisfied.
Q: I see that you have many languages in aroma, could you add my own?
A: Personally I make only two translations - English and Polish. All other languages are available thanks to appropriate contributors. If you want to contribute to ArchiDroid project and implement your own language then I'm very happy to hear that and I'm looking forward to merge your strings . You should start with reading dummy.lang, I've attached proper instructions there. It's really easy job but it requires some patience and free time. If you're familiar with github or you want to learn how to use it then I'd be very happy to see a pull request with your language.lang. Otherwise everything you need to do is register at github and edit above dummy.lang file. This will automatically send pull request, which I can merge.
Q: How can I disable these cpu stats on the top?
A: This app is called "Cool Tool", you had an option to disable it in aroma. You can also delete/freeze it with Titanium Backup, or change it's behaviour in app settings.
[SIZE=+1]ArchiDroid 2.X[/SIZE]
Q: When I switch to ART runtime, it automatically switches back to dalvik after reboot, why is that?
A: If you have xposed installed then it forces dalvik. You need either to uninstall xposed or stay with dalvik.
Q: My bluetooth headset doesn't work! I can hear only weird noise or can't hear anything!
A: ArchiDroid 2.X is based on open-source Android sources. It doesn't have many closed-source drivers, while only a few have been reverse-engineered to provide you with functionality of your device. ArchiDroid 2.X will work only with a few BT headsets and it won't change until Samsung releases proper drivers, what is very unlikely to happen in near future. Either deal with it, or stick with a stock-based rom, for example ArchiDroid 1.X.
Q: I think that I found a bug. Could you fix it?
A: First of all, please notice that ArchiDroid 2.X is based on AOSP. Some things may be unfixable, while other are hard to reproduce. If you want to have your issue resolved then you must provide as much information as possible, because if you won't expect answers like "works fine here".
Some things to consider:
a) Have you tried full wipe and clean ArchiDroid installation?
b) Have you tried "Bare Bones" preset during flashing, which gives you clean AOSP installation?
c) Have you tried to reproduce this issue on latest OmniROM nightly build?
If bug exists in nightly then it's global bug and either it's unfixable or will be fixed soon (next release). If bug exists in normal installation but doesn't exist on bare bones preset then it may be possible that third-party ArchiDroid function causes issue. In this case I'd be very happy if you could make some basic tests and try to find root of this issue. If bug exists also on bare bones preset but doesn't exist on latest nightly then it's ArchiDroid-specific bug and should be fixed in sources. It's ultra important to provide at least answers to following three questions. If you're advanced user it'd be also cool if you can provide a logcat (if possible) and more specific information f.e. how to reproduce a bug. 99% of the ROM problems are caused by the base, therefore I can't directly fix them and you should forward them directly to the OmniROM. Especially if you can reproduce bug in b) and c) steps.
[SIZE=+1]ArchiDroid 1.X[/SIZE]
Q: Camera or Wi-Fi doesn't work right after flashing with custom kernel. What's the reason?
A: In some rare scenarios it looks like flashing custom kernel in aroma may cause such issues. Users say that flashing stock kernel, first boot & loading camera, and then flashing custom kernel helps, however I couldn't reproduce camera/wi-fi issue, so it's not global bug.
Call recording 1.7.5
Hi,
is there a way to enable automatic call recording (i.e. set the automatic recording of all incoming and outgoing calls)?
Thanks!
Hi JustArchi;
Um using ur omnirom v2.3.2 and i have problem with change to my Runtime dalvik to ART i wanna try ART and im choosing it in developer settings and after i chose my phone reboot but when i checked it is still dalvik. Why İ cannot change my Runtime? Pls help me. How can i use ART?
puHu
bazsoczi said:
Hi,
is there a way to enable automatic call recording (i.e. set the automatic recording of all incoming and outgoing calls)?
Thanks!
Click to expand...
Click to collapse
I'm afraid that you need a third-party app for that or heavily modified stock dialer.
puhu said:
Hi JustArchi;
Um using ur omnirom v2.3.2 and i have problem with change to my Runtime dalvik to ART i wanna try ART and im choosing it in developer settings and after i chose my phone reboot but when i checked it is still dalvik. Why İ cannot change my Runtime? Pls help me. How can i use ART?
puHu
Click to expand...
Click to collapse
If you have installed xposed then it forces dalvik. Either uninstall xposed and use ART or keep xposed and use dalvik.
Can you help me with my DPI issue?
Sent from my GT-I9300 using xda app-developers app
Ahad Ejaz said:
Can you help me with my DPI issue?
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Wait for 1.7.5.1 hotfix.
JustArchi said:
If you have installed xposed then it forces dalvik. Either uninstall xposed and use ART or keep xposed and use dalvik.
Click to expand...
Click to collapse
Thats mean xposed doesnot work with art right?
puHu
puhu said:
Thats mean xposed doesnot work with art right?
puHu
Click to expand...
Click to collapse
Yup.
How do I run ArchiDroid_FstrimAll.sh on ArchiDroid V2.3.3
How do I run ArchiDroid_FstrimAll.sh on ArchiDroid V2.3.3
I open Terminal Emulator, type in
Code:
su - root
change directory to ArchiDroid/Scripts folder, and run
Code:
./ArchiDroid_FstrimAll.sh
I get a Permission Denied error. I can't seem to upload my screenshot now, but my original post has a screenshot at http://forum.xda-developers.com/showthread.php?p=49336985#post49336985
Thanks
mvariyawa said:
How do I run ArchiDroid_FstrimAll.sh on ArchiDroid V2.3.3 (running OmniROM).
I open Terminal Emulator, type in
Code:
su - root
, change directory to ArchiDroid/Scripts folder, and run
Code:
./ArchiDroid_FstrimAll.sh
I get a Permission Denied error. I can't seem to upload my screenshot now, but my original post has a screenshot at http://forum.xda-developers.com/showthread.php?p=49336985#post49336985
Thanks
Click to expand...
Click to collapse
You have two ways for that.
1. Use any script manager, for example root browser included with ArchiDroid. Navigate to proper folder and execute script as root.
2. Use Android Terminal Emulator. Type "su" and then "sh /data/media/0/ArchiDroid/Scripts/ArchiDroid_FstrimAll.sh"
Eventually you can also chmod this script to 755.
I'll add 755 chmod to updater-script, as it should be 755 from start.
Whats the best Recovery now,, CWM? TWRP? or Phils Recovery and can u post the link thanks,, :good: oh i have Philz Touch 5 at the moe,,, cwm base 6.0.4.4
The King Tyrone said:
Whats the best Recovery now,, CWM? TWRP? or Phils Recovery and can u post the link thanks,, :good:
Click to expand...
Click to collapse
I'm using PhilZ Touch Recovery but any recovery, which you mentioned will work properly, as long as it's the latest version.
JustArchi said:
Yup.
Click to expand...
Click to collapse
I uninstalled xposed and tried many times for change to ART but after i reboot it is still dalvik it doesnot change :'(
puHu
puhu said:
I uninstalled xposed and tried many times for change to ART but after i reboot it is still dalvik it doesnot change :'(
puHu
Click to expand...
Click to collapse
Did you uninstall it completely? I can assure you that it works with no-xposed right after flashing.
Genius
JustArchi said:
You have two ways for that.
1. Use any script manager, for example root browser included with ArchiDroid. Navigate to proper folder and execute script as root.
2. Use Android Terminal Emulator. Type "su" and then "sh /data/media/0/ArchiDroid/Scripts/ArchiDroid_FstrimAll.sh"
Eventually you can also chmod this script to 755.
I'll add 755 chmod to updater-script, as it should be 755 from start.
Click to expand...
Click to collapse
You are a genius. Method 1 worked perfectly. Thanks
JustArchi said:
Did you uninstall it completely? I can assure you that it works with no-xposed right after flashing.
Click to expand...
Click to collapse
Yes i uninstalled it competely with Titanium backup and reboot and i changed Runtime to ART and reboot but after reboot i checked it still dalvik :'(
puHu
puhu said:
Yes i uninstalled it competely with Titanium backup and reboot and i changed Runtime to ART and reboot but after reboot i checked it still dalvik :'(
puHu
Click to expand...
Click to collapse
You should try with full wipe and unticking xposed in aroma then. Sorry, can't help much.
HELP!!!
its happend again!!!! everytime i install or update archy rom, it always boots in to Recovery! why dos it do that?? any other roms dont,, its just this one,,,,,, how to fix thanks UPDATE!!!!!!!!!!!!!!!!!!!!!!! i found the problem!!! i unticked Xposed Framework and flashed again and now i have boot screen! PHONE IS ALIVE!!! :d
Hello all, I got my Amazfit Pace a few days ago and the first thing that I wanted to do after flashing PACEified was get proper on-device root, as you know right now PACEified comes with adb root shell so we can modify the watch however we want from and adb shell but that means we're always dependent on another device for doing so, apps on the watch have no way of getting root access.
I am actually amazed that no one else even seemed to have any interest in achieving this as it was somewhat easy for me to figure it out and now I'm sharing it with y'all.
Requirements: being on a ROM that has adb root (ex: PACEified) or ability to boot the temproot kernel.
WARNING: If the stock kernel has dm-verity the temproot then install SuperSU method will lead to the device refusing to boot, I do not know whether it does or not.
Disclaimer: I am in no way responsible for any damage this can or will cause to your watch and/or phone, you are the only one responsible for your own actions.
Anyway here's the steps to getting SuperSU 2.79 fully working on your watch:
Download the attached zip file.
Copy the zip file to the watch.
Open a terminal/cmd/powershell in the folder where your adb binary is located.
Run the following commands in order:
Code:
adb root
Code:
adb remount
Code:
adb shell
Now you are running shell commands on the watch itself so do:
Code:
busybox unzip /sdcard/SuperSU-2.79-amazfit.zip
Code:
cd /sdcard/supersu/
Code:
sh root_amazfit.sh
Done, reboot and enjoy!
I hope this helps others as it did help me and I do hope I didn't make any mistake.
Credits:
Chainfire for SuperSU
Neuer_User for PACEified
KevinX8 for the SuperSU 2.79 zip for Android Wear (I used that one cause it already is setup to allow all by default)
Everyone else that I can't remember right now
List of useful root apps for the Amazfit:
MiXplorer-useful file manager with addons and root file management options: https://forum.xda-developers.com/showthread.php?t=1523691
Kernel Adiutor 4 Wear-very popular kernel options management app, won't give too many options since the stock kernel is actually quite limited but still allows tweaking a few things like changing the schedulers and their options, enabling init.d and other such stuff: https://forum.xda-developers.com/android-wear/development/app-kernel-audiutor-4-wear-t3126122 (I only tested this version but the latest normal Kernel Adiutor version might also work perfectly since the interface seems pretty friendly with low resolutions)
Advanced Settings for Watch-provides a plethora of options like Bluetooth and WiFi settings management, reboot menu and most importantly PACKAGE MANAGEMENT and by that I mean it doesn't just have the normal app settings menu that allows you to clear data/cache, force stop or disable/uninstall apps but ALSO INCLUDES A PACKAGE INSTALLER for installing apks straight on the watch: https://play.google.com/store/apps/details?id=com.sssemil.advancedsettings&hl=en (get the wear apk from inside the main apk, it is located in /res/raw just open the phone apk as an archive also WARNING: many menus/options make it crash cause this is not Android Wear)
Another one.
Wich are the benefits of doing that?
jmpcarceles said:
Wich are the benefits of doing that?
Click to expand...
Click to collapse
Same as on any other rooted Android device.
A few apps I have on the watch that use root are:
MiXplorer-file manager
Kernel Adiutor-can improve battery life/performance by messing around with it a bit
Root Essentials (the wear part sent from inside the phone apk)-it's great for uninstalling apps and such
Hello. Stock ROMs can boot "temproot kernel"? Could you please like to where it's explained? Thanks.
Ranomez said:
Same as on any other rooted Android device.
A few apps I have on the watch that use root are:
MiXplorer-file manager
Kernel Adiutor-can improve battery life/performance by messing around with it a bit
Root Essentials (the wear part sent from inside the phone apk)-it's great for uninstalling apps and such
Click to expand...
Click to collapse
Nice.
MiXplorer is my mobile favourite Android explorer.
I don't know the other apps, i must learn about it.
Any suggestions about them, Kernel auditor seems very interesting. I have very much problems with my Amazfit battery, last month suddenly i don't get more than 2 days of autonomy
Thx.
lfom said:
Hello. Stock ROMs can boot "temproot kernel"? Could you please like to where it's explained? Thanks.
Click to expand...
Click to collapse
Stock ROM can boot temproot kernel only if old enough version to not have the bootloader locked OR you unlocked the bootloader after, to get the temproot kernel go to the PACEified thread and read the install instructions, it has you booting the temproot kernel on order to flash it and it might be possible to just boot it, root and reboot but I am not entirely sure, if the Amazfit has dm-verity it will refuse to boot after altering the system, I actually didn't think about that when I wrote this guide cause it was 5AM so would recommend flashing a custom ROM.
@Neuer_User does the Amazfit have dm-verity?
Also would you consider adding SuperSU to PACEified in the future?
Double post cause mobile XDA is messed up, delete.
jmpcarceles said:
Nice.
MiXplorer is my mobile favourite Android explorer.
I don't know the other apps, i must learn about it.
Any suggestions about them, Kernel auditor seems very interesting. I have very much problems with my Amazfit battery, last month suddenly i don't get more than 2 days of autonomy
Thx.
Click to expand...
Click to collapse
To be honest MiXplorer just about works but isn't really 100% usable cause things don't fit on screen, looking for a better root file explorer for the watch.
The stock kernel doesn't really allow you to control much cause the stock kernel doesn't seem to have too many features but can still change governor and a few other stuff and if nothing else it can enable init.d if you don't already have it enabled, I use the Kernel Adiutor 4 Wear version but TBH I think the normal one should be just as usable.
For your battery problem you could try deleting some unneeded apps like the Mi Home or the Chinese radio one (if on Chinese ROM/PACEified) and maybe Greenify will also work but wouldn't really put my bets on it, perhaps try using some battery saving scripts?
Right now I'm looking for an apk installer...I have a solution already but it's probably the worst one possible: a init.d script that checks if there are apps in a folder on the internal storage then installs all of them and deletes the apk files but that means you need to reboot in order to install apps, could make crond run the script every hour or so but that would also not be too convenient so either a script runner or a apk installer would be best.
BTW after uninstalling apps from the watch using a root app you need to crash the launcher or it will still show the icons for the uninstalled apps.
Also I'm working on improving the script to add safety checks (if someone tries to run it without the other files in the same folder right now it would most certainly end up in a mighty bootloop, fortunately a bootloop with adb access so easy to fix but still not great, I made that script in like 5-10 min after I manually did it on my own watch) and add more features like installing a newer busybox version and linking missing applets (unzip for example).
Updated 2nd post with a few useful apps, one of them finally giving us the power to install apps straight on the device, will publish the new version of my script in a few days, have been working on adding A LOT of new features and now I kinda need to concentrate on the project for my Android class for a bit, sorry for the delay.
Ranomez said:
Updated 2nd post with a few useful apps, one of them finally giving us the power to install apps straight on the device, will publish the new version of my script in a few days, have been working on adding A LOT of new features and now I kinda need to concentrate on the project for my Android class for a bit, sorry for the delay.
Click to expand...
Click to collapse
Hi Ranomez,
When do you plan to publish the new script for local root?
Thx in advance.
Merry Xmas.
jmpcarceles said:
Hi Ranomez,
When do you plan to publish the new script for local root?
Thx in advance.
Merry Xmas.
Click to expand...
Click to collapse
Most probably next week, haven't really had time to work on it with the last week of college before the holidays and the fact that I bought Xenoblade Chronicles 2 on launch day and it's been eating most of my free hours, lol, sorry for the delay, anyways the current script still works for simply rooting but will give a no such file or directory error if init.d isn't already enabled, just ignore that.
Thank you @Ranomez
I've just tried your local root using the temproot kernel on the latest stock rom, and it worked great. So, I can say my pace doesn't have dm-verity enabled?
btw, SU was added to Stockfied, Pacefied and Stratosfied, just needs to be enabled.
Ok lets first explain the situation
I've been dabbling with Tasker (Paid for version)- getting some automation depending on certain situations (mainly stuff like 'If I'm @ {location} get volumes set high' or ' If Unread msg then vibrate my Amazefit bip watch' - Nothing too complicated using variables / javascript etc)
One situation I want to attempt though is 'If Gpay app is started - turn on NFC, but when I leave the app - turn NFC off'
Now I already know there are 2 'main' ways I can turn on/off NFC in Tasker.. either use 'AutoInput plugin' or use 'Secure Settings'
- I've tried with Autoinput plugin but the problem is that with the free option, you need to watch an Ad every day to use it but of course I can pay for it (its only a couple of quid)
However you can't Install it & pay for it directly from within the plugin - you need to install yet another App (AutoApps) first - & although this one is free - I just don't like adding more bloat to my phone than necessary. Adding both the plugin & this additional App adds (although only a 'minor' amount) up to 20Mb
The other method is give Tasker 'Secure settings' permission
- So I read the 'What to do to give 'Write Secure Settings Permission' to Tasker' (enable Developer mode > Usb Debugging > Install ADB on PC etc etc) & it looks simple enough,
But (a loooong time ago) I tried other 'hacks' & it ended up disastrously (probably I did something wrong with missing a step or something) & I just want to make sure that it IS as simple as it seems and also ask how safe is it
for example
* If I type in the command in ADB - could something go wrong & could it crash/brick the phone ?
* Is this permanent - ie if I turn off/on phone or if I get an OTA update & phone restarts - will it stay, or will I have to repeat the ADB command each time ?
* Will this 'break' official OTA updates (whether security &/or Android firmware) - I once did a firmware update with a step that used ADB (IIRC) & it broke something that prevented any updates from happening
- official OR manual firmware updates
Any help/advice would be appreciated
Cannon_Foddr said:
* If I type in the command in ADB - could something go wrong & could it crash/brick the phone ?
* Is this permanent - ie if I turn off/on phone or if I get an OTA update & phone restarts - will it stay, or will I have to repeat the ADB command each time ?
* Will this 'break' official OTA updates (whether security &/or Android firmware) - I once did a firmware update with a step that used ADB (IIRC) & it broke something that prevented any updates from happening
- official OR manual firmware updates
Click to expand...
Click to collapse
ADB is the door to your phone's Android. It's a tool not meant to be used by John Doe. Wrongly used you can brick your phone. Hence it's by default disabled.
1. Yes, using ADB you can render your phone absolutely useless. If you e.g. enter
Code:
adb shell rm -rf /
then phone gets totally wiped ( really all gets destroyed, it gets naked ) - you can throw it into electric waste.
2. ADB commands aren't persistent, but their results may be.
3. ADB itself breaks nothing: it's a driver installed on your computer that let you access Android's files and launch Android executables.
Thanks for the reply
I doubt I'll use THAT command.
I forgot to mention what tasker's command is
adb shell pm grant net.dinglisch.android.taskerm android.permission.WRITE_SECURE_SETTINGS
Not 100% sure about your last comment though.
ADB allows access to android files so changing android files could break things, which I'm worried about especially with OTA updates etc. (my last phone stopped getting OTA updates when I rooted it despite using official firmware)
However IF I understand the above command all this does is tell the android operating system ('android') to only give the tasker app (which 'Real' name is 'net.dinglisch.android.taskerm') the rights ('permission') to access the required settings ('WRITE_SECURE_SETTINGS') which the NFC on/off toggle is part of (settings >connected devices > connection preferences> nfc) & 'shouldn' t' affect any other files such as OTA (unless OTA is also part of secure setting?)
@Cannon_Foddr
As I can see you until now haven't understood what ADB is, how it works.
Same probably your understanding of what an OTA is.
Personally never would allow 3rd-party apps ( like Tasker ) to modify sensible system settings: Tasker isn't an open-source app, so you can't control what it does in the last run.
It's simply on you to decide whether Tasker is given that right, or not ...
Can't see why 'open-source' has to do with this
IMHO if Open-source - anyone can release similar apps with added extra hidden code that could spy's on you/steal info etc, but a 'closed sourced' app from a long running developer (tasker been around for 10yrs with over 1mil downloads) must mean people seem to trust him/them & if he was 'dodgy' surely he would've been caught out by now
Anyway the Bottom line seems to be
Safe route: pay for plugin & live with extra bloatware
Or
Risky route: give access to secure system resources, see what happens & keep fingers cross nothing does
Thanks for your replies.. I think I may have to sit down & have a long hard think which route I feel more comfortable with
I have been using Automate for about 4 months now. I granted it WRITE_SECURE_SETTINGS and I have not noticed any modifications in my system. Granted I may have not looked specifically for them but as far as braking the system or disruption of OTAs no issues so far
DennisHarrows said:
I have been using Automate for about 4 months now. I granted it WRITE_SECURE_SETTINGS and I have not noticed any modifications in my system. Granted I may have not looked specifically for them but as far as braking the system or disruption of OTAs no issues so far
Click to expand...
Click to collapse
I assume you had to do something like Taskers command then to grant the secure settings
( "adb shell pm grant net.dinglisch.android.taskerm android.permission.WRITE_SECURE_SETTINGS" )
Cannon_Foddr said:
I assume you had to do something like Taskers command then to grant the secure settings
( "adb shell pm grant net.dinglisch.android.taskerm android.permission.WRITE_SECURE_SETTINGS" )
Click to expand...
Click to collapse
Automate is straight forward, there is a toggle for "modify system settings" needed for some tasks to run and one you run the ADB command, it's done