Database Develop

Bunch of errors after restarting phone. Please help.

So I turned off my phone and restarted it again and when I slide down the lock screen I get all these pop ups of;The process android.process____ has stopped unexpectedly. Please try again. I get that from like phone, Google Maps and all that. My phone doesn't even connect to the network. Anyway to make it work without having to delete all my stuff:/

have you modded your phone in anyway? Rooted, Custom Rom??? these are questions that need to be answered

w01fm4n said:
have you modded your phone in anyway? Rooted, Custom Rom??? these are questions that need to be answered
Click to expand...
Click to collapse
Oh sorry my bad. No I haven't done anything to my phone. No rooting whatsoever and all apps have been downloaded from the app market.

that is a interesting one. first open would be to hard boot it pull the battery for a minute or so and then try it. only other option i could think of off the top my of head is to do a RUU installation going back to bone stock... do not have the link handy but it's available around XDA somewhere.

w01fm4n said:
that is a interesting one. first open would be to hard boot it pull the battery for a minute or so and then try it. only other option i could think of off the top my of head is to do a RUU installation going back to bone stock... do not have the link handy but it's available around XDA somewhere.
Click to expand...
Click to collapse
Wouldn't hard boot delete all my stuff?
Edit-
Nevermind. After turning it off and on many times I finally heard my phone receive a text message so I knew it was working again. :]]] It's so weird that it just came back, I'm glad though. =]

Will rooting the Nexus one/Froyo cause problems?

Guys, I had someone here talk me through rooting my nexus one with froyo and I'm running into some problems but I didn't know if it had something to do with rooting it or not and the reason is, I got it rooted the same day I received it so I hadn't tried those functions before I got it rooted.
I got it rooted so I could buy this program that makes the fonts larger and it required a rooted phone.
Well, today I was going to try to use it as a hot spot or wifi router and when I tried to enable it, it just says error.
Also, when trying to call and talk to people today, they could barely hear me and I had a hard time hearing them (not sure if this was temporary or not because later, although in a different area, it sounded fine).
When trying to reply to some e mail (online email/godaddy) when I clicked where the text/body goes, I could not type anything 'cause the keyboard wouldn't come up. If I clicked in the email or subject areas, the keyboard came up but not in the body text area.
Any ideas?
I guess I could reset it to default settings to see what happens but it took almost two hours to get it rooted so I really would like to avoid that.
Thanks
George

This should be in Q&A!
Not dev related.
To solve your problem:
looks like a bad boot.img for me.
I always had "Activiating Wifi"... "Error" with bad boot.img.
MOD: move to Q&A

Thanks. I wasn't sure about where to put it and thought there was possibly bigger chance of a reply here. Thanks for moving it.
So, considering I have NO idea what I'm doing and someone else helped me, is the answer to my next question short and simple or not?
What do I do about it?
No, I have no idea what a boot image is.
Should I try to get hold of the guy who helped me root it or see if someone else can talk me though how to fix it?
Thanks
George

guiri_too said:
Thanks. I wasn't sure about where to put it and thought there was possibly bigger chance of a reply here. Thanks for moving it.
So, considering I have NO idea what I'm doing and someone else helped me, is the answer to my next question short and simple or not?
What do I do about it?
No, I have no idea what a boot image is.
Should I try to get hold of the guy who helped me root it or see if someone else can talk me though how to fix it?
Thanks
George
Click to expand...
Click to collapse
Im not a Mod, I did not move your thread.
The boot.img is part of a ROM.
But I don't know what ROM you're using, what build (FRF50/72/85B/91) nor the kernel etc.
I cannot tell you more right now.
Just try a new rooter update.zip because yours might have broke your WiFi.
See Cyanogen's or re-flash a pre-rooted rom.

Actually, I noticed it wasn't moved yet but anyway, I think I have the 72 but still, not sure, I'll have to investigate 'cause I like this phone and I would LIKE it to work for me. Especially since I can apparently use it on tmobile and att.
THanks
The hunt continues
George

no rooting in general does not harm your phone or cause problems in any way. however it is possible to mess something up, maybe install something or screw up settings or similar that could cause problems. you can always flash back to factory ROM, or hard reset, to get your phone working again.
even better, since you are rooted, you should be creating nand backups. and anytime something goes wrong, you restore to a working nand backup to a state that you know your phone was working good.

Yeah, now I have to figure out how to do this but thanks for the replies
George

[Q] LCD BLACK BUT STILL FUNCTIONAL BLIND, MAJOR KEYS still lit up

First of all running stock Droid 3 Rooted Flashed to cricket
with all the fixin's, Bootstrap, CMW, ... etc....
:edit ... Now with safestrap.
_________________________________________
I noticed after taking my phone out of my pocket while trying to turn it on from normal off screen while on that it wouldn't show up the light still indicated it was working I can even turn off the phone.
Taking the battery out and back in semi fixed this but only to the extent where when the phone is turned on the moto logo doesn't appear but the droid eye does.
whence at the booted screen if I were to let it go black it has a chance to not stay on unless I RIGHT after it boots unlock it and keep it lit,
(but)
the main problem I noticed was it really only did this after lets say I was typing or doing anything with the qwerty board open and perhaps I let the screen turn off after a minute,
when I try to wake it up it stays black. EVERY TIME like most of the time,
it has to do with the keyboard being open when the screen goes to sleep.
WHAT IS WRONG *pulls hair out*
_________________________________
I can't say when but I've looked everywhere
tried uninstalling every app but the essentials,
then restoring to my first restore which was after my first initial root.
Tried factory reset,
Tried flashing back to stock,
yeah I think this counts for as much as I've gone insane looking for an answer for.
I have been told this sounded like a software issue so all I'd need to do is re install like I did when flashing back to stock THIS MORNING.
____________________________________________________
I need help to identify somehow if this IS or IS NOT a software/hardware problem.
and an answer to help me fix this would be nice as well thank you.
I know I am supposed to be brief but putting in all that into google and into every forum I have delved just isn't going to put it the way it needs to be said.
______________________________________________________
______________________________________________________
Edit:
Ok so far since no one has said anything I have also reinstalled my old newest state, still giving me crap.
Then just did the newest update 5.7 blah and still it's happening.
I hypothesize it might be the flex ribbon cable maybe (but it really might not) I read from another phone it might be a capacitor but it might not.
Whatever is wrong the phone still is able to at times now 40/60% of the time work properly and wake normal but then again not.
__________________________________________
Right as of now I have put isc to see if this helps .......... .... to be continued or helped.
I'm back, well ics installed fine after the second time made it boot loop over and over.
-----------------------------------------------------------------------
I can receive calls now
but
no sms, mms, or internet.
(even though the network status settings are blank it's weird I can still receive calls, and send calls.)
since you can't restore the apn's with 3rd party I now have this NEW issue.
the phone goes unresponsive within cdma workshop and ##Program does not work.
I'd like some help in finding out now how to if it is possible yet to properly flash to cricket and or just change my apns and get into cdma as well as QPST.
__________________________________________
PLEASE I NEED HELP thank you
-3nJo1

Yeah, it does sound like a hardware problem. If nobody else can help you fix it, you'll need to reflash the latest OTA update (or revert to your safestrap nandroid), unroot it and restore all the system apps that you may have frozen/deleted, and hope that Verizon will replace it.

Thanks
necromanteion said:
Yeah, it does sound like a hardware problem. If nobody else can help you fix it, you'll need to reflash the latest OTA update (or revert to your safestrap nandroid), unroot it and restore all the system apps that you may have frozen/deleted, and hope that Verizon will replace it.
Click to expand...
Click to collapse
Thanks for your input.
(verizon wouldn't replace it since I baught it from someone else (legit) and I don't have verizon.
UNLESS you think if I had the previous owner take it into the store could they replace it? what steps would they take to see if it was rooted?
_______________________
I never unrooted it when I did allll of this
Do you think rerooting is soumething that I should have done before doing this?
Or most likely is this a flex ribbon cable thing ....
I just tried the diagnostic (leave keyboard open then turn the screen off and on thing)
it came on at least 3 times normal then it didn't either right after the 3rd try or upon closing the qwerty board ...
also do you have an answer at all for the ics portion of my problem?
THANK YOU
___________________________________________________________
EDIT!!!!!!!! Actually realized I did reroot after the sbf ota flash .....
so all things aside yehs I also did that any other solutions inquiries ...
ANYONE ELSE PLEASE HELP!

Another path to try down is Motorola - depending on the age of the phone, I believe there's a warranty through them.

stud beefpile said:
Another path to try down is Motorola - depending on the age of the phone, I believe there's a warranty through them.
Click to expand...
Click to collapse
Thanks,
well it is less than a year old I think, could I be able to get motorola to replace it when all I have is the phone no receipt or box ???
MORE HELP FROM ANYONE ELSE PLEASE

I bought my d3 off craigslist and the power button and n key weren't always working. I took it in to Verizon and had a new one in the mail 3 days later!
Sent from my XT862 using XDA App
Sorry didn't read the part about you being on cricket. Maybe you could make friends with someone that has d3 on verizon have them activate it and take it in for you.

3nJo1 said:
Thanks,
well it is less than a year old I think, could I be able to get motorola to replace it when all I have is the phone no receipt or box ???
MORE HELP FROM ANYONE ELSE PLEASE
Click to expand...
Click to collapse
I believe there is another apn type tool that the Cricket Android tools are using for their specific settings. You may have to search XDA a bit to see if anything shows up for othere phones on Cricket.
Sent from my DROID3 using XDA App

[Q] HTC One Screen Problem

Hey guys,
I bought an HTC One about 15 days ago. Within 2-3 days of using it, I started getting problems with the display screen. I suppose this problem was seen by few people who owned the HTC One X but I couldnt find any useful solutions in those formums hence im posting here.
This is what happens:
1. Whenever I receive a call, the screen goes black and doesnot turn on until I hang up the call. This effectively makes the device useless as a phone, as I can't see who is calling and also during call I cannot access the screen.
2. Sometimes, there is a delay with the power button. When I press the power button, the touchscreen becomes responsive but the display doesn't turn on.
The problem is, if I factory reset the device, it starts working perfectly again!! Again after about 2 days it starts the same problems.
So I thought it was a software issue and so, I got s-off and installed the GPE Rom on the device. 7 days passed, no problems. On the 8th day, the same problem occured again. And as earlier, factory resetting solved the problem.
Is this a software issue, hardware issue or something else I dont know about?
I have taken a video of the device malfunctioning, but I don't know if I can post it as an attachment.
Thanks in advance!

anibjoshi said:
Hey guys,
I bought an HTC One about 15 days ago. Within 2-3 days of using it, I started getting problems with the display screen. I suppose this problem was seen by few people who owned the HTC One X but I couldnt find any useful solutions in those formums hence im posting here.
This is what happens:
1. Whenever I receive a call, the screen goes black and doesnot turn on until I hang up the call. This effectively makes the device useless as a phone, as I can't see who is calling and also during call I cannot access the screen.
2. Sometimes, there is a delay with the power button. When I press the power button, the touchscreen becomes responsive but the display doesn't turn on.
The problem is, if I factory reset the device, it starts working perfectly again!! Again after about 2 days it starts the same problems.
So I thought it was a software issue and so, I got s-off and installed the GPE Rom on the device. 7 days passed, no problems. On the 8th day, the same problem occured again. And as earlier, factory resetting solved the problem.
Is this a software issue, hardware issue or something else I dont know about?
I have taken a video of the device malfunctioning, but I don't know if I can post it as an attachment.
Thanks in advance!
Click to expand...
Click to collapse
upload it on youtube and post the link.
And something else. Make a factory reset again and then don't install any apps. Does the error also occure?

Im new to XDA forums and hence the site does not allow me to post URLS. However I have uploaded the video to youtube.
If you put 'HTC One screen problem Aniruddha Joshi ' in the youtube search box, you will find my video.
Im sorry I couldnt think of any other way
I did not install anything out of the ordinary. Just updated the existing google apps and installed facebook, twitter and whatsapp! No crazy apks or unknown apps.
Also, once I factory reset the phone, it starts working perfectly and there is no way to know the time after which it starts giving problems again. Once it was 3 hours, once it was a week.
So I don't have any way to check if some app is causing the problems.

LibertyMarine said:
upload it on youtube and post the link.
And something else. Make a factory reset again and then don't install any apps. Does the error also occure?
Click to expand...
Click to collapse
Im new to XDA forums and hence the site does not allow me to post URLS. However I have uploaded the video to youtube.
If you put 'HTC One screen problem Aniruddha Joshi ' in the youtube search box, you will find my video.
Im sorry I couldnt think of any other way
I did not install anything out of the ordinary. Just updated the existing google apps and installed facebook, twitter and whatsapp! No crazy apks or unknown apps.
Also, once I factory reset the phone, it starts working perfectly and there is no way to know the time after which it starts giving problems again. Once it was 3 hours, once it was a week.
So I don't have any way to check if some app is causing the problems.

anibjoshi said:
Im new to XDA forums and hence the site does not allow me to post URLS. However I have uploaded the video to youtube.
If you put 'HTC One screen problem Aniruddha Joshi ' in the youtube search box, you will find my video.
Im sorry I couldnt think of any other way
I did not install anything out of the ordinary. Just updated the existing google apps and installed facebook, twitter and whatsapp! No crazy apks or unknown apps.
Also, once I factory reset the phone, it starts working perfectly and there is no way to know the time after which it starts giving problems again. Once it was 3 hours, once it was a week.
So I don't have any way to check if some app is causing the problems.
Click to expand...
Click to collapse
after seeing your video, I am even more confused. I really don't know what could cause this problem. But the fact, that I didn't have this issue and almost no other person too, makes me think about a hardware defect. But the randomness and that it only occures after several days don't support this theory. So the only thing we can do about his is basic troubleshooting.
- 1) Try to flash Cyanogenmod and try this mod for several days
- 2) Try another Rom, for example: Omni Rom
- 3) Try to use a different Kernel for GPE stock.
- 4) Use a RUU that matches for you
Sorry, I don't have any other ideas left! But after this troubleshooting we may get new information or gain some knowledge that allows us to determine the cause of this error more exactly!

anibjoshi said:
Hey guys,
I bought an HTC One about 15 days ago. Within 2-3 days of using it, I started getting problems with the display screen. I suppose this problem was seen by few people who owned the HTC One X but I couldnt find any useful solutions in those formums hence im posting here.
This is what happens:
1. Whenever I receive a call, the screen goes black and doesnot turn on until I hang up the call. This effectively makes the device useless as a phone, as I can't see who is calling and also during call I cannot access the screen.
2. Sometimes, there is a delay with the power button. When I press the power button, the touchscreen becomes responsive but the display doesn't turn on.
The problem is, if I factory reset the device, it starts working perfectly again!! Again after about 2 days it starts the same problems.
So I thought it was a software issue and so, I got s-off and installed the GPE Rom on the device. 7 days passed, no problems. On the 8th day, the same problem occured again. And as earlier, factory resetting solved the problem.
Is this a software issue, hardware issue or something else I dont know about?
I have taken a video of the device malfunctioning, but I don't know if I can post it as an attachment.
Thanks in advance!
Click to expand...
Click to collapse
Try flashing a Sense ROM, like ARHD or MaximusHD?
Enviado de meu HTC One usando Tapatalk

LibertyMarine said:
after seeing your video, I am even more confused. I really don't know what could cause this problem. But the fact, that I didn't have this issue and almost no other person too, makes me think about a hardware defect. But the randomness and that it only occures after several days don't support this theory. So the only thing we can do about his is basic troubleshooting.
- 1) Try to flash Cyanogenmod and try this mod for several days
- 2) Try another Rom, for example: Omni Rom
- 3) Try to use a different Kernel for GPE stock.
- 4) Use a RUU that matches for you
Sorry, I don't have any other ideas left! But after this troubleshooting we may get new information or gain some knowledge that allows us to determine the cause of this error more exactly!
Click to expand...
Click to collapse
The original device shipped with sense Rom. I flashed GPE to check if it was a software fault. But no luck. It gave the same problem although significantly later(about a week after I flashed it).
One more thing, I hope this gives some more information..
One time, I had rooted the device and installed a custom recovery. The phone was then working perfectly for about 4-5 days. and then later when I went ahead and unrooted the device, it immediately started giving problems. So I rooted it again hoping that the problem will go away, but no luck...the problem persisted. So, I had no option than to factory reset again, at which point it started working perfectly again.
This is all so bizarre, I have never seen something like this happen
This is just a theory, but is it possible that there is a problem with the hardware which gets triggered only on certain conditions, like some interrupt, or flag or something like that?
So until those conditions are not met, the device runs perfectly, and when they are, it starts giving issues.
Thats all i can think of as the reason.

well its clearly something youre installing if it is occuring after a few days, a root app which controls your sensor or brightness probably, do you have apps of that nature?

IINexusII said:
well its clearly something youre installing if it is occuring after a few days, a root app which controls your sensor or brightness probably, do you have apps of that nature?
Click to expand...
Click to collapse
No I rooted the device but did not install any root apps...i unrooted the device to install the GPE Rom(not necessary i know, but it seemed like a proper way) and found that it started giving problems immediately. Can non-root regular apps also cause such problems? I had installed only a limited number of apps anyway, updated the pre installed apps, facebook, twitter, whatsapp, some games..thats it..nothing wierd..

Might be a Screen-Off max. frequency issue. Like the phone gets only 500Mhz in sleep mode at maximum. Which is to low for an incoming call. Could you install a app like Android Tuner or Trickster Mod to check your Screen-Off Max frequency. If it`s that low, set it to ~1000Mhz.

anibjoshi said:
The original device shipped with sense Rom. I flashed GPE to check if it was a software fault. But no luck. It gave the same problem although significantly later(about a week after I flashed it).
One more thing, I hope this gives some more information..
One time, I had rooted the device and installed a custom recovery. The phone was then working perfectly for about 4-5 days. and then later when I went ahead and unrooted the device, it immediately started giving problems. So I rooted it again hoping that the problem will go away, but no luck...the problem persisted. So, I had no option than to factory reset again, at which point it started working perfectly again.
This is all so bizarre, I have never seen something like this happen
This is just a theory, but is it possible that there is a problem with the hardware which gets triggered only on certain conditions, like some interrupt, or flag or something like that?
So until those conditions are not met, the device runs perfectly, and when they are, it starts giving issues.
Thats all i can think of as the reason.
Click to expand...
Click to collapse
That is very stange indeed. As I don't know any other causes for this error than:
Underclocked CPU or/and GPU on screen off
Root application that controls the brightness
Hardware issue(But what would cause this???)
I can only advice you:
Since you are S OFF, take a RUU, and follow this guide and ****ing set back your device back to stock! Don't root it! Don't use custom kernels. Don't install any strange apps that may control your display brightness. SERIOUSLY! Don't install an app that controls brighness even if it works on a friends phone! Just don't!
And if you still get this issue: It is a hardware issue! If you followed step by step the instruction and if you did everything I told you to do, it HAS to be a hardware issue! The fact that the error didn't appear on GPE that fast is caused by the lower performance requierement by GPE! So I seriously have doubt that this issue is caused by a hardware defect. But it isn't impossible for sure. I just have the impression that you changed some system files and you didn't know what you were doing. This is NOT against you, but it seems to be a reasonable possibility because a factory doens't reset the /system partiton.
P.S.
I'd be very kind if you hit the thanks button since we, the community, are really trying to help you.

LibertyMarine said:
That is very stange indeed. As I don't know any other causes for this error than:
Underclocked CPU or/and GPU on screen off
Root application that controls the brightness
Hardware issue(But what would cause this???)
I can only advice you:
Since you are S OFF, take a RUU, and follow this guide and ****ing set back your device back to stock! Don't root it! Don't use custom kernels. Don't install any strange apps that may control your display brightness. SERIOUSLY! Don't install an app that controls brighness even if it works on a friends phone! Just don't!
And if you still get this issue: It is a hardware issue! If you followed step by step the instruction and if you did everything I told you to do, it HAS to be a hardware issue! The fact that the error didn't appear on GPE that fast is caused by the lower performance requierement by GPE! So I seriously have doubt that this issue is caused by a hardware defect. But it isn't impossible for sure. I just have the impression that you changed some system files and you didn't know what you were doing. This is NOT against you, but it seems to be a reasonable possibility because a factory doens't reset the /system partiton.
P.S.
I'd be very kind if you hit the thanks button since we, the community, are really trying to help you.
Click to expand...
Click to collapse
Agreed, trying following the guide and if it doesn't work make it s-on and send it to HTC for them to give a look.
Sent from my HTC One

LibertyMarine said:
That is very stange indeed. As I don't know any other causes for this error than:
Underclocked CPU or/and GPU on screen off
Root application that controls the brightness
Hardware issue(But what would cause this???)
I can only advice you:
Since you are S OFF, take a RUU, and follow this guide and ****ing set back your device back to stock! Don't root it! Don't use custom kernels. Don't install any strange apps that may control your display brightness. SERIOUSLY! Don't install an app that controls brighness even if it works on a friends phone! Just don't!
And if you still get this issue: It is a hardware issue! If you followed step by step the instruction and if you did everything I told you to do, it HAS to be a hardware issue! The fact that the error didn't appear on GPE that fast is caused by the lower performance requierement by GPE! So I seriously have doubt that this issue is caused by a hardware defect. But it isn't impossible for sure. I just have the impression that you changed some system files and you didn't know what you were doing. This is NOT against you, but it seems to be a reasonable possibility because a factory doens't reset the /system partiton.
P.S.
I'd be very kind if you hit the thanks button since we, the community, are really trying to help you.
Click to expand...
Click to collapse
I will definitely follow your guide and try to troubleshoot the problem. I hope its not some hardware defect and I dont have to send the device to HTC. I've heard those guys are poor at customer service
Thanks a lot, you've been a great help!
Btw, I was trying to find that Thanks button since the first day, I just couldn't figure out where it was. I just did.
Thanks again

Yup try installing kernel and custom rom.
Remove the case and try ( i know this is stupid thing but can give it a try)

Jvov said:
Agreed, trying following the guide and if it doesn't work make it s-on and send it to HTC for them to give a look.
Sent from my HTC One
Click to expand...
Click to collapse
Thanks for your help buddy! I really appreciate it!

anibjoshi said:
I will definitely follow your guide and try to troubleshoot the problem. I hope its not some hardware defect and I dont have to send the device to HTC. I've heard those guys are poor at customer service
Thanks a lot, you've been a great help!
Btw, I was trying to find that Thanks button since the first day, I just couldn't figure out where it was. I just did.
Thanks again
Click to expand...
Click to collapse
Thanks ! That's awesome and gives so much motivation! If you find out that you have a hardware defect and that you have to send it to HTC, I'll give you some information how to deal with those guys that you get your warranty.

Logcat for previous "Strange Issue" post.

So I posted about a strange issue with my device lately, when I shut it off, I can't turn it back on right away, I have to wait like, 20 seconds or so before it will show the "Google" splash screen again and boot. My thoughts were that maybe it is just shutting off the screen before the rest of the device ACTUALLY powers off, I messaged someone here on the forums and he told me that very well could be it. I have a logcat here of me powering off the device, is there anything here that seems off or not right? When it comes to logcats, I have no idea what any of this means lol Thanks in advance to anyone who can decipher this logcat.
http://pastebin.com/rDkb6TbQ

You can stop there! It's the new bootloader. You can roll it back an older one to fix it.

Does the logcat look suspicious? Or is this just a know thing? Thanks for the reply! I could use all the help!
Sent from my Nexus 6 using XDA-Developers mobile app

H4X0R46 said:
Does the logcat look suspicious? Or is this just a know thing? Thanks for the reply! I could use all the help!
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Didn't look at your log. Known issue

DR3W5K1 said:
Didn't look at your log. Known issue
Click to expand...
Click to collapse
Thanks! Seems like it does it with the MOB30I bootloader and the N preview bootloader, strange.

H4X0R46 said:
Thanks! Seems like it does it with the MOB30I bootloader and the N preview bootloader, strange.
Click to expand...
Click to collapse
Try the one before those two

H4X0R46 said:
So I posted about a strange issue with my device lately, when I shut it off, I can't turn it back on right away, I have to wait like, 20 seconds or so before it will show the "Google" splash screen again and boot. My thoughts were that maybe it is just shutting off the screen before the rest of the device ACTUALLY powers off, I messaged someone here on the forums and he told me that very well could be it. I have a logcat here of me powering off the device, is there anything here that seems off or not right? When it comes to logcats, I have no idea what any of this means lol Thanks in advance to anyone who can decipher this logcat.
http://pastebin.com/rDkb6TbQ
Click to expand...
Click to collapse
Im gonna be honest. You shot yourself in the foot. Any dev that looks at that logcat will not help you due to you having and using lucky patcher. That app will make sure that devs hate you. Sorry man but that is the way it is. Also might want to keep in mind that developers are adding in code that causes issues if it detects things like lucky patcher. Bewteen that and that malware ridden app of ES file manager and your issues could be many.
I will say this. There are tons of system errors all over that log. Might want to start from the ground up and knock out the system errors.

H4X0R46 said:
So I posted about a strange issue with my device lately, when I shut it off, I can't turn it back on right away, I have to wait like, 20 seconds or so before it will show the "Google" splash screen again and boot. My thoughts were that maybe it is just shutting off the screen before the rest of the device ACTUALLY powers off, I messaged someone here on the forums and he told me that very well could be it. I have a logcat here of me powering off the device, is there anything here that seems off or not right? When it comes to logcats, I have no idea what any of this means lol Thanks in advance to anyone who can decipher this logcat.
http://pastebin.com/rDkb6TbQ
Click to expand...
Click to collapse
DR3W5K1 said:
You can stop there! It's the new bootloader. You can roll it back an older one to fix it.
Click to expand...
Click to collapse
Which bootloader? I am running the latest bootloader from the N preview 3 firmware and when I power off my device, about 2 seconds after the screen goes black, I can then press the power button and it comes on just fine real quick. This is the bootloader that makes the "Google" logo bold. No problems here at all.
And out of curiosity, may I ask why you need to power off the device, and then turn it back on immediately? Why not just reboot your device if your on a custom firmware.

zelendel said:
Im gonna be honest. You shot yourself in the foot. Any dev that looks at that logcat will not help you due to you having and using lucky patcher. That app will make sure that devs hate you. Sorry man but that is the way it is. Also might want to keep in mind that developers are adding in code that causes issues if it detects things like lucky patcher. Bewteen that and that malware ridden app of ES file manager and your issues could be many.
I will say this. There are tons of system errors all over that log. Might want to start from the ground up and knock out the system errors.
Click to expand...
Click to collapse
So lucky patcher can cause issues, and es file manager is bad as well? Never knew. I saw that there were lots of errors in my logcat, but not experienced enough to figure out what they mean. Would you advise not using either of these apps then? And with this many issues in the logcat, is that the entire problem? Thanks.
EDIT: I should also add that I'm running the N preview.

christianpeso said:
Which bootloader? I am running the latest bootloader from the N preview 3 firmware and when I power off my device, about 2 seconds after the screen goes black, I can then press the power button and it comes on just fine real quick. This is the bootloader that makes the "Google" logo bold. No problems here at all.
And out of curiosity, may I ask why you need to power off the device, and then turn it back on immediately? Why not just reboot your device if your on a custom firmware.
Click to expand...
Click to collapse
Currently using Android N and the bootloader that comes with it, the one that makes "Google" show in bold. And reasoning would be to either boot into my bootloader and recovery, or to switch to another ROM. (I use multirom)
Another EDIT: I flashed MOB30I and formatted my userdata, clean start. I'm gonna keep an eye on my logcats and see what happens, so far, no errors like you saw in the posted logcat. Thanks Zelendel for mentioning all the errors caused by Lucky Patcher and ES File Manager.

H4X0R46 said:
Currently using Android N and the bootloader that comes with it, the one that makes "Google" show in bold. And reasoning would be to either boot into my bootloader and recovery, or to switch to another ROM. (I use multirom)
Another EDIT: I flashed MOB30I and formatted my userdata, clean start. I'm gonna keep an eye on my logcats and see what happens, so far, no errors like you saw in the posted logcat. Thanks Zelendel for mentioning all the errors caused by Lucky Patcher and ES File Manager.
Click to expand...
Click to collapse
No prob. Sorry for the late reply. Just got off of work. Yes lucky patcher is not only hated but worked against. It is one of the main apps that the Privacy Guard commits were made for. Others have code that won't boot the rom if it gets installed.
Es file explorer has gone to heck. Also avoid anything by the Cheetah company. Same issues.