yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] Lzortin:
Please, take a look on this below:

First of all, thanks again, your attention has been a important support​

Was great, I installed Kingo Root and now is rooted, but without bugs. Then, I installed SuperSU, BusyBox, Titanuim Backup, ROM Manager, Flashify, Liveboot and TWRP Manager, the Free versions.

The “ROM Manager App” (with the Black Hat icon) which I’ll need have some of this kind of app from now ahead, it have some Sansung Galaxy S5 models and have two S6 also , listed as supported, but none of the models Galaxy A3, A5, A7 and A8.

Once installed, in order to make the download from it own server, of a “ClockworkMOD Recovery” or of “TWRP”, it asked me to choose one of these two app, I chose the last one.

So, when it suppose to started the download, at same time asked me to inform my cell model from that list. As I didn’t found, I did not choose any of them, so it failed the download and the main app didn’t run.

SuperSu is running well, limited as free versions are, but ok. And are making the log of the Busybox calls and all the others root applications. (only these above mentioned app I meant)

The Titanium, despite it is not a paid Donation version, is limited, I just made the Backup App & System App, the full one, but not to SD Card, once I use the hybrid nano chip rom with no memory card, but with a cell nano chip, using the Duos capacity, of the device. So it saved in a backup file from the own Titanium Backup.

I have been reading and studying during my free time, looking to learn how use this advanced capacities from a rooted smartphone, but yet a “sailor from first trip” with a lot to learn from now ahead.

So, I also have read about install a custom ROM’s, like a Cyanogen ROM that can speed up the processor capacity, and make the device more fast and things like that.

Thus, what a “ROM Manager app”, one with a onboard download capacity of a “ClockworkMOD Recovery app” or “TWRP app”, that you may recommend to my device?

On timely, what is the custom Cyanogen ROM firmware, reliable, that I may install, in order to replace the Android Kitkat 4.4.4, optimizing the A5 entirely?

Better, firstly what you say about Cyanogen ROM to the Galaxy A5?

Much thanks in advance.

​
[Nook Touch General] nmyshkin:
SOLVED!!!! See post #25.
[Nook Touch General] :
I am going to test this, for sure. If it indeed works, which I am very confident it will, you're going on the Important Links list. :)
[Nook Touch General] :
Tested it, multiple times. Your steps did not work for me.

What does work, though, is this:

- Plug in OTG cable, set in Host mode.

- Plug in audio device.

- Open AudioCtl. Hit "Beep".

- Unplug audio device.

- Open ES Task Manager. Open Volume.

- Set "Media" meter to whatever you like.

- Plug audio device back in.

- Open AudioCtl. Hit "Beep".

Good to go.
[Nook Touch General] nmyshkin:
Trying to track down volume adjustment

I've been thinking about the volume adjustment as described above and wondering if it could not be examined to reveal what is going on behind the scenes with a view to incorporating those changes into either Renate's AudioCTRL app or my one-touch USB Audio app--or both. My Android knowledge is, however, very basic.

I've attached a logcat session (including everything...) which begins with the usual sequence for enabling USB audio on a freshly booted NST. There's a lot to wade through, much of it irrelevant--even I can tell that. The beginning of the actual volume adjustment operation can be found by text searching for "Removed device", which is where the USB Audio gizmo is disconnected from the OTG cable while Task Manager is used to adjust the volume (as described in the post above). The logcat ends with the disconnection of the OTG cable and termination of USB host mode.

I've begun looking over this in hopes of seeing something that indicates what is different when AudioCTRL is invoked the second time to see if the volume is indeed no longer ear-splitting. Maybe there is something there, and maybe there is a better log to look at.

Any suggestions/help/joiners?
[Nook Touch General] digixmax:
Have you made any more progress on this volume adjustment problem?

The ES Task Manager's volume setting doesn't do anything more than what I can do with the hardware volume control on the USB Audio adapter.

My solution at the moment is to use some low-efficiency earbuds/headphones.
[Nook Touch General] nmyshkin:
Unfortunately it seems beyond my skill and no one else seemed interested in tackling it. This leads me to believe that either not many people use the audio capability (maybe for this reason?!) or they just found other methods that "worked" for them. In searching for something--anything--that would make the volume other than full on I thought I had the solution several times and that suggests to me--along with your experience with ESTM--that the behavior is almost device idiosyncratic. That's a scary thought.

That said, I hope you'll give the ESTM another try. It works wonderfully well for me and provides full range volume control from a whisper to blasting using the native android controls as well as external buttons. I have two USB audio devices, one with volume buttons and one without. Both work equally well with this method, but you do have to follow the procedure exactly:

1. Set up your USB audio device in the usual way, using Renate's two apps (you can also use my one-touch app--must be version 3--to set the volume this way).

2. Remove the USB audio device from the cable (do not detach the OTG cable from the NST)

3. Open ESTM and access only the quick menu (three bars at the top left)

4. Select volume adjust.

5. Adjust only the media volume to something on the order of 60%--don't diddle with this. One adjustment. If you do too much you can cause a reboot.

6. Close ESTM

7. Reattach the USB audio device.

You should be good to go at that point until your next cold or warm boot and unless you're working on your system, that can be a very long time with the Nook ST! It doesn't matter that you get in and out of USB mode. Something in that hoo-doo process sets a flag or pushes an unruly gaggle of electrons around in the system so that the volume control works as it should. I only wish I knew what it was!

Just in case, the version of ESTM I am using is 1.4.2 (attached below).
[Nook Touch General] digixmax:
That did the trick!!!

I think I had previously skipped the step of removing the US Audio adapter ...

Can you post the link to your one-touch app?

Tx.
[Nook Touch General] nmyshkin:
Good! I hate kludges, but this one does actually work :)

Here's the one-touch app.
[Nook Touch General] digixmax:
Thanks.

Now, if your one-touch app can finagle the volume control I'd be in heaven and go stocking up a few more NSTs :)
[Nook Touch General] nmyshkin:
Amen to that, brother--from your fingertips to the terminal screens of those who can do it. It's the last piece of the audio puzzle and it would be a shame not to complete the work.
[Nook Touch General] nmyshkin:
Oh....I'm so close!!!!! I can write a little volume setting app to use after the USB Audio toggle (or the standard method). Like the kludge above the adjustment is persistent until a reboot but you don't need ES Task Manager.

What I can't do (yet) is combine the volume adjustment with the USB Audio toggle :(

I need to consult the Tasker experts for a workaround. In the meantime I'll get the app posted later today after a little more testing.

Edit: Ugh. Or maybe not. The app causes a reboot.... Still working on the problem.
[Nook Touch General] digixmax:
Not having to navigate through ES Task Manager to get to its Volume tab is a significant improvement.

Does your app still entail the ritual of disconnecting/reconnecting the audio adapter?
[Nook Touch General] nmyshkin:
I'm afraid so but that is rather moot since I've run into the reboot problem. I'm not giving up, though :fingers-crossed:
[Nook Touch General] nmyshkin:
tiny "progress"

Oy. This really needs someone who can understand all the stuff thrown out in the logcat.

But...I have made one discovery that tames (not controls) the ALSA volume. In the master ALSA configuration file at /system/etc/asound.conf there are three instances of Speaker Volume of one kind or another. All three are set to the

maximum

(150 for each channel). Although the minimum is supposed to be 0, anything lower than 4 effectively mutes the sound card. Reducing the setting to 4 may make some headphones usable without the kludge described earlier. You can do this with a simple text editor, either on the device, or pull the file to your computer, edit and put it back. A reboot is needed for this to take effect even though ALSA documentation says this file is always read anew when a device is detected.

If you want to see whether this is even worth the trouble and you have adb access, you can fire up the USB Audio (without the kludge) and send the following shell command:

adb shell alsa_amixer -c 1 set Speaker 4

The volume change will be instantaneous but not permanent. For that you need to make the change in the asound.conf file.

The real issue, of course, is that without the mysterious beneficial effect of the kludge, the native android volume control has

no

effect on either actual media volume OR the ALSA volume. When the kludge is used there is still (I believe) no effect on the ALSA volume but the native volume control is able to take the static value of the ALSA volume and decrease it, thus giving the effect of a volume control.

I think this is correct because when the asound.conf file is edited as described above, the maximum android volume is

less

than the earsplitting level when the ALSA controls were set to their maximum (150).

In any case if you query the ALSA volume post-kludge it's clear that the android media volume setting is having no effect on the ALSA value which remains whatever is specified in asound.conf

Therefore part of the problem is that rather than controlling the ALSA volume, the native android volume control overlays the constant ALSA value.

OK, I admit I wrote most of that to clarify the issues in my own mind. Maybe someone will get another idea. I've Googled every search string I can think of and have only learned to tinker a little with ALSA commands. But the real mystery is in the android system and what the logcat shows.
[Nook Touch General] digixmax:
[MENTION=5562185]nmyshkin[/MENTION]:

You solved the mystery!!!

Following the lead in your PM, I re-enabled Phone.apk (which many of us had disabled to conserve battery) and now volume-control using my USB Audio adapter's volume-button works like a charm. :)
[Nook Touch General] nmyshkin:
LOL--I

hope

you are correct, but there seems to be a devil in my details. I now cannot get it to work using my one-touch toggle app, but it does seem to work with the standard 2-app setup. What seems to fail using my app is that mediaserver is not killed (maybe it's just wounded....). So I'd be curious to know if this continues to work for you, even after a reboot. I thought I had it all sewed up until a reboot showed me otherwise.

When I found the PID for mediaserver as [MENTION=4474482]Renate NST[/MENTION] instructed in order to replicate the function of her AudioCtl app, I may have oversimplified things too much. Not knowing much, I just assumed the PID was constant. So I wrote the value I found (19409) into my app. But now that I am having trouble, I find that this:

adb shell ps

which lists the PID values for apps and processes gives something quite different for /system/bin/mediaserver (1818 right now).

So.....Renate's app continues to work and I'm guessing that's because it queries the PID value before killing mediaserver. I can't say that enabling the Phone.apk has changed the PID value for mediaserver, but there are a whole lot of processes listed now that it's back compared to when I checked PIDs before.

So as a "proof of concept" I just edited the Tasker task from which my one-touch app was produced, changing the PID value to 1818. That worked like a charm.

Next I ran the one-touch app again andthis time it worked. I guess I'm showing my ignorance (yet again) but that does not make sense. I'm betting that if I reboot something different will happen.

........

OK, so on a reboot I get a PID of 978 for /system/bin/mediaserver and (not surprisingly) my one-touch app does not work. And now Renate's 2-step method hangs up on the AudioCtl app. Another check of the PID via adb shows it has changed to 2263.

I'd be very curious to know how your device behaves after a reboot. Mine's a mess (as far as this audio stuff goes---everything else is fine).
[Nook Touch General] nmyshkin:
This morning it occurred to me that my one-touch toggle app might just be corrupted. I've really put my poor NST through the wringer the past few weeks working on this problem :(

So I uninstalled it and put on a fresh copy. It worked on the first try :)

I'm hoping your experience is the same. If so I'll monitor the power issue for a week and then write a summary post and call this "solved".

Edit: Or not. After a reboot the one-touch toggle app again failed to work. What does seem to work consistently is using Renate's two apps for the first time after a reboot. Thereafter, for some reason known only to Heisenberg (and maybe Renate), the one-touch toggle app successfully sets up the USB Audio with proper volume control. Until another reboot. I need to contact Renate.
[Nook Touch General] digixmax:
Sorry I should have been clearer: I have not gotten around to try your one-step app yet, as I want to make sure I don't introduce more variables into my mysterious "loss of sound" problem (as I described in my PM). So what work for me so far (fingers crossed :) as I am starting to lose faith in Bacon's principles :)) is Renate's two step-process.

Yes the PID for a Linux-type OS process is not deterministic (except for the one and only "init" process which has PID of 1). You can find the PID of a currently running process with the command pipe "ps ax | grep <process-name>" (but I have no idea if/how you can make use of this from inside your app).

Yes, I now see the old familiar "Cell Idle" process topping the battery-usage list :(.
[Nook Touch General] nmyshkin:
Thank you for that helpful info about the PID. I'll see what I can do with it. It does not explain how the one-touch app worked before the phone.apk was awakened nor how it works after the 2 step method has been used once. But it's a start.

I installed a battery app today to keep an eye on things but it's showing me the "dialer" as consuming only 0.8% of the battery usage. I may not have access to what I need to know with this particular app.
[Nook Touch General] digixmax:
Apparently the ps command in Android behaves a bit differently than its Linux counterpart, there is no need for the "ax" option stuff.

Instead, this command pipe

ps | grep phone | tr -s ' ' | cut -d ' ' -f 2

(note the single blank between the two single quotes as value for the -s and -d options) will yield the PID for the phone process.
[Nook Touch General] Renate:
My original AudioCtl made the mediaserver crash itself, then it would restart properly.

I never really dived into what the conflict was exactly.

This is the whole guts of AudioCtl:

AudioManager am = (AudioManager) getSystemService(Context.AUDIO_SERVICE);
am.setSpeakerphoneOn(true);
am.setMicrophoneMute(false);
[Nook Touch General] digixmax:
I am curious about the nature of the dependency of volume control on the Phone app.

Also given the dependency it would be nice to be able to fire up and kill Phone as part of AudioCtl.
[Nook Touch General] nmyshkin:
I have thought about this already in light of some people's power drain experience. I can kill an app as part of the procedure and start one up but not sure if the fact that it's a

system

app will wreak havoc if I try--or if it will just restart once the system discovers it's not running. There's also the issue of it starting up automatically when you boot/reboot so then you would need to run USB Audio right away to kill it? That seems a bit excessive. I'd like to look at the power drain issue more closely before adopting a strategy like that.

What happens if you move a system app out of /system/app to /data/app?

I have to say that I don't see a "major" power drain with phone.apk enabled. My battery lost 1% overnight (from about 7 pm to 6 am). In any case, I will see what I can do with the information both you and Renate have provided. Her method for restarting mediaserver is more genteel than mine. I've just been trying to drive a stake through its heart :rolleyes:

I'm grateful for the help.
[Nook Touch General] nmyshkin:
I'm sure you've been told many times (or should have been), but you are a GEM, Renate!

I now have a routine that works perfectly and with android control of the volume. Now to look at that phone.apk/power consumption issue.....

Edit: I have posted version 3 of the USB Audio toggle app (and the similar Tasker task). This version works with or without phone.apk being used to access the android volume control.
[Nook Touch General] digixmax:
This is in line with what I observed on my NST.
[Nook Touch General] nmyshkin:
I am working on the power drain issue. My strategy goes something like this:

1. default disabled phone.apk("phone.OLD")

--here execute command sequences to enable USB Audio--

2. remount /system rw, rename "phone.OLD" to "phone.apk"; remount /system ro

3. pm enable com.android.phone

4. etc. for typical startup of USB Audio

on exit from USB Audio:

5. typical exit from USB Audio

6. remount /system rw, rename "phone.apk" to "phone.OLD"; remount /system ro

7. pm disable com.android.phone

That's the concept, anyway, since I've failed to find any solution to the cell standby "feature". Google is littered with years of posts regarding this problem and the "best" solution is to disable phone.apk :p

So I'm working on it but now that I have an app that lets me see the battery draining processes and I have phone.apk disabled while I work (and have rebooted) I see "phone idle" listed as the major power-eating process. What the heck?!

Edit: see here
[Nook Touch General] Renate:
Mmm, I don't think that I'd remount /system all the time.

You should be able to install phone.apk as a normal app (in /data/app), I think?
[Nook Touch General] nmyshkin:
Yeah, it looks kinda risky. The renaming part works perfectly. But I am unable to launch the app once it has its normal .apk ending :( That seems to require a reboot. Not the idea at all.

I also can't disable the app if it starts with a boot. It just restarts right away. Grr....

I did try renaming the app system/app/Phone.OLD and then installing a copy into data/app. The installer states that the app is already installed and do I want to do a new installation (yes). After that the app appears in the correct folder (no sign of it in the launcher). I forget now how I tried to run it--maybe via adb. But it did nothing.

Edit: OK, I used a Market app to convert the system app to a user app. Still a no-show in the launcher but it starts automatically on boot and resists killing. So that's no good....

Edit: see here
[Nook Touch General] nmyshkin:
decompile of Phone.apk

LOL. It's desperation time here, folks. I've tried every sort of way to disable the "cell standby". Any settings I can get the NST to take have no effect.

So....with APK Studio I have decomplied the phone.apk, hoping to gain some insight into the audio side of things. What I don't know about Java and the innards of apps would fill several Watson-sized memory banks, but it couldn't hurt to take a look-see, right? Ideally someone who understands such things would know what to look for, but in

my

case, I just started searching through all the smali files for the string "audio".

It turns out the occurrence of the string "audio" is pretty much confined to two of the files (attached below for "light reading" of inquiring minds).

This seems to be the most common "set" statement: setAudioControlState(I)V

Anyway, I present it here for perusal. I'm going to disable my phone.apk for awhile and return to the ES Task Manager kludge (post #3). The battery drain is a bit much for me :crying:

It seems like an ideal project for a rainy day: gut phone.apk to create a tiny system app with just the audio control properties--but way beyond my abilities.

Edit: see here
[Nook Touch General] Renate:
Oh, I think I see what's going on here with intents.

I can't even find a copy of Phone.apk here.

Is this 1.2.1?
[Nook Touch General] nmyshkin:
Yes, 1.2.1

Here's a copy.

I've started gutting all the cell and Bluetooth stuff from the app with a view to recompiling a simpler version. A meat-ax approach.

Edit: see here
[Nook Touch General] Renate:
I took a bit more look into this.

This works for setting the beep volume in AudioCtl:

setVolumeControlStream(AudioManager.STREAM_MUSIC);
[Nook Touch General] nmyshkin:
This is excellent! Is there some way to recreate this result by sending an intent or via adb shell commands? I've been searching on both possibilities since I saw your post but have come up with hints only.

Edit: see here
[Nook Touch General] Renate:
Yeah, I'm on my way to a patch for the root cause, but right now I have to get off to my day job...
[Nook Touch General] nmyshkin:
Analysis of phone.apk and power drain complete

See here.
[T-Mobile Samsung Galaxy S6] postmastergeneral:
i cannot find the setting and i'm about to lose my mind. i know it was there at some point...
[T-Mobile Samsung Galaxy S6] OsSkates1996:
All the way at the bottom mate
[T-Mobile Samsung Galaxy S6] postmastergeneral:
:(

http://i.imgur.com/n3Vwq5Q.png
[T-Mobile Samsung Galaxy S6] OsSkates1996:
Are you fully stock? :o
[T-Mobile Samsung Galaxy S6] ambervals6:
Happened to me once. Do a factory rest.

Sent from my SM-G920T
[T-Mobile Samsung Galaxy S6] Fightoffyoredeamons:
Did you delete smart manager? If so that will delete the link to the battery
[Android Q&A, Help & Troubleshooting] vooks:
I S-off'ed and rooted my 6123 but accidentally deleted a few system apps including the Setup Wizard.

When I did a factory reset, I got this error'Unfortunately Setup Wizard has stopped'

Now the most I can do is to access the settings but nothing else.

Please advise on removing this error and restoring my old system apps
[Sprint Galaxy S 5 Q&A, Help & Troubleshooting] indigold:
ii bought this phone off ebay , i mean g900p and i dont have 3g. only 2g. when i select 3g i have noi signal. does anyone have a working qcn
[P3600 ROM Development] dogmood:
Dear All,

Previous upgrade a wm6 rom from xda-developers.

Now during the upgrade by official rom...the machine hang on three color bar

and could not hard reset...

The words are:

Trin100

IPL-0.50

Trin100

SPL-1.07.0000

Please help me and teach me what should do...plenty thanks!!!
[P3600 ROM Development] racerx_:
You need to reflash an original ROM from your manufacturer.

look here for more details..

www.trinityguides.info
[P3600 ROM Development] dogmood:
dear sir, thx! yr solution works for me n now im replying u on my ppc wm6!
[P3600 ROM Development] ward777:
What if you don't have an official ROM?
[P3600 ROM Development] Matterhorn:
I think there are original roms available to download for most all Trinity phones and languages except Orange. Look in the Wiki of this site.
[P3600 ROM Development] ward777:
You hit the nail on the head! My phone is the Orange M700. Does anyone know any other methods :confused:
[P3600 ROM Development] Kris404:
Try the RUU from pof's SIM & CID unlocker package.

Kris
[LG Optimus L90] EagleSlashZero:
I have CyanogenMod 11 made for the D415 LG L90, but I want to go back to stock because of screen problems and video problems. Can I use the flashing KDZ method with, say, KDZ 10e to go back to Stock Kitkat? Is there any extra steps or precautions while flashing from Cyanogen to Stock? I do not have an SD card, so I cannot flash a ROM through recovery.
[LG Optimus L90] lerner17:
Check this thread to offline flash kdz, this one for KK, and this one for lollipop
[LG Optimus L90] EagleSlashZero:
I know how to flash an offline KDZ, but is it possible to revert back to stock (10c/10e KDZ) through this method without bricking my device?