Database Info

[Q] May WiFi tethering damage the phone?

Hi guys,
I've a question I cannot properly answer by myself. I've searched the web but I didn't find an exhaustive answer.
I wanna use my Nexus S as WiFi router during holiday, for about one month, several hours a day. I'm concerned to possible damage that this could cause to my phone, especially due to overheating and fast battery drain.
When I tested WiFi tethering I noticed, obviously, overheating and also battery drain.
Since the phone will be probably connected to wall charger while tethering (that causes overheating itself), could the excessive heat damage something, somehow? I think I'll underclock to embank it a little, but I'm still worried..
And also the continue charghing of the battery, beside overheat, could really damage it ? :silly:

gnaurittiello said:
Hi guys,
I've a question I cannot properly answer by myself. I've searched the web but I didn't find an exhaustive answer.
I wanna use my Nexus S as WiFi router during holiday, for about one month, several hours a day. I'm concerned to possible damage that this could cause to my phone, especially due to overheating and fast battery drain.
When I tested WiFi tethering I noticed, obviously, overheating and also battery drain.
Since the phone will be probably connected to wall charger while tethering (that causes overheating itself), could the excessive heat damage something, somehow? I think I'll underclock to embank it a little, but I'm still worried..
And also the continue charghing of the battery, beside overheat, could really damage it ? :silly:
Click to expand...
Click to collapse
The battery may be degraded a little bit as a result of overheating. As for the rest of the hardware, I'm not sure what the effect is on that, shouldn't be a real issue I guess. You can try to cool your phone with an icepack underneath it or something? But why not just take a wifi router with you? or make us of Ad-hoc from the laptop?

kwibis said:
The battery may be degraded a little bit as a result of overheating. As for the rest of the hardware, I'm not sure what the effect is on that, shouldn't be a real issue I guess. You can try to cool your phone with an icepack underneath it or something? But why not just take a wifi router with you? or make us of Ad-hoc from the laptop?
Click to expand...
Click to collapse
Yes, I thought about cooling the phone somehow, but it sounds weird :silly: Anyway, I'm on linux and the driver (iwl4695) of the wifi card on my laptop doesn't support AP-mode ( I need to connect more than one device to it), so I cannot use that. I would do this to avoid buying a brand new device such a MiFi, but I'm not still sure, but maybe it will be the best choice, (apart from the 50€, obviously :laugh: )

gnaurittiello said:
Yes, I thought about cooling the phone somehow, but it sounds weird :silly: Anyway, I'm on linux and the driver (iwl4695) of the wifi card on my laptop doesn't support AP-mode ( I need to connect more than one device to it), so I cannot use that. I would do this to avoid buying a brand new device such a MiFi, but I'm not still sure, but maybe it will be the best choice, (apart from the 50€, obviously :laugh: )
Click to expand...
Click to collapse
They're not that expensive are they? Couple of years back bought a very cheap wifi router for 20 euros... still functioning :good:But good luck with your decision

kwibis said:
They're not that expensive are they? Couple of years back bought a very cheap wifi router for 20 euros... still functioning :good:But good luck with your decision
Click to expand...
Click to collapse
Finally I opted for WiFi tethering. Battery is about 42-43 degrees, but it's fine for now. And it's also charging with USB, great. I'm posting this with my PC WiFi connected to the phone.:laugh:
BTW, if phone will die for this, nevermind, it will be a good reason for switch to Galaxy Nexus :silly:
Anyway, thanks for help.:good:
I ìll leave this unsolved, because even if I solved my own situation, it will be interesting read experiences of users using their phones as router for extended period of time. I'll post my own experience after holiday.

ive been using wifi tet. while on my last holiday for about a week, few hrs a day, never got warm/hot when unplugged from charger, although when on charge and i was streaming videos from net , phone was warm..
if ur phone is really hot while using wifi tet, try to reflash ur rom.

Battery discharge while on charger

Using CM11 snapshot january update
I woke up late last night to see my phone still with the yellow charging light on while it was on the charger. i found that odd since it had been on the charger for almost 4 hours. i went to bed with it at 75% and when i went to the battery page it was at 50%. wierd thing is the graph says "3hr and 50 min on battery" but the line graph shows that its is, in fact, charging. another thing ive noticed is that the wifi line graph is solid, im not 100% sure its supposed to be intermittent, i.e. phone is sleeping and what not.
once i noticed that it was still discharging i looked at running apps, nothing outside what anyone else would have running at the end of the night. after i cleared the running apps it started charging again.
i know that i may have answered my own question at the end of the second paragraph but chargers put out more power than a phone can consume while being dormant so im trying to isolate a handful of things.
1. is the wifi line graph supposed to be solid all the time? (I didnt think so but)
2. is the rom im using (cm11 snapshot current update) on an outdated kernel?
3. whatever else that can brainstormed
and before i get a but of wrong forum reply's, i dont have a choice i need my 10 reply's to get this into the correct forum..... unless admin moves it into a developer forum....eh...eh?
thanks for any help you guys can provide.

Justyn86 said:
Using CM11 snapshot january update
I woke up late last night to see my phone still with the yellow charging light on while it was on the charger. i found that odd since it had been on the charger for almost 4 hours. i went to bed with it at 75% and when i went to the battery page it was at 50%. wierd thing is the graph says "3hr and 50 min on battery" but the line graph shows that its is, in fact, charging. another thing ive noticed is that the wifi line graph is solid, im not 100% sure its supposed to be intermittent, i.e. phone is sleeping and what not.
once i noticed that it was still discharging i looked at running apps, nothing outside what anyone else would have running at the end of the night. after i cleared the running apps it started charging again.
i know that i may have answered my own question at the end of the second paragraph but chargers put out more power than a phone can consume while being dormant so im trying to isolate a handful of things.
1. is the wifi line graph supposed to be solid all the time? (I didnt think so but)
2. is the rom im using (cm11 snapshot current update) on an outdated kernel?
3. whatever else that can brainstormed
and before i get a but of wrong forum reply's, i dont have a choice i need my 10 reply's to get this into the correct forum..... unless admin moves it into a developer forum....eh...eh?
thanks for any help you guys can provide.
Click to expand...
Click to collapse
forgot..

solid wifi line.. go to the phones main settings, wifi, wifi settings(3 dots bottom right), advanced, disable scanning always available.
cm uses cm kernel. outdated is when a kernel is no longer good, a lower kernel number doesnt mean anything.
and this kind of post have no business being in development, no mod would ever even consider moving it there. development is for development, not questions that are very basic. you actually got the right forum.

Weird. As Sims said turn wifi scanning to off.
It could be a nightly issue with CM at the current moment, check there.
PS: There are other ROMs than just buying a phone and throwing cyanogen mod on it.

Good deal. Thanks guys.
I know I could put any ROM on a phone I used to have an s4 and did several ROMs with that. Then I had to send it in and they gave me one that was mf3 and I was just tired of jumping through hoops. But I put cm on mine because I getting away from full service and using strictly Google voice on a data only plan for cheaper service (Att is the best service overall where i am but their no contract sucks), and cm, so far, is the only one that has voice plus to integrate gv SMS into you native SMS app. That's my big thing. But if there's other ROMs at utilize voice+ I'm open to them.

I'm going to be of no help to you, but just to let you know, this is the correct forum. Nothing except something that you developed goes in development. Nothing. Questions and all other random things go in either Q&A or General.

I don't see you mention which charger you used. Wired? Stock charger and cable? The WiFi bar will be solid over night with your WiFi on and never intermittent.
Sent from my Nexus 5 using Tapatalk

Yea after I was told to look at the WiFi settings, I changed some settings. But yes Its wired. I played around with the cable and it wiggles a bit but I didn't notice it disconnecting but I'll do More investigating on that front over the next few days.
Sent from my Nexus 5 using Tapatalk

Justyn86 said:
Yea after I was told to look at the WiFi settings, I changed some settings. But yes Its wired. I played around with the cable and it wiggles a bit but I didn't notice it disconnecting but I'll do More investigating on that front over the next few days.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Wiggle won't effect charge speed. Using a different adapter or cable then what came with your phone will effect charging speed however as well as the phone's current draw.

Well yea right. What I meant to say was that I may not be getting a solid connection, and if I had it sitting a certain way, it may not be charging at all, making appear as though the battery was draining "while charging" when it actually wasn't even charging. My biggest thing was that this is the first I've noticed it so. Maybe the cable is just crappy and is giving out. ( not the OE cable)
Sent from my Nexus 5 using Tapatalk

Justyn86 said:
Well yea right. What I meant to say was that I may not be getting a solid connection, and if I had it sitting a certain way, it may not be charging at all, making appear as though the battery was draining "while charging" when it actually wasn't even charging. My biggest thing was that this is the first I've noticed it so. Maybe the cable is just crappy and is giving out. ( not the OE cable)
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Most likely it's just the cable then. You may be interested in the contents of this thread including a quick comparison video Bacon made.
http://forum.xda-developers.com/showthread.php?t=2609087
http://www.youtube.com/watch?v=wGYkt4CeYuk&feature=youtu.be

Wow that's pretty impressive makes me want to get Motorola cable
Sent from my Nexus 5 using Tapatalk

Turns out a combo of things. One being the cable with now power output. And the other was just being a cheap cable and was fitting in the port loosely and not maintaining a connection all the time. Thanks for the help.
Sent from my Nexus 5 using Tapatalk

[Q] phone not being recognized at ALL as usb? (cm11)

hi..
after installing cm11 it would appear my phone is not being recognized as usb device at all? neither as usb mass storage device or as mtp , i does charge the phone, but that's it.
i've enabled MTP in usb comptuer connection, and tried to connect it to 2 different computers.

Hmmm. I haven't seen an answer to this question posted yet. Emaayan, did you ever get a resolution to this? I actually have run into this twice in the past, and the answer is to shut the phone down, and do a battery pull to reset the hardware completely. Had me scratching my head for months, and even had me develop a way to do a full unroot and return to stock without ever touching USB or terminal, until I took the battery out of my fiancee's phone since we were planning on returning it, and using it on what would've been her backup phone. When I returned the battery to it, the USB worked again. It's not a CM issue, or a software issue at all. It's definitely a Samsung not-initializing things properly issue. I've seen it happen on stock, I've seen it happen in the old 4.3.1 FatToads, and the 4.4.X FatToads.

Let me know if the above works (battery pull).
I had this issue too, didn't realize it until I tried updating different roms...
I put on Carbon after OmniRom ... OmniRom was overheating my phone and battery and it was at that time I actually pulled it apart and wrapped it in a gel ice pack to cool it down.
I don't recall if Carbon had worked, but I'm back on CM11 now and am getting USB working.
I also updated to the latest CWM per OmniRom thread in development forum.
I trust Magamo, though, in providing the right diagnosis and solution.

mod please delete

REV3NT3CH said:
i believe OmniRom caused my phone to brick...flashed it to see the issue people were having to help with a fix....apparently lbcoder is breaking stuff again lol...when i get either a new relay somehow or fix mine..i may look in their code to see what it is...im almost assuring its how MTP is not being handled correctly.... i respect @Magamo and most the other devs.. but all i can do is suggest a fix and get disrespected by lbcoder
Edit: like this for example https://github.com/TeamApexQ/androi...mmit/b9d389cca9f241d778f1d8206195e16dfcb3dee8
Click to expand...
Click to collapse
OmniRom was not the cause of your bricking, I hate to break it to you. The commit you just linked actually has very little to do with the kernel. It was an update to fstab to match a change in paths. There was no driver functionality change in anything that was dependant upon. If you respect me, I would appreciate it if you were to stop spreading FUD about us, and my work. I'm starting to become personally insulted here. Bricks more often happen due to faulty hardware. No properly booting kernel would have been the cause of what happened to you. I assure you, our kernel is working properly.
This is also completely off topic to the question asked. As stated, I've personally seen this happen on several images, Stock included. This particular issue is a Samsung hardware initialisation issue, and is resolved by a battery pull.
Since it is off topic for this question, I will not ask here what you feel is wrong with our MTP code. We can start another thread, and stop hijacking this one. Better yet, as always, the best place to discuss this with us would be on IRC.

Surprisingly, pulling the battery fixed the problem!
After spending the last few days without my phone being recognized by multiple computers and considering a factory reset on a Samsung Galaxy Relay, I came across the post here mentioning that pulling the battery worked to fix the problem with phones not being recognized through USB.
I can vouch that pulling the battery does fix the problem with devices not being recognized.
Perhaps these devices should have a more convenient way to pull the battery if doing so makes them work properly.

Autolooper said:
After spending the last few days without my phone being recognized by multiple computers and considering a factory reset on a Samsung Galaxy Relay, I came across the post here mentioning that pulling the battery worked to fix the problem with phones not being recognized through USB.
I can vouch that pulling the battery does fix the problem with devices not being recognized.
Perhaps these devices should have a more convenient way to pull the battery if doing so makes them work properly.
Click to expand...
Click to collapse
It's not working for me. I have the MTP available, but not simple USB Mass Storage with CM11. Any other ideas?

xob3444 said:
It's not working for me. I have the MTP available, but not simple USB Mass Storage with CM11. Any other ideas?
Click to expand...
Click to collapse
Android 4.0+ no longer supports USB Mass Storage out of the box for the internal storage, and neither do any of the custom images that I can think of. MTP is the answer here. The fact that you are getting MTP means that the device is talking over USB, which means that you are not suffering from the problem described in this thread.

[Q] Battery drain on cyanogen

I did not find an answer for this so i wanted to know if the battery bug also happen in cm11?
if not i will just change the rom to cm11 and not wait for a stable release.

There is no such bug, it's a problem caused by usage of charger with one-step charging only, which cause the electronics on the battery to go nuts.
Same goes for using a lousy/bad USB port on your computer, especially if it can't reach 500mAh output for some reason.

so if there is not any problem why motorola said they are checking it and there is a 30 pages thread here with people who complains about this problem?

st379 said:
so if there is not any problem why motorola said they are checking it and there is a 30 pages thread here with people who complains about this problem?
Click to expand...
Click to collapse
Read again what I've written.
I had over 30 moto g passed in my hands in the post 3-4 months and not even 1 have had this issue.
Either I've been extremely lucky and np one ever complained or I dunno.

http://forum.xda-developers.com/showthread.php?t=2545553&page=30
like you can see it is a very strange problem but maybe it is a charger problem.
I just wanted to know if maybe the rom is the blame in this problem.

Wifi issues and Q about flashing stock ROM

Hi, I bought a used Verizon Note Pro 12.2 SM-P905V and when I got it, noticed that the wifi is very flaky. Initially, it connected to my router fine but took 9 hours to load 120 apps when I signed in to Play using my normal Google account. So I did a factory reset, and then it wouldn't see my router at all. Restart router, factory reset device, no dice.
In the notification shade, wifi icon is always green as if it's on, but when I go into settings, the toggle is off. When I slide it to on, it turns gray and after a minute or so goes back to off. Multiple hard resets, still the same issue. Occasionally, it will "see" the routers, but this only lasts for a few seconds and then they are gone.
So I decided to flash the firmware. I did not complete another factory restore before I embarked on this, but had only just gone through the initial language screens and signed in on the tablet with a brand new Gmail account that had nothing on it. So I downloaded official 5.1.1 ROM from Sammobile, installed device drivers, installed Odin, (followed some great instructions found on XDA, thanks), got the tablet into download mode, connected to laptop and Odin on my laptop showed connection was live and it began to do it's thing. So I left it alone for 30 minutes and when I came back, Odin read "all done!" (or something similar) highlighted in green , and the tablet had restarted, so I assumed all is good.
However, I expected that the flash process would have wiped the setup I had begun on the tablet, but it did not. And the wifi issue still exists. Looks to me like nothing has changed. So two questions for you:
1) Does this mean that the flash did not happen correctly?
2) Do you have any suggestions on how I can fix this wifi issue? (LTE works fine but I don't want to eat up all that expensive data.)
Thanks for any help!

Wifi circuit has many components on mainboard and I believe it's beyond abilities of most users even professionals as you cannot find components and schematic to fix them.
Your best source is looking for this tablet with a broken LCD like this one:
http://www.ebay.com/itm/172145691764?_trksid=p2060353.m1438.l2649&ssPageName=STRK:MEBIDX:IT
http://www.ebay.com/itm/Samsung-Gal...069075?hash=item1a15927393:g:D8MAAOSwbYZXZKDb
If you don't have the need to LTE connection, Note Pro wifi mainboard SM-P900 also fit but you need rear camera for SM-P900 as rear camera of LTE won't work in Wif mainboard.
Any LTE Note Pro 12.2 like P907T( Tmobile) P907A ( AT&T ) mainboard will fit to P905V as they are exactly the same mainboard, except firmware, bootloader and software loaded into it.
I swapped a SM-P907A mainboard to a SM-P905V tablet, it works as an AT&T tablet because the software is for AT&T.

I purchased a verizon note pro 12.2 SM-P905V refurbished from groupon last October. For the last few months the wifi on the tablet has been very flaky. I have a number of devices and only this one frequently drops connection. I never upgraded from kitkat I and was hoping that this issue was software related. Seeing that moransw is experiencing the same problem with this same model but is trying to get back to sock kitkat gives me concern that a software update will not resolve the problem. The other problem I've been having lately is that the device no longer recognizes the stock charger, and will now only charge painfully slow. I've tried a different charge cable from a samsung s6 to no avail. Is the SM-P905V a lemon?

You should use this one to test your charger and usb cable
http://m.ebay.com/sch/i.html?_nkw=u....Xusb+voltage+current&sqp=usb+voltage+current
If you're using correct cable and charger, current should be 1.7 A and voltage should be 5.3 V
Test with known working cable and charger, if nothing is different you should consider to buy new usb flex charging port, around $10.
These basic steps you should do first as nobody can give exactly an answer with many unknowns. It happens to many used tablets, not just this model.
These basic troubleshootings are easy done for simple problem of bad cable, charger or USB port
Try them first then post your results if you need more help for further steps

moransw said:
However, I expected that the flash process would have wiped the setup I had begun on the tablet, but it did not. And the wifi issue still exists. Looks to me like nothing has changed. So two questions for you:
1) Does this mean that the flash did not happen correctly?
2) Do you have any suggestions on how I can fix this wifi issue? (LTE works fine but I don't want to eat up all that expensive data.)
Thanks for any help!
Click to expand...
Click to collapse
1) I am using stock kitkat rooted and I was experiencing the same issue
2) I found this thread regarding our tablet that seems to suggest a bug with wifi if you are using a Bluetooth device
http://forum.xda-developers.com/galaxy-note-pro-12/help/wifi-disconnects-bluetooth-device-t2851406
I was streaming audio through bluetooth to my home surround system, I disabled the bluetooth radio and I haven't had an issue with wifi since. I now use chromcast to stream audio through my surround sound.