Update hotfix!
So, if you're having the same issue as described below, the solution is apparently to contact HTC support.
Explain to them you have this issue, you could also mention this thread and they should ask you for your SN or IMEI.
A few days later you can check for an update and you should be able to find one. It's about 70MB and only includes the hotfix, nothing else.
This is the direct link to the OTA (European?) if you wish to install it manually:
http://fotadl.htc.com/OTA_IMAGINE_D...2.55.401.1_release_549055s9q6pz2h8oow5ojn.zip
The problem
Ever since the android 9/pie update I've been having issues with my microphone during speaker calls and video calls.
Normally I call my girlfriend every day using a video call in WhatsApp or wechat. But after the upgrade she said: what happened? I can barely hear you.
As it seems, when the phone is in speaker mode during a call, the volume of the microphone from my phone is too low. Unless I shout, the other party can't hear me.
The weird thing is that the microphone seems to work fine in other cases like when you hold the phone to your ear for a phone call, video recording or even voice clip recording. Only speaker mode has issues somehow.
What I've tried
I've factory reset my phone already, without any improvement whatsoever. It seems to me that this is a bug in the update.
Use of this thread
I'd like this thread to be a place for people to find each other with the same problem, and possibly fix it. Or have at least a collection of people to tell HTC: fix this.
List of users with the same problem
Other users, reported so far:
@AtAM1
@harvey1483
@Dehypnotizer
Response HTC and test
I've contacted the HTC live chat support and described the issue. They recommended me to test the following:
A) Dial *#*#3424#*#* and run the diagnostic tool for the audio test and check the Microphone performance.
B) Sometimes the downloaded applications conflicts with the phone's OS making it not to perform in a normal way, so please try to use the phone in the safe mode by following the steps below:
1.Press and hold “power key “till you see the options of Power off and restart option
2. Press and hold on the screen on the power off option till you can reboot to safe mode
4. “Safe Mode “text will appear on the lower left of screen.
C) Check for updates from Menu> Settings> About> Software Updates (preferably using Wi-Fi)
D) If you followed these steps and the issue is resolved, it means that you have downloaded 3rd party application downloaded from the internet which conflicts with you device OS. Please remove it from:
Menu>settings>applications >downloaded >click on the applications and un-install them.
F) If you followed these steps still the same issue, please back up your phone information as resetting your phone will erase your phone data completely and follow the step below:
Menu>settings>Backup & Reset>Reset phone.
Click to expand...
Click to collapse
I'll try this tonight myself and report my findings.
If these test come back negative, the HTC expert told me then he wants my phone for repair. It's unlikely I'll do that however, since I believe this is a software issue and not hardware.
Final response HTC
The tests HTC told me to do passed successfully. After sending a link to this thread with @AtAM1 findings, they made a flag for it for the developers.
The HTC expert told me she hoped it would be solved soon.
Now we wait?
Thanks for making a dedicated thread to cover this bug.
I tried all sorts of hardware and software tests including the ones recommended by HTC in your post but nothing helped.
The only thing I haven't tried is resetting the phone which I am dredding as many services are tied to app activations.. If I had to though, I'll probably unlock the phone and switch to LeeDroid's rom (root) for more troubleshooting and customization options.
However, I did google this issue and it seems it's a software bug, specifically with the OS and mainly with Pie, and nothing to do with the hardware.
Quick update: The bug is most likely with incorrect values set/used for the properties persist.audio.fluence* and ro.qc.sdk.audio.fluencetype and more generally persist.audio* / ro.qc.sdk.audio*. Only way to rectify it without having to wait for a fix from HTC is to root the phone and mod build.prop
Can anyone running factory RUU under Oreo share with us their getprop output via adb shell?
Thank you
Edit: Forgot to mention - The issue still persists after resetting the phone or reflashing Oreo RUU then upgrading to Pie
Update 2: I managed to get the getprop values from Oreo 1.53 - key differences are HTC seems to have either dropped or forgotten to add and/or port over vendor specific values to Pie, specifically:
Missing Properties / Values in Pie [Audio related]
Code:
-[persist.vendor.audio.fluence.speaker]: [true]
-[persist.vendor.audio.fluence.voicecall]: [true]
-[persist.vendor.audio.fluence.voicerec]: [false]
-[persist.vendor.audio.headset.anc.type]: [feedback]
-[persist.vendor.audio.ras.enabled]: [false]
-[vendor.audio.adm.buffering.ms]: [2]
-[vendor.audio.dolby.ds2.enabled]: [false]
-[vendor.audio.dolby.ds2.hardbypass]: [false]
-[vendor.audio.enable.dp.for.voice]: [false]
-[vendor.audio.flac.sw.decoder.24bit]: [true]
-[vendor.audio.hw.aac.encoder]: [true]
-[vendor.audio.noisy.broadcast.delay]: [600]
-[vendor.audio.offload.buffer.size.kb]: [1024]
-[vendor.audio.offload.multiaac.enable]: [true]
-[vendor.audio.offload.multiple.enabled]: [true]
-[vendor.audio.offload.passthrough]: [false]
-[vendor.audio.offload.pstimeout.secs]: [3]
-[vendor.audio.offload.track.enable]: [true]
-[vendor.audio.parser.ip.buffer.size]: [262144]
-[vendor.audio.safx.pbe.enabled]: [true]
-[vendor.audio.tunnel.encode]: [false]
-[vendor.audio.use.sw.alac.decoder]: [true]
-[vendor.audio.use.sw.ape.decoder]: [true]
-[vendor.voice.path.for.pcm.voip]: [true]
Unchanged Properties / Values in Pie [Audio related]
Code:
[persist.audio.fluence.speaker]: [true]
[persist.audio.fluence.voicecall]: [true]
[persist.audio.fluence.voicerec]: [false]
[vendor.audio_hal.in_period_size]: [144]
[vendor.audio_hal.period_multiplier]: [3]
[vendor.audio_hal.period_size]: [192]
New Properties / Values in Pie [Audio related]
Code:
+[media.stagefright.audio.deep]: [true]
Another major change to how the microphone is managed under pie (audio_platform_info.xml)-
Code:
@@ -239,6 +239,7 @@
<usecase name="USECASE_AUDIO_RECORD_LOW_LATENCY" type="in" id="17" />
<usecase name="USECASE_AUDIO_PLAYBACK_ULL" type="out" id="17" />
<usecase name="USECASE_AUDIO_PLAYBACK_EXT_DISP_SILENCE" type="out" id="27" />
+ <usecase name="USECASE_AUDIO_A2DP_ABR_FEEDBACK" type="in" id="40" />
</pcm_ids>
<config_params>
<param key="spkr_1_tz_name" value="wsatz.13"/>
@@ -349,6 +350,388 @@
<device name="SND_DEVICE_IN_HEADSET_AS20_AMBIENT" interface="SLIMBUS_0_TX"/>
<!-- HTC BACKEND END -->
</backend_names>
+ <!-- below values are hardware info from audio HW team: [email protected] -->
+ <microphone_characteristics>
+ <microphone valid_mask="31" device_id="builtin_mic_1" type="AUDIO_DEVICE_IN_BUILTIN_MIC" address="bottom" location="AUDIO_MICROPHONE_LOCATION_MAINBODY"
+ group="0" index_in_the_group="0" directionality="AUDIO_MICROPHONE_DIRECTIONALITY_OMNI" num_frequency_responses="93"
+ frequencies="100.00 106.00 112.00 118.00 125.00 132.00 140.00 150.00 160.00 170.00 180.00 190.00 200.00 212.00 224.00 236.00 250.00 265.00 280.00 300.00 315.00 335.00 355.00 375.00 400.00 425.00 450.00 475.00 500.00 530.00 560.00 600.00 630.00 670.00 710.00 750.00 800.00 850.00 900.00 950.00 1000.00 1060.00 1120.00 1180.00 1250.00 1320.00 1400.00 1500.00 1600.00 1700.00 1800.00 1900.00 2000.00 2120.00 2240.00 2360.00 2500.00 2650.00 2800.00 3000.00 3150.00 3350.00 3550.00 3750.00 4000.00 4250.00 4500.00 4750.00 5000.00 5300.00 5600.00 6000.00 6300.00 6700.00 7100.00 7500.00 8000.00 8500.00 9000.00 9500.00 10000.00 10600.00 11200.00 11800.00 12500.00 13200.00 14000.00 15000.00 16000.00 17000.00 18000.00 19000.00 20000.00"
+ responses="-0.9 -0.9 -0.8 -0.7 -0.5 -0.4 -0.7 -0.4 -0.6 -0.6 -0.6 -0.7 -0.7 -0.8 -0.6 -0.4 -0.5 -0.6 -0.6 -0.3 -0.5 -0.7 -0.5 -0.7 -0.7 -0.7 -0.7 -0.7 -0.6 -0.5 -0.4 -0.4 -0.5 -0.3 -0.2 -0.6 -0.8 -0.7 -0.5 -0.2 0.0 0.1 1.0 1.4 1.6 1.5 1.5 1.9 2.1 2.2 2.4 2.6 2.8 2.9 3.0 2.8 2.7 3.1 3.4 3.2 3.3 4.0 5.2 6.5 7.2 9.7 10.4 9.1 8.2 11.4 13.8 17.1 18.9 17.1 18.9 17.7 24.0 22.6 25.4 23.1 24.0 16.2 14.5 11.8 9.3 5.1 5.2 5.1 5.3 5.6 5.8 5.2 5.1"
+ sensitivity="-37.0" max_spl="132.5" min_spl="28.5" orientation="0.0 -1.0 0.0" geometric_location="0.0510 0.0 0.0022" />
+ <microphone valid_mask="31" device_id="builtin_mic_2" type="AUDIO_DEVICE_IN_BACK_MIC" address="back" location="AUDIO_MICROPHONE_LOCATION_MAINBODY"
+ group="0" index_in_the_group="1" directionality="AUDIO_MICROPHONE_DIRECTIONALITY_OMNI" num_frequency_responses="93"
+ frequencies="100.00 106.00 112.00 118.00 125.00 132.00 140.00 150.00 160.00 170.00 180.00 190.00 200.00 212.00 224.00 236.00 250.00 265.00 280.00 300.00 315.00 335.00 355.00 375.00 400.00 425.00 450.00 475.00 500.00 530.00 560.00 600.00 630.00 670.00 710.00 750.00 800.00 850.00 900.00 950.00 1000.00 1060.00 1120.00 1180.00 1250.00 1320.00 1400.00 1500.00 1600.00 1700.00 1800.00 1900.00 2000.00 2120.00 2240.00 2360.00 2500.00 2650.00 2800.00 3000.00 3150.00 3350.00 3550.00 3750.00 4000.00 4250.00 4500.00 4750.00 5000.00 5300.00 5600.00 6000.00 6300.00 6700.00 7100.00 7500.00 8000.00 8500.00 9000.00 9500.00 10000.00 10600.00 11200.00 11800.00 12500.00 13200.00 14000.00 15000.00 16000.00 17000.00 18000.00 19000.00 20000.00"
+ responses="-0.9 -0.9 -0.8 -0.7 -0.5 -0.4 -0.7 -0.4 -0.6 -0.6 -0.6 -0.7 -0.7 -0.8 -0.6 -0.4 -0.5 -0.6 -0.6 -0.3 -0.5 -0.7 -0.5 -0.7 -0.7 -0.7 -0.7 -0.7 -0.6 -0.5 -0.4 -0.4 -0.5 -0.3 -0.2 -0.6 -0.8 -0.7 -0.5 -0.2 0.0 0.1 1.0 1.4 1.6 1.5 1.5 1.9 2.1 2.2 2.4 2.6 2.8 2.9 3.0 2.8 2.7 3.1 3.4 3.2 3.3 4.0 5.2 6.5 7.2 9.7 10.4 9.1 8.2 11.4 13.8 17.1 18.9 17.1 18.9 17.7 24.0 22.6 25.4 23.1 24.0 16.2 14.5 11.8 9.3 5.1 5.2 5.1 5.3 5.6 5.8 5.2 5.1"
+ sensitivity="-37.0" max_spl="132.5" min_spl="28.5" orientation="0.0 0.0 1.0" geometric_location="0.037 0.0195 0.0024" />
+ <microphone valid_mask="31" device_id="builtin_mic_3" type="AUDIO_DEVICE_IN_BUILTIN_MIC" address="front" location="AUDIO_MICROPHONE_LOCATION_MAINBODY"
+ group="0" index_in_the_group="2" directionality="AUDIO_MICROPHONE_DIRECTIONALITY_OMNI" num_frequency_responses="93"
+ frequencies="100.00 106.00 112.00 118.00 125.00 132.00 140.00 150.00 160.00 170.00 180.00 190.00 200.00 212.00 224.00 236.00 250.00 265.00 280.00 300.00 315.00 335.00 355.00 375.00 400.00 425.00 450.00 475.00 500.00 530.00 560.00 600.00 630.00 670.00 710.00 750.00 800.00 850.00 900.00 950.00 1000.00 1060.00 1120.00 1180.00 1250.00 1320.00 1400.00 1500.00 1600.00 1700.00 1800.00 1900.00 2000.00 2120.00 2240.00 2360.00 2500.00 2650.00 2800.00 3000.00 3150.00 3350.00 3550.00 3750.00 4000.00 4250.00 4500.00 4750.00 5000.00 5300.00 5600.00 6000.00 6300.00 6700.00 7100.00 7500.00 8000.00 8500.00 9000.00 9500.00 10000.00 10600.00 11200.00 11800.00 12500.00 13200.00 14000.00 15000.00 16000.00 17000.00 18000.00 19000.00"
+ responses="-0.9 -0.9 -0.8 -0.7 -0.5 -0.4 -0.7 -0.4 -0.6 -0.6 -0.6 -0.7 -0.7 -0.8 -0.6 -0.4 -0.5 -0.6 -0.6 -0.3 -0.5 -0.7 -0.5 -0.7 -0.7 -0.7 -0.7 -0.7 -0.6 -0.5 -0.4 -0.4 -0.5 -0.3 -0.2 -0.6 -0.8 -0.7 -0.5 -0.2 0.0 0.1 1.0 1.4 1.6 1.5 1.5 1.9 2.1 2.2 2.4 2.6 2.8 2.9 3.0 2.8 2.7 3.1 3.4 3.2 3.3 4.0 5.2 6.5 7.2 9.7 10.4 9.1 8.2 11.4 13.8 17.1 18.9 17.1 18.9 17.7 24.0 22.6 25.4 23.1 24.0 16.2 14.5 11.8 9.3 5.1 5.2 5.1 5.3 5.6 5.8 5.2 5.1"
+ sensitivity="-37.0" max_spl="132.5" min_spl="28.5" orientation="0.0 0.0 -1.0" geometric_location="0.0235 0.1445 0.0022" />
+ <microphone valid_mask="31" device_id="builtin_mic_4" type="AUDIO_DEVICE_IN_BUILTIN_MIC" address="top" location="AUDIO_MICROPHONE_LOCATION_MAINBODY"
+ group="0" index_in_the_group="3" directionality="AUDIO_MICROPHONE_DIRECTIONALITY_OMNI" num_frequency_responses="93"
+ frequencies="100.00 106.00 112.00 118.00 125.00 132.00 140.00 150.00 160.00 170.00 180.00 190.00 200.00 212.00 224.00 236.00 250.00 265.00 280.00 300.00 315.00 335.00 355.00 375.00 400.00 425.00 450.00 475.00 500.00 530.00 560.00 600.00 630.00 670.00 710.00 750.00 800.00 850.00 900.00 950.00 1000.00 1060.00 1120.00 1180.00 1250.00 1320.00 1400.00 1500.00 1600.00 1700.00 1800.00 1900.00 2000.00 2120.00 2240.00 2360.00 2500.00 2650.00 2800.00 3000.00 3150.00 3350.00 3550.00 3750.00 4000.00 4250.00 4500.00 4750.00 5000.00 5300.00 5600.00 6000.00 6300.00 6700.00 7100.00 7500.00 8000.00 8500.00 9000.00 9500.00 10000.00 10600.00 11200.00 11800.00 12500.00 13200.00 14000.00 15000.00 16000.00 17000.00 18000.00 19000.00"
+ responses="-0.9 -0.9 -0.8 -0.7 -0.5 -0.4 -0.7 -0.4 -0.6 -0.6 -0.6 -0.7 -0.7 -0.8 -0.6 -0.4 -0.5 -0.6 -0.6 -0.3 -0.5 -0.7 -0.5 -0.7 -0.7 -0.7 -0.7 -0.7 -0.6 -0.5 -0.4 -0.4 -0.5 -0.3 -0.2 -0.6 -0.8 -0.7 -0.5 -0.2 0.0 0.1 1.0 1.4 1.6 1.5 1.5 1.9 2.1 2.2 2.4 2.6 2.8 2.9 3.0 2.8 2.7 3.1 3.4 3.2 3.3 4.0 5.2 6.5 7.2 9.7 10.4 9.1 8.2 11.4 13.8 17.1 18.9 17.1 18.9 17.7 24.0 22.6 25.4 23.1 24.0 16.2 14.5 11.8 9.3 5.1 5.2 5.1 5.3 5.6 5.8 5.2 5.1"
+ sensitivity="-37.0" max_spl="132.5" min_spl="28.5" orientation="0.0 1.0 0.0" geometric_location="0.0546 0.1456 0.00415" />
+ </microphone_characteristics>
.... continued see attached file.
Could you respond to HTC and share the above with them so it is escalated to their dev team for an urgent fix release?
Thanks
Wow, amazing stuff @AtAM1 !
I've just relayed the information to HTC, I talked to Arya and she promised she raised a flag at the development team.
Not sure how soon to expect a fix for this with the current state of HTC, but I hope we'll get it soon.
Unluckily same issue after pie update! And now? I know Htc and probably we have to wait Android Q if u12+ will receive it.
harvey1483 said:
Unluckily same issue after pie update! And now? I know Htc and probably we have to wait Android Q if u12+ will receive it.
Click to expand...
Click to collapse
The same bug here. People can't hear what I'm saying while in Speaker Mode.
Have you noticed another sound-related bug? Pressing Volume Up/Down changes volume of the media, not the ring tone.
This is almost as much annoying as messed up microphone's settings.
I just hope HTC is alive enough to release yet another fix OTA.
Dehypnotizer said:
Have you noticed another sound-related bug? Pressing Volume Up/Down changes volume of the media, not the ring tone.
Click to expand...
Click to collapse
This is NOT a bug. This is how Pie works in other devices, not just HTC. Definitely more logical as people don't always change ringtone volume all the time and it can even ruin your "default" ringtone volume level by accidentally increasing/decreasing it.
This post should've been deleted, sorry for that.
ijuanp03 said:
This is NOT a bug. This is how Pie works in other devices, not just HTC. Definitely more logical as people don't always change ringtone volume all the time and it can even ruin your "default" ringtone volume level by accidentally increasing/decreasing it.
Click to expand...
Click to collapse
You are WRONG. I have two devices running on Pie and that's how it works in Huawei and HTC 11 Lite:
https://drive.google.com/file/d/10Gw7XBuKjIM3Y3wR365jlGJYpsgnWgJV/view?usp=drivesdk
Besides, I disagree with you. A phone is a device primarily designed to make telephone calls. That's why, for years, volume buttons have been changing ring tone's volume, by default. If the phone was playing music - that's the other story.
Now, by default, I change volume of internal speaker (sic!). That's just insane - I have to go to Settings to change the volume of the ring tone.
Don't get me wrong: I love HTC, that's why I have U12+ even though I knew the HTC was dying at the time I bought the phone. But bug is a bug.
ive just updated my cellphone and im having the same problem and sometimes i can't unlock the phone using the double touch or swiping up ?, any news about when they gonna fix this? and can someone tell how to not see when ur touching the screen those little white dots, how to deactivate that thing?
No problems here on USA version
---------- Post added at 10:50 PM ---------- Previous post was at 10:46 PM ----------
larrymtz said:
ive just updated my cellphone and im having the same problem and sometimes i can't unlock the phone using the double touch or swiping up ?, any news about when they gonna fix this? and can someone tell how to not see when ur touching the screen those little white dots, how to deactivate that thing
Click to expand...
Click to collapse
Go to settings>system>developer options>turn off show taps
Usa version unlock
teh_pwnrer said:
No problems here on USA version
---------- Post added at 10:50 PM ---------- Previous post was at 10:46 PM ----------
Go to settings>system>developer options>turn off show taps
Click to expand...
Click to collapse
i have that version and i found the reason why it was showing the taps, the glove mode was enabled, gedtures still not working properly...
Yet another bug
After Digital Wellbeing app downloaded itself, during routine check of updates in Play Store, the only way to start it is to search for it in Settings. There's no entry in Settings for it. Fortunately, application has an option to place its icon in the app list.
HTC 11 Lite, on the other hand, has it done correctly.
Hopefully, someone from HTC reads that and they will ultimately release an update... Such a sad story. I loved HTC 10 and basically all their flagships and such a great company dies
I have here the same problem, this is all afther the update to Android 9.
Good that there is a topic about it, hopefull there will be more people with the same problem.
In addition to sound problems, I almost always have my phone on do not disturb. Despite this function, sound is just ringing and sound notifications come through with the apps.
Have already looked at the settings, these are only alarms and media on.
Last week I had the duration of not disturbing turned on at number of hours, the time format that he indicates was wrong, by the way still miss the option between switching off when your alarm goes off. this was still standard in Android 8.
Finally, I think it is a shame that they have moved the clock, had first used an appe to switch it off, because on my home screen I have the clock in large, but because it did not work, I left it. I have to say that I am used there for the rest. Only would have preferred that room for the reports.
I have it to
Maybe a stupid question, but why can't we manually edit the audio-related props to insert the missing lines?
MNoisy said:
Maybe a stupid question, but why can't we manually edit the audio-related props to insert the missing lines?
Click to expand...
Click to collapse
You'd need root. If you have root you're welcome to try and report back the improvements
WPtE said:
You'd need root. If you have root you're welcome to try and report back the improvements
Click to expand...
Click to collapse
I would be happy to. Any recommendations on tools to perform the edits along with backing them up first?
MNoisy said:
I would be happy to. Any recommendations on tools to perform the edits along with backing them up first?
Click to expand...
Click to collapse
Don't do that. You open yourself for possible attacks. Rooting phone for fun is cool but it's best to use a test Google account and a phone you do not use for normal, regular daily usage.
Others may and probably will disagree but if we're talking about your main device I'd keep it unrooted.
Related
Dear all,
I've bought this device : http://www.androidtoitaly.com/goods.php?id=923
quite similar to the Ulefone v12 (http://forum.xda-developers.com/showthread.php?p=30360533)
Infact for its similitude to th eUlefone I tried to flash following that guide.... and ... ooohh! nooo!!
Now I've my mobile dead... sigh!
There is someone that is able to help me on the recovery ?
Thanks in advance
usb jig
use usb jig to flash your phone!!!!
mehediatcom said:
use usb jig to flash your phone!!!!
Click to expand...
Click to collapse
Thank you for your reply, i want to add that with Flash tool I'm able to flash the device , but i don't have any rom useful for it
the problem arose because the original was really full of bug and trying to reflash i would to correct .... but ... you all know the results
here on the bottom you can see the back of the smartphone
Please heeeeelp me !
T5 Model MHT865
k-armando said:
So these my news (bad news)
this my phone, seems to be MHT865, it is quite similar to th ULEFONE v12 / Star v12 but these are its specs:
[Tipologia] Android phone candy touch screen
[Brand] T5
[OS] Android 4.0
[RAM] 512M
[CPU] MTK6577 1 Ghz
[Core] Dual core
[ROM] 4G
[Display] Multi-touch capac
[Screen res] 540*960 QHD
[Dual sim] Supported
[USB] microUSB
[Ext memory] 32G Micro SD
GSM 850/900/1800/1900 WCDMA 850/2100
[front camera] 0.3 mp
[back camera] 8.0 mp
[WIFI] Supported
[3G] Supported
[G-sensor] Supported
[Bluetooth] Supported
[GPS] Supported
[Multi-touch] 4
The device is not bad but the software is the worst you ever had in your life (this and the next). For that reason I tried to flash it.
I used SP_Flash_Tool_v3.1222.00. All the steps followed for making the operation went good but ... my phone now is dead :crying:
What are the symptoms ? ... after switch-on there is a frontal led that in sequence turn on Green - Red - Yellow and anything other ...
There is someone that has this device ? and has been able to flash ? or there is someone that has a stock rom for it ?
Thank you
Click to expand...
Click to collapse
T5
forum.china-iphone.ru/tinji-titan2-4-5-960x540-android-4-0-mtk6577-t23345-20.html?hilit=titan2
forum.china-iphone.ru/ihtc-titan-2-t24309.html
hi k-armando, have you solved?
k-armando said:
k-armando said:
So these my news (bad news)
this my phone, seems to be MHT865, it is quite similar to th ULEFONE v12 / Star v12 but these are its specs:
[Tipologia] Android phone candy touch screen
[Brand] T5
[OS] Android 4.0
[RAM] 512M
[CPU] MTK6577 1 Ghz
[Core] Dual core
[ROM] 4G
[Display] Multi-touch capac
[Screen res] 540*960 QHD
[Dual sim] Supported
[USB] microUSB
[Ext memory] 32G Micro SD
GSM 850/900/1800/1900 WCDMA 850/2100
[front camera] 0.3 mp
[back camera] 8.0 mp
[WIFI] Supported
[3G] Supported
[G-sensor] Supported
[Bluetooth] Supported
[GPS] Supported
[Multi-touch] 4
The device is not bad but the software is the worst you ever had in your life (this and the next). For that reason I tried to flash it.
I used SP_Flash_Tool_v3.1222.00. All the steps followed for making the operation went good but ... my phone now is dead :crying:
What are the symptoms ? ... after switch-on there is a frontal led that in sequence turn on Green - Red - Yellow and anything other ...
There is someone that has this device ? and has been able to flash ? or there is someone that has a stock rom for it ?
Thank you
Click to expand...
Click to collapse
Click to expand...
Click to collapse
[Q&A] [kernel] [racer] [l2.0] lpx13d | cm11 | oc-uv | Γ | intelli | s2w-dt2w-s
Q&A for [kernel] [racer] [l2.0] lpx13d | cm11 | oc-uv | Γ | intelli | s2w-dt2w-s2s |
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [kernel] [racer] [l2.0] lpx13d | cm11 | oc-uv | Γ | intelli | s2w-dt2w-s2s |. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
rachanta said:
@HAKAhero Yeeesss. Just install su again if su breaks.
Click to expand...
Click to collapse
Does anyone know how's the battery drain in LPX13D?
Suggestion
How about TCP Westwood+ and Westwood?
xda_adam said:
How about TCP Westwood+ and Westwood?
Click to expand...
Click to collapse
Tried and didnt succeed earlier. Will try again later.
Kernel BUG
I just installed Racer L9.1, and put it through Antutu. Even though I've raised all voltages by 50 mV, the phone continues to reboot once it reaches the CPU float test, so I checked the kmsgs. Initially, it is just a data corruption about CPU 0, and it specifies the frequency of the processor when it 'crashed'. But in my last few tests, it shows that there is a kernel bug, and even after reinstalling the kernel, the same message persists. I attached the last_kmsg, and here's a portion of the log that sort of matters:
[ 462.978385] ------------[ cut here ]------------
[ 462.978456] Kernel BUG at c0517be4 [verbose debug info unavailable]
[ 462.978493] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP ARM
[ 462.978559] CPU: 0 Not tainted (3.4.104-RACER_L9.5_20141119 #1)
[ 462.978600] PC is at regulator_check_voltage+0xbc/0x14c
[ 462.978665] LR is at regulator_set_voltage+0x64/0x108
[ 462.978702] pc : [<c0517be4>] lr : [<c051a23c>] psr: 20000013
[ 462.978703] sp : ee1f1e48 ip : ee17f680 fp : ed8dfc84
[ 462.978798] r10: 00000002 r9 : c017bdbc r8 : c103bd54
[ 462.978861] r7 : 00124f80 r6 : 0012b128 r5 : ee27a400 r4 : ed971580
[ 462.978896] r3 : 0012b128 r2 : ee1f1e68 r1 : ee1f1e6c r0 : ee27a400
[ 462.978960] Flags: nzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel
[ 462.979024] Control: 10c5787d Table: 26bc406a DAC: 00000015
[ 462.979059]
[ 462.979060] PC: 0xc0517b64:
This still occurs even if I leave the max CPU frequency at its default 2265 MHz.
https://www.dropbox.com/s/2xpax38l75dmwxe/last_kmsg.txt?dl=0
mashedpotato13 said:
I just installed Racer L9.1, and put it through Antutu. Even though I've raised all voltages by 50 mV, the phone continues to reboot once it reaches the CPU float test, so I checked the kmsgs. Initially, it is just a data corruption about CPU 0, and it specifies the frequency of the processor when it 'crashed'. But in my last few tests, it shows that there is a kernel bug, and even after reinstalling the kernel, the same message persists. I attached the last_kmsg, and here's a portion of the log that sort of matters:
[ 462.978385] ------------[ cut here ]------------
[ 462.978456] Kernel BUG at c0517be4 [verbose debug info unavailable]
[ 462.978493] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP ARM
[ 462.978559] CPU: 0 Not tainted (3.4.104-RACER_L9.5_20141119 #1)
[ 462.978600] PC is at regulator_check_voltage+0xbc/0x14c
[ 462.978665] LR is at regulator_set_voltage+0x64/0x108
[ 462.978702] pc : [] lr : [] psr: 20000013
[ 462.978703] sp : ee1f1e48 ip : ee17f680 fp : ed8dfc84
[ 462.978798] r10: 00000002 r9 : c017bdbc r8 : c103bd54
[ 462.978861] r7 : 00124f80 r6 : 0012b128 r5 : ee27a400 r4 : ed971580
[ 462.978896] r3 : 0012b128 r2 : ee1f1e68 r1 : ee1f1e6c r0 : ee27a400
[ 462.978960] Flags: nzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel
[ 462.979024] Control: 10c5787d Table: 26bc406a DAC: 00000015
[ 462.979059]
[ 462.979060] PC: 0xc0517b64:
This still occurs even if I leave the max CPU frequency at its default 2265 MHz.
https://www.dropbox.com/s/2xpax38l75dmwxe/last_kmsg.txt?dl=0
Click to expand...
Click to collapse
Please switch to latest. L9.5.5. Link at OP. Runs up to Max 2726 with min 4 cores, performance gov, and returns Antutu > 44000 with repeatability after cool down < 43C.
Thanks for reporting the bug. I will check in any case.
Thanks for the reply! Unfortunately the issue still persists with latest version, so I guess I'll have to do a full-wipe over the weekend.
mashedpotato13 said:
Thanks for the reply! Unfortunately the issue still persists with latest version, so I guess I'll have to do a full-wipe over the weekend.
Click to expand...
Click to collapse
The log you sent suggests a problem with the voltage regulator. I am doing a build with a completely revamped voltage regulator system. I will post once I test it to some extent.
best battery life I ever get.
Thanks you very much ! Your kernel improve a lot the battery !
Can you add nightmare governor ? I love that.
Thanks for your response.
rachanta said:
The log you sent suggests a problem with the voltage regulator. I am doing a build with a completely revamped voltage regulator system. I will post once I test it to some extent.
Click to expand...
Click to collapse
I also noticed that sometimes the phone reboots after being boosted to 3014 MHz, despite having my max frequency set at 2726. I think disabling MPDec temporarily fixes that issue, though.
mashedpotato13 said:
I also noticed that sometimes the phone reboots after being boosted to 3014 MHz, despite having my max frequency set at 2726. I think disabling MPDec temporarily fixes that issue, though.
Click to expand...
Click to collapse
This problem is solved in last few builds.
---------- Post added at 03:28 PM ---------- Previous post was at 03:26 PM ----------
dryx01 said:
Thanks you very much ! Your kernel improve a lot the battery !
Can you add nightmare governor ? I love that.
Thanks for your response.
Click to expand...
Click to collapse
Added in latest test build posted in main thread. Pl let me know how it works. BTW what's special about nightmare?
I'm getting a lot of watchdog bites and resets now.
Please reinstall ROM, kernel and su.
@rachanta your new Kernel is awesome. Smooth and fast.
Good Job man :good:
试试
好样的，看看能发中文不
Loang X. Von said:
好样的，看看能发中文不
Click to expand...
Click to collapse
English please
Latest 5.1 build vs latest Racer kernels
Hi Rachanta,
Unfortunately I cannot flash your latest kernel builds over latest 5.1 factory image (LMY47I). I constantly facing with "E:Unable to mount '/cache'" error message.
Do you have any suggestions on this?
Thanks!
PS
Forgot to mention that i'm using latest TWRP 2.8.6.0. Can it cause the issue?
Phone crashes whenever I try to change voltage.
I tried to change the voltage (underclock) and right away the phone locks up. I am using cm12.1 hammerheadcaf (bokrom). As well as that the minimum frequency does not go below 300mhz. 96 mhz is not an option, and selecting 300mhz does not stick. This is all done with Kernel Adiuter .
Has anyone had issuea with Pandora since latest 5/19 update? I get no sound from Pandora now and I was wondering if anyone else had that issue?
Does anyone have issues with Pandora not working with aosp kernel?
Hello, I have a question about CM11 but not on Galaxy S II Plus...on Galaxy Trend Plus (GT-S7580 codename kylepro).
I'm asking this question here because Trend Plus has Broadcom BCM21664 and VideoCore IV HW and I know that i9105 has Broadcom BC28155 and VideoCore IV as well
So, the user SandPox from CyanogenMod Forum ported CM 11 to Galaxy Trend Plus, and it has some bugs and I'm wondering if some devs/users from here could help him since both phones use hardware from Broadcom
Bugs:
1. In call problem: you can make or receive calls but you cannot hear anything nor does the other caller hear you. It doesn't work with headset either. The microphone is working as tested with CM Sound Recorder.
2. Wi-Fi won't turn On: when you try to switch Wi-Fi On it goes Off instantly (Model: BCM4330)
3. MTP doesn't work, only UMS sometimes
If anybody could help, any help would be much appreciated.
Useful links:
Trend Plus (kylepro) Device Tree on GitHub by SandPox
CM zip package
Original Thread
THANK YOU for any help! If you think this thread shouldn't be here I'll ask for it to be moved.
All credits for this port go to SandPox!
Mike
Try to contact this man: @mikeioannina
I wrote him.
Check your audio_policy and mixer_paths for audio
Are you using the correct wifi module? What does your logcat say? What do your dmesges say?
Try this for mtp:https://github.com/pawitp/android_k...mmit/c7568be475b505597d265121eb3443b44d83d266
Also be sure your permissions and sepolicy are working correctly
Hi, wifi is already fixed in the new builds.
UMS/MTP are fixed too (not tested yet).
The main problems are now: dialing (no audio in call) and H/W decoder.
The trend plus is armv7 so it can be fixed.
Any help would be appreciated
Thanks, Marvin
______________________
Credits for cm11 on Kylepro go to the awesome developer Sandpox!
marvino112 said:
Hi, wifi is already fixed in the new builds.
UMS/MTP are fixed too (not tested yet).
The main problems are now: dialing (no audio in call) and H/W decoder.
The trend plus is armv7 so it can be fixed.
Any help would be appreciated
Thanks, Marvin
______________________
Credits for cm11 on Kylepro go to the awesome developer Sandpox!
Click to expand...
Click to collapse
MTP still does not work in the newest build for me.
Can you help us with that @pawitp ?
CoolDevelopment said:
Check your audio_policy and mixer_paths for audio
Are you using the correct wifi module? What does your logcat say? What do your dmesges say?
Try this for mtp:https://github.com/pawitp/android_k...mmit/c7568be475b505597d265121eb3443b44d83d266
Also be sure your permissions and sepolicy are working correctly
Click to expand...
Click to collapse
Thank you for you help. We managed to fix MTP bug. But bug with no call sound still persists. Do you have any other suggestions for fixing that bug?
Its not only call sound i think the microfon doesnt work too
But in record application is working.
We came to conclusion that here is somewhere a problem with sound call:
V/ALSAStreamOps( 1476): setParameters() routing=1 for playback rate=48000 modechanging=1 mode=2
V/ALSAStreamOps( 1476): setParameters() mIsRealCall=0
D/ALSAStreamOps( 1476): ALSAStreamOps mParent->mModeChanging = 1
D/AudioHardwareALSA( 1476): ->VoIP_DBG setVoiceOn mCntVoiceOn=0 mMode=2 curdev=2 device=1 option=2
D/AudioHardwareALSA( 1476): getVoiceCallDevice for device = 0x1 returned source = 1 sink = 0 tty=0[ 1, 0]
W/AudioHardwareALSA( 1476): Mode is still in call but removing incall profile
W/AudioHardwareALSA( 1476): EnableAppProfile profile -1 is out of range [0, 17] index=1
D/AudioHardwareALSA( 1476): Audio System RR : setVoiceOn(): correct mCntVoiceOn = -1 -> 0
D/AudioHardwareALSA( 1476): setVoiceOn(): vc_swt=0x0, enable=0x0 <==============================
D/AudioHardwareALSA( 1476): setVoiceOn(): VoiceCall=0, VtCall=0, VoipCall=0
I/AudioHardwareALSA( 1476): driverDevice={1,0,1,0} for device 1
D/AudioHardwareALSA( 1476): getPlaybackDevice for device = 0x1 returned sink = 0
D/AudioHardwareALSA( 1476): <-VoIP_DBG setVoiceOn mCntVoiceOn=0 mMode=2 curdev=2 device=1 option=2
Click to expand...
Click to collapse
I want to ask if is there any way to change VoiceCall=0 to VoiceCall=1? Because similar phone with brodacom has VoiceCall=1 and has working calls. Thank you.
Hello, warmest greeting from indonesia. I want to ask regarding volume up problem on my mi note 3, after update to miui 11, my volume up button is not respond, try to reboot also not help, i am still facing the same problem. Volume down and power button work normal. Is this problem from software (bug from miui 11) or hardware problem? Thanks in advance
Seems to be hardware. Try flashing another miui rom for example earlier version. If situation is the same than it is for aure hardware.
Послато са Mi Note 3 помоћу Тапатока
Salam dostlar. Mənə kömək lazımdır. Black Shark 4 mənim telefonumdur. Normalda 8 nüvədən, 870 CPU-dan istifadə edir. Amma 2 ay əvvəl 4 nüvə heç bir şey olmadan yararsız hala düşdü. Heç aktiv deyil. Format etdim (hard reset), ota vasitəsilə China rom etdim (indi Çin A0). Əvvəllər H0. Mənim problemim odur ki, 4 nüvə ümumiyyətlə işləmir. Heç vaxt. Xahiş eliyirəm, mənə kömək eləyin. Mən reball etmək üçün axtarış etdim, lakin telefon tamamilə söndürüldükdə təkrar topun edilməsi lazımdır. Telefonum işləyir. Cəmi 4 nüvə işləmir.
Mod edit: Google translate added below
@pervanhuseyn kindly post in English next time
Hello friends. I need help. Black Shark 4 is my phone. Normally it uses 8 cores, 870 CPU. But 2 months ago, 4 cores became useless without anything. Not active at all. I formatted (hard reset), made China rom via ota (now China A0). Previously H0. My problem is that 4 cores don't work at all. Never. Please help me. I searched for reballing, but when the phone is completely turned off, it needs to be reballed. My phone is working. Only 4 cores are not working.