Head-Fi.org › Forums › Equipment Forums › Portable Source Gear › Android phones and USB DACs
New Posts  All Forums:Forum Nav:

Android phones and USB DACs - Page 98

post #1456 of 4559

I think i know why, i activated fast charge earlier today... that might have killed it =( 

sucks because I currently have no job, and was relying on the phone on my applications. 

post #1457 of 4559
Thread Starter 
Quote:
Originally Posted by hypertek View Post

I think i know why, i activated fast charge earlier today... that might have killed it =( 
sucks because I currently have no job, and was relying on the phone on my applications. 

Oh, that might be a problem. I'd try factory resetting first, if its a software fault that should fix it... If not DanBa better add a warning about that to his list of confirmed devices. I hope a reset fixes it frown.gif
post #1458 of 4559
-stupid post
post #1459 of 4559

already took the phone apart, I am thinking about just credit card charging a broken screen verizon s3 from ebay and swapping the motherboard. Luckily i do have a recent backup of all my stuff on the sd card. Sucks though. But yeah please make that a warning, I am sure the fast charge killed it. 

post #1460 of 4559
Quote:
Originally Posted by hypertek View Post

already took the phone apart, I am thinking about just credit card charging a broken screen verizon s3 from ebay and swapping the motherboard. Luckily i do have a recent backup of all my stuff on the sd card. Sucks though. But yeah please make that a warning, I am sure the fast charge killed it. 

I've hooked a 12v charger up to my HTC and my now ex-GF's Samsung - killed them both.

post #1461 of 4559

What was your battery charge like when the problem occured?
If less than 25%, then I'd charge it up overnight.

 

Otherwise, try removing the battery for ten minutes.

Put it back in.

Then press volume down + power button + home button at the same time.

Keep holding them down until you get some sort of action on the screen.

If nothing at all comes up on the screen, then it's hard bricked. :(

 

If you get ANYTHING at all that comes up on the screen, then you might be okay.  Let us know!

post #1462 of 4559
Fast charge has nothing to do with the audio out except it uses the same cable? Did it vampire the fiio? I'm so sorry that happened man, total suck
post #1463 of 4559

Yeah i don t know how it could damage the motherboard, seems like its only software enabled via custom kernal or software. Maybe it shorted out.  No nothing shows up on the screen when I try powering it up, tried the reset button comands (holding up and home while hitting the power button, down and home etc).

 

At least I think its mainly the fast charge setting that messed it up. I mean i tested it before without fast charge with the new cable and e07k and it worked fine.. 

 

I did try a voltmeter to the battery and I am getting about 6v, I know the bat is rated at 3.8 2100mah, is that about right?

post #1464 of 4559
Quote:
Originally Posted by CZ Eddie View Post

 

Hahah,  I'm downloading Ubuntu right now to try and learn how to kernel hack so I can add USB drivers!

 

http://wiki.cyanogenmod.org/index.php?title=Build_for_d2att#Download_the_source_code

 

I'm pretty sure it's not just as easy as that.  But it can't hurt to learn a bit about the process.

Ktoonsez on XDA still says he's going to try and look into it soon.  He's a kernel dev.  

 

Great call! I've been wanting to sit down and actually learn a thing or two about this for a while. I don't doubt that the vast majority of it would be above my abilities, but I think I'd at least gain a greater appreciation of how these amazing little devices actually work if I could monkey around with their guts a bit ;)

 

Quote:

Originally Posted by WiR3D View Post

 

all I'm saying is NANDROID backup!

 

Ha! Roger that ;)
 

EDIT: Apologies for the hackjob on the multiple quotes here. Doesn't exactly bode well for somebody wanting to learn to code, eh? :p


Edited by Theogenes - 1/23/13 at 7:54am
post #1465 of 4559
Quote:
Originally Posted by hypertek View Post

Yeah i don t know how it could damage the motherboard, seems like its only software enabled via custom kernal or software. Maybe it shorted out.  No nothing shows up on the screen when I try powering it up, tried the reset button comands (holding up and home while hitting the power button, down and home etc).

 

At least I think its mainly the fast charge setting that messed it up. I mean i tested it before without fast charge with the new cable and e07k and it worked fine.. 

 

I did try a voltmeter to the battery and I am getting about 6v, I know the bat is rated at 3.8 2100mah, is that about right?


Sent from my ADR6425LVW using Tapatalk 2

I don't know how the voltage could be that high on a battery because the cell chemistry shouldn't allow for that. I suggest trying another battery. I suggest measuring the voltage on another battery also to verify your meter. A fully charged lithium chemistry battery is around 4.2V.
post #1466 of 4559
Quote:
Originally Posted by hypertek View Post

Yeah i don t know how it could damage the motherboard, seems like its only software enabled via custom kernal or software. Maybe it shorted out.  No nothing shows up on the screen when I try powering it up, tried the reset button comands (holding up and home while hitting the power button, down and home etc).

 

At least I think its mainly the fast charge setting that messed it up. I mean i tested it before without fast charge with the new cable and e07k and it worked fine.. 

 

I did try a voltmeter to the battery and I am getting about 6v, I know the bat is rated at 3.8 2100mah, is that about right?


Sent from my ADR6425LVW using Tapatalk 2

I don't know how the voltage could be that high on a battery because the cell chemistry shouldn't allow for that. I suggest trying another battery. I suggest measuring the voltage on another battery also to verify your meter. A fully charged lithium chemistry battery is around 4.2V.
post #1467 of 4559
post #1468 of 4559

Samsung rolls out Android 4.1.2 Jelly Bean update to the Galaxy S II

http://www.sammobile.com/2013/01/23/samsung-rolls-out-android-4-1-2-jelly-bean-update-to-the-galaxy-s-ii/

 

Does this means that USB Audio will now be available to SII users?

post #1469 of 4559
Quote:
Originally Posted by symont View Post

Samsung rolls out Android 4.1.2 Jelly Bean update to the Galaxy S II

http://www.sammobile.com/2013/01/23/samsung-rolls-out-android-4-1-2-jelly-bean-update-to-the-galaxy-s-ii/

 

Does this means that USB Audio will now be available to SII users?

Doubt it, read something about hardware incompatibility.

post #1470 of 4559
Quote:

Nope.

New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Portable Source Gear
Head-Fi.org › Forums › Equipment Forums › Portable Source Gear › Android phones and USB DACs