Has anyone else had random reboots with their R1 HD? I get a few a day and am not sure what the cause is. I have a Prime version converted to OEM and have unlocked the bootloader and rooted it. I am thinking it is related to the "Standby intelligent power saving" mode, but haven't had it long enough to test this theory. If anyone else has had this issue, let me know and if you fixed it.
linuxgator said:
Has anyone else had random reboots with their R1 HD? I get a few a day and am not sure what the cause is. I have a Prime version converted to OEM and have unlocked the bootloader and rooted it. I am thinking it is related to the "Standby intelligent power saving" mode, but haven't had it long enough to test this theory. If anyone else has had this issue, let me know and if you fixed it.
Click to expand...
Click to collapse
I have never experienced an issue of random reboots on Prime w/ conversion, or with Prime itself. I have manually removed amazon bloat and some Google bloat. Only issue I seem to have is apps disappearing from adopted storage, more so on Prime. Do you have any third party software that may be causing this? Or possibly defective hardware? Try running a stress test see if possibly a hardware issue...
https://play.google.com/store/apps/details?id=com.into.stability
kal250 said:
I have never experienced an issue of random reboots on Prime w/ conversion, or with Prime itself. I have manually removed amazon bloat and some Google bloat. Only issue I seem to have is apps disappearing from adopted storage, more so on Prime. Do you have any third party software that may be causing this? Or possibly defective hardware?
Click to expand...
Click to collapse
I don't have any apps that I haven't used on other phones before with no issues. I doubt it's a hardware issue unless it's just a bad design. I am wondering if the power button itself is getting pressed while in my pocket. When I get a case that can give it a bit more protection I should be able to see if that's the problem.
Edit: I'll try out that app and see what it shows if/when I see it reboot again.
linuxgator said:
I don't have any apps that I haven't used on other phones before with no issues. I doubt it's a hardware issue unless it's just a bad design. I am wondering if the power button itself is getting pressed while in my pocket. When I get a case that can give it a bit more protection I should be able to see if that's the problem.
Edit: I'll try out that app and see what it shows if/when I see it reboot again.
Click to expand...
Click to collapse
Quick update... I flashed the OEM ROM again, this time without rooting it, and I haven't had any issues (yet). @kal250, is your phone rooted?
linuxgator said:
Quick update... I flashed the OEM ROM again, this time without rooting it, and I haven't had any issues (yet). @kal250, is your phone rooted?
Click to expand...
Click to collapse
Yes, my bootloader is unlocked, TWRP installed, and rooted, no issues. Except occasional problems with apps on SD (adopted), but not sure if its rom related or if apps just don't like being on SD.... No issues with random reboots.
kal250 said:
Yes, my bootloader is unlocked, TWRP installed, and rooted, no issues. Except occasional problems with apps on SD (adopted), but not sure if its rom related or if apps just don't like being on SD.... No issues with random reboots.
Click to expand...
Click to collapse
What root method did you use?
Sent from my BLU R1 HD using Tapatalk
linuxgator said:
What root method did you use?
Click to expand...
Click to collapse
Here..... second post
http://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
Yep, that's the method I used. However, I also converted to a system root so I could use a few apps that don't like systemless root. I'm beginning to think that may have had something to do with it. Or maybe just a bad flash at some point. It's been running strong without a reboot since I manually did it yesterday evening after reflashing the system. If it makes it through the day, I may try rooting it again.
Thanks again for your help.
Sent from my BLU R1 HD using Tapatalk
linuxgator said:
Yep, that's the method I used. However, I also converted to a system root so I could use a few apps that don't like systemless root. I'm beginning to think that may have had something to do with it. Or maybe just a bad flash at some point. It's been running strong without a reboot since I manually did it yesterday evening after reflashing the system. If it makes it through the day, I may try rooting it again.
Thanks again for your help.
Click to expand...
Click to collapse
I went with systemless root
Related
All,
We don't have an ICS Bugs thread going on. I wanted to check with some of the people here on XDA to see if they are experiencing what I am. Currently on .213, but most of these bugs I've seen since the begining. Oh, I'm also in Canada running on 3G HSPA+. I'm stock, but rooted with safestrap installed.
1) When placing a phone call, the phone hangs up immediately (you here the disconnected beep), then retries the phone call a few seconds later (it always succeeds). I have tried this on a freshly wiped phone and found the same experience. I have also tried disabling the Assisted Dialing, but have found ikt's the same thing
2) When using Google Chrome, if there is a input box, most of the time my keyboard won't appear (I'm using Swype as my default keyboard)
3) Phone runs hot sometimes, and when it's running hot it slows down to a halt. Usually happens after a day or two without a restart
4) My photo doesn't appear in the text messaging app (worked in AOKP/CM9 on my D3, as well as it works on my gf's Nexus S)
The only bug I noticed was that it initially booted up in global mode, and wouldn't connect to 4G/CDMA. Switching it to CDM+LTE fixed the issue and I haven't seen a bug since (213).:good:
podspi said:
The only bug I noticed was that it initially booted up in global mode, and wouldn't connect to 4G/CDMA. Switching it to CDM+LTE fixed the issue and I haven't seen a bug since (213).:good:
Click to expand...
Click to collapse
Is your chrome working properly? Specifically the bug I mentioned in the OP...?
I didn't comment on that because I use Opera
Just tried the Chrome Beta now just to see, and I can confirm I am seeing the same behavior. I use Swiftkey, so it isn't a Swype-specific bug either.
What exactly is the difference between Chrome and the built-in browser? Aren't they both Webkit-based? Why is Google bothering to work on both?
podspi said:
I didn't comment on that because I use Opera
Just tried the Chrome Beta now just to see, and I can confirm I am seeing the same behavior. I use Swiftkey, so it isn't a Swype-specific bug either.
What exactly is the difference between Chrome and the built-in browser? Aren't they both Webkit-based? Why is Google bothering to work on both?
Click to expand...
Click to collapse
Chrome is way faster at many things since it users hardware acceleration for video. Does text input work properly on opera?
Sent from my XT894 running ICS
I'm in the US also running .213
I haven't noticed any bugs, its working fine for me. I do not use chrome beta so I can't comment on that. The stock is not too bad, I don't use it much anyways.
Sent from my DROID4 using xda app-developers app
danifunker said:
Chrome is way faster at many things since it users hardware acceleration for video. Does text input work properly on opera?
Sent from my XT894 running ICS
Click to expand...
Click to collapse
Text entry works fine in both the stock browser and Opera. BTW, Opera also has hardware acceleration, which is why it never worked in any of the Frankbuilds of ICS based off the GB kernel ... So you can have your teh snappy and type with it too :laugh:
I'm on the 212 build and i can't screencap using power + volume down.
Is this fixed in 213 or am i just doing it wrong?
Also on 212 i can't control the default google music app or winamp from my bluetooth headset when the screen is off. I could do this before with the same version of the winamp app when i was back on gingerbread. I tried upgrading winamp, but that did nothing. Is there any change in 213?
Thanks ahead of time
Edit: just tried it and the volume down + power combo worked. Lol
One question, possible thought to ponder.
Are the bugs being described here really bugs of Android 4 or are they bugs in the individual app itself not being fully compatible with Android 4 yet?
Do similar bugs happen on a non-motorola device with android 4?
I'm considering flashing one of the leaks, so I'm trying to understand how you are sure these are ics bugs before I make the leap and run into issues.
Thanks.
Apologies if this constitutes hijacking the thread, if it does let me know and I"ll edit it to delete the question.
I was able to figure out bug #4, I had to login with my Google+ account again, since the update yesterday everything seems to be working fine.
Bugs 1 through 3 still exist, although I've switched off Global mode for now and put it to GSM only, it seems like the phone runs a lot cooler in this mode.
Even after updating Chrome to the final version, I'm still experiencing that text input bug. Maybe it's a Motorola issue... Can't wait for the next version of the leak!
I have tasker reboot my phone every morning at 6am. The phone doesn't need to be rebooted every day, but it ensures that it is fresh and ready to go every morning :laugh:
Nothing more annoying than trying to do something with your phone and having to reboot it because it is slow for whatever reason.
podspi said:
I have tasker reboot my phone every morning at 6am. The phone doesn't need to be rebooted every day, but it ensures that it is fresh and ready to go every morning :laugh:
Nothing more annoying than trying to do something with your phone and having to reboot it because it is slow for whatever reason.
Click to expand...
Click to collapse
for this reason I think there will be other leaks, ICS is supposed to handle killing processes much better than GB, however the settings seem to not be aggressive enough in 213.
Probably there will be, though I likely won't update again for a while. Don't feel like losing all that data...
podspi said:
Probably there will be, though I likely won't update again for a while. Don't feel like losing all that data...
Click to expand...
Click to collapse
You could just do what I do: once you have root install safestrap and then take a backup of your phone before flashing the upgrade.
Once you're all done upgrading, re-root and re-install safestrap, then do an advanced restore and only restore the data. Voilla, all your apps are back.
podspi said:
Probably there will be, though I likely won't update again for a while. Don't feel like losing all that data...
Click to expand...
Click to collapse
I don't know, just had a random reboot after watching a youtube video in firefox, most likely memory related, not sure who's fault though, Motorola or Firefox. gotta root and use system tuner to change memory mgmt states.
danifunker said:
You could just do what I do: once you have root install safestrap and then take a backup of your phone before flashing the upgrade.
Once you're all done upgrading, re-root and re-install safestrap, then do an advanced restore and only restore the data. Voilla, all your apps are back.
Click to expand...
Click to collapse
That is a great idea. Though there hasn't been another leak since 213, so
Notification Bar Sticking/Wont Pull Down
I am on 212 currently, and I have noticed in 208 and 212 something that has happened only twice so far. Today, I just tried to check my notifications, and the bar will not pull down.
After a reboot it works fine, and it has only happened 2 times in the past couple weeks since the leaks first appeared.
Obviously it is a minor glitch, but just thought I'd throw it out there in case anyone else has seen it and overlooked it. :cyclops:
danifunker said:
You could just do what I do: once you have root install safestrap and then take a backup of your phone before flashing the upgrade.
Once you're all done upgrading, re-root and re-install safestrap, then do an advanced restore and only restore the data. Voilla, all your apps are back.
Click to expand...
Click to collapse
I have heard of a few others using this method successfully. If you are not using safestrap or just don't want to go this route take a look at the post link in my signature. It's a modified version of the original Droid 4 Utility and includes a script to jump from one ICS leak to another without losing data. It also flashes the GB files and the Kernel (boot.img) in one script, thus making it easier to go from one leak to another.
Regarding bugs, my wife got a razr yesterday. It wouldn't pull down the ICS update, so I just sideloaded it. We both run some of the same apps. So this gave me a chance to do side by side comparisons.The issue with some of the icons being small in the left top of the status seems to be a app issue. The chrome issue isn't present on the razr, of course there isn't a physical keyboard. Otherwise my 213 ICS seems to run great.
I found a new bug, it looks like GSM call forwarding doesn't work properly... at least it doesn't with my SIM card, I'm on Rogers in Canada.
Does Verizon support call forwarding? Does it work on there?
I have noticed in Chrome that pressing shift and then one of the symbol keys (like @) will only work if you hold the shift key.
More importantly I don't get notifications of app updates from google play. Check to see if you have any apps that need updating. Superuser had a update on July 1, dropbox yesterday and voodoo rootkeeper on June 28, I think. Anyone else?
I did a mass app update in the Play Store last night (c.18 apps but crucially, I don't remember which ones!) and am now stuck in the following loop:
1. Boot handset (S3 LTE)
2. Watch responsiveness get progressively worse over period of a few minutes while available RAM shrinks progressively to zero
3. Phone shuts down or soft reboots when it runs out of available RAM.
I can't see any obvious culprit but then am no real expert in what I'm looking for. Desperate to avoid factory reset, particularly as I can't even get the phone to stay on long enough to sort out my backups.
Any thoughts?
Install this then run it as soon as you have booted up, it will stop the apps and free up your ram.
https://play.google.com/store/apps/...GwsMSwyLDEsImNvbS5jbGVhbm1hc3Rlci5tZ3VhcmQiXQ..
Raistlin1158 said:
Install this then run it as soon as you have booted up, it will stop the apps and free up your ram.
https://play.google.com/store/apps/...GwsMSwyLDEsImNvbS5jbGVhbm1hc3Rlci5tZ3VhcmQiXQ..
Click to expand...
Click to collapse
Thanks for the suggestion but the task killer shows no tasks running (and therefore nothing to kill), which fits with what the native task manager is saying. I don't know whether it's some background process but whatever it is, it seems quite hard to identify!
Very confused. From what (admittedly little) I understand, it should be impossible for Android to "run out of" RAM, which is exactly what's happening to me. Which begs the question, why isn't the system doing what it is supposed to? Which in turn makes me think this may not actually be app-related.
Sorry, bit stream of consciousness but if anyone else has any ideas they'd be gratefully received.
maybe some apps don't play well togheter and triger this issue, is your phone rooted?
maranello69 said:
maybe some apps don't play well togheter and triger this issue, is your phone rooted?
Click to expand...
Click to collapse
Possibly, I guess the question is which apps? Yes, I am rooted.
Starting to wonder whether this is related to the problems with SuperSU that seem to have arisen in the last update.
dave_uk said:
Possibly, I guess the question is which apps? Yes, I am rooted.
Starting to wonder whether this is related to the problems with SuperSU that seem to have arisen in the last update.
Click to expand...
Click to collapse
In case this is of use to anyone else, having now unrooted and removed SuperSU, problem seems to have disappeared! Chainfire is working on a fix.
I've tried browsing the forums, and even locating the post talking about the fix for the camera, and I simply can't find it. I really don't want to go without a phone seeing as my job requires my phone, but it really sucks not having a camera or a flashlight toggle.
I've seen some people that have indicated its a physical issue, however, it sporadically starts working again. Note: I would like to avoid doing the super data wipe as I'm also having computer issues at the same time. If someone needs me to post a catalog, I will need help Learning what to filter out in order to upload only the necessary info.
I've tried wiping the data through twrp advanced wipe, and of course the dalvik cache has been wiped many-a-time. Any help would be appreciated!
Um...I don't think you even explain you problem. Might want to elaborate a bit.
Sent from my Nexus 6 using XDA Free mobile app
No matter what ROM I use, no matter what camera I try to install, I cannot get it to consistently work. More often than not, cannot connect to camera. I feel like its a setting or file sticking on the "SD card" that is interfering. I also cannot use the flashlight toggle, and parts of Google+ and gallery crash at times. This has been intermittently occurring since my first flash. Blissful ROM v1.7 twrp 2.8.4.0
Tried every wipe except for the one that makes me type yes. I've already flashed boot.IMG to disable decryption, and I'm starting to think that may have something to do with it.
I was under the impression I had twrp 2.8.4.0, but after double checking, it looks like it was stuck on 2.8.2.1. I flashed the newer version from twrp manager, and now my camera is working. I didn't do anything other than install the new recovery. And yes I've tried rebooting my phone in the past. This may be a temporary fix, but I'll report back tomorrow on whether it is still working. This is very odd.
Andddddddd it stopped working again. Super legit.
Might be similar to my issue.
My camera started only showing front facing..even the option for back facing wasn't there. Did wipes in recovery and app settings. Would work, it seemed, but would revert right back to not working. At one point the camera app wasn't appearing in the app drawer at all even though it was shown in "all apps".
This occurred on stock and custom ROMs. I was advised to try flashing factory IMG but I'm well within the warranty period ( phone less than 2weeks) so I'm locking it back up and have a replacement on the way from ATT...
* I also noticed the issue starting while I was on bliss ROM 1.7
Sent from my Nexus 6 using XDA Free mobile app
My camera is really shaky and won't focus correctly in landscape mode. I returned the first phone I had for basically the same thing because it wasn't focusing in portrait mode but looked fine in landscape. I haven't seen anyone else have this issue. At first I thought the camera was inconsistent but if you zoom in you can see that it doesn't focus properly.
I'm starting to wonder why there are so many people experiencing the same or similar camera issues. The only reason I'm starting to think that it is software based and not entirely hardware based is because I was having this same issue (cannot connect to camera) on my sgs5 with cm based Roms.
I'm not saying any of this makes sense, its just strange. I wish we could help troubleshoot what the root of this problem is instead of just RMAing the device. I'm afraid to RMA with T-Mobile.
you better do it before its too late. id rma it.
cellularticulate said:
No matter what ROM I use, no matter what camera I try to install, I cannot get it to consistently work. More often than not, cannot connect to camera. I feel like its a setting or file sticking on the "SD card" that is interfering. I also cannot use the flashlight toggle, and parts of Google+ and gallery crash at times. This has been intermittently occurring since my first flash. Blissful ROM v1.7 twrp 2.8.4.0
Tried every wipe except for the one that makes me type yes. I've already flashed boot.IMG to disable decryption, and I'm starting to think that may have something to do with it.
I was under the impression I had twrp 2.8.4.0, but after double checking, it looks like it was stuck on 2.8.2.1. I flashed the newer version from twrp manager, and now my camera is working. I didn't do anything other than install the new recovery. And yes I've tried rebooting my phone in the past. This may be a temporary fix, but I'll report back tomorrow on whether it is still working. This is very odd.
Click to expand...
Click to collapse
There is no sdcard.
Try going back to factory sysimage, and data wipe.
Are you using any "added in" camera software? If so, what?
cellularticulate said:
I'm starting to wonder why there are so many people experiencing the same or similar camera issues. The only reason I'm starting to think that it is software based and not entirely hardware based is because I was having this same issue (cannot connect to camera) on my sgs5 with cm based Roms.
I'm not saying any of this makes sense, its just strange. I wish we could help troubleshoot what the root of this problem is instead of just RMAing the device. I'm afraid to RMA with T-Mobile.
Click to expand...
Click to collapse
Similar issue. Get errors "Unfortunately, camera has stopped" or "cannot connect to camera." I picked up the phone right before a 2 week vacation so unfortunately I can't bring back to AT&T. Hopefully Moto plays nice. Problems originally occurred on stock 5.0 before the 5.0.1 update. Since AT&T was lagging on OTA, I flashed to the official BlissPop rom but I have the same problems. Sometimes it'll work like it's supposed to for a couple days but always reverts back to the errors. Nothing like being at the top of a mountain in Hawaii and "cannot connect to camera" right????Since I've read about this happening on so many different firmware variations, I have to believe it's a hardware issue.
I have only had issues with the stock camera app. Ive been running Pure Shamu for 2.5 weeks now and only using the Google Camera app from the play store (the one with HDR+ and the icon has the lens filled with rainbow colors) with absolutely no issues and only getting excellent quality pictures.
Had the issue where the camera wouldn't focus and everything on the screen gets jiggly and wavy like there's some sort of interference. I had motion sickness looking at the screen. Called Moto for an advance replacement and after a week of delay due to stock issue...somehow they were kind enough to upgrade me to a CW 64gb model. I hope it's new and no more camera issues.
Has everyone who got the 'no-focuse OIS' issue gotten new phone on RMA?
I took mine to repair few days ago and they said that they won't give me a new phone instantly, rather they try to fix the OIS. Not sure how that is going to work..?
They also suggested that this issue might be "self inflicted" or just an "feature" of the camera itself. fml.
Giants2010 said:
Similar issue. Get errors "Unfortunately, camera has stopped" or "cannot connect to camera." I picked up the phone right before a 2 week vacation so unfortunately I can't bring back to AT&T. Hopefully Moto plays nice. Problems originally occurred on stock 5.0 before the 5.0.1 update. Since AT&T was lagging on OTA, I flashed to the official BlissPop rom but I have the same problems. Sometimes it'll work like it's supposed to for a couple days but always reverts back to the errors. Nothing like being at the top of a mountain in Hawaii and "cannot connect to camera" right????Since I've read about this happening on so many different firmware variations, I have to believe it's a hardware issue.
Click to expand...
Click to collapse
I returned mine to stock, unroot/locked boot loader, factory reset, before shipping it off and the camera issue was still there. Maybe hardware related I'm thinking.
Sent from my Nexus 6 using XDA Free mobile app
Something rather peculiar Ive noticed...
I didn't really pinpoint this until today, but the camera very consistently starts working when you go into fastboot, load the recovery, and then boot into system. I'm really, sincerely not quite sure why this would be happening, but I still feel like it has something to do with boot.IMG
If any devs can point me in the right direction to try and track down the possibility of this being an issue, I'd love to potentially fix a bunch of people's camera issues (albeit there is probably also a hardware defect direct from moto).
Is logcat going to pick up on issues that originate from boot?
cellularticulate said:
I've tried browsing the forums, and even locating the post talking about the fix for the camera, and I simply can't find it. I really don't want to go without a phone seeing as my job requires my phone, but it really sucks not having a camera or a flashlight toggle.
I've seen some people that have indicated its a physical issue, however, it sporadically starts working again. Note: I would like to avoid doing the super data wipe as I'm also having computer issues at the same time. If someone needs me to post a catalog, I will need help Learning what to filter out in order to upload only the necessary info.
I've tried wiping the data through twrp advanced wipe, and of course the dalvik cache has been wiped many-a-time. Any help would be appreciated!
Click to expand...
Click to collapse
This is a hardware issue. Check http://forum.xda-developers.com/nexus-6/help/camera-lens-movement-t2984298
rdizzle707 said:
This is a hardware issue. Check http://forum.xda-developers.com/nexus-6/help/camera-lens-movement-t2984298
Click to expand...
Click to collapse
Not the issue I'm explaining though. This is a bit more deeply seeded of an issue. When I boot directly into the ROM, my twrp installer says I'm back on 2.8.2.1, but when I boot into fastboot and then twrp, and then ROM, it says 2.8.4.0 and my camera works. This is legitimately weird as ****.
cellularticulate said:
Not the issue I'm explaining though. This is a bit more deeply seeded of an issue. When I boot directly into the ROM, my twrp installer says I'm back on 2.8.2.1, but when I boot into fastboot and then twrp, and then ROM, it says 2.8.4.0 and my camera works. This is legitimately weird as ****.
Click to expand...
Click to collapse
Ohhh man that is weird.
rdizzle707 said:
This is a hardware issue. Check http://forum.xda-developers.com/nexus-6/help/camera-lens-movement-t2984298
Click to expand...
Click to collapse
rdizzle707 said:
Ohhh man that is weird.
Click to expand...
Click to collapse
It appears a bit more stable now. I tried flashing twrp from my computer and it seems to be a bit more nice. That and normal reboot to twrp doesn't say 2.8.2.1 - let me check twrp manager now.
And my camera and flashlight have worked for almost three days now. Dafuq.
Same issue. "Unfortunately, Camera has stopped."
No flash light available, only front camera working, clicking on HDR exits the app with the aforementioned error message.
Has anyone solved this issue?
I was on 5.1 stock (with root) and now I've updated to 5.1.1, but with no change to the Camera behaviour.
OK, so this is an interesting one that's not the end of the world but odd non the less.
My phone 64GB CW bought from GPS. Rooted only, stock recovery still. Lightflow, and carrier tether check disabled are the only two mods I really wanted.
My friend 64GB CW bought from GPS. Stock no root.
His phone will play crossy road just fine, Mine will boot it until it gets to the developer name then crash out.
Anyone else had weird quirks with apps like this after root? I've seen one thread about it and it said to clear the cache in recovery, and that didn't work for everyone. I haven't felt the need to put a 3rd party recovery on yet so I really can't do that quickly.
meest said:
OK, so this is an interesting one that's not the end of the world but odd non the less.
My phone 64GB CW bought from GPS. Rooted only, stock recovery still. Lightflow, and carrier tether check disabled are the only two mods I really wanted.
My friend 64GB CW bought from GPS. Stock no root.
His phone will play crossy road just fine, Mine will boot it until it gets to the developer name then crash out.
Anyone else had weird quirks with apps like this after root? I've seen one thread about it and it said to clear the cache in recovery, and that didn't work for everyone. I haven't felt the need to put a 3rd party recovery on yet so I really can't do that quickly.
Click to expand...
Click to collapse
Doesnt the stock recovery have a wipe cache option? It did on the 5
I've got a rooted 64GB MB and it plays Crossy Road just fine.
rootSU said:
Doesnt the stock recovery have a wipe cache option? It did on the 5
Click to expand...
Click to collapse
If there is I'm not sure how to get to it? I'm assuming a command of some sorts via ADB or Fastboot? This is my first Nexus device since my GNex since i'm on Verizon. So is my Friend though. Both of us still encrypted also. I've uninstalled and installed 4-5 times also. Cleared app cache a few times also.
I find it really strange as well. I download it, closes on developers name screen. Tried on two different roms and both don't work . Maybe just a bug. Not much info to be found on the issue.
jellybsly55 said:
I find it really strange as well. I download it, closes on developers name screen. Tried on two different roms and both don't work . Maybe just a bug. Not much info to be found on the issue.
Click to expand...
Click to collapse
What sort of similar changes have you been making? DPI changes, kernel changes or something else that may be common between the ROMs. Also, I am assuming you wiped in between the ROMs, if so did you restore data. I am just thinking out loud though. Logcats would probably help you find the cause of the problem.
Crossyroads has worked for me on stock, rooted or not, chroma, slimlp, try clearing data on the game, install from playstore and dont restore from TiBu if you are.
Donjuanal said:
Crossyroads has worked for me on stock, rooted or not, chroma, slimlp, try clearing data on the game, install from playstore and dont restore from TiBu if you are.
Click to expand...
Click to collapse
Yeah it's quite weird. (Nexus 5 though, shouldn't really make a difference). I don't even have a cache/date to clear since the game won't boot up enough to make one i think . Quite strange, just wanted to say that the OP isn't only one
It crashed everytime on my N6 so I emailed the developer and he said it doesn't work with ad blockers installed.. So I disabled the adblocker I had running and crossy road loaded just fine with exact same setup.. So if you have adblockers that's probably the issue.
meest said:
OK, so this is an interesting one that's not the end of the world but odd non the less.
My phone 64GB CW bought from GPS. Rooted only, stock recovery still. Lightflow, and carrier tether check disabled are the only two mods I really wanted.
My friend 64GB CW bought from GPS. Stock no root.
His phone will play crossy road just fine, Mine will boot it until it gets to the developer name then crash out.
Anyone else had weird quirks with apps like this after root? I've seen one thread about it and it said to clear the cache in recovery, and that didn't work for everyone. I haven't felt the need to put a 3rd party recovery on yet so I really can't do that quickly.
Click to expand...
Click to collapse
See attached pic
We need min min guard for lollipop or something that let's us choose which apps to block ads.
Guys,
I have Tencent version with WW fingerprint. Had it since end of September. It will not charge (no lights) and not turn on with any combination of power and volume etc. I have tried both ports in a PC and nothing.
If anyone can help, great, but I'm not optimistic. Anyone know if there was an update last night. I did have Asus Launcher 1.04 by HomerSP installed (https://forum.xda-developers.com/rog-phone-2/themes/app-asusupdater-ww-updates-tencent-t4022547) and was just wondering if somehow it did update but I suspect something went pop in the night. It was charging at the time.
I'm in the UK so I doubt Asus will honour a warranty.
Thanks guys for taking the time to read.
EDIT: Guys Phone just came on. Held down power and plugged it in to my PC. Sorry for the time you wasted reading this....
Glad u fix it, i think it's software issue, before i had a few bugs like fps drops in games, screenrotation after unlocking screen etc... For me that default rom is really crap, so looking forwrd for Android10 and custom roms. Btw i can recommend to flash kernel from here https://forum.xda-developers.com/ro...rnel-kirisakura-1-0-0-asus-rog-phone-t4028237 - since then i didn't have serious issue
Thanks for the suggestion. I do like custom ROMs but I need to retain my banking apps. Using magisk modules didn't help with my old doggee S60 phone... They still spotted the root.
If anyone can confirm it works with starling, vanquis and EE I'd give it a go
scum2000 said:
Thanks for the suggestion. I do like custom ROMs but I need to retain my banking apps. Using magisk modules didn't help with my old doggee S60 phone... They still spotted the root.
If anyone can confirm it works with starling, vanquis and EE I'd give it a go
Click to expand...
Click to collapse
Did You change magisk manager's app name? Did the trick for me (hide etc ofc enabled)
VarDes said:
Did You change magisk manager's app name? Did the trick for me (hide etc ofc enabled)
Click to expand...
Click to collapse
Yes, I tried that on S60 made no difference. It's coming to the point where I may risk it. I miss twrp and I want to have LTE and WiFi calling. I'm sick of waiting for Asus to official activate them. I'm really happy with the phone overall.