I have a big problem...
My battery status always shows as 0% no matter what i do
Brief story
_________________________________
whiped boot, system, data, cache, sd.
Got calkulin`s rom and installed.
didnt liked calkulin so much.
whiped everything again
got vegan 5.11 AND THE PROBLEM STARTED
_____________________________________________
What i have tried:
Format:
http://forum.xda-developers.com/showthread.php?t=974422
NVFlash:
http://forum.xda-developers.com/showthread.php?t=861950
Getting back to calkulin
Installing gingerbread(vegan Gingerbread)
installing froyo:
Stock, vegan 5.11, calkulin
restoring from CWM:
Restored to a time when the meter was working
Whiping battery stats:
http://forum.xda-developers.com/archive/index.php/t-868663.html
(After complete charge, when no battery left, other ways.)
External apps like battery doctor to show the battery level(with no luck)
_____________________________________________
Some especifications:
As long as the tab is Off, the battery/charger/led indicator work perfectly.
-When the charger is connected, the led light responses and turns red or green depending on the battery.
-The battery charges well. takes many hours to uncharge the tablet in use when you have reached the green light when uncharged.
When the tablet is ON:
-Since the second animation upon booting, the led light turns off if connected to power(not on if charges is not connected anyway)
-Battery meter always shows 0%
-If connected, the rom detects it and says that it is connected, but no response from the led light or the meter itself(it doesnt gets the battery metter full, just gets it as 0% but connected)
-Not even clockwork mod gets the led light on when connected. I am starting to really worry
Click to expand...
Click to collapse
Success. I had to open the tablet, plug and unplug the battery supply and when i booted, the battery meter starter working. Any ideas on what the problem was?
Let the battery completely drain and then reset the battery stats using CWM...Nevermind, I see you already tried that
ill try again because it seems to be what everyone is doing to solve similar problems; XD, but i have already tried once.
Thanks for the quick answer.
Any other recomendations...?
probably titanium back up + flash something else (try gingerbread experimentalist + vegan tested beta 2 (kernel) )
then restore your apps with titanium
ok, i tried the complete battery drain again, no success.
akodoreign said:
probably titanium back up + flash something else (try gingerbread experimentalist + vegan tested beta 2 (kernel) )
then restore your apps with titanium
Click to expand...
Click to collapse
I have tried the format utility, back to stock, vegan 5.11, and gingerbred experimentals+vengan tested 2 beta(kernel). No use.
I am really greatfull for the comments, but does someone else has any more ideas I can try??, I dont know, an ADB command or a APX script? I ma starting to get a little worried
***********Bump***********
I am getting desperate. It is really something very annoying, but most annoying is that i find no solution to it.
anyone please help...
I would say take it back to stock.
Battery meter shows that means its not completely done.
I would go back to your OEM Firmware.
http://www.thegalaxytabforum.com/index.php?/topic/112-samsung-galaxy-tab-firmware-list/
this is a complete list, just make sure you use the right .pit.
you could also try another countries variant to see if you at least can get it working.
vzt said:
I would say take it back to stock.
Battery meter shows that means its not completely done.
I would go back to your OEM Firmware.
http://www.thegalaxytabforum.com/index.php?/topic/112-samsung-galaxy-tab-firmware-list/
this is a complete list, just make sure you use the right .pit.
you could also try another countries variant to see if you at least can get it working.
Click to expand...
Click to collapse
This is a good recomendation and i would like to try it, but i dont have a galaxy tab; this is the Viewsonic G-Tablet.
WHOOOPPSSSS!!!! My bad. That's what you get for having multiple tabs open. Lol.
Sent from my SCH-I500 using XDA App
But here is a link to the stock firmware.
http://forum.androidcentral.com/viewsonic-g-tablet/50329-g-tablet-stock-rom.html
Another option that has gotten someone to at least clockwork.
http://forum.xda-developers.com/showthread.php?t=1008050
Sent from my SCH-I500 using XDA App
I already tried getting back to stock with format utility and nvfalsh with no luck....
Thanks for the comments.
I have the same issue. It started the same way as yours...hopefully someone can find us a solution
hello....
I found this post:
http://androinica.com/2010/02/tip-how-to-fix-your-androids-battery-issues-rooted-devices/
Can someone show me how would it be the process for the g tab?? Do i turn it of and use the power+"+ button" or i do it turned on?
Please, can someone that knows show me the right process for the g tab to make a safe process?
idontknowu2 said:
I have the same issue. It started the same way as yours...hopefully someone can find us a solution
Click to expand...
Click to collapse
What exactly did you do to have this problem as well?
I tried calkulins Rom and then went back to vegan 5.1.1....does your charging light turn on when the tab is powered on? Mine only charges when I shut down
idontknowu2 said:
I tried calkulins Rom and then went back to vegan 5.1.1....does your charging light turn on when the tab is powered on? Mine only charges when I shut down
Click to expand...
Click to collapse
i am not relly sure if it charges when connected when it is on. BTW; do you came from calkulin 1.1 too? I thought i would be because the battery saver script or something like that.
I have a questions for any developer or anyone that knows this kind of stuff, when the g tab is turned on, does the led light depends on the battery percentage or do they work apart?
I have the same problem from the moment of the first switching-on of the device.
From some time my device doesn't charge the battery even when it is off. Now the device doesn't work with the battery generally.
Here a fragment of an output of a command dmesg
<6>[ 6.509846] tegra_nand tegra_nand: tegra_nand_probe: probing (c06c7c70)
<6>[ 6.517326] tegra_nand tegra_nand: tegra_nand_scan: found NAND chip (Vendor = 0xad, DevId = 0xdc)
<6>[ 6.908714] tegra_nand tegra_nand: Block 0xaaf is bad [chip=0,offset=0x155e0000]
<5>[ 7.112181] 7 cmdlinepart partitions found on MTD device tegra_nand
<5>[ 7.118450] Creating 7 MTD partitions on "tegra_nand":
<5>[ 7.123590] 0x000000bc0000-0x000001bc0000 : "misc"
<5>[ 7.129139] 0x000003cc0000-0x000004cc0000 : "recovery"
<5>[ 7.134826] 0x000004d40000-0x000005d40000 : "boot"
<5>[ 7.140176] 0x000005dc0000-0x0000125c0000 : "system"
<5>[ 7.146068] 0x000012640000-0x00001ff80000 : "cache"
<6>[ 7.151085] tegra_nand tegra_nand: Block 0xaaf is bad [chip=0,offset=0x155e0000]
<5>[ 7.159352] 0x000000740000-0x000000b40000 : "bootbmp"
<5>[ 7.164976] 0x000001c40000-0x000003c40000 : "logodata"
and that
<6>[ 7.499720] Tegra High-Speed USB SOC Device Controller driver (Apr 20, 2007)
<3>[ 7.512513] tegra-udc tegra-udc.0: vbus_draw regulator error -19; charging disabled
I think, certain IC of the supply-controler has failed.
Question to experts. How the controler of charging of the battery is implemented? Is it posible to repair it in house-conditions?
In the attached file you can see some more errors.
Sorry my bad English.
View attachment dmesg.txt
0% at first boot
I just got my G Tab today, and when I first booted it, it just stayed at 0%. left it on/off, didn't matter. always showed "Charging 0%". I let it do the OTA update to 3588 hoping it would fix it. Afterwards it still said 0%, but I just turned off the screen for about 10 minutes. Came back and it showed 2%. After that it charged just fine, then I flashed TNT lite on it. I'm not sure what caused it to work, but hopefully this will help one of you with the same issue.
left off the screen in what build, was it connected to a power supply?
it was the official TNT stock build 3588. It was plugged in, cause if I unplugged it it would instantly shut itself off. I didn't run any custom roms until it was able to charge properly.
Related
Hi everyone,
My apologies if these issues can be solved by searching, I have tried and have spent many days already trying to sort out these issues then more keep arising.
Issue #1: Battery drain
I have the dreaded Android OS/kworker/wakelock bug - I'm losing 100% battery life within 6 hours and there seems to be nothing I can do about it. I'm planning on doing a full wipe of the phone and trying a reinstall of the OS to see if this solves the issue - but that brings me to issue #2
Issue #2 - Phone is not connecting to PC via USB
I am trying to do a backup and obviously flash my phone once the backup is done with the stock ROM for my phone (I am running a stock ROM at the moment but a clean version rather than the one from my provider loaded with rubbish) - http://forum.xda-developers.com/showthread.php?t=1602579 - the phone will not connect to the PC via Kies USB, it is charging via the USB but Windows reports "Driver installation failed" when it attempts to install the USB drivers to use the phone in mass storage mode.
I have tried in debug mode (it's on right now) if anyone was going to ask that.
Currently running 4.0.3 Official
Download mode DOES work and drivers install fine (Odin gives yellow box)
I have tried uninstalling and reinstalling KIES
Going to see if I can connect it via Wifi now to try and get all my stuff off - even if it is slowly :/
Thank you everyone for any help - I am rather upset that my phone which has worked perfectly up until now has suddenly gained 2 major issues at once - one of which cancels out me sorting out the other :<
i had similar issue,
uninstall kies, install USB drivers ONLY... restart
try different usb cables, make sure MTP is enabled if ur using a custom rom, on resurrection before 1.5 you had to run a few commands in terminal, thats what made it work for me!
Thank you for the information - I'm uninstalling KIES now - how do I just install the USB driver without installing KIES? I just tried reinstalling KIES again and had the same problem. Windows just fails to find any drivers and reports a failure to install the device. Which makes no sense because Samsung drivers are installed - Windows seems to be insistent on looking on Windows update, in preconfigured folders and then giving it a big red cross
http://dl.dropbox.com/u/34590193/SAMSUNG_USB_Driver_for_Mobile_Phones.exe
Hope this helps.
Thank you for that - I'm about to try a full wipe and see if that does anything for me.
Also on your PC go to Computer/Properties/device manager. Connect your samsung phone via USB. uninstall the samsung driver.Unplug your usb then plug it back in.
reinstall the drivers.
I was having these issues on the official Rom so I flashed resurrection Remix v1.5 (ics 4.0.4) and problem solved... If you have charged only one cycle I recommend you try some more...
Sent from my GT-I9100 using Tapatalk 2
Sent from my GT-I9100 using Tapatalk 2
Doing the full wipe did seem to solve the Android OS bug - until I unplugged it from the charger this morning and after 13 minutes I'm sitting on 88% battery CPU Total is 33m 19s and Keep awake is 12m 25s so once again kernel wakelocks are keeping it from deep sleep and draining the hell out of the battery.
I have just uninstalled ANY app on the phone that says "Able to prevent phone from sleeping" that I can uninstall in the hope that it's something simple.
Going by the fact I just did a reboot and already Android OS is using 83% battery - I don't think so.
The strange thing is that for about 2 weeks ICS was working perfectly - then with no warning at all it started draining the hell out of the battery with kernel wakelocks and for the life of me I can't figure out why.
Maybe I'll downgrade to GB and see if it helps.
Did you solve issue 2 so that issue 1 can be resolved. If you did then from recovery do a full wlpe, ie data/factory reset, delvik cache, battery stats. Then format system in mounts & storage. Install original gb firmware from Odin.
Sent from my GT-I9100 using xda premium
Hi all - thank you for the help thus far. I have an update:
I have downgraded the phone to my carrier's official 2.3.6
Neither issue is solved, Odin will see the phone if I boot it in download mode but Windows will not see it at all. I did a backup of all my data over Kies Air though and have done several wipes which were needed in order to downgrade to 2.3.6
The phone is still draining within 3-4 hours from a 100% reported charge. If I plug the phone into USB on the computer it reports as Charging (AC) which I found odd - since it used to say Charging (USB). I'm wondering if the battery is not getting a full charge since it's not being charged at full voltage but thinks it is?
I now have a new issue I didn't have when I previously ran 2.3.6 - the screen turns itself on and if I try to turn it off by pressing the power button it freezes, reboots and then repeats the same again.
I have done about 15 wipes so far, I've used 6 different MicroUSB cables and reflashed 2.3.6 7 times already - at this point I'm really over it since the phone is just unusable and I'm assuming there MUST be a hardware fault somewhere so I'm thinking I'll have to send it in for service and be without it for at least 2 weeks.
I'm rather frustrated by this whole thing because none of it makes sense. I've been told by the service guys to reflash right back to the branded 2.3.3 that shipped with the phone to see if that solves the problem and if not, to send it in.
If anyone else has any idea what I can do to fix this please let me know - it would be very much appreciated so I don't have to be without it for a minimum of 2 weeks :<
Phone is currently sitting next to me charging off USB - I just pressed the power adapter since again the screen was stuck on and it shut itself off. It now has the usual picture of the battery on the screen with the white dots moving underneath.
Another update:
Just did yet another wipe and for some reason this time the CSC comes up instead of coming up as unknown, and initially Windows detected it when I plugged it in via USB - then promptly said the device was unplugged a second later.
Got it charging now, but so far haven't seen the screen turn on randomly so it could just be that the problem of battery usage is solved, by downgrading from ICS to GB
I still suspect the USB port may be faulty since it's still not working within Windows (it does say MTP Connected though) but it still says "Charging (AC)" in the Settings -> About menu.
You need to try another PC or laptop. Also have you tried downgrading to 2.3.3.
Do a full wipe. If downloading the 2.3.3 firmware from Samfirmware, download the flash program too. Then try putting the recomended .pit file into odin.
Sent from my GT-I9100P using Tapatalk 2
Edit: Scratch all that - I just downgraded completely to 100% stock original shipped 2.3.3 carrier branded bloatware firmware and it appears in Windows straight away without any issues. This is really quite annoying >_< but I guess I'm stuck on 2.3.3 for now since it works or risking the ICS upgrade to 4.0.3 again and just downgrading again if the poop hits the proverbial fan.
Thank you everyone for your help - I still suspect the USB port may be bad but at least it's working for now. Please feel free to close the thread mods.
Update: For those that are interested - I have now upgraded to ICS again and it's working perfectly. Which is really odd and makes no sense. But for those interested:
I was running 4.0.3 unbranded (OPS but with XEU CSC) XXLP8 - USB not working, battery draining in 4-5 hours, USB detects as AC for some reason
Downgraded to 2.3.6 Unbranded (XSA) - USB detecting on phone and saying connected, CSC coming up as unknown but format fixed this. Drivers not installing in Windows for Kies or MTP - suspected USB port
Downgraded to 2.3.3 Branded (OPS) - This was what shipped with my phone, USB started working with MTP, pops up in Windows no problem - CSC working
Upgraded to 4.0.3 unbranded (XSA) - Still working with MTP in Windows without issue. Battery drain seems to be solved as well but we'll see.
USB when plugged in is now detecting in settings -> about phone as Charging (USB) again as well.
I have no idea what the hell happened, I've done so many wipes the last few days and everything else it just all makes no sense (speaking of which I haven't done a wipe since I upgraded from 2.3.3 to 4.0.3... I should probably do that) and for whatever reason downgrading all the way back has solved it. Thank you again everyone for trying to help, I guess it's just one of those weird issues that noone can explain :/
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?
I install Resurrection Remix JB 3.1.4 rom into my s3 last nite and it went fine, can do whatever **** it usually does. When I woke up this morning, it can’t be turn on anymore although it is charging from the time I went to bed.
This is what I did for the pass 24 hours:
Device: gt-i9300, previous rom is wanam lite.
1. Use Super Backup to backup my SMS, contacts, and call log
2. Use titanium pro to back up all user app+data and backup Email 4.0
3. Save RR JB 3.1.4 to my extsd 8gb
4. Went in cwm make full backup
5. Cwm wipe dalvik cache, battery, and reset factory
6. Install RR JB 3.1.4 from extsd
7. Successful. Done all settings. Restore all user apps. All went smooth.
8. Restore Email 4.0. Got forced close, but I just **** it. Reboot device, got forced close email again.
9. Play game, watch YouTube, facebooking, while charging the device.
10. Went to sleep with device charging.
11. Woke up this morning, device with green led on, unplug it, green led light when off, phone can’t turn on.
12. Tried to press here and there but nothing happens.
13. Grabbed my hair, bang my head on the wall, and shouted “fuuuuccccckkkkkkkk”.
14. Typing this post.
Any kind soul out there, please lead my s3 to the path of light….. Thanks in advance.
Have you flashed the ELLA bootloader?
This sounds like sudden death, check out the threads in General. But first, try replacing the battery and the charger
Glebun said:
Have you flashed the ELLA bootloader?
This sounds like sudden death, check out the threads in General. But first, try replacing the battery and the charger
Click to expand...
Click to collapse
Lol, sort of sudden death..... I don't know what is ELLA boot loader so I'm sure I didn't do anything about it. I plugged in my charger but the led didn't turn on and nothing appear on the screen. I will try to change other battery to test it. If it still doesn't work, I think it's called "freaking sudden bricked".....
Thanks for ur reply.
Samsung will repair it under warranty.
I'm sorry to say but you have the sds...
Verzonden door mijn GT-I9300 met xda premium
, it can’t be turn on anymore although it is charging from the time I went to bed.
Common issue of Sudden Death reports = overnight charge .
jje
Hello Devs,
I have problem charging my s3 international version.
My phone is rooted and running custom rom s5 sensation v4.0 kitkat 4.4.2 with boeffla kernel v6.0 and latest CWM touch recovery.
I have flashed many custom roms before and all was working good before. The phone was also charging properly before.
But after some time when 4.3 was released I have flashed s4 revolution.
After flashing that rom my problem started.
1st problem was the phone was not gettin connected to my cell tower. Later after searching soo many hours on google I found out that it changed the efs version from v1 to v2. So I found out a rescue zip file which include only modem of xxemg4. I flashed it and then all was working good.
After some time I faced a problem of reverse charging means the phone is kept on charge but instead of charging the battery decrease. So again I searched on google about my problem and found out an app called galaxy charging current which show the power that is getting the phone while its connected to the charger. when I installed it and saw the current it was only showing max 100 min 999 and avg 100. I saw some where that the default current the phone should get is 1000 in max.
I searched alot on google on how to solve this problem, tried many diffrent rom , tried changing my charger, tried to flash back the previous rom which I was using in which I was not having any problem but after doing all this the result was same.
when I connect to the charger it shows 700 In max n after some time it keeps going down like 500 then 300 then last 100.
So after searching on google I have found out a solution of flashing custom kernel. I flashed googymax kernel in which using sTweak we can configure the battery power and ignore safety measures and unstable power.
After doing that my phone gets max 1000 min 1000 and avg 999.
My problem is that when ever I flash new rom I hav to flash custom kernel to ignore the unstable power and safety measures to properly charge my phone.
is there any way I can get back as before I was charging my phone without flashing custom kernel...???
Any answer will be appreciated.
Note :- I was using the original charger which I got in the box while purchasing.
First replace your battery, charger and lead, then flash full stock firmware with Odin.
What happens when you attempt to charge the phone completely off. Do you see the charging graphic?
If something is wrong with the micro-USB port then a wireless charging solution might be your only option.
You could try reloading the firmware using the Kies software on your PC - here's an overview of what to do:
- if you don't already have the Kies software installed on your PC, download it (just search Google) and install it. The first time it runs it'll update itself to the latest version so make sure you run it once before proceeding.
- put your phone in Download mode: with the phone completely off, press and hold the Volume Down and Home and Power buttons simultaneously, and release them all when you see the Samsung splash screen
- connect the phone to your PC with the USB cable that came with the phone
-- if you've never had the phone connected to your Windows-based computer before, you'll see messages about installing drivers, etc - just wait until this is done (may take 5 or 10 minutes) [I don't know what happens if you have a Mac - it probably just works]
- in the Kies software, select the second item in the Tools menu and just follow the prompts to enter the model number (in CAPS) and IMEI/Serial Number (both found under the battery - it's ok to remove the battery at this point)
- the Kies software should start downloading the correct firmware for your phone from the Internet; once that's done (depending on your Internet connection speed) it'll begin downloading that to the phone (this probably takes 10 minutes or so)
Thnaks for your rply
boomboomer said:
First replace your battery, charger and lead, then flash full stock firmware with Odin.
Click to expand...
Click to collapse
1st of all thanks for replying on my query.
As u stated to change the battery, Charger, Lead and to full flash stock firmware.
I already did that.
I have tried my friends battery with his charger ( not the 1 which come in box ).
but then also its the same.
Whats the problem in it.
Is it a software fault or hardware fault....???
Hermosa said:
What happens when you attempt to charge the phone completely off. Do you see the charging graphic?
If something is wrong with the micro-USB port then a wireless charging solution might be your only option.
You could try reloading the firmware using the Kies software on your PC - here's an overview of what to do:
- if you don't already have the Kies software installed on your PC, download it (just search Google) and install it. The first time it runs it'll update itself to the latest version so make sure you run it once before proceeding.
- put your phone in Download mode: with the phone completely off, press and hold the Volume Down and Home and Power buttons simultaneously, and release them all when you see the Samsung splash screen
- connect the phone to your PC with the USB cable that came with the phone
-- if you've never had the phone connected to your Windows-based computer before, you'll see messages about installing drivers, etc - just wait until this is done (may take 5 or 10 minutes) [I don't know what happens if you have a Mac - it probably just works]
- in the Kies software, select the second item in the Tools menu and just follow the prompts to enter the model number (in CAPS) and IMEI/Serial Number (both found under the battery - it's ok to remove the battery at this point)
- the Kies software should start downloading the correct firmware for your phone from the Internet; once that's done (depending on your Internet connection speed) it'll begin downloading that to the phone (this probably takes 10 minutes or so)
Click to expand...
Click to collapse
Thanks for the reply.
When I try to charge my phone when completely off, 1st it was showing me the graphics of battery charging when I was using 4.3 Custom Rom. But since I flashed my phone with 4.4 Custom Rom, I can't see the graphics of charging battery now.
As per your overview above I have tried all the possible ways to get back charging work properly ( your overview was also included in it ) but I dont get any success in it.
Now I have to compulsory flash custom kernel which supports the options of ignoring unstable power and safety measures.
But then also I will try to do what you told me.
Once again thanks.
Hi,
I was using my phone as tether (usb).
I unplug my phone And some times later it shutdown showing 0% battery's boot screen. I know that was wrong.
So I plug in phone, reboot And immediatly see that phone show 20% charge. After 2 hours, phone remain at 20%
I use it all the Day And battery's indicator don't drop.
Battery stamina is the same as before.
Apps see it as "good"
I try to reflash previous And stock rom, Wipe dalvik And data.
Nothing change.
Phone remain with full life battery but at 20 %
So I don't know the real %
And I don't know if Quick charge drop or not. This May be dangerous.
Any idea / solution ?
Thanks to read
Try this,
Open up the phone app, and type *#*#7378423#*#* . You will get into the service menu. Go into Service Info -> Factory Charging. What % do you get?
Required level 50%
Present level 20%
Factory charging unfinished
Please connect the charger ( or Factory charging is going on, Please. Wait)
Sent from my E5823 using XDA-Developers Legacy app
hazote said:
Required level 50%
Present level 20%
Factory charging unfinished
Please connect the charger ( or Factory charging is going on, Please. Wait)
Sent from my E5823 using XDA-Developers Legacy app
Click to expand...
Click to collapse
how many sony telemtery services do you have disabled? diagnostics: sonymobile.devicemonitor and sonymobile.phoneusage give info to sonymobile.support and also to What's New and Lounge... when I had disabled permissions for support, i couldn't see any usage data until i opened Whats New and Lounge permission to storage and phone... this was when I was experimenting which apps i could disable without root and not cause the settings menu to crash
another thing to try is [Power + Vol Up] cache clear
When you flashed the Stock ROM again, did you leave (if you got one) the custom kernel on?
I would strongly suggest you completely flash the device anew with flashtool including the kernel.sin, even temporarily locking the bootloader. If it's still stuck then it's not a software problem and the battery controller might be wonky.
dumraden said:
When you flashed the Stock ROM again, did you leave (if you got one) the custom kernel on?
I would strongly suggest you completely flash the device anew with flashtool including the kernel.sin, even temporarily locking the bootloader. If it's still stuck then it's not a software problem and the battery controller might be wonky.
Click to expand...
Click to collapse
Yes I leave the custom kernel.
I had add a new battery, and all works fine now.
so I think this is the battery's controler that is dead .