yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] pndwal:
Thanks.

Sounds about right. Latest ROM is 2018.01.05.

Trying to work out why [MENTION=7986364]kekkkko[/MENTION] is having problems on L01. From what I understand from him, he has loud in call volume and no adjustment.

For me since lineage-14.1-20171226_233047-UNOFFICIAL, AudioFX bug is gone, in call volume level is adjusted by vol up / down rocker buttons for earpiece, headphones, speaker and Bluetooth, and Echo for other caller / call quality is now fixed for phone earpiece.

Do you have Speaker quiet, Echo for other caller (they hear themselves) with Y550 on speaker mode only, or bluetooth quality (in call) problems? If so, should be solved by setting ro.qc.sdk.audio.fluencetype=none in buildprop as long as in call vol rocker adjustment, noise cancellation problems (ie Echo for other caller (they hear themselves)) using phone earpiece, etc are already fixed by ROM updates for you.

With root enabled explorer this can be edited manually. Find /system/build.prop and use text editor. I just use a build.prop editor from playstore for safety / ease of use however.

I didn't have speaker problems you mentioned. Are they ongoing, or fixed permanently after toggling?

Is anyone else experiencing loud in call volume with no adjustment?

Regards, PW.
[Android Q&A, Help & Troubleshooting] desalesouche:
hi all.

http://www.mediafire.com/file/bt46bdpt31cy7xo/lineage-14.1-20180225-UNOFFICIAL-y550.zip

please feed back.
[Android Q&A, Help & Troubleshooting] blairfancy:
Hi all,,

no audio issue detected with january build on my L01. Tested car bluetooth, headset.

not tested handfree speaker nor bluetooth headset.

regards
[Android Q&A, Help & Troubleshooting] pndwal:
Thanks. It now seems it's not a common L01 problem. PW
[Android Q&A, Help & Troubleshooting] blairfancy:
Hi,

After dirty flash phone boot properly. I just noticed that since several rom version charger is not detected properly.

The last working kernel is 3.10.106 compiled in august.

regards

BF
[Android Q&A, Help & Troubleshooting] blairfancy:
With new kernel 3.10.108 there is strange behavior.As you can see in picture bellow ampere app say that phone is charging but in next line it say on battery.
[Android Q&A, Help & Troubleshooting] pndwal:
Working well for me. No issues at all for me so far. Audio seems good. I don't seem to have any charging issues either, but no kernel support for quick charge.

Snapdragon 410 supports Qualcomm Quick Charge 2.0, enabling up to 24 watt charging over micro USB. Hacker and Nato had Quick Charge kernel support for y550 in previous ROMs. Will it be possible to implement this again soon?

Regards & thanks for continuing development for Y550 users. PW.
[Android Q&A, Help & Troubleshooting] fwiep:
Dirty-flashed, wiped cache. All seems well for my daily usage.

Placing calls, receiving calls, media playback, Wifi, camera, flashlight.

Did an extended test of the speaker-mode, microphone muting and volume control using rockers while calling. This is what my L01 does:

- the other caller does not hear any echo of either her own voice or mine (good)

- I hear no echo or distortion while calling, both on normal and handsfree (speaker) mode (good)

- microphone muting works (good)

- I do not need to toggle speaker mode, as I described earlier (good)

- the rockers do work in controlling the volume (good)

- the actual volume difference when dragging (or rocker-ing) the call volume is VERY small

(the audio level has its minimum at about 10% of the slider, its maximum at 100%)

This volume control issue is not critical for me, but others may need and use this feature. Perhaps this is what [MENTION=7986364]kekkkko[/MENTION] described in post #6004.

I found the build.prop file, thanks to [MENTION=7550078]pndwal[/MENTION] 's instructions.

Hope this helps, and thanks for the update!

Frans-Willem
[Android Q&A, Help & Troubleshooting] pndwal:
Yes, for me in call vol adjustment is sufficient, and I guess it is prevented from approaching zero for good reason (eg, so one doesn't assume call has not connected). [MENTION=7986364]kekkkko[/MENTION] never replied re whether he has any vol. adjustment in call, so I'm assuming now that this is working on all models (L01, 02, 03), and that your deduction that he is simply not happy with min volume level is correct.

Please can you and others confirm that buildprop setting ro.qc.sdk.audio.fluencetype=none is working well. (I think that in latest ROM this has now been set to none). For me, this was necessary to fix noise reduction problems (esp. echo for other caller - they hear themselves) with y550 on speaker mode only. Thanks, PW.
[Android Q&A, Help & Troubleshooting] fwiep:
This is my current /system/build.prop file, untouched after flashing [MENTION=4479868]desalesouche[/MENTION] 's latest ROM on my L01. The setting you mention is not there. But neither are the audio-problems (as I described earlier).

# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=NJH47F
ro.build.display.id=lineage_cherry-userdebug 7.1.2 NJH47F 4679e26d75 test-keys
ro.build.version.incremental=4679e26d75
ro.build.version.sdk=25
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=7.1.2
ro.build.version.security_patch=2018-02-05
ro.build.version.base_os=
ro.build.date=dimanche 25 février 2018, 17:41:16 (UTC+0100)
ro.build.date.utc=1519576876
ro.build.type=userdebug
ro.build.user=desalesouche
ro.build.host=desalesouche-NoGiveUp
ro.build.tags=test-keys
ro.build.flavor=lineage_cherry-userdebug
ro.product.model=cherry
ro.product.brand=Huawei
ro.product.name=lineage_cherry

Thanks for digging into this,

Frans-Willem
[Android Q&A, Help & Troubleshooting] pndwal:
Well it is there, set to none, further down under # Audio.

Build.prop file is about 7 times longer than this with settings for # build properties, # Audio, # Display, # HWUI, # Radio, # camera debug, # Storage, and # ADDITIONAL_BUILD_PROPERTIES.

You seem to have captured only initial lines that fit on y550 screen in portrait mode.

If you find ro.qc.sdk.audio.fluencetype=none and set to 'fluence', I will be interested in whether noise reduction problems with y550 on speaker (ie echo for other caller - they hear themselves) return. I'm pretty sure 'none' setting was needed to cure it.

Thanks to [MENTION=4479868]desalesouche[/MENTION] for restoring stock 'none' setting in latest ROM. PW.
[Android Q&A, Help & Troubleshooting] fwiep:
You are absolutely right, on both fronts. The build.prop file is indeed longer. The setting was there and set to 'none'.

I used adb shell, su - and vim /system/build.prop to view the file. This local version of vim seems to be limited to 24 lines.

I set it to 'fluence' and restarted. Then performed a test call and behold: the person being called heard herself back (echo) and described my voice as 'very sharp, very digital'.

Incidentally, the crackle-sound I described earlier in post #5844 has returned with this setting.

Case confirmed, it seems.

Frans-Willem
[Android Q&A, Help & Troubleshooting] pndwal:
Thanks. Just for clarity, did test setting 'fluence' produce echo for other caller on speaker mode only, or did it affect earpiece also? PW
[Android Q&A, Help & Troubleshooting] fwiep:
No, there was no echo during non-speaker mode.
[Android Q&A, Help & Troubleshooting] pndwal:
That's what I thought. I was searching for cure for speaker mode, but didn't want to affect calls over earpiece for other Y550 users.

Seems other in call audio problems have been fixed by [MENTION=4479868]desalesouche[/MENTION]'s refined commits in last couple of ROMs, but previous experiments to fix noise reduction problems by altering buildprop settings resulted in ro.qc.sdk.audio.fluencetype=fluence being adopted as some felt it improved in call audio (and before ROM updates this did in fact have a marked effect on calls over earpiece also, possibly improving them, although I experienced echo for other caller using earpiece also at that time).

Seems to be confirmed that since ROM updates, ro.qc.sdk.audio.fluencetype=fluence setting now only serves to degrade calls over speaker and cause other problems, so this should now be set to 'none' as in stock ROM.

Thanks for your input / confirmation of this. Happy to hear it fixes your crackle-sound too. PW
[Android Q&A, Help & Troubleshooting] stmr:
As far as I remember, there were always problems with fluence, we used to fix them by using fluencepro (which didn't solve all the problems), have yet to test none on my device
[Android Q&A, Help & Troubleshooting] pndwal:
My recollection too, - very limited success with either fluence or fluencepro, or the other buildprop changes suggested - always had issues, and now that audio issues have been largely fixed in latest ROMs, these settings seem only to degrade speaker mode use (as well as causing Bluetooth problems on some headsets, and crackle-sound according to [MENTION=7866480]fwiep[/MENTION]). 'fluence' causes echo for other caller, and 'fluencepro' caused other party not to hear anything the once I tried it (speaker mode only), and both caused very low speaker volume (only with 'none' setting is speaker volume level useful / adequate).

In latest ROM this has been restored to 'none' in any case (was 'none' in stock ROM too), so after updating you'll necessarily be testing 'none' setting. You shouldn't have any issues, but you can try setting to 'fluence' / 'fluencepro' to confirm that these cause speaker mode problems etc. PW
[Android Q&A, Help & Troubleshooting] desalesouche:
los 7.1.2 update coming...

hi guys , new upate coming ... some kernel update about sound/cve/bug resolution.
[Android Q&A, Help & Troubleshooting] desalesouche:
hi.sorry for being late... too much work and some problems with laptop i hope i solved.
[Android Q&A, Help & Troubleshooting] rudolfm:
We are thankfull for everything we get. Nothing to be sorry for.
[Android Q&A, Help & Troubleshooting] pndwal:
If in call volume is still too high with vol rocker at minimum, try this:

Adjust in-call volume

You need root and root explorer.

Go to system/etc, there is file named mixer_paths_qrd_skuh.xml

Make backup of that file before you start!

Look for this code (its almost at the end of file):

<path name="handset">

<ctl name="RX1 MIX1 INP1" value="RX1" />

<ctl name="RDAC2 MUX" value="RX1" />

<ctl name="RX1 Digital Volume" value="84" />

<ctl name="EAR PA Gain" value="POS_6_DB" />

<ctl name="EAR_S" value="Switch" />

</path>

You have to change value in this line:

<ctl name="RX1 Digital Volume" value="84" />

Try 80, 76 etc, eg:

<ctl name="RX1 Digital Volume" value="80" />

Save the file, (may need to reset permissions to rw-r-r), reboot phone and check if in call volume level is suitable.

Please let us know if it is better for you / works. I can't try as I need to replace erratic digitiser / screen lens. Hope it helps, PW.
[Android Q&A, Help & Troubleshooting] kekkkko:
<path name="handset">

<ctl name="RX1 MIX1 INP1" value="RX1" />

<ctl name="RDAC2 MUX" value="RX1" />

<ctl name="RX1 Digital Volume" value="76" />

<ctl name="EAR PA Gain" value="POS_6_DB" />

<ctl name="EAR_S" value="Switch" />

</path>

the volume is high
[Android Q&A, Help & Troubleshooting] pndwal:
So it didn't change at all? If it did, try lower value. PW.
[Android Q&A, Help & Troubleshooting] kekkkko:
I try with value 55 and it seems improved

thanks
[Android Q&A, Help & Troubleshooting] pndwal:
Good to hear. I was hoping kernel responds to these values as research suggests it should.

Since I updated ROM on my wifes y550, in call volume seems a bit loud to us too, but we're happy everything seems to work as it should including noise reduction and volume adjustment.

Please let us know:

With value set to 55, do you still use phone on minimum volume? Do you have reasonable volume adjustment between minimum and maximum?

Also, could you confirm that it doesn't affect anything else, eg speaker or headset volume, or voice quality. Thanks, PW.
[Android Q&A, Help & Troubleshooting] yeshayh:
Hello everyone, again me.

As my phone Huawei Y550 L03 died completely after finishing the flashing of the stock rom (I think they were sequels that left the modified ROMs in some critical partition), I decided to buy the same phone to try to recover the other broken phone. The problem is that to make a backup of the firmware to the phone that I bought I need to enable the USB diagnostic mode and even though I tried everything does not enter that mode (when I from adb or terminal emulator send the command setprop sys.usb. config diag,adb the only thing that happens is that the PC no longer detects the phone, also being off the phone, I try with combinations of keys and connecting the USB cable but I do not succeed).

So my question is if someone who is running a modified ROM tried to enable the USB diagnostic mode and he answers me if he could do it, because with the stock rom I could not or does not support it.

Thank you ;)
[Android Q&A, Help & Troubleshooting] pndwal:
What about this question?

Thanks, PW.
[Android Q&A, Help & Troubleshooting] kekkkko:
I wrote

<path name="handset">

<ctl name="RX1 MIX1 INP1" value="RX1" />

<ctl name="RDAC2 MUX" value="RX1" />

<ctl name="RX1 Digital Volume" value="55" />

<ctl name="EAR PA Gain" value="POS_6_DB" />

<ctl name="EAR_S" value="Switch" />

</path>

The value 55 should be the minimum if that it's wrong how will do I change minimum and maximum value?

but it seems that there are some interferences and the people don't listen me very well .I think that change doesn't affect anything else,when I use headphones to call volume remains high
[Android Q&A, Help & Troubleshooting] pndwal:
Thanks for that.

I meant minimum volume, and reasonable volume adjustment using volume rocker buttons. Do you leave it at maximum, or adjust down (during a call)?

I haven't had interference (or noise reduction - incl. echo for other caller) problems since last few ROM updates so this is strange.

I'll try lower value setting too, after I replace my digitizer (touchscreen lens). PW.
[Android Q&A, Help & Troubleshooting] desalesouche:
7.1.2 update coming

kernel change : https://github.com/HUAWEI-Y550-Y635/android_kernel_huawei_msm8916/commits/los-14.1

http://www.mediafire.com/file/6ih5wr3j6xcljb6/lineage-14.1-20180315-UNOFFICIAL-y550.zip
[Android Q&A, Help & Troubleshooting] yeshayh:
As I said before, nothing works, I press the buttons with the different combinations to enter recovery, dload or fastboot etc and nothing happens, no vibration, the led does not flash, the screen does not turn on, the phone is completely dead but can be recovered.
[Android Q&A, Help & Troubleshooting] blairfancy:
Phone upgraded with this version charging issue is still there then downgraded kernel to august 2017 one. Still test system and ll report any other bug

regards

BF
[Android Q&A, Help & Troubleshooting] desalesouche:
I made nothing for now about charging issue. Will have a look at that later when I will have more time. Thanks for feed back and telling me remaining bugs.
[Android Q&A, Help & Troubleshooting] pndwal:
Thanks for confirming no response at all with dload. Had in mind some reasons dload may fail, but these are clearly not the problem.

Not sure about USB diagnostic mode but after Enable Android Debugging, may need to make sure MTP and PTP are not enabled when connecting (Storage > USB computer connection).

Re QDLoader 9008, found good guide which may help here:

https://www.droidsavvy.com/unbrick-qualcomm-mobiles/

Learned about old and new Qualcomm HS-USB QDLoader 9008 modes, and forcing old mode etc. May need to substitute some Qualcomm files, eg uses prog_emmc_firehose_8936.mbn. Snapdragon 410 probably requires prog_emmc_firehose_8916.mbn.

Found prog_emmc_firehose_8916.mbn here:

https://github.com/openpst/assets/blob/master/programmers/Unidentified/prog_emmc_firehose_8916.mbn

Found collection of others (incl alternative 8916 files) here:

https://www.leakite.com/2017/07/collection-qualcomm-emmc-programmer-files.html

Can find original info re unbrick-qualcomm from XDA thread: [PROJECT] Reviving Hard Bricked YU (QLoader 9008 Mode) by tirta.agung, here:

https://xdaforums.com/yureka/help/question-qualcomm-download-mode-k-t3068040. Very interesting reading. (Some file links no longer work).

Sorry if my questions sounded annoying / impertinent, but I'm happy to help however I can. Please let us know if anything here helps and re your progress which could very well be invaluable to other Y550 users in same jam. All the best with it, and with retrieving critical files from new stock Y550. PW.
[Android Q&A, Help & Troubleshooting] fwiep:
All OK for my daily usage, so far. Dirty-flashed this ROM and OpenGApps.

Then discovered that the root-option "apps and adb" was no longer available. So I flashed the LineageOS-su-add-on.

https://download.lineageos.org/extras, choose "14.1" and "arm".

I am looking forward to this month's security updates; they are not contained in this ROM.

Thank you very much.

Frans-Willem
[Android Q&A, Help & Troubleshooting] rudolfm:
I did a dirty flash and I still have the root-option "apps and adb".
[Android Q&A, Help & Troubleshooting] fwiep:
Confirmed on a clean flash. All root-options are present by default.

Must have been a glitch on my device.

Thanks,

Frans-Willem
[Android Q&A, Help & Troubleshooting] felix-development:
Hello guys. As I ordered a new motherboard and a new battery for my Huawei Ascend Y550 (it's still on it's way) and I still need to wait for a firmware update on my new phone to work with project treble I like to inform everyone I gonna be back here in msm8916 world for this time and try the best I could to develop ROMs for this device... As soon as my device is repaired, I gonna run a test build of RR to see if everything works as I expect. Looking forward to oreo too... ;) It would be also nice if someone can link me the kernel source of our phone.. Regards

Edit: Found the Kernel Source already
[Android Q&A, Help & Troubleshooting] pndwal:
Guess you found it here: https://xdaforums.com/android/development/huawei-y550-development-t3425524. If not, worth a look again. (Post #2 maintained by [MENTION=6726815]Saint_13[/MENTION]. -post #3 was yours).

Dont forget to flash 4XQWT_LP_Modem first time moving up from stock. PW.
[Android Q&A, Help & Troubleshooting] Genetyk:
Hello, I tried unnecessary programs in Huawei Y560-L01 and accidentally deleted the applications responsible for setting the keyboard and system language after selecting this option in the settings now nothing happens or someone would be able to send me these applications so that I could reinstall them on the phone and the menu again worked
[Android Q&A, Help & Troubleshooting] desalesouche:
https://github.com/HUAWEI-Y550-Y635/android_kernel_huawei_msm8916/commits/los-14.1
[Android Q&A, Help & Troubleshooting] pndwal:
??? - are you running stock ROM? Rooted? Running Lineage custom ROM from here?

If on lineage, suggest you simply reflash the rom (dirty flash, but wipe Cache & Dalvik / ART Cache) to restore system apps. PW.
[Android Q&A, Help & Troubleshooting] Genetyk:
I have stock room and root but i don't have unlock bootloader to install custom rom
[Android Q&A, Help & Troubleshooting] pndwal:
How did you root without unlocked bootloader?

Why don't you join the club n try LineageOS 14.1 (Android N)?

Follow unlock bootloader instructions post #2 here:

https://xdaforums.com/android/development/huawei-y550-development-t3425524 to get code (

works only on PC

- now in English too)

See Installing Custom Recovery (post #2 link above) to flash twrp.

Flash Lineage (post #6039 here is latest), modem update (post #2 link above) and 32 bit open gapps (I use nano). SuperSU root is inbuilt, but I flash latest Magisk... And your done! PW.
[Android Q&A, Help & Troubleshooting] Genetyk:
I have y560 and Huawei don't send me unlock code

I have B046 ver. Rom and i need unlock code to unlock bootloader?
[Android Q&A, Help & Troubleshooting] pndwal:
Ok, so this is wrong forum for you. This is

Everything y550.

But I think you can use info in link I posted to get unlock code directly from official Huawei forum. Most Huawei model numbers are supported. I think they haven't responded to personal requests for unlock codes for several years now.

Make sure there is TWRP and custom or stock rom specifically for y560 before flashing. Either should fix your problems. PW.
[Android Q&A, Help & Troubleshooting] Genetyk:
I know it's a forum about y550 but nobody answered right

I have received information from Huawei that my model can not get the code for the bootloader
[Android Q&A, Help & Troubleshooting] pndwal:
You may be right. Not familiar with Y560, but many sites say this method unlocks any Huawei phone, so I'd try anyway. Nothing ventured nothing gained.

[Seems you can use MV Unlocker (edit: don't use - seems may include malware - posts #6059, 6060) and other methods too,] but I know nothing about these. PW.
[Android Q&A, Help & Troubleshooting] kekkkko:
are you developing rom with oreo go edition?
[Android Q&A, Help & Troubleshooting] Genetyk:
This is malware!
[Android Q&A, Help & Troubleshooting] pndwal:
My bad. You're probably right. Avoid this.

DC Unlocker / Phoenix is good, but requires nominal payments for services (unlocking, fixing corrupt partitions, IMEI & SN loss etc). PW
[Android Q&A, Help & Troubleshooting] sole4ce:
Dear [MENTION=4479868]desalesouche[/MENTION] please port Oreo go rom for us. Thank you
[Android Q&A, Help & Troubleshooting] pndwal:
Looks like once / if we get LineageOS 15.1 (Android 8.1), you'll be able to turn it (in fact any Android 8.1 Oreo ROM) into an Android Go-Optimized version (ie downgrade to Android Go-Optimized version) in any case if that's your wish, simply by flashing Low RAM Property Patcher from here:

https://www.xda-developers.com/android-oreo-android-go-low-ram-patcher/

Or developers thread here:

https://xdaforums.com/android/software-hacking/mod-low-ram-property-patcher-android-t3737373

Or Magisk module here:

https://xdaforums.com/apps/magisk/magisk-module-low-ram-property-patcher-t3740199

So seems may be best just to wait for LineageOS 15.1 which appears to be [MENTION=4479868]desalesouche[/MENTION]'s WIP, and then try the patch.

Doing this, you'll necessarily have a more stable / bug free OS (still based on the much refined and streamlined unofficial Cherry - for our snapdragon 410 device) than you would have with any fresh port from an Android Go device (mostly available only for later snapdragon 200 series, etc). At least that's how I see it.

Additional info:

"Developers should get less requests to compile with or without Go just because one user wants to have a feature (multitasking for example) re-enabled or to force low-ram changes."

"The target system is Oreo, but the low-ram property was introduced since Android KitKat 4.4, therefore it should work on other versions, unless the ROM developers did not validate the low-RAM UI changes (recent apps UI mostly) against the additions they made."

"Features affected by the low-ram property: Flat recent / multitasking UI,

multi-users disabled, high-end graphics disabled, less recent apps cache,

multi-windows disabled, minor notification icons changes, less logger buffer sizes (devs), no apps notifications access / zen access / VR listeners / picture in picture (PIP) accesses."

Edit: Some are requesting Open Gapps to 'Add Google go edition packages'. Apparently (they claim) Lineage OS will ship Android Go in 15.1. See: https://github.com/opengapps/opengapps/issues/589

I ran Magisk module, and low-ram property flag had the expected effect. Of course, in playstore this will not invoke "Go" optimised apps automatically unless running on Oreo ROM. However these streamlined / light apps are already available from 'Comparable app available' notice. [Eg. selecting Maps (Google) notifies you that Google Maps Go is available as Comparable app]. This makes it possible to manually achieve most of the 'Go' optimisations without Oreo (Ie. by flagging the low-ram property to adjust / disable the 'higher-end' features listed above, and by swapping out standard apps for Go edition apps) PW.