yashsingh1/xdaforums huggingface dataset:
[MTCB Software Development] agentdr8:
My work on XMTC ceased a while back, but what was posted above was correct at the time. The audio output was controlled by the MCU, and triggered via different AudioManager object parameters.

The problem is, all Android app-based audio is done via 1 MCU output (av_channel=sys IIRC). So anyone designing an app would have to determine what the current av_channel parameter is set to. The stock MTC apps do that sort of (they just assume the newly-launched app is taking over audio control, and switches the av_channel).
[MTCB Software Development] typos1:
That was pre [MENTION=322215]7floor[/MENTION] audio mod which bypasses the MCU and gives Android control of the audio IC, I wonder how XposedMTC works with that ? Not heard any one say that I remember.
[MTCB Software Development] p_mike83:
Does this code work as it is?

It is a java code isnt it?

You said it worked for you to cut the audio from stock apps, but inside there is the option to enable it as well? I don't understand?

I would like to stop dvd using this code in tasker. I assume I have to change dvr with dvd and remove this part : // Enable sound from stock audio applications

this.am.setParameters("av_channel_enter=dtv");

I am sorry but I dont unsterstand java.

A time ago I creaTed Modeswitch https://xdaforums.com/android-auto/...t/app-modeswitch-spotify-swc-control-t3310966

An application to help with audio focus on our devices. I am now trying to optimize it to speed it up, and now allow it change the audio focus even if the mode circle didn't run ( that was a limitation of the releases until now)

I would appreciate your help
[MTCB Software Development] typos1:
Wouldnt it be easier to go into factory settings and uncheck "DVD" ? That would remove the DVD from the circle entirely.
[MTCB Software Development] p_mike83:
I am aware of this. Actually my app has already a setting to exclude dvd from mode circle. But its not what I am trying to do. If you are listening to a track on cd/dvd disk and you open spotify (or other music app) the audio from the track continues to play, and you have audio from 2 sources !?
[MTCB Software Development] typos1:
Right, I thought this was sorted by [MENTION=434511]agentdr8[/MENTION] 3 years ago with MTCXposed.
[MTCB Software Development] agentdr8:
It was something I tried to address with XMTC and had moderate success with. Unfortunately that code has aged beyond the current ROM releases, and I didn't have time to keep it up to date.

In order to catch all launches of audio-outputting apps, you'd need an Xposed module to hook into either the current Launcher process to know when apps are opened, or into the system ActivityManager. From there, you could interrogate the AudioManager instance and get/set parameters to flip audio sources. It was something I was looking into for XMTC, but never made any progress.

EDIT: Not sure if you've tried adding in this to switch away from the dvd source and back to the Android source:

am.setParameters("av_channel_exit=dvd");
am.setParameters("av_channel_enter=sys");

Also, I don't think any of this would matter if the [MENTION=322215]7floor[/MENTION] mod was done. Everything should be piped into the standard Android audio streams at that point.
[MTCB Software Development] typos1:
Oh, I thought that XposedMTC was still THE way to stop 2 sources from playing at the same time and to add extra sources into the src button (I use the built in apps myself so dont use XMTC for that)>
[MTCB Software Development] p_mike83:
Thanks! I came along this as I was trying to find the answer. (You have to remove "this" from the code). But anyway I already found an other work around ?. So time for testing my app. The first tests were successful!?
[Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot] Anoobossi:
My wife‘s A3 2016 (A310F) has a weird problem.

It has connection to the Internet but not to ethernet-connected devices.

It connects to the Internet via Fritzbox 7390.

Most of our network devices (QNAP NAS, Philips Hue, Sonos) are connected to a Netgear GS108Tv2 switch. Our Fire TV connects via Wifi.

She can connect to the Fire TV and Sonos if the players connect to our wifi (without the bridge).

My S7 and our tablets have no problems connecting to all devices.

I removed the A3 from the Fritzbox and re-added it: no solution

FritzApp 2 connects to the Fritzbox.

A scan with Fing finds all network devices with proper names and IP.

QNAP File or other apps like SyncMe wireless can‘t find the NAS.

She was on latest German stock firmware. I rooted her phone and installed latest JX‘s L‘oogle ROM. No solution.

Is it ok to flash latest modem (Nordic Countries) via Odin on a German phone?

Does anybody have a clue?
[Huawei P9 Questions & Answers] halliday77:
Hi guys,

I have been hacking around with this thing and reading the forums for days and I'm officially beaten.

I was on EVA-L09C43B140 - Optus Australia.

Attempted to flash to L09C636 using this guide.

As L09C636 isn't a popular choice, it took a lot of looking to eventually find the C636 oeminfo.

On top of that, when viewing the 'verlist.img' file, there were only two lines: EVA_C900B000 and EVA_Global.

Changed the files, and force flashed the UPDATE.APP file, and needless to say, it was unsuccessful and i got a cross-flash C900 version with broken themes.

So I decided to go back, and restored my oeminfo and custom.bin and flashed the original UPDATE.APP - and now I'm reading the correct version number, but still broken themes.

[MENTION=1276411]fibbles[/MENTION]an says here that you need to ensure you flash update_data_dt_default.app", "update_data_hw_eu.app" and "update_data_hw_normal.app" to fix the broken file system - but WHERE CAN I GET THESE FILES?! I have manged to get the ZIP files for "update_data_full_optus_au", and the rest that correspond to the firmware from the Warehouse post, but can't find any mention of these files as .APP files.

I'm sure I have all the files and tools I need, but I have no idea how to fix this and no one else seems to have experience with the C636/C43 firmware.

Any help would be very, very much appreciated. I just need my phone to work now.

Thanks in advance, and keep up the good work everyone.
[Huawei P9 Questions & Answers] Marsou77:
Try to delete data in recovery again. I fixed a P8 Lite doing so.
[Huawei P9 Questions & Answers] halliday77:
Broken /cust partition.

Unfortunately no amount of wiping data/cache will do the trick.

From what I've read, it's a broken /cust partition.

I'm looking for more specific information to fix this, or avoid it breaking during flash, so I can finally flash the stock firmware I wanted, or return to original operator firmware.

Thanks.
[Huawei P9 Questions & Answers] halliday77:
FIXED Rollback

So, i solved this using TWRP to flash the two ZIP files that came with the Firmware.

'update_data_full_optus_au.zip'

and 'update_data_full_hw_normal.zip'

It was not obvious from the [WAREHOUSE] post that these files were required, or even obvious to download.

It might be because of amateur knowledge, but only closer inspection of the file list and manually entering the sub directory and extensions yielded these files. I might post some clearer instructions for the other noobs.

Now that I know I can restore, I'm going to attempt to try the debrand again another day.
[Zuk Z1 General] GRider02:
hi,

Facing lag and unwanted noise during recording while using Smule app.

i tried this on ZUI 2.5 and all MM Roms, it works perfectly fine.

but while on custom roms of N I face the issue.

Any help would be appreciated.
[Zuk Z1 General] Mandek:
i have similar problem. so i should back to mm rom to do smule.
[Zuk Z1 General] singh.9yashpal9:
well there are issues with default camera app in all nougat rom in zuk z1 for example:

1) camera app crashes when used in hdr mode and after crashing camera app it doesnt restart,it always says unknown error or media server died etc (**this error occurs in Mokee 7.1.1 and RR official 7.1.1**)

2)camera touch focus hang and lag when used in auto mode also touch response hangs(**this error occurs in lineage os unofficial nightlies**)

i have tested all nougat roms so far and indeed there is an camera issue...which is a lineage os bug. since evey rom is based on lineage os therefore they inherit camera bug as well...i hope it will be fixed in near updates
[Android General] Cyanic Sword:
Hi, can I please get the device tree you used to make this. Thanks!
[Android General] Digian:
Before flashing TWRP, can anyone share stock recovery for y6 elite (LYO-L02) please ? It is not available online.

root@y6elite:/ # ls -al /dev/block/platform/mtk-msdc.0/by-name/

ROOTM -> /dev/block/mmcblk0p11

boot -> /dev/block/mmcblk0p7

cache -> /dev/block/mmcblk0p24

cust -> /dev/block/mmcblk0p23

expdb -> /dev/block/mmcblk0p10

flashinfo -> /dev/block/mmcblk0p26

frp -> /dev/block/mmcblk0p19

keystore -> /dev/block/mmcblk0p15

lk -> /dev/block/mmcblk0p5

logo -> /dev/block/mmcblk0p9

metadata -> /dev/block/mmcblk0p21

nvdata -> /dev/block/mmcblk0p20

nvram -> /dev/block/mmcblk0p2

oeminfo -> /dev/block/mmcblk0p18

oemkeystore -> /dev/block/mmcblk0p13

para -> /dev/block/mmcblk0p6

proinfo -> /dev/block/mmcblk0p1

protect1 -> /dev/block/mmcblk0p3

protect2 -> /dev/block/mmcblk0p4

recovery -> /dev/block/mmcblk0p8

seccfg -> /dev/block/mmcblk0p12

secro -> /dev/block/mmcblk0p14

system -> /dev/block/mmcblk0p22

tee1 -> /dev/block/mmcblk0p16

tee2 -> /dev/block/mmcblk0p17

userdata -> /dev/block/mmcblk0p25

To dump recovery, it should be as simple as,

dd if=/dev/block/mmcblk0p8 of=/sdcard/recovery.img

Additional partition info,

No. Start End Size F/S Name
1 524kB 3670kB 3146kB proinfo
2 3670kB 8913kB 5243kB nvram
3 8913kB 19.4MB 10.5MB ext4 protect1
4 19.4MB 29.9MB 10.5MB ext4 protect2
5 29.9MB 30.4MB 524kB lk
6 30.4MB 30.9MB 524kB para
7 30.9MB 47.7MB 16.8MB boot
8 47.7MB 64.5MB 16.8MB recovery
9 64.5MB 72.9MB 8389kB logo
10 72.9MB 83.4MB 10.5MB expdb
11 83.4MB 83.9MB 524kB ROOTM
12 83.9MB 84.4MB 524kB seccfg
13 84.4MB 86.5MB 2097kB oemkeystore
14 86.5MB 92.8MB 6291kB secro
15 92.8MB 101MB 8389kB keystore
16 101MB 106MB 5243kB tee1
17 106MB 112MB 5243kB tee2
18 112MB 179MB 67.1MB oeminfo
19 179MB 180MB 1049kB frp
20 180MB 213MB 33.6MB ext4 nvdata
21 213MB 252MB 38.3MB metadata
22 252MB 2721MB 2469MB ext4 system
23 2721MB 3146MB 425MB ext4 cust
24 3146MB 3305MB 159MB ext4 cache
25 3305MB 7801MB 4496MB ext4 userdata
26 7801MB 7818MB 16.8MB flashinfo
[Android General] outlander43:
I have a Y6 elite that hasn't been updated yet. Care to walk me through the dumping procedure?
[Android General] Digian:
There is a catch to creating a backup of the stock recovery, you need to be root to read the raw recovery partition.

Once you have root, either enable developer mode in the android settings menu and connect via USB with the adb-tools and run the DD command above to create a backup copy. Or alternatively, use an app like Flashify to take a backup locally.

There's a few ways to get root without installing TWRP, you could try: KingRoot, FramaRoot, CFRoot, or Kingo Root. It may be trial and error to find which one works on this phone.

Before rooting, I suggest unlocking the bootloader using the guide above in case you run into any issues, obviously stop at Step #10 before installing TWRP if you want to take the stock recovery backup.

If anyone knows an alternate way to grab a backup of the stock recovery, or better ways to get root ... let us know.
[Android General] outlander43:
Finally got around to playing with this. Unlocked the bootloader, tried a few of them but no success

Kingroot makes it to 66% and goes no further

framaroot says the device is not compatible with any exploits

Kingoroot makes it 90% and then comes back with there is a problem parsing the package

Kingoroot PC makes it to 31% then fails

CFroot, I don't know which link to use

Suggestions on where to go from here would be appreciated
[Android General] Digian:
One idea was to try moving the KingoRoot .apk to a temp folder with full permissions, such as "/data/local/tmp" in case there is a conflict. Chmod 777.

Secondly, did you try these ? http://www.technicalnotes.org/fix-parse-error-in-android-there-is-a-problem-parsing-the-package/
[Android General] outlander43:
So .apk is the installation package. To be clear, it installed just fine. But running it, it only reaches 90% completion, then the screen changes and the parsing error comes up. Whatever the case, I copied the install .apk to local storage/android/data/tmp and installed it from there. Same result. I also tried the previous version 4.2.3 with no change in result.
[Android General] outlander43:
Gave up trying the one click root apps, and installed TWRP. Very easy! One thing, if your having problems on step 3, disable and re-enable the usb debugging. Before I did that adb was showing UNAUTHORISED
[Android General] goodjonte:
plz help

when i do the command 'fastboot flash recovery huawei-y6-elite-twrp-3.0.2.img ' it comes up with an error saying fastboot flash recovery huawei-y6-elite-twrp-3.0.2.img erroe: cannot load 'huawei-y6-elite-twrp-3.0.2.img'

can some one please help me out
[Android General] goodjonte:
so i mess ed around with it and what i did was i put in ' fastboot flash recovery ' and then draged the file in and then did it and now its working and ive rooted my device

Thanks
[Android General] scaIIy:
Phone sent for repair
[Android General] Toni2345:
Please Help

Whenever i try to flash the custom recovery a This happens in adb C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery huawei-y6-elite-twrp-3.0.2.img

target reported max download size of 134217728 bytes

sending 'recovery' (11044 KB)...

OKAY [ 1.068s]

writing 'recovery'...

FAILED (remote: failed to get download permission because status is locked!)

finished. total time: 1.092s:(
[Android General] m00nlight3r:
not able to root huawei LYO-L02

HI everyone,

Ok im new to this so bare with me. Im trying to root my Huawei y6 Elite. I have followed the instructions(from in here) to the letter and everything went according to plan but when i go to check using root checker i get this error

Root access is not properly installed on this device

HUAWEI LYO-L02

Android version 5.1

Stage 1: Super user App : installed

Stage 2: Superuser Binary files Installed

Stage 3: Root User Account Error:

Error: stderr: null, stdout, null, exit_value: 1

So as you can see i really need some help; I hope there is someone out there that can help me it would be most appreciated

Moonlighter:)
[Android General] maoriboi:
I have this device an used this method at the start of the thread months ago when it was first posted an had no problems so the method works fine thanks.

You can alternatively root the phone with

Magisk - A Root & Universal Systemless Interface by topjohnwu.which I'm my opinion is the best root out there today for android 5 up so big thanks to him an his hard work.if you read the thread there it mentions it can be installed without custom recover like Twrp so this can be a way to get a stock recover image for the device as you now have root an still using stock recover.use flashfy to make a backup of stock image.go through the step at the start of thread on how to unlock the boot loader first.then try the way mentioned in the post

Which can be found at

https://www.google.co.nz/url?sa=t&s...DxAB&usg=AOvVaw0qTxicf0kOFDLDL-79NyS6&ampcf=1

This is the latest thread up at the moment.

But alternatively I just installed via Twrp as I found a stock recover for this device.note the latest version of magisk v15.3

Work fine but system less exposed module (sdk22)v.89 will cause boot loop.so in order to make it work use magisk v14.0zip at the bottom of the thread at the link above.An use system less exposed sdk22 v87.3 zip first as for some reason if you try install the latest version which is v89.1 it will cause boot loop also so flash sdk22 v87.3 which can be found here at https://www.google.co.nz/url?sa=t&s...FjAAegQIDxAB&usg=AOvVaw2A5-BuyM3GaodiV1QsBLb8

Now that you have both magisk an exposed (system less) working. open magisk manager now go to download an update to the latest exposed module an this will bring exposed up to v89.0 an not cause boot loop.note don't update magisk to latest version stay on magisk v14.0 but if you don't use exposed just install the latest version of magisk.
[Android General] maoriboi:
Here is a stock recover image for this device (Huawei y6 elite) that works an tested it originally comes from the Huawei A5/Y6ii hope this help you all out

Sorry I removed link as it was broken so I uploaded the file in next post

Thanks
[Android General] maoriboi:
Here is a stock recover image for this device (Huawei y6 elite) that works an tested it originally comes from the Huawei A5/Y6ii hope this help you all out

Flash via Twrp or flashfy

Good luck
[Android General] maoriboi:
! Do the command so only type in'fastboot flash recover' then drop an drag the file Huawei-y6-elite-twrp-3.0.2.img in to the command.an you should be right.
[General Topics] Syam Reddy:
Games nowadays are not products, they are services. This applies to the gaming industry overall but it is particularly evident in mobile games for the following reasons:

Discoverability. This is one of the biggest if not the biggest problem for mobile games. There are just too many of them and to get a game to a place where it markets itself, e.g. top of the free games chart, is close to impossible.

Risk. It is a lot quicker and cheaper to update a game than to develop and release a new one. If you are risk adverse, updating a good game is the preferable choice over releasing a new one with unknown performance.

Audience. This is closely tied with discoverability. If you have a large audience, you probably have a good game. If you do have a good game, your audience will generate more audience through virality without the hurdles of discoverability. If you release multiple games, thus fragmenting your audience you’ll have to put more effort in maintaining your audience in each game and not maintaining your audience means less virality. A case can be made that more games may “spread the risk” but I’d challenge that with the portfolio of the largest mobile companies that often have less than a handful of games that they are updating and rarely launch a sequel.

I know it’s fun to create new titles and sequels to games you like. To be honest there’s nothing wrong with that, I’ve done it quiet a bit some years ago. However if you want to think of it business wise, you really need to get your head around the problems and opportunities of your games in the market they are at.

One last point is that I’d like to make is that updating allows for cycles of improvement. You put out your minimum viable product, analyse its performance and improve it or let it go. That’s a completely different mindset from old-school game development, which I love! but it’s a lot less commercially viable.
[Galaxy S 4 Mini General] Zz~:
So I'm not going to make a super detailed thread... But!

I bought an SCH-i435. I realized it suffered exploits. I told a tier 2 Verizon guy and they footed the bill for an SCH-i435L board because I determined the hardware was absolutely identical minus the rev numbers being generally lower per part on the L.

I parts gallery has a few left on ebay. There was another seller for much cheaper out of the UK.

http://www.ebay.com/itm/OEM-UNLOCKE...745037?hash=item2101e5998d:g:1hQAAOSwDNdV6gfQ

I also researched that the SCH-R890 (serranolteusc) is also identical minus some radio presets and revision variations. View the XDA qualcomm post about changing the available frequencies to better your connection. However no modification is required to get minimal service for me at least.

The reason i9195 roms are not compatible is that they have differing assemblies for the mic/usb and speaker layout. Due to different radio etc requirements, the circuits are combined with additional components.

TWRP

https://dl.twrp.me/serranolteusc/ - flash from odin checking AP

OctOS - 7.1.1 is not stable, marshmallow 6.01 RC3 works just fine

https://www.teamoctos.com/release-builds/ - flash as zip after factory reset from TWRP

It appears to be fully functional. Enjoy. I can't help further I need to start paying attention to working on my razr -> unlegacy + interviews. If you have a problem don't be afraid to think ;)

It should work for your off model too! Use ebay to look for parts and compare them to ensure they are roughly similar.

[IMG="Note the baseband..."]https://s28.postimg.org/mun85d4cd/20131231_220328.jpg[/IMG]
[Galaxy S 4 Mini General] AgentOrange96:
I just purchased a board. I'm looking forward to having an up to date phone while still keeping the size down! Thank you!

Also, I do have a question. You mentioned the SCH-R890 is the same with some minor adjustments. Is this relevant to the R890 board or the R890 ROMs? In other words, if I'm using an i435L board, are these adjustments I'd need to make to make it work better or would that only be something I'd do if I actually had an R890 board?
[Galaxy S 4 Mini General] AgentOrange96:
So after successfully doing this, here are some notes I have:

If you use the SCH-i435L motherboard, all the same bands are enabled as are on the SCH-i435, so there are no issues here. However, by default, the U.S. Cellular ROM tries to connect to U.S. Cellular towers rather than Verizon's. (Which for me where I currently am isn't too big an issue since the two share towers in my area.) To fix this, I edited the build prop according to this post.

The parts I changed/added were:

And while I was there I changed the model name to SCH-i435L for accuracy.

It is important to note that installing TWRP will set the KNOX Warranty flag, which

cannot

be reset at all using any known method. As you're doing a board transplant, I doubt you're going to be worried about voiding your warranty, however there are also security applications (particularly with government positions) where this might matter, if I remember correctly. If you're curious, Google it.

For me, this didn't matter. The last thing is it installed an FM radio app. Sadly, the SCH-i435L is like the SCH-i435 where it does not have the FM radio enabled in hardware, so that didn't work for me.

Overall, holy s*** having an up to date version of Android is amazing! I actually did opt for the weekly nougat built, and the current weekly (as of 2/17/2017) has crashed on me twice, but I have not had any other issues with it. So it's stable enough to satisfy me. And my battery lasts the whole day! (Albeit I'm on wifi most of the time and have Data off) And I've not had my watch disconnect from my phone once! I was afraid it'd be a "The grass is always greener" scenario and I'd end up with some huge drawback, but god, so far it's been totally worth it!

Okay, maybe one small drawback: My Verizon has no idea what phone I have. So terrible.
[Galaxy S 4 Mini General] autur:
tried 7.1.2 successfully

I have an unlocked SCH-i435L (Verizon) and can confirm that the latest Octos build 7.1.2 works just fine. Should caution though that I haven't tried mobile data, as I use it strictly at home as a wireless device. Thanks for posting and encouraging others to try.
[Galaxy S 4 Mini General] Zz25:
So I forgot the email I used with my op account. I'll find out later.

Awesome!!

I have confirmed that there are benefits to using the r890 board (GPS works better and radio is available). However my daily driver has been the i435L since I posted. I like navigation without GPS, honestly. I also cannot guarantee that every r890 and chassis configuration including peripherals will work. My research was bent on the i435L. If someone wants to research it be my guest. I can almost guarantee from my tests that it will work solving the GPS issue. That being I bought a broken phone and swapped the board in to my test build (I have three full sets of parts now)

Edit:

Also to reset Knox just flash stock from Odin. Besides. The warranty is for the board you've replaced therefore voiding the warranty ;)