Related
Hello All,
I want to raise a question here because I don't seem to find any help about it.
I am using a nice TF101 tablet with great joy. Now with less as yesterday while watching youtube the sound has gone and did not return after a reboot or using the DSP Reinit in the Kat Tools.
Now this has happened with me already a week before. Then I was using Jousteink's unofficial room. Then I've changed to KatKiss 4.2.2 and the sound reappeared again. Later to give it a whirl I have then upgraded to KatKiss 4.3 and everything was wokring like charm for 3 days then the sound went to Honolulu again.
Does anyone have any idea how can I get the sound working again or what can be the cause? Or simple share the same experience?
Thanks for the help.
Hate to ask, but is your volume up?
I had issues with the hangouts/talk notifications muting my volume when using the cascade option in the KAT tool.
frederuco said:
Hate to ask, but is your volume up?
I had issues with the hangouts/talk notifications muting my volume when using the cascade option in the KAT tool.
Click to expand...
Click to collapse
Thanks for the reply.
Yup, the volume is as high as it can go
szilasz said:
Thanks for the reply.
Yup, the volume is as high as it can go
Click to expand...
Click to collapse
So, you are saying that the sound works sometimes and then cuts out. Intermittently? Maybe hardware related - but I'd leave a proper diagnosis to the experts here.
I know that I have the volume toolkit installed on my TF101 and to be honest - it doesn't seem to make a whole lot of difference when listening thought the tablet's speakers.
Ziggy
Theziggy said:
So, you are saying that the sound works sometimes and then cuts out. Intermittently? Maybe hardware related - but I'd leave a proper diagnosis to the experts here.
I know that I have the volume toolkit installed on my TF101 and to be honest - it doesn't seem to make a whole lot of difference when listening thought the tablet's speakers.
Ziggy
Click to expand...
Click to collapse
Nope, it is gone. Totally. It is OK on bluetooth and through jack but the speakers are deaf. From one point to another and remains so even after reboot and reflashing with a /system format.
On ICS based roms there was a problem similar to this where restarting the tab fixed it for some time and you could have save this reboot with the KAT tool. You could just reinitalize the sound. I agree on the quality part though
I hope it is not HW related, this was always a popular problem with the TF101. I just hope to find someone who encountered this and can give a fresh idea of a fix.
Which build are you using? The latest one I have the same issue, but if I go back a few it's working fine.
Lethe6 said:
Which build are you using? The latest one I have the same issue, but if I go back a few it's working fine.
Click to expand...
Click to collapse
Hello there,
I am using the latest #020 build. Which one are you on? I would like to give it a whirl to see if will I get my sound back.
Thanks in advance!
szilasz said:
Hello there,
I am using the latest #020 build. Which one are you on? I would like to give it a whirl to see if will I get my sound back.
Thanks in advance!
Click to expand...
Click to collapse
I'm using 018 right now because with 019 and 020 the back button stops working. I was also unable to control the sound through the device itself but if I would start, say, a movie on MX Player then I could hear and adjust volume.
Lethe6 said:
I'm using 018 right now because with 019 and 020 the back button stops working.
Click to expand...
Click to collapse
That's because you forgot to flash the gapps after the rom zip.
Follow exactly the instructions from the 1st post and it'll work fine.
timduru said:
That's because you forgot to flash the gapps after the rom zip.
Follow exactly the instructions from the 1st post and it'll work fine.
Click to expand...
Click to collapse
I'll take your word for it, but I'm fairly sure I did, twice.
Lethe6 said:
I'll take your word for it, but I'm fairly sure I did, twice.
Click to expand...
Click to collapse
I know I had no sound, or GPS when I 1st flashed this. I had flashed it from TWRP 2.5.00, and I got it updated to TWRP 2.6.100, and reflashed it, and now everything is working. I would make sure your TWRP is up to date.
C0BRA01 said:
I know I had no sound, or GPS when I 1st flashed this. I had flashed it from TWRP 2.5.00, and I got it updated to TWRP 2.6.100, and reflashed it, and now everything is working. I would make sure your TWRP is up to date.
Click to expand...
Click to collapse
There is no 2.6 for the tf101 ... what did you install exactly? The title says 2.6 but the files are 2.3. http://www.teamw.in/project/twrp2/109
It was fixed after just flashing the newer one.
Edit: Yeah, not touching unofficial cooked recoveries with a 1000 foot pole.
Then you will be waiting a long time, as there have been no new "Official" TWRP recoveries for a long time now for the tf101.. His is working fine.
You take similar risks every time you flash a ROM.
Lethe6 said:
There is no 2.6 for the tf101 ... what did you install exactly? The title says 2.6 but the files are 2.3. http://www.teamw.in/project/twrp2/109
It was fixed after just flashing the newer one.
Edit: Yeah, not touching unofficial cooked recoveries with a 1000 foot pole.
Click to expand...
Click to collapse
Lethe6 said:
There is no 2.6 for the tf101 ... what did you install exactly? The title says 2.6 but the files are 2.3. http://www.teamw.in/project/twrp2/109
It was fixed after just flashing the newer one.
Edit: Yeah, not touching unofficial cooked recoveries with a 1000 foot pole.
Click to expand...
Click to collapse
I agree with @C0BRA01. The only reason that joesteink's build were not official is because no one from the TWRP team approved them. I have not heard of any issues of anyone bricking or having issues caused by any of the 2.5 or 2.6 builds for the TF101. I am running sidneyk's 2.6.1.0-c build right now and have had zero issues, other than the superuser nag screen at reboot when running KatKiss 021. It has to do with the supersu app even though root is working fine in the ROM.
Q&A for [ROM] Official Cyanogenmod 11 4.4.4 for the Moto G 4G (Peregrine)
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. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Notification light not working with cyanogenmod
Hi,
I'm using cyanogenmod (m6 and afterwards the current daily builds) on my moto g and for quite some time I have the problem that my notification light is not working. I tried out installing the motorola led activator widget, but this doesn't help. Even when trying out an LED tester app nothing happens. The LED is not broken though as it lights up when trying to boot my moto g on low battery. Do you have any ideas how to solve this?
Thank you in advance!
Link down
Seems the latest build link is down
not I download the latest build. fallen servers
Does the ROM still have the low ram bug ?
Problem audio speakers CM11 / Stock ROM
How about, first of all, I'm new here and do not speak English, so I excuse my writing.
I have a problem with my Moto G LTE (XT1040) with Stock ROM 4.4.4 KK Brazil, although I am from LatinAmerica.
Well, I have not much to this terminal, but a few days ago I had some problems with the rom Stock, restarting not it caught more, so I decided to flash the latest rom Cyanogenmod (specifically 20,141,012) due to some stability issues decided you go back to the Stock, having the same error when freezing some applications Motorola as usual to, so back to CM and switch to the "20141016" to the few hours I started to fail the camera, remained frozen when taking a photo . After that, it went back to flashing CM rom and had the same errors, updating the "20141018" was the same, but a new bug, and could not hear the music or videos without headphones was added, calls were heard if it was not for speaker, so I decided to go back to the Stock, but apparently the problem was continuing, feel that the speakers are damaged, but the alarms or notification sounds if they worked properly. Now try wipes Cache / Dalvik from CWM but only achieved a temporary solution, put a good song and all, but to change it or put it back the audio is going.
Help me, do not know what else to do, I guess that having unlocked the bootloader and lost my warranty
Thanks in advance if this post is incorrect or I violate any rule, excuse me, I'll delete.
I'm also trying to get GPS to work on my Moto G LTE in cm11:
Based on what I read here, I reflashed stock, and tried it out, had no problems at all. Then restored the cm11 nandroid I had made, and it couldn't see any satellites still. Will restoring the nandroid backup also restore the not-working-gps then? What is being saved by unlocking the gps? Will I have different results from backing up everything with titanium backup, then going back to stock, using gps, reinstalling cm, and restoring the backed up apps? It's much more of a pain to do it that way, but if it works, I'll find the time...
This is a canadian xt1040, btw, in case it makes a difference.
UPDATE: I went ahead and reinstalled stock, played with gps for a while, and it worked without any trouble, then reinstalled CM11 (oct 21 nightly this time) restored my backed up apps with titanium backup (not any system apps). Unfortunately, still no gps at all. It never sees a single satellite. Is there anything else to try?
Hello,
First of all, thank you and all people to contributing and helping developing CM for this device!
I only have one question about GPS bug :
You indicate that it's necessary to have a GPS lock in the stock ROM first to enable GPS in CM.
Does a fix for this bug is intended/possible or the only one solution is to reinstall the stock rom, enable GPS and install CM?
Thanks in advance.
Audio solved
It updated my previous query, I could solve the problem of audio speaker, I began to disassemble the phone and as imagined, I found steel wool at the entrance and were making contact, so the cell believed to have headphones all the time .
Enable GPS in Moto G Nightly
This is in response to jac0708 in the thread this thread who asked:
Mind expanding on these two? What is the low ram bug? And how do you get a lock from stock for the gps fix?
Sorry for noobishness
Click to expand...
Click to collapse
The answer I found for the GPS not working was that when I installed CM11 within hours after taking delivery of my Moto G, the GPS would not get a fix. The solution is explained here by colinw:
Posted 11 October 2014 - 10:42 PM
Okay I just fixed my problem following some other post for a Moto phone.
1) Made a (nandroid) backup using clockwordmod of my current setup (cyanogen 11)
2) Restored old backup of a stock rom (I restored back to the one that came with my phone)
3) Then I had to USE the GPS - hadn't done that yet. Also made sure it was set to Device Only mode in settings->location because someone somewhere suggested it.
4) Restored to cyanogen rom.
5) Working!!
Click to expand...
Click to collapse
Just wanted to add that it doesn't always work. I tried at least three times, restoring stock, using gps, and then restoring my backup before I had gps working in CM. But it does work now! Be patient, and maybe just leave the phone with the stock, sitting on maps for a while. Perhaps I rushed it before?
For the last few months I people on the other end of a phone call have been struggling to hear my voice in normal phone mode (not speaker phone) but when I switch to speakerphone the problem goes away and the call quality is excellent.
I have previously tried to fix it using some work arounds on the Oneplus forums but none of these have worked and in the last week or so it has really been annoying me.
I am currently on exodus 6.0.1 and the Google dialer from the play store but this problem has been consistent across many ROMs (aosp, cm and cos based, as well as lolipop and marshmallow) and a few different dialers.
I'm suspecting that the microphone is the problem but since all of the threads regarding this issue are too old too ask I'm not sure.
Any help with this issue would be greatly appreciated!!!
Check if the "OK Google" hotword is active systemwide inside the Google App.
If yes, deactivate it or set it to "App only".
This is one possible reason and it got fixed on the CM13 Nightlies a couple days ago.
This is the commit which fixes the OK Google issue
http://review.cyanogenmod.org/#/c/137753/
I can't find it in Exodus gerrit.
I have just tried this method and it did not work, however the problem still went away when I was using the speaker phone, as it did with the "from any screen" option enabled.
Thank you for the suggestion though.
Bump
I, too am having the same issues. From my research, the One plus has 3 mics, and when using the speaker phone, a different mic is being used.
When i am on calls, i can hear people but people can't hear me. I have to literally put my mouth on the bottom mic and talk loud into it. I've tried the Ok Google thing and it does not work for me. I am going nuts trying to figure this out. Almost want to smash my phone...
What bugs me is when i was researching the problem, hundreds of OPO owners are experiencing mic issues. Why haven't this been address by ONO company?
There's a main mic bypass zip you can flash from here
http://forum.xda-developers.com/oneplus-one/development/mod-oneplus-one-stereo-mod-t2967925
This has worked for me for quite a while until I started flashing more recent marshmallow ROMs. When I would flash this call volumes were great, but then notifications and alarms stopped working. I made some edits to the original zip and fixed it for marshmallow if you want to try it, you can get it here.
https://app.box.com/s/4u0wixtyrb8pzte37ubo4dh2m36d93l1
mikiosmart said:
There's a main mic bypass zip you can flash from here
http://forum.xda-developers.com/oneplus-one/development/mod-oneplus-one-stereo-mod-t2967925
This has worked for me for quite a while until I started flashing more recent marshmallow ROMs. When I would flash this call volumes were great, but then notifications and alarms stopped working. I made some edits to the original zip and fixed it for marshmallow if you want to try it, you can get it here.
https://app.box.com/s/4u0wixtyrb8pzte37ubo4dh2m36d93l1
Click to expand...
Click to collapse
Thank you so much!!! Great patch! Works on CM13, and I now have notification etc again!
You, sir, are a hero :good:
mikiosmart said:
There's a main mic bypass zip you can flash from here
http://forum.xda-developers.com/oneplus-one/development/mod-oneplus-one-stereo-mod-t2967925
This has worked for me for quite a while until I started flashing more recent marshmallow ROMs. When I would flash this call volumes were great, but then notifications and alarms stopped working. I made some edits to the original zip and fixed it for marshmallow if you want to try it, you can get it here.
https://app.box.com/s/4u0wixtyrb8pzte37ubo4dh2m36d93l1
Click to expand...
Click to collapse
Omg... Youuu.... arrrrreeeeee..... theeeee.... mutha...... fnnnnnnn......... Mannnn
Thank u sooooo much...
P.s.. Voltron was a good touch :good:
mikiosmart said:
There's a main mic bypass zip you can flash from here
http://forum.xda-developers.com/oneplus-one/development/mod-oneplus-one-stereo-mod-t2967925
This has worked for me for quite a while until I started flashing more recent marshmallow ROMs. When I would flash this call volumes were great, but then notifications and alarms stopped working. I made some edits to the original zip and fixed it for marshmallow if you want to try it, you can get it here.
https://app.box.com/s/4u0wixtyrb8pzte37ubo4dh2m36d93l1
Click to expand...
Click to collapse
Underrated post
mikiosmart said:
There's a main mic bypass zip you can flash from here
http://forum.xda-developers.com/oneplus-one/development/mod-oneplus-one-stereo-mod-t2967925
This has worked for me for quite a while until I started flashing more recent marshmallow ROMs. When I would flash this call volumes were great, but then notifications and alarms stopped working. I made some edits to the original zip and fixed it for marshmallow if you want to try it, you can get it here.
https://app.box.com/s/4u0wixtyrb8pzte37ubo4dh2m36d93l1
Click to expand...
Click to collapse
Could you create one for nougat? Tried flashing it but it loops... @mikiosmart
mikiosmart said:
There's a main mic bypass zip you can flash from here
http://forum.xda-developers.com/oneplus-one/development/mod-oneplus-one-stereo-mod-t2967925
This has worked for me for quite a while until I started flashing more recent marshmallow ROMs. When I would flash this call volumes were great, but then notifications and alarms stopped working. I made some edits to the original zip and fixed it for marshmallow if you want to try it, you can get it here.
https://app.box.com/s/4u0wixtyrb8pzte37ubo4dh2m36d93l1
Click to expand...
Click to collapse
Hi, your zip file working good on cm13. But there are so many Android 7 roms for oneplus one. We can't use it, because your zip file couldn't work on nougat. Can you update your zip file to the Android 7? Please help us mister.
Works great on jgcaap CM-13 20161102. Thank you!
mikiosmart said:
There's a main mic bypass zip you can flash from here
http://forum.xda-developers.com/oneplus-one/development/mod-oneplus-one-stereo-mod-t2967925
This has worked for me for quite a while until I started flashing more recent marshmallow ROMs. When I would flash this call volumes were great, but then notifications and alarms stopped working. I made some edits to the original zip and fixed it for marshmallow if you want to try it, you can get it here.
https://app.box.com/s/4u0wixtyrb8pzte37ubo4dh2m36d93l1
Click to expand...
Click to collapse
Please can you modify the file to add compatibility with Android nougat/cm 14.1 please?
Nougat here using [ROM][CM14.1][Android 7.1][OMS] TugaPower 4.0
I used the build.prop fix alongside with the mixer path and it worked great
hope it helps
Ifollow this tutorial
https://vcillusion.wordpress.com/20...n-low-mic-during-call-problem-in-oneplus-one/
MassiveDRS said:
Nougat here using [ROM][CM14.1][Android 7.1][OMS] TugaPower 4.0
I used the build.prop fix alongside with the mixer path and it worked great
hope it helps
Ifollow this tutorial
https://vcillusion.wordpress.com/20...n-low-mic-during-call-problem-in-oneplus-one/
Click to expand...
Click to collapse
I'm on tugapower too, tried the tutorial you gave and it just doesn't work at all (no sound, no notification, nothing...) can you share your modified build.prop and mixer_path.xml please?
phoenixita said:
Could you create one for nougat? Tried flashing it but it loops... @mikiosmart
Click to expand...
Click to collapse
@olbatar
I really have no idea if this works on N since I dont have it, but you can try:
Find this 2 rows in this two files.
/system/build.prop
Change: ro.qc.sdk.audio.fluencetype=fluence
to
ro.qc.sdk.audio.fluencetype=none
Then, edit /system/etc/audio_platform_info.xml
<device name="SND_DEVICE_IN_HANDSET_MIC" acdb_id="40" />
to
<device name="SND_DEVICE_IN_HANDSET_MIC" acdb_id="4" />
Reboot and check if it worked. I used this on COS12,COS13 and 13.1 and always worked.
mikiosmart said:
There's a main mic bypass zip you can flash from here:
http://forum.xda-developers.com/oneplus-one/development/mod-oneplus-one-stereo-mod-t2967925
This has worked for me for quite a while until I started flashing more recent marshmallow ROMs. When I would flash this call volumes were great, but then notifications and alarms stopped working. I made some edits to the original zip and fixed it for marshmallow if you want to try it, you can get it here.
https://app.box.com/s/4u0wixtyrb8pzte37ubo4dh2m36d93l1
Click to expand...
Click to collapse
Has anyone tried this with other Nougat ROMs besides Tugapower?
seanwlk said:
@olbatar
I really have no idea if this works on N since I dont have it, but you can try:
Find this 2 rows in this two files.
/system/build.prop
Change: ro.qc.sdk.audio.fluencetype=fluence
to
ro.qc.sdk.audio.fluencetype=none
Then, edit /system/etc/audio_platform_info.xml
<device name="SND_DEVICE_IN_HANDSET_MIC" acdb_id="40" />
to
<device name="SND_DEVICE_IN_HANDSET_MIC" acdb_id="4" />
Reboot and check if it worked. I used this on COS12,COS13 and 13.1 and always worked.
Click to expand...
Click to collapse
This fix is not for the same problem, so it can't do anything for nougat problem...
Please someone can modify the fix to add compatibility with cm14.1 please????
mikiosmart said:
There's a main mic bypass zip you can flash from here
http://forum.xda-developers.com/oneplus-one/development/mod-oneplus-one-stereo-mod-t2967925
This has worked for me for quite a while until I started flashing more recent marshmallow ROMs. When I would flash this call volumes were great, but then notifications and alarms stopped working. I made some edits to the original zip and fixed it for marshmallow if you want to try it, you can get it here.
https://app.box.com/s/4u0wixtyrb8pzte37ubo4dh2m36d93l1
Click to expand...
Click to collapse
Does this disable noise cancellation completely? Maybe it's just in my head, but I think my phone cancelled the background noise pretty nicely when it was new. Then this bug happened, and now after this fix, everything just goes through. Nothing gets cancelled. Is this normal? Is there a workaround?
mikiosmart said:
There's a main mic bypass zip you can flash from here
http://forum.xda-developers.com/oneplus-one/development/mod-oneplus-one-stereo-mod-t2967925
This has worked for me for quite a while until I started flashing more recent marshmallow ROMs. When I would flash this call volumes were great, but then notifications and alarms stopped working. I made some edits to the original zip and fixed it for marshmallow if you want to try it, you can get it here.
https://app.box.com/s/4u0wixtyrb8pzte37ubo4dh2m36d93l1
Click to expand...
Click to collapse
mikiosmart you're a genuis. bypassing the main mic is still the best option for me also. what parameter is resonsible for volume over the loud speaker? When I use loud speaker with this mod, people can hardly hear me. If you can fix that you will have truly solved everything.
P.S - Voltron is a nice touch. :good:
Haven't managed to test if it fixes the bug because I had to sleep lol.
https://github.com/Demon000/libra/commit/b5067833797cd1eb207cd976bf2419c58ca8c7ed
If anyone can test if it works, I would be very thankful.
How I did it?
Get a hex file editor.
Compile kernel with old touchscreen firmware.
Open the synaptics_biel_sharp_update.fw or synaptic_biel_auo_update.fw that have been generated in firmware/ folder in the hex editor.
Get the MIUI kernel, split it, uncompress it.
In the .fw files, the first four hex groups are magic numbers(a hex group looks like "3F"), and after that there are some common hex groups in sharp and auo firmware.
Use the hex editor to search for the common groups in the MIUI kernel, and also find the magic number before the common groups.
Use the "csplitb" program to split the the kernel binary at the newly found magic number + common groups, and strip the result to 12661 lines.
Repeat this for every common group found.
Then use the objcopy program inside the toolchain to convert the binary files to .ihex, and replace the ihex files in the firmware folder.
Done.
It is complicated, but once you get the first steps it will be easy to understand.
Although I don't know if I did a good job at explaining.
Cozmy, you are magic. Lot of thanx, Man.
Many thanks. :good:
How does one flash this?
danbrown162 said:
How does one flash this?
Click to expand...
Click to collapse
You cannot, devs that make custom roms can use it to build rom with fixed display firmware.
danbrown162 said:
How does one flash this?
Click to expand...
Click to collapse
I can post a kernel build with it later, not tested as currently I'm working on lineage os using all the vendor binaries and blobs from the nougat release.
Harrynowl said:
I can post a kernel build with it later, not tested as currently I'm working on lineage os using all the vendor binaries and blobs from the nougat release.
Click to expand...
Click to collapse
I couldn't get it to update the firmware because I was not using Xiaomi touchscreen drivers in my kernel, but the firmware itself should be working fine.
I don't want to bloat my CAF touchscreen driver so it will take me longer until I find where it fails.
Please keep us updated.
https://drive.google.com/open?id=0B9WMSJf5LSatdG5WM24zNnJPaEk
Kernel image which fixes the touchscreen problem.
PS. This kernel may use more battery, just because I didn't spend time optimizing the kernel, but rather optimizing the source-code quality, lol.
You can try flashing your original kernel to see if the fix remains.
Tested on Resurrection Remix Nougat.
EDIT: I haven't tested it on any AUO panels, as my phone has a Sharp one.
EDIT2: Flashed back the Resurrection Remix kernel and touchscreen is still fixed. Success!
Guide: backup your kernel, flash the kernel I provided, restore your old kernel.
Proof as attachment.
Cozzmy13 said:
https://drive.google.com/open?id=0B9WMSJf5LSatdG5WM24zNnJPaEk
Kernel image which fixes the touchscreen problem.
PS. This kernel may use more battery, just because I didn't spend time optimizing the kernel, but rather optimizing the source-code quality, lol.
You can try flashing your original kernel to see if the fix remains.
Tested on Resurrection Remix Nougat.
EDIT: I haven't tested it on any AUO panels, as my phone has a Sharp one.
EDIT2: Flashed back the Resurrection Remix kernel and touchscreen is still fixed. Success!
Guide: backup your kernel, flash the kernel I provided, restore your old kernel.
Proof as attachment.
Click to expand...
Click to collapse
I hope this gets implemented on next releases of our roms
solis_f said:
I hope this gets implemented on next releases of our roms
Click to expand...
Click to collapse
Just give the ROM maintainers a link to this, they will surely add it to the ROM.
Holy **** You're a hero Cozzmy13, thank you!
I just tried the image on my AUO Mi4c, and I couldn't boot TS CM13 with the kernel. The fix didn't stick after restoring the original boot partition, but I have a feeling we're very close here
I'll try flashing RR later and see what I get, I have a Nandroid backup somewhere.
Phlogistol said:
Holy **** You're a hero Cozzmy13, thank you!
I just tried the image on my AUO Mi4c, and I couldn't boot TS CM13 with the kernel. The fix didn't stick after restoring the original boot partition, but I have a feeling we're very close here
I'll try flashing RR later and see what I get, I have a Nandroid backup somewhere.
Click to expand...
Click to collapse
It's my fault, I compiled the image with RR ramdisk. It definitely works on RR Nougat, that's for sure. I have since switched to Lineage OS and the fix sticked.
I have problem . Ive installed the fix on AICP 12.1 the phone doesent boot. Returned the old kernel from backup. My phone boots but now i have problem with my hardware buttons, sometimes take 3-4 to respond to the touch. I also deleted and flashed system partititon but problem stil presist.
bankov said:
I have problem . Ive installed the fix on AICP 12.1 the phone doesent boot. Returned the old kernel from backup. My phone boots but now i have problem with my hardware buttons, sometimes take 3-4 to respond to the touch. I also deleted and flashed system partititon but problem stil presist.
Click to expand...
Click to collapse
Is the touchscreen problem fixed? If it's not then this is not my fault. If it is fixed then it's XIAOMI's fault. I will test on my device and report back. Use on-screen buttons until I do some research.
The problem was not in your update. It was from the last AICP update 23.01.2017 i installed 19.01.2017 and buttons are fine now. The touchscreen seems to be fixed iven with full wipe, going back to miui and restoring 19.01.2017 AICP.
Well, I just installed RR on my AUO mi4c, and it doesn't work. The touchscreen is broken and registers touches consistently but strangely. It even does it in recovery. I'm trying to restore my backup now.
EDIT: backup restored. Still don't know why the firmware didn't work
bankov, which flavor of mi4c do you have? Sharp or AUO?
Phlogistol said:
Well, I just installed RR on my AUO mi4c, and it doesn't work. The touchscreen is broken and registers touches consistently but strangely. It even does it in recovery. I'm trying to restore my backup now.
EDIT: backup restored. Still don't know why the firmware didn't work
bankov, which flavor of mi4c do you have? Sharp or AUO?
Click to expand...
Click to collapse
Can you explain the problem a bit more?
Did it get fixed after restoring?
Phlogistol said:
Well, I just installed RR on my AUO mi4c, and it doesn't work. The touchscreen is broken and registers touches consistently but strangely. It even does it in recovery. I'm trying to restore my backup now.
EDIT: backup restored. Still don't know why the firmware didn't work
bankov, which flavor of mi4c do you have? Sharp or AUO?
Click to expand...
Click to collapse
Mine is AUO. My touchscreen was like yours but it was from AICP update.
Basicly im not 100% shure it is fixed but i remember it couldnt register touch on the left bezel if somhere else is toched on the screen. And now is fine.
For anyone applying this from now on, the process is not reversible, because of the way the driver checks if firmware can be updated, it only wants to do upgrades, not downgrades.
Also, for anyone having problems that go away after a clean flash, they are probably not because of my fix.
If they don't go away, there is probably an updated firmware version somewhere that fixes it. I'll extract them again from the newest Nougat version.
Cozzmy13 said:
Can you explain the problem a bit more?
Did it get fixed after restoring?
Click to expand...
Click to collapse
Sure, I was a bit pressed for time yesterday
The touchscreen was inconsistent, for lack of a better word. Touches on a specific point on the screen didn't register on that location, but on some other one. It wasn't random because I could reliably reproduce this. There were also some points on the screen I couldn't reach at all. The capacitive buttons also didn't work. I'd have taken logs, but I couldn't get into developer options
I don't know exactly how this works, but the touchscreen got reversed to its original state when I managed to restore a backup of my earlier TS CM13.1 system from TWRP (I restored all available partitions). It took a few tries because of the weirdness though When I say original state, I mean it still suffers from the multitouch bug, so nothing got fixed.
Hope this is useful, but I'm stumped. Could we have different digitizers?
why is no one discussing stable android 11 for op7p ? got my update round 3 a.m. this morning. been searching all day for a working twrp since the stable android 11 been released. no luck though......
Hi,
Today I installed the update manually and my phone keeps flashing the TWRP load-screen at boot. It's stuck now. Is that because there is no compatible TWRP version yet? How do I fix this?? Any idea?
There is no working TWRP yet for Android 11. You'll need to flash the stock boot.img or rooted boot.img from one of the threads in the news, guides section.
Edit: TWRP screen flashing is because it's incompatible. I had the same issue on the open betas.
Have the exact same issue as above, Twrp screen flashing, cannot boot back to normal even with adb... anybody has a rooted boot.img link that knows works with Android 11?
Should have checked on xda first *slaps his face*
Always check xda first *slaps his face again*
EDIT: For other poor saps with this issue use this -> https://www.androidfilehost.com/?fid=2188818919693770594 I didnt managed to get booted with rooted img but the original boot img file worked well ... at least I got a phone now...
im on 10.3.8 and rooted..
can i just do the same old process.. twrp isnt an issue as long as may apps are safe and root..
santiagoruel13 said:
im on 10.3.8 and rooted..
can i just do the same old process.. twrp isnt an issue as long as may apps are safe and root..
Click to expand...
Click to collapse
No, its not the same process.... For me for example I couldnt get wifi to actually work on rooted image AND you lose the ability to do backups via TWRP..... Refer here for the latest on this: https://forum.xda-developers.com/t/...p-recovery-for-oneplus-7-pro.3931322/page-153
dejjem said:
No, its not the same process.... For me for example I couldnt get wifi to actually work on rooted image AND you lose the ability to do backups via TWRP..... Refer here for the latest on this: https://forum.xda-developers.com/t/...p-recovery-for-oneplus-7-pro.3931322/page-153
Click to expand...
Click to collapse
I mean.. same steps.. that ive used so far amd retain its root.
1. Download rom via o2 updater
2. Flash it via local update
3. Install magisk to inactive slot
4. Reboot.
So if i do this.. wifi wont work??? Is that it???
Finished updating my phone..after downloading it for about 2 hours.
And im quite satisfied with the results. No problems whatsoever..
Glad for you... You probably had already removed the encryption on your mobile... from what I'm reading that is the main incompatibility issue with TWRP...
FWIW after playing around for a day, I had to revert everything Phone wifi was weird (weirder with root and all mods disabled) and system was a little unstable in some 3p apps and there seems to be some bugs with the phone screen 60/90 refresh... Gonna wait a bit to update again.
dejjem said:
Glad for you... You probably had already removed the encryption on your mobile... from what I'm reading that is the main incompatibility issue with TWRP...
FWIW after playing around for a day, I had to revert everything Phone wifi was weird (weirder with root and all mods disabled) and system was a little unstable in some 3p apps and there seems to be some bugs with the phone screen 60/90 refresh... Gonna wait a bit to update again.
Click to expand...
Click to collapse
i dont mind not having TWRP for the meantime,, i just used TWRP previously for flashing CUSTOM kernels.. hehehehe.
anyways, what problem have you encountered regarding wifi?? i dont seem to experience those,, maybe because i came from stable oos 10.3.8..
what app crashed and problems have you encountered???