Recent ROM update w/ app restore has resulted in some fairly consistent random reboots. This is first jelly bean device I've had that I've needed a logcat from, so I just learned that logging isn't that simple any more.
I've tried a couple of different methods to capture a log (aLogcat, Catlog, adb logcat), but never get output. Moved Catlog to a system app after reading in its store comments that that worked, but no joy. Granted read logs permission in terminal per another suggestion, still no go.
Any ideas how to get a log on the Note 2 to troubleshoot something like this?
Open your file manager with root access and go to /dev/log/ and check whether the file "main" and "system" exist or not
wcypierre said:
Open your file manager with root access and go to /dev/log/ and check whether the file "main" and "system" exist or not
Click to expand...
Click to collapse
System, yes, main, no.
I wonder if logging was turned off by this ROM's chef. I know some do that to improve performance. I'll check on that.
Sent from my SGH-T889 using Tapatalk 2
wcypierre said:
Open your file manager with root access and go to /dev/log/ and check whether the file "main" and "system" exist or not
Click to expand...
Click to collapse
System, yes, main, no.
I wonder if logging was turned off by this ROM's chef. I know some do that to improve performance. I'll check on that.
Sent from my SGH-T889 using Tapatalk 2
I don't know if this WL help you at all I really don't know how to read log cats but I do know that I use system tuner pro and one of the functions is log and when I go to it it appears to be a logcat. Also I used another app from the market I forget which I will to back and check. Also one other thing that maybe will help you in this situation is chain fire has an app that replaced your boot animation with a live log cat so when you boot it would kinda look like when you boot up your windows PC. You have to pay but its only like 2 bucks. And it says it is a real live log cat not per recorded. I don't know if any of that will help but just a suggestion.
---------- Post added at 10:27 PM ---------- Previous post was at 10:21 PM ----------
The other app was. Called logcat extreme
distortedloop said:
System, yes, main, no.
I wonder if logging was turned off by this ROM's chef. I know some do that to improve performance. I'll check on that.
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
Most probably so as some of the devs do remove the log files. Now, go to /system/etc/init.d/ and check every file in there for this line:
rm /dev/log/main
If you found that line, add a hash(#) in front of it to enable logcat so it will become
#rm /dev/log/main
If you want to disable the logcat again, just simply remove the hash(#)
If you can't find that line of code, then search for your apps(there are some apps that will delete /dev/log/main)
wcypierre said:
Most probably so as some of the devs do remove the log files. Now, go to /system/etc/init.d/ and check every file in there for this line:
rm /dev/log/main
If you found that line, add a hash(#) in front of it to enable logcat so it will become
#rm /dev/log/main
If you want to disable the logcat again, just simply remove the hash(#)
If you can't find that line of code, then search for your apps(there are some apps that will delete /dev/log/main)
Click to expand...
Click to collapse
That's enlightening stuff. I've never played around with init files and start up scripts.
Sure enough, one of them does remove the log, and remming it out has brought back logcat function.
Thank you so much for the help and the education.
Interestingly, my random reboots seem to have stopped for the time being, meaning I don't need the logs for now, but I like having them available.
distortedloop said:
That's enlightening stuff. I've never played around with init files and start up scripts.
Sure enough, one of them does remove the log, and remming it out has brought back logcat function.
Thank you so much for the help and the education.
Interestingly, my random reboots seem to have stopped for the time being, meaning I don't need the logs for now, but I like having them available.
Click to expand...
Click to collapse
First of all, you're welcome
I have been doing some research on logging features for the past few months, so I know how to troubleshoot some problems that are related to logging.
If you want to, you can take a look at my tool, AIOlog, which is a command line program to extract logs(which encourages me more to do more research on logging).
Anyway, have fun with your new knowledge and don't forget to spread it to those who needs it
Already shared the solution on the Jedi X ROM thread.
Your tool's in the play store?
Sent from my SGH-T889 using Tapatalk 2
distortedloop said:
Already shared the solution on the Jedi X ROM thread.
Your tool's in the play store?
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
Nope, as Playstore only allows apps that are compiled using their sdk while my tool is a tool compiled with g++.
But who knows? maybe I'll make a logcat app in the future(but I don't feel so as there's a lot of alternatives in the playstore)
Run this:
su
cat /proc/last_kmsg > /mnt/sdcard/last_kmsg.txt
This is the last syslog after a reboot and extremely helpful in debugging random reboots.
---------- Post added at 04:56 AM ---------- Previous post was at 04:55 AM ----------
wcypierre said:
Nope, as Playstore only allows apps that are compiled using their sdk while my tool is a tool compiled with g++.
But who knows? maybe I'll make a logcat app in the future(but I don't feel so as there's a lot of alternatives in the playstore)
Click to expand...
Click to collapse
Why not simply use the NDK?
fivefour said:
Run this:
su
cat /proc/last_kmsg > /mnt/sdcard/last_kmsg.txt
This is the last syslog after a reboot and extremely helpful in debugging random reboots.
---------- Post added at 04:56 AM ---------- Previous post was at 04:55 AM ----------
Why not simply use the NDK?
Click to expand...
Click to collapse
NDK increases the complexity of the app and there's better alternative such as catlog and alogcat.
Moreover, Google has implemented a restriction on apps logging so its another no no for me.
Related
Major edit:
This is now the rooted system pull, including EVERYTHING that you'll need to dev for this phone. Links are here:
http://d-h.st/2No This link is system.img compressed to a 7z format, expect it to be HUGE (about 1.4gb) when uncompressed.
http://d-h.st/7YC This is the standard system.tar.gz pull.
http://d-h.st/wvp System.tar.gz mirror
If anyone needs another system dump uploaded let me know. Got mine today and am in no hurry to switch over to it so its a test bed.
Thanks for posting. I'm sure this will be of great help to some folks doing research on the device for some flashing goodness!
anyone wanna test TW launcher with wallpaper scrolling
already have it done.
howtomen said:
anyone wanna test TW launcher with wallpaper scrolling
already have it done.
Click to expand...
Click to collapse
You're already on a roll! Good to see some familiar SN's on this side already!
howtomen said:
anyone wanna test TW launcher with wallpaper scrolling
already have it done.
Click to expand...
Click to collapse
wut? lol the launcher doesn't have wallpaper scrolling? wow didn't know that.
HERE IS A JumboFiles MIRROR
Thanks, Neverends. Just edited my first post.
I got a T-mo version today, and would love to provide a dump, but I don't have a clue how. My Odin/adb are all good, I just don't know what the commands are. Anyone want to give me a list so I can have at it?
Janis said:
I got a T-mo version today, and would love to provide a dump, but I don't have a clue how. My Odin/adb are all good, I just don't know what the commands are. Anyone want to give me a list so I can have at it?
Click to expand...
Click to collapse
Adb pull /system and post in tmobile forum
Sent from my HTC Desire HD using xda premium
Janis said:
I got a T-mo version today, and would love to provide a dump, but I don't have a clue how. My Odin/adb are all good, I just don't know what the commands are. Anyone want to give me a list so I can have at it?
Click to expand...
Click to collapse
Make a folder to hold the dump. I did C:/SGS3Dump
Then type adb pull /system C:/SGS3Dump and it takes about 15 minutes to complete
entropism said:
Make a folder to hold the dump. I did C:/SGS3Dump
Then type adb pull /system C:/SGS3Dump and it takes about 15 minutes to complete
Click to expand...
Click to collapse
There is a better way to do this. By doing it the way that you mention windows will add a carriage return to end of every line of the basic files, since Adnroid is linux at it's base, that is not a good thing.
The better way to grab a system image is like this:
adb shell
cat /dev/block/system > /sdcard/system.img
This can be mounted like an iso on any OS.
I'll do this now. Thanks for the tip!
Edit: Says no such file or directory. odd
jimbridgman said:
There is a better way to do this. By doing it the way that you mention windows will add a carriage return to end of every line of the basic files, since Adnroid is linux at it's base, that is not a good thing.
The better way to grab a system image is like this:
adb shell
cat /dev/block/system > /sdcard/system.img
This can be mounted like an iso on any OS.
Click to expand...
Click to collapse
no root so it cant be done....
howtomen said:
no root so it cant be done....
Click to expand...
Click to collapse
Yes that is true, but still a better way for a true image. The other way, will miss any files that are not readable by "other" on the filesystem, so that can be an issue, as well.
As soon as we get root, I'll post up a proper system dump. I just need to know how to get access to the boot.img, so we can get root.
entropism said:
I'll do this now. Thanks for the tip!
Edit: Says no such file or directory. odd
Click to expand...
Click to collapse
You may have to figure out where the device for /system is at in /dev it may be something like /dev/block/mmcblk0p(1-26). Those last numbers in the parenthesis are the partition number for /system, that will be what you will need to find in /dev/block, and it will be a number between 1 and 25 usually.
You will need root to this, just like howtomen mentioned. For now how you mentioned will just sort of do the job. It would be best to do it from cygwin rather than from the windows command line though, as cygwin should NOT add the carriage returns.
OK well... I have a linux machine I can use, but I never used ADB on it. if someone wants to walk me through it, I'll do a system dump on linux. If not, well, not much I can do...
Would love to look at the dump, but that mirror ain't working well for me.
Sent from my SGH-I997 using xda premium
Me neither... I'm posting up my dropbox again.
http://dl.dropbox.com/u/6421623/ATTSGS3 System Dump.7z
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
To take a screen shot, just slide left
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Nexus 10 (manta)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Click to expand...
Click to collapse
Phil3759 said:
Flashing can brick your phone
This will be removed after people report it is booting fine without bricking their phone
Click to expand...
Click to collapse
But... my phone is across the room and isn't even Android. Maybe I should rip the battery out just to be safe though
This sounds pretty cool though.
espionage724 said:
But... my phone is across the room and isn't even Android. Maybe I should rip the battery out just to be safe though
This sounds pretty cool though.
Click to expand...
Click to collapse
I warn people when I release an untested recovery on a given device
Most noobs tend to forget that flashing is not a safe operation. It can always turn into a nightmare
You can check the list of currently supported devices from main thread here: http://forum.xda-developers.com/showthread.php?t=2201860
And browse into the different device support forums
Till now, the warning never became true except when some people flashed the wrong file in their phone
This warning should keep noobs away from testing it
Ah, yeah I have nothing against the warning, glad it's there even The Nexus 10 is a tablet though, not phone
espionage724 said:
Ah, yeah I have nothing against the warning, glad it's there even The Nexus 10 is a tablet though, not phone
Click to expand...
Click to collapse
LoL
It is a generic copy paste message
Well, will you be the first to give a feedback ?
Phil3759 said:
Well, will you be the first to give a feedback ?
Click to expand...
Click to collapse
Sure
I went to bootloader, erased recovery and flashed this one. Rebooted to recovery.
Battery meter at top-right says -1% (my tablet was on Pogo charge for hours prior to flashing). Get an error about being unable to create brightness sys file. During key test, randomly getting constant presses when holding 3 fingers on screen (probably a touchscreen-related issue).
espionage724 said:
Sure
I went to bootloader, erased recovery and flashed this one. Rebooted to recovery.
Battery meter at top-right says -1% (my tablet was on Pogo charge for hours prior to flashing). Get an error about being unable to create brightness sys file. During key test, randomly getting constant presses when holding 3 fingers on screen (probably a touchscreen-related issue).
Click to expand...
Click to collapse
Thank you for the feedback (reached my daily limit for :good
Brightness:
Do you by case know the path for your device brightness file?
Not a big deal though as I can search / look for it in rc files. I used Samsung usual path, but it seems they used a different one for google devices
Battery:
Will check for the battery path used
Touch
It is supposed to be one finger to use
Interesting though...
Can any one run this in adb shell while in recovery
Or you can use the console terminal in aroma file manager while in recovery
Code:
find /sys/. -name '*bright*' >/sdcard/brightness.txt
Then
Code:
find /sys/. -name '*battery*' >/sdcard/battery.txt
And attach the resulting brightness.txt and battery.txt files on sdcard
About multi touch: i will look to allow only slot 0 to ignore second finger
Sent from my GT-I9100 using Tapatalk 2
Forget it. I found path in source
Sent from my GT-I9100 using Tapatalk 2
Ok, still would need battery info it seems
Code:
find /sys/class/power_supply/ -name '*' >/sdcard/battery.txt
And as described above, attach resulting battery.txt file here
Please do this in recovery, not main system
Sent from my GT-I9100 using Tapatalk 2
Phil3759 said:
Ok, still would need battery info it seems
Code:
find /sys/class/power_supply/. -name '*' >/sdcard/battery.txt
And as described above, attach resulting battery.txt file here
Please do this in recovery, not main system
Click to expand...
Click to collapse
see attached - is this what you're looking for?
Ok,
Can you do this now:
Code:
ls-l /class/power_supply/android-battery >/sdcard/battery.txt
And attach the file
Many thanks
Phil3759 said:
Ok,
Can you do this now:
Code:
ls-l /class/power_supply/android-battery >/sdcard/battery.txt
And attach the file
Many thanks
Click to expand...
Click to collapse
Sorry I'm a bit out of sync with you -- but I've attached the one you asked for just before revising your post.
find /sys/class/power_supply/ -name '*' >/sdcard/battery.txt
Result is attached. I'll run the other command in a moment.
Phil3759 said:
Ok,
Can you do this now:
Code:
ls-l /class/power_supply/android-battery >/sdcard/battery.txt
And attach the file
Many thanks
Click to expand...
Click to collapse
OK -- re-learning linux command line as I go (it's been many years!). Good to wake up that part of the brain again...
Had to modify command above: needed a space between ls and -l, and I'm assuming you want "/sys" up front in the fully qualified file name... Assuming that's all good, the new result is attached as battery2.txt
Let me know if this is what you need, or if anything else is needed. I've got some time to squeeze in a few of these today as needed. Also REALLY looking forward to trying this out on my N10 (and would love to see this on the Galaxy Nexus if ever possible!).
Sorry for the time I make you loose
Was at work, on a hurry, typing using tapatalak mess
I am at home and I could test before posting this. The symlinking is a small issue to first traverse folders wthout going into tons of links
Anyway, here's what should find the needed files
Code:
ls -l /sys/class/power_supply/android-battery/* >/sdcard/battery.txt
Thank you for your patience :good::good:
Phil3759 said:
Sorry for the time I make you loose
Was at work, on a hurry, typing using tapatalak mess
I am at home and I could test before posting this. The symlinking is a small issue to first traverse folders wthout going into tons of links
Anyway, here's what should find the needed files
Code:
ls -l /sys/class/power_supply/android-battery/* >/sdcard/battery.txt
Thank you for your patience :good::good:
Click to expand...
Click to collapse
Try the attached...
jonstrong said:
Try the attached...
Click to expand...
Click to collapse
bingo :good:
Code:
/sys/class/power_supply/android-battery/capacity
Phil3759 said:
bingo :good:
Code:
/sys/class/power_supply/android-battery/capacity
Click to expand...
Click to collapse
Great -- let me know if you need anything else -- I'm home today, and can pull some more if needed.
Does this recovery support USB OTG?
I must be in stupid mode today !!
Have been running Galaxy S3 with PhilZ Touch for some time now .... superb :good:
Got a new Nexus 10 last week and want it on there as well ..... stupid bit coming now
Downloaded latest version from this thread - but it shows as "philz_touch_5.00.7-manta.img"
Not a zip or a tar file for Odin ..... what am I missing from under my nose?
Homer
Root is no longer working on MM update.
Don't suppose anybody knows how to get to recovery with hardware button?
hecksagon said:
Don't suppose anybody knows how to get to recovery with hardware button?
Click to expand...
Click to collapse
Swipe from top-left to bottom-right at the Asus logo. That gets you to fastboot mode, then swipe up and down to change menu items, swipe right to select.
Or you can enable debug mode and use adb reboot recovery.
CSX321 said:
Swipe from top-left to bottom-right at the Asus logo. That gets you to fastboot mode, then swipe up and down to change menu items, swipe right to select.
Or you can enable debug mode and use adb reboot recovery.
Click to expand...
Click to collapse
You are a hero. I have looked for the better part of 2 hours for this. Anyway I'll sideload the LP update and start over. Hopefully somebody can make use of the recovery and boot pulls and get us a working recovery.
I would be very interested in REMOVING the Wellness app. This is the only reason I want root. Guess I will need to wait until we have a root enabled file manager. Alas, I can write in C++ fairly well, but know nothing of coding for android. Be glad to test any recoveries and operating systems on my ZenWatch.
nethead72 said:
I would be very interested in REMOVING the Wellness app. This is the only reason I want root. Guess I will need to wait until we have a root enabled file manager. Alas, I can write in C++ fairly well, but know nothing of coding for android. Be glad to test any recoveries and operating systems on my ZenWatch.
Click to expand...
Click to collapse
It can be done without a file manager. If you have root, you can enable debugging, connect to a PC by USB, use adb to get a root shell, then adb uninstall package_name.
Edit...Which Benton are you in, BTW. I'm not far from Benton, IL.
CSX321 said:
It can be done without a file manager. If you have root, you can enable debugging, connect to a PC by USB, use adb to get a root shell, then adb uninstall package_name.
Edit...Which Benton are you in, BTW. I'm not far from Benton, IL.
Click to expand...
Click to collapse
Es File Explorer works fine and has an OK interface when on the watch. Also the KingRoot app that gets pushed has an uninstaller too for system apps. The biggest issue I've had is that when the prompt to allow root comes up you can not select allow. You have to cover the screen to back out, then go into KingRoot and open the log, then select the app you want to allow and set it to always allow. You have to do this after the initial failed prompt.
Edit: Freeport, IL here. Worlds a small place.
File Types?
hecksagon said:
The latest Windows version of kingroot works on the zenwatch. I currently have root that persists after reboot and I am working on pulling the boot.img and recovery.img. Not sure what to do after that, hope somebody can pick up on this.
Recovery.img
https://drive.google.com/file/d/0BxOsuCVqSlnfVzVGRWo4bmZZZHc/view?usp=docslist_api
Boot.img
https://drive.google.com/file/d/0BxOsuCVqSlnfLVp4Z19EQ0owdTQ/view?usp=docslist_api
Click to expand...
Click to collapse
Am I looking at .iso files here, tarballs, or some other kind of binary? I need to add file extensions to make them useful.:good:
---------- Post added at 09:30 PM ---------- Previous post was at 09:28 PM ----------
Benton Arkansas.
---------- Post added at 09:32 PM ---------- Previous post was at 09:30 PM ----------
hecksagon said:
Es File Explorer works fine and has an OK interface when on the watch. Also the KingRoot app that gets pushed has an uninstaller too for system apps. The biggest issue I've had is that when the prompt to allow root comes up you can not select allow. You have to cover the screen to back out, then go into KingRoot and open the log, then select the app you want to allow and set it to always allow. You have to do this after the initial failed prompt.
Edit: Freeport, IL here. Worlds a small place.
Click to expand...
Click to collapse
I use ES File Explorer on my Nexus 6, CyanogenMod 12.1
I do not have a wearable app on my ZenWatch. Is it in settings somewhere?
nethead72 said:
Am I looking at .iso files here, tarballs, or some other kind of binary? I need to add file extensions to make them useful.:good:
---------- Post added at 09:30 PM ---------- Previous post was at 09:28 PM ----------
Benton Arkansas.
---------- Post added at 09:32 PM ---------- Previous post was at 09:30 PM ----------
I use ES File Explorer on my Nexus 6, CyanogenMod 12.1
I do not have a wearable app on my ZenWatch. Is it in settings somewhere?
Click to expand...
Click to collapse
You have to download the normal phone apk from apkmirror or some other site and use adb to sideload it. Google sideloading apps to Wear, should work the same for any watch. Otherwise you can buy Apps2Wear on the play store. I have done that because its more convenient.
Ok, went through the whole process, is there a way to check root access using ADB?
You should have KingRoot app installed on your watch. That will tell you if you have root. I imagine you could try to pull some files from /system or something that would normally not be accessible. I wouldn't recommend writing to system yet. I soft bricked by watch just by pasting a modified build.prop over the original, trying to turn off low bit depth ambient mode.
Root confirmed, having issues side-loading the ES File explorer apk, though. I'm using the App2Wear method. Still trouble shooting.
nethead72 said:
Root confirmed, having issues side-loading the ES File explorer apk, though. I'm using the App2Wear method. Still trouble shooting.
Click to expand...
Click to collapse
Make sure you have adb debugging and adb bluetooth debugging enabled on watch. Make sure you have usb adb debugging turn on on phone. Then make sure you have bluetooth debugging turn on in Wear app. Make sure you do these in that order because the toggle in the wear app wont show up unless you have debugging enabled on phone first.
This is the KingRoot file you need for windows.
https://onedrive.live.com/redir?res...3077&authkey=!AA2AI4RkRdiA4tg&ithint=file,exe
Attached is the latest ES File Explorer APK
EDIT: I rebooted everything, and worked fine. Funny how rebooting fixes so many issues... Will test when side-load is completed.
EDIT 2: Looks like its gonna take a long time. Gonna go do dishes and whatnot and be patient.
nethead72 said:
Am I looking at .iso files here, tarballs, or some other kind of binary? I need to add file extensions to make them useful.:good:
Click to expand...
Click to collapse
Sorry, they are .img. They were pulled using Flashify. The extension must have been stripped when I uploaded them to Drive.
nethead72 said:
This is the KingRoot file you need for windows.
https://onedrive.live.com/redir?res...3077&authkey=!AA2AI4RkRdiA4tg&ithint=file,exe
Attached is the latest ES File Explorer APK
EDIT: I rebooted everything, and worked fine. Funny how rebooting fixes so many issues... Will test when side-load is completed.
EDIT 2: Looks like its gonna take a long time. Gonna go do dishes and whatnot and be patient.
Click to expand...
Click to collapse
Sometimes it fails once and works when you retry. Not sure why.
hecksagon said:
Sometimes it fails once and works when you retry. Not sure why.
Click to expand...
Click to collapse
ES is 28 MB when installed, according to App2Wear, that should be 45-60 minutes to install.
nethead72 said:
ES is 28 MB when installed, according to App2Wear, that should be 45-60 minutes to install.
Click to expand...
Click to collapse
Maybe 10-15 mins when I did.
hecksagon said:
Maybe 10-15 mins when I did.
Click to expand...
Click to collapse
Seems like its taking way too long (going on 1 hour+). Gonna reboot and try again.
---------- Post added at 11:55 PM ---------- Previous post was at 11:25 PM ----------
If it fails this time, I will connect it to ADB with command line and manually push the apk onto the watch. I will give it until after dinner to complete the process.
Cant get it to install, and adb says its an invalid apk file when i try to push it. I suppose its not really necessary anyway. Ill just use KingRoot app if I need to do file management.
nethead72 said:
Seems like its taking way too long (going on 1 hour+). Gonna reboot and try again.
---------- Post added at 11:55 PM ---------- Previous post was at 11:25 PM ----------
If it fails this time, I will connect it to ADB with command line and manually push the apk onto the watch. I will give it until after dinner to complete the process.
Cant get it to install, and adb says its an invalid apk file when i try to push it. I suppose its not really necessary anyway. Ill just use KingRoot app if I need to do file management.
Click to expand...
Click to collapse
Did you confirm the apk was good? I'd try installing it on your phone. I don't think KingRoot has file management capabilities.
On a side note, I would advise against uninstalling anything. I just went to flash the previous OTA and it failed because I didn't have Jawbone installed.
You're busy and don't have time to wait, which is why you need to stop reading this thread and get back to organizing your Pogs. Rate this thread to express how the OnePlus 3 performs when multitasking. A higher rating indicates that the OnePlus 3 keeps many apps in memory so that they don't need to reload, and that when moving between apps, transitions are smooth and performance is excellent.
Then, drop a comment if you have anything to add!
Incredible after applaying the memory fix by settig the app limit to 42
Julius1993 said:
Incredible after applaying the memory fix by settig the app limit to 42
Click to expand...
Click to collapse
Any idea on how this affects battery life?
airchicken said:
Any idea on how this affects battery life?
Click to expand...
Click to collapse
So I also switched my background processes to 42, and I ended up dialing it back to 32, because I do think it affects battery life a bit. To be honest, at 42, I was using 5GB of RAM at a time, which was amazing (SO MANY apps in RAM), but honestly, while it's fun, it's not really helpful in day to day use. But the default setting of 20 is too low.
airchicken said:
Any idea on how this affects battery life?
Click to expand...
Click to collapse
Batterylife might be effected, but its perfectly fine for me. Im getting around 4h of SOT with brightness at 100% (adaptive) Wifi and Bluetooth turned on, connectet to my huawei watch and using it quite a lot. And there was literally no app cleared from ram. I will test it again with the value set to 36 though!
Its such a great experience to have a phone which doesn't have to start up an App twice.
Sounds great... but for me stock settings only end up getting about 2h of SOT wich seems to be not that much... Seems like Android System drains a lot...
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
By default limit is low but i think for day to day usage it is fine
I able to use only 3 to 4 apps daily for multi tasking and it is fine and giving me good battery experience.
Sent from my ONEPLUS A3003 using Tapatalk
Julius1993 said:
Incredible after applaying the memory fix by settig the app limit to 42
Click to expand...
Click to collapse
By stating a memory fix you are referring to rooting the phone prior to adjusting the value, correct?
Can someone post on how to do this without root - please give the adb commands. I know that a quora post was provided to do without root using adb etc but was not able to do this..
I was able to do the screen display density to 400 without root using adb commands (density) but was not able to do this. I will be very thankful if someone can do this.
airchicken said:
Any idea on how this affects battery life?
Click to expand...
Click to collapse
harharryhar said:
Can someone post on how to do this without root - please give the adb commands. I know that a quora post was provided to do without root using adb etc but was not able to do this..
I was able to do the screen display density to 400 without root using adb commands (density) but was not able to do this. I will be very thankful if someone can do this.
Click to expand...
Click to collapse
Go on Youtube and search vor "OnePlus 3 - How to Root". The Channel is called C4ETech. The Guy in the video gives you perfect instructions.
In the video description you will also find all the downloads you will need!
---------- Post added at 09:14 AM ---------- Previous post was at 09:10 AM ----------
harharryhar said:
Can someone post on how to do this without root - please give the adb commands. I know that a quora post was provided to do without root using adb etc but was not able to do this..
I was able to do the screen display density to 400 without root using adb commands (density) but was not able to do this. I will be very thankful if someone can do this.
Click to expand...
Click to collapse
You can not do this without root!!! All you can do wihtout root, is to pull the build.prop via adb (adb pull /system/build.prop <your desired location>), but you cannnot push it back to your phone, because you need access to your phones root directory which is read only out of the box.
---------- Post added at 09:20 AM ---------- Previous post was at 09:14 AM ----------
The simplest way to apply the memory fix is the following:
-Go on Youtube. Search for "OnePlus 3 - How to Root". The Channel is called C4ETech. The Guy in the video gives you perfect instructions. Its really easy, you will find all the downloads in the videos description.
-then download the build prop editor app from the play store and look for the right value (ro.sys.fw.gb_apps_limit=20) and change it.
Julius1993 said:
You can not do this without root!!! All you can do wihtout root, is to pull the build.prop via adb (adb pull /system/build.prop <your desired location>), but you cannnot push it back to your phone, because you need access to your phones root directory which is read only out of the box.
Click to expand...
Click to collapse
Thanks for your reply..but in the xda article on how to fix it , it says:
http://www.xda-developers.com/how-t...-management-almost-double-the-apps-in-memory/
"There are many ways to edit the build.prop, including pulling it through ADB without root or using root apps specifically designed for build.prop editing. I personally used Root Explorer this time around, but all methods should work."
The word ADB is linked to a quora page where the methods are mentioned, but I have not been able to get it to work:
https://www.quora.com/How-do-I-edit-the-build-prop-file-in-Android-without-Rooting-it
So there is no way to do without root as the article refers?
Incase of root ( I am worried about security), if there is a way to unroot it (will have to find it), the OTA update might change it back to 20, so do we have to keep the root on?
So will be really thankful if someone can give the exact ADB commands. Thanks for your help.
harharryhar said:
Thanks for your reply..but in the xda article on how to fix it , it says:
http://www.xda-developers.com/how-t...-management-almost-double-the-apps-in-memory/
"There are many ways to edit the build.prop, including pulling it through ADB without root or using root apps specifically designed for build.prop editing. I personally used Root Explorer this time around, but all methods should work."
The word ADB is linked to a quora page where the methods are mentioned, but I have not been able to get it to work:
https://www.quora.com/How-do-I-edit-the-build-prop-file-in-Android-without-Rooting-it
So there is no way to do without root as the article refers?
Incase of root ( I am worried about security), if there is a way to unroot it (will have to find it), the OTA update might change it back to 20, so do we have to keep the root on?
So will be really thankful if someone can give the exact ADB commands. Thanks for your help.
Click to expand...
Click to collapse
You can change the build prop without root, but you cannot push it back on your device. i have tried it without root, but its simply not possible and it doesnt make sense either. if you dont have access to write on your root directory you cannot change anything there.
i really recommend rooting. just by the fact, that you can get rid of all the in app commercials! (really awesome)
Also rooting will not void your warranty on your 1+3. you can alway unroot your device by flashing the stock rom back on your device!
You will find all the ADB commands in the video i was talking about before.
-adb devices
-adb reboot bootloader
-fastboot devices
-fastboot oem unlock (will wipe your device!)
-fastboot flash recovery recovery.img (TWRP Recovery [is needed])
-then reboot the device into recovery manually by using the volume and power button, not by the command fastboot reboot.
-install superuser
-Done
-Edit build.prop with buildprop editor and allow super user access.(easiest way for noobs)
Julius1993 said:
You can change the build prop without root, but you cannot push it back on your device. i have tried it without root, but its simply not possible and it doesnt make sense either. if you dont have access to write on your root directory you cannot change anything there.
i really recommend rooting. just by the fact, that you can get rid of all the in app commercials! (really awesome)
Also rooting will not void your warranty on your 1+3. you can alway unroot your device by flashing the stock rom back on your device!
You will find all the ADB commands in the video i was talking about before.
-adb devices
-adb reboot bootloader
-fastboot devices
-fastboot oem unlock (will wipe your device!)
-fastboot flash recovery recovery.img (TWRP Recovery [is needed])
-then reboot the device into recovery manually by using the volume and power button, not by the command fastboot reboot.
-install superuser
-Done
-Edit build.prop with buildprop editor and allow super user access.(easiest way for noobs)
Click to expand...
Click to collapse
I believe there is a utility that does this all for you as well. I don't have my OP3 yet but I have used utilities with my Moto G3 and it simplified the process a lot.
There is no Utility for the op3. And it already is very simple
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
Julius1993 said:
You can change the build prop without root, but you cannot push it back on your device. i have tried it without root, but its simply not possible and it doesnt make sense either. if you dont have access to write on your root directory you cannot change anything there.
i really recommend rooting. just by the fact, that you can get rid of all the in app commercials! (really awesome)
--
-Edit build.prop with buildprop editor and allow super user access.(easiest way for noobs)
Click to expand...
Click to collapse
I'm just an "interloper" curious about this new phone and noticed this while browsing the forum, and I've modified / files without root being "installed" on many phones before as long as someone had already created a custom recovery for it that worked (and supported adb when booted to custom recovery)::
Should be something like :
Code:
Boot to custom recovery ::
open shell and adb shell,
su // this should just work since recovery's are by definition already rooted and you're booted into it.
Make sure system is mounted (mount -o remount,rw /system) (or whichever switches it requires)
modify your file using the terminal mode or editor provided by TWRP/{other} and save
remount as read (mount -o remount, ro /system)
reboot.
I hope that helps, if not, I will shut up in this forum. I'm assuming TWRP for this device is about the same as for nearly every other one. Sorry if not,.
Cheers.
That's actully true! Haven't thought about that. You can Mount/remount by using a custom Recovery. But still I would recommend rooting, since it doesn't even Void your warranty
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
Dunno guys,i just got my phone yesterday,barely installed anything,like 3 apps running in the background and my Nonstop Knight game reloads in 7/10 tries.
With OOS 3.2 the RAM can (well, could) be used to its fullest. I simply could not throw enough at it to fill up. Five big, full 3D games, 20+ Chrome tabs, all my apps (30ish) open and still 1Gb remaining whilst load-less app-switching
The multitasking on this device is awesome! Good job OnePlus
If this phone had 4GB of RAM, I think it wouldn't have changed anything.
Does anyone know if they already have a solution to fix the fingerprint on any GSI on the moto g7 play?
I don't think there will be a fix for it. GSIs are basically developed for testing purposes and are not functionally ROMs.
---------- Post added at 07:01 AM ---------- Previous post was at 06:58 AM ----------
https://source.android.com/setup/build/gsi
Guhl0rd64 said:
Does anyone know if they already have a solution to fix the fingerprint on any GSI on the moto g7 play?
Click to expand...
Click to collapse
I'm working on this right now. It requires a jar from /system/framework, and some libs from the stock OS. And maybe an overlay, but that part I'm unsure about. If I get anything working I'll post a flashable zip.
Spaceminer said:
I'm working on this right now. It requires a jar from /system/framework, and some libs from the stock OS. And maybe an overlay, but that part I'm unsure about. If I get anything working I'll post a flashable zip.
Click to expand...
Click to collapse
man, you are the g7 play hero ngl, can you post an explanation of what needed to be done when youve done it, you know like the technical side, so people like me can learn?
00p513 said:
man, you are the g7 play hero ngl, can you post an explanation of what needed to be done when youve done it, you know like the technical side, so people like me can learn?
Click to expand...
Click to collapse
I use a few methods in general to figure stuff out.
1. Google, Arch linux Wiki, stack exchange.
2. Sleuthing. Go digging though system files or app manifests.
3. Poke it with a stick. Running strings or grep on a file for keywords. Poke the box with the right input, and it'll often give you prizes in return. This is especially true for things you can't just decompile like a bootloader image. You can even do things like tease partition mounts from a vendor image this way.
4. Load files into a hex editor. I personally use HxD. This works similar to the poke the box method. If strings and grep are like a radio, then using a hex editor is like watching TV.
5. Don't reinvent the wheel if you don't have to. Look for things that you know accomplish the same, or a similar task, then adapt them to your situation. This isn't always easy but 90% of the time it'll get you there or damn close.
This project is a combo of 2 and 5.
I first went digging through system and vendor files. I know from prior experience that apps and hardware features often require library files (/system/lib/*.so), bin files (/system/bin & /vendor/bin), jar files (/system/framework/*.jar), and permissions (/system/etc/permissons & (/vendor/etc/permissions). Occasionally hardware features also have an init script to start them. (/system/etc/init & /vendor/etc/init)
So I searched with a root explorer for any files in those locations that have "finger" in the name. That gave me gold. I made a note and created a file structure to match them, then copied the files over and created a zip.
This is where #5 comes in. In order to flash it, we need a script to tell twrp how to mount the partitions we're going to modify, where the files go, and what file permissions to set. (rw-r--r--, 0755 etc.) I knew how to do this from modifying phh's su to work on Lineage OS 17. And I learned how to do that by looking at the flashable zips for, viper for android, and the universal disabler. Since I had adapted those for Phh su, when I needed to do it again, I pulled the scripts from Phh su and edited them to use the new files and permissions.
That's the jist of it. If you want to see how the scripts are written, extract the zip and look at META-INF/com/google/android/updater-script with a text editor. I recommend either Quick Edit pro for android, or notepad++ if using Windows.
Finger Print Test #1
If anyone running a GSI wants to test this, just flash it in twrp and let me know if the finger print sensor works. It should NOT break anything. If you get any flashing errors please tell me. It means there's a typo somewhere in the scripts and I need to fix it.
Spaceminer said:
I use a few methods in general to figure stuff out.
1. Google, Arch linux Wiki, stack exchange.
2. Sleuthing. Go digging though system files or app manifests.
3. Poke it with a stick. Running strings or grep on a file for keywords. Poke the box with the right input, and it'll often give you prizes in return. This is especially true for things you can't just decompile like a bootloader image. You can even do things like tease partition mounts from a vendor image this way.
4. Load files into a hex editor. I personally use HxD. This works similar to the poke the box method. If strings and grep are like a radio, then using a hex editor is like watching TV.
5. Don't reinvent the wheel if you don't have to. Look for things that you know accomplish the same, or a similar task, then adapt them to your situation. This isn't always easy but 90% of the time it'll get you there or damn close.
This project is a combo of 2 and 5.
I first went digging through system and vendor files. I know from prior experience that apps and hardware features often require library files (/system/lib/*.so), bin files (/system/bin & /vendor/bin), jar files (/system/framework/*.jar), and permissions (/system/etc/permissons & (/vendor/etc/permissions). Occasionally hardware features also have an init script to start them. (/system/etc/init & /vendor/etc/init)
So I searched with a root explorer for any files in those locations that have "finger" in the name. That gave me gold. I made a note and created a file structure to match them, then copied the files over and created a zip.
This is where #5 comes in. In order to flash it, we need a script to tell twrp how to mount the partitions we're going to modify, where the files go, and what file permissions to set. (rw-r--r--, 0755 etc.) I knew how to do this from modifying phh's su to work on Lineage OS 17. And I learned how to do that by looking at the flashable zips for, viper for android, and the universal disabler. Since I had adapted those for Phh su, when I needed to do it again, I pulled the scripts from Phh su and edited them to use the new files and permissions.
That's the jist of it. If you want to see how the scripts are written, extract the zip and look at META-INF/com/google/android/updater-script with a text editor. I recommend either Quick Edit pro for android, or notepad++ if using Windows.
Finger Print Test #1
If anyone running a GSI wants to test this, just flash it in twrp and let me know if the finger print sensor works. It should NOT break anything. If you get any flashing errors please tell me. It means there's a typo somewhere in the scripts and I need to fix it.
Click to expand...
Click to collapse
Wow, thank you very much my friend, I will test now
Spaceminer said:
I'm working on this right now. It requires a jar from /system/framework, and some libs from the stock OS. And maybe an overlay, but that part I'm unsure about. If I get anything working I'll post a flashable zip.
Click to expand...
Click to collapse
Thank you.
---------- Post added at 06:41 PM ---------- Previous post was at 06:40 PM ----------
Guhl0rd64 said:
Wow, thank you very much my friend, I will test now
Click to expand...
Click to collapse
So...?
Marcondes BR said:
Thank you.
---------- Post added at 06:41 PM ---------- Previous post was at 06:40 PM ----------
So...?
Click to expand...
Click to collapse
I installed by TWRP, I have Lineage OS 17.1, still with the same problem
Descendent Modified GSI, doesnt work. It sees the reader, but doesnt recognise me touching it
Spaceminer said:
I use a few methods in general to figure stuff out.
1. Google, Arch linux Wiki, stack exchange.
2. Sleuthing. Go digging though system files or app manifests.
3. Poke it with a stick. Running strings or grep on a file for keywords. Poke the box with the right input, and it'll often give you prizes in return. This is especially true for things you can't just decompile like a bootloader image. You can even do things like tease partition mounts from a vendor image this way.
4. Load files into a hex editor. I personally use HxD. This works similar to the poke the box method. If strings and grep are like a radio, then using a hex editor is like watching TV.
5. Don't reinvent the wheel if you don't have to. Look for things that you know accomplish the same, or a similar task, then adapt them to your situation. This isn't always easy but 90% of the time it'll get you there or damn close.
This project is a combo of 2 and 5.
I first went digging through system and vendor files. I know from prior experience that apps and hardware features often require library files (/system/lib/*.so), bin files (/system/bin & /vendor/bin), jar files (/system/framework/*.jar), and permissions (/system/etc/permissons & (/vendor/etc/permissions). Occasionally hardware features also have an init script to start them. (/system/etc/init & /vendor/etc/init)
So I searched with a root explorer for any files in those locations that have "finger" in the name. That gave me gold. I made a note and created a file structure to match them, then copied the files over and created a zip.
This is where #5 comes in. In order to flash it, we need a script to tell twrp how to mount the partitions we're going to modify, where the files go, and what file permissions to set. (rw-r--r--, 0755 etc.) I knew how to do this from modifying phh's su to work on Lineage OS 17. And I learned how to do that by looking at the flashable zips for, viper for android, and the universal disabler. Since I had adapted those for Phh su, when I needed to do it again, I pulled the scripts from Phh su and edited them to use the new files and permissions.
That's the jist of it. If you want to see how the scripts are written, extract the zip and look at META-INF/com/google/android/updater-script with a text editor. I recommend either Quick Edit pro for android, or notepad++ if using Windows.
Finger Print Test #1
If anyone running a GSI wants to test this, just flash it in twrp and let me know if the finger print sensor works. It should NOT break anything. If you get any flashing errors please tell me. It means there's a typo somewhere in the scripts and I need to fix it.
Click to expand...
Click to collapse
I have tested on several GSI, and I have had no success
Guhl0rd64 said:
I have tested on several GSI, and I have had no success
Click to expand...
Click to collapse
You might need to add ro.fpsensor.position=1 & persist.qfp=false to the build prop.
Spaceminer said:
You might need to add ro.fpsensor.position=1 & persist.qfp=false to the build prop.
Click to expand...
Click to collapse
it still didn't work
Guhl0rd64 said:
it still didn't work
Click to expand...
Click to collapse
I'm unfortunately out ideas at this point.
Spaceminer said:
I'm unfortunately out ideas at this point.
Click to expand...
Click to collapse
I guess this means no fingerprint on Ubuntu Touch when i get it to work