Hi there, first of all I would like to let you guys know a few things:
1. I'm running 5.1 stock since I can't unlock bootloader.
2. I already flashed factory image with no success.
3. I've noticed phone restarts whenever I use some Google Apps such as Play Store, Chrome, Maps, etc. and also at the time I try to open up a game doesn't matter which one is.
I was able to capture a logcat via ADB (see attachment). I've read that whenever logcat captures W/ and E/ those are for warnings and errors and I did noticed that I'm getting lots of E/ related to some WiFi stuff and audio as well; for W/ I got some package manager errors which can give me a clue it may be a SW issue but like I said I've flashed stock around 3 times and that keeps happening.
Any help would be greatly appreciated! Thanks in advance! :good:
Related
So I was working on developing an app for android when I noticed that my camera had stopped working. Like many, I rebooted to find that it was still broken. This is my record for future Droid 3 users who get the same error "Unable to initialize" when starting up their camera.
To note:
I was rooted
I had the OTA update installed
Camera was working with both cases above
The camera was found broken after:
1. I was connected to the computer with "USB Mass Storage" Enabled
2. I was uploading Kitchen Sink, a test app for appcelerator through titanium X
3. I was testing geolocation which worked
4. I was testing camera which then reported "Unable to initialize"
I then quit the kitchen sink app, started the stock camera, which reported "unable to initialize"
I had read a few pages of google searches by this point like the one following:
https://supportforums.motorola.com/message/468467
I've had this camera since the release so its not that easy to simply send it to wirefly which is where I got it.
So I tried wiping the data, still didn't work. Reinstalled the camera files directly from the OTA update file, didn't work.
So what seemed to work was what follows:
-Factory reset
I restarted
held the X key
wiped cache TWICE
did a factory reset TWICE
reboot
Still didn't work.
So I restarted
held the X key
installed the latest OTA update
reboot
And now it works.
I hope this helps someone like me out there. There really isn't much material on this issue.
yea
when my camcorder wasnt workin i replaced the build.prop cause i know i did a few things that messed with it.
Can someone else confirm this fix?
Droid 3 camera not working.
So ive been looking all day on this site for a successful fix for my problem and everything I have tried is not working. Im not sure how it happened I assume I did it when installing a rom. When I Try to open my camera or anything involving the camera hardware the screen stays black and will force close then upon a second time it just pops up with the "camera was unable to initialize" Im running the Droid 3 android version 2.3.4 sys version .xt862 and currently have on the dark droid rom. Im not that good at this and have been just winging it and following walkthroughs on the sites but I seemed to have missed a step or something along the way. Any help or advice would be awesome.
Hi guys,
My phone is experiencing random soft reboots (reboots without a need to type in simcard PIN) during the day. It happens totally randomly, sometimes 3 times a day, sometimes not once in a couple of days. Sometimes when I use it, sometimes when it's idle on the table.
I'm running stock JB 4.3 A.1.205, LB, Towel-rooted, no custom recovery (I tried some previously and they were givig me all sorts of trouble, so I downloaded fresh official ROM and Towel).
I've been trying to track down the process that causes reboots, I temporarily uninstalled Xposed framework but it still ocurred.
Is this a known issue? Is there a better way to check what is causing that (perhaps in some log file)?
Thanks in advance,
Regards,
Michal
niedzwiedz102 said:
Hi guys,
My phone is experiencing random soft reboots (reboots without a need to type in simcard PIN) during the day. It happens totally randomly, sometimes 3 times a day, sometimes not once in a couple of days. Sometimes when I use it, sometimes when it's idle on the table.
I'm running stock JB 4.3 A.1.205, LB, Towel-rooted, no custom recovery (I tried some previously and they were givig me all sorts of trouble, so I downloaded fresh official ROM and Towel).
I've been trying to track down the process that causes reboots, I temporarily uninstalled Xposed framework but it still ocurred.
Is this a known issue? Is there a better way to check what is causing that (perhaps in some log file)?
Thanks in advance,
Regards,
Michal
Click to expand...
Click to collapse
Try with hard reset or try to flash another stock ftf
Thanks, but the reset doens't seem to change much, it occurs anyway.
I'd rather avoid changing rom again, as I said I just recently installed clear stock offcial rom via PCC and only towel-rooted it.
Any ideas how I could try to track the fault process?
niedzwiedz102 said:
Thanks, but the reset doens't seem to change much, it occurs anyway.
I'd rather avoid changing rom again, as I said I just recently installed clear stock offcial rom via PCC and only towel-rooted it.
Any ideas how I could try to track the fault process?
Click to expand...
Click to collapse
I would have said it´s because of the xposed framework if you haven´t said you uninstalled it once. I had the same problem once, and I was kind of sure that it´s because of some gravitybox settings which gave trouble.
I recommend you to uninstall the xposed framwork once again, reboot and give it a try
Crash...X said:
I would have said it´s because of the xposed framework if you haven´t said you uninstalled it once. I had the same problem once, and I was kind of sure that it´s because of some gravitybox settings which gave trouble.
I recommend you to uninstall the xposed framwork once again, reboot and give it a try
Click to expand...
Click to collapse
Well, I'll give it a go, however I did it before and the reboots occurred anyway... I'm now slowly uninstalling all the apps one by one to see when this craziness stops
I'm starting to suspect that it's a fault of Google Play Services, they're always on high positions in my Wakelock and Battery Usage lists, I heard people are also having some other problem with this app.
Edit:
Another thing is that I try to modify something in AppOps (I'm accessing it via some shortcut apps from the Store), but I cannot change permanently any settings (I click back, then enter again some app and it's all 'allowed' again), is this normal?
I'm digging up an old thread, but I narrowed down my problem to Stamina Mode, I think.
I wiped all data via factory reset, reinstalled clean system via PCCompanion and only townel-rooted. The soft-resets began to appear again shortly after first boot. I tried to eliminate differet things and it seems that the reboots occur only when Stamina Mode is on. I've switched it off like a week ago and the phone has been running smooth ever since.
Now I'm just asking out of pure curiosity, has anyone ever stumbled upon similar problem? Is Stamina Mode known for causing any issues of this kind?
So I installed M today using fastboot, however when I run through my phone's setup, I get stuck on opting in to Google Now. When I hit next, I I get a Network Error: Check Your Network Connection message and am forced to skip it to continue with the setup. I've tried clearing the app cache and data for Now, I've tried a complete reinstall of M multiple times, and even tried downgrading to Lollipop (Chroma) and continue to see this message whenever I try to start Google Now. I've tried clearing all of my search and location and Now card history as was suggested elsewhere, but this did nothing. In addition, it seems that Now isn't working on my desktop Chrome either anymore. I can't seem to get it enabled while it's broken on mobile.
Has anybody else run into this problem since trying M? And does anyone have any suggestions? I use Google Now a lot and it's kind of driving me nuts.
try one of the twrp flashable zips for M, in the android development section.
Having the same problem, and seen a few others too, did you find a fix for it?
Wrong forum... my bad
So lately I'm getting this weird error wherein after the battery drops below 30% and if I try to call or if I receive a call, the phone restarts itself. And after restarting, it completes boot animation, loads "Starting Apps" screen and after that screen just goes blank(ie. Pressing any button is futile at this point of time). This keeps on repeating itself. The only workaround I have found to it is to connect a charger while restarting. After connecting charger the phone boots itself (instead of screen going blank) and works normally.
I'm currently on Cataclysm 6.0.1
Kernel : Elite Kernel
Multi ROM : Installed.
Xposed : Installed
I've tried various kernels and various ROMS combinations (except the stock ones) but the error keeps on repeating itself.
Any help appreciated.
x0nar said:
So lately I'm getting this weird error wherein after the battery drops below 30% and if I try to call or if I receive a call, the phone restarts itself. And after restarting, it completes boot animation, loads "Starting Apps" screen and after that screen just goes blank(ie. Pressing any button is futile at this point of time). This keeps on repeating itself. The only workaround I have found to it is to connect a charger while restarting. After connecting charger the phone boots itself (instead of screen going blank) and works normally.
I'm currently on Cataclysm 6.0.1
Kernel : Elite Kernel
Multi ROM : Installed.
Xposed : Installed
I've tried various kernels and various ROMS combinations (except the stock ones) but the error keeps on repeating itself.
Any help appreciated.
Click to expand...
Click to collapse
an error is when an error screen appears, you arent having an error. first thing first though, completely get xposed off your phone, completely, reflash if need be. i bet this will fix your issue. whenever weird issues appear, and xposed is installed, most likely its xposed.
simms22 said:
an error is when an error screen appears, you arent having an error. first thing first though, completely get xposed off your phone, completely, reflash if need be. i bet this will fix your issue. whenever weird issues appear, and xposed is installed, most likely its xposed.
Click to expand...
Click to collapse
Hi thanks for replying. I've followed your instructions, however the issue still persists.
So this is my current combination
Benzo ROM : 6.0.1
Kernel : Default
Multi ROM : Uninstalled
Xposed : Uninstalled.
The only change that is left to make is to change the recovery from Multi ROM to TWRP.
The most weird part of this problem is that as soon as I make a call or receive a call it restarts and enters into a black screen. However as soon as I connect charger it works normally. That is what bugs me the most. Also my bootloader and Radio are the updated ones. And I checked if there was a log in /sys/fs/pstore but there isn't any.
Please suggest.
x0nar said:
Hi thanks for replying. I've followed your instructions, however the issue still persists.
So this is my current combination
Benzo ROM : 6.0.1
Kernel : Default
Multi ROM : Uninstalled
Xposed : Uninstalled.
The only change that is left to make is to change the recovery from Multi ROM to TWRP.
The most weird part of this problem is that as soon as I make a call or receive a call it restarts and enters into a black screen. However as soon as I connect charger it works normally. That is what bugs me the most. Also my bootloader and Radio are the updated ones. And I checked if there was a log in /sys/fs/pstore but there isn't any.
Please suggest.
Click to expand...
Click to collapse
You're probably not going to like this suggestion, but here goes. In order to confirm or deny a potential hardware defect, you probably should go back to 100% stock. Fastboot flash the factory image for MMB29K. IMHO
Your issue is most likely multi. It has been known to cause random issues.
Your best bet is to make it do it again and grab a logcat or kmsg
zelendel said:
Your issue is most likely multi. It has been known to cause random issues.
Your best bet is to make it do it again and grab a logcat or kmsg
Click to expand...
Click to collapse
I'm willing to do that, but the problem is as soon as I connect it to the charger or USB on my laptop to take out log via ADB it acts normally. So, I believe the log will come out normal. Now the only option left here for me is to Factory Reset, and see how it goes.
To be honest, I never faced this issue while on 5.1.1. This just started out recently. Anyways, thank you.
cam30era said:
You're probably not going to like this suggestion, but here goes. In order to confirm or deny a potential hardware defect, you probably should go back to 100% stock. Fastboot flash the factory image for MMB29K. IMHO
Click to expand...
Click to collapse
Unfortunately that is what I believe I'll have to do.
x0nar said:
I'm willing to do that, but the problem is as soon as I connect it to the charger or USB on my laptop to take out log via ADB it acts normally. So, I believe the log will come out normal. Now the only option left here for me is to Factory Reset, and see how it goes.
To be honest, I never faced this issue while on 5.1.1. This just started out recently. Anyways, thank you.
Click to expand...
Click to collapse
There are apps out there that will do it without being connected to the pc. Try one of those. If it was me I would just drop multi rom all together. It has never been completely stable and most likely never will be.
zelendel said:
There are apps out there that will do it without being connected to the pc. Try one of those. If it was me I would just drop multi rom all together. It has never been completely stable and most likely never will be.
Click to expand...
Click to collapse
I've dropped Multi ROM completely. The issue sad-fully still persists. I have even deleted Kernel Control Apps and any apps that revolve around Root. I really am not aware of what I should be doing next other than formatting and just hoping nothing worse happens. Also could you name a few apps that could take out logcat even while booting. In a surprising twist of events, now as soon as I hit reboot on the phone, it enters into bootloop and does not return back to normalcy, until connected to a charger or PC via USB. So I guess, I could take a logcat. Thank You again.
Hi all,
I completed a root for my z3c following Strmy's guide from here:
https://forum.xda-developers.com/z3-compact/general/guide-newbshow-to-291-mm-z3clocked-t3536395
one change I had to make to that process was to not flash the ''superuser_238_291.zip'' because every time I did, the phone kept getting stuck in a boot loop.
The process was completed successfully, and the phone worked like a charm for a day.
This morning, I found it strangely incapacitated - missing were many of the new apps I installed, along w gmail, chrome, and google play. I can't access the settings on the phone, and when connected to a computer, I can't allow file transfer.
Does anybody have an idea what may be happening and how to approach this situation?
Many thanks!
Update: I have since flashed the D5803_Customized US_23.5.A.0.570 R5D w/o any change to functionality of the phone. It also appears that I have lost access to TWRP recovery. This is all really confusing. Any advice would help.