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.
Related
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. =]
Sorry for the vague title, but I couldn't think of a concise way of describing this.
I have a T-Mobile HTC One with the GPe ROM installed on it. I'm on 4.4.2 and using ART. I woke up this morning to find my phone in a boot loop. It would come up with the screen that shows the "Google" logo and the icon showing my phone is unlocked, remain on that screen for longer than normal, then reboot and do it again before getting to the actual ROM boot sequence.
I held down the power button to shut the phone off. When I turned it back on, it made it to the ROM boot, where the four colored circles fly around, but then came up with a screen asking for my disk encryption password. I've never set up encryption on the phone. I didn't want to try passwords I use in case this was some kind of phishing, though I'm not sure how that would be possible. At this point I wasn't really in the mood to do much troubleshooting so I did a factory reset from the bootloader and it seems fine now.
I'm just wondering if anyone knows what happened.
kernco said:
Sorry for the vague title, but I couldn't think of a concise way of describing this.
I have a T-Mobile HTC One with the GPe ROM installed on it. I'm on 4.4.2 and using ART. I woke up this morning to find my phone in a boot loop. It would come up with the screen that shows the "Google" logo and the icon showing my phone is unlocked, remain on that screen for longer than normal, then reboot and do it again before getting to the actual ROM boot sequence.
I held down the power button to shut the phone off. When I turned it back on, it made it to the ROM boot, where the four colored circles fly around, but then came up with a screen asking for my disk encryption password. I've never set up encryption on the phone. I didn't want to try passwords I use in case this was some kind of phishing, though I'm not sure how that would be possible. At this point I wasn't really in the mood to do much troubleshooting so I did a factory reset from the bootloader and it seems fine now.
I'm just wondering if anyone knows what happened.
Click to expand...
Click to collapse
Just don't use ART for now, stay with Dalvik. Much stable atm.
alray said:
Just don't use ART for now, stay with Dalvik. Much stable atm.
Click to expand...
Click to collapse
I wasn't planning on switching back to it. But that's not really answering my question about if anyone knows what happened. Unless you're saying that this is a known problem that happens to people who use ART, but it sounds more like you're just saying since I was using ART and something went wrong, it's a good chance that was why.
kernco said:
I wasn't planning on switching back to it. But that's not really answering my question about if anyone knows what happened. Unless you're saying that this is a known problem that happens to people who use ART, but it sounds more like you're just saying since I was using ART and something went wrong, it's a good chance that was why.
Click to expand...
Click to collapse
What most likely happened is ART corrupted the system and it forced a bootloop. You may have to full wipe and reflash. I would also advice to stay away from ART. It is not made for users.
zelendel said:
What most likely happened is ART corrupted the system and it forced a bootloop. You may have to full wipe and reflash. I would also advice to stay away from ART. It is not made for users.
Click to expand...
Click to collapse
I did a factory reset and so far everything is fine. Are you saying there might still be an issue and I should wipe and reflash to be safe?
kernco said:
I did a factory reset and so far everything is fine. Are you saying there might still be an issue and I should wipe and reflash to be safe?
Click to expand...
Click to collapse
I would just to be safe. Mainly with the pre-Alpha tag of the ART compiler. I mean it may not even make it to be official.
When someone calls me I can't answer an incoming call. If I'm lookin at stuff on my phone it just rings and freezes what ever its on. If I try to touch the screen it doesn't respond to any touch. Really frustrated as this is my first motorola smartphone. Isn't the call screen supposed to pop up? I have rooted my phone and I'm using xposed, but I've tried to disable every module on it and still same problem! And there is others with the same problem as mine (probably without root) out there :/
Please any help would be very appreciated! Thanks
There is a gravity box setting called 'non-intrusive calls' or something like that, might be part of the problem.
My guess is its exposed. Uninstall all modules, uninstall the framework, flash the disabler zip in recovery and try it again.
laurorual said:
When someone calls me I can't answer an incoming call. If I'm lookin at stuff on my phone it just rings and freezes what ever its on. If I try to touch the screen it doesn't respond to any touch. Really frustrated as this is my first motorola smartphone. Isn't the call screen supposed to pop up? I have rooted my phone and I'm using xposed, but I've tried to disable every module on it and still same problem! And there is others with the same problem as mine (probably without root) out there :/
Please any help would be very appreciated! Thanks
Click to expand...
Click to collapse
I helped another user with an issue that matches what you have described exactly. After much troubleshooting, the only thing that fixed it was to flash the entire stock SBF as per the "Return to Stock" thread.
Keep in mind this erases EVERYTHING, including anything you have downloaded to the internal memory. So save anything important to your PC first, and put it back afterwards.
You can try other methods, but I fear they won't work - based on [much] experience.
Good Luck!
samwathegreat said:
I helped another user with an issue that matches what you have described exactly. After much troubleshooting, the only thing that fixed it was to flash the entire stock SBF as per the "Return to Stock" thread.
Keep in mind this erases EVERYTHING, including anything you have downloaded to the internal memory. So save anything important to your PC first, and put it back afterwards.
You can try other methods, but I fear they won't work - based on [much] experience.
Good Luck!
Click to expand...
Click to collapse
I feared this. I just can't imagine why this happened out of nothing. But thanks for the advice, I'll try to do this
Aha! At least you got some responses! I posted here http://forum.xda-developers.com/showthread.php?t=2826011 with the same issue and got none but yes I'm experiencing the same issue. Very dumb the phone just doesn't let you answer and takes the nav bar away
Sent from my XT1060
rocketsaucev2 said:
Aha! At least you got some responses! I posted here http://forum.xda-developers.com/showthread.php?t=2826011 with the same issue and got none but yes I'm experiencing the same issue. Very dumb the phone just doesn't let you answer and takes the nav bar away
Sent from my XT1060
Click to expand...
Click to collapse
Sorry @rocketsaucev2 . I must have missed your thread, otherwise I would have suggested this. I try to help, whenever possible. At least now you have some suggestions to go on.... Good Luck.
samwathegreat said:
Sorry @rocketsaucev2 . I must have missed your thread, otherwise I would have suggested this. I try to help, whenever possible. At least now you have some suggestions to go on.... Good Luck.
Click to expand...
Click to collapse
No sweat I didn't mean anything by it. Fwiw I did an fdr and re-fastbooted 4.4.4 (vzw) and everything is working now [emoji4]
Sent from my XT1060
Q&A for [Sprint/Boost/Virgin] DragonRom by Team YAR
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Sprint/Boost/Virgin] DragonRom by Team YAR. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
I can't even download it because boost mobile rely throttles your data speed down once you hit your high speed limit for the month ?
Ubiquitous_22 said:
I can't even download it because boost mobile rely throttles your data speed down once you hit your high speed limit for the month ?
Click to expand...
Click to collapse
Sorry. We've removed as much as we can and we still have the smallest ROM that I'm aware of.
Great Job Team YAR
Ok since i am new it wont let me post to the forums But instead go into the q/a.. So team YAR Firstly i just want to say great work on the rom however i few have few concerns and such.... Hangouts is great for sms however some people like the stock sms anyway to reimpliment that in case of someone not wanting to use hangouts as default as that is the only sms that is implemented in the rom. Also battery life is ok not a lot of things to bog it down however for some reason when your in the 3g vs 4g lte battery drain is hell. Is that a common issue when you have a 4g lte phone? Also i took a look through the build prop when i found out this rom has zero tethering capabilities. I turned the values on the build prop to reflect that tething is all in fact on however it does not allow tethering it stays greyed out. I could tether without an issue before this rom using Raptop rom. Im not calling any rom better i feel it is a based on taste decision. But i would like your rom 100% better if it included tethering. Also with this phone and i dont know if it falls the same for all boost variants but the hotspot feature has to do a subscription check to see if you actually paid for a monthly subscription. I did a little digging on the stock rom and found how to bypass it and tether without an issue. But could you please for the sake of other people include tethering with or without a bypass either native or a working 3rd party app. Also is there a way to make more space up because htc and boost did a real job on leaving little to no space and even with links2sd dont clear much up. Could removing some of the launchers help resolve the space issue?..... Sorry for the novel just my concerns
Having issue booting into rom, stuck at HTC also. :0(
originaleq said:
Having issue booting into rom, stuck at HTC also. :0(
Click to expand...
Click to collapse
Try pulling the battery. When I get hung up like that sometimes, pulling it usually does the trick. Worth a try. Let us know.
Oh yeh, was coming from RaptorRom v2. Cant get voicemail notifications with it and no visual voicemail so hoping to get on DragonRom. Yeh I have to do battery pull when the HTC screen freezes cause the power won't shut off at that point even when held down. The zip says it flashes and installs SUCESSFULLY, so I don't get it.
originaleq said:
Oh yeh, was coming from RaptorRom v2. Cant get voicemail notifications with it and no visual voicemail so hoping to get on DragonRom. Yeh I have to do battery pull when the HTC screen freezes cause the power won't shut off at that point even when held down. The zip says it flashes and installs SUCESSFULLY, so I don't get it.
Click to expand...
Click to collapse
Sometimes I have to do a "factory reset/wipe" like 3-4 times and then flash the ROM again. Usually, if all is good and I am installing the right thing, doing the right things etc, if boots up eventually. I know it can be a pain in the As* and it gets very frustrating at times, but usually it'll eventually work. Good luck man!!!
Well i dont guess im going to get a reply to my question lol
SheetzNGiggles said:
Well i dont guess im going to get a reply to my question lol
Click to expand...
Click to collapse
We didn't implement native tethering at this time. I'm sure its a function well include in a future version.
Per the space issue, Minimalist has literally just about everything we could remove, removed, if we find more things to remove, we will continue to do so. We are already planning our next release, unfortunately there is no eta currently.
As per Hangouts. I think the reason @dragonhart6505 included it is because it functions both as SMS and Hangouts. It's killing two birds with one stone for those that use Hangouts. As always, you can remove anything you deem unnecessary and replace it with your preferred app. I'm not at my computer, but if I remember correctly it is located in /system/app so you'll have to use Titanium to remove it. The kernel is pre-rooted and the write protection is disabled.
SheetzNGiggles said:
Well i dont guess im going to get a reply to my question lol
Click to expand...
Click to collapse
Native tethering has not been enabled as of yet, but we will work on including it. I use PDANet to tether via USB and Bluetooth, but its WiFi function does not work on our device. We'll get tethering resolved in a near update.
As @dip_spit said, we removed as much as possible while staying sure everything worked as it should. I am currently tearing through the entire system to find what cam be removed and what should stay. Minimalist is perfect if space is a concern, however you wont get much more than ~1gb on a stock based rom.
---------- Post added at 07:59 PM ---------- Previous post was at 07:54 PM ----------
originaleq said:
Oh yeh, was coming from RaptorRom v2. Cant get voicemail notifications with it and no visual voicemail so hoping to get on DragonRom. Yeh I have to do battery pull when the HTC screen freezes cause the power won't shut off at that point even when held down. The zip says it flashes and installs SUCESSFULLY, so I don't get it.
Click to expand...
Click to collapse
We recommend flashing from a Stock TWRP backup and factory reset as other roms appear to be conflicting with the permissions needed by a stock-based rom.
We apologize for the inconvenience and we are working on making DragonRom a fully flashable, self-sustained rom that requires no such system to be installed prior to flashing. It is alot of work getting the permissions necessary for this, so please bare with us.
Ive been late to the thread here as i was unaware it existed. Ive now subbed to the thread and will monitor it frequently
Ty
Thank you i was just wondering spacewise if links to sd would clear much more space if i was flashing minimalist rom and building from there? Also as for the tethering i hope its in your future release because i do tether alot lol and i cant always make use of bluetooth tether. But great job never the less im looking forward to testing anything new. Also i have a stock roms from any carrier as well as build.prop from any said carrier if needed.
first time poster
1st off... absolutely love this rom. I've been running the minimal rom for over a week, almost as soon as it was posted. Most storage space I've had yet on my phone! Any problems I had with initial install have easily been dealt with. The one problem I had from from the install was google play not working, would crash as soon as launched. Was solved by sending new version from my computer to install on phone. After my friend saw the rom, we tried to install the featured rom on his phone which got stuck on the HTC boot screen. This problem was solved by installing the stock backup from this site then installing the rom again. But again we love this rom, Thanks Team YAR!!!
Does DragonROM currently support Link2SD's mount scripts at boot for other filesystems than FAT? Also, how risky would it be to try Xposed at this stage of development?
kranao8472 said:
Does DragonROM currently support Link2SD's mount scripts at boot for other filesystems than FAT? Also, how risky would it be to try Xposed at this stage of development?
Click to expand...
Click to collapse
Xposed works pretty well for everyone who everyone who has installed. Remember to make TWRP backups before you install anything.
Front Facing Camera
**Ok I did a search from camera on this particular thread and nothing popped up, so sorry if someones already covered this but....
Has anyone tested the front facing camera on this mod? I need my selfies brah. Nah! but would be nice to have this back! Yo! My camera? Sweet innocent camera --never hurt anyone.
I think I screwed myself.
I think I really got a BRICK here. Ok, I did something stupid. I flashed the HBOOT trying to get the S-OFF but failed. All I got not is HBOOT and under that it says checking.,... overlaying the word checking are the words Press <POWER> to reboot. And that is it. If I try to boot regularly is hangs on the HTC Logo. Did I just really brick my phone for life???
FYI, device is NOT found using adb or fastboot. Interesting this though, when I did have the nonsense rom up and had this HBOOT issue, I could boot regularly and use flashify to boot into recover. So recover is there I just have NO way of getting to it now. Every since I flash with Dragon, no offence, cause dragon is hanging on me at the HTC Logo. AAAAHHHHHHHUUUGHHH. I just broke my phone, I think.
BadRx said:
I think I really got a BRICK here. Ok, I did something stupid. I flashed the HBOOT trying to get the S-OFF but failed. All I got not is HBOOT and under that it says checking.,... overlaying the word checking are the words Press <POWER> to reboot. And that is it. If I try to boot regularly is hangs on the HTC Logo. Did I just really brick my phone for life???
FYI, device is NOT found using adb or fastboot. Interesting this though, when I did have the nonsense rom up and had this HBOOT issue, I could boot regularly and use flashify to boot into recover. So recover is there I just have NO way of getting to it now. Every since I flash with Dragon, no offence, cause dragon is hanging on me at the HTC Logo. AAAAHHHHHHHUUUGHHH. I just broke my phone, I think.
Click to expand...
Click to collapse
Unfortunately, I think you did.
Have you tried pulling the battery and then after you put it back in hold the volume down button and then press the power button until it comes on to see if you can get into your recovery application?
MrMike2182 said:
Unfortunately, I think you did.
Have you tried pulling the battery and then after you put it back in hold the volume down button and then press the power button until it comes on to see if you can get into your recovery application?
Click to expand...
Click to collapse
WAIT! I'm back in baby!!!! HOOOOLLLLIYYYY MOLE' Apparently the HBOOT IMG was in the form of a zip files that was placed in the root of the SD CARD. As I go into HBOOT, bootloader is trying to upgrade to this zip file.. Once I took the SD Card out, bouya! HBOOT is back. What a scare that was. Still having issues booting into the new flash rom, however. I think i'm done for today though... i'm hanging up the hat for the day.
My phone is stuck on the HTC screen after installing DragonRom through the TWRP. I followed all of the directions. I'm on VM.
Once and and while my Pixel 5 reboots and gets stuck in a bootloop. It happens while I listen to music with YouTube Music on a bluetooth ear phones or search for updates on the Play Store or nothing at all. I have no idea what is causing this.
I suspect one app called ProCall Mobile but I can't really test for two reasons: 1st it happens to randomly, weeks without one, than two in a row, than nothing for a month, or for few days, 2nd I need the app for my job and can't just remove it for testing.
I'm really annoyed by this, I also can't reset the phone because of reasons. Any ideas how can I narrow it down?
Sounds like something is causing a kernel panic, and it's hard to say what. The best thing I could really recommend is a complete factory reflash, but that requires an unlocked bootloader. I believe there may be a way to use ADB and USB Debugging to get a log dump, but I have no idea how to do that or how to read it.
V0latyle said:
Sounds like something is causing a kernel panic, and it's hard to say what. The best thing I could really recommend is a complete factory reflash, but that requires an unlocked bootloader. I believe there may be a way to use ADB and USB Debugging to get a log dump, but I have no idea how to do that or how to read it.
Click to expand...
Click to collapse
I fear you are right. I think I should set aside a few hours on the weekend to do that.
tehabe said:
need the app for my job and can't just remove it for testing.
Click to expand...
Click to collapse
Nope. If it's your phone, you don't have to keep any app on it. I have never experienced bootlooping or forced reboot on P5. Ask them for a work phone or tablet. It's not like old phones are expensive.
tehabe said:
I'm really annoyed by this, I also can't reset the phone because of reasons. Any ideas how can I narrow it down?
Click to expand...
Click to collapse
Also nope. You can back the entire phone up on google, data reset and reinstall everything.
Try force stop and clear cache in app.
Uninstall reinstall app.
Remove all unused apps.
Check Battery Usage
Go to Dev Options and turn on System Tracing and other debuggin features. I highly doubt you will be able to figure it out from there, but it may help others.