Hello!
My phone doent go deep sleep randomly
BBS and kernel logs show:
-1:misconfigured IRQ 43 smp2p
-1:misconfigured IRQ 470 glink-native (!!!!!!!!! this is a main mistake)
Spoiler: previous time
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Spoiler: new time after fastboot
On any firmware / rom / kernel, stock or non-stock
I tried fastboot official rom - but problem still
It fixes only with reboot.
Pls, help me!
Probably not in time, but will post for people googling solution.
Yes, this is common important problem which Xiaomi not rush to fix during at least 5 months. This related to modem / radio. Confirmed that changing SIM card for new from operator can fix drain but not for all.
Thankfully, @uditkarode fixed this in his έpsilon kernel.
In commit he just limits wakelock time to 250 ms instead infinity.
To install kernel you need to unlock bootloder (wait 7 days) and install TWRP.
Bonoboo said:
Probably not in time, but will post for people googling solution.
Yes, this is common important problem which Xiaomi not rush to fix during at least 5 months. This related to modem / radio. Confirmed that changing SIM card for new from operator can fix drain but not for all.
Thankfully, @uditkarode fixed this in his έpsilon kernel.
In commit he just limits wakelock time to 250 ms instead infinity.
To install kernel you need to unlock bootloder (wait 7 days) and install TWRP.
Click to expand...
Click to collapse
Thank you , i investigated that problem is modem/radio.. but no really solution
I tried epsilon + arrow, no mistakes for now, but still active mode randomly, need to reboot phone
Phone heats 43°C while talking by phone.
Some of us testing crdroid + epsilon now, 3 days without active mode, but i think that doesn't help in distance
Xiaomi doesn't want to fix that, i sent a lof of bug reports
Changing sim doesnt help too
bodyajoy said:
still active mode randomly
Click to expand...
Click to collapse
Hmm, what wakelock shown in bugreport, same smp2p?
Also first versions of epsilon kernel till "26jul" had no fix, so maybe that was your case.
Bonoboo said:
Hmm, what wakelock shown in bugreport, same smp2p?
Also first versions of epsilon kernel till "26jul" had no fix, so maybe that was your case.
Click to expand...
Click to collapse
have no opportunity to see bugreport now
i use last version of epsilon, august
Our group (that have this problem) tried almost everything for this 5 months, every fix we found on the Enternet was tried, every custom. Last chance is crDroid + Epsilon, if it won't have problem for 1 week, our group will install it with full wipes and test it
bodyajoy said:
have no opportunity to see bugreport now
i use last version of epsilon, august
Our group (that have this problem) tried almost everything for this 5 months, every fix we found on the Enternet was tried, every custom. Last chance is crDroid + Epsilon, if it won't have problem for 1 week, our group will install it with full wipes and test it
Click to expand...
Click to collapse
Did you ever figure this out? - Having a similar problem with my Poco X3 Pro
bodyajoy said:
Thank you , i investigated that problem is modem/radio.. but no really solution
I tried epsilon + arrow, no mistakes for now, but still active mode randomly, need to reboot phone
Phone heats 43°C while talking by phone.
Some of us testing crdroid + epsilon now, 3 days without active mode, but i think that doesn't help in distance
Xiaomi doesn't want to fix that, i sent a lof of bug reports
Changing sim doesnt help too
Click to expand...
Click to collapse
Hmmmm, Are you sure about this problem?
Related
My device is constantly awake on the current build after doing a full clean flash (twice).
Something in the system is holding awake after the screen is off.
So I've tried stock OOS and CM13, and I am still getting the same wakelock so that means it is not ROM dependent, something else changed within my phone that is causing this wakelock.
I first started noticing this wakelock when I tried the offical ResurrectionRemix 7.1 from here, after flashing that ROM, I've had the wakelock on all other roms. Anyone have any ideas about how to solve this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
check with better battery stats app and post Screenshots
ForcedZucchini said:
My device is constantly awake on the current build after doing a full clean flash (twice).
Something in the system is holding awake after the screen is off.
So I've tried stock OOS and CM13, and I am still getting the same wakelock so that means it is not ROM dependent, something else changed within my phone that is causing this wakelock.
I first started noticing this wakelock when I tried the offical ResurrectionRemix 7.1 from here, after flashing that ROM, I've had the wakelock on all other roms. Anyone have any ideas about how to solve this?
Click to expand...
Click to collapse
Take it off the charger.
Sent from my OnePlus 3T using XDA Labs
Try the wakelock detector app
Sent from my ONEPLUS A3000 using Tapatalk
Attaching some wakelock screenshots. These also show that it is off the charger.
Id format everything in twrp after saving anything valuable. Then I'd install a ROM without flashing Google apps. I wouldn't even login or sign-in or install a single app after booting up. Then see if the issue is still present. If it is gone then you know it's either your apps or Google but not the ROM or phone.
954wrecker said:
Id format everything in twrp after saving anything valuable. Then I'd install a ROM without flashing Google apps. I wouldn't even login or sign-in or install a single app after booting up. Then see if the issue is still present. If it is gone then you know it's either your apps or Google but not the ROM or phone.
Click to expand...
Click to collapse
So here is what I've tried so far:
I installed stock OOS Recovery over TWRP. Through the stock recovery I sideloaded the official OOS 4.0 Nougat release and wiped the phone clean through recovery selecting the option (Erase everything (pics, vids, etc.)). I then rebooted the phone and completed set-up by skipping everything and no google sign in. I am still getting the constant wake issue.
I also noticed the following kernel wakelocks that show 99% and 69% usage respectively:
1. fusb301_otg_wl
2. 6a00000.ssusb
I found these threads around the wakelocks above.
https://forum.xda-developers.com/showthread.php?p=68634552#post68634552
^ This one suggests clearing cache on Play Services, I tried this and still not working.
https://forum.xda-developers.com/oneplus-3/help/otg-wakelock-problem-t3511310
https://forum.xda-developers.com/oneplus-3/help/6a00000-ssusb-wakelock-wld-bbs-t3463062
Just wanted to update in case anyone else has this problem. I have fixed the issue.
I flashed 3.5.4 OOS and then proceeded to install CM13. I am no longer experiencing constant wake on CM or OOS.
ForcedZucchini said:
Just wanted to update in case anyone else has this problem. I have fixed the issue.
I flashed 3.5.4 OOS and then proceeded to install CM13. I am no longer experiencing constant wake on CM or OOS.
Click to expand...
Click to collapse
Will try this. Hopefully this helps.
The problem has actually reappeared for me on OOS. Still not sure what is causing it...
Screenshot attached is me currently running OOS Nougat beta.
I've got already the same problem
ForcedZucchini said:
The problem has actually reappeared for me on OOS. Still not sure what is causing it...
Screenshot attached is me currently running OOS Nougat beta.
Click to expand...
Click to collapse
Did you solve the problem? I'm bored with this new phone. Thanks
hi...my note 5 has deep sleep issue on android N and I've root my note with twrp but not fixed...please fix it dr.ketan :crying:
i love android N but my battery is troubling :crying:
Full wipe and flash rom. I'm not issue deep sleep. Full wipe sistem,data,cache,dalvik/art.....
Ivpiter said:
Full wipe and flash rom. I'm not issue deep sleep. Full wipe sistem,data,cache,dalvik/art.....
Click to expand...
Click to collapse
No. Not fixed
meysam.m09 said:
hi...my note 5 has deep sleep issue on android N and I've root my note with twrp but not fixed...please fix it dr.ketan :crying:
i love android N but my battery is troubling :crying:
Click to expand...
Click to collapse
I requested respected @dr.ketan a week ago the same, but he said that he found no such issue on Nouagt.
But I'm facing it and Now you too.... You can request dr may be he can look into the issue
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
meysam.m09 said:
hi...my note 5 has deep sleep issue on android N and I've root my note with twrp but not fixed...please fix it dr.ketan :crying:
i love android N but my battery is troubling :crying:
Click to expand...
Click to collapse
install this https://play.google.com/store/apps/details?id=com.asksven.betterbatterystats and see if you really have the "deep sleep issue" because on everything stock on nougat i had no problems with deep sleep
Ijaz Farooq said:
I requested respected @dr.ketan a week ago the same, but he said that he found no such issue on Nouagt.
But I'm facing it and Now you too.... You can request dr may be he can look into the issue
Click to expand...
Click to collapse
Are you so post #06 ?
I have the same issue when I tripped my knox when I rooted my phone in MM. I had to flash a kernel when I was on MM but have not found a kernel for N yet. Now I have uodated my phone to N and the deep sleep trouble is back.
dmbOi said:
I have the same issue when I tripped my knox when I rooted my phone in MM. I had to flash a kernel when I was on MM but have not found a kernel for N yet. Now I have uodated my phone to N and the deep sleep trouble is back.
Click to expand...
Click to collapse
There is no deep sleep issue actually on Nougat. Only a few users face it. I suggest you start fresh, factory reset your device and should be good.
Use smart switch, device initialization.
Deep sleep issues already confirmed Fix on Android N.
sunny1119 said:
There is no deep sleep issue actually on Nougat. Only a few users face it. I suggest you start fresh, factory reset your device and should be good.
Click to expand...
Click to collapse
I did what you suggested and so far it's working fine now. ?
---------- Post added at 11:52 AM ---------- Previous post was at 11:51 AM ----------
sunny1119 said:
There is no deep sleep issue actually on Nougat. Only a few users face it. I suggest you start fresh, factory reset your device and should be good.
Click to expand...
Click to collapse
Did what you have suggested and so far it is working fine now! Thanks a lot!
I got deep sleep issue today on my note 5
Tried resetting device and flash from ordinary. Not works for me. Plz help
deep sleep issue with nougat and moto x pure?! was fine prior to 7.0 (patch level oct 1, 2017), but now stacks notifications at night but not during day. checked settings and as far as i can tell all are consistent with stay awake.
resolved
contacted motorola support. wiped cache and reinstalled nougat. seems to be ok now. first tech i talked to was not at all helpful. actually hung up on me because i was a bit slow on following his incomplete directions. second tech was helpful and resolution was quick.
Not my work... Just sharing what I came across...
Works great on our device (with bugs, ofcourse)...
https://mega.nz/#F!3XwFlAaC!VdzCKlrR-f6D-a8oEz9JkQ
INSTRUCTIONS
Clean Flash
Download the zip of GSI
Extract the system.img
Flash any treble enabled ROM.
Wipe: Dalvik and Cache
Flash the GSI (system image) from recovery
Reboot & Enjoy
Source - https://forum.xda-developers.com/pr...vice-development/9-0-lineage-os-16-0-t3840801
Thanks which one supports to be download
kpmohamedhussain said:
Not my work... Just sharing what I came across...
Works great on our device (with bugs, ofcourse)...
https://mega.nz/#F!3XwFlAaC!VdzCKlrR-f6D-a8oEz9JkQ
INSTRUCTIONS
Clean Flash
Download the zip of GSI
Extract the system.img
Flash any treble enabled ROM.
Wipe: Dalvik and Cache
Flash the GSI (system image) from recovery
Reboot & Enjoy
Click to expand...
Click to collapse
I see two folders on the link.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my ONEPLUS A3003 using Tapatalk
Ours is A only...
Camera fix - https://androidfilehost.com/?fid=1322778262904000685
Call fix - Set phone app as primary
Root - Magisk 16.7
Hotspot doesn't work...
Other minor bugs in normal LOS 16 remains as is...
kpmohamedhussain said:
Camera fix - https://androidfilehost.com/?fid=1322778262904000685
Call fix - Set phone app as primary
Root - Magisk 16.7
Hotspot doesn't work...
Other minor bugs in normal LOS 16 remains as is...
Click to expand...
Click to collapse
can you share some screen shots like Settings, about phone , kernel version etc?
and the source portal?
xuser_ said:
can you share some screen shots like Settings, about phone , kernel version etc?
and the source portal?
Click to expand...
Click to collapse
Updated OP with source... Reverted back to normal LOS 16... If possible when time persists today will flash again and get screen shots...
kpmohamedhussain said:
Updated OP with source... Reverted back to normal LOS 16... If possible when time persists today will flash again and get screen shots...
Click to expand...
Click to collapse
Ok, but out of curiosity why not use LOS 16.0 or NOS 9.0???
xuser_ said:
Ok, but out of curiosity why not use LOS 16.0 or NOS 9.0???
Click to expand...
Click to collapse
Thus is just to experience treble, the future for our device...
kpmohamedhussain said:
Thus is just to experience treble, the future for our device...
Click to expand...
Click to collapse
Not really.
First of all, you can't really experience Treble. There's nothing different for the user, it's just for developers to easier port newer Android versions.
Secondly, it's somewhat pointless if it isn't properly implemented by the manufacturer. There's no benefit to port new version "easily" if you hame much more trouble to get Treble in the first place; might as well use those resources to port the ROM "the old way".
And lastly, as long as hardware manufacturers provide new drivers it's better to have it the old way.
Basically, porting Treble to old devices is more or less an experiment and a fun project for devs, not really expected to work flawlessly or take off.
Sent from my OnePlus 3 using Tapatalk
Well if this is mature, it can benefit both parties though IMO
For users, we can finally have an OS for all hardware just like in PC/Laptop enviroment
For devs, more user will use their product (build), mean increase in donation.
Later it would bring forth companies that build a paid/premium ROM. More devs would get a regular payment rather than relying in donations.
The rom can just including the generic driver to make the phone function for later use to install the driver from manufacture.
Manufacture would be forced to release a constant working driver or else get blamed by all parties.
All that later, we can say goodbye to bootloader lock since phone manufacture would just selling a phone, not the OS inside it.
The main issue here is that this thread is not a development thread, just basically a link towards the thread itself. Not sure this is the right place for that
Installed Beta 2 (which I believe corresponds with Beta 5 on the Pixels) a couple days ago. It is available here.
It has the September 5 security patch, and overall works well. The only bug I have noticed so far is in Settings when trying to set links that an app opens by default. It worked but crashed, and sent me back to my home screen.
I used a debloater via Magisk to remove Asus apps.
How the battery is better or worse compared to the 11.
dar12ek said:
How the battery is better or worse compared to the 11.
Click to expand...
Click to collapse
Tough to tell but I'd say better.
thatguy222 said:
Installed Beta 2 (which I believe corresponds with Beta 5 on the Pixels) a couple days ago. It is available here.
It has the September 5 security patch, and overall works well. The only bug I have noticed so far is in Settings when trying to set links that an app opens by default. It worked but crashed, and sent me back to my home screen.
I used a debloater via Magisk to remove Asus apps.
Click to expand...
Click to collapse
So this is already an Asus customized android (Zen UI Version)? Afaik the beta 1 was more of a vanilla android without the Asus flavor
Using beta 2 as a daily driver. And i'm really impressed by the aesthetics and the stability of the system. Everything works as intended for me.
Only missing thing is a complete french translation of the system.
How to install Beta 12 I try but pops up with the message "The script can't be used in this devices, hwid =, project = project"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
just reboot to bootloader. solved it for me.
dar12ek said:
How to install Beta 12 I try but pops up with the message "The script can't be used in this devices, hwid =, project = project" View attachment 5412043
Click to expand...
Click to collapse
I have an unlocked bootloader but it does not go to the bootloader.
reboot using "adb reboot bootloader"
Do I have to wait some time after unlocking tat as it was in xiaomi.
No you just need to enable USB debugging in developer options. Run the command in cmd and run the bat script provided in the zip.
When I go to the bootloader, I only have this screen
When I go to Fastboot, I only have such a screen, I marked it with a red arrow or it means that I have a locked bootloader.
When unlocking, this message pops up, does it mean that I have to set a pin code before unlocking.
I installed, I had to install asus drivers, I also have an incomplete Polish translation
A critical bug that i found is when trying to set a google account for the twin apps forces you to factory reset afterwards.
morpheus302 said:
A critical bug that i found is when trying to set a google account for the twin apps forces you to factory reset afterwards.
Click to expand...
Click to collapse
Before installing the system, you must delete the Google account so that this error does not appear
This beta has bugs. I will not install it. If your phone is a test mouse and you don't care about it, do it. Everything official is better than beta.
Ibrahim.69 said:
This beta has bugs. I will not install it. If your phone is a test mouse and you don't care about it, do it. Everything official is better than beta.
Click to expand...
Click to collapse
Can you point the bugs you found?
Just above someone wrote he uses it daily and it works great...
I hope that 12 will be officially released soon, however.
Any long time impressions?, how is battery life?
I've been running it (beta 2) since it was released. Overall, it is good. Most annoying issue is sometimes it just doesn't charge until I power cycle the phone. Maybe 50% of the time.
A more minor issue is that some notifications can't be swiped away until I power cycle. Can't think of any more issues off the top of head.
Hello everyone, hope you guys are having a great day! I've bought my phone (realme 8/4g) about a week ago, it's working fine except the wifi segment. Wifi gets disconnected and reconnects on it's own. I've tried to solve the issue through several methods:-
1. Checked the router as well as frequency (2.4/5Ghz), both of them are working fine as well as i'm running my primary device using the same network it didn't face any issue! Router--> Deco M4, dual unit [firmware is up to date]
2.did a network reset of the phone but in vain.
I've got an update few days ago, after that the issue has been occurring frequently. Before the update the phone was somehow stable! Please find me a soln. Also, provide me the best working gcam rn for this device!
Thanks a ton!
What version you have ? A_22 or A_24 ?
DaLiV said:
What version you have ? A_22 or A_24 ?
Click to expand...
Click to collapse
A_24
can try to flash back A_22 (links to images are in the near topic), afterwards disable update ... and test...
WIFI - sometimes can be some vendor coexistence problems , also as channels (when above 12 or above 52) ... or even WPA-3-Drafted router ...
+ MESHING !!! - that is oft not nice ... cabling rulez ...
DaLiV said:
can try to flash back A_22 (links to images are in the near topic), afterwards disable update ... and test...
WIFI - sometimes can be some vendor coexistence problems , also as channels (when above 12 or above 52) ... or even WPA-3-Drafted router ...
Click to expand...
Click to collapse
As it's running somehow well that's why don't wanna downgrade. Is there any good custom rom which may solve the issue?
Wizzie.Lord said:
As it's running somehow well that's why don't wanna downgrade. Is there any good custom rom which may solve the issue?
Click to expand...
Click to collapse
Wizzie.Lord said:
As it's running somehow well that's why don't wanna downgrade. Is there any good custom rom which may solve the issue?, wifi channels can't be controlled, it's an autonated system of deco
Click to expand...
Click to collapse
Wizzie.Lord said:
I've got an update few days ago, after that the issue has been occurring frequently
Click to expand...
Click to collapse
Wizzie.Lord said:
As it's running somehow well
Click to expand...
Click to collapse
So ... simple decide self ... Well ot not so well ...
on my sight - outages in networking is not good thing ...
No custom roms seen at the moment
Additional possibility - are you using simultaneously with bluetooth and connected to 2.4Ghz ? - then can forcibly try to divide net for 2.4 and 5 ghz ... and connect to 5 implicit ...
DaLiV said:
Additional possibility - are you using simultaneously with bluetooth and connected to 2.4Ghz ? - then can forcibly try to divide net for 2.4 and 5 ghz ... and connect to 5 implicit ...
Click to expand...
Click to collapse
Nope, i was only using wifi then
after updating to android 12 version c.07, I can't login to my home 5G wifi. Before the update everything was without problem. Does anyone have any experience or knows the cause?
I have the Realme 8 5G and I also had the problem of disconnection with a TP-Link Deco M5 and the solution was to deactivate the mesh technology for my device from the deco app and thus the disconnection problem was solved
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}