On 2.9 version, mm 6.01, mokee rom, boost mode, experiencing constant 'sign in to network ' notifications for both cellular and WiFi networks while the network connection is ok.
Screen is attached.
I have the same issue. It even says 'no internet connection. But all works fine. Its bothering me though.
dimdimdim said:
On 2.9 version, mm 6.01, mokee rom, boost mode, experiencing constant 'sign in to network ' notifications for both cellular and WiFi networks while the network connection is ok.
Screen is attached.
Click to expand...
Click to collapse
And even more. I disabled all the settings in greenify one by one and then disabled the exposed module, then reboot, then deleted greenify via force stop/clear data/uninstall, then cleared all the caches and... Nothing happened. The notifications are still here.
The only difference I see the Internet speed is seemingly lower. So, I've run Google fiber test and found it says 'no servers responded '.
So, there is a problem.
Taking into account I see no other answers here, I will re-flash the rom keeping my data. Hope, the changes were made to system, so it should help.
I didnt have the issue by reflashing. It just suddenly started to happen. I gonna flash my ROM to the latest and hope it gets resolved. This is a dealbreaker for me. Hope it gets solved fast.
avsmartmobiles said:
I didnt have the issue by reflashing. It just suddenly started to happen. I gonna flash my ROM to the latest and hope it gets resolved. This is a dealbreaker for me. Hope it gets solved fast.
Click to expand...
Click to collapse
No, the problem occured not after a rom reflash, but just after greenify installation. I used system reflash in hopes to fix the issue. But it doesn't help. Seems, the changes are somewhere in data and I just don't know where.
dimdimdim said:
No, the problem occured not after a rom reflash, but just after greenify installation. I used system reflash in hopes to fix the issue. But it doesn't help. Seems, the changes are somewhere in data and I just don't know where.
Click to expand...
Click to collapse
Check this url: https://www.reddit.com/r/cyanogenmod/comments/4jo86y/cm13_wifi_connected_with_no_internet_sign_but/
I dont know how to do it. Do you know what we have to do?
avsmartmobiles said:
Check this url: https://www.reddit.com/r/cyanogenmod/comments/4jo86y/cm13_wifi_connected_with_no_internet_sign_but/
I dont know how to do it. Do you know what we have to do?
Click to expand...
Click to collapse
Okay, seems there is a way to fix it, close to what you've found: http://android.stackexchange.com/qu...ction-how-to-remove-exclamation-mark-on-wi-fi
The steps:
1. You should be rooted
2. Install any terminal emulator
3. Run it
4. Enter su
5. press enter
6. Enter
settings put global captive_portal_detection_enabled 0
7. Press enter
8. Reboot
I've check it and it works for me.
I'm not sure it's the best solution, but it works for this problem at least.
Damn im a noob i cant even post an Image here. I did the Steps u Said but I get : global captive_portal_detection_enabled 0
The program 'global' is not installed. Install it by executing:
apt install global
$
Van you print Screen it for me please ?
I cant seem to fix it. I get An error in the command. See printscreen. Please Help.
avsmartmobiles said:
I cant seem to fix it. I get An error in the command. See printscreen. Please Help.
Click to expand...
Click to collapse
You must enter first command
su
After that press
enter
And then copy the whole line of the command
settings put global captive_portal_detection_enabled 0
And then press
enter
again.
On the second screen you made it correct but forget to enter
su
before
dimdimdim said:
You must enter first command
su
After that press
enter
And then copy the whole line of the command
settings put global captive_portal_detection_enabled 0
And then press
enter
again.
On the second screen you made it correct but forget to enter
su
before
Click to expand...
Click to collapse
Thanks a lot men I think its fixed.
But now, as I supposed, the sign in to networks, which really need sign in (all public hotspots), doesn't throw out the notification.
I suppose it's still possible to sign via browser, but...
Worked for me
Thanks Bro! It worked for my mokee L 5.1 Rom on xiaomi Redmi 1s
dimdimdim said:
Okay, seems there is a way to fix it, close to what you've found: http://android.stackexchange.com/qu...ction-how-to-remove-exclamation-mark-on-wi-fi
The steps:
1. You should be rooted
2. Install any terminal emulator
3. Run it
4. Enter su
5. press enter
6. Enter
settings put global captive_portal_detection_enabled 0
7. Press enter
8. Reboot
I've check it and it works for me.
I'm not sure it's the best solution, but it works for this problem at least.
Click to expand...
Click to collapse
Thanks for this! I recently received the OTA update to 7.1.1 on my Nexus 6P. After the update, it kept pestering me to sign into my company's wifi portal page. When I clicked the alert, the page would load and then the entire window would close. If I tried again, the same thing would happen. The alert would immediately return and I couldn't figure out how to get rid of it. I'm not using Greenify so I hope this solution helps others who have a similar problem.
Thanks. It worked for me.
Related
So I have had this issue with my phone today where I couldn't seem to get passed the Too many pattern attempts screen.
After trying all my combinations of e-mail and passwords, I was unable to access my phone. As a result, I attempted to do a hard reset (the pressing of both volume rockers and then trying to reset it in that recovery mode).
I did so, wiping all my data, but the too many pattern attempts screen remained. So as a result, I booted up Odin and downloaded the stock versions of the Samsung Fascinate's ROM and proceeded to reflash (or what I believe to be reflashing, I simply followed the directions found in the stickies).
That all said and done, my phone still remains in the too many pattern attempts lock.
I've checked the similar posts on a couple of websites, but was unable to find a situation where all of these fixes did not work.
Thank you!
No replies yet, so I am just going to throw this out there on the off chance that it *might* actually work.
The "complete voodoo lagfix removal" uninstall.zip CWM flash seems to be working as a cure-all for just about whatever may ail your phone, whether you actually *have* voodoo or not...
I would check that out in the OP of this thread.
Download the Voodoo Uninstall on your PC. Copy it to your SDcard (if you don't have a computer that you can put the card in after pulling it out of your phone, try using adb to push it to the phone)
Boot into stock recovery, and flash "update.zip" to get into CWM recovery.
Flash that voodoo uninstall zip using CWM.
I really hope this helps. (Just in case it happens to me. )
Let us know!
I work for flextronics. we see this all the time. it's a known issue that the lock screen doesn't reset with a factory wipe. just call the phone, answer and press the home screen button. it's what we do in store
Sent from my SCH-I500 using XDA App
This is more than likely living in /dbdata . You can wipe that by doing a privacy wipe in settings (requires access to the phone), or flash CWM via odin, and then when in recovery, rm -r /dbdata/ and reboot.
If the phone-call / home button thing else_where posted works, obviously go that route, then do a privacy wipe.
namebrandon said:
This is more than likely living in /dbdata . You can wipe that by doing a privacy wipe in settings (requires access to the phone), or flash CWM via odin, and then when in recovery, rm -r /dbdata/ and reboot.
If the phone-call / home button thing else_where posted works, obviously go that route, then do a privacy wipe.
Click to expand...
Click to collapse
you will more than likely need to mount the /dbdata partition r/w before you can delete the data. This is covered in the Voodoo removal thread (which I had the joy of doing).
martian21 said:
you will more than likely need to mount the /dbdata partition r/w before you can delete the data. This is covered in the Voodoo removal thread (which I had the joy of doing).
Click to expand...
Click to collapse
Good point!
mkdir /dbdata
mount -t rfs -o nosuid,nodev,check=no /dev/block/stl10 /dbdata
else_where said:
I work for flextronics. we see this all the time. it's a known issue that the lock screen doesn't reset with a factory wipe. just call the phone, answer and press the home screen button. it's what we do in store
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
You work for Flextronics ???? Didn't Verizon end their contract with them for all regions already ????
working in an A class store. allot of the philly market and north east stores still have techs. besides or sales people are helpless. like every time with a cellbrite is their first time
Sent from my SCH-I500 using XDA App
Hey guys thanks for all the help,
The calling of the phone didn't work. Tried it, but it kept giving me corrupt errors so I wasn't able to access the home screen.
The voodoo removal sort of worked in that while I was doing it, I also went ahead and did a privacy wipe. Everything would be fine and dandy however, my phone no longer connects to any network. It seems to be in a perpetual state of being unable to find a network. It's not airplane mode, but my phone does think it's January first 2005 again.
Did I miss a step?
runeliger said:
Hey guys thanks for all the help,
The calling of the phone didn't work. Tried it, but it kept giving me corrupt errors so I wasn't able to access the home screen.
The voodoo removal sort of worked in that while I was doing it, I also went ahead and did a privacy wipe. Everything would be fine and dandy however, my phone no longer connects to any network. It seems to be in a perpetual state of being unable to find a network. It's not airplane mode, but my phone does think it's January first 2005 again.
Did I miss a step?
Click to expand...
Click to collapse
You did the privacy wipe from within the settings menu ???? That fixed a similar issue where I couldn't connect to the network
mexiken said:
You did the privacy wipe from within the settings menu ???? That fixed a similar issue where I couldn't connect to the network
Click to expand...
Click to collapse
Yes indeed I did. The first thing I did was the Factory data reset.
Unfortunately, the phone seems to be in a state of perpetual ariplane mode preventing access to any network.
The phone also seems to be suffering from that com.android.phone crashes that I suppose make sense given how the Hardware version and the Baseband version are both unknown.
I'm going to try to flash it again in hopes of resetting my phone. The perpetual airplane mode is of course an issue. (but at least I got the alarm functinoality of my phone back)
Hrm, I'm concerned now. Check your settings / about phone and baseband version. Please tell me it does not say 'unknown'.
Yea, mine wasn't stuck in airplane mode, just didn't connect to google's servers to set up gmail.
If you're still rooted, maybe try the radio update ????
Any update ????
mexiken said:
maybe try the radio update ????
Click to expand...
Click to collapse
DANGER! - Don't go updating your radio unless you really know what you're doing. Yes there has been a radio update with the D01 however flashing the wrong thing to the radio will result in a shiny brick that as of right now can't be recovered!
Yeah I was seeing a bunch of unknowns in a lot of my slots.
I wasn't sure what was wrong, so I did some more research and it seemed as though that the modem aspect of my phone must have corrupted.
So I simply went to a verizon store and swapped out my phones (since I couldn't find a fixed modem).
The other fix of deleting via the privacy wipe definitely worked though.
Thanks everyone!
i500 fascinate too many patterns
what I did I turn the phone off
then turn it on ones the one verizon animation goes of it asks for the email and pass so start hitting home button as fast as you can and sometimes emergency button till it takes you to the main many do not stop till al the icons load up
then you got it but you have to go in to the menu and wipe it off or erease the email account
it worked for me after few tries it shoulg work for you too
anngiehdz said:
what I did I turn the phone off
then turn it on ones the one verizon animation goes of it asks for the email and pass so start hitting home button as fast as you can and sometimes emergency button till it takes you to the main many do not stop till al the icons load up
then you got it but you have to go in to the menu and wipe it off or erease the email account
it worked for me after few tries it shoulg work for you too
Click to expand...
Click to collapse
i think its safe to say that responding to 6+ month old threads is at best pointless..at worst stupid
nitsuj17 said:
i think its safe to say that responding to 6+ month old threads is at best pointless..at worst stupid
Click to expand...
Click to collapse
Respectfully I have to disagree. Sharing a new solution to an old problem cannot be a bad thing. maybe 6+ months from now it will save someones bacon without having to start a new thread for it
Hi,
when I reset my Optimus One with VolDown, Power + Home something got messed up and I received a phone where the desktop is not starting any longer.
After the above reset the setup screen appears where I can choose my language etc, but at the last step I get a force close message for the Setup Wizard every single time. When I then force close, the screen goes dark except for the status bar on the top.
After a while the phone autolocks and I can see the lock screen with moving grass and time etc. When I unlock, again the black screen with only the status bar on top.
The phone receives SMS messages and calls and shows the appropriate screen, just no desktop to choose any apps to start. I can even long press home and then get the recent apps screen with no apps to start.
Can someone help me to get my phone functional again?
Thanks.
Binser
seems like problem with your launcher app. use adb push command to push new launcher in your phone.
no debug
fundoozzz said:
seems like problem with your launcher app. use adb push command to push new launcher in your phone.
Click to expand...
Click to collapse
Yes that would be a good idea if I could enable USB debug. But I cannot get to the settings where I could enable USB debug, therefore ADB push is not a possible option for me.
u can log into your google account on desktop and install any launcher app from playstore , it will automatically get installed on your cell if your data is on.
fundoozzz said:
u can log into your google account on desktop and install any launcher app from playstore , it will automatically get installed on your cell if your data is on.
Click to expand...
Click to collapse
Thanks again for ur input: But the VolDown Menu Power thing did a complete reset and therefore the phone is completely virgin, i.e. no google account is set-up.
While during initial boot the setup wizard comes up, I get the error message:
"The application Setup Wizard (process.com.android.setupwizard) has stopped unexpectedly. Please try again."
So I cannot setup a google account for this phone.
u may be able to go to contacts screen while on call. there u will have an option to add google account. try this n if this doesn't work try resetting your phone again.
Thank you! That did it! I called myself with another phone and during the call via the menu button I was able to go into the account section and add an account. Then the play store updated (some time is needed for registration to take hold on the play store web site) and then I installed the Go launcher via web install.
After I got access to the launcher, I immediately activated USB debugging in Settings > Application Settings > Development and also install from unknnown sources in Application Settings.
I wrote these details so that people with the same problem of corrupted launcher or setup wizard know what to do.
BTW before I tried numerous phone resets but none solved the problem.
Now I still have the following problem: To root a reset is suggested to have a clean file system. A reset however again gives me the above problem. How can I break that vicious cycle?
Again, thanks a million for your help.
Regards,
Binser
binser said:
Thank you! That did it! I called myself with another phone and during the call via the menu button I was able to go into the account section and add an account. Then the play store updated (some time is needed for registration to take hold on the play store web site) and then I installed the Go launcher via web install.
After I got access to the launcher, I immediately activated USB debugging in Settings > Application Settings > Development and also install from unknnown sources in Application Settings.
I wrote these details so that people with the same problem of corrupted launcher or setup wizard know what to do.
BTW before I tried numerous phone resets but none solved the problem.
Now I still have the following problem: To root a reset is suggested to have a clean file system. A reset however again gives me the above problem. How can I break that vicious cycle?
Again, thanks a million for your help.
Regards,
Binser
Click to expand...
Click to collapse
No need of reset or so, just root and install clockworkmod recovery via ROM manager app, choose optimus 1 old baseband even if u r on new coz the recovery for old baseband is much more stable.
NOTE:-
do not choose to boot into recovery from ROM manager,u might end up at emergency mode. instead use the key combo to enter into recovery.
don't choose to factory reset from phone menu once u have installed custom recovery, instead do that from recovery.
Thanks, hephappy's ICS CM9 is running well now.
There is only one problem, possibly because I did not get your advice about old baseband in time: Cannot make or receive calls/texts, but I am being asked for SIM PIN and the phone shows the carrier ID in notifications.
My phone has the 20d baseband - is that the problem? Do I need to upgrade to 20g or would that not matter?
Regards,
Binser
OK, I flashed the 20G baseband and the problems are now history. I can make an receive calls.
There was a problem when flashing: The phone did not reboot into recovery mode. I had to do that manually and disable the LG modem. Then when the process was done I the phone showed 20G baseband, but no IMEI and network. I solved that by using the saved NV2 file in a subdirectory of the LGMDP.exe and the NV Restore button on the program icon bar.
Now everything is fine.
Again, thank you for your help.
Ciao,
Binser
To get rid of Popup dialogs try pressing search button, it works for me
Sent from my sending thing.
I have been using epinter's CM10.1 for Atrix 4g and following the Atrix 4g CM10.1 developer discussions. I am trying to get the camera flash to work. krystianp posted that one should extract from CM9, the files tcmd and tcmdhelp and put in /system/bin. But I cannot find a CM9 for the Atrix 4g (olympus) that has these files. Does anyone know where to find them? (Would have posted to the CM10.1 thread but don't have permission to do so.)
Search fo his cm9. It should have the libs you are looking for. Also, z's one shot cm10.1 might have them as well
Hit the damn thanks button instead!
Enviado desde mi MB860
Thanks
andresrivas said:
Search fo his cm9. It should have the libs you are looking for. Also, z's one shot cm10.1 might have them as well
Hit the damn thanks button instead!
Enviado desde mi MB860
Click to expand...
Click to collapse
Thanks... Downloading a CM9 from krystianp now. I was thinking of trying to get from z's one shot if that didn't work. (And yes I did hit the thanks button ). Now on to see if putting these files in /system/bin will actually get the flash to work. The only post I could find from someone who tried it suggests "no".
The problem I've been having is the flash not flashing at all when the "shutter" button is pressed. Instead the phone light comes on when I press the "focus" button and goes off when released (unless I've selected "no flash"). Seems like for other people the flash works but timing is off.
rhcohen said:
Thanks... Downloading a CM9 from krystianp now. I was thinking of trying to get from z's one shot if that didn't work. (And yes I did hit the thanks button ). Now on to see if putting these files in /system/bin will actually get the flash to work. The only post I could find from someone who tried it suggests "no".
The problem I've been having is the flash not flashing at all when the "shutter" button is pressed. Instead the phone light comes on when I press the "focus" button and goes off when released (unless I've selected "no flash"). Seems like for other people the flash works but timing is off.
Click to expand...
Click to collapse
I placed those files but flash is still not working, maybe you have better luck :fingers-crossed:
reply
Feche said:
I placed those files but flash is still not working, maybe you have better luck :fingers-crossed:
Click to expand...
Click to collapse
No, no better luck here. Copied files to /system/bin, changed permissions to 755, verified owned by root like other files in the directory, rebooted. Same behavior as before.
Did you try Krystianp's 12/31 kernel, which apparently has flash working for some? I downloaded it but haven't flashed it yet out of concern for the bad battery drain noted by someone.
rhcohen said:
No, no better luck here. Copied files to /system/bin, changed permissions to 755, verified owned by root like other files in the directory, rebooted. Same behavior as before.
Did you try Krystianp's 12/31 kernel, which apparently has flash working for some? I downloaded it but haven't flashed it yet out of concern for the bad battery drain noted by someone.
Click to expand...
Click to collapse
I currently have it installed, the flash with stock camera app doesn't work, but with CameraMX flash works fine. :good:
reply
Feche said:
I currently have it installed, the flash with stock camera app doesn't work, but with CameraMX flash works fine. :good:
Click to expand...
Click to collapse
For what it is worth, I just installed the 12/31 kernel and the flash with stock camera app now DOES work for me*, and the timing even seems to be OK. So someone ought to be interested in understanding the difference between your configuration and mine. (If anyone is actually following this, my sequence, executed over the past week or so, was a wipe/clean install of epinter's 12/11 CM10.1 rom, followed by his latest gapps, followed by a second flash of the 12/11 rom. Then this morning putting the tcmd and tcmdhelp files in /system/bin, with appropriate permisssions; and then finally flashing krystianp's 12/31 kernel.) Too soon to comment on battery life.
I think this kernel is supposed to be logging network disconnects (which I also seem to experience, about one a day, requires reboot to reconnect). Do you know where we find the resultant logs, and how (lacking permissions to post at the developers' site) we are supposed to deliver them to krystianp? I notice that, in response to a submitted log file, krystianp made a post about restarting the radio from a terminal, which didn't actually achieve a re-connection for the one person who tried it.
* small update: the flash works with stock app, but only if I do a spot ("touch") focus first. Small price to pay!
Great to know its working! As fir that "thanks" thing, it's my signature from tapatalk, nothing personal
As for the logs, on either cm9 or cm10 forum krystianp gave instructions on how to get those logs. One is dmesg and the other logcat, but can't remember exact commands
Hit the damn thanks button instead!
Enviado desde mi MB860
reply
andresrivas said:
Great to know its working! As fir that "thanks" thing, it's my signature from tapatalk, nothing personal
As for the logs, on either cm9 or cm10 forum krystianp gave instructions on how to get those logs. One is dmesg and the other logcat, but can't remember exact commands
Hit the damn thanks button instead!
Enviado desde mi MB860
Click to expand...
Click to collapse
Thanks --- so I found the relevant krystianp post on the logs:
http://forum.xda-developers.com/showthread.php?p=48954198&highlight=dmesg#post48954198
Specifically,
"To get kernel log just do (as root):
dmesg>/sdcard/kernel.log
And for radio log do:
logcat -b radio >/sdcard/radio.log
(Logcat works continuously so you might have to use ctrl+c to cancel it) "
Question is, what do I do with these logs? I could attach them to a reply at the developer forum if I had permission to reply....
Presumably I don't want to keep running this kernel with debugging turned on forever.
You can attach they here and nention krystianp so he get notified
Hit the damn thanks button instead!
Enviado desde mi MB860
reply
andresrivas said:
You can attach they here and nention krystianp so he get notified
Hit the damn thanks button instead!
Enviado desde mi MB860
Click to expand...
Click to collapse
Thanks, I will wait a couple of days so there is some accumulated info in the logs and do that. So far, no drops and one spontaneous reboot.
reply, to forward to krystianp
andresrivas said:
You can attach they here and nention krystianp so he get notified
Hit the damn thanks button instead!
Enviado desde mi MB860
Click to expand...
Click to collapse
OK, attached are kernel.log and radio.log (combined into the file atrixlogs.tar). Hopefully someone notifies krystianp.
Here is what they represent: I installed krystianp's kernel two days ago. Since then I have had two spontaneous reboots, and two more reboots that I initiated because in the first case the radio died; in the second case the radio didn't die (still had bars) but there was no data connection. In both cases rebooting restored full functionality.
Note in the case where the radio died, I went to no bars and stayed there; then when I tried turning airplane mode on and off, the network status symbol in the status bar disappeared (no triangle at all, rather than having an empty triangle).
Krystianp had suggested trying to stop/restart the radio from a terminal when the network drops; I did not try this as I was away from my computer and so did not have access to the instructions for the terminal command.
I hope these logs are of help.
rhcohen said:
OK, attached are kernel.log and radio.log (combined into the file atrixlogs.tar). Hopefully someone notifies krystianp.
Here is what they represent: I installed krystianp's kernel two days ago. Since then I have had two spontaneous reboots, and two more reboots that I initiated because in the first case the radio died; in the second case the radio didn't die (still had bars) but there was no data connection. In both cases rebooting restored full functionality.
Note in the case where the radio died, I went to no bars and stayed there; then when I tried turning airplane mode on and off, the network status symbol in the status bar disappeared (no triangle at all, rather than having an empty triangle).
Krystianp had suggested trying to stop/restart the radio from a terminal when the network drops; I did not try this as I was away from my computer and so did not have access to the instructions for the terminal command.
I hope these logs are of help.
Click to expand...
Click to collapse
have you tried turning radio on and off from testing tab from dialer *#*#4636#*#* then select phone info scroll down and there is a tab to turn radio off and on. saves time from a reboot.
You should have mention him by @krystianp . Not sure it will work from the phone
Hit the damn thanks button instead!
Enviado desde mi MB860
RE turning radio off and on
overboard1978 said:
have you tried turning radio on and off from testing tab from dialer *#*#4636#*#* then select phone info scroll down and there is a tab to turn radio off and on. saves time from a reboot.
Click to expand...
Click to collapse
No I haven't tried this. Does this do something different from krystianp's suggestion from Jan 2 at the 10.1 developer thread :
echo "shutdown" > /sys/class/radio/mdm6600/command
echo "powerup" > /sys/class/radio/mdm6600/command
which, per reply post from Feche (also Jan 2), succeeds in starting up the radio but not making a connection?
further update
rhcohen said:
No I haven't tried this. Does this do something different from krystianp's suggestion from Jan 2 at the 10.1 developer thread :
echo "shutdown" > /sys/class/radio/mdm6600/command
echo "powerup" > /sys/class/radio/mdm6600/command
which, per reply post from Feche (also Jan 2), succeeds in starting up the radio but not making a connection?
Click to expand...
Click to collapse
----------
OK I have a further update. Using the testing tab from the dialer gives me the option of turning the radio off; when I click it nothing changes -- in particular no option to turn the radio on.
When I try krystianp's echo "shutdown" and echo "powerup" commands, I get a system prompt back but no indication that anything has changed with the radio (though maybe it would be reflected in the radio logs). In any event, certainly no connection to the network.
With regard to including @krystianp in the mssage -- where am I supposed to include this (to get the log files to him)?
rhcohen said:
----------
With regard to including @krystianp in the mssage -- where am I supposed to include this (to get the log files to him)?
Click to expand...
Click to collapse
Doesn' t it appear as a link to his user profile? go there and select
Code:
send message -> send a private message to krystianp
.
I don't see a place to attach a file to the message, but you can link to this thread.
reply; and what is "uv"?
PolesApart said:
Doesn' t it appear as a link to his user profile? go there and select
Code:
send message -> send a private message to krystianp
.
I don't see a place to attach a file to the message, but you can link to this thread.
Click to expand...
Click to collapse
-------------
Thanks. Sending the logs may no longer be relevant; @krystianp posted a new kernel a day and a half ago. I flashed it yesterday, and so far, no radio drops. If I get any I will post another message with logs and also send a message to krystianp.
I notice in describing the new kernel he says he made changes to radio and UV. Can someone tell me what is UV? I tried a search in the 10.1 developer forum and a more general google search but find nothing useful (I suspect this use of "UV" does not mean "ultra-violet".)
As of today, he said the last kernel just adds more debug information. for me it didn't work for much time, with random reboots, probably caused by UV changes. UV is shorthand for "undervolting", an attempt to lower voltage to cpu (and perhaps some other devices) in order to preserve battery and generate less heat.
reply
PolesApart said:
As of today, he said the last kernel just adds more debug information. for me it didn't work for much time, with random reboots, probably caused by UV changes. UV is shorthand for "undervolting", an attempt to lower voltage to cpu (and perhaps some other devices) in order to preserve battery and generate less heat.
Click to expand...
Click to collapse
I saw today's post but didn't interpret it the same way. He had already said that this kernel, along with the one from 12/31, were for people with the disconnect errors (which I was getting), but when he posted the Jan 5 kernel he indicated there were changes to radio and UV; I thought today's notice was just reaffirming the purpose of both the 12/31 and 1/5 kernels.
The 12/31 kernel clearly did more than just turn on logging however, as it seems to have fixed the camera flash for many (including me).
And the 1/5 kernel seems to be working more stably for me -- 1 1/2 days now without a radio drop. Maybe just luck.
For quite some time I have been using Tasker to do an automatic reboot at 4 am every day. Since upgrading to the new firmware, it no longer seems to work. I check the Superuser log, and it shows that access was granted at the time it was supposed to run, but nothing happened. When go in to try and manually test the reboot command in Tasker, nothing happens there, either. Can anyone else confirm whether this is a problem on their updated phone?
Thanks.
ElMadre said:
For quite some time I have been using Tasker to do an automatic reboot at 4 am every day. Since upgrading to the new firmware, it no longer seems to work. I check the Superuser log, and it shows that access was granted at the time it was supposed to run, but nothing happened. When go in to try and manually test the reboot command in Tasker, nothing happens there, either. Can anyone else confirm whether this is a problem on their updated phone?
Thanks.
Click to expand...
Click to collapse
I am running sense 5.5 v4 and just tried and tasker reboot isn't working for me either, you can probably use a shell script as root to reboot if you can find the command
Hi, My Mi A3 keeps restarting. If i stay a while without using the phone it simply restarts and expects sim code to start again. The result is that ithou knowing i'm contantly with the phone shut down. Anyone can help? Thanks
You need to provide a bit more information than that.
Have you flashed anything at all to the device (magisk, twrp, ROM, any kind of mod)
Is it completely stock?
If so it sounds like a software issue and reflashing the stock rom with mi flash tools may help
garylawwd said:
You need to provide a bit more information than that.
Have you flashed anything at all to the device (magisk, twrp, ROM, any kind of mod)
Is it completely stock?
If so it sounds like a software issue and reflashing the stock rom with mi flash tools may help
Click to expand...
Click to collapse
Hi, thanks for the prompt reply. Yes, is just stock ROM. Android 9 plus november security patch. Already did a factory reset and the problem remains. The only uncommon thig i've noticed was an android.process.acore error which i today tried to solve by seaching solutions online. Thanks
jcoelho111 said:
Hi, thanks for the prompt reply. Yes, is just stock ROM. Android 9 plus november security patch. Already did a factory reset and the problem remains. The only uncommon thig i've noticed was an android.process.acore error which i today tried to solve by seaching solutions online. Thanks
Click to expand...
Click to collapse
That's an issue with your contacts and nothing to do with random reboots which may indicate that the update to November sec patch might have caused this issue. Something may have happened when you updated and caused some files to get messed up somehow which is why a factory reset won't work.
That's why it still hasn't fixed the android.process.acore error or the random reboots
As I said in my previous post, reflash the latest rom with mi flash tools and that issue may very well get fixed.
garylawwd said:
That's an issue with your contacts and nothing to do with random reboots which may indicate that the update to November sec patch might have caused this issue. Something may have happened when you updated and caused some files to get messed up somehow which is why a factory reset won't work.
That's why it still hasn't fixed the android.process.acore error or the random reboots
As I said in my previous post, reflash the latest rom with mi flash tools and that issue may very well get fixed.
Click to expand...
Click to collapse
ok. thanks once again
wipe format cache data everything internal storage too( it will delete ALL ypur photos,videos etc.) flash stock rom or any custom rom . i hope it will be solved
jcoelho111 said:
Hi, My Mi A3 keeps restarting. If i stay a while without using the phone it simply restarts and expects sim code to start again. The result is that ithou knowing i'm contantly with the phone shut down. Anyone can help? Thanks
Click to expand...
Click to collapse
How often does it happen? You could try connecting your phone to a PC and keep running "adb logcat" to catch the crash. Also try capturing logcat right after a reboot, it might contain some useful info about the crash.
With root you could get additional info:
Kernel Log:
adb shell su -c dmesg > dmesg.log
Last_kmsg:
adb shell su -c "cat /proc/last_kmsg" > last_kmsg.log
sasukeob said:
wipe format cache data everything internal storage too( it will delete ALL ypur photos,videos etc.) flash stock rom or any custom rom . i hope it will be solved
Click to expand...
Click to collapse
thanks
_mysiak_ said:
How often does it happen? You could try connecting your phone to a PC and keep running "adb logcat" to catch the crash. Also try capturing logcat right after a reboot, it might contain some useful info about the crash.
With root you could get additional info:
Kernel Log:
adb shell su -c dmesg > dmesg.log
Last_kmsg:
adb shell su -c "cat /proc/last_kmsg" > last_kmsg.log
Click to expand...
Click to collapse
thanks
I got the same problem...How do I reflash the latest rom with mi flash tools?
any one tried with Miflash till now? please update your feed back here
---------- Post added at 12:45 PM ---------- Previous post was at 12:28 PM ----------
@garylawwd
A3 have ufs memory and all ufs have different configuration than emmc partitions need to set active partition if you will not set active partition the phone will boot looping or hang on logo and make restarts
Click to expand...
Click to collapse
do you think any problem with this file system (Mi update team is not that dumb) but simply asking
in my case it restarts with boot loops , auto formates it self if you connect charging wire (with erasing mentioned for 15seconds) and fails to restar for 3 time and bootups with welcome language selection screen!
Ended up here because my Mi A3 is becoming increasingly unstable. It rebooted three times around lunch time. I've just installed the May 2020 update and it's already restarted once already
I'm going to have to consider returning it - my mobile is my main business phone too so can't have this level of instability and hassle Sadly a very black mark against Xiaomi. I've recommended their phones to several friends and clients because they were great phones.
Hmm... whilst typing this message it's just restarted again...