Related
After being able to unlock and flash Hairybean recently, I've definitely found a new love for my tablet. One thing that was never quite solved for me though was the lag after an application install, uninstall, or update action. To elaborate, after I'd do any of these actions, the tablet would take about 15-20 seconds to "catch up" and perform well again. data2sd may be a fix, but seeing as how complicated it is to get it working, this is one of my last resorts. Does anyone else have this issue and have a possible solution?
bump..just curious if this is still an issue that's fixable with any of the ROMs out there?
I have been experiencing a series of force closes. I am posting this to see if anyone else has experienced this, and whether anyone can suggest a fix. I'm pretty sure it was something I did, but I'm not sure what. I'm hoping that this can maybe narrow it down.
Device: SM-N900P
Firmware: OC5, stock, rooted, with several tweaks and modifications(detailed below).
The problem: I am getting several force closes. They only occur when I am trying to open certain settings. So, they aren't just popping up at random. They are slightly troubling, but not really problematic. Which is to say, aside from the actual force closes themselves, I don't really seem to be experiencing any major problems. Here are the FC's I am experiencing:
-Menu> Settings> General> Battery: This one results in a "Unfortunately, Settings has stopped" dialog box, and an immediate return to my home screen. So, I can't check out my battery usage. I'm not seeing any crazy battery drain. By opening Root Explorer and navigating to data> system> batterystats.bin, and deleting batterystats.bin, the problem is kind of fixed- I can open battery from the settings menu after that. But there is only battery level and state displayed, no usage information(just a message saying it is not available).
-Menu> Settings> General> Developer options> Process Stats: Results in the same dialog box, and the background turns black if I don't press "OK". I'm not even sure what this does, but after my Battery started force closing, I started checking the rest of the settings out.
-Menu> Settings> Connections> Data usage: Dialog box, immediate return to home screen.
The probable cause: hard to say, I've done a few things to it. Like I said, I was hoping that someone would be able to figure out what I've done from the following information about what I have done so far. So, here goes.
I was on NK4, running Priest Punch ROM. I reverted to stock and took the OTA about a week or so ago. I immediately rooted and installed TWRP using the method in this thread: http://forum.xda-developers.com/note-3-sprint/general/how-to-root-note-3-lollipop-t3089382 .
After rooting, I didn't see a whole lot of OC5 development, so I started poking around to see what kinds of mods I could use. First thing I wanted to do was remove bloat. I started off using Root Explorer, then I happened upon this thread featuring a bloatware removal tool for the T-Mobile variant: http://forum.xda-developers.com/note-3-tmobile/development/tool-utility-sgn3-sm-n900x-bloat-t2813036 . It worked. I removed a bunch of apps, but nothing I wasn't sure I could safely remove(I had to check Google a few times). I did not notice any problems at this time.
Then I installed this mod to pump sound out of both speakers: http://forum.xda-developers.com/note-3-sprint/development/mod-sm-n900p-surround-sound-t2966042 . I did not notice any problems at this time.
Next, I decided I wanted more fonts, so uninstalled the preloaded fonts and pushed the apk from this thread: http://forum.xda-developers.com/showthread.php?t=2752379 . Again, no problems.
I decided that a working hotspot would be nice, so I used the method in this thread to get one: http://forum.xda-developers.com/note-4-sprint/general/lollipop-hotspot-root-flashing-t3048163 . I tested it and it worked. No problems.
I really wanted to silence my shutter sound, and I happened upon this Galaxy S4 thread: http://forum.xda-developers.com/showthread.php?t=2261789 . It worked, and there were no issues. This was my first exposure to csc codes. I found a similar thread for the s6( http://forum.xda-developers.com/galaxy-s6-edge/general/quick-guide-enabling-hidden-features-t3087506 ), and followed the instructions. I was able to enable the camera during calls and enable call recording. No problems here. I tried a keyboard mod from the same thread, which had no effect at all(good or bad), so I reverted the code for that one back.
This is when I think I started to go off the rails a bit. I saw a thread for the Polish variant of the Note 3, N9005. http://forum.xda-developers.com/gal...camera-mod-note-3-n9005-lollipop-5-0-t3067827 -it had a neat sounding mod designed to improve camera quality, remove recording time and snapshot restrictions, and make 60fps HD the default camcorder mode. It took a little trial and error to get it installed, but I was making backups of files I was messing with, and was able to quickly and easily reverse any missteps. Again, the mod works fine, and I have noticed no issues. So, I started looking at the dev's other work. Which led me to this thread: http://forum.xda-developers.com/galaxy-note-3/themes-apps/secsettings-mod-17-swipe-charging-t3046032 . I wanted some different unlock effects, and I wasn't really finding them, so I tried his mod out. It was a 3 step process: replace a SecSettings app, copy paste some .ogg files, and finally, copy paste a SustemUI .apk. The first two steps went fine, but the third resulted in a persisitent, repetitive dialog box. I forget what this dialog box said, but it popped up almost as soon as I could press "OK", and I had to restore the backup of SystemUI to make it usable again. Oddly enough, about half of the new unlock animations still worked fine, and I wasn't seeing any problems after that, so I left everything else there. I liked the unlock animations, and they didn't seem to be causing any problems after I restored the original systemUi .apk.
Let's see, what else might be relevant? I was using the built-in task killer quite a bit. I'm also using SetCPU. I have 2 profiles: Screen on, 1728 MHz max, 300 MHz min, governor ondemand. And Screen off, 1036 MHz max, 300 MHz min, governor interactive. And I have installed the Material Power Menu from this thread: http://forum.xda-developers.com/android/apps-games/app-materialpowermenu-reveal-animations-t3059169 .
I started to notice the battery FC last bight. So, I wiped the battery stats as outlined above. Noticed it again today, wiped stats again, and kept checking it. After about an hour, it was force closing again. That's when I started poking around and found the others.
I dunno if anything can be done about this, or if anyone might know what's wrong. And, like I said, Aside from these FC's I'm not experiencing any real problems. I'm a little worried that they may get worse, or turn into something more serious, but I can always restore a backup if that happens. But if there is some kind of fix for these issues, I would use it. Thanks in advance to anyone who takes the time to read this wall of text, and tale of irresponsible phonery.
These are all settings that monitor usage.... should that tell me anything? I have tried wiping cache and dalvik, but that only seems to fix battery usage and data usage very temporarily(like, for a minute or less). And it doesn't seem to have effect on Process Stats.
My thoughts:
Seeing as you have flashed a lot of mods, it could be anything. If it were me, I'd start the rom from scratch. Then for the first step, instead of removing apps, I'd freeze them with titanium backup and give that a day or two to check the stability.
If that works, I'd continue with the mods one by one, giving a day or so for stability checks.
If you'd rather not do all that, you could use a logcat to find the origin of the problems.
Sent from my SM-N900P using XDA Free mobile app
jlechner said:
My thoughts:
Seeing as you have flashed a lot of mods, it could be anything. If it were me, I'd start the rom from scratch. Then for the first step, instead of removing apps, I'd freeze them with titanium backup and give that a day or two to check the stability.
If that works, I'd continue with the mods one by one, giving a day or so for stability checks.
If you'd rather not do all that, you could use a logcat to find the origin of the problems.
Sent from my SM-N900P using XDA Free mobile app
Click to expand...
Click to collapse
I'd probably try the logcat first. One, because I hate doing stuff over, and two, Ive neber done it before and it should be a learning experience. Is it complicated? I'm assuming there is a thread here on xda about it...
GAPO said:
I'd probably try the logcat first. One, because I hate doing stuff over, and two, Ive neber done it before and it should be a learning experience. Is it complicated? I'm assuming there is a thread here on xda about it...
Click to expand...
Click to collapse
It's fairly straight forward. I did one to see why an app wasn't loading, didn't need instructions. But that was a fairly simple check, yours sounds more complicated. I'd do a bit of reading on it.
Sent from my SM-N900P using XDA Free mobile app
jlechner said:
It's fairly straight forward. I did one to see why an app wasn't loading, didn't need instructions. But that was a fairly simple check, yours sounds more complicated. I'd do a bit of reading on it.
Sent from my SM-N900P using XDA Free mobile app
Click to expand...
Click to collapse
Will do. Thanks for your help!
Okay well I decided to re flash OC5 and start from scratch.
I took it back to stock and re rooted. Am now debloating....no isssues yet.
I have flashed everything except the Polish camera mod and the wallpapers. Having zero issues of any kind. I know it can take difficulties some time to manifest themselves, but I'm betting it is either the lock screen animations or the camera mod. Leaning towards the lock screen animations because it involves messing with system.ui...
Okay, made a new backup and flashed the camera mod. No issues. After every mod, I have been going back and checking for issues. This is all stil pretty new, but if everything is still fine after a couple of days, well, I will be convinced that it was the lock rings. Not surprising obviously that flashing stuff meant for foreign variants can wreck your sh*t, lol.
How's it going, everyone? I just want to apologize ahead of time if this is in the incorrect forum. There's so many to choose from and I didn't see one dedicated to this particular tablet.
I recently acquired a Verizon Ellipsis 8 and the first thing I wanted to do with the device was root it. After trying what must have been 10-15 different methods, I was finally successful at getting the device rooted using a (What I assume to be) Chinese root method called Kingroot. They had support for the tablet and actually got me root access, so I went with it. Shortly after, I installed all my necessary root apks and got the device working in what I would describe as acceptable order. I then began hunting for custom ROMS for the thing, but if there was one thing harder to find for this tablet than root access, it was a custom ROM.
Anyways, I've been living quite happily on rooted stock. I removed all the unnecessary bloatware from the device and everything has been going smoothly, until a few days ago. Verizon pushed out an OTA update and now I am receiving daily prompts from Verizon to update to the latest firmware. Now, this isn't my first rodeo when it comes to dealing with OTA updates, so I began digging around inside my system files to find the update.zip and disable it, as well as remove the different processes that would possibly be spamming this update notification. After several different files given the .bak extension and several different reboots, I felt comfortable that I had taken care of the issue. Hell, I even went so far as to take the same steps on my wife's tablet (She has the same one, rooted in the same fashion), and HER tablet has stopped sending her updates. HOWEVER, even though I have taken all the necessary steps, I still get the same prompt on my tablet at least once a day.
Now, I know for a fact the update files have been disabled, because last night I decided to test the update to see if it would actually go through, but it always results in the same error and the update doesn't apply. But no matter what, the prompt still shows up for me the next morning.
The prompt itself is quite annoying. It takes up the entirety of the screen, disables all other functionality of the tablet and doesn't let me choose other processes, and makes me select one of two options: Either I choose to apply the update, which immediately fails, or I can choose to delay the update to a different time during the day. If I could grab a screenshot, I'd show you guys what it looks like. But, I literally can't do anything on my tablet until after I make that selection, which immediately closes the process. That means I can't freeze the process using TitaniumBackup or something like that. I am helpless to suffer these update prompts every morning.
Now don't get me wrong. I'm not ever going to actually run the update, but the reminder is just such an inconvenience. So, I thought I'd make a post and see if there's anything you guys can think of that might be able to help me find whatever is causing these prompts and get rid of it. I've disabled the update.zip, I've disabled notifications from the Google Play Services, and I've rid myself of all the unnecessary bloatware on my device. I left a few Verizon processes on the tablet that I wasn't 100% sure if they were safe to remove or not, and I've even installed the FOTAKill.apk to see if that would help. The update doesn't work, but the prompt still shows up every morning.
I'd be forever in your guys' debt if you could help me on this one. Thanks for the read, and thanks ahead of time for any help! =D
metalslug53 said:
How's it going, everyone? I just want to apologize ahead of time if this is in the incorrect forum. There's so many to choose from and I didn't see one dedicated to this particular tablet.
I recently acquired a Verizon Ellipsis 8 and the first thing I wanted to do with the device was root it. After trying what must have been 10-15 different methods, I was finally successful at getting the device rooted using a (What I assume to be) Chinese root method called Kingroot. They had support for the tablet and actually got me root access, so I went with it. Shortly after, I installed all my necessary root apks and got the device working in what I would describe as acceptable order. I then began hunting for custom ROMS for the thing, but if there was one thing harder to find for this tablet than root access, it was a custom ROM.
Anyways, I've been living quite happily on rooted stock. I removed all the unnecessary bloatware from the device and everything has been going smoothly, until a few days ago. Verizon pushed out an OTA update and now I am receiving daily prompts from Verizon to update to the latest firmware. Now, this isn't my first rodeo when it comes to dealing with OTA updates, so I began digging around inside my system files to find the update.zip and disable it, as well as remove the different processes that would possibly be spamming this update notification. After several different files given the .bak extension and several different reboots, I felt comfortable that I had taken care of the issue. Hell, I even went so far as to take the same steps on my wife's tablet (She has the same one, rooted in the same fashion), and HER tablet has stopped sending her updates. HOWEVER, even though I have taken all the necessary steps, I still get the same prompt on my tablet at least once a day.
Now, I know for a fact the update files have been disabled, because last night I decided to test the update to see if it would actually go through, but it always results in the same error and the update doesn't apply. But no matter what, the prompt still shows up for me the next morning.
The prompt itself is quite annoying. It takes up the entirety of the screen, disables all other functionality of the tablet and doesn't let me choose other processes, and makes me select one of two options: Either I choose to apply the update, which immediately fails, or I can choose to delay the update to a different time during the day. If I could grab a screenshot, I'd show you guys what it looks like. But, I literally can't do anything on my tablet until after I make that selection, which immediately closes the process. That means I can't freeze the process using TitaniumBackup or something like that. I am helpless to suffer these update prompts every morning.
Now don't get me wrong. I'm not ever going to actually run the update, but the reminder is just such an inconvenience. So, I thought I'd make a post and see if there's anything you guys can think of that might be able to help me find whatever is causing these prompts and get rid of it. I've disabled the update.zip, I've disabled notifications from the Google Play Services, and I've rid myself of all the unnecessary bloatware on my device. I left a few Verizon processes on the tablet that I wasn't 100% sure if they were safe to remove or not, and I've even installed the FOTAKill.apk to see if that would help. The update doesn't work, but the prompt still shows up every morning.
I'd be forever in your guys' debt if you could help me on this one. Thanks for the read, and thanks ahead of time for any help! =D
Click to expand...
Click to collapse
You will need to modify your build.conf to prevent the update screen from prompting you.
Change the build number to something else....
/system/build.prop
Change the build to something like: ro.build.display.id=AKOT49HA
and do the same to the rest of them in the file.
Note: this is another issue reporting thread. In case of duplicate or forum location problem, consider (re)moving my post.
Hello,
Months ago I noticed a weird issue in the internal browsing system of the SM-G361F
When I browse to a website using the WebGL integrated API (for exemple: https://get.webgl.org/ ) the displayed shape gets glitchy. Nothing really strange first, just some random blink or short frame flashbacks. But after a time (generally above 30 seconds) the shape become more and more glitchy until the kiss of death: the whole phone process freezes, as nothing respond anymore, then the screen gets shady on some parts and bright on the other, until a kind of bar come across the screen and the phone make a complete reboot without any transition.
I already experienced such thing a year ago, but that was due to a bad root flash that triggered the freeze on any root access request.
The other strange thing is that I discovered it when I ran a web code displaying an "holographic" shape: however, the code worked fine the first times, and I did it long ago; so would this be due to a bad firmware flash or a system harm?
If you own like me a SM-G361F device and are not easily scared (this issue normally doesn't harm the device, it will just freeze and reboot) you can test it by opening the link to the WebGL official website.
Sharing experience about this potential issue would be appreciated.
I also had this issue. I experienced severe jitter in videos, and gifs in the web browser. It seemed to occur randomly, and would sometimes stop after a little while.
I didn't experience the device crashes though, but fixed the video by downgrading "android webview"
Sorry for late reply.
Atronid said:
Note: this is another issue reporting thread. In case of duplicate or forum location problem, consider (re)moving my post.
Hello,
Months ago I noticed a weird issue in the internal browsing system of the SM-G361F
When I browse to a website using the WebGL integrated API (for exemple: https://get.webgl.org/ ) the displayed shape gets glitchy. Nothing really strange first, just some random blink or short frame flashbacks. But after a time (generally above 30 seconds) the shape become more and more glitchy until the kiss of death: the whole phone process freezes, as nothing respond anymore, then the screen gets shady on some parts and bright on the other, until a kind of bar come across the screen and the phone make a complete reboot without any transition.
I already experienced such thing a year ago, but that was due to a bad root flash that triggered the freeze on any root access request.
The other strange thing is that I discovered it when I ran a web code displaying an "holographic" shape: however, the code worked fine the first times, and I did it long ago; so would this be due to a bad firmware flash or a system harm?
If you own like me a SM-G361F device and are not easily scared (this issue normally doesn't harm the device, it will just freeze and reboot) you can test it by opening the link to the WebGL official website.
Sharing experience about this potential issue would be appreciated.
Click to expand...
Click to collapse
Hello mate!
I must tell you that this happens not only on your device but on SM-G360H Varient too.
In the last 2-3 days i figured it also happens due to high CPU usage and the Kernel goes into panic mode.
Try disabling Kernel panic from apps like LSpeed and see if it helps!
Thanks!
SnapDrag910 said:
Hello mate!
I must tell you that this happens not only on your device but on SM-G360H Varient too.
In the last 2-3 days i figured it also happens due to high CPU usage and the Kernel goes into panic mode.
Try disabling Kernel panic from apps like LSpeed and see if it helps!
Thanks!
Click to expand...
Click to collapse
Thanks for your advise ^^
Atronid said:
Thanks for your advise ^^
Click to expand...
Click to collapse
1 more.
If you are on a custom ROM, then remove the AOSP webview for root -> system -> apps -> Webview. And then install Google webview from the playstore and convert to system app(optional).
It may fix the random crashes and freezes. It does freeze but no more crashes
Hello,
Even though I found a lot of similiar problems and possible solutions for them,
none seemed to be suitable for my case.
My Phone:
Motorola Moto G2 with Android(either 4.4.4 or 6.0 sorry i dont know)
with SD-Card as internal storage
no root and with the stock bootloader locked
I will begin to describe my problem:
After accidentally tapping on a android app (the android head as icon - probably the setup wizard -) on my normally functioning phone, I got thrown into the setup sequence of the android setup-wizard, which is
unfortunately bugged and keeps crashing and restarting(-setup wizard has stopped-) no matter what. Any other action like using the home button(which disappeared) or access the dropdown menu is not possible and restarting or rebooting the phone wont solve the problem. The phone always starts in this setup-wizard.
So there are multiple Solutions to be found, but each of them either requires to have a rooted device or unlocked Bootloader or if not, factory reset the phone in order to install the above mentioned.
The thing is that I kinda gave up in getting my phone to work again since the only thing I seriously dont want to lose is the data, which im not able to extract anymore because I cant setup a ADB without access to settings or unlocked bootloader. And I am a big big dummy because I never did any backup on this device.
What really bugs me is that the phone still seems to function just fine(for example it still makes noises when I (probably) receive a message ) but its impossible to leave that damn setup-wizard.
I apologize for any dumb stuff or typos I just wrote, which are probably the result of a lot of exhaustion and despair.
I hope anyone can suggest a way to get to my data or even solve the problem.
Thanks in advance!
Romizzle said:
Hello, Even though I found a lot of similiar problems and possible solutions for them........
Click to expand...
Click to collapse
I don't have this device but, the following area of the forum is specific to your device.
https://forum.xda-developers.com/moto-g-2014
With that guidance...
You should be able to obtain some member guidance within the following Q&A thread that's specific to your device as well.
https://forum.xda-developers.com/showthread.php?t=2875723
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.
OK, fixed it thank god
I will write down my solution in case that anyone faces the same problem and isnt
able to use advanced root/bootloader methods.
My Hero was a little "glitch" in the wizard, where you could partially leave it by
establishing a new network and write done something random to mark it and then
press share. afterwards you can try different applications which are shown to somehow reach the settings which is your golden goal. Gmail worked for me but it was really a back and forth till I somehow ended up in the playstore and then opened the settings application(if its not in the playstore try to open a launcher like Nova launcher or Google Now). If you managed to reach that point its nearly done.
just find the setup-wizard in your applications (systemapps) and give it ALL the rights it needs(should be phone and contacts). I have stopped him additionally but I dont think that added up anything. After that is done just hold the power button till its off and after the restart the setup wizard should be able to detect ur google account and finish his job.
Thank god there are glitches out there.
But as far as I found out alot of glitches get patched sooner or later so...yea:silly: