Finally figured this out and it helped a couple people in the trupure thread so i figured I'd share it here in case anyone else is annoyed by this as well.
Apparently when the power and volume up buttons are pushed together, it creates a bug report and notification. Another user (forgot your username) pointed out that it also removes the reboot menu in the power menu (if you have it enabled through gravity box) until you restart the phone.
To fix this, I froze the app "com.Motorola.Bug2go" in titanium backup, and I had also renamed the bug2go and bug report files in /system/bin to include ".Bak" at the end, which I'm not sure if that is necessary or not since right after I did that I froze that app in titanium backup. There are also bug2go files in system/etc
Since doing this I havent had a single bug report pop up (basically every time I took my phone out of my pocket) and my reboot menu finally stays. So if these reports bug you too p) try this and hopefully it helps
Related
I have a problem with titanium back up when I go to the backup and restore tab none of my apps populate in the list. I've used this app before on another hero and it worked fine. I just reinstalled busy box and can't figure out how to make a backup of my apps.
So you already tried clicking the "Problems?" button and having it redownload the busybox executables? I had this same problem, and doing that fixed the problem.
Otherwise, the developer of the app is *really* responsive. I've emailed him and he's gotten back to me within hours, so you might want to give him a shout and see if he has any ideas.
thanks...that helped me out
You know how when you first set up the phone, let's you swipe up on the lockscreen to start right away, or down to "tune a few things first?" Well my phone repeatedly keeps doing that any time the lockscreen comes up, like whenever I turn it on or when the phone sort of crashes. When it happens, I have to wait for No Lock to disable the screen again, because if I use either option, the animation freezes half way through the unlocking and the phone crashes, going to a black screen and I have to turn it off to get it to work.
I thought it might be due to system apps I froze with bloat freezer, so I unfroze them one by one and did resets, to see if that solved it. I did this until everything was unfrozen, to no avail. I thought maybe it was due to a glitch in the extended controls widget I used to disable the lock screen, so I switchedto no lock; same problem. I don't knowb what else to do. Any ideas?
God I hate samsung and their glitch riddled android hacks. They improve literally nothing from stock android, its just glitchy hacks and downgrades.*prays for the next nexus to have a hard keyboard.*
Just fixed the same issue with my sk4g. I tried installing with terminal and various install apps, no dice. There is a workaround until you get the apks back in place. Turn on the pattern lock and set it. When the curtain lock comes up DO NOT SLIDE IT, just open the screen and the pattern lock should pop up. First install Systemapp Remover, if not done already. Download the dump in development section and pull the apks from the app folder. The two apks causing the error are PhoneSetupWizard.apk and Learn.apk(maybe not learn but i did both to be sure also copy/paste the .odex files). Make sure neither can be seen in the system app list in Systemapp remover, if they are there uninstall them. Take the apks from the dump and copy/paste them to SysteAppBackup folder on the sdcard. Go to the restore menu in Systemapp remover and tap to restore each apk. Reboot and all should be well. Thanks to the kind people of xda for this, not me.
edit>>> Run the setup wizard and uncheck the data options to stop maps from running all the time for no reason.
Ok, i've been modding and playing with my LG Optimus Black P-970 lately, and it's been working pretty nicely. But today it started being unstabile, and weird. Examples, often when scroll around menus etc, i see a black rectangle i would guess is about 5x10 px in size, lined up in the left side of the screen. Lots of apps act weird and stops responding. If i tru to unlock after a while in standby, the screen freezes on what looks like a untuned analog tv channel, just with some colors in it. So what might have caused it?
What i have done tody, is to:
1. Updated GO Launcher EX
2. Download BusyBox, and apply the newest update it offered
3. Update the su-binary in superuser.
4. Lastly, which i suspect, i pulled Phone.apk, replaced a few background pictures in it (New ones is same resolution, but different type, from RGB to Monochrome), and pushed it back in.
Now i got problems, so i did this without any results so far:
- I've replaced GO Launcer EX with ADW.
- Removed some widgets i made with Chronotopia.
- Uninstalled BusyBox (But probably not the updates it applied to my system).
Any experiences/knowledge with these kind of problems? I do suspect the Phone.apk and the updated BusyBox...
EDIT: I managed to get a screenshot of that block dot that keeps appearing on the left side. For some reason, it appears as white in the screenshot. w00t? Dunno if it's relevant.
I would change phone.apk back to stock just to see if that helps. I kind of doubt it had to do with busy box. Good luck!
That was my idea, and i thought i had Phone.apk laying around, but no So i tried something stupid and ended up bricking the phone again, lol. So now i'm back to stock, rooted it and did a backup Updated BusyBox, Superuser and su-binary. Seems good so far, haven't done anything else. I'm gonna be so sad if i find out that i can't change a few png's in Phone.apk without stability problems. I didn't sign the modified Phone.apk before i pushed it back, may that be the problem?
I suppose it could be. Try your change again & see what happens.
Ok, last time i ended up doing a full LG recovery, and just a little tweaking. Yesterday, i made a backup, then started to heavily modify the framework-res.apk, and i got the same problem once again. This time i didn't even touch any other apk's. So now, barely awake, lol, i tried removing the old files and replace them with stock in drawable-hdpi folder, and push it back. Still the same. Tried to push the stock untouched framework-res.apk, still the same. Tried to recover to the backup i made, and still the same. What bothers is that i bypass an error message saying "ERROR, LG Security Team !" on every boot.
So i tried another, bit old backup, and this one works fine. But these problems i mentioned has not been showing between those two backups. I just had to try to restore the backup i made yesterday once more, and still it's buggy. I just can't make any sens out of that...
Hoping someone can help out with solving a persistent CMUpdater download notification. I mentioned this in the CM main thread (here), but despite some helpful suggestions, no solution was found. Rather than hijacking that thread, thought I'd do a separate thread here.
The problem is this (kind of a summary from the above linked thread):
I've been using CM nighties for a long time now. Originally I downloaded from the "get.cm" site, moved onto phone through USB, and flashed either in ClockWork app or via recovery. About two months ago I started using the CMUpdater from System Settings --> About Phone --> Updates. Seemed just fine for a while. A couple of weeks ago I tried to download one of the nightlies, the usual notification down arrow thing showed up, but it never started the download. A bit like when the connection is not yet made, just the blue line flashing across, but no % download made. I tried to close the app, reboot, but the download notification arrow stills runs, with the blue line flashing. I even downloaded more recent nightlies, flashed them successfully, but after rebooting into the new nightly, the notification is still going. Have cleared the cache, force closed, deleted data for apps -- no fix. Deleted the CMUpdater folder -- no fix. Can't find the file in ES explorer either - as noted above, it doesn't actually start the download, just the sort of connect to download server part with the fast blue line racing across the screen (not the slow blue line with the % for progress). Removed the daily update checker to manual, and no go either. And all this with both Titanium and regular App Manager. Have also tried various backup type remedies, including a whole Nandroid backup and restore. It just keeps reappearing!
It isn't really causing much of a big problem, doesn't seem to be excessively draining the battery or anything, but obviously it shouldn't be doing this.
Any solutions? Thanks in advance.
<Bump>
Anything?
Prajnacara said:
<Bump>
Anything?
Click to expand...
Click to collapse
found a solution! Swype down to see the download notification, press and hold on it. You'll get a menu for App Info. Select it and it'll take you to Download Manager app info. Clear data and Force stop. Voilá!
Brilliant! Actually worked, and simple too. Thank you, much appreciated.
Sent from my CM10 Nexus S via XDA App
Got my OPO yesterday, very happy with it, rooted and got Xposed in the first 20 minutes after updating as I have with all my Android devices. Unfortunately I noticed a few problems today.
File manager won't let me move, copy, or create files. It seems to be fine with deleting, but trying any of the former yields a "Requires elevated permission (root)" despite the fact that I have already set File Manager to rooted mode and granted it permission in SuperSU. Other file managers yield the same result.
I can't take screenshots, or let other apps take screenshots. Stock screenshot will give me a notification saying "Couldn't save, storage in use."
Similarly, Snapchat and Keepchat won't let me save my own or others' snaps.
I can restore Helium backups, but I can't create a backup. Made sure Helium has the proper permissions too.
I'm pretty sure this isn't app-related or root-related, but rather something preventing me from writing to /storage/emulated/legacy.
Things I've tried (to no avail):
Fixing permissions in TWRP
Unrooting
Uninstalling Xposed
Factory resetting
Searching for a fix on XDA and the OPO forums, all of which have led me to try the former three solutions which failed.
Also completely unrelated, but sometimes pressing the lock button won't wake my device; the hardware buttons glow as if the device is on, but nothing happens after that and the device won't wake up so I have to reboot. This is a somewhat rare problem however.
Any ideas for either problem? Thanks in advance.