I have started having the LOS issue since rooting on the 10-2. I have had alogcat running in the background while waiting for a LOS instance to occur. I have the alogcat buffer set to radio. I don't know if it's of any use to anyone but I am attaching it anyway. I am also going to attach a log with the buffer set to events and main to try to get as much information as possible when a LOS instance occurs. I am not a developer and I don't know much about this stuff but I want to contribute to figuring it out if at all possible. Let me know if there is anything else I can do to help. Thanks.
Post #2 alogcat logs
Post #3 ksmg pastebin links
Post #4 reserved for bugreport.txt
Edit:
Just fyi I've had my phone since release day, rooted using Heimdall in Ubuntu with Zedomax v3 and currently running Midnight rom v2.
PRL 60681
Not sure if this will matter or not if they release future versions of the E4gt, Hardware version D710.10.
Edit #2
I will try to add the logs/kmsg output pastebin links to the appropriate post at the beginning of the thread with the original posters name as they are added to the thread.
To get the kmsg output on a rooted phone use terminal emulator, type "su", press enter and allow super user privileges. Then type the command "cat /proc/kmsg".
For a non rooted phone use the guide below from frifox.
Hook up to your PC in debugging mode, have adb at the ready, and do:
"adb shell cat /proc/kmsg > out.txt"
Then pastebin the context of the .txt.
Thanks to K0nane, mkasick and frifox for their input.
Alogcat buffer logs
10-9-11 Alogcat radio buffer log
http://pastebin.com/Ng3JPNnd
10-9-11 Alogcat event buffer log
http://pastebin.com/SEb66mtR
10-9-11 Alogcat main buffer log
http://pastebin.com/sVYkRdg2
10-6-11 Alogcat main buffer log from firemedic624
This log is for a LOS instance after LCD Resolution restarted the phone. http://pastebin.com/SiPxteRZ
10-6-11 Alogcat event buffer log from firemedic624
This log is for a LOS instance after LCD Resolution restarted the phone. http://pastebin.com/gCYzeXzh
10-5-11 Alogcat event buffer log from firemedic624
http://pastebin.com/c07Vakc6
10-4-11 Alogcat radio buffer log from firemedic624
http://pastebin.com/8QbeAeHQ
Kmsg Logs and Interrupt Logs
10-10-11 Interrupts log on Zedomax v3 from jirafabo
http://pastebin.com/PFF9UWWi
10-9-11 Kmsg from firemedic624
http://pastebin.com/0Zh7yPrX
10-6-11 Kmsg from jirafabo
http://pastebin.com/Xr4dF8nx
10-6-11 Kmsg from firemedic624
This LOS occurred after LCD Resolution restarted the phone.
http://pastebin.com/zdsz8FwX
10-5-11 #2 Kmsg from firemedic624
http://pastebin.com/9qMUMmG8
10-5-11 #1 Kmsg from firemedic624
http://pastebin.com/B7wQsGf2
10-4-11 Kmsg from dts_stretch
http://pastebin.com/4HQTMH2C
Bug reports
10-7-11 bugreport by frifox
10-5-11 bugreport by firemedic624
10-10-11 bugreport immediately after LOS by frifox
10-10-11 bugreport 5 minutes after LOS by frifox
10-11-11 bugreport noLOS by frifox
Thanks for getting some data! It's high time someone did so.
A kmsg would be incredibly helpful to go along with this. For future reference, you may wish to paste to pastebin.com for readability and to save space.
k0nane said:
Thanks for getting some data! It's high time someone did so.
A kmsg would be incredibly helpful to go along with this. For future reference, you may wish to paste to pastebin.com for readability and to save space.
Click to expand...
Click to collapse
OK I will do that. How do I go about getting a kmsg?
Sent from my SPH-D710 using xda premium
firemedic624 said:
OK I will do that. How do I go about getting a kmsg?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
cat /proc/kmsg?
Would it help to add some others? I'll need direction as I've never done a logcat but I'm willing to learn and share...
frifox said:
cat /proc/kmsg?
Click to expand...
Click to collapse
This, on a rooted phone.
Hook up to your PC in debugging mode, have adb at the ready, and do:
adb shell cat /proc/kmsg > out.txt
...right after an LOS incident. Then pastebin the context of the .txt.
Here is a kmsg after a LOS incident
http://pastebin.com/4HQTMH2C
k0nane said:
This, on a rooted phone.
Hook up to your PC in debugging mode, have adb at the ready, and do:
adb shell cat /proc/kmsg > out.txt
...right after an LOS incident. Then pastebin the context of the .txt.
Click to expand...
Click to collapse
Tried it without a LOS incident, just to practice... The out.txt gets output to the same folder as ADB correct?
Found it and it just said this..
"cat: can't open '/proc/kmsg': Permission denied"
logcat printed out fine.....
jirafabo said:
Tried it without a LOS incident, just to practice... The out.txt gets output to the same folder as ADB correct?
Found it and it just said this..
"cat: can't open '/proc/kmsg': Permission denied"
I'm gonna jump in the irc and learn this real quick...
Click to expand...
Click to collapse
Make sure you give super user rights. after adb shell type su and then acknowledge on your phone.
dtm_stretch said:
Make sure you give super user rights. after adb shell type su and then acknowledge on your phone.
Click to expand...
Click to collapse
thanks good sir. yeah i tried that too, but i didn't acknowledge on phone, i already have so wasn't asked too. trying again, here's my results, tried two different commands....
\
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Bo>cd..
C:\Users>cd..
C:\>cd androidsdk/tools
C:\AndroidSDK\tools>adb shell
$ su
su
# adb shell cat /proc/kmsg > out.txt
adb shell cat /proc/kmsg > out.txt
adb: not found
# cat /proc/kmsg > kmsg2.txt
cat /proc/kmsg > kmsg2.txt
cannot create kmsg2.txt: read-only file system
#
jirafabo said:
thanks good sir. yeah i tried that too, but i didn't acknowledge on phone, i already have so wasn't asked too. trying again, here's my results, tried two different commands....
\
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Bo>cd..
C:\Users>cd..
C:\>cd androidsdk/tools
C:\AndroidSDK\tools>adb shell
$ su
su
# adb shell cat /proc/kmsg > out.txt
adb shell cat /proc/kmsg > out.txt
adb: not found
# cat /proc/kmsg > kmsg2.txt
cat /proc/kmsg > kmsg2.txt
cannot create kmsg2.txt: read-only file system
#
Click to expand...
Click to collapse
after you have granted su just type
cat /proc/kmsg then just right click>select all>paste in paste bin
for some reason creating the .txt is causing the error
dtm_stretch said:
after you have granted su just type
cat /proc/kmsg then just right click>select all>paste in paste bin
for some reason creating the .txt is causing the error
Click to expand...
Click to collapse
That worked. Weird that it won't write the file now, as it did for logcat and it actually did earlier but with an error written in the txt file. Oh well, this way worked.
I'll share my kmsg in the morning when I wake up with my LOS.
dtm_stretch said:
Here is a kmsg after a LOS incident
http://pastebin.com/4HQTMH2C
Click to expand...
Click to collapse
Bump just in case no one reads the first page. This is after an LOS.
dtm_stretch said:
cat /proc/kmsg then just right click>select all>paste in paste bin
Click to expand...
Click to collapse
or better yet, bugreport -d > /sdcard/bugreport.txt and pastebin that file.
i set my tasker to detect LOS and dump a log/bugreport to sdcard as soon as the sh1t happens. see this thread for more info:
http://forum.xda-developers.com/showthread.php?t=1286773
Great minds think alike!
Here is my post in that other thread:
My tasker profile to capture logs of LOS
Profile: LoS Reboot (11) ***name of profile***
Priority: 10 CoolDown: 0 ***gave it top priority, so it runs above everything else***
Event: Variable Set [ Variable:%CELLSRV Value:noservice ] ***profile runs when only when service drops out, thinking about duplicating this to another profile except for service in an "unknown" state***
Enter: Los Report And Reboot (10) ***name of task***
A1: Wait [MS:0 Seconds:20 Minutes:0 Hours:0 Days:0] ***wait 20sec after seeing no service, to allow for boot up, switch from roam to home or home to roam, ect...basically filters any "blips" out***
A2: Stop [With Error:Off] Stop [ %CELLSRV !~ unknown ] ***If I have cell service after 20sec this tells the whole thing to cancel***
A3: Airplane Mode [Set:On] ***switch airplane mode on because sometimes airplane cycle this fixes it***
A4: Wait [MS:0 Seconds:5 Minutes:0 Hours:0 Days:0] ***wait 5 sec for airplane mode to kick on***
A5: Airplane Mode [Set:Off] ***cycle airplane mode off***
A6: Wait [MS:0 Seconds:5 Minutes:0 Hours:0 Days:0] ***wait 5sec for mode to settle***
A7: Stop [With Error:Off] Stop [ %CELLSRV !~ noservice ] ***if I have cell service process is cancelled***
A8: Run Shell [Command:bugreport -d > /sdcard/losbug_$(date +%y-%m-%d_%H-%M-%S).txt Timeout (Seconds):0 Use Root:On] ***saves text file of bug report, this is a large file too. 3-5mb from what I've seen***
A9: Run Shell [Command:cat /proc/kmsg > /sdcard/loskmsg_$(date +%y-%m-%d_%H-%M-%S).txt Timeout (Seconds):0 Use Root:On] ***k0nane suggested this might be helpful in another thread***
A10: Wait [MS:0 Seconds:10 Minutes:0 Hours:0 Days:0] ***I have it wait because sometimes those reports take a little while to dump***
A11: Say [Text:Lost signal Engine:Voice:com.samsung.SMT:eng-USA-f01 Stream:3 Pitch:10 Speed:5 Continue Task Immediately:On] ***some people prefer a popup, I thought this was kinda cool. lol***
A12: Reboot [Type:Normal] ***reboot so I get service back and don't miss 15 calls***
Click to expand...
Click to collapse
Another thing I haven't posted here and I don't think I need to. I have another bootup profile set to run logcat -c that way the log is clear and fresh on every boot.
I don't know what I can do with these logs, but I'm hoping that devs can use them and fix our problem. Or at the very least figure out what is going on. I haven't had a damn LOS since running this...dammit! lol. But when I do I will post all logs to pastebin.com. We should maybe create another thread that consists purely of pastebin.com links regarding LOS
Click to expand...
Click to collapse
That's not a bad idea. I tried running bugreport -d > /sdcard/bugreport.txt but when I open it the text inside says that the file is to large.
Also added a few more logs to the 2nd and 3rd posts.
Sent from my SPH-D710 using xda premium
I get the same error, you have to open it with something other than the text editor or transfer it to your computer.
Related
Is there something additional I need to do to actually gain "root"? I can't install the clear lock screen from smurf, can't wireless tether.... Don't know what's going on, all of this used to work fine on my Hero - what am I missing?
I don't think you have given enough info for people to even know what the problem is that you are having. Maybe you could be a bit more specific. Do you have superuser installed?
Sorry about that.... basically im on stock 2.2 with supposed "root" using regaws method - problem is, I can't use anything though; adb, wireless tether, I can't flash a lock screen (just sits at boot screen).
Download superuser app from the market place or google it if it is not on your phone already. Install it then launch an app that requires root. You will know real fast if you are rooted.
DomSim said:
Download superuser app from the market place or google it if it is not on your phone already. Install it then launch an app that requires root. You will know real fast if you are rooted.
Click to expand...
Click to collapse
I do have SU... that's the thing but when I try ADB Remount it says device not permitted or something like that, can't remember exactly
You could try full wipe / reflash.
Maybe try a diff ROM too.
You need to flash the engineering bootloader (0.76.2000). Go to Toast's method part 2 and follow the steps to unlock nand. You need the engineering bootloader in order to access /system.
Sent from my PC36100 using XDA App
sombdy said:
You need to flash the engineering bootloader (0.76.2000). Go to Toast's method part 2 and follow the steps to unlock nand. You need the engineering bootloader in order to access /system.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Nand root... I was looking for more info on this, I thought it was the culprit, thanks - ill post results, hopefully good
Edit: Won't work "Permission denied" .... this is really starting to piss me off grrr
DirtyShroomz said:
Nand root... I was looking for more info on this, I thought it was the culprit, thanks - ill post results, hopefully good
Edit: Won't work "Permission denied" .... this is really starting to piss me off grrr
Click to expand...
Click to collapse
Have you run Unrevoked Forever? This will turn off security permissions and should then allow you to flash anything.
Sent from my PC36100 using XDA App
Ok, the reason
Code:
adb remount
doesn't work is because the boot.img isn't patched to allow that, because I forgot to at the time of posting. You still have root (as long as you actually completed the guide successfully), that's just an all time access root through adb
To acheive the same results, type
Code:
adb shell
type
Code:
su
you will then see #. thats root.
Then remount your /system partition using
Code:
mount -o rw,remount / /system
there you go.
regaw_leinad said:
Ok, the reason
Code:
adb remount
doesn't work is because the boot.img isn't patched to allow that, because I forgot to at the time of posting. You still have root (as long as you actually completed the guide successfully), that's just an all time access root through adb
To acheive the same results, type
Code:
adb shell
type
Code:
su
you will then see #. thats root.
Then remount your /system partition using
Code:
mount -o rw,remount / /system
there you go.
Click to expand...
Click to collapse
When I try to type "su" it says "Permission denied"
DirtyShroomz said:
When I try to type "su" it says "Permission denied"
Click to expand...
Click to collapse
Do you have usb debugging on?
Try the new 1 click root in the dev forum. Unrevoked 3.2. See if that doesn't do the trick.
Sent from my PC36100 using XDA App
My guess is you didn't flash the 2.2-root.zip at the end then.. That's the best I can do w/ the info you've given.
one was already asked once but i had two questions
1. Is USB Debugging turned on or off? Settings > Applications > Development
2. you are using a stock rooted rom. are you trying to use sprint's wireless tether app? Sprint's app wont work you need to download wireless tether from the market.
joebags said:
one was already asked once but i had two questions
1. Is USB Debugging turned on or off? Settings > Applications > Development
2. you are using a stock rooted rom. are you trying to use sprint's wireless tether app? Sprint's app wont work you need to download wireless tether from the market.
Click to expand...
Click to collapse
Running stock 2.2. Regaw I did flash 2.2-root at the end and I am trying to use wireless tether not Sprints hotspot
I do have superuser in my apps list and I was able to install SNeoid, Swype, Setcpu, juicedefender and a few others that may require root but it wont let me do anything via adb or install any themes/mods that come in .zips
DirtyShroomz said:
Running stock 2.2. Regaw I did flash 2.2-root at the end and I am trying to use wireless tether not Sprints hotspot
I do have superuser in my apps list and I was able to install SNeoid, Swype, Setcpu, juicedefender and a few others that may require root but it wont let me do anything via adb or install any themes/mods that come in .zips
Click to expand...
Click to collapse
ok do this in command prompt and paste the results in code tags (to save space)
Code:
adb shell ls /system/bin/
regaw_leinad said:
ok do this in command prompt and paste the results in code tags (to save space)
Code:
adb shell ls /system/bin/
Click to expand...
Click to collapse
Code:
setconsole
dumplayer
svc
e2fsck_recvy
chownto
apph
ps
id
chownThp
notify
dhcpcd
pand
renice
bugreport
snd8k
hciattach
iqfd
top
lsmod
setprop
ionice
ifconfig
iptables
kthp_proxy
logwrapper
getevent
htcipcd
su
start
iqd
wipe
ip
smd
sleep
getWiMAXPropDaemond
newfs_msdos
vdc
sync
udhcpd
pppd
rmmod
fsck_msdos
netstat
route
sound8k
rm
radiooptions
pm
logcat
setWiMAXPropDaemond
resize2fs_recvy
htc_inittest
vmstat
dvz
mmcamera_test
keystore
dmesg
system_server
linker
fbtool
reboot
sdptool
busybox
hd
iftop
insmod
bootcomplete
rild
schedtop
debuggerd
wpa_supplicant
schedtest
bluetoothd
ping
btld
ime
omx_tests
tc
sendevent
racoon
toolbox
date
bma150_usr
bootanimation
wimaxDhcpRenew
log
installd
wimax_uart
applypatch
wimaxAddRoute
dexopt
monkey
ln
getprop
album_hdmiexe
stop
surfaceflinger
uevent
akmd
monitorMTD
wimax_mtd
mv
debug_tool
servicemanager
wimaxDumpKmsg
dumpstate
ipd
DmWrapperTest
nandread
kill
gzip
chmod
rmdir
lsc_camera
dbus-daemon
run-as
netcfg
cat
htclogkernel
sh
mount
printenv
mkdir
bmgr
wimaxDhcpRelease
umount
mke2fs_recvy
dnsmasq
input
df
ioctl
am
wimaxDumpLogcat
app_process
chown
htc_timezonetest
service
netd
ls
netsharing
cam_ins_spmo
mm-venc-omx-test
dalvikvm
ser2net
dmagent
shutdown
ndc
dumpsys
mediaserver
vold
sequansd
awb_camera
dd
keypress
cmp
mscompress
wimaxDumpLastKmsg
mtpd
watchprops
ok, so "su" is in there... you should be able to
Code:
adb shell
su
and it give you a #
try opening SuperUser.apk on your phone, THEN doing the above commands. a pop up should come up on your phone saying to allow root to su
regaw_leinad said:
ok, so "su" is in there... you should be able to
Code:
adb shell
su
and it give you a #
try opening SuperUser.apk on your phone, THEN doing the above commands. a pop up should come up on your phone saying to allow root to su
Click to expand...
Click to collapse
that worked, now to get remount do i have to always use that previous command you wrote?
Since our forum isnt ready for the responsibility have having dev threads yet there is some use to posting logcats. People should post logcat somewhere like here.
Can people post logcats here in some organized way like
ROM in Bold
Logcat in italics
Useful thread on how to get a logcat
http://forum.xda-developers.com/showthread.php?t=1378491
How to install ADB in Ubuntu
http://forum.xda-developers.com/showthread.php?p=11823740#post11823740
How to install ADB in Windows and Mac
http://forum.xda-developers.com/showthread.php?t=1387527
If anyone needs help with how to pull a Logcat you can also find some answers here.
http://developer.android.com/guide/developing/tools/logcat.html
Listing of logcat Command Options
Option Description
-b <buffer> Loads an alternate log buffer for viewing, such as event or radio. The main buffer is used by default. See Viewing Alternative Log Buffers.
-c Clears (flushes) the entire log and exits.
-d Dumps the log to the screen and exits.
-f <filename> Writes log message output to <filename>. The default is stdout.
-g Prints the size of the specified log buffer and exits.
-n <count> Sets the maximum number of rotated logs to <count>. The default value is 4. Requires the -r option.
-r <kbytes> Rotates the log file every <kbytes> of output. The default value is 16. Requires the -f option.
-s Sets the default filter spec to silent.
-v <format> Sets the output format for log messages. The default is brief format
---------- Post added at 09:11 PM ---------- Previous post was at 09:05 PM ----------
I guess I'll be the first. This is a Logcat output for data on the radio buffer:
Rom: ICS-4.0.3-Self-Kang/ICS Leak
Link to Pastebin: http://pastebin.com/zCGNqLK0
Just a thought, maybe it would be wise to use something like pastebin to post logcats.
Sent from my SAMSUNG-SGH-I727 using xda premium
zander145 said:
Just a thought, maybe it would be wise to use something like pastebin to post logcats.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Thats a good idea.
updated with adb install instructions.
Also, system tuner allows you to view and save logs right to your device
https://play.google.com/store/apps/details?id=ccc71.pmw
Sent from my Galaxy Nexus using xda premium
I rebooted and it went away but this is one for the camera when it just froze with media scanning in screen
[ROM] ***SkyRocket-ICS-Port-SGH-T989***
Link to Pastebin http://pastebin.com/7hrYcdaU
This should be stickyed not buried in the forums
Now if we can only get people to read this...
It would make a lot easier for the developers!
More logcat info in my sig if you want to pull some of it to add to your OP
Oops, wrong thread
for installing the SDK in 64 linux you need to do
Code:
sudo apt-get install ia32-libs
It used to be on the google site but google reorganized the site and now it doesnt mention it. Good going google.
Folks, i really don't know what to do to get a specific problem log file to be sent/showed to someone to fix my problem, any help or suggestions will be really appreciated here
If you just had a hard reboot, once booted up, from pc
Adb pull /proc/last_kmsg
This will get last kmsg file related to the last boot session to your pc.
If no hard reboots but freezes etc, then
Adb shell dmesg > /sdcard/dmesg.txt
To see what's been going on since the boot at kernel level. File gets created on sdcard. Use
Adb pull /sdcard/dmesg.txt
To get it to your pc.
To get a log of something, before trying it, start the logcat with
Adb logcat > logcat.txt
File will be created on the pc.
This is from my post 6843 in official cm10 thread. You can also use
Adb shell cat /proc/kmsg > /sdcard/kmsg.txt
To see kernel logs since last boot.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Edit: /proc was missing 3 lines above
eyosen said:
If you just had a hard reboot, once booted up, from pc
Adb pull /proc/last_kmsg
This will get last kmsg file related to the last boot session to your pc.
If no hard reboots but freezes etc, then
Adb shell dmesg > /sdcard/dmesg.txt
To see what's been going on since the boot at kernel level. File gets created on sdcard. Use
Adb pull /sdcard/dmesg.txt
To get it to your pc.
To get a log of something, before trying it, start the logcat with
Adb logcat > logcat.txt
File will be created on the pc.
This is from my post 6843 in official cm10 thread. You can also use
Adb shell cat /kmsg > /sdcard/kmsg.txt
To see kernel logs since last boot.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
thanks eyosen you are the best
what if i already rebooted it several times due to weird signal loss? please check this http://forum.xda-developers.com/showthread.php?p=32791585#post32791585
does this means i've lost the latest log? if no, then how to extract the specific problem log from it such as the signal loss? or shall i send the whole log?
Hossam.Abdelsalam said:
thanks eyosen you are the best
what if i already rebooted it several times due to weird signal loss? please check this http://forum.xda-developers.com/showthread.php?p=32791585#post32791585
does this means i've lost the latest log? if no, then how to extract the specific problem log from it such as the signal loss? or shall i send the whole log?
Click to expand...
Click to collapse
use "adb logcat -b radio"
Press the thanks button if you want to thank me
You are welcome.
Just send the whole log. Best practice is to post it to pastebin and post the link in the forum.
After every reboot you will lose the previous last_ksmg.
Sent from a gadget on my balcony.
wcypierre said:
use "adb logcat -b radio"
Press the thanks button if you want to thank me
Click to expand...
Click to collapse
i already pressed it
but it seems this shows you the log at the run time, but what am trying to get is the log of my weird signal loss for incidents happened yesterday, is this even possible?
No that's not possible. You can start a logcat, repeat the steps that caused the problem, after the problem , post logcat and kmsg.
Sent from a gadget on my balcony.
Hossam.Abdelsalam said:
i already pressed it
but it seems this shows you the log at the run time, but what am trying to get is the log of my weird signal loss for incidents happened yesterday, is this even possible?
Click to expand...
Click to collapse
well, it should be able to trace back if the time duration is not that long, but you can just try and do what eyosen had suggested
Yesterday, @dproldan and I were editing my build.prop file for the 360. I figure that this might be a good thread to talk about what you have done with your build.prop and what it does.
ro.ambient.enable_when_plugged=false
and not sure if this is also needed,
ro.ambient.force_when_docked=false
This will turn your screen off when the device is docked.
@dproldan also suggests TRYING the CPU throttling property.
hw.cpu.throttle.state=1
If it doesn't work, just change it back to default.
ALWAYS remember to make a copy of the build.prop before you alter it.
XDA:DevDB Information
[ROOT] All 360 Mods, Device Specific App for the Moto 360
Contributors
abuttino, abuttino
Version Information
Status: Testing
Created 2014-10-17
Last Updated 2014-10-16
Yes! no more worries about the display getting the image persistence issue or the wife complaining about the room being illuminated by the watch.
About the throttle property. It is used in the /init.minnow.rc file, at the end you'll see that when it's not set (0), the max frequency is 1GHz, when it's set (1), the max frequency is 600MHz. It does so by writing a value to /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
The valid frequencies, set in the kernel, are 300MHz, 600MHz, 800MHz and 1 GHz. so you can write directly to that and get a direct result:
Code:
echo 800000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
This doesn't mean that It will use less battery, but it's something to try.
Awesome! Any chance of turning off automatic HRM? I'm really curious how much battery increases since it turns on every 5 min.
HRM?
abuttino said:
HRM?
Click to expand...
Click to collapse
Heart Rate Monitor
I found the name of the apk that needs to be modified for the HRM but I'm not at home to message dproldan
Any way to change the ambient mode to be always on and/or adjust the brightness?
PsychDrummer said:
Awesome! Any chance of turning off automatic HRM? I'm really curious how much battery increases since it turns on every 5 min.
Click to expand...
Click to collapse
We need to edit a Motorola package, but that will take some time.
For the moment, you could disable the constant monitoring with:
Code:
pm disable com.motorola.targetnotif
This will remove the automatic heart monitoring, but also the default watchfaces and the connection to the motorola app in the phone. The rest of the functions are not modified. You can still access the HRM with the google Fit app.
dproldan said:
We need to edit a Motorola package, but that will take some time.
For the moment, you could disable the constant monitoring with:
Code:
pm disable com.motorola.targetnotif
This will remove the automatic heart monitoring, but also the default watchfaces and the connection to the motorola app in the phone. The rest of the functions are not modified. You can still access the HRM with the google Fit app.
Click to expand...
Click to collapse
Thanks! Will running that command with "enable" instead of "disable" reverse it?
Tonight was a very productive night for the 360!
@dproldan and I were on a conversation on the freenode IRC chat #moto360 and he and I have tested some things out that seem to work extremely well.
The first and most requested thing was to disable the unattended heart rate monitor called "Heart Activity"
So, with your rooted watch in a root/su shell prompt type:
pm disable com.motorola.targetnotif/com.motorola.omni.HealthActivity
Now, until we figure out which EXACT activity is using the pedometer, he suggested we kill the fit app altogether by using this command:
pm disable com.google.android.apps.fitness
If you feel that you MUST disable the Heart Rate program that DOES NOT take your heart rate unattended, or use any battery unless you run it yourself:
pm disable com.motorola.targetnotif/com.motorola.omni.HeartRateActivity
I've seen this mentioned a few times and, figure I would at least put it out there for people to try if they need to.
If you need to root your watch, @dproldan is selling a cradle that he designed and, is a LOT more stable than a self built cat5e connector that can short at any time.
http://forum.xda-developers.com/moto-360/development/cradles-moto360-usb-conection-sale-t2901110
The 360 community needs more devs and people willing to test. If you have any requests, solutions please post in this thread. If you need help with rooting your watch; please don't be afraid to post in the Q&A section of the 360 forum.
PsychDrummer said:
Thanks! Will running that command with "enable" instead of "disable" reverse it?
Click to expand...
Click to collapse
Yes.
Just got Rooted and and been doing little mods here and there, some inverted apps and such. The thing I'm having an issue with is writing to system, the keep getting permission failed, is any one else successfully writing to system. I even edited the 360 superboot.Img to install busybox and still no success. If any one has a solution to this I can start adding some cool mods and possible features.
Did you rename it to boot.img?
I just Rooted using the utility, I have root, just if I try pushing something to system I get a permission denied error, samething with adb remount.
Get the boot image from the post here, rename it to boot.img and do this:
"fastboot boot boot.img"
Stick with the tried and true methods
ok ill try that right now. one question are you pushing to system with the adapter or over BT?
Fastboot is always over USB. ADB commands can be done over b/t
steal25 said:
ok ill try that right now. one question are you pushing to system with the adapter or over BT?
Click to expand...
Click to collapse
To push things to /system, you need to make the partition writable. With previous devices, you'de do that with "adb remount", but the moto360 over bluetooth doesn't allow that, AFAIK. We also don't have a root adb yet, so you need to put things in /storage/sdcard0 from the computer, then move them to the final folder from a root shell
What I've been doing is:
Code:
computer: adb -e shell
moto360: su
moto360: mount -o rw,remount /dev/block/mmcblk0p14 /system
moto360: exit
moto360: exit
computer: adb -e push whatever-you-want-to-push /storage/sdcard0/
computer: adb -e shell
moto360: cp /storage/sdcard0/whatever-you-want-to-push /where-you-want-to-place-it
I hope that makes sense. I have only moved simple things yet, but I hope we'll find better ways soon.
You can push the build.prop over Bluetooth and should be able to remount system too. I've done it every time I've edited my build.prop
dproldan said:
To push things to /system, you need to make the partition writable. With previous devices, you'de do that with "adb remount", but the moto360 over bluetooth doesn't allow that, AFAIK. We also don't have a root adb yet, so you need to put things in /storage/sdcard0 from the computer, then move them to the final folder from a root shell
What I've been doing is:
Code:
computer: adb -e shell
moto360: su
moto360: mount -o rw,remount /dev/block/mmcblk0p14 /system
moto360: exit
moto360: exit
computer: adb -e push whatever-you-want-to-push /storage/sdcard0/
computer: adb -e shell
moto360: cp /storage/sdcard0/whatever-you-want-to-push /where-you-want-to-place-it
I hope that makes sense. I have only moved simple things yet, but I hope we'll find better ways soon.
Click to expand...
Click to collapse
Yep makes sense, been driving me nuts, I even edited the Rooted boot . Img to install busybox and it works but when I ran busybox mount..... It returned couldn't find etc/Fstab. I'll do a little more digging when i get home
If anyone wants to disable charging LED, here's an easy way via Tasker.
Note: notifications will not cause LED to blink while charging
State, power, power any
Enter task:
1. run shell as root, "chmod 644 /sys/class/leds/red/brightness"
2. run shell as root, "echo 0 > /sys/class/leds/red/brightness"
3. run shell as root, "chmod 444 /sys/class/leds/red/brightness"
Exit task:
1. run shell as root, "chmod 644 /sys/class/leds/red/brightness"
2. run shell as root, "echo 0 > /sys/class/leds/red/brightness"
Hi! Thanks for sharing. I am getting the following error:
23.21.58/E Run Shell: ->
23.21.58/E Run Shell: ->
23.21.58/E Run Shell: ->
23.21.58/Shell runBackground "chmod 644 /sys/class/leds/red/brigthness" root: true timeout: -1
23.21.58/Shell start process-thread ID 725
23.21.58/E add wait type Shell1 time 2147483647
23.21.58/E add wait type Shell1 done
23.21.58/E add wait task
23.21.58/E Error: 127
Am I doing something wrong?
Thanks!
Dj Telo said:
Hi! Thanks for sharing. I am getting the following error:
23.21.58/E Run Shell: ->
23.21.58/E Run Shell: ->
23.21.58/E Run Shell: ->
23.21.58/Shell runBackground "chmod 644 /sys/class/leds/red/brigthness" root: true timeout: -1
23.21.58/Shell start process-thread ID 725
23.21.58/E add wait type Shell1 time 2147483647
23.21.58/E add wait type Shell1 done
23.21.58/E add wait task
23.21.58/E Error: 127
Am I doing something wrong?
Thanks!
Click to expand...
Click to collapse
Does Tasker have root access? Check it in Magisk/superuser section.
_mysiak_ said:
Does Tasker have root access? Check it in Magisk/superuser section.
Click to expand...
Click to collapse
Yes it does. I can even execute other shell commands with root without problem. Is the command you are giving maybe only valid with Nougat and not Oreo?
Thanks!
Dj Telo said:
Yes it does. I can even execute other shell commands with root without problem. Is the command you are giving maybe only valid with Nougat and not Oreo?
Thanks!
Click to expand...
Click to collapse
Oups, my bad, sorry for the typo in the instructions. It has to be brigHTness, not brigTHness.
Will this work on the Mi A3 too?
And will the notification led still blink when not charging the phone?
Thank you
DBuffon said:
Will this work on the Mi A3 too?
And will the notification led still blink when not charging the phone?
Thank you
Click to expand...
Click to collapse
I don't have rooted A3 at hand, so can't try it. It might work, there is no harm in sending those commands over adb shell as root user. You will see the result immediately.
Sent from my Mi A1 using Tapatalk
_mysiak_ said:
I don't have rooted A3 at hand, so can't try it. It might work, there is no harm in sending those commands over adb shell as root user. You will see the result immediately.
Click to expand...
Click to collapse
Ok, I'll try but I don't understand the following:
_mysiak_ said:
State, power, power any
Enter task:
1. run shell as root, "chmod 644 /sys/class/leds/red/brightness"
2. run shell as root, "echo 0 > /sys/class/leds/red/brightness"
3. run shell as root, "chmod 444 /sys/class/leds/red/brightness"
Exit task:
1. run shell as root, "chmod 644 /sys/class/leds/red/brightness"
2. run shell as root, "echo 0 > /sys/class/leds/red/brightness"
Click to expand...
Click to collapse
Are the "Enter task" the code that should be run when the charging cable connects to the phone and the "Exit task" the one that runs when unplugging the cable?
I don't understand what this code does, and I don't want to mess up the led (that is: before I proceed, I want to know how to revert if things don't go as they should). Thank you.
DBuffon said:
Ok, I'll try but I don't understand the following:
Are the "Enter task" the code that should be run when the charging cable connects to the phone and the "Exit task" the one that runs when unplugging the cable?
I don't understand what this code does, and I don't want to mess up the led (that is: before I proceed, I want to know how to revert if things don't go as they should). Thank you.
Click to expand...
Click to collapse
Enter and exit tasks are for Tasker. If you want to try the commands from adb shell, enter those mentioned in "entry task" first and check if LED stopped glowing. To restore the original state enter commands from "exit task" (or just reboot the phone). Changes are not permanent.
Commands do the following - enable RW access to LED control, set intensity to 0%, disable RW access.
_mysiak_ said:
Enter and exit tasks are for Tasker. If you want to try the commands from adb shell, enter those mentioned in "entry task" first and check if LED stopped glowing. To restore the original state enter commands from "exit task" (or just reboot the phone). Changes are not permanent.
Commands do the following - enable RW access to LED control, set intensity to 0%, disable RW access.
Click to expand...
Click to collapse
Great, thanks for the information.
Unfortunately I can't issue the commands (sorry, I'm new to the adb shell):
Code:
[email protected]:~$ adb shell chmod 644 /sys/class/leds/red/brightness
chmod: /sys/class/leds/red/brightness: Permission denied
[email protected]:~$ adb root
adbd cannot run as root in production builds
DBuffon said:
Great, thanks for the information.
Unfortunately I can't issue the commands (sorry, I'm new to the adb shell):
Code:
[email protected]:~$ adb shell chmod 644 /sys/class/leds/red/brightness
chmod: /sys/class/leds/red/brightness: Permission denied
[email protected]:~$ adb root
adbd cannot run as root in production builds
Click to expand...
Click to collapse
adb shell
su
chmod ....
It works on the A3 too. Thanks!
In my mi A1, revengeos android 9, in enter task, 2th step go in error
d_borghi said:
In my mi A1, revengeos android 9, in enter task, 2th step go in error
Click to expand...
Click to collapse
What kind of error..?
_mysiak_ said:
What kind of error..?
Click to expand...
Click to collapse
Allego
d_borghi said:
Allego
Click to expand...
Click to collapse
Try to run that command from terminal on the phone (or via ADB) as root. Alternatively, store the error message in some variable in Tasker and display it, so we know why exactly does it fail. On my phone it still works fine (Mi A3 now).
how can i try by an emulator terminal app in my phone directly?
d_borghi said:
how can i try by an emulator terminal app in my phone directly?
Click to expand...
Click to collapse
Install and run for example this app https://play.google.com/store/apps/details?id=yarolegovich.materialterminal&hl=en
_mysiak_ said:
Install and run for example this app https://play.google.com/store/apps/details?id=yarolegovich.materialterminal&hl=en
Click to expand...
Click to collapse
Finally, I try the app.
By this terminal I receive no error, look at the screenshot.
Why tasker goes in error?
d_borghi said:
Finally, I try the app.
By this terminal I receive no error, look at the screenshot.
Why tasker goes in error?
Click to expand...
Click to collapse
Could you take a screenshot of the details in Tasker for that one task which gives you an error? Maybe you have a typo there.