Related
Hi everyone. It's been two days since the process com.google.process.gapps has started crashing, "stopping unexpectedly" whenever i use the browser on my tab.
Reading the error report, it seems (not 100% sure about that) this is somehow related to the bookmarks sync with Chrome, but i can't find a way to disable this.
Has anyone exprerienced the same issue? Any known solution? Thanks
Go to settings > accounts and sync, click on your account then uncheck everything, then manually sync everything one by one to see what is causing the error.
Then go to manage apps and clear the cache of all the problem apps and re-sync them once you're done. It might take a few tries but it should take care of that error.
I'll try that as soon as possible, thanks!
browser sync was causing this for me
I believe that bookmarks sync no long works with galaxy tab. Google changed something on their end that should have worked fine(it still works on the xoom, transformer, etc.) but since samsung changed a bunch of stuff for no apparent reason, it is now broken. samsung is so stupid sometimes..
So you're basically suggesting that bookmarks sync should stay off to avoid problems like that?
well I don't really know. I never used bookmark sync in the first place. I'm just going by what is said in this article.
http://www.zdnet.com/blog/perlow/br...gle-or-the-oems/17840?tag=mantle_skin;content
It turns out that at some point Google started making some changes to the backend systems that handle Google’s user account data. There’s nothing wrong with them doing this; it happens all the time. In fact, no other Android 3.1 tablets had any issues at all with the changes, and their bookmark sync continued to work without a blip on the radar.
Not Samsung, however... I did some digging around the internet, and it’s become somewhat well-known amongst Android developers that Samsung actually modifies core source code in the Android operating system that handles communicating with Google’s backend data services.
Click to expand...
Click to collapse
Well, that's a pity. I had just started to think it was a useful tool to keep track of unread web pages between work, home and outside...
Let's hope Samsung somehow fixes that.
PS: disabling bookmarks sync actually stops the process from crashing, I think I've solved (if we could really say so...) the issue. Thanks to all!
Thanks, disabling auto sync for browser has stopped the error. Samsung developers need to fix this - I can't auto sync my gmail
What am I missing here?
Ok be prepared, this post may be rather long winded however I will try my best to prevent that. I have a Tmobile G2x I purchased on launch date. Ive not attempted to Root, change roms, or anything of the sort. (as much as I always wanted to, I always felt that my skills were not good enough to attempt these ideas no matter how easy they may seem. I just did not want to be the cause of screwing up my phone that I paid dearly for)
So I have a friend who claims to be the master (of disaster so it turns out) of rooting androids and such. He stops by my house just to hang out and eventualy convinces me to let him root my phone and install CM7. Within a few minutes the phone was rooted (super1click) and was running CM7 release candidate. (I really dont know what all these things truly are but I drilled him for answers once he jacked up my phone and left me with a half-bricked phone) So he installed Rom manager and convinced me to upgrade to the premium version via marketplace so I did. He was then showing me how easy it was to flash new roms at the touch of a few buttons. He put on some other rom which looked like CM7 but claimed to have extra tweaks. It worked fine. A few minutes later he put on some Faux Rom which gave a boot up screen like my old Nexus One did. (Multicolored X) It seemed to work fine as well. Then he said lets check out the nightly CM7 Rom so he put it on. (however I dont think it ever actually put CM7 back on.-still on Faux?) Thats when things got crazy.
Now I get the com.google.process.gapps force close message all the time. He tried to fix it for 4 hours and finally gave up. Here is what I know he/we tried: After searching the internet for hours we tried everyone elses ideas. Clearing calenders cashes, un syncing, etc. We did about 40 factory resets. We have tried to install my backup (which was from BEFORE he even touched my phone) and upon holding both volume rockers and plugging in USB (no battery installed) and it still does nothing. Windows recognizes device but phone screen stays black. Tried Debug mode while doing this as well. If we hold the volume down button and power the little install bar comes on the screen and it does its thing (whatever that is) and goes right back to the way it was. I keep getting the gapps message all the time. After factory reset I cant even type in my gmail address to start the initial setup of the phone. The force close keeps cutting me off. If I type fast, I can sync the account but I cant use market whatsoever. Tried installing Rom manager to re-flash but just sticks at starting download and gapps pops up again.
My son is starting school tomorrow and he has a medical condition. I NEED this phone to communicate with the school nurse via emails and such. As of now I can only text, call, or surf web all while dodging force closes. If ANYONE out there can please help me get my phone back to normal Id greatly appreciate it. Im sure its something easy but as I said before, Im not good at this thing and thats why I never attempted it myself. Your welcome to submit answers here or PM me your phone # if you want to walk me through it on the phone. (I have a landline phone to talk to you on) Thanks in advance for everyones time and Im sorry this ended up being so long.
Hello,
Based on your post, I would suggest that you search your phone's development forum on XDA for a compatable clockwork recovery mod which will install a custom recovery on your phone. The thread will give you instructions on how to do so and how to enter recovery mode.
You can then enter the 'Backup and Restore' part of the recovery and restore your backup manually without using ROM manager. If this doesn't work, I would suggest that you then download the ROM of your choice and install it from the clockwork recovery. Make sure you clear user data and wipe the cache before you install.
Any fix yet? This is really annoying me as I rely on my bookmarks tremendously.
try this:
Open stock browser and under settings choose clear cache and deletehistory
This fixed both my Camera and Google Talk that stopped working in Sense ROMS om 08-31-11.
FIX:
1. Go to Settings and select Date & Time.
2. Un check Automatic
3. Change the time to 08-01-11
4. Go and open your camera (it should work now)
5. Now you can go back and check Automatic in the Time & Date Setting
yes,I see log:
Code:
I/CameraService( 3944): CameraService started (pid=3944)
I/OlaEngine( 3944): [Ola_Engine_Create:75] engine build info [ name ] : htc
I/OlaEngine( 3944): [Ola_Engine_Create:79] engine build info [ date ] : 2011-05-13 18:34:22
I/OlaEngine( 3944): [Ola_Engine_Create:83] engine build info [ version ] : __bulid_revision_171__
E/OlaEngine( 3944): [Ola_Engine_Create:91] This library will be expired at 2011/8/31.
D/OLAWORK ( 3944): create OlaEngine failed -32
Have time to lock this file:/system/lib/libcameraservice.so
However, I found that you can use incredible_s (s710d) file to replace.
I put a file in here, from RUU_Vivo_W_CT_Gingerbread_S_HTCCN_CHS_CT_2.13.1401.4_Radio_1_01_50_0701_NV_MFG_CT_2.22_release_202988_signed extraction.
This file is not the time lock. 2.07.605.0 ~ 2.11.605.0 stock rom application.
View attachment libcameraservice.zip
I TAKE NO CREDIT FOR THIS. Thanks to the help of mpwt51 on the Android Central Forums and Snow02 on the BAMF Forums, this issues is now resolved.
Looks like Verizon put some sort of time bomb into these apps. Simply changing the date back wil resolve this issue. Of course that is no way to actually resolve it. Flash this http://db.tt/Bcltlcr instead and it should solve these two issues.
Source: BAMF via Android Central Forums
You guys are freaking geniuses. I have been looking for a solution for this for over 4 hours and found nothing. Figures, the minute I check XDA there is a solution, right there.
Kalandros said:
You guys are freaking geniuses. I have been looking for a solution for this for over 4 hours and found nothing. Figures, the minute I check XDA there is a solution, right there.
Click to expand...
Click to collapse
That wasn't the case last night when I originally posted the issue and 4 guys over at TheMikMik were flashing like mad men, including myself, to try to figure out what sickness was ailing our beloved devices! Glad there's a cure though.
not rooted
This can't be flashed if not rooted, correct? I'm on GB 2.11 not rooted
It worked on GB 2.11 1nd 2.10 not rooted, Thank you very much!
Mig1234 said:
This can't be flashed if not rooted, correct? I'm on GB 2.11 not rooted
Click to expand...
Click to collapse
I seriously doubt it.
I've tried this and can confirm it works like a charm.
8-1-11?
Hey guys,
I'm amazed that someone actually figured out that the date is causing this problem. Seems lame that there's this code in the system with expiration dates. WTH Verizon!
Thank you for this fix its a life saver
Sent from my ADR6400L using xda premium
Does this fix the front camera issue on google talk on gingerbread?
wj_johnson said:
Does this fix the front camera issue on google talk on gingerbread?
Click to expand...
Click to collapse
No idea what you're talking about.
Google talk video on gingerbread (thunderbolt) will not use the front facing camera
wj_johnson said:
Google talk video on gingerbread (thunderbolt) will not use the front facing camera
Click to expand...
Click to collapse
That's always worked fine for me. You're ROM is the issue.
UndergroundWire said:
I TAKE NO CREDIT FOR THIS. Thanks to the help of mpwt51 on the Android Central Forums and Snow02 on the BAMF Forums, this issues is now resolved.
Looks like Verizon put some sort of time bomb into these apps. Simply changing the date back wil resolve this issue. Of course that is no way to actually resolve it. Flash this (nooblinkremoved) instead and it should solve these two issues.....
Click to expand...
Click to collapse
I'm not really sure why, but this only fixes my google talk, but not my camera. I've tried several of the camera fix .zip files and the most common result, across multiple ROMs is that google talk gets fixed, but the camera stays black, acting like it's working, but there are no buttons and the screen is black.
I first tried this on BAMF Forever 1.10 and acheived that result. Then, I tried it on Liquid Vigorsense v1.1 (can't find v1.2 on Rom Manager and the rootzWiki link doesn't work b/c it was on multiupload) and had the same problem. Eventually, I flashed each ROM again, wiping data, cache, dalvik and batter stats multiple times and when I wen't back in to BAMF Forever, it worked. B/C I liked sense 3.5, I wanted to go back to Liquid VS, so I tried flashing back to it and sure enough, both gtalk and the camera worked.
At that point, the only thing I wanted on a sense 3.5 ROM to make my life complete was the keyboard with arrows, so I tried a few keyboard w/arrows zips and none of them worked, so I tried flashing one of the Infected ROMS (Airborne). I found a keyboard w/arrows zip within their lists, so I flashed it and got the keyboard to work, but then the camera was gone. I found a camera fix that they had and it didn't work initially, but after a few re-flashes, everything worked.
Then I got greedy and wanted my sense world clock/widget, so before flashing back to one of my backups from liquid vs, I backed up the Infected ROM and when it booted back up, gtalk and camera were broken again. I tried flashing all of my backups from liquid and bamf forever that had a working camera and the camera/gtalk were broken on them as well.
So, I've flashed Bamf SOAB and I used the keyboard zip for bamf SOAB (worked!) and the camera fix mentioned in this thread and no dice. gtalk works, but still, just a black screen camera. I've wiped and flashed and wiped and flashed each, liquid and SOAB couple of times each (each time, wiping multiple times).
I've got a hilarious 1 year old girl and really want to get back to documenting her life in the candid fashion she so often provides, but I need my camera to be fixed.
I haven't seen many posts on this topic across most of the forums/sites after Septemer, 2011, so it makes me feel like everyone else got this to work. I didn't have the problem in September. It never hit me until I had to swap out my TBolt due to the right side of my screen crapping out. When the new one came from VZW, the camera/gtalk problem happened.
Any help or ideas? (sorry for writing a book)
Much thanks in advance.
I can't post in the developer forums yet since i think this is the first time i've posted. Anyways im wondering if any one else is seeing these issues once installing the BeastMOD alpha V0.4 ROM. Caller ID does not seem to be working for me, when the phone rings it does not show who is calling the only way i can find out who called is to check the missed phone call area afterwards. Second issue is i keep receiving the - android.process.acore has stopped unexpectedly - this keeps happening on the facebook app and not sure if it does it on anything else since that's all i tested. I reinstalled the ROM a second time making sure to do a wipe of data, cache, and dalvik beforehand but still ran into the issues again.
Just curious if anyone else has ran into these issues or if it's only me. Besides those two issue the ROM was running great and i love the AOSP look so much better.
i will look into those man
Thanks Xboarder I wasn't sure if you would see my post. Keep up the great work that you're doing it's appreciated.
So I have a Droid X2, now un-rooted and back on stock 2.3.4 and this is an issue I have had since I had the phone and have never found a fix. I have asked this multiple times on the Verizon forum for the DX and never get an answer...
SO every day I seem to have issues with my notifications going mute, sometimes, but not always, my ringer even goes mute. Usually once a day I have to reboot my phone because it is the only way I can fix it. I thought at first it had to do with my blutooth, but since SBFing and going back to stock I have not re-added my blutooth and it still happens. I took it into the store and he suggested that it is an app causing a conflict and I should uninstall 10 or so apps at a time to try and narrow it down... but I just went ahead and did a factory restore to see if it would help... but it happened again today...
Now, the notifications I use are ones I put on the phone. I have tried putting them on the SD and the internal and it seems to happen with both. I have also put them directly on and also tried ringdroid but it still does the same thing. The sound and notification levels will be all the way up, and when you go into the settings and try to pick a notification sound or ringtone, even the stock ones, you wont hear anything (and you would usually hear a preview of the sound)... The only way I can get the sounds to work is to reboot the phone and when it comes back, it will be fine... for a while. Sometimes have to reboot multiple times a day, but almost always at least once a day to get them back up...
Since you all seem smarter than the Verizon folks and have been a huge help to me thus far, I thought I would ask here and see if anyone else has ran into this and has a fix or if there are any known apps that would cause this. I have done searches but found nothing...
Is your music player ok?
Sent from my MB870 using XDA App
king..kranium said:
Is your music player ok?
Sent from my MB870 using XDA App
Click to expand...
Click to collapse
You know, I have never thought to check. I will next time it happens. I rebooted the last one earlier and its been fine, but I am positive it'll happen again here later...
king..kranium said:
Is your music player ok?
Sent from my MB870 using XDA App
Click to expand...
Click to collapse
Okay... happening again. Nope. Music won't play. Says something about not being able to play that type of file. Just regular music that plays any other time. If I reboot the phone I'm sure it'll work. Any ideas?
I have the same issue of notification sounds going mute randomly. I'm using galaxy tab P1000, android 2.3.3
sometimes music player stops playing songs randomly too!
DroidTalk said:
I have the same issue of notification sounds going mute randomly. I'm using galaxy tab P1000, android 2.3.3
sometimes music player stops playing songs randomly too!
Click to expand...
Click to collapse
I hate to say it, but finally good to hear someone else is having the same issue. Ive not found anything on it and cant seem to get helpfrom anywhere to fix it! Hopefully one of the smart people here will be able to help!
Happened to me again. This time right after i updated google plus app.i had to restart to get it back.
kalojado said:
Okay... happening again. Nope. Music won't play. Says something about not being able to play that type of file. Just regular music that plays any other time. If I reboot the phone I'm sure it'll work. Any ideas?
Click to expand...
Click to collapse
What rom are you on?
Sent from my MB870 using XDA App
DroidTalk said:
Happened to me again. This time right after i updated google plus app.i had to restart to get it back.
Click to expand...
Click to collapse
Hrmmm, I don't have g+ installed, so I know that isn't it for me... but same thing, I reboot and it comes back...
king..kranium said:
What rom are you on?
Click to expand...
Click to collapse
No rom. I was rooted but un-rooted and went back to stock gingerbread...
I upgraded to android 2.3.6 overcome 4.1.0 (its a custum rom for galaxy tab). Lets see if it resolves the issue. I'll report back if the problem happened again.
DroidTalk said:
I upgraded to android 2.3.6 overcome 4.1.0 (its a custum rom for galaxy tab). Lets see if it resolves the issue. I'll report back if the problem happened again.
Click to expand...
Click to collapse
Awesome... thank you!
I've had a similar issue but not exactly the same. I normally keep my phone on silent mode but sometimes during the day it will automatically go off silent mode. Seems to happen most often when the battery level is below half. I just learned to live with it. My alarm would deactivate by itself in Froyo, so at least this isn't going to cause me to be late for work like that.
Problem is solved here after last week's upgrade. I'd suggest flashing a new build if possible. I guess for some unknow reason, parts of the OS gets corrupted or maybe its a bug in device drivers for our android phones thats been addressed in later builds.
kalojado said:
So I have a Droid X2, now un-rooted and back on stock 2.3.4 and this is an issue I have had since I had the phone and have never found a fix. I have asked this multiple times on the Verizon forum for the DX and never get an answer...
SO every day I seem to have issues with my notifications going mute, sometimes, but not always, my ringer even goes mute. Usually once a day I have to reboot my phone because it is the only way I can fix it. I thought at first it had to do with my blutooth, but since SBFing and going back to stock I have not re-added my blutooth and it still happens. I took it into the store and he suggested that it is an app causing a conflict and I should uninstall 10 or so apps at a time to try and narrow it down... but I just went ahead and did a factory restore to see if it would help... but it happened again today...
Now, the notifications I use are ones I put on the phone. I have tried putting them on the SD and the internal and it seems to happen with both. I have also put them directly on and also tried ringdroid but it still does the same thing. The sound and notification levels will be all the way up, and when you go into the settings and try to pick a notification sound or ringtone, even the stock ones, you wont hear anything (and you would usually hear a preview of the sound)... The only way I can get the sounds to work is to reboot the phone and when it comes back, it will be fine... for a while. Sometimes have to reboot multiple times a day, but almost always at least once a day to get them back up...
Since you all seem smarter than the Verizon folks and have been a huge help to me thus far, I thought I would ask here and see if anyone else has ran into this and has a fix or if there are any known apps that would cause this. I have done searches but found nothing...
Click to expand...
Click to collapse
I'm certainly no dev, just an avid user who likes learning and tweaking to get the most from his phone. I recall having similar problems with FROYO stock or rooted which as I remember went away when GINGERBREAD came out. I've been running DZK's CM7 beta as my daily driver since it was released with virtually no problems and unlike most other ROM's does not need multiple tweaks and scripts to scream with the exception of a wifi and/or dialer glitch that looks like Moonshadow has recently fixed. Sooooo unless HDMI is a deal breaker I'd suggest you flash CM7 and see if that takes care of your problems just remember to abide by the cautions regarding use of TBU to restore apps. And lastly as a rule of thumb I reboot my phone every morning once I get to 100% charge...force of habit I guess.
Good luck
Sent from my MB870 using Tapatalk
Thanks everyone... I havent been on because it strangely hasn't been happening. Not sure what changed. Did not uninstall any apps, and have not had any updates (as far as I know... well besides app updates) and for some reason it hasnt been happening lately. Again, no idea what changed. Still unrooted on stock 2.3.4 gingerbread and phone seems fine now. Been happening for months and when I finally come here to get help, the problem seemed to have went away. I will keep you all updated if this changes. Hopefully if it is happening to anyone else, it has also been fixed... Thanks again for all your help. Really appreciate you guys helping out this noob
what i did
i have an mb870 too with no service running google voice and groove ip . my issue with notifications
was with my kids hitting all the button selections she could. in the process my message notifications
got defaulted to the wrong messaging app. i was still getting messages but no tones or vibrations.
so i just went to all the messaging apps i have and made sure to select the right one for the default
hope this helps
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.