Here is a great script that is apparently making its way through the android world. It increases the SD card read/write by reading in larger chunks. You can get it to work on Fascinate somehow.
Many of us in the Eris world have gotten this to work and my now SLOW eris reads pictures and related SD functions twice as fast as my fascinate!! Now to start testing this on my ever godly fascinate...
sharing the wealth:
http://forum.xda-developers.com/showthread.php?t=1013554
This can technically be hard coded into ROMS, but im no ROM developer (hint hint)
----update-----
I didn't find anyone in the Fascinate world doing this, but apparently the Epic has this somewhat working:
http://forum.xda-developers.com/showthread.php?t=1021647
----update----
And here are the Epic versions flashable files... i'll test them later today to see if they work on the fascinate:
http://forum.xda-developers.com/showpost.php?p=12660493&postcount=73
Sounds great. I was just complaining about my pictures loading slowly yesterday, and here you are to save the day!
I'm backing up my phone now, and will flash the 2k file.
I did test this app, which essentially does the same thing, and it does work great on the fascinate. But, its an app that has to be turned on, and wont stick at boot. Although the app does have a set at boot option... thats still one more app running at boot.
http://www.appbrain.com/app/sd-increase/com.sdincrease.it
I'll post results on my flashing of the scripts shortly.
ok I can confirm the following did stick at boot.
njoy everyone:
SDCardSpeedFix2048KB.zip
I tried that app, and I'm not sure that it even worked. You probably know more than I do, but after doing the setting in SD Speed Increase i can open the file and it still says 128. i also tried it on my eris and it did change the file to 2048. Weird. Is there gonna be a link to a flashable in your post. thanx...
Izeltokatl said:
ok I can confirm the following did stick at boot.
njoy everyone:
SDCardSpeedFix2048KB.zip
Click to expand...
Click to collapse
Worked perfect. Thanks so much. The slow loading gallery always really bothered me
Sent from my SCH-I500 using XDA App
cableguy1 said:
I tried that app, and I'm not sure that it even worked. You probably know more than I do, but after doing the setting in SD Speed Increase i can open the file and it still says 128. i also tried it on my eris and it did change the file to 2048. Weird. Is there gonna be a link to a flashable in your post. thanx...
Click to expand...
Click to collapse
check my last link in the OP. All the various flashable files are in that link. I used 2k version. Thats what I used in my Eris.
the app you have to use the slider to adjust the amount (again use 2048) click on that RED/ORANGE button with the arrow and it will set it.
what it says in "Status" is what is defined in your phone. So thats how you can confirm it worked. Or just open up the gallery and compare a large folder before the flash(or app change), and then run the same gallery folder after the flash (or app change). It should be MUCH faster.
Ok, now the 2048k from that link worked great.
But just for the record, I did push that button to finalize the setting in SD Speed Increase . I don't know why it didn't change the file...oh well, thanks a lot sir!
Sent from my SCH-I500 using XDA Premium App
jt1134 implemented this about a week ago, and I and several others did the same with the custom kernels that were released. If it's being set in the initramfs and not via an init.d script, you can change the values all you want and it likely isn't doing anything to change the read/write performance.
imnuts said:
jt1134 implemented this about a week ago, and I and several others did the same with the custom kernels that were released. If it's being set in the initramfs and not via an init.d script, you can change the values all you want and it likely isn't doing anything to change the read/write performance.
Click to expand...
Click to collapse
From what I can tell the flash files are writing to the init.d. So it should be sticking. This is still good to know as some people might not be using custom kernels, or might want to change from whatever defaults the kernel devs have pre-set.
Options are in the spirit of Rooting
=-)
Izeltokatl said:
From what I can tell the flash files are writing to the init.d, so the settings are taking effect. So it should be sticking.
Click to expand...
Click to collapse
If the change is applied in the initramfs, that will likely take precedence over the init.d script, but I have no idea how it works if there are two things telling it what to run at.
Related
Hi everyone.
I am using the SalsaSense ROM. I am unable to post in that thread because I am new here, so I'm hoping someone here will be able to help me.
In the stock SMS app there is the option to delete old messages once a limit has been reached. I installed the ROM, recovered my messages, and enabled the option in the stock app with the limit set at 200. But my old messages are not being deleted. With one contact I have 7k+ messages, and since enabling the option I have sent and received several messages with them. When I had Elelinux-7.1.0-Hero-v2.6 installed beforehand, following these steps was enough to provoke it to keep my inbox in check. But not now.
Is this a problem with the ROM, or the stock app, or am I just unlucky?
I'm hoping someone here may have come across this and can help me out.
Many thanks, BurnseyBoi
I think you've been unlucky. It sounds like a ROM problem since it's beta.
You could delete them using an app like SuperSMS Delete (I think it's that).
Yeah, guess I'll just have to wait for an update to it. I had a look round the market and found the app you were referring to. Worked a charm, thanks very much! Now my phone is a bit speedier.
Yeah i noticed this, unfortunately its a problem with the ROM. I've got a lot of issues to iron out so it takes me a while to solve each one, rest assured though it will be fixed
Sent from my Hero using XDA Premium App
Awesome, glad to hear it
I love this ROM! I forgot how much I missed the little Sense features and looks. My friend just got himself a Sensation, which is where I got the idea to browse around for a Sense ROM. Many thanks!
JieeHD said:
Yeah i noticed this, unfortunately its a problem with the ROM. I've got a lot of issues to iron out so it takes me a while to solve each one, rest assured though it will be fixed
Click to expand...
Click to collapse
I'm trying to follow the build.prop editing suggestion, but adb doesn't list my phone under connected devices. I've tried while the phone is on, and in recovery.
Is there another way of successfully editing it?
Yeah, you can use Root Explorer from the Market. ES File explorer may work too, look in the app's settings for Root options.
Navigate to the directory with the build.prop and long press and I think there's an edit option if you use Root Explorer. Then you can just edit as you would normally via the phone.
Thanks! I already had ES File Explorer, didn't realise it had root options though.
Made both changes that JieeHD suggested, then powered it off and back on. I've never seen my phone go from power button to lock screen that fast in the 2 years I've had it! I definitely notice a speed improvement from making those changes. Everything just feels sharper and more responsive.
Many thanks!
BurnseyBoi said:
Thanks! I already had ES File Explorer, didn't realise it had root options though.
Made both changes that JieeHD suggested, then powered it off and back on. I've never seen my phone go from power button to lock screen that fast in the 2 years I've had it! I definitely notice a speed improvement from making those changes. Everything just feels sharper and more responsive.
Many thanks!
Click to expand...
Click to collapse
I've tried them and can confirm they do speed things up.
Wish there was some option to use a standard notification bar, I think it would help.
hero_pt said:
I've tried them and can confirm they do speed things up.
Wish there was some option to use a standard notification bar, I think it would help.
Click to expand...
Click to collapse
I agree. I tried following the instructions in this thread but I couldn't get it to work. Has anyone else using this ROM been able to successfully do this?
I am new here and new with Android too . I'd install UrukDroid 1.0 in internal my Archos 101. I can use compcache but I can't enable the swap in Urukconfig. It keep saying ERROR: VALUE NOT FOUND! NO CHANGE MADE.
So, anyone here know how to do it. Please help...... Im a PC guy, don't know anything about Linux.
THANK YOU VERY MUCH.
Sent from my A101IT using XDA Premium App
steven20052009 said:
I am new here and new with Android too . I'd install UrukDroid 1.0 in internal my Archos 101. I can use compcache but I can't enable the swap in Urukconfig. It keep saying ERROR: VALUE NOT FOUND! NO CHANGE MADE.
So, anyone here know how to do it. Please help...... Im a PC guy, don't know anything about Linux.
THANK YOU VERY MUCH.
Sent from my A101IT using XDA Premium App
Click to expand...
Click to collapse
Swap has been set to use a partition, so you'll have to change it back to using an image file.
I'm going from memory here, but use root explorer to edit /etc/uruk.conf/swap. You have to comment(add a #) swap_mem_partition=/dev/block/mmcblk1p4 and uncomment(remove the #) swap_mem_file=/swap01.file.
Then you can use urukconfig to enable it and change the size and swappiness.
Hi, can you just give me the whole things of comment and steps? I don't know how to edit in root explorer and where should I do the comments. Im really stupid in these things man please help me.... sorry to ask you alot.... have a good day.
Sent from my A101IT using XDA Premium App
steven20052009 said:
Hi, can you just give me the whole things of comment and steps? I don't know how to edit in root explorer and where should I do the comments. Im really stupid in these things man please help me.... sorry to ask you alot.... have a good day.
Sent from my A101IT using XDA Premium App
Click to expand...
Click to collapse
Open root explorer. Navigate to /etc/uruk.conf. Press and hold on "swap" until the menu comes up. Scroll down and select "Open in Text Editor". Add a "#" to "swap_mem_partition=/dev/block/mmcblk1p4" It should look like this:
Code:
# swap_mem_partition=/dev/block/mmcblk1p4
Then remove the # from "# swap_mem_file=/swap01.file" and "# swap_mem_size=50" so it looks like this:
Code:
swap_mem_size=50
swap_mem_file=/swap01.file
Then enable swap in Urukconfig. In the future, check the wiki first, it may help.
http://code.google.com/p/urukdroid/wiki
Thank you very much..... I' ve read from google several times but could't understand... that why I ask you. BTW... Thanks .... good night.
Sent from my A101IT using XDA Premium App
steven20052009 said:
Thank you very much..... I' ve read from google several times but could't understand... that why I ask you. BTW... Thanks .... good night.
Sent from my A101IT using XDA Premium App
Click to expand...
Click to collapse
No problem. It can be hard to understand without experience. Doesn't make you dumb.
Without wishing to sound like a complete noob what does enabling swap do for you?, performance?. Thanks for your patience lol
sent from the awesomeness that is my SGS2
stigslim said:
Without wishing to sound like a complete noob what does enabling swap do for you?, performance?. Thanks for your patience lol
sent from the awesomeness that is my SGS2
Click to expand...
Click to collapse
Swap is extra space the system can use as RAM. It doesn't work exactly the same though. For instance, if you set a 1 gig swap file, so the system theoretically has 1.25 GB of ram, it will still not act like it. In my experience, I've only seen 5-10 megs of swap space used, then the system starts killing background apps again, so I set my swap to 50MB and forget about it. Someone else may have more details on how the system actually uses the swap. I have a feeling apps don't use swap, only the underlying unix framework, but I've never really cared enough to look into it. Also, keep in mind that using solid-state storage for swap will reduce the life of the storage, since the system is constantly reading and writing to that portion of it(solid-state storage will crap out after a certain number of write cycles, it's hard to say how badly swap will affect this though).
Sounds like more hassle than its worth. Is there that much of an improvement in overall performance to warrant the effort?.
sent from the awesomeness that is my SGS2
stigslim said:
Sounds like more hassle than its worth. Is there that much of an improvement in overall performance to warrant the effort?.
sent from the awesomeness that is my SGS2
Click to expand...
Click to collapse
It just depends on how you use your device. On the newest stock firmware, when I start watching a video in the stock video player, it will kill Launcher Pro in the background. If I enable swap, it doesn't kill it. But playing a game like Gun Bros will always kill LP in the background. If you frequently have the launcher restarting(reloading all your widgets) when you go back to home, you should probably give it a shot. If you're on Uruk, it's not hard to enable, just have to edit one file with a text editor, and you can do it in root explorer.
Thank you. I am a long time looking for a way how to make the swap work
I'm not sure why but whenever I flash a GB ROM the widgets in overview mode jump around too much/too fast to the point where I can't even accurately choose which one I want to go to. It's smooth at first after a fresh boot/reboot but as time goes on my overview mode always starts to act crazy no matter which ROM I flash (I've been going back n forth between EWJET and WB and it happens with both of them). Is it possible to get the stock overview mode from GB with the widgets that are static and don't move round like in these custom versions? Any help would be appreciated, this is the only feature I am starting to not like.
I suspect this has to do with the fps unlock. I noticed it worked OK without it.
Sent from my X10i using XDA App
speig said:
I suspect this has to do with the fps unlock. I noticed it worked OK without it.
Sent from my X10i using XDA App
Click to expand...
Click to collapse
I didn't even think of that! That does sound like it could be a valid reason. Thanks!
Hey speig, do you know if there's a way to remove the uncap/restore the 30 or 32 (whichever it is) cap? I searched and found a solution in a thread that says to delete some line from a file in root explorer but it's not letting me edit the file, just view it even though I enable all permissions. Thanks in advance if you're able to help!
Scratch that...I was able to use ES file explorer/manager to restore the cap
Simple script to run to maximize the MoPho's RAM usage. **ROOT USERS ONLY**
I take NO credit for this tweak whatsoever, and am simply providing a quick "how-to" of how to run the script for those who have not used it on previous Android devices.
Here's the link to the original thread (in the general section in the MoPho forum), created by member Custodian on 8/11/11. Big thanks to him for that! http://forum.xda-developers.com/showthread.php?t=1212820
First, follow the ongoing development threads to familiarize yourself of what this tweak truly accomplishes:
http://forum.xda-developers.com/showthread.php?t=991276
http://forum.xda-developers.com/showthread.php?p=15948434#post15948434
Secondly, follow this how-to, in this order:
1) Download the script of your choice from the second hyperlink above, or from - http://forum.xda-developers.com/show...postcount=5021
2) Download Script Manager from the Market (free app).
3) Wipe your caches.
4) Open Script Manager, locate the script you dl'd on your SD Card, select "run as root", and DO NOT select "run as boot".
5) Load the script (select 1 or 0 for scrolling speed). It will most likely tell you that you are running too new of a Busybox version, and may experience bootloops. You're fine. Busybox v1.19.2-Stericson runs just fine, no issues.
6) Once script loads, enter selection #9 (Super 1000hp Aggressive mem setting).
7) Enter selection #13 to "bulletproof" your Launcher (helps eliminate risk of having it close during while your mem settings are working)
8) Enter selection #19 for Nitro Lag Nullifer, and install.
9) Enter selection #25 for options. Enter y for build.prop edit.
10) Enter selection #27 to close the script.
Now, reopen Script manager and navigate to the folder /sdcard/V6_SuperCharger. Run the 99SuperCharger.sh script, and select to "run as root", and "run as boot".
Reboot your phone, and you are good to go.
You can create widgets to quickly shift between memory tweaks.
Lastly, you can run the V6 script and select #19 to "flush" your caches and reclaim any lost RAM throughout the day to keep your phone running optimally without having to reboot your phone or "kill" any apps through various task managers. I do this about 1x-2x a day just as habit, but not necessary by any means. (A widget can be created for this too - open Script Manager, and find /data/fast_engine_flush.sh. One click RAM re-claimer!)
That's it. No need for any 3rd party task managers (ATK, Auto Killer, etc.). Just let the script do its thing, and enjoy a lag free MoPho!
this is great - I ran across this the other day - very easy to install and activate - my phone seems to be very reponsive - quite a interesting MOD - thanks for posting!
Latest script - RC3.2
http://forum.xda-developers.com/show...postcount=5021
Nice, I'll try out RC1. BTW, has anyone tried his 3g turbocharger?
This is weird. I keep getting ... "AWK Not Found. Unable to determine busybox version."
Root Check says I have busybox-1.18.0git. wtf?
MisterTedster said:
Nice, I'll try out RC1. BTW, has anyone tried his 3g turbocharger?
Click to expand...
Click to collapse
Yes. I'm still on the fence as far as noticing any performance gains, though...
Sent from my MB855 using XDA App
tuxytuxy said:
This is weird. I keep getting ... "AWK Not Found. Unable to determine busybox version."
Root Check says I have busybox-1.18.0git. wtf?
Click to expand...
Click to collapse
Try installing a newer Busybox version...that should fix that.
Sent from my MB855 using XDA App
My settings wouldn't stick after reboot (using homebase 2.1)
Had to use Script Manager to load /system/etc/init.d/99SuperCharger "on boot" and "run as root" (for me it was called S99SuperCharger)
MisterTedster said:
Nice, I'll try out RC1. BTW, has anyone tried his 3g turbocharger?
Click to expand...
Click to collapse
Just did. I had some weak download speeds at work this morning, only getting to 550kps tops, using the experimental 1 setting doubled my down speed to 1meg.
cobrahicks said:
My settings wouldn't stick after reboot (using homebase 2.1)
Had to use Script Manager to load /system/etc/init.d/99SuperCharger "on boot" and "run as root" (for me it was called S99SuperCharger)
Just did. I had some weak download speeds at work this morning, only getting to 550kps tops, using the experimental 1 setting doubled my down speed to 1meg.
Click to expand...
Click to collapse
NICE!
I get crap 3G speed @ work regardless of which 3G script I run (.2-.4 down on avg), but .8-1.0 avg w/ 4G. I didn't realize that it doesn't exactly hurt the battery life tremendously to leave 4G enabled on the MoPho, as it puts itself into a sleep mode when not in use. I'm not sure of the specifics as far as scan/refresh intervals right off hand, but I'm tracking approx 1% of batt. life lost every 10 minutes while the phone is idle and 4G enabled (data disabled, as I'm sure I'd be losing 3-4% batt. life in the same range w/ it enabled w/ 4G).
Dumb question: Anything special I should know to run 3G turbocharger?
MisterTedster said:
Dumb question: Anything special I should know to run 3G turbocharger?
Click to expand...
Click to collapse
Nope. Just run the script and select the option that's best for you and reboot. Test all 4 and the experimentals.
YMMV - not all phones behave the same, and I'm sure 3G gains/losses are still contingent upon your location anyway, so you may experience a boost, a loss or no change at all. Either way, it won't hurt anything to try it.
Now RC2 is out... The best setting for MoPho is option 9+12.... Use build prop option to stick otherwise will not stick after reboot.... V6 default windowsmgr event setting is only 75. If you want better smooth scolling change this line "windowsmgr.max_event_per_sec=75 to 150(got two lines not include original line). Well 3g tweak is depend on your service provider.... test with speed test.net and find which setting is the best for you.
Sent from my MB855 using Tapatalk
pswin09 said:
Now RC2 is out... The best setting for MoPho is option 9+12.... Use build prop option to stick otherwise will not stick after reboot.... V6 default windowsmgr event setting is only 75. If you want better smooth scolling change this line "windowsmgr.max_event_per_sec=75 to 150(got two lines not include original line). Well 3g tweak is depend on your service provider.... test with speed test.net and find which setting is the best for you.
Sent from my MB855 using Tapatalk
Click to expand...
Click to collapse
Thanks man, OP has been updated accordingly w/ latest release info.
MisterTedster said:
Nice, I'll try out RC1. BTW, has anyone tried his 3g turbocharger?
Click to expand...
Click to collapse
i have both running on my phone and it is pretty fast, i used the experimental #1 for the 3g and i was hitting 1+ meg downloads which is faster than the .48-.75 that i normally get. usually when i open my browser on 3g it takes a while to load even the google homepage but now it pops up as soon as i open the browser no load time same for xda took a while before now it loads really quick almost ike i have 4g on i had to double check and make 4g was the first time i tried it because it was so much faster.
RC3.1 is out already. Looks like there are a bunch of fixes and enhancements.
where do you see the RC3.2?
http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021
Does anyone know how this runs with my kernel
Sent from my MB855 using XDA App
Install zepps kickass kernel and v6 ...you'll get some great results using your kernel. Forgot to post, with your latest rev and a few tweaks im rocking 4500's in smartbench.
jokersax11 said:
Does anyone know how this runs with my kernel
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
Does this work on stock rom
Sent from my MB855 using XDA App
Drop this file in your /system/etc folder, replacing the stock one. Cleaned up, and modified to work with a stock kernel or lean kernel.
Please open up the file, and read some of the notes I added, so you know what this does and how to change it if you so desire. It is very basic and straightforward.
Also, please remember one thing, if you want to go to the stock kernel, simply change any words in the scripts from "interactiveX" to "interactive".
Recommended lean kernel 3.16 with these scripts.
Designed to work with ALL Galaxy Note 3's running touch wiz 4.4.2 ROMs and running lean kernel or stock kernel. Other kernels are not guaranteed due to the voltages applied.
This will make a huge difference in performance and battery. Been using this (developed by me) for a long time now.
Summary:
*I/O optimization
*tuned interactive parameters
*fixed sysfs permissions for cpu's (root now has full control of sysfs tuneables)
*GPU sysfs identified for user to customize
*screen off frequency set to 1.2 GHz (can be changed by user)
*custom voltage set for bin 2 device. (Read instructions within file to adjust for others bins accordingly)
*custom mpdecision tuning and other relevant instruction regarding mpdecision binary
*general CPU tweaks for better performance, responsiveness and battery life (yes all 3 can be achieved, and are)
Again, open the file with a file explorer (or notepad+ in windows). Read it, understand it, adjust what you want, or leave it be. These settings are very much dialed in for the interactiveX governor of LK. It won't get much better. I'd say take a look at the voltage portion and mpdecision for now (found at the end).
Once more, drop file into the /system/etc directory... Replace the existing one, and reboot.
FILE DOWNLOAD
Updated today... many useful changes, and fixes (set up for stock kernel for now)
https://www.dropbox.com/s/tjlygujptls3lks/init.qcom.post_boot.sh?dl=0
Nice but it breaks fauxsound
Edit: nevermind
" I'm a Junglist soldier"
Nice work, thanks for the contribution. Glad to see you here.
Speeds up the UI.
Thanks
The comment aren't "G" rated...
Just giving you all a heads up.... I think there may have been a few errors in the stock init.qcom.post_boot file (they are human too, remember).
I am testing a few small changes to certain lines in the "factory" script to make sure. A brief explanation of it is that there are certain lines I removed from the one you all are using right now, and I did so because the file paths being called out did not exist!
However, I was going over this again tonight, getting ready for the official LP release and decided to review this odd discrepancy one more time. After doing some digging, I found that the file that some of those values were intended to be written to, were actually somewhere else!
Doh! - Sammy/QC. It is very possible that this location changed from a previous design or fs structure and somebody simply forgot to modify the script. Very interesting indeed.
Anyways, after I run this for a couple of days and do a little bit more investigating, I'll post the updated script for all of you.
Looking forward to trying
Sent from my 0x1 Note 3...... I love tep
Updated link... highly recommend updating this if you were using my previous one.
red_can_soda said:
Updated link... highly recommend updating this if you were using my previous one.
Click to expand...
Click to collapse
Is there still a need to change any statements to use this with the stock kernel? I browsed the file and didn't see any "interactiveX" statements to change.
Sent from my SM-N900P using Tapatalk 2
biggdevon said:
Is there still a need to change any statements to use this with the stock kernel? I browsed the file and didn't see any "interactiveX" statements to change.
Sent from my SM-N900P using Tapatalk 2
Click to expand...
Click to collapse
Guessing not we were to remove X for the stock kernel.
rbeavers said:
Guessing not we were to remove X for the stock kernel.
Click to expand...
Click to collapse
Just wanted to make sure there weren't any other changes to make, other than those. It appears this was designed for the Lean kernel but worked on stock if small changes were made (as stated in the OP). He updated the file and appearently removed the "X" statements. I just wanted to play it safe and make sure there weren't any other changes that needed to be made on my end seeing as I'm using the stock kernel.
Just to clarify...
The updated version, is set up for stock, but if you are using lean kernel, simply modify the "echo interactive > /sys/...." Statements (there are 4 total, towards the top of the script) to say "interactiveX"... As lean kernel's version of interactive is called this.
That is the only thing you need to change. Everything else is fine.
Will this work with Xposed framework?
Sent from my SM-N900P using Tapatalk 2
biggdevon said:
Will this work with Xposed framework?
Sent from my SM-N900P using Tapatalk 2
Click to expand...
Click to collapse
I am not having any problems running both.
biggdevon said:
Will this work with Xposed framework?
Sent from my SM-N900P using Tapatalk 2
Click to expand...
Click to collapse
Yes
Tested this tonight. Caused "No SIM card" message and reboot after 3-5min of run time. Any suggestions?
Sent from my SM-N900P using Tapatalk 2
biggdevon said:
Tested this tonight. Caused "No SIM card" message and reboot after 3-5min of run time. Any suggestions?
Sent from my SM-N900P using Tapatalk 2
Click to expand...
Click to collapse
Hard to say without a log or any other information.
What ROM you running?
red_can_soda said:
Hard to say without a log or any other information.
What ROM you running?
Click to expand...
Click to collapse
Completely stock NC5, rooted, with Xposed. I'm not really new to this but haven't ever had to grab a log file. Would happily post one if I knew how
Sent from my SM-N900P using Tapatalk 2
biggdevon said:
Completely stock NC5, rooted, with Xposed. I'm not really new to this but haven't ever had to grab a log file. Would happily post one if I knew how
Sent from my SM-N900P using Tapatalk 2
Click to expand...
Click to collapse
Next time you have a reboot, copy this file to your SD card:
/proc/last_kmsg
And upload it, then send it to me.
red_can_soda said:
Next time you have a reboot, copy this file to your SD card:
/proc/last_kmsg
And upload it, then send it to me.
Click to expand...
Click to collapse
Seems as though it has something to do with wifi and/or wifi calling. Phone ran fine for 3 hrs while at work and rebooted almost instantly once I got home. I don't see "last_kmsg" but I do have "kmsg" by itself. Attempting to copy to SD but it's going on 5 min without finishing. I'm using Root Explorer. Am I missing something?
Sent from my SM-N900P using Tapatalk 2
Kmsg isn't the one you want, that is a live log that is constantly writing dmsg lines. It will not stop copying..
If you don't have last_kmsg, it has likely been disabled by whatever kernel developer made the kernel you are using... If you are on stock and aren't seeing it, the only thing I can recommend is to run logcatX or some similar app that will allow you to filter errors only and log those to your SD card.