Related
Hi folks,
I have got a problem with my S2 on NDTs newest MIUI rom running with the latest siyah kernel (actually problems started around mid december).
The phone freezes very often while having wlan turned on (esp. when I am using the market app). I have to take out the battery to revive the phone.
Second "problem" is that the phone reboots quite often lately (hot reboot, i dont have to enter my pin). it usually happens when i am playing some game or browsing the internet.
These problems have occurred on various roms (miui,ics,stock).
Need help as I need the phone for work (though I haven't had a reboot/freeze while talking or messaging). Anyone?
Maybe the logcat file can help. I saved the logfile moments ago, shortly after the phone had 2-3 reboots while playing Little Empire. I don't know how to "read" it though
Uh, and I asked the shop where i bought my phone about a replacement device. no chance. they want me to send the phone to their repair center which will take at least 7 days (the whole process). can't do that because i need it for work ((
a more experienced user will be along soon no doubt.
I'd do a full wipe and re-flash miui to be honest mate nobody wants to lose their data but if its randomly rebooting a lot then its possibly your only option other than sending it to be serviced.
Hey. I have done countless wipes and i have re-flashed different versions of miui more often than i can remember. I formatted /system and /data (/system was kind of stupid as I had to flash via Odin afterwards -.-). Even if I do not use any backups (I have also tried only adding my google account and installing some apps from the market after a clean install) these problems occur. ARG§$R%"$
dabrain23 said:
Hi folks,
I have got a problem with my S2 on NDTs newest MIUI rom running with the latest siyah kernel (actually problems started around mid december).
The phone freezes very often while having wlan turned on (esp. when I am using the market app). I have to take out the battery to revive the phone.
Second "problem" is that the phone reboots quite often lately (hot reboot, i dont have to enter my pin). it usually happens when i am playing some game or browsing the internet.
These problems have occurred on various roms (miui,ics,stock).
Need help as I need the phone for work (though I haven't had a reboot/freeze while talking or messaging). Anyone?
Maybe the logcat file can help. I saved the logfile moments ago, shortly after the phone had 2-3 reboots while playing Little Empire. I don't know how to "read" it though
Uh, and I asked the shop where i bought my phone about a replacement device. no chance. they want me to send the phone to their repair center which will take at least 7 days (the whole process). can't do that because i need it for work ((
Click to expand...
Click to collapse
i got the same problem! my phone freez on market often . i think it's not related to kernel ! probably something wrong with miui or market app.
Seriously no one?
really need help as i am close to throwing my phone against the wall -.-
have you tried a complete repartitioning of the phone, and then flashing a stock ROM with the new bootloader ?
(EDIT : looks to me like the problem comes from the modem you're using and your service provider, you got a lot of lines like those in your log :
I/TelephonyRegistry( 6376): notifyServiceState: 0 home Telekom.de Telekom.de 26201 UMTS CSS not supported -1 -1RoamInd: -1DefRoamInd: -1EmergOnly: false I/TelephonyRegistry( 6376): notifyDataConnection: state=2 isDataConnectivityPossible=true reason=null interfaceName=pdp0 networkType=3
Basically it tells you some parameter passed to the modem is incompatible with the service you're connected to.
I'd try flashing another modem -through CWM or Odin, don't matter as long as you do a dalvik cache wipe before you reboot the phone).
you mean repartitioning via odin?
somehow i tried flashing the original roms from here http://forum.xda-developers.com/showthread.php?t=1075278
but it didnt work. got any link for me (esp. new bootloader)?
Modem ver is XXLP6, prior to that i have been using BOKJ1 which was said to be specifically for T-Mobile (my carrier). the problem occurred on bokj1 too, just a bit less frequently.
Hm, no one else having these problems?
i guess i got unlucky with my device then ...
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?
Hello there and please excuse me for my bad english! As the title says, I can't connect to wifi network. Well, I can but it just work sometimes and works weird. Here's the scenario:
MIUI 3.6.7 rom on a Motorola Atrix 4G.
Android 4.1.2 JZO54K
Baseband N_01.77_38P
Kernel 2.6.32.60-MB860-CM10-ged7b511
On last sunday I tried to connect to a open wifi network, all week I was connecting to my home network. The status of wifi kept on "Turning on wifi..." for a while, but nothing happened. I restarted the phone and happened the same thing. At home, the connection worked but suddenly it closed for no reason. I tried to connect it again but kept again on the "Turning on wifi..." thing and suddenly the phone restarted! Not enough, it got stucked on the very first screen (the one with the "unlocked" text and Motorola logo), so I had to do a battery pull.
I've wiped Dalvik cache, cache partition, did some full wipes, installed again the rom (I was on 3.5.31 for then, updated yesterday to 3.6.7 and still the same), changed the Baseband, installed another kernel and I'm in the same situation. It's driving me crazy.
Got a logcat with Catlog, and found some (maybe interesting) lines (you can find the whole file in ge.tt/36KSn9j/v/0 -- sorry for be unable to post a link or uploading a file here):
06-11 15:21:54.508 W/CommandListener(1415): Failed to retrieve HW addr for eth0 (No such device)
06-11 15:21:54.508 D/CommandListener(1415): Setting iface cfg
06-11 15:21:54.508 E/WifiHW (1714): Unable to open connection to supplicant on "eth0": No such file or directory
06-11 15:21:54.508 I/wpa_supplicant(11001): rfkill: Cannot open RFKILL control device
06-11 15:21:54.508 E/wpa_supplicant(11001): Could not read interface eth0 flags: No such device
06-11 15:21:54.508 E/wpa_supplicant(11001): WEXT: Could not set interface 'eth0' UP
06-11 15:21:54.508 E/wpa_supplicant(11001): eth0: Failed to initialize driver interface
06-11 15:21:55.508 E/WifiHW (1714): Supplicant not running, cannot connect
06-11 15:21:59.508 E/WifiStateMachine(1714): Failed to setup control channel, restart supplicant
Googling about this got me to this thread (drakaz.com/forum/viewtopic.php?id=120... again sorry for the links thing) and got me thinking why the net interface is listened as 'eth0' and not 'wifi0' or something. I'm pretty noob to Android but I'm sort of an average GNU/Linux user, so I checked for what is going on in the dhcpcd.conf file and founded there the hostname was writed as 'wifi0' so I changed to 'eth0'... but this thing is still the same. Can you give me a clue about what the hell is going on? Thank you so much!
Make a nandroid backup and try a different ROM (preferrably a GB/CM7 based one).
ravilov said:
try a different ROM (preferrably a GB/CM7 based one).
Click to expand...
Click to collapse
Thank you so much for your answer! I tried CM7 (both stable and nightly, I heard the last one was a bit more stable than the first one) doing full wipe, of course. But when restarting, on both cases they only reached the very first screen (the one with the Motorola logo) and after like 5 seconds the phone rebooted automatically.
The thing is I really don't want to change MIUI. I've been using it since august, 2012 and I'm in love with it. This is the first time I got an issue so serious. Is there anything else I can do? Thank you so much!
No idea really. I'd tell you to do a full wipe before flashing but you've done that already. The only thing I can think of is flashing MROM (since its kernel has early USB enumeration) and then trying to pull out some more logcats very early on. This is quite a weird error and working out a solution will definitely involve a lot of creative thinking.
ravilov said:
No idea really. I'd tell you to do a full wipe before flashing but you've done that already. The only thing I can think of is flashing MROM (since its kernel has early USB enumeration) and then trying to pull out some more logcats very early on. This is quite a weird error and working out a solution will definitely involve a lot of creative thinking.
Click to expand...
Click to collapse
After the millionth full wipe I just got to install CM7 nightly and a clean reboot. But the wifi thing is still there... Well, a fc popup dialog appears after like 10 seconds: "Sorry! Application Settings (in process com.android.settings) is not responding.". I'm going to install MROM and catch a logcat, will be back then with a logcat. Thank you so much!
So I finally could get MROM working (I guess the thing about all GB roms rebooting when are just installed is about CWM). There's still the same thing I got with CM7. I have a logcat under MROM, and another I catched before I flased MROM (using MIUI v5): As I couldn't got MROM working just after wiping all when I was with CM7, I tried flashing MIUI. It flashed normally and at startup wifi was working, but after a while the connection closed suddenly. I got a logcat from that.
So the logcat with MIUI v5 (2013-06-14-02-26-28.txt) is here: ge.tt/6AQdiSj/v/0
And the logcat with MROM (2013-06-14-15-32-55.txt) is in ge.tt/7slxiSj/v/0
Hope this can help, I will keep pending so if you want to know something just let me know. Thank you so much for your help!
Seems that this is a problem about planned obsolescence. I'm such a noob, I hadn't seen this thread before (http://forum.xda-developers.com/showthread.php?t=1656760) where they explain many people had this issue. I can't post to that thread, but seems that they never got their wifi working again as I do sometimes. This is the weirdest s**t I've ever had with an electronic device.
Hi, I'm running cyanogenmod 10.1.3-i900 on my phone. The problem that i have is that it frequently looses connection, sometimes even while i'm on the phone.
If this happens i can't even search for networks in my area it just says "network error" or something like that.
I tried several modems that should work in my area:
XXLPS
XXLPX
WXKL3
KG6
KL4
Some work better, some worse but none of them solve my connection issues.
On my old phone (Galaxy 3, not s3 ^^, with kyrillos rom) i could turn on aircraft mode to reset the connection if i had problems but with the i900 only reboot works. If i go into aircraft mode it doesn't ask for the sim-pin if i turn it off again.
I'm using my phone in germany and my network is o2 (or their resseller simplytel)
Where can i start looking for the root cause of those issues? Or can you recommend a ROM or modem that i should try instead?
best regards Samy
I also have the problem that my internal storage runs low so i investigated it at it seems that i the /data/log folder runs full with 1438 1mb big log files that have this title:
dumpstate_ril_RESET_BY_CP_SILENTRESET_2014xxxxxxxxxx.log
I know that ril is something you shouldn't touch while messing with your phone, i guess cyangen mod messed with it somehow and maybe that is the root cause of my problem?
I tried xxlpw now because i thought it is still a modem issue but, same proble: I loose connection after 3 minutes, and then i can't even search for networks anymore. Plus 2 new log files with dumpstate_ril_RESET_BY_CP_SILENTRESET_2014... in the /data/log folder
UPDATE:
I'm now trying all the modems from the cyanogenmod site for the I9100:
I9100XXKDH = 3 disconnects (+dumpstate_ril messages) in 40 minutes reconnected though no permanent crash (network error)
I9100XXKDJ = 5 disconnects in 30 minutes, last one permanent (no reconnection).
I9100XXKE4 = 5 disconnects in 8 hours, but then i went on a train and had one disconnect every minute
I9100XXKE7 = 0 disconnects while driving on a train, 5 hours running, i hope this will be it
UPDATE: I9100KE7 seems to be the best modem for my area/phone and network and solves all my problems:
0 disconnects in 28 hours and counting
Hey Guys , so today i have a very very strange error to report ,
It occured on my Galaxy S3 and started almost 3 weeks ago ago with some apps disappearing from the phone but easily beeing reeinstalled (noticed it because it affected my Launcher (Nova Launcher) about 1 week ago the well known UID´s inconsisten issue begann to show up , however no new apps have been installed to the device in at least 2 months and it was pretty much a standard setup ( not even rooted)
the device started crashing several times during random use ( with the interesting exception of ongoing calls)
After each reboot the UID´s inconsitent error wash shown , after 1 day suddenly the phone lost all user Settings ( passwords ,Launcher settings and Contact information , yet none of the data , only the user storage was affected , the UID´s inconsistent error was still beeing shown .
then yesterday the phone got stuck entirely
now the device seems to operate for about 1 second after power , leading to it beeing stucked on the Galaxy S3 screen when starting normaly and the battery loading screen when connecting to Power ( it is not active long enough to determine battery levels , the waiting circle is in it´s starting positon )
booting into recovery mode and Download mode is sitll possible , safe boot is not responsive.
if i start Android System Recovery (<3e>)
a string of near identical errors show up in the following scheme :
E:failed to mount /cache ( No such file or directory)
E:failed to mount /data( No such file or directory)
and so on
when i try factory reset the error is
E:format_volume: make_ext4fs failed on /dev/block/mmcblk012
Should i try reinstall the device with Odin or is this a lost cause that requires a hardware fix ( or probably scrapping the device concidering the age)
i am looking forward to your help
Do you no what android version you have installed? something like 4.1?
Version
Darke5tShad0w said:
Do you no what android version you have installed? something like 4.1?
Click to expand...
Click to collapse
Yes it is 4.1.2 , and it is the standard international version without sim lock( in case that makes a difference)
Try and flash stock again with odin, once i get on the comp ill past you a link to read up on.
Sounds like it maybe this
http://forum.xda-developers.com/galaxy-s3/general/sudden-death-sds-dont-android-4-1-2-cwm-t2091045
If flashing stock with odin does not help try the rescue firmware then im sorry but im out of ideas.
http://forum.xda-developers.com/showpost.php?p=30087735
http://forum.xda-developers.com/galaxy-s3/help/s3-dead-e-mount-t2824869