Related
Hey, I have 5.0.1Gr3 and when i run pac-man it flickers and blinks during game play. Anyone have the most recent .apk i can try? or can tell me a solution? Thanks.
its the same on both.
I'm experiencing that as well. On 5.0.2Hr3. At 245mHz, 384mHz, and 528mHz.
Kinda reminds me of the flickering on the arcade, but gets annoying after a while lol.
anyone know hwo to fix this? i liekd to play pacman while taking a **** hahaha.
hey ,im haveing the same issue with pacman.i have a non rooted g1 .just updated to the cupcake filmware 1.5 . mine flickering too, its working just fine other than that. i even tryed to uninstall it and reinstall but same thing .hope fully some one will figure out why ?thanks for you help
same problem here: JFv1.5
Same problem with JF's CRB43 build. It's a Cupcake-wide problem and I have emailed Namco about this (like they read the massive amounts of email they get every day).
blackknightavalon said:
Same problem with JF's CRB43 build. It's a Cupcake-wide problem and I have emailed Namco about this (like they read the massive amounts of email they get every day).
Click to expand...
Click to collapse
lets us know what they say.thanks for emailing them .glad its not just mine
update in marketplace fixed flickering !!!!!!!!!!!
hi everyone ,just looked in market pacman game had update.it fix the flickering just wanted to let you all know!!!!!!!!!!!!!!!!!!!!
Does anyone have the .apk for the cupcake update? It wont let me download from market.
All right, so a while ago say..few hours or a day ago, I dropped my phone. Nothing seemed wrong, everything was working fine. Until I decided to go play Abduction World Attack. It's a game where you tilt the G1 and the little character moves according to how you tilt it. Surprise Surprise I ran into my problem. The little avatar wouldn't move and it was just stuck there no matter how I turned my phone. I also just noticed that auto-rotate won't work. I believe it's because the accelerometer is broken...Anyone have any advice on how to fix this or calibrate it? I've tried calibrating inside apps that use the accelerometer. I've searched but to no avail. Help will be appreciated Thank-you.
[Edit]: A wipe has fixed this! =)
If your under warranty, you may want to try and get it exchanged. Let T-Mobile/HTC know that it just stopped working.
If you are out of warranty, you can attempt at looking for a solution by taking apart the phone. The official manual is here
The manual has all of the disassemble instructions. Hopefully that will lead you to a solution.
Sounds like it could be a hardware issue but no harm in testing to see if it is a software one. Tried rebooting the mobile? If so see if other programs like Bubble works. If not then a final resort would be a reflash to at least eliminate the software side of things.
If its no go then best to try and get it exchanged...
I've fixed it guys ^^ Seemed like a wipe would do it. I changed to the hero build for a second and then reflash CM after a wipe and accelerometer is fixed. Thanks for the suggestions though! Greatly appreciated
The power of the mighty wipe ^_- Good to hear its been sorted. Since you're the OP too, could you edit the title to SOLVED so people know?
NeoBlade said:
The power of the mighty wipe ^_- Good to hear its been sorted. Since you're the OP too, could you edit the title to SOLVED so people know?
Click to expand...
Click to collapse
Sure. OP and title has been updated!
Sure wish I had your luck. I'm having the same problem and a wipe didn't do me any good.
I have tried several different mods and none of them work.
tested with browser, bubble, Papi game apps, and Accelerometer xyz Values.
I don't have any akm files located in /data/misc
I do have a /system/bin/akmd but my ps output doesn't show it running.
whatchamccallum said:
Sure wish I had your luck. I'm having the same problem and a wipe didn't do me any good.
I have tried several different mods and none of them work.
tested with browser, bubble, Papi game apps, and Accelerometer xyz Values.
I don't have any akm files located in /data/misc
I do have a /system/bin/akmd but my ps output doesn't show it running.
Click to expand...
Click to collapse
Most likely a hardware problem then mate. You could try un-rooting and see if the accelerometer works.
If I install RC29 then the accelerometer works without issue. So that rules out hardware issue.
Here is another thread I found that goes in much more detail about what I am experiencing.
http://forum.xda-developers.com/showthread.php?t=533749
so far there isn't any movement on this thread. I'm surprised that this issue isn't more wide spread.
I just had the accelerometer on my HTC Sapphire go belly up.
Auto-rotate was broken, compass apps wouldn't initialize, tilting maze games would slowly move the ball to the top left side regardless of actual tilting, etc..
Reboot didn't fix it. However I did have a file under /data/misc/akmd_set.txt and most of the values in it were set to 0.
I renamed that file to akmd_set.txt, then killed akmd, per instructions in a neighboring thread.
akmd rose from its ashes, a new akmd_set.txt automagically appeared, with lots of different numbers for each value in it. All my accelerometer-depending features were happy again.
so yay, and all that.
As a side-note, I've been playing with some not insignificant magnets on my desk, and I'm wondering if abnormal magnetic fields around my phone might have caused the accelerometer miscalibration?
Good for my G1 too.
Kudos to the OP, this solution worked perfectly on my G1 with the same symptoms. Many Thanks!
I have been having a persisting force close issue that I initially thought was linked to Greenify. "Unfortunately, Context Service has stopped" after every call I made or received, and upon booting the phone. Trial and error have caused me to find the only thing that allows me to run Xposed without any issue is having 7 or less modules enabled. I can switch between modules. For instance, I had Xposed Torch enabled and things were fine with 7 modules. I installed Xtoast, rebooted, and instant error/FC. Repeats no matter how many times I reboot. I uninstall Xposed Torch, which was just working perfectly fine, and leave XToast installed. Reboot and no error. Rebooted over and over to ensure, no error. Switched a few modules around to ensure, and it seems to not matter what modules I have installed. I have no issues whatsoever running Xposed as long as I only have seven modules installed, but if I go to install an 8th, no matter what it is, I immediately get Context Service force closes. I have not found anything on here about a definitive amount of modules you can install, so I can only hope someone has a clue what could be going on. Normally I'd look to the Logcat, but it doesn't seem to be a specific module causing this. I'd really appreciate any help any of you might have. Xposed has a lot more to offer for me than you can cram in seven modules.
Logcat? The Xposed log may not show you anything but an unfiltered logcat will.
GermainZ said:
Logcat? The Xposed log may not show you anything but an unfiltered logcat will.
Click to expand...
Click to collapse
You mean the full logcat I create through adb? If so, do i need to produce the issue while the phone is one and then take the logcat? Phone has been rebooted since the last time i got the FC, just don't want to waste time learning to upload and uploading a logcat now while phone is working if I need to re-create the problem first in order for it to be useful. Definitely will take the time to upload a logcat because I would really like to fix this issue, I just wanna make sure I do it correctly.
wrongway213 said:
You mean the full logcat I create through adb? If so, do i need to produce the issue while the phone is one and then take the logcat? Phone has been rebooted since the last time i got the FC, just don't want to waste time learning to upload and uploading a logcat now while phone is working if I need to re-create the problem first in order for it to be useful. Definitely will take the time to upload a logcat because I would really like to fix this issue, I just wanna make sure I do it correctly.
Click to expand...
Click to collapse
Enable 7+ modules so that the issue will be reproduced on next boot.
Reboot and start the logcat while the device is booting.
Wait till you see the FC and stop the logcat.
Upload the logcat.
Thanks for your reply. I just figured out the problem, thankfully.. I was preparing to do what you said, and I for some reason thought to reinstall Busybox before installing an eighth module and rebooting. My Busybox install must have been faulty. After reinstalling it said I had just reinstalled the same version as previously installed, but now I am back to nine modules and no problems.
scratch that, problem keeps getting weirder. Installed Wanam Xposed again and the issue came right back, uninstalled and the issue came back until I went back down to 7 modules and now no issue. I'm so confused..
wrongway213 said:
scratch that, problem keeps getting weirder. Installed Wanam Xposed again and the issue came right back, uninstalled and the issue came back until I went back down to 7 modules and now no issue. I'm so confused..
Click to expand...
Click to collapse
Honestly can't say anything without a logcat, please grab one.
You should also be able to use an app to do it (e.g. CatLog) since your device is booting. Just start the app as soon as your device boots.
GermainZ said:
Honestly can't say anything without a logcat, please grab one.
You should also be able to use an app to do it (e.g. CatLog) since your device is booting. Just start the app as soon as your device boots.
Click to expand...
Click to collapse
FC is not currently happening, but I just downloaded Catlog and I am still getting a lot of errors in my logcat.. makes me curious as to whether my issue can be pinpointed without messing things up yet again. I attached my logcat filtered for "error", if you are able to discern anything from it, please do let me know what you find. If not I'll be sure to load Catlog at boot and grab one if the error does occur again. Thank you for recommending Catlog, by the way, SO much easier for a new guy like me than terminal emulator/ADB.
Edit: I see you mentioned an unfiltered logcat earlier, but honestly I do not know what I am doing with logcats at all, and as the error is not occuring right now I thought it might be a little unnecessary to look through a million lines of text.. I figure this is short enough that if something sticks out I can fix it, if not I can run Catlog again if the problem persists.
F/C All devices
All of my androids device using Xpose are force closing, well apps that are associated with it. Only fix I could find is older download..it seems the update had issues..
wrongway213 said:
FC is not currently happening, but I just downloaded Catlog and I am still getting a lot of errors in my logcat.. makes me curious as to whether my issue can be pinpointed without messing things up yet again. I attached my logcat filtered for "error", if you are able to discern anything from it, please do let me know what you find. If not I'll be sure to load Catlog at boot and grab one if the error does occur again. Thank you for recommending Catlog, by the way, SO much easier for a new guy like me than terminal emulator/ADB.
Edit: I see you mentioned an unfiltered logcat earlier, but honestly I do not know what I am doing with logcats at all, and as the error is not occuring right now I thought it might be a little unnecessary to look through a million lines of text.. I figure this is short enough that if something sticks out I can fix it, if not I can run Catlog again if the problem persists.
Click to expand...
Click to collapse
I'm asking for an unfiltered logcat because not all useful lines will contain "error". Filtering for " AndroidRuntime" is usually enough, but it's safer to just upload the whole thing.
Anyway, please upload one when you can reproduce the issue. I see some errors related to secure storage in your log but I don't think that's related to anything.
jon3640 said:
All of my androids device using Xpose are force closing, well apps that are associated with it. Only fix I could find is older download..it seems the update had issues..
Click to expand...
Click to collapse
Well, if it is a problem with the framework, it won't be fixed unless you help out by posting a logcat.
GermainZ said:
I'm asking for an unfiltered logcat because not all useful lines will contain "error". Filtering for " AndroidRuntime" is usually enough, but it's safer to just upload the whole thing.
Anyway, please upload one when you can reproduce the issue. I see some errors related to secure storage in your log but I don't think that's related to anything.
Well, if it is a problem with the framework, it won't be fixed unless you help out by posting a logcat.
Click to expand...
Click to collapse
problem came back again for no reason, only 6 mods enabled and all have been stable for days... restart phone because i was getting a crazy mms wakelock in bbs. here's the logcat with the "unfortunately, context service has stopped" both from just automatically happening and i triggered it by having my girlfriend call me. i then disabled xposed, restarted and no problems, so i took a logcat of that to show how my phone runs normally in case you need it. let me know if you do and i will upload that as well.. if you can find anything in here i will greatly appreciate it. i can't even use xposed at this point, i'm worried i'm either damaging my phone or possibly missing calls/texts/notifications. thanks for your time in advance.
It's an ANR (Application Not Responding) error, so I'm guessing your phone kinda hangs for a bit before showing you the dialog?
It doesn't seem to be related to Xposed at all, though. It's Samsung's "Context service" (com.samsung.android.providers.context), so I'd personally try checking for a system update before anything else. You're likely to get more help in the S5 section (since the problem isn't related to Xposed), through it looks like no one else has this problem.
It hangs for a second, but those errors don't stop things I can see, just errors. I have to admit, I don't quite understand, if it's not related to Xposed, why would it only happen with certain modules enabled? That's why I assumed it was xpoaed related to begin with. Do I need to Odin back to stock? I don't want to damage my phone but I don't know anything about that error or if it could he damaging.. Sorry for the text wall. Thanks for being so helpful.
Sent from my SM-G900V using XDA Free mobile app
wrongway213 said:
It hangs for a second, but those errors don't stop things I can see, just errors. I have to admit, I don't quite understand, if it's not related to Xposed, why would it only happen with certain modules enabled?
Click to expand...
Click to collapse
Coincidence, I'd say. You'd probably get the same thing without Xposed, but as you've noticed it seems to happen semi-randomly, so chances are you weren't "lucky" enough.
wrongway213 said:
Do I need to Odin back to stock?
Click to expand...
Click to collapse
If you're using a custom ROM, you could also report this problem to the ROM dev with the logcat and ask him if his base is up to date or if there's anything he can do about it.
wrongway213 said:
I don't want to damage my phone but I don't know anything about that error or if it could he damaging..
Click to expand...
Click to collapse
It's mostly just annoying, there should be no permanent damage of any kind.
GermainZ said:
Coincidence, I'd say. You'd probably get the same thing without Xposed, but as you've noticed it seems to happen semi-randomly, so chances are you weren't "lucky" enough.
If you're using a custom ROM, you could also report this problem to the ROM dev with the logcat and ask him if his base is up to date or if there's anything he can do about it.
It's mostly just annoying, there should be no permanent damage of any kind.
Click to expand...
Click to collapse
could it be related to s health? i know this isn't the s5 forum, but i see under app info on s health there is a "com.samsung.android.providers.context.permission.WRITE_USE_APP_FEATURE_SURVEY".. i have heard people talk about having issues with s health and xposed. could that permission be the context service error i am getting, based on what you have seen in my logcat?
wrongway213 said:
could it be related to s health? i know this isn't the s5 forum, but i see under app info on s health there is a "com.samsung.android.providers.context.permission.WRITE_USE_APP_FEATURE_SURVEY".. i have heard people talk about having issues with s health and xposed. could that permission be the context service error i am getting, based on what you have seen in my logcat?
Click to expand...
Click to collapse
I didn't see anything related to S Health, but it might've related to the secure storage (though I'm not sure if that's a stock Samsung thing or if it's activated by the user).
Hi guys,
I have encountered massive sudden unresponsiveness about 3 times since I've got the phone and I'm trying to troubleshoot the problem.
The phone becomes very unresponsive with extreme lag and eventually after a long wait it reboots itself. I saw it twice on Nougat leaked beta and just today, on official OOS4.
On one occasion I encountered while it was charging in the car, and navigating. It was frustrating as GPS wasn't reliable. Phone felt warm too.
However, on other occasions, I was doing some simple tasks like browsing FB and the issue started. I highly doubt this is CPU throttling as I I've gotten the phone hotter before without any problems.
Now, is there any app which logs CPU resources in the background? Kinda like Windows task manager which tells you which app is hogging resources. I have Wakelock detector which is great, but the app using more batt is not necessarily the culprit.
So far, I replaced LightFlow with LED blinker and will monitor. Any ideas, feel free to share.
Thanks for reading!
MasK said:
Hi guys,
I have encountered massive sudden unresponsiveness about 3 times since I've got the phone and I'm trying to troubleshoot the problem.
The phone becomes very unresponsive with extreme lag and eventually after a long wait it reboots itself. I saw it twice on Nougat leaked beta and just today, on official OOS4.
On one occasion I encountered while it was charging in the car, and navigating. It was frustrating as GPS wasn't reliable. Phone felt warm too.
However, on other occasions, I was doing some simple tasks like browsing FB and the issue started. I highly doubt this is CPU throttling as I I've gotten the phone hotter before without any problems.
Now, is there any app which logs CPU resources in the background? Kinda like Windows task manager which tells you which app is hogging resources. I have Wakelock detector which is great, but the app using more batt is not necessarily the culprit.
So far, I replaced LightFlow with LED blinker and will monitor. Any ideas, feel free to share.
Thanks for reading!
Click to expand...
Click to collapse
if you saw these on Nougat leaked beta, its normal, because as the name says, its an old build, not the one that came out before EOY. On official build, its normal as well, being Beta 1 build. I`m using it too, and I encounter a lot of lag, small freezes , and things like there. These are going to be fixed, but we just need to simply wait for OnePlus to do their job. And I`m ok with this, since I`m also working in development branch and I know how their processes work
smilirulz said:
if you saw these on Nougat leaked beta, its normal, because as the name says, its an old build, not the one that came out before EOY. On official build, its normal as well, being Beta 1 build. I`m using it too, and I encounter a lot of lag, small freezes , and things like there. These are going to be fixed, but we just need to simply wait for OnePlus to do their job. And I`m ok with this, since I`m also working in development branch and I know how their processes work
Click to expand...
Click to collapse
Thanks. I've searched quite a bit for this issues but I couldnt find it. I felt that nobody else saw it. The occurrence might be low, but the problem is big. Phone becomes unusable for quite a substantial amount of time.
Lets see how it goes.
MasK said:
Thanks. I've searched quite a bit for this issues but I couldnt find it. I felt that nobody else saw it. The occurrence might be low, but the problem is big. Phone becomes unusable for quite a substantial amount of time.
Lets see how it goes.
Click to expand...
Click to collapse
Have you tried to reset to factory settings after update? That might help
smilirulz said:
Have you tried to reset to factory settings after update? That might help
Click to expand...
Click to collapse
I didn't feel the need for it, as all my installs were clean from scratch. So having this issue across at least 2 FW tells me that it's likely a rogue app causing this..
What about the stable version of Nougat here?
http://otafsc.h2os.com/patch/amazon...s3TOxygen_28_OTA_035_all_1612310259_2dc0c.zip
Link from this original thread: https://forum.xda-developers.com/oneplus-3t/how-to/zip-flashable-firmware-modem-t3509015
m0d hipp� said:
What about the stable version of Nougat here?
http://otafsc.h2os.com/patch/amazon...s3TOxygen_28_OTA_035_all_1612310259_2dc0c.zip
Link from this original thread: https://forum.xda-developers.com/oneplus-3t/how-to/zip-flashable-firmware-modem-t3509015
Click to expand...
Click to collapse
Yup.. I am using that right now. Saw the issue once so far.
Hard to say if it's a rogue app without knowing which apps you have installed
I'd recommend a factory reset since that's usually the first troubleshooting step. Try installing apps back slowly, and only the ones you absolutely need. I'm on the stable nougat build and haven't noticed that happen with me yet.
Hello,
Tried all 7.x ROMs - and I am struggling with instagram videos are very choppy (the snapchat style ones) as well as camera crashes or buffer gets full.
Tried a number of kernels too
Any advice on how to fix that?
cheers
Stop using Instagram?
Seriously, you don't give enough information for anyone to really help you. For example, you mentioned trying all Android 7.x ROMs. Did you try going back to a stock ROM as well? Did you actually search the forum to see if other people have had the same issue? Did you provide a logcat so someone on XDA could attempt to troubleshoot the issue?
Gut instinct is telling me you have a hardware problem, i.e. a failing camera. Your first thing is get yourself back to a stock ROM and see if the problem occurs there. From there, you need to see if others have the same issue, and then you need to post a logcat.
Thank you. Will start from that
Thanks for a long reply
Strephon Alkhalikoi said:
Stop using Instagram?
Seriously, you don't give enough information for anyone to really help you. For example, you mentioned trying all Android 7.x ROMs. Did you try going back to a stock ROM as well? Did you actually search the forum to see if other people have had the same issue? Did you provide a logcat so someone on XDA could attempt to troubleshoot the issue?
Gut instinct is telling me you have a hardware problem, i.e. a failing camera. Your first thing is get yourself back to a stock ROM and see if the problem occurs there. From there, you need to see if others have the same issue, and then you need to post a logcat.
Click to expand...
Click to collapse