yashsingh1/xdaforums huggingface dataset:
[Motorola Atrix 2] dmroeder:
So I went back and looked at the dirty unicorn change log and the last update that was made added KEXEC support to the ROM. Do you guys think that something changed with the KEXEC kernel since then that has caused this issue? (it would have had to change with both the "stock" and JBX).

As far as I can tell none of the 4.2.2 ROMS had this problem, at least not their final versions (maybe they did early on).

I need to keep reading up on ROMS / Kernels / Kexec. Maybe I need to build a few of my own ROMS in order to get a little better understanding of the nuts and bolts.
[Motorola Atrix 2] nma83:
[MENTION=4899078]dmroeder[/MENTION]: Is it possible for you to check the diff the disassembled audio libs between stock, 4.2.2 + JBX 0.8 and a newer kexec ROM? I do not have a partition flashed with the 4.2.2 + JBX to check myself. Can you also attach logcat snippets during a call from 4.2.2 + JBX build? It would be great if we can crack this!
[Motorola Atrix 2] dmroeder:
I'm willing to do anything at least once! Just need to make sure that I understand what you are after:

These audio libs, are you referring to the audio libraries in /system/lib/hw ? (like alsa.omap4.so) (maybe not because I don't think .so files are disassembled)

I'll PM you a logcat here in a sec.

Just a note, I tested the CM10.1.3, volume adjustment worked and I tested Mokee 4.3 and it did not work.
[Motorola Atrix 2] nma83:
.so files can be disassembled with arm-elf-objdump. Thanks in advance for the logs.

Just to be clear, do you mean CM10.1.3 with a kexec kernel works?
[Motorola Atrix 2] dmroeder:
Good to know, I'll look into disassembling them in the morning. If the ones in /system/lib/hw are the ones I should be looking at, then I already have some set aside for both my working 4.2.2 and non working 4.4.1. I'll be honest with you, I have no idea what I'll be doing, but I'll give it hell...

And yes the CM 10.1.3 I was referring to is a KEXEC version (latest build posted). I did not install any additional kernel, just using the one that came with it (JBX 0.8.1)
[Motorola Atrix 2] nma83:
Ah that sounds good. I will also try to extract the libs from the ROM and compare with stock and non-working version I have.
[Motorola Atrix 2] dtrail1:
I figured that when using Xposed modules to adjust volume steps the volume is working fine - w/o this issue. So this must be fixable by rom side independant from kernel.
[Motorola Atrix 2] nma83:
Hi dtrail, Thanks for your response. Did you use Xposed modules on edison to adjust volume? I assumed it was kernel related since atleast in PA, the problem appears only in kexec builds, the ROM part being the same...
[Motorola Atrix 2] nma83:
I tried with Xposed + Xvolume module but of no avail :(.
[Motorola Atrix 2] Ravikirancg:
well, from what I remember, the first kexec based pac that I built had it working.. that was probably a dirty build.. I think some of you guys are still trying to use non kexec roms for battery.. can one of you tell me if de-kexecing the rom gets the in-call working? that way we can figure out for sure if its kernel related or not.. if that doesn't work, try replacing the audio related files in lib/hw..

Good Luck :)
[Motorola Atrix 2] nma83:
Hi Ravi, ROMs without kexec have it working (I tried a couple of them). But just replacing the audio lib in lib/hw caused a boot loop in the kexec ROMs. So I think a simple replace might not help. Trying to reverse the audio lib and hope for a solution.
[Motorola Atrix 2] dtrail1:
Replacing libs cannot work because they were compiled by different kernel sources.

Btw: I'm using nexus experience 1.8 + jbx 12-09 and I don't have any problems with volume adjustment during calls. Also tried to reproduce that "issue", but there is no issue for me. Tried a fully clean reinstall absolutely from scratch (rsd, etc)?

Once I had the problem that I couldn't flash kernel to stock system, I performed a clean reinstall of everything and now it works again.

Most people aren't reporting that bug, so it might happen randomly on some devices - or it's caused by any user action, don't know

However, could you guys send some logs from a reproduced bug situation with this? Please don't forget you send me both, a logcat and a dmesg dump.

Gesendet von meinem XT910 mit Tapatalk 4
[Motorola Atrix 2] nma83:
Hi dtrail, are you talking about edison (mb865) ROMs or razr-spyder? As far as I know, all of Edison's kexec ROMs have this issue and mentioned in the OPs of each thread.

And yes, I do realise that copying old libs wont work. Just a desperate measure :).
[Motorola Atrix 2] dtrail1:
Oops.. In tapatalk this topic was listed under my subscribed threads, but it doesn't show the devices sections in its overview . :D

So no, I'm taking about RAZR.

Gesendet von meinem XT910 mit Tapatalk 4
[Motorola Atrix 2] nma83:
Thanks for clarifying. I thought I was horribly mistaken about something for a moment :).
[Motorola Atrix 2] nma83:
Duplicate post removed.
[Motorola Atrix 2] nma83:
These are the conclusions I have come to after a week of prodding around and interactions with altered and dtrail.

The audio lib for edison is a proprietary blob pulled from the razr leaks.

razr and edison use different modem (BP) chips, qcom in the razr and STE in edison.

In edison, the voice call volume path is controlled via AT commands sent from the audio lib (stock version).

Since the kexec audio lib comes from razr (with a different BP), the calls that send the AT commands do not exist.

The issue would be solved if we can find a way to send AT commands to the STE modem. If did not any /dev/tty* devices exposed until now.

Is it possible to build the RIL (rild binary) from the source available here? If so, we can add a hook to pass AT commands.

EDIT: Found the source for the modem daemon (mid). Looks like this executable is compiled from source for edison. Can explore patching this...
[Motorola Atrix 2] nma83:
Solution in sight!

I have updated OP with a proposed solution complete with implementation and source code. I was able to mimic the modem init daemon mentioned in the previous post to pass any AT command to the modem. Voice volume can now be controlled albeit in a clumsy way. But it would'nt take much time to wrap this into the core framework I hope...
[Motorola Atrix 2] yx868868:
Thank you for the contribution you make

Very happy this old problem, it is necessary to solve the
[Motorola Atrix 2] nma83:
App created!

Updated OP with app for adjusting the voice volume. Testers welcome!
[Motorola Atrix 2] elgeorge_rp:
Thanks for your great work.
[Motorola Atrix 2] Uzayr:
thanks a lot nma for putting your effort and time into this.

if you don't mind, i'm thinking of integrating this fix in my future releases.
[Motorola Atrix 2] yx868868:
bug feedback

After restarting the phone, they automatically revert to maximum volume.
[Motorola Atrix 2] nma83:
No problems Uzayr. It would be good to integrate this in all kexec builds, assuming its proved stable.
[Motorola Atrix 2] nma83:
Yes. That's because the setting is not stored anywhere. An enhancement for sure. Will track on github.
[Motorola Atrix 2] yx868868:
You send the patch if integrated into the ROM can use the volume keys to adjust the volume?
[Motorola Atrix 2] nma83:
No you still have to use the app to change volume. There is some more work to integrate fully into the ROM.
[Motorola Atrix 2] yx868868:
Come on, wait you of good news.
[Motorola Atrix 2] dmroeder:
I finally got a chance to use it and I must say this is great. This issue has kept me back on an older rom.

It works as advertised for me. Even if it doesn't make it farther than this I'll be satisfied. I don't find myself adjusting it very often anyway, I usually keep it at the same level.

A big thanks again for your efforts on this. I think it's a very big contribution to this phone.
[Motorola Atrix 2] RAD7:
Good work NMA83, Cheers!
[Motorola Atrix 2] nma83:
Update

Updated OP with a new version. Changelog added too.

Thanks!
[Motorola Atrix 2] dmroeder:
Kind of petty, but could I convince you to put a field that displays the value of the slider? That way you don't have to hit apply to see what value it is at?

Thanks again for the solution! It's much appreciated!
[Motorola Atrix 2] nma83:
Oh yes. That should be minor, will update this weekend.
[Motorola Atrix 2] dmroeder:
Rad man, thanks!
[Motorola Atrix 2] nma83:
Done and updated in OP.
[Motorola Atrix 2] dmroeder:
I've gotten reports from others that 35=no echo and 39=slight echo. So I keep mine at 35.
[Motorola Atrix 2] elgeorge_rp:
Thanks for this great apk. Could you add the possibility to change the volumen by default when you move the bar, without press apply everytime?

It will very ussefull.

Thanks
[Motorola Atrix 2] nma83:
The reason for not changing when the bar is adjusted is because the app asks for root permission for the update. It would be poor user experience if the SU dialog came up (for someone who did not grant it always) for every change of the bar. Hence the decision to do the update on a button press. In a future update, the app could potentially not need the root permission (if a daemon started at boot could handle the low level calls) and then this change can be done.

Can add it as an option though, next update...
[Motorola Atrix 2] nma83:
New version

Updated with the above change.
[Motorola Atrix 2] elgeorge_rp:
Thanks for you work!! This is a usefull apk.
[Motorola Atrix 2] xmotouserx:
Atrix 2

Graphical glitches = Fixed :good:

1080p HD recording = Fixed :good:

In-call volume issue = Fixed :good:

Now, lets go for the only remaining issue...HDMI output...we need to get it fixed... :laugh:
[Motorola Atrix 2] Aceofzeroz:
HDMI output : Fixed ;)

Sent from the Ace's MB865 using Tapatalk
[Motorola Atrix 2] arnab:
incall volume is fixed from the rom itself or we have to use the atcmd apk
[Motorola Atrix 2] dmroeder:
You have to use the apk
[Motorola Atrix 2] xmotouserx:
Its fixed??? :confused:

when??? where??? how??? what rom??? kernel??? :eek:
[Motorola Atrix 2] Aceofzeroz:
Someone reported it working for them in the JBX thread, although it seemed to only him/her alone. Check it out if you haven't already. :)
[Motorola Atrix 2] nikhJ:
Wait this fixed apk .. Do I need to install it on a jbx ROM.. I'm running cm11. Without jbx
[Motorola Atrix 2] nma83:
It is meant for all kexec ROMs. JBX or not does'nt matter.
[Motorola Atrix 2] elgeorge_rp:
Hello,

Any News about : "Make the socket code run as a daemon on boot "

Thanks
[Motorola Atrix 2] nma83:
The volume control code already runs as an Android service. I will remove that item from the TODO list.

By the way, any particular reason you ask that?
[Motorola Atrix 2] arnab:
Plz add an about section in the abandoned settings option on top right corner.....about callvol like thar...give it a polish look
[Motorola Atrix 2] sameerm02:
In call volume for NON-KEXEC

I have Mirage Rom v2.9 [Nonkexec] by Aceofzeroz on one of my system and this rom is unable to adjust in-call volume. :(

So I tried to install your ATCmd_30122013.apk to check if it works here or not :confused:

and miracle IT IS WORKING HERE also !! :good: :victory:

we can adjust in-call volume. :good: :victory: :highfive:

So thanks for your great app :angel:
[Motorola Atrix 2] nma83:
Great to know it works across multiple types of ROMs. :good:
[Motorola Atrix 2] sameerm02:
You can add this in OP.. :D
[Motorola Atrix 2] Aceofzeroz:
I don't recall if I thanked you personally, but thank you very much nma for all your hard work on making this app back then.;):D

Now that I know that it can work with non-kexec roms, I'll let my team know so that we can link your app to our threads.:cool:

Sent from the Ace's MB865 using Tapatalk
[Motorola Atrix 2] nma83:
Ace, this is nothing compared to all the porting you people are doing! :cowboy:

I hope to integrate this fix into the phone dialer app so that we can use the volume buttons properly during call.

But I am not sure where the dialer app is built from. I tried to clone and build the dialer from CM repo but seems to have lot of dependencies.
[Motorola Atrix 2] Aceofzeroz:
Aaww shucks, much appreaciated!

Thanks a bunch, was our pleasure!:D:highfive: I don't have much android source building knowledge yet, but I'm sure you'll be able to find a way and/or another dialer app to add it to from the available sources.

Either way, take your time with it and I wish you the best of success with your plans!:cool:
[Motorola Atrix 2] ShurikKb:
Finally, tru in-call volume changing!

Good news, everyone!

I've implemented normal in-call volume controls by adding to this awesome application BroadcastReceiver handling VOLUME_CHANGED_ACTION.

This means now we can finally control volume during a call by native controls. Superuser is still needed for each volume step change so I highly recommend to give permanent su access to the application and switch off superuser's notices and logging for it because they slow things down. And don't push buttons too fast and too hard, be patient ;). Though it still can be improved in terms of preformance, it works stable for me.

You can find sources on my github and try my build in the attach (at your own risk! ;)). You'll need to uninstall previous build first. And it takes some time after reboot before you can use volume controls, a couple of minutes, so its not critical at all.

And, of course, big thanks to nma83 and all who helps with this issue!
[Motorola Atrix 2] sameerm02:
Thanks a lot ShurikKb... :good:

Trying it now.. :)
[Motorola Atrix 2] sameerm02:
Tested !!

Worked !! :good: :good:
[Motorola Atrix 2] nma83:
This is great news ShurikKb! Will try it out soon...
[Motorola Atrix 2] رامز:
do we need to install the new apk normally or move it to system/app? some "How to" here please..
[Motorola Atrix 2] dmroeder:
I installed it normally but I had to uninstall the current version first
[Motorola Atrix 2] sameerm02:
It is already given by ShurikKb,

But here's the how to:

1. Uninstall the old call volume app (if you have it).

2. Install the apk given by ShurikKb, allow SU permissions

3. Restart your phone (I did it)

4. Don’t call immediately as your phone turns ON, wait until you get the message that super user has given the permission to call volume.

5. After this message, call anyone and check the in-call volume

6. Just take care not to press volume up or down button repeatedly, wait for some moment after the press then press the required volume buttons.

That’s all ;)

Hope this will help you
[Motorola Atrix 2] رامز:
thanks and +1 :D
[Motorola Atrix 2] josuearisty:
What about if this app is integrated into system files? Included inside system apps in the rom?

Enviado desde mi MB865 mediante Tapatalk
[Motorola Atrix 2] nma83:
OP updated

I have added the new app from [MENTION=2372465]ShurikKb[/MENTION] to the OP. Also added a small how-to section (from [MENTION=5363366]sameerm02[/MENTION]).

Thanks to both! :good:
[Motorola Atrix 2] ShurikKb:
Thanks, some corrections:

- reboot is not needed, I just mentioned it in case of immediate call after it.

- I highly recommend to go to SuperUser right after granting the permission and switch off journaling and notifications for this programm, it will improve performance.
[Motorola Atrix 2] nma83:
The 2nd one is a good tip. Updated in OP.
[General Omni Discussion] webore:
Hi

I'm Chinese and my device is find 5 and I find some text in the settings are still in English.

I want to try translating them but I'm not using linux and not familiar with gerrit or git.

Can anyone give me the xml files so I can contribute ?
[Galaxy Tab Q&A, Help & Troubleshooting] adreno2:
Hi,

I'm new to Android development, I own an old GT-P1010 tablet and would like to experiment with building a newer kernel and Android stack for it.

The tablet has a Cortex A8 CPU, however it usually comes integrated into an SoC which remains unknown to me. Any ideas on what it might be?

What toolchain (gcc-based) should I use to build a stack such as CM9 or AOSP?

Finally, do you guys know what GPU the P1010 has integrated? Is it the Adreno 200? Is there a kernel driver/patches out there for the said GPU and corresponding to the userspace GL|ES libraries?

Cheers,
[Galaxy Tab Q&A, Help & Troubleshooting] adreno2:
A bit of investigation tells that's based on a TI's OMAP3 SoC and has a PowerVR SGX530 for 3D h/w acceleration.
[General Topics] jschleider:
Has anyone been able to change the hareware buttons on the T mobile SDA?
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] jarcher12:
I have been very happy with one click odin mf9 rom and wondering if anyone is working on making a one click rooted mk2 for us who are not so thrilled about flashing this that and the next thing to get stuff to work.

Not even sure i want to wander into the knox minefield anyone have any thoughts if it s worth it. I live in Indonesia and have no recourse if my phone bricks, no easy replace by sprint here.....:confused:
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] daniel4653:
Advice. Stay on Sprint oartiess.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] jarcher12:
oartiess OTA's i get it took a little while.

just want stock rooted pretty much, but seems to be a big hassle just to get that to work and no guarantees thats why i asked about a one click.
[Galaxy S II Q&A, Help & Troubleshooting] soeschelz:
Hi,

at the moment I run CM11 Unofficial on my SII, but it is still a bit laggy. So I want to ask how smoth OMNI is running on SII an does OMNI has the feature to block calls from anonym callers? That's a very importent feature to me and a ROM which doesn't support this is useless to me.
[Galaxy S II Q&A, Help & Troubleshooting] mosespl:
You can watch review about omni and pound on youtube

Wysłane z mojego GT-I9100 przy użyciu Tapatalka
[Galaxy S II Q&A, Help & Troubleshooting] D-Construct:
I have been using Omni nightlies on my S2 and it's very smooth and fast till now.

I'm having severe battery drain issues and I'm trying to isolate the cause for that but other members have reported that the battery works out well for them.

It doesn't seem to have the call blacklist feature till now and I too miss the feature.

Don't want to use some app or mod for that.
[Galaxy S 4 Q&A, Help & Troubleshooting] etrobear:
I have a samsun s4 i9505, and since a month or so , when i connect the phone to charge and the displlay goes of the red led that is supposed to stay on its not, also when tyhe low battery either.

I have try the menu *#o*# and in the test of the leds the red it is on as the blu opr green.

I have clean up my phone with a hard resert and even witout any applications intaled only the ones that came with the phoe the led doesnt work.

I looked at the adjust display led configuration and the option it is marked.

And dont know what more to do, i any of you have the same problem please let meknow if you get the solution for that.

I also have tried programs to ontrol the leds but still not working, i have vhange the color notification for whatsup from lue to red and nothing i get the messages but the led doesnt blink as just before foes.

Please HELP

Thanks
[Galaxy S 4 Q&A, Help & Troubleshooting] Joku1981:
Try to put ur phone charging and press the button Power one time (Lock/Black screen). Tell me if the RED LED appears :highfive:

EDIT: Go to APPS - SETTINGS - MY DEVICE - LED and tick all options :)
[Galaxy S 4 Q&A, Help & Troubleshooting] etrobear:
I did what you say anf the led doesnt appears

I think is maybe something wrogn with the red led because if i changw the coloeçr to blue during the chrge works

USING LIGHT MANAGER I CAN PUT ONLY BLUE AND GREEN ANY CMBINATIONS WITH RED DONY WORK
[Galaxy S 4 Q&A, Help & Troubleshooting] etrobear:
Yesterday i tryed again what you told me and the red light appear but only for a few seconds after that when out again.

Thats helps.
[Galaxy S III Q&A, Help & Troubleshooting] flruleu:
Hello everyone. I flashed Android Revolution HD 40.0 on my Samsung GT-I9300 international, everything works fine, just i have an incredible delay on unlocking screen.

If i don't use phone for 15 minutes or more he will unlock with a lag of 5-10 seconds or so.

When i was on Android Revolution HD 32 i didn't have this problem. So, please either someone give a tip on how to solve that, or give a link where i can find Android Revolution HD 32. I did google for it before posting here, it appears that is no place to download it from.
[Galaxy S III Q&A, Help & Troubleshooting] Saixer:
ARHD 40 is based on a bugged release. To resolve the delay you can install a rom based on mk6 (i suggest you to wait s4 revolution v12) or install another kernel over your rom. In this case i suggest you GoogyMax kernel which allow to resolve all my problem
[Galaxy S III Q&A, Help & Troubleshooting] flruleu:
thank you.
[Samsung Galaxy Grand Quattro] RulerAk:
PLease tell me which is the best os to make a custom rom i.e windows or ubuntu.

I tried making roms in win using cygwin but never succeeded (status 0 or status7 keep irritating me)

Also if ubuntu is the best give me some links to make a rom from beginners to pro level.

my phone - galaxy grand quattro.

thanks
[Samsung Galaxy Grand Quattro] scool54:
well i think this can help u bro.....http://xdaforums.com/showthread.php?t=2541198
[Samsung Galaxy Grand Quattro] RulerAk:
Ty bro...will try for sure;):victory:
[Samsung Galaxy Grand Quattro] coolkoushik07:
There is nothing best in xda..
[Samsung Galaxy S II Plus] ale99iwillbeadev:
Can i flash cm 11 on cm 10.1 ? Does it boot ?
[Samsung Galaxy S II Plus] nickchk:
u need at least stock 4.2.2 to flash cm10.2 and above(cm11). upgrade to 4.2.2 first
[Nexus 7 (2013) Q&A] nevinconstantin:
Hi, I recently dropped, cracked my screen and broke the digitizer on my year old 1st generation Nexus 7.

I have two options:

1) Buy a new 2013 nexus 7 for 288$AUS

2) Replace my screen myself for 60$AUS off eBay with the risk of breaking my screen or tablet. I could also get scammed with a faulty or broken replacement screen

Please Note:

-Replacing the old Nexus 7's glass requires replacing the whole screen which ends up getting expensive.

-Replacing the Screen officially costs about 170$

I would like people's opinions on the new nexus 7 and is it worth the upgrade?
[Nexus 7 (2013) Q&A] mertzi:
If you can get the Google play edition of the lg g pad in Australia you should go for that instead. Lg is superior hardware wise. Better build quality. Read about the touch problems of the n7 -13.
[Nexus 7 (2013) Q&A] mj0528:
That device comes with its own set of issues just like every device. I have a new 13 n7 and it's perfect without issue!
[Nexus 7 (2013) Q&A] mertzi:
Of course it is! Problems never happen to loyalists.
[Nexus 7 (2013) Q&A] shieldee:
I own the Nexus 7 for 3 months now. I've never had any mentioned issues with the touchscreen or random reboots.

It's a wonderful piece of hardware especially the display. Just love it.

On the down side it looks kind of fragile. The plastic on the sides of the screen, top device has few bruises although I don't remember ever dropping or hitting it against something.

All in all its a great value for the money.
[Nexus 7 (2013) Q&A] LoopDoGG79:
And problems always happen to people who act like jerks. :rolleyes::rolleyes::rolleyes::rolleyes:

I to have no problems and by far are no "loyalist" I initially did have some touchscreen issues, but have disappeared with the latest updates.
[Nexus 7 (2013) Q&A] mj0528:
Actually it's my first nexus ever!!!!
[Nexus 7 (2013) Q&A] slyr114:
I like my nexus 2013 but after owning it for a while now I would recommend buying the old one brand new again, the overall shape and build is better IMO and as long as u don't need the upgraded screen I would save your money.
[Nexus 7 (2013) Q&A] nevinconstantin:
I didn't do much research, but it looks like the Google play edition is not available yet and the regular edition is 400$. My maximum budget is around 300$. The old N7 did have reports of bad build quality, bad touch screen and also random reboots but i was willing to take the risk and had no problems with it until it fell. I am willing to trust asus again and buy the new N7.
[Nexus 7 (2013) Q&A] ethanfel:
i own one and if i had to do it again i would stay away. Touchscreen issue plague my experience everyday..