i did find a official nightly for the condor but need to know whether it supports dual SIM version too (XT1022).
vishalaestro said:
i did find a official nightly for the condor but need to know whether it supports dual SIM version too (XT1022).
Click to expand...
Click to collapse
it supports dual sim. But it has some bug related to call may irritate you... so it is better to stay where you are.
Sent from my XT1022 using XDA Free mobile app
The problem is that the power button restarts my phone and so i need a kernel for the double tap to wake function. I tried the furnace kernel for the stock 4.4.4 but it brought many problems such as call dropping ,touch freeze and so there is a need for me to migrate to a double tap to wake based kernel for the stock 4.4.4. About the call quality problem you said ,what type of problem are you experiencing ? one of my friend runs cm12.1 and he reported that there is no call related issues.
vishalaestro said:
The problem is that the power button restarts my phone and so i need a kernel for the double tap to wake function. I tried the furnace kernel for the stock 4.4.4 but it brought many problems such as call dropping ,touch freeze and so there is a need for me to migrate to a double tap to wake based kernel for the stock 4.4.4. About the call quality problem you said ,what type of problem are you experiencing ? one of my friend runs cm12.1 and he reported that there is no call related issues.
Click to expand...
Click to collapse
Sometimes when phone get call screen doesn't become ON.
and randomly sometimes no sound comes.. completely mute...
It happened with me a lot.. But people are also claiming that this call bug is due to youtube App. So dont install youtube and u might be fine.. if u even get this bug then solution is to make a reboot will solve problem temporarily..
CM 12.1 doesn't need any custom kernel as it has MOTO doze feature which automatically wakes your phone by waving your hand 2 times on proximity sensor... also this doze feature doesn't do any battery drainage..
Sent from my XT1022 using XDA Free mobile app
Yes , moto e xt 1022 dual sim supports cm12.1 .
Intact I have been using it for about a month on mine.
Make sure the twrp version is the latest
Related
Hi all,
For a long time I have being using CM and CM based rome like Slim. Recently (since 4.2.1 and up) I have very annoying issue that is preventing me on using these ROMs as a daily drivers. Namely when my phone boots up I can place only a couple of outgoing calls before they start being rejected with message "Call Ended". That is happening before even call is connected at 0:00. I have tried to google for the problem and have found only that some users on Motorola phones had similar issue back when GB rolled out and they have being able to temporarily correct it by deleting dialer cache. Sadly that doesn't work for me too. Only thing that I can do is to restart my phone...
Thank you for your help guys...
AdoSA said:
Hi all,
For a long time I have being using CM and CM based rome like Slim. Recently (since 4.2.1 and up) I have very annoying issue that is preventing me on using these ROMs as a daily drivers. Namely when my phone boots up I can place only a couple of outgoing calls before they start being rejected with message "Call Ended". That is happening before even call is connected at 0:00. I have tried to google for the problem and have found only that some users on Motorola phones had similar issue back when GB rolled out and they have being able to temporarily correct it by deleting dialer cache. Sadly that doesn't work for me too. Only thing that I can do is to restart my phone...
Thank you for your help guys...
Click to expand...
Click to collapse
Actually I don't know why u r facing this problem may be flashing a different modem will solve your problem
And for reboot... If u have to reboot frequently use a app (forgetting its name) that will restart all your networks in one click without rebooting...
Sent from my GT-I9100 using xda app-developers app
jeetBLswami said:
Actually I don't know why u r facing this problem may be flashing a different modem will solve your problem
And for reboot... If u have to reboot frequently use a app (forgetting its name) that will restart all your networks in one click without rebooting...
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thanks on ur answer but I really don't want to use some app every time I want to make a phone call. Is it possible that modem is causing issues because when I flash 4.1.2 I don't have these issues and also, like I mentioned before, I can make one or two calls after I reboot my phone.
I am using latest version of Epinter's CyanogenMod 10.1 rom. Sometimes, scratch that almost once every hour my phone doesn't wake up when i pressed the power button. My only option is to take out the battery. I' ve seen other people with similar problem but they said it reboots before experiencing this problem, but I don't see any reboot. It even happens when I lock it and try to wake up a second later. Also if my phone is locked in that state when people call me they hear it ringing but my phone gives no response. Does anyone have a similar problem and/or have a solution to this problem. Thnaks in advance.
deep sleep fix or did you not try that? furthermore, you do realize that this could have been posted in the dev thread, and that this is an alpha kernel and an alpha rom and is experimental
Sent from my MB860 using xda app-developers app
Hi All
Any one facing proximity issues here , i saw so many peoples reported in mi forums that when we make a call screen blacks out when we moved to ears( Thats normal) and won't turn back again , so i have to wait the other side person to hangup the call or screen won't turn on power button does work that time, i think this only affects with Sensortek stk3x1x sensor, Redmi note 3 pro comes with two proximity sensors one is from Liteon and other is Sensortek.... Liteon sensors doesn't have this issue, for temporary fix "Wipe proximity area with a cloth or reboot fixes this and it comes back after sometime....( Calibrated but same it works for sometime) no idea wats causing this , issues there in Miui and CM roms....
I found sometimes a flip case with a magnet can cause issues like this when folded right back against the back of the phone, the screen won't come back on because it thinks the flip case is closed.
meangreenie said:
I found sometimes a flip case with a magnet can cause issues like this when folded right back against the back of the phone, the screen won't come back on because it thinks the flip case is closed.
Click to expand...
Click to collapse
yeah but i don't have flipcase, this sensor issues starts with those have "Sensortek Proximity Sensor" Liteon doesn't have issue i think....
Flash the rom again using mi flash tool u will find that yr issue will be solved
Or go to test mode amd calibrate the sensor... that's all
Fastboot flash persist persist.img from latest miui rom? I recently had a problem with sensors. The above cured all
@Hemphiz i think that method for dead sensors bro, this one working sometimes it doesn't mostly if we flash a new rom and use no issues but if we reboot the phone after sometime issue starts.... @ra.one i did that bro flashmiui and recalibrate sensor but that works for temporary please check which sensors you got from this app from playstore https://play.google.com/store/apps/details?id=imoblife.androidsensorbox
if you got Liteon Sensors mostly no issues with proximity, if u got Sensortek u will be having issues or once u got issue it will come back..... im not sure why is causing that..... this is really very annoying bug.... Thousands of people reported in Mi forums about these proximity issues on various devices even on newly launched Redmi 3s/ prime may be they have all got "Sensortek Proximity Sensors".......
This is not a bug, You can disable Prevent Pocket dials under Settings-->Lock screen-->Prevent pocket dials...
I had this since last miui 6.9.9 flash.
Disabled prevent Pocket dials and All is working fine
Edit: for a few hours it was working.
Now its the same again. Phone blacked Out After a call and wont turn on, After a few seconds its coming back. As i said , since flashing new 6.9.9
Android2003 said:
This is not a bug, You can disable Prevent Pocket dials under Settings-->Lock screen-->Prevent pocket dials...
I had this since last miui 6.9.9 flash.
Disabled prevent Pocket dials and All is working fine
Edit: for a few hours it was working.
Now its the same again. Phone blacked Out After a call and wont turn on, After a few seconds its coming back. As i said , since flashing new 6.9.9
Click to expand...
Click to collapse
like i said it may be mostly an issue with Sensortek proximity, can u check which sensors u got from this app https://play.google.com/store/apps/d...droidsensorbox
I have sensortec.
But i think its Software related.
Its since last Update.
I calibrate the Sensor and the issue with calls is still there.
Sensor Works fine, test is okay.
Android2003 said:
I have sensortec.
But i think its Software related.
Its since last Update.
I calibrate the Sensor and the issue with calls is still there.
Sensor Works fine, test is okay.
Click to expand...
Click to collapse
Yes i think its software related but, one trick works clean flash the same rom and use it for a week without any reboot...... (DO CLEAN FLASH and Dont reboot the phone)
don't need to calibrate.... for me when i install new rom and use it for a week no issues , if i reboot the phone the issue starts after sometimes.... i don't knw wats causing it so many peoples with sensortek having issues and this bug is not resolved from Miui 7 to Now Miui 8 MM, the issue there in Custom roms im using RR rom i have issues....
Guys For those having issues Check which sensor you got from this app, if u have proximity issues while calling its mostly "Sensortek"
https://play.google.com/store/apps/details?id=imoblife.androidsensorbox
We need Permanent fix....
I also have exact same issue and i have sensortek sensor. But i can unlock the screen while on a call by pressing power button and then unlocking with fingerprint. Bit annoying
Sent from my Redmi Note 3 using Tapatalk
haree87 said:
I also have exact same issue and i have sensortek sensor. But i can unlock the screen while on a call by pressing power button and then unlocking with fingerprint. Bit annoying
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
So its confirmed its an issue with Sensortek Sensor, no Liteon users reported here, like i told flash the same rom which you are in (clean flash) and don't reboot phone for a week there will be no issues it works perfectly, if u reboot a phone once the issue starts again after sometime so after reboot something is going on no idea what....
i am using this app(for rooted users) on official RR and it works fine
https://play.google.com/store/apps/details?id=com.mobiledirection.proximitysensorreset
anujyadava said:
i am using this app(for rooted users) on official RR and it works fine
https://play.google.com/store/apps/details?id=com.mobiledirection.proximitysensorreset
Click to expand...
Click to collapse
even me used, but i don't think its properly working..... this issue starts only after a reboot, when u flash new roms and after boot dont reboot or power off the phone for a week, not needed any apps, proximity will work properly but once u rebooted issue starts....
But this app's settings load every time phone boots up.so it will work after every boot.
press thanks if I helped u in any way
anujyadava said:
But this app's settings load every time phone boots up.so it will work after every boot.
press thanks if I helped u in any way
Click to expand...
Click to collapse
yes this app i tested earlier, but after sometimes may be in a day or two it won't work....
Found another related issue with proximity , i think proximity is not working properly when there is not enough light around us something related with ambient light sensor i think ..... Eg: if we are in a dark room proximity won't work correctly turn on the light and try it works properly.... i think Xiaomi messed up with something with both sensors Liteon and Sensortek thats why Liteon users face Gyroscope lag in games in dark room and now i think may be the same reason why proximity not working properly in dark room....
hello. I have the BUG but my phone has sensortek version 1 (not 2)
When in a call the screen wont turn off when placing the phone at my ears. With whatsapp the bug wont happend.
I think this is a BUG related to sensor + phone app
A functional workarround is to dial, then press menu (putting the call at background) and then putting the call at foreground again. It works 100% of the time.
Any news? I have this annoying problem too!
Hi guys,
Kind of new to pocophone but I'm experiencing something really strange that I haven't on any other phone I've had before. Here's the background..
I bought the phone as a gift for my mum and she absolutely loves it but she's told me the phone will randomly make a call itself. I didn't believe it until I saw it happen. She can be on the phone (having made or received a call legitimately) and the call will automatically be put on hold waiting for her to answer a call from another person. The issue is, that person hasn't called her so when she calls back, the person is confused. This can also happen when she isn't on the phone
I checked her call waiting options (turned off and on, neither makes a difference) and reset the phone to factory settings but still getting the same issue. We haven't set up Google assistant or anything similar so the calls wouldn't have been made my a voice command either.
It's really strange and I've looked on the Internet but can't find anything reported on it. The phone is running miui 10 and she is on virgin mobile. The phone is less than 2 weeks old.
Any help is much appreciated.
Vik
Haven't faced something similar. If I were in your shoes, I would 1. Factory reset everything, 2. flashed latest global stable miui ROM and 3. checked again if the same problem persists.
melodystyle2003 said:
Haven't faced something similar. If I were in your shoes, I would 1. Factory reset everything, 2. flashed latest global stable miui ROM and 3. checked again if the same problem persists.
Click to expand...
Click to collapse
Thanks @melodystyle2003. I've tried a factory reset on the phone. When the phone does a factory reset, would that not install the latest stable miui ROM? It installed miui 10 and when I checked for updates on the phone, it informed me that there were no more updates available
I think the problem is, proximity sensor. This used to happen to older family member.
About phone->MIUI version, which version does it use?
green. said:
I think the problem is, proximity sensor. This used to happen to older family member.
Click to expand...
Click to collapse
Thanks @green. Did you ever find a solution to that proximity sensor issue?
melodystyle2003 said:
About phone->MIUI version, which version does it use?
Click to expand...
Click to collapse
@melodystyle2003 here's the version information I see when I go to about phone : Miui Global 10.1. Stable. 10.1.3.0. ( PEJMIFI)
vikz.t said:
@melodystyle2003 here's the version information I see when I go to about phone : Miui Global 10.1. Stable. 10.1.3.0. ( PEJMIFI)
Click to expand...
Click to collapse
This is the latest stable version.
Install the google dialer, and force stop the default one. Also, try switching your network connection, like if it's on 3G, shift it to 2G or vice versa, for some time.
And if proximity sensor is the cause (as mentioned by another fellow member), you can check the sensor wake up time through BBS or similar app. Proximity sensor does appear in the sesnor column of BBS app. And going through the wakelock's data, you might also be able to detect any other possible cause.
Have you tried switching off the 'redial automatically' option in the dialer options? That seems to be your problem.
vikz.t said:
Thanks @green. Did you ever find a solution to that proximity sensor issue?
Click to expand...
Click to collapse
It's not the hardware fault. Old people tends to keep the phone slight upwards while speaking, the proximity sensor wakes the screen and by accidentally registers the touch. This usually happens and the accidentally put the call on hold, accepts the second call or the add new call. You can try using the phone for a day.
Old thread, but just wanted to add that we have the same issue with a Pocophone we use at work. When you put away the phone after a call, then at random times it calls the last person you talked to before the current call. Does it about 1 out of 40 calls and is 100% a phone firmware issue, not some old lady holding her phone wrong.
Hello Everyone,
Well to start, after update Sony Xperia 1 III (QX BC-52) to latest system update build number 61.1.A.9.128 I noticed the following couple of problems:
1) When I am in an area where the network coverage is weak, when the phone does not use 3g 4g but only the 2g network, it sometimes happens that the phone cannot make calls as if there is no signal, and also a message for a missed call arrives, or when I someone calls the phone starts ringing and stops after a second, as if someone just called me and hung up.
2) When the mobile data is turned on (wi-fi turned off) and after that it enters the following applications, there is a problem with the interruption of the internet.
1 Music player - play song with max volume level
2.Facebook - start video with sound on max volume level
3. Instagram - start video with sound on max volume level
4 Youtube - start video with sound on max volume level
5. Viber video call
As I wrote at the beginning, I noticed these bugs after the software update. I have been trying to solve this problem for a week in the following ways:
- software reinstallation via Xperia Companion,
- restoring to factory settings,
- resetting network settings, returning apn parameters to factory values,
- despite all that, I took a new sim card, but the problem was still not solved.
After a week of trying to solve this problem, last night I was able to see exactly how this problem occurs, that is, what needs to be done to make this bug appear, and also what needs to be done to prevent this bug from appearing and what the problem is let me know if I do things to fix this problem. This software bug was confirmed by a few more people after the latest system update on a couple of forums (xda developers and reddit xperia. I post this problem on this two sites and get answer.
If you need I can record video and show this bug?
All that needs to be done to detect this bug is the following:
Launch one of the apps I listed above and do the following:
Press the volume up button to the maximum volume level or press and hold once. After that, click a few more times, but you don't have to, and then reduce it by one click or a couple of clicks and repeat this several times. AFTER THAT THE 3G, 4G ICON DISAPPEARS FOR A SECOND, APPEARS AGAIN AND DISAPPEARS AGAIN AND SO MANY TIMES UNTIL WE REDUCE THE VOLUME TO A LITTLE MORE THAN HALF. AT THAT MOMENT WHEN THE 4G ICON DISAPPEARS, DATA TRANSMISSION IS TERMINATED AND THEN THE INTERNET DOESN'T WORK.
I NOTICED THIS PROBLEM FOR THE FIRST TIME WHEN I WAS TALKING ON VIBER ON A VIDEO CALL AND NOT KNOWING WHEN I VOLUME UP ALL THE WAY THE VIDEO CALL CUT OFF, AND THE SAME WHEN I WAS WATCHING A VIDEO ON YOUTUBE AND WHEN I VOLUME IT TO THE MAXIMUM VOLUME LEVEL IN A VERTICAL POSITION THE 4G ICON DISAPPEARS, AND IN A HORIZONTAL POSITION IT PUTS OUT THE MESSAGE AT THE BOTTOM OF THE SCREEN THERE IS NO INTERNET CONNECTION, AND AFTER A FEW SECONDS IT WRITES BACK ONLINE. THIS KIND OF NONSENSE AFFECTS THE USER EXPERIENCE A LOT. IMAGINE WHEN YOU ARE WATCHING A VIDEO ON YOUTUBE AND EVERY MOMENT YOUR MOBILE DATA CUT OFF AND DURING A VIDEO CONVERSATION ON VIBER, YOUR VIDEO IS INTERRUPTED. I NOTICED THESE COUPLE OF BUGS, FOUND IN WHICH SITUATIONS THEY APPEAR AND WHAT TO DO TO PREVENT THEM FROM OCCURRING, BUT IN TURNS, SOME OTHER PROBLEM ARISES.
IMAGINE WHEN YOU ARE WATCHING A VIDEO ON YOUTUBE AND EVERY MOMENT YOUR MOBILE DATA TURN OFF AND DURING A VIDEO CONVERSATION ON VIBER, YOUR VIDEO IS INTERRUPTED. I NOTICED THESE COUPLE OF BUGS, FOUND IN WHICH SITUATIONS THEY APPEAR AND WHAT TO DO TO PREVENT THEM FROM OCCURRING, BUT IN THIS CASE SOME OTHER PROBLEM ARISES. IF YOU SET THE VOLUME ON MAX LEVEL THIS BUG WILL TURN OFF YOUR MOBILE DATA EVERY SECOND, BUT IF YOU SET VOLUME LEVEL ON THE MIDDLE OR LITTLE HIGHER THIS BUG WILL BE GONE.
SONY XPERIA TEAM, I HAVE FOUND THIS BUG, AND RESEARCHED AND SHOW HOW IT AFFECTS THE USER EXPERIENCE, AND IT'S UP TO YOU TO FIX THIS PROBLEM AS SOON AS POSSIBLE. THE PHONE COSTS OVER 1000E AND I THINK IT IS UNACCEPTABLE THAT SUCH PROBLEMS ARE OCCURRING. OTHERWISE, I AM A LONG-TERM SONY USER SINCE THE AGE OF SONY ERICSSON. THANKS A LOT
This sounds like a flaw in RF shielding or power stability. The OS should have hacks to avoid triggering conditions of common defects - stuff like making sure variable digital clocks don't align with the radio signals and pulses of power consumption don't overlap to an overload.
If yours is uncommon you might need a warranty replacement.
My US model has a lot of weird radio, touchscreen, and fingerprint glitches that haven't been completely fixed in updates. Good luck.
XQ-BC72 61.1.A.9.219 have fixed mobile data bug
evaokay said:
XQ-BC72 61.1.A.9.219 have fixed mobile data bug
Click to expand...
Click to collapse
Im debating if I should go back to stock since Evolution Gsi aren't being updated. I may start building them
bountyman334 said:
Im debating if I should go back to stock since Evolution Gsi aren't being updated. I may start building them
Click to expand...
Click to collapse
Yes please Make a Evolution GSI for the Xperia 1 III
Ainz_Ooal_Gown said:
Yes please Make a Evolution GSI for the Xperia 1 III
Click to expand...
Click to collapse
There is one but it's not being maintained.
21.3 GB folder on MEGA
17 files and 16 subfolders
mega.nz
bountyman334 said:
There is one but it's not being maintained.
21.3 GB folder on MEGA
17 files and 16 subfolders
mega.nz
Click to expand...
Click to collapse
But I want it to updated daily. No choice but to builf
evaokay said:
XQ-BC72 61.1.A.9.219 have fixed mobile data bug
Click to expand...
Click to collapse
I've just wanted to ask about the new update all I have to do is to wait for the EEA customized
LaceeWearsPrada said:
I've just wanted to ask about the new update all I have to do is to wait for the EEA customized
Click to expand...
Click to collapse
Xperia 1 III: 61.1.A.9.219
This system software update features
Android security patch level: July 1st, 2022
One thing with this latest version is that magisk doesn't play nice. I think Google got johnwu to give up the back door to his method. I mean that using the Kirisakura_Sagami_S_2.0 kernel will cause you to bootloop. Until u reflash using new flasher to save your data
bountyman334 said:
One thing with this latest version is that magisk doesn't play nice. I think Google got johnwu to give up the back door to his method. I mean that using the Kirisakura_Sagami_S_2.0 kernel will cause you to bootloop. Until u reflash using new flasher to save your data
Click to expand...
Click to collapse
Which magisk you use ? I am on latest fw .219 and magisk 25.2 just works fine.
Pandemic said:
Which magisk you use ? I am on latest fw .219 and magisk 25.2 just works fine.
Click to expand...
Click to collapse
Yep Magisk 25.2 app and 25.2 (25200) Magisk install...just saw this and updated myself just to get the infinite Xperia Boot Animation
Ainz_Ooal_Gown said:
Yep Magisk 25.2 app and 25.2 (25200) Magisk install...just saw this and updated myself just to get the infinite Xperia Boot Animation
Click to expand...
Click to collapse
Patch your boot.img with magisk 25.2 i did it to and works fine
Pandemic said:
Patch your boot.img with magisk 25.2 i did it to and works fine
Click to expand...
Click to collapse
no your using stock kernel. I was using Sagami. now on evo11
bountyman334 said:
One thing with this latest version is that magisk doesn't play nice. I think Google got johnwu to give up the back door to his method. I mean that using the Kirisakura_Sagami_S_2.0 kernel will cause you to bootloop. Until u reflash using new flasher to save your data
Click to expand...
Click to collapse
Both statements are incorrect. There's no backdoor that magisk is using. Magisk requires bootloader unlock, there's no backdoor needed.
Kernel works also fine on latest firmware on my end.
After updating my Sony Xperia 1 III to the latest software version build number 61.1.A.9.219 all the problems or bugs that I wrote in this post that I published here on XDA developers are resolved. No more problems with mobile data, no more interruptions during phone calls. Sony team, thank you very much for solving these problems that existed in the previous version of the software in the shortest possible time. Thanks to all the people who gave their suggestions on how to solve the problems here.