Database Info

Weird behavior on rooted ChaCha?

Thanks mostly to this forum I successfully rooted my HTC Status (the AT&T version of the ChaCha) and was able to finally remove some bloatware via Titanium Backup. (The internal storage had been so full it wouldn't even download Facebook or Calendar updates and couldn't update Marketplace apps.)
Anyway, I'm super stoked that this is taken care of, but I've discovered a few odd things about the phone post-root, and I'm wondering if there's any way to fix these issues:
Keyboard layout slightly different. I'm a USA AT&T customer, and I have US English selected in the phone settings, but the keyboard layout is different now. When I press the @ key, the phone shows the British Pound symbol. When I press the .com key, the phone enters camera mode.
When I plug the phone in to charge, I just get a black screen and the LED is always orange. It used to show an animation with a battery and indicate how far charging is complete. It DOES still charge the battery, but the visual feedback's definitely broken. The LED never changes to green, even when the phone's completely charged.
If I turn off the phone and then plug it into a PC for a charge, I cannot power the phone back on without pulling out the battery first. (And if you own a ChaCha, you probably know it's not very fun to get the battery cover off this phone.) I can live with the other issues, but this is really bizarre and a bit of a pain. Anyone know why this is happening and whether there's anything that can be done about it? I have tried different computers (one with the Android SDK/drivers, one without) and see the same behavior. Also, I have disabled the "USB Debugging" option on the phone, and the default USB Connection method is "Charge Only."

1. Common issue. Just look around for a thread containing flashable keyboard files. Mikevhl or iDarek posted one I think.
2. Might have been that you have removed something which displayed that (bloatware specific)
3. I've seen the exact same thing on my phone. It gets stuck in some sort of charging state; can't figure out what's wrong (didn't checked it that much either). It seems to be S-OFF related only..

Alex C. said:
1. Common issue. Just look around for a thread containing flashable keyboard files. Mikevhl or iDarek posted one I think.
2. Might have been that you have removed something which displayed that (bloatware specific)
3. I've seen the exact same thing on my phone. It gets stuck in some sort of charging state; can't figure out what's wrong (didn't checked it that much either). It seems to be S-OFF related only..
Click to expand...
Click to collapse
I will search for the keyboard files. Thanks!
The items I've removed with Titanium Backup are: AT&T Family, FM Radio, HTC Likes, Live TV, Quick Lookup, Shop Music, Transfer, Voice Dialer, Voice Search, and YP.
I may try restoring individual apps to see if one of them was somehow linked to the charging anims.

If you find out how to resolve the keyboard issue on the status, let me know. I've tried all the flashable zips as well as pulling the files directly from a temprooted S-On Status and none of them fully resolve the issue. It still retains the EU english layout regardless. I'm not sure people realize that the actual keyboard layout differs significantly from the english layout of the European Chacha model. To further compound things, I've diffed the .kl and kcm files between the chacha and the status and they're identical, which leaves me scratching my head. Any help would be greatly appreciated.

My phone did that freeze charging orange light thing before I s off'd...
Sent from my ChaCha using Tapatalk

So it's a phone issue then...

Sometimes fails to boot/backlight kind of working - need technical help

Hey there, I have kind of trouble with my PQ.
The PQ sometimes fails to boot correctly.
Booting the PQ results in a short (a few seconds) backlight and then dark. (Important: No picture or text is shown!)
Then there are two errors I've experienced so far:
- after the backlight is dark, I press a button (POWER/VOL_UP-DOWN/CAMERA) and it vibrates. After a few times of pressing and vibrating, it vibrates long and it then seems to be off. Since the backlight is off, I can't know if it's really off.
- after the backlight is dark, I do nothing except sliding out the keyboard (backlight is off). In this error it seems to start "correctly", because after some time the keyboard backlight goes on. That means, that "android" has bootet and is waiting for password entry (because of encrypted phone).
Either way, I have to reboot several times until it boots correctly. (With some luck it takes only 2-3 times.)
Some notes:
- I have to put my sdcard off, because the password entry doesn't appear if it's in. (ext4 filesystem, android seems to want to decrypt that -.-)
- [needs more testing] The phone has had force resets. I think it was my Access Point/Router, causing the WLAN (or qualcomm SoC) to hang. I changed the screen-part (touchscreen+display etc.), seems not to help. (I also disabled that Access Point/router, so I'm still waiting for a force reset.)
- [needs more testing] Sometimes the SIM-card and/or sdcard is not recognized after a reboot/cold boot. I have to reboot to get it back to work. SIM-card recognition may take more than one reboot.
What's in /system?
- CM11 M11 snapshot
- gapps
- XPosed framework (it boots and everything actually works fine)
...if I forgot anything, I will notice that in a later post or edit this and notice in a new post.
I also have a problem with wakeups again (started just a few days ago, after uninstalling two apps...). That's weird, but I can't find the cause. Neither in the XPosed Logs nor in catlog. I need to investigate it further.
I tried to be very exact and I've put anything that might be relevant into this post.
If you have any ideas (no matter how implausibly they are), post them. I am out of any ideas.
It might be helpful to get a log when it boots "incorrect", but I'm sure it's not written anywhere inside the system.

The good thing is, my wakelock problem "disappeared".
The PQ is having deep sleep again.
I have no idea what the wakelock caused...
No force reboot so far.

Another good thing: the force reboots are gone after disabling the AP/router which probably was the cause.
A stable week for me, the phone didn't crash at all.
Of course the other issues stays.
Saturdays (today) the phone is being rebooted by Titanium Backup. Like a wonder, the phone chose to show the password input (encrypted phone; with sdcard inserted).
After entering the password and some boot-time, the mobile part (SIM-card etc.) chose not to work.
A reboot didn't help and I've got into the annoying problem, that I get a blank black screen with backlight but it boots "normally" (without anything displayed).
It took about 20-30 minutes with trial and error on getting it up with the mobile part again.
BUT: I've found today something new, beside the issue this morning.
Bluetooth seems to be enabled always! It's probably caused by Llama (android app).
Needs also further testing, just wanted to write that somewhere down, so I don't forget.
More details: After disabling it, my "PS3 headset" wanted to pair with "all" devices nearby.
I got pairing messages on the PQ even with disabled BT.

Loader009 said:
Another good thing: the force reboots are gone after disabling the AP/router which probably was the cause.
Click to expand...
Click to collapse
(If anyone cares) the force reboots are gone after setting preamble to "long" (PQ malfunctioning if set to "short") in the router.
The other problem persists but are not that bad because it happens rarely that I need to reboot (soft reboot is mostly enough).

[SOLVED] Limited functionality

This thread was originally titled "System wide problems", please see the reply for the solution.
Original post:
"Hi all,
Been forever since I've made a post to XDA, but I have a problem I'm not able to solve without taking an inconvenient plunge. I should mention that my phone was 100% fine yesterday evening, but since I was asleep last night it seems to have run out of battery, so this morning I charged it a bit, then I turned it on to a world of problems.
Ok, so let me run through a list of just a handful of the problems I'm having right now...
Totally stock (not rooted) Nexus 5 running Android 6.0.1 (Security: 1 March 2016)
1. Home and App switch soft keys don't work
2. Notifcations are not working at all
3. Notification shade wont pull down
4. Widgets cannot, and will not load
5. Cannot get into Developer options "Developer options are not available for this user"
Seems I'm not the only one to experience the strange bug, some folks over at Android Central were experiencing the exact same thing toward the end of last year.
http://forums.androidcentral.com/an...me-button-not-working-many-more-problems.html
Some people to have resolved this issue using "adb shell am start -n com.google.android.setupwizard/.SetupWizardTestActivity" but I cannot get into Developer options to turn on USB Debugging (unless I don't need to?)
What I've tried already...
1. Cleared all Google App data "CLEAR ALL DATA"
2. Tried to make another user, just flashes and goes back to "Opula" my main and broken user profile, never creates the other profile, same thing happens when I press on Guest too
3. Safe mode, but the problem persists there too
4. Virus scan, turned up a whole lot of nothing
I'm now at the point where I'm thinking I'm going to have to do a Factory data reset (the "inconvenient plunge"), even though I think I've backed everything up the "Touch to sync" option on my Account > Google doesn't do anything, neither does the "Sync now" from the drop down menu. So despite having explored my Google account on my desktop I cannot see if it has backed up my Apps and App data, but it seems to have backed up my contacts and such.
I'm going to get a third party app to back up as stuff as I possibly can as well, but even Helium is useless now since I cannot get into the Developer options so enable USB debugging.
Anyone got any experience with this issue or how to resolve it?
Many thanks to everyone in advance."

Hi all,
Just wanted to update this thread to say that I did a factory reset and the phone is now fixed, but I wouldn't to give a more comprehensive account of the problems I was experiencing with the phone until I did the factory reset.
List of problems
Home and app-switch soft keys not working (back key is working)
Google Now 'on tap' not appearing (cause of home key)
Cannot see notifications just says "No notifications" (but the light and sound work fine when a notification is received)
Cannot pull down notification shade to toggle controls
Widgets cannot be added and will not load
Cannot pull down the immersive mode overlay
Google Backup not working (after 8+ days)
All types of syncing not working
Phone's storage doesn't appear on PC when plugged in via USB
Cannot access developer options (due to active profile level)
Cannot create or switch users
The best advice I can give to mitigate such an unusual problem (that appeared totally out of the blue on a cold boot) is use Google Backup services, keep on top of syncing, and manage your data via your Google account! Or as an alternative, manage and maintain manual backups.

Keep apps running in background?

I am still having trouble running apps in the background. Specially WhatsApp. I've disabled many evenwell apps and duraspeed using adb commands but not working. I am on the latest release of PIE. Is there a definitive guide to make this phone multitask?

Did you already try the instructions at dontkillmyapp.com?
I tried everything, and I haven't still got the Screentime app to work. Something keeps closing it when the phone is on battery and screen off. If the phone is charging over the night, the app stays in the background as it should. Also if the screen is on, there is no problems. An app like Screentime is quite useless if something keeps killing it all the time.
Quite annoying, as I selected Nokia because of Nokia having close to stock Android.

k701 said:
Did you already try the instructions at dontkillmyapp.com?
I tried everything, and I haven't still got the Screentime app to work. Something keeps closing it when the phone is on battery and screen off. If the phone is charging over the night, the app stays in the background as it should. Also if the screen is on, there is no problems. An app like Screentime is quite useless if something keeps killing it all the time.
Quite annoying, as I selected Nokia because of Nokia having close to stock Android.
Click to expand...
Click to collapse
Well... I have managed to (somewhat) solve the issue with keeping the apps running on the background, so I'll share which my experience was, so you can check through it and see if it fits your needs and/or it helps you.
IT MUST BE NOTICED that some of the described stuff is because my personal needs, but nonetheless it can bring some ideas about what could work for you (or anyone else).
First of all, according to a discussion here on XDA there are a couple of evenwell apps that can be disabled and/or deleted from the device. I found that thread a little too late after I've done some of the following steps, but I wanted to point it out just in case you can find something useful.
So, as we have learn on https://dontkillmyapp.com/nokia (DKMA) there are two probable culprits regarding the killing of the apps:
The Powersave App
The Duraspeed process/daemon
Powersave/Evenwell Apps
For this ones I followed the given instructions on the DKMA page to no avail, as they worked only for a certain time and then the background processes started to get killed after a while.
So, after digging on the Nokia Forums I found this discussion and specifically this comment where an user when full ballistic and created a one-line script to delete/uninstall all evenwell applications (this needs to be run on the ADB shell). I must add that after some "trial-error" loops I noticed that sometimes there were some background processes running, so I done the following:
This is for doing a Force Stop to every Evenwell process. I would suggest to running it a couple of times, just in case there are some processes that refuse to be stopped:
for crap in $(pm list packages | grep even | cut -d ":" -f2) ; do am force-stop $crap; done
This is for Disabling every Evenwell process for the current user. Same additional suggestion as above:
for crap in $(pm list packages | grep even | cut -d ":" -f2) ; do pm disable-user $crap; done
This is for Uninstalling every Evenwell process. Same suggestion as above. Please note that this uninstalls the apps ONLY for the current user, that means, only for you (hence the [--user 0] parameter). As rooting is not possible yet, is not possible to get rid of these apps at system level:
for crap in $(pm list packages | grep even | cut -d ":" -f2) ; do pm uninstall --user 0 $crap; done
What those commands do is, first get all the packages that have "even" on their name (you can go and use the full name "evenwell", I left it as it is because I performed this steps after a factory reset), and for each one of them it performs the indicated operation (disabling, force stopping, uninstalling).
After that, I read somewhere else (can't recall exactly were) that it could be useful to clear the cache of Google Services and Google Play Store, and reboot the device afterwards.
Those steps solved most of the issues, as now the applications weren't killed after the screen goes black, or the device is idle. But, after a couple of hours (~3 hours) I still had some issues as the processes were still being killed, so that's when I went to the next item.
Duraspeed
As we know, this is a major annoyance as this thing (service/daemon) is impossible to uninstall, and it's very annoying to disable. What was most annoying is that my device (TA-1074) it wasn't listed on DKMA as a device having that thing, but it seemed that I had it.
So, this is where the fun starts, because although the instructions posted on DKMA works, it seems (basically) that it only works on the current session of the device, meaning that if the device was rebooted the operation was needed to be performed again. There's a discussion on Github where this is explained more lengthy and in more detail.
To add more fun to the mix, it seems that even if the setting was disabled, the Duraspeed service ignores the current value of that setting while booting the system, only taking notice of it when the value changed, meaning that we need to change the value to something else, and then setting it again to 0 (zero) in order to make a successful disabling of Duraspeed. There's no need to say that doing that on every reboot is a PIA.
Any way, on the thread some users suggested using some automation applications (like Tasker or Macrodroid), but not before granting some permissions to the automation apps, similar to what the guys of Syncthing-Android (fork) suggested (just changing the package name, of course).
But, for me here's the catch: none of the automation apps worked for me. It could be for several reasons, because I needed to setup some other things that I need to run at startup, but, well, YMMV.
Anyway, it seems that the developer of Syncthing-Android has added a routine to its application that makes the change of the setting and therefore disabling the Duraspeed service and that such change is live on production, and I can say that it works as intended.
---
After doing all of that, I was able keep the background apps alive doesn't matter if I rebooted my phone or not.
I hope that this could be of any help.
Kind regards.

Quick question
Thank you for the awesome write-up.
So, just to make sure: is the Syncthing-Fork the solution? I tried the DuraSpeed/MacroDroid/Evenwell route, but Whatsapp and IFTTT still refuse to cooperate.
Please advise.

Hi!
Well... To be honest, as far as I've seen, the thing that is causing most (if not all) of the issue is the DuraSpeed daemon/service, and in my particular use case, the only thing that worked is how Syncthing handles the "workaround". Let me explain...
It seems that DuraSpeed is controlled by a global setting named setting.duraspeed.enabled, and as weirdly as it sounds, it seems is that the value of that setting its taken into account when its changed and not during system boot. On other words, if we configure the value of the setting to 0 (zero), and we reboot the phone, although the value is persistent (I mean, it is not changed during the reboot/shutdown), DuraSpeed tend to ignore during the startup and will work as "designed" (that is, going in a killing spree from time to time) and giving us all the issues that we are aware of. As DuraSpeed will take into account the value of the setting only when it's changed, what is needed to do is to change the 0 to another value (let's say 1), and then changed again to 0 in order to be disabled.
Also, there's a funny thing about DuraSpeed: it seems that DuraSpeed start killing processes almost since the startup process, and not only after all the OS/UI has been loaded/is ready... What is frustrating enough, as it kills some processes just before we can use them.
So, according to what I've seen on some captured catlogs, is that Syncthing makes that change during startup, and not after the OS/UI has been loaded. I don't know how they do that (I have not taken a look into the codebase), but according to what I have read on the logs, the change is made on the early steps of the startup, just before any damage could be done.
So, my guessing is that, perhaps the Automation applications (Tasker, Macrodroid) are being killed before they can make any change into the setting, and DuraSpeed do all its nasty things.
By the way... Did you grant to the app that you're using, the ability to write to the settings store (using ADB)? The procedure that I am referring to is the one that is described on this response on Urbandroid's GitHub thread. I ask because I forgot to do that after the factory reset and was having the "DuraSpeed issues".
If you haven't, it could be that it's the only missing thing on your setup, and that probably it will solve the issue for you. If you already have done that, I'm guessing that you're on the same boat as I, and those applications are not able to perform the workaround.
Other thing (that I can think of) to check is the "Battery Optimization" setting. This is located on "Settings -> Apps & Notifications -> Advanced -> Special App Access -> Battery optimization". There you can configure if an application will be optimized or not, by clicking/pressing on an application and selecting "Don't optimize"/"Optimize" (according to your needs). It will probably be less severe as DuraSpeed, but I've configured some apps there too, just in case.
I hope this is useful for you.
Kind regards.

Thank you for the very detailed response - greatly appreciated.
I have done all of the above, I even reached out to the maker of Syncthing-Fork who took the time to write back almost immediately with additional help.
So far - WhatsApp is still dead. Unless the phone is being charged or the screen is on, messages and voice calls do not work (the other thing that wakes it is an incoming cell phone call or a cell text message). Similarly - IFTTT: I have yet to get it to trigger anything when the screen is off.
I use MacroDroid to perform the DuraSpeed value change at boot time and I had granted it the required permissions - exactly as described on the forums that you reference. Not sure what else to try.
I now see why some comments on DKMA call Nokia phones "dumbphones" - the phone and texts are the only things that work consistently.
Anyway, thank you again for taking the time to reply.

Hi there!
Well, I can't deny that it's a downer that your device is refusing to cooperate and just work as you, the owner/user, are expecting it and not how the developers/makers thought it should work...
The only last thing that I can think of is a little bit of an overkill, and it is making a factory reset, and perform any/all of the suggested steps (by DKMA, catfriend1, myself, etc) before installing anything else (besides, perhaps, the automation app)... Just in case that something else is interfering with the workarounds, and to have a "blank state" to start to work... As I stated before, I think that it's an overkill, specially because all that implies doing that (backups, mainly), but well... I can't think about anything else.
I now see why some comments on DKMA call Nokia phones "dumbphones" - the phone and texts are the only things that work consistently.
Click to expand...
Click to collapse
Yeah, I fully agree with you, although the specs (for a budget phone in my case) aren't so bad, all the battery customization (and bloatware) just sucks... To say the least.
I hope that you can find a solution for your issues, or at least a device that doesn't let you down as Nokia does...
Kind regards!

Still no luck
Did the factory reset, installed Macrodroid, gave it the required permissions. Disabled the evenwell packages that have also been identified as culprits. Checked duraspeed status via adb - it is disabled.
No luck. Dumbphone it is.
The annoying part? I have a nexus 4 and a nexus 5 with just as little ram and likely an inferior processor. Both phones work great (albeit really slow, not to mention the battery life). I feel the principle "don't fix it unless it is broken" applies here...

Issues with the Android Pie Update (Google Play Store and Camera -> Gallery App)

Hello everyone!
Today I updated my HTC U12 + (128GB) to the Android Pie version (9.0):
First I received an update of approximately 350 MB, which was downloaded and installed without any problem, the cell phone restarted without any problems (I clarify that my cell phone is encrypted and when it restarts, ask for a password to continue with the restart). For now everything is going well.
After a while the main update was downloaded (950 MB approx) and I had it installed as soon as the download was finished.
Again the cell phone restarted, he asked me for the password to decrypt it, but after that, it went completely black, he did not advance anything else for several minutes. Amid the panic, fear and despair, I pressed the power button to restart the cell phone, asked for the password again, and apparently charged the rest of the installation.
When I went to use the Camera application, the option thath appears in the lower right corner to see the last photos taken (like a gallery) is not working well, the application crashes and is not letting me see the photos taken. (Here goes the first problem).
Another problem I have is with the Google Play Store app: It doesn't allow me to download apps from the store, as if it were locked or something like that. (Here goes the second problem).
Now, the main problem is: Like any good engineer, any problem can be solved with a reboot to see if everything loads well, but I already tried and it didn't work. And following the good traditions of the good engineer, it can be said that I do a hard reset (erasing all the settings and content of the cell phone, which I also consider an effective solution, I will not deny it), but currently I am outside the country where I have hired My phone number, and for work I need WhatsApp (and as you know, I need a text message with the code to login), and I have no way to activate Roamming.
Can anyone help this good citizen with any advice, trick, recommendation or magic spell that does not involve formatting the phone and solving these problems?
Thanks!
PD: A friend with the "same" model (64GB) had no issues with the instalation, and we compared the camera version number, and everythings is the same.

Delete camera and gallery data in settings and reboot. If that don't work do a factory reset... Sometimes after an update it is necessary to delete old caches that get stuck

dioggo92 said:
Delete camera and gallery data in settings and reboot. If that don't work do a factory reset... Sometimes after an update it is necessary to delete old caches that get stuck
Click to expand...
Click to collapse
I have already deleted the cache of the applications with problems, but it still does not work properly.
Thanks for your answer and support with this.
(Until I can return to my country, I cannot do the hard reset... sadly)

no issues here since yesterday evening
So far it's great, very smooth, phone (64GB blue on TMO US w/ 128GB SD) is faster & battery life seems to have improved a lot though it's only 1PM here so we will see...
Upgrade went the same way like yours except I waited patiently to come back from the "blackout" after the decryption was done, thanks for the heads-up (though I usually wait a while anyway.)
UI is a tad more responsive - I have a lot running on my phone, I use it heavily for business all day long.
I like the clock's new location in the upper left corner actually more than the previous one - however the new UI design is a too bubbly and too colorful, too 'pop' for my taste, the previous one was far more elegant, I think. I will give it some time, see if I get used to it - if not I will just look up some more subtle theme.
I only had to re-apply my notification sound setting, everything else was kept intact so it's all good.
All in all I'm satisfied so far, very smooth upgrade - it did worth the wait, thank you HTC!