Related
The following is a common problem with the Atrix, so it seems:
http://forum.xda-developers.com/showthread.php?p=26120173#post26120173
Symptoms:
Try to enable the WiFi or Bluetooth : Doesn't enable BT or WiFi, sometimes will reboot phone.
Or it will constantly reboot phone, depending if you can get to the Airplane mode switch quick enough.
Sometimes in middle of calls it will reboot.
Suggested remedies
1) Format cache
2) Fix permissions
3) Replace firmware libs on /system/etc/modules/wifi
4) Detach + reattach battery clock on CPU/Accelerometer/WiFi/BT motherboard
5) Run stock ROM
6) Vote for Ron Paul
I've done the following
1 + 2 + 3 + 4 + 5. 6 doesn't seem probable to fix this case.
TWICE I've got the WiFi to work again. After that, reboot hell untill I could disable WiFi / BT.
Disclaimer : the following is a cross post from the previous forum
Kernel dumps
[ 31.028143] sdhci_tegra_wlan_detect Detecting WLAN
[ 31.028164] mot_wifi_set_carddetect: Nobody to notify
[ 31.029391]
[ 31.029395] Dongle Host Driver, version 4.218.248.32
[ 31.029400] Compiled in /tank/jokersax/cm9/kernel/moto/olympus/wifi-module/wlan/osrc/open-src/src/dhd/linux/../.. on May 7 2012 at 11:40:09
[ 31.328158] mmc1: error -110 whilst initialising SDIO card
WARNING: at /tank/jokersax/cm9/kernel/moto/olympus/lib/kobject.c:595 kobject_put+0x50/0x60()
[ 214.627572] kobject: '<NULL>' (0003da74): is not initialized, yet kobject_put() is being called.
[ 214.627581] Modules linked in: dhd(+)
[ 214.627591] Backtrace:
[ 214.627612] [<c0040010>] (dump_backtrace+0x0/0x10c) from [<c05b68c8>] (dump_stack+0x18/0x1c)
[ 214.627622] r7:c031c6c4 r6:c071fb48 r5:00000253 r4:e83a1e98
[ 214.627647] [<c05b68b0>] (dump_stack+0x0/0x1c) from [<c00bc5b8>] (warn_slowpath_common+0x50/0x68)
[ 214.627663] [<c00bc568>] (warn_slowpath_common+0x0/0x68) from [<c00bc61c>] (warn_slowpath_fmt+0x30/0x38)
[ 214.627673] r7:bf081000 r6:00000000 r5:bf076570 r4:0003da74
[ 214.627692] [<c00bc5ec>] (warn_slowpath_fmt+0x0/0x38) from [<c031c6c4>] (kobject_put+0x50/0x60)
[ 214.627701] r3:00000000 r2:c071fb80
[ 214.627720] [<c031c674>] (kobject_put+0x0/0x60) from [<c03787f0>] (put_driver+0x14/0x18)
[ 214.627729] r4:e98390c0
[ 214.627742] [<c03787dc>] (put_driver+0x0/0x18) from [<c0378938>] (driver_register+0x144/0x164)
[ 214.627757] [<c03787f4>] (driver_register+0x0/0x164) from [<c037994c>] (platform_driver_register+0x4c/0x60)
[ 214.627767] r9:00000000 r8:00000000 r7:bf081000 r6:00000000 r5:e83a0000
[ 214.627782] r4:bf078890
[ 214.627826] [<c0379900>] (platform_driver_register+0x0/0x60) from [<bf049fa4>] (wifi_add_dev+0x24/0x40 [dhd])
[ 214.627870] [<bf049f80>] (wifi_add_dev+0x0/0x40 [dhd]) from [<bf0810bc>] (init_module+0xbc/0x238 [dhd])
[ 214.627902] [<bf081000>] (init_module+0x0/0x238 [dhd]) from [<c003b5c8>] (do_one_initcall+0x40/0x1bc)
[ 214.627912] r5:e83a0000 r4:c07e0c00
[ 214.627932] [<c003b588>] (do_one_initcall+0x0/0x1bc) from [<c00f3880>] (sys_init_module+0xcc/0x200)
[ 214.627941] r9:e83a0000 r8:c003c364 r7:00046bd8 r6:00000000 r5:bf076748
[ 214.627957] r4:5c126008
[ 214.627970] [<c00f37b4>] (sys_init_module+0x0/0x200) from <c003c1e0>] (ret_fast_syscall+0x0/0x2c)
[ 214.627979] r7:00000080 r6:5e0fdb34 r5:5c126008 r4:405ad0f0
[ 214.627995] ---[ end trace 2416c978061dd5a5 ]---
[ 214.628002] Error: Driver 'bcm4329_wlan' is already registered, aborting...
Now I had some experience with WiFi kernel driver development (iMx51 + CSR based WiFi/BT combo chip).
The startup sequence on kernel level will probably go like this:
1) Kernel startup
2) ARM CPU specifics startup
3) Platform specific device setup (setup clocks)
3) Platform driver dependency registration (like, on SDIO 1 there is a WiFI chip that needs driver X to work)
4) Sub-platform driver startup (SPI, SDIO, UART, I2C)
I think this is where we fail first - Error -110 means timeout. Each MMC / SDIO chip has a MMC specific startup sequence, then depending what was given on number 3, it jumps over to SDIO (SDIO is a superset of MMC).
When our BT/WiFi chip is put into SDIO mode, the SDIO commands fail with a time out.
Possible reasons for it failing:
1) Incorrect voltages
2) Skewed clock
3) Busted chip.
4) We talk to it too fast
5) Kernel is messed up
Now, seeing that (through weird loops, check my previous post) I could get the unit running two more times, I do not think it is 3.
Why it could be 1:
Voltage rails needs to start up at the correct sequence for some chips. Like some chips will specify an operating range of between 1.8V and 3.3V. That means if it finds 5V on it, it will shut itself off. Sometimes some chips needs an initial 3V, then after 10 seconds it can be put into 1.8V (in-chip startup). Sometimes, it needs 10seconds to stabilize before you can talk to it (in our case via SDIO).
Why it isn't 1:
I've tried a lot of other kernels. It is all based off the ATT code, and they do the voltage rail setup correctly. I've even reverted back to stock code - no dice.
Why it could be 2
By removing the small cell battery, the drain on the battery was lifted. It could then store up enough current to put itself into the correct clock rate when it was put back.
Why it isn't 2
? Don't know. More needs to be known of the function of this battery. Obviously it is driving some RTC (real time clock). RTC's normally work at 32MHz, (32768, easilly divideable by 2, 4, 8 etc).
Does the Broadcom chip need this RTC? Isn't its clock lines driven by the Tegra2?
Why it could be 4
If the RTC is compromised (number 2) then init will suffer. If the Tegra's clock is not derived from the battery and the Broadcom's is, then there will be a disparity between the 2 units chatting together, as SDIO communication is clock based and not latch based (like SPI). If I'm chatting to you at 32MHz and you are 5% off, then we will not be communicating (if you are an SDIO master and I'm an SDIO slave).
Why it isn't
No idea.
Why it could be 5
Bunch of kernel errors stating un-inited modules pointing to null.
Why it isn't 5
Stock kernels also have the same problem
So, sorry folks, this issue points to a hardware problem.
Our biggest answer will be at the following:
1) What does that battery do?
2) Why is the SDIO subsystem having timeouts?
That's all for now.
Dude, I have this SAME EXACT problem. Full wiping helped temporarily, and sometimes not at all. Flashing back to stock doesn't even help. My next move is to buy a new battery.
And I was already planning on voting for Ron Paul.
I got so tired of my Atrix rebooting and the WiFi not working that I ended up downgrading back to my Captivate. :/
that does seem to me like a Hardware failure on the broadcomm bt/wifi chip =/ there seems to be a sdio/mmc1 error in your first dump, did you try removing the external sdcard ?
on the other hand, did you try to rsd flash a stock rom (not just flash it form recovery but with rsd)?
I had this issue and struggled with it for over a month. Finally, I ended up sending it back to Motorola for warranty.
It's unlocked and I didn't try to obscure that - it seemed dishonest, and this issue isn't caused by my actions as far as I can tell. I've seen lots of people online with stock handsets with the same issue.
They received it yesterday, so we'll see if they fix it. If not, I'll be happy if they let me pay to have it repaired out of warranty. Their site says out-of-warranty repairs are $110, flat, so that's not too bad. If they refuse to service it, I'll probably never buy a Motorola product again...
I did everything I could think of to try and make it work, and it got progressively worse and finally stopped working at all. The only ROMs I had used when mine died were stock, CM7 BA2TF, and the two CM9 KANGs floating around. I was using turl's v9 when it started giving me the error.
mine started doing that when i went from nottach's the darkside prefinal to turls v8 then to nottachtrix4g 1.0
I Haven't got this problems.
I've got random reboots for no reason (4-5 at day) and when trying to switch from offline mode to online always caused reboots (but after a long idle in offline)
Send it on warranty, and they replaced the MoBo (I think, they call it " Electronical Board") so I've got a new IMIEI too.
10 hours and not one single reboot. Tonight i'll try to put in offline .
Tomorrow I'll post :v
crnkoj said:
that does seem to me like a Hardware failure on the broadcomm bt/wifi chip =/ there seems to be a sdio/mmc1 error in your first dump, did you try removing the external sdcard ?
on the other hand, did you try to rsd flash a stock rom (not just flash it form recovery but with rsd)?
Click to expand...
Click to collapse
Yea, I've tried removing my sd card even while flashing back to stock using RSD.
I have the same exact problem. I found another thread referencing to it and an interesting YouTube video too. Ill post soon
Sent from my MB860 using XDA
Ok so, after the replace of the MoBo, no reboots, and this morning (after kept the phone in airplane mode in the night ,8 hours) switching to online, no reboot.
Anyway I will keep u informed if it comes back or w/e
same problem
I have also Atrix 4G (ATT) witch same problem "WiFi error"
What i ready do and check:
- reflash latest radio = NOT HELP
- flash many ROMs = NOT HELP
- wipe all = NOT HELP
- disconnect and connect internal battery = NOT HELP
- after disconnect and connect internal battery - reboot stop... and start after i try setup BT or WiFi
Also what i finde intrest:
- internal battery have 2.4 V (not 3V, but i dont know correct value)
- i cant make backup from CWM may PDS
What i plane to do:
- replace internal battery to new one
- try to make PDS repair (i finde on forum PDS repair file)
- rehot phone PCB (i have infrared soldering station)
What i serch for help
- Atrix scheme and service manual
- information about phones factory repaired witch this problem (IMEI same or changed ?)
- some one try repair own PDS for fix this problem ?
THX for any information, if i finde way - post here
ready check soft brick
I make softbrick for may Atrix - all manual erased and then install clear radio and rom = NOT HELP
I sent my root & unlocked Atrix to Motorola - they sent me a new one under warranty. I restored the factory ROM, but did not try to hide the fact that it was unlocked.
Sent from my Samsung Galaxy Tab 2.
TheTinkerer said:
... If they refuse to service it, I'll probably never buy a Motorola product again...
Click to expand...
Click to collapse
May be they read the forum too and trying to keep you as a customer
I have the same issues.... This happened to me after flashing Neutrino's CM7 ROM so I'm still thinking this is a fixable issue... I hope!
But so far no luck. Yesterday I even reset everything using the Motorola update software on my laptop. It re-locked my phone, put on the default Android recovery, and reset the ROM to un-rooted and stock. The boot screen was AT&T's logo and everything I'd expect from a fresh phone from the store. But still the WiFi settings showed an "Error" as it's status and if I click it on a few times the phone reboots just like before.
So I performed the unlock and loaded the CM Recovery and now I'm back to the ICS ROM which is awesome except I have no WiFi or Bluetooth. Data usage is adding up on my AT&T account...
Any fresh ideas are gladly welcomed.
I've never had any random wifi reboots until I installed 2.3.5 or 2.3.6 stock and custom roms. When I installed anyone's version of the two rom, my wifi signal would drop every 3 mins like clock work. I have a Beklin wireless N router at home. This only happened to me when I was using that router. All other makes worked fine (netgear, linksys, wifi hotspot, etc). I can't figure out what setting is causing this, any ideas?
Sent from my MB860 using xda premium
bigron77 said:
I've never had any random wifi reboots until I installed 2.3.5 or 2.3.6 stock and custom roms. When I installed anyone's version of the two rom, my wifi signal would drop every 3 mins like clock work. I have a Beklin wireless N router at home. This only happened to me when I was using that router. All other makes worked fine (netgear, linksys, wifi hotspot, etc). I can't figure out what setting is causing this, any ideas?
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Sounds like you have a router issue and a quick place to start is do a physical reset of the router so it goes back to stock settings. Then configure it one thing at a time until the comes up again.
The issue posted here is different. We're having the wifi and bluetooth hardware malfunctioning. It's not that we have issues holding a connection to a certain router, it is that wifi on the phone won't turn on at all. Maybe there's a distant relation to the issues, but I'm thinking their unrelated.
---------- Post added at 10:43 PM ---------- Previous post was at 10:42 PM ----------
robeknight said:
I have the same issues.... This happened to me after flashing Neutrino's CM7 ROM so I'm still thinking this is a fixable issue... I hope!
But so far no luck. Yesterday I even reset everything using the Motorola update software on my laptop. It re-locked my phone, put on the default Android recovery, and reset the ROM to un-rooted and stock. The boot screen was AT&T's logo and everything I'd expect from a fresh phone from the store. But still the WiFi settings showed an "Error" as it's status and if I click it on a few times the phone reboots just like before.
So I performed the unlock and loaded the CM Recovery and now I'm back to the ICS ROM which is awesome except I have no WiFi or Bluetooth. Data usage is adding up on my AT&T account...
Any fresh ideas are gladly welcomed.
Click to expand...
Click to collapse
Btw, I've had my Atrix for about 14 months now so I can't get it replaced by warranty. I've already tried that :-(
Have you tried fastboot erase boot? Then reflash your rom
Sent from my MB860 using XDA
aaron.a said:
Have you tried fastboot erase boot? Then reflash your rom
Sent from my MB860 using XDA
Click to expand...
Click to collapse
it doesn't matter, it's a hardware issue.
I rehot BROADCOM ic - WiFi = NOT WORK
I have exactly the same problem. Wifi started to error here and there last September. Then started to get progressively worse in the winter. Then it finally crapped out in February. Just have to keep an eye on my data plan till I can get it fixed. If it is a hardware problem, would it still matter if I am unlocked?
Let me first explain what I did.
1. From stock rom, after doing the root (TWRP recovery), i flashed JellyDaemon v 2.0 listed here http://forum.xda-developers.com/showthread.php?t=2307247 . Used CPU control inbuilt in app to set CPU governer to OnDemand
Fantastic ROM with no problems.
2. After the news of 4.2.1 release came, I started looking for 4.2.1 based roms. I went with StarkHD listed here http://forum.xda-developers.com/showthread.php?t=2212028 . I think my download went wrong and file wasn't downloaded cleanly. I flashed with it. Flash went on successful. Phone got hung at the boot animation. Tried multiple methods to start the ROM. No success. Phone not booting into any ROM.
3. I had stock rom v 0.16 available with so flashed it with SP flash tools. Flash was successful.
4. Downloaded Naturewiz HD listed here http://forum.xda-developers.com/showthread.php?t=2319288 . ROM flashed and phone booted. Restored the apps. Used battery calibration app to calibrate the battery. After this, noticed that every time phone went into standby, it won't wake after that and needed reboot. I thought it to be bug in the rom.
5. Downloaded 4.2.1 based rom listed here http://forum.xda-developers.com/showthread.php?t=2306461 and flashed it. Flash was successful followed by successful TP upgrade. Installed everything. Same problem noticed. Phone won't wake from standby. Needed to be rebooted.
6. I figured it to be a CPU governer problem left over from JellyDaemon v. 2.0. So installed juice defender and set the CPU governer to OnDemand. Frequency of reboots has reduced but the problem still persists.
Problem: The phone does not wake up when put to standby for a duration of 2-3 hours.
Any solutions to this? There are no other problems I am facing.
"I figured it to be a CPU governer problem left over from JellyDaemon v. 2.0. So installed juice defender and set the CPU governer to OnDemand. Frequency of reboots has reduced but the problem still persists.
Problem: The phone does not wake up when put to standby for a duration of 2-3 hours.
Click to expand...
Click to collapse
Looks like you yourself gave an answer to your problem. Don't enable Ondemand. if you still getting the problem. take a video of your problem and try posting along with a link to the video (I am not sure whether it is allowed). this way it will be easy to know what the problem is... hope i helped..
Sent from my CaNvAs HD using xda-developer app.
adizrox said:
Looks like you yourself gave an answer to your problem. Don't enable Ondemand. if you still getting the problem. take a video of your problem and try posting along with a link to the video (I am not sure whether it is allowed). this way it will be easy to know what the problem is... hope i helped..
Click to expand...
Click to collapse
Thanks for your reply. I will try your suggestion and see. In the meanwhile, I removed TWRP and flashed CWM 6.0.3.0 and fixed permissions with that. The phone did not reboot on its own for close to eight hours (which it was doing earlier at random). I thought problem was solved. But trying to go through contacts list (DW Contacts), phone rebooted on its own.
Can anyone tell me a method where you do a clean install and bring the phone to a factory fresh state. Something similar to tutorial by team overcome for galaxy tab. Frankly, that seems to be the only possible solution: Get the phone in a completely formatted factory fresh state and then install any other ROM.
SP flash tools
To get your phone to a default factory status. you have to flash the original rom using SP tools. Links to both can be found in the forum.
Finally, tired after numerous attempts, decided to take it to the service center. Asked them to update to 4.2.1. They had the same problem. After flashing, the phone just wouldn't boot past the boot animation.
They kept trying. After two hours, they gave it back to me saying there is a hardware problem which requires a main board change.
I had suspected all along and now I know I was right. I asked them about the time line. The answer I got was even more shocking. Minimum two weeks, but there are lots of hand sets awaiting main board since more than a month
I guess I am better off with current status (Ver .20 installed and rooted).
Seriously, this episode has seriously dented my faith in micromax as a brand. One can buy there phones and be happy with whatever has been packaged. Trying anything new can be dangerous.
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.
Hope you can help me - I am desperate to halt the OTA update for my galaxy s4 -
based on everything I’ve read, Samsung did a really bad job on this update, 4.4.2, and they are currently rolling out 4.4.3 and 4.4.4, but of course, the s5 is getting it well before we are.
anyway,
I have been “happily” running 4.3 and just dealing with the bluetooth issues, found enough hacks/fixes for the wifi issue that i have been ok with it since getting 4.3 in November.
There are just too many unworkable issues of battery drain, overheating, losing apps, pics, etc etc etc for me to risk the update to 4.4.2.
HERE’S MY PROBLEM - Somehow, altho i'm fairly technical, the update finally got on my phone (after having kept it off for months) and for the past month or more, I've just been
dealing with the notification, putting it off for 24 hrs at a time.
I guess it finally decided not to allow me to do that any longer, and started the installation without permission. i stopped it by pulling the battery, but when i try to start in recovery mode just so i can clear cache and hopefully reboot without actually installing the new os, I cannot - it goes through (some of) the motions but when i let go of the power button as i should when it's running normally, and would get the options of factory reset, clear cache, et al, it just brings up the android bot and shows that it is continuing to install where it left off. I’ve done this numerous times.
Tried different methods of button-holding and other trouble-shooting based on massive searching, but always get the same result. and I can only pull the battery to stop it.
Am I stuck? Do I have to install now at this point?
I do not want to perform factory reset, guess I'd rather install the 4.4.2 s/w. (altho I can't even get to that option at this point)
Sincerely hope someone out there will respond – I've posted to multiple sites, and no one is responding - gonna have to turn my phone back on at some point soon...
Thanks in advance!!
Roxanne
rkohlin said:
Hope you can help me - I am desperate to halt the OTA update for my galaxy s4 -
based on everything I’ve read, Samsung did a really bad job on this update, 4.4.2, and they are currently rolling out 4.4.3 and 4.4.4, but of course, the s5 is getting it well before we are.
anyway,
I have been “happily” running 4.3 and just dealing with the bluetooth issues, found enough hacks/fixes for the wifi issue that i have been ok with it since getting 4.3 in November.
There are just too many unworkable issues of battery drain, overheating, losing apps, pics, etc etc etc for me to risk the update to 4.4.2.
HERE’S MY PROBLEM - Somehow, altho i'm fairly technical, the update finally got on my phone (after having kept it off for months) and for the past month or more, I've just been
dealing with the notification, putting it off for 24 hrs at a time.
I guess it finally decided not to allow me to do that any longer, and started the installation without permission. i stopped it by pulling the battery, but when i try to start in recovery mode just so i can clear cache and hopefully reboot without actually installing the new os, I cannot - it goes through (some of) the motions but when i let go of the power button as i should when it's running normally, and would get the options of factory reset, clear cache, et al, it just brings up the android bot and shows that it is continuing to install where it left off. I’ve done this numerous times.
Tried different methods of button-holding and other trouble-shooting based on massive searching, but always get the same result. and I can only pull the battery to stop it.
Am I stuck? Do I have to install now at this point?
I do not want to perform factory reset, guess I'd rather install the 4.4.2 s/w. (altho I can't even get to that option at this point)
Sincerely hope someone out there will respond – I've posted to multiple sites, and no one is responding - gonna have to turn my phone back on at some point soon...
Thanks in advance!!
Roxanne
Click to expand...
Click to collapse
Are you rooted?
SiVisPacemParaBellum
OderintDumMetuant
stvn2569 said:
Are you rooted?
SiVisPacemParaBellum
OderintDumMetuant
Click to expand...
Click to collapse
Thanks for responding stvn2569!
Nope, not rooted.
But based on all my searching I sure wish I was and likely will the next phone.
Stock Verizon Galaxy s4 - 32gb - model # SCH-I545
(Sorry, should have put this in orig message)
THis summarizes some of the reason I don't want to update the OS - -
ack - can't post links - will have to type it out if you are interested in all the bugs Samsung saddled us with -
(most egregious is the battery drain, but others are quite serious and hard to live with too)
www(dot)androidpit(dot)com(slash)samsung-galaxy-s4-update-to-android-4-4-2-littered-with-bugs
rkohlin said:
Thanks for responding stvn2569!
Nope, not rooted.
But based on all my searching I sure wish I was and likely will the next phone.
Stock Verizon Galaxy s4 - 32gb - model # SCH-I545
(Sorry, should have put this in orig message)
Click to expand...
Click to collapse
You'll need to root the phone to stop the OTA notifications, it's all very easy.
Go to settings > security > allow installations from unknown sources, check the box
Go to www.towelroot.com
Click on the lambda, download and install the towelroot.apk
Click on "make it ra1n", reboot
Download "SuperSU" from the play store
Upon opening the app, it will prompt you to "update binaries". Do this using the "normal" option
Then download "Root Explorer" from the play store
Navigate to the system and system-priv app folders
In one of those folders you'll find "FWupgrade,apk" and "SDM.apk"
Delete those apk's and no more OTA updates:good:
joshm.1219 said:
You'll need to root the phone to stop the OTA notifications, it's all very easy.
.......
:
Click to expand...
Click to collapse
Thanks, Josh, I appreciate your trying to help, but if you read the original post -
I CANNOT TURN ON THE PHONE, hence couldn't get to settings if I wanted to, BUT - -
It is not the notification that is the issue -
the phone has finally downloaded the OTA update and IS INSTALLING IT. (every time I turn it on)
I DO NOT WANT THIS UPDATE INSTALLED. (see prior post for the reason - it's terribly buggy update - worse than what I have)
I have to figure out how to halt it - when I try to start in "recovery mode", it doesn't give me the options
it normally would - I won't start in a normal recovery mode.
It continues the OS update.
I noted all this in the original post - I completely understand how to get rid of the update notifications.
One doesn't even have to root the phone to do this, you can just rename the SDM apk (like add .bak or something)
Do you have ideas how to stop the installation? How I can turn phone on in recovery mode?
(note the steps I've taken to do that are also in the original post)
I know there are many people out there smarter than me about this - hoping you guys can help...,
rkohlin said:
Thanks, Josh, I appreciate your trying to help, but if you read the original post -
I CANNOT TURN ON THE PHONE, hence couldn't get to settings if I wanted to, BUT - -
It is not the notification that is the issue -
the phone has finally downloaded the OTA update and IS INSTALLING IT. (every time I turn it on)
I DO NOT WANT THIS UPDATE INSTALLED. (see prior post for the reason - it's terribly buggy update - worse than what I have)
I have to figure out how to halt it - when I try to start in "recovery mode", it doesn't give me the options
it normally would - I won't start in a normal recovery mode.
It continues the OS update.
I noted all this in the original post - I completely understand how to get rid of the update notifications.
One doesn't even have to root the phone to do this, you can just rename the SDM apk (like add .bak or something)
Do you have ideas how to stop the installation? How I can turn phone on in recovery mode?
(note the steps I've taken to do that are also in the original post)
I know there are many people out there smarter than me about this - hoping you guys can help...,
Click to expand...
Click to collapse
My bad, I would suggest booting into download mode and flashing the mk2 tar file with odin (3.09 recommended).
I didn't suggest renaming the file because it doesn't always work. Told my brother to do that on his Note 3 (no root method at the time) and it start downloading an OTA upon reboot one day.
joshm.1219 said:
My bad, I would suggest booting into download mode and flashing the mk2 tar file with odin (3.09 recommended).
I didn't suggest renaming the file because it doesn't always work. Told my brother to do that on his Note 3 (no root method at the time) and it start downloading an OTA upon reboot one day.
Click to expand...
Click to collapse
Thanks, Josh!
When you say "boot into download mode" - you mean safe/recovery/download mode right?
(like when one holds (for this model) VolumeUpButton+PowerButton right?)
If that's the case, it doesn't allow me to boot that way. When I do that, it just skips right to
"Installing system update" (with the droid bot)
That's my problem.
Cannot access anything (without allowing the install). :crying:
Have also tried VolumeUpButton+PowerButton+HomeButton. Same.
Drat.
Looks like I may have to accept this OS.
Others I know that have deal with terrible battery drain issues (from 10 hrs heavy use on charge down to 2 hrs)
rkohlin said:
Thanks, Josh!
When you say "boot into download mode" - you mean safe/recovery/download mode right?
(like when one holds (for this model) VolumeUpButton+PowerButton right?)
If that's the case, it doesn't allow me to boot that way. When I do that, it just skips right to
"Installing system update" (with the droid bot)
That's my problem.
Cannot access anything (without allowing the install). :crying:
Have also tried VolumeUpButton+PowerButton+HomeButton. Same.
Drat.
Looks like I may have to accept this OS.
Others I know that have deal with terrible battery drain issues (from 10 hrs heavy use on charge down to 2 hrs)
Click to expand...
Click to collapse
It is Power button click and hold volume down....
rkohlin said:
Thanks, Josh!
When you say "boot into download mode" - you mean safe/recovery/download mode right?
(like when one holds (for this model) VolumeUpButton+PowerButton right?)
If that's the case, it doesn't allow me to boot that way. When I do that, it just skips right to
"Installing system update" (with the droid bot)
That's my problem.
Cannot access anything (without allowing the install). :crying:
Have also tried VolumeUpButton+PowerButton+HomeButton. Same.
Drat.
Looks like I may have to accept this OS.
Others I know that have deal with terrible battery drain issues (from 10 hrs heavy use on charge down to 2 hrs)
Click to expand...
Click to collapse
Like he said, download mode is Power+VolumeDown, press and hold.
UPDATE:
Well, never could get into download mode, so had to accept the OS update to KK 4.4.2
Guess I'm one of the lucky ones, (I do have a fairly new model S4) and I didn't lose apps or contacts.
however,
The Battery Life is TERRIBLE after the 4.4.2 update! Some WiFi issues too.
Seem to have fixed WiFi (for now anyway)
Been searching around and recalibrated my battery, am trying a battery life extender app,
turned off a huge bunch of Samsung and Google apps that evid constantly "ping" and use battery.
It's been a little better, but not a lot.
Hope for 4.4.4 to be available soon (heard 4.4.3 is not a good variant either)
Hello,
I am having some battery problem.
I am currently on 10.3.12.0 (EU) build,( before that i was on 10.3.11.0 (EU)) which i flash directly via twrp, because i was not able to get the ota update, it always failed to install. Yes i followed the instructions for ota with magisk.
Since the 10.3.11.0 update, the battery get bad, i was getting around barely 10h sot, now it super bad- can not get even 3h SOT + there is massive heat issue 40° for no reason.
CPU frequencies are not loadable ( since the beginning ) in kernel auditor, gsm battery or any app. (see the screenshots)
It can be only monitored in real time, and it is showing for every scroll spikes to the maximum.
There is battery drain even in Stand by- 5-10 %.
What will you advise me.
Thanks in advance!
Some screenshots.
https://drive.google.com/folderview?id=16uFKuXgd1M5oR3F61j4pwTvsBzpnEUw3
Connect phone to the PC and:
- adb shell
- type in "su", allow root access on the phone
- type in "top"
- make screenshot/copy data, press ctrl+c
- type in "top -s 11"
- make screenshot/copy data, press ctrl+c
- post screenshot/data here
_mysiak_ said:
Connect phone to the PC and:
- adb shell
- type in "su", allow root access on the phone
- type in "top"
- make screenshot/copy data, press ctrl+c
- type in "top -s 11"
- make screenshot/copy data, press ctrl+c
- post screenshot/data here
Click to expand...
Click to collapse
Thank you for the fast answer!
I am using terminal emulator, because i am not able to use PC at the moment.
I will add later the proper data if needed.
Try to uninstall XDA navigation gestures app, reboot phone to reset stats and then check after 1-2 hours again with the same commands if the situation has been improved. Hopefully it's the only app triggering MagiskD (its CPU usage should be practically zero).
_mysiak_ said:
Try to uninstall XDA navigation gestures app, reboot phone to reset stats and then check after 1-2 hours again with the same commands if the situation has been improved. Hopefully it's the only app triggering MagiskD (its CPU usage should be practically zero).
Click to expand...
Click to collapse
Thank you !
I was just thinking about the same app, but i am using it since Sunday, and the problem is since the previous update( i was on the 10.3.10.0 only for 2 days)
But i am hoping this will solve everything!
Thank you again!
_mysiak_ said:
Try to uninstall XDA navigation gestures app, reboot phone to reset stats and then check after 1-2 hours again with the same commands if the situation has been improved. Hopefully it's the only app triggering MagiskD (its CPU usage should be practically zero).
Click to expand...
Click to collapse
Strange, the little cores are almost always maxed out 1804 Mhz.
But there is improvement since yesterday!
Now i am having around 1-1.2 %h drain.
By the way my old redmi 4 prime was way better, stand by drain- less than 0.5 %
alexandarpb said:
Strange, the little cores are almost always maxed out 1804 Mhz.
But there is improvement since yesterday!
Now i am having around 1-1.2 %h drain.
By the way my old redmi 4 prime was way better, stand by drain- less than 0.5 %
Click to expand...
Click to collapse
Could you upload the output from "top" commands somewhere else? Screenshots don't load via Tapatalk or web page of XDA, always giving me the error "can't load". Strangely the third picture loads fine everywhere
~1%/h doesn't sound so bad. My usual screen off usage is ~2%/h (wifi/data on, AOD enabled and often use of Whatsapp for web).On my wife's phone it's about 0.3%/h (wifi/data on, no AOD and only the "standard" apps).
_mysiak_ said:
Could you upload the output from "top" commands somewhere else? Screenshots don't load via Tapatalk or web page of XDA, always giving me the error "can't load". Strangely the third picture loads fine everywhere
~1%/h doesn't sound so bad. My usual screen off usage is ~2%/h (wifi/data on, AOD enabled and often use of Whatsapp for web).On my wife's phone it's about 0.3%/h (wifi/data on, no AOD and only the "standard" apps).
Click to expand...
Click to collapse
https://drive.google.com/file/d/19-wXJx249GfvroIe5eSDMPlHPRVvZyZL/view?usp=drivesdk - top
https://drive.google.com/file/d/18xJgNAl0Q7yi_gw-L7Z05jngqi1jaXLg/view?usp=drivesdk - top s11
I am not as worried about the 1%, as about the peaking processor, which is maybe leading to drain, and that not loading frequencies in every cpu tracking app( maybe kernel restrictions?)
alexandarpb said:
https://drive.google.com/file/d/19-wXJx249GfvroIe5eSDMPlHPRVvZyZL/view?usp=drivesdk - top
https://drive.google.com/file/d/18xJgNAl0Q7yi_gw-L7Z05jngqi1jaXLg/view?usp=drivesdk - top s11
I am not as worried about the 1%, as about the peaking processor, which is maybe leading to drain, and that not loading frequencies in every cpu tracking app( maybe kernel restrictions?)
Click to expand...
Click to collapse
Try switching to Facebook messenger lite at least for a while, the standard Messenger seems to be using an awful lot of CPU.
Which apps aren't working properly for you? I'll try them on my phone.
_mysiak_ said:
Try switching to Facebook messenger lite at least for a while, the standard Messenger seems to be using an awful lot of CPU.
Which apps aren't working properly for you? I'll try them on my phone.
Click to expand...
Click to collapse
Kernel adiutor on main screen showing " failed to load frequencies"
Gsam battery monitor cpu chart are not showing information about frequencies during the day.
About messenger, just one app force close did the work, now there is no cpu usage for that app.
Thank you for the guidance!
https://drive.google.com/folderview?id=16uFKuXgd1M5oR3F61j4pwTvsBzpnEUw3
alexandarpb said:
Kernel adiutor on main screen showing " failed to load frequencies"
Gsam battery monitor cpu chart are not showing information about frequencies during the day.
About messenger, just one app force close did the work, now there is no cpu usage for that app.
Thank you for the guidance!
https://drive.google.com/folderview?id=16uFKuXgd1M5oR3F61j4pwTvsBzpnEUw3
Click to expand...
Click to collapse
Kernel adiutor seems to be not working correctly, even for Mi A1 it required special version of the app. I guess it's not compatible with our device. Also it seems that it messed up the minimum CPU frequencies on my phone, try to uninstall the app and reboot, it might help "unstucking" your little cores.
About the CPU states, the issue is here:
testResults
file_not_exists:
/sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
It's either stock Android Pie behavior or Xiaomi forgot to implement this feature.
Edit: someone at Xiaomi probably really forgot to enable this.. https://android.googlesource.com/ke...ease/Documentation/cpu-freq/cpufreq-stats.txt
I am now trying to use messenger lite, because really Facebook messenger is doing something wrong, there are plenty of posts about that app triggering the cpu, or draining battery.
Now i think the problem comes from installing the latest security patch, but i didn't do anything wrong, the update via twrp is not something unknown, and i had the same problems in the previous version.
alexandarpb said:
I am now trying to use messenger lite, because really Facebook messenger is doing something wrong, there are plenty of posts about that app triggering the cpu, or draining battery.
Now i think the problem comes from installing the latest security patch, but i didn't do anything wrong, the update via twrp is not something unknown, and i had the same problems in the previous version.
Click to expand...
Click to collapse
The only problem, well 2 problems, I see with updating via TWRP:
1. you can't update with stock OTA if you ever decide to
2. you can't really say what's in someone else's TWRP backup unless you inspect it. There is always a small chance that someone tampered the file system and included some "extras". I'm not saying that it happened, but with stock fastboot images there's zero chance of modification.
_mysiak_ said:
The only problem, well 2 problems, I see with updating via TWRP:
1. you can't update with stock OTA if you ever decide to
2. you can't really say what's in someone else's TWRP backup unless you inspect it. There is always a small chance that someone tampered the file system and included some "extras". I'm not saying that it happened, but with stock fastboot images there's zero chance of modification.
Click to expand...
Click to collapse
In fact maybe that is the case, after typing tune2fs i can see that mount count is FIVE, i think that is why Ota has a problem.
Maybe i should flash stock fastboot image ?
Sapper Morton said:
Indeed, it has been tampered with; you should flash system image again, and if you use TWRP, be sure to follow as _mysiak_ explained, don't allow remount; also, check for other partitions if you want to restore manually, or for it to be easier, just run flash_all_except_data_storage, and do the OTA installation afterwards, the latest Magisk patched files are up, in the [ROOT] thread, by Typhus.
Click to expand...
Click to collapse
Hi, sorry for the dumb question,
Is flash_all_except_data_storage, a MiFlash tool command?
Or it is for adb?
Also which version of Mi flash will recommend? I found some tutorials to work with it but either they differ in the instructions or are not applicable in the latest version i found
Like the last fastboot rom i found is tbz file, not zip, as mentioned in some instructions.
alexandarpb said:
Hi, sorry for the dumb question,
Is flash_all_except_data_storage, a MiFlash tool command?
Or it is for adb?
Also which version of Mi flash will recommend? I found some tutorials to work with it but either they differ in the instructions or are not applicable in the latest version i found
Like the last fastboot rom i found is tbz file, not zip, as mentioned in some instructions.
Click to expand...
Click to collapse
1. unpack fastboot rom (tgz - Tar Gnu Zip)
2. unpack unpacked file again (tar). Then you will see flashing script files and images.
3. connect phone via fastboot
4. switch to partition A
5. run flash_all_except_storage.bat
6. wait for it to finish, phone will reboot automatically
7. congrats, you have fully stock phone now
The latest version of MiFlash should work fine, though I never used it. In each case you must make sure that you are on partition A.
hi again,
i would like to flash latest fastboot rom,(flash_all_except_storage.bat) because maybe have done something and have several unusual problem- heating again+40°C, while riding my bike, that cause and battery drain(less than 5 sot), super slow booting, so is the procedure the same as before? is the android 10 script have something different?
thank you!
P.S
Did it like before. Not sure if that fix my previous problem