Database Users

Big Problem with USB

Hi. I moved from a DInc on Verizon to the Vibrant because I hated the sunlight on an AMOLED, and because Verizon was stealing my money. Although honestly verizon just lowered prices, and Tmo's network is still crap in my town.
Anyways down to business: My phone is rooted, and I applied one click lag fix. I am assuming that was when problems started but then again not for sure. I've gone from stock to Vibrant5 to Vibrant6 roms, no change.
The first problem here is this: my phone always thinks it's plugged in to USB. It cycles on an off, but never just stops and stays normal. I'm talking several times a minute ''usb connected'' or whatever on, off, on, off... annoying but no big deal. Except that freaking battery meter that pops up when your phone is off but plugged in via USB starts popping up when it's not plugged in and my phone is turning on... but since there isnt really usb in, it just hangs and resets. The second I plug in a real usb, meter pops up and i just turn it on and all good.
Second problem, which makes it so bad: my phone does this things that I've seen on XDA several times where when the processor bogs down, or GPS is on, or whatever taxes the phone, it will randomly reset once or twice a day.
Put those together and what you get is me, in public away from a charger, with a phone that won't turn on. WTF. So I repeatedly take the battery out and jam the power button till once in a while I'm able to start it before the stupid usb thinks its plugged in. Other times I'm screwed till I find my car charger.
Now, what can I do? Before anyone says warranty, yes I unrooted, did my best to unlagfix, and went to the Tmo store. They ordered me a new phone. However I have to send mine in when it gets and here and would like to insure there is no root related crap for them to find, plus I'm stuck with this phone freaking out on me for another week.

I was having the same problem , but it started since.my dougther put the usb canle in her mouth xD , I just cleaned the contacts and waited a few hours but now is fine , running
Vibe6 oc
Sent from my SGH-T959 using XDA App

cleaned the contacts on your cable, or inside your usb port on the phone? How would you clean those?

Sooooo, no input huh. Okay then.

trevorwhopkins said:
Sooooo, no input huh. Okay then.
Click to expand...
Click to collapse
If people keep messing up their phones by rooting and flashing roms and then, rather than trying to fix the problem, send them into tmobile, I bet future firmwares and android phones will be more like the iPhone and iOS.

First I would try to flash it back to stock and leave t factory. Then if problem persist, its probably hardware. I mean you are returning it anyways so flash it back to the stock rom and do a factory reset
Sent from my SGH-T959 using XDA App

[Q] usb debugging failed

USB debugging no longer activates on my phone. Activating it in settings/applications/development brings up the "Allow USB debugging?" permission window. However, no usb notifications appear, and the phone appears to be a dead device to any PC it is connected to.
This started when I accidently got into the download screen from the phone options popup. The display showed the yellow sign, android guy with shovel, and message warning not to turn target off. Phone was not connected to anything at the time.
Searching found a couple of threads indicating that a battery pull was safe to get out of it. Did same.
Since then, usb debugging (or usb anything) has been dead on this phone. Other methods of usb access (thru usb settings) have no effect either.
Tried the following...
(1) restore to my last backup rom.
(2) numerous reboots and battery pulls.
(3) mount/unmount sd card in cwm recovery
(4) clear caches
(5) changed pc's and cables (all worked before)
(6) reinstalled usb drivers on pc (worked before, didn't expect it to help since issue is at phone end)
As you can see, I'm running out of sticks to poke the horse with. Does anyone have any ideas?
Update: new kernel didn't help, either
Update2:
(a) Can't do a restore via odin, which won't detect the phone.
(b) Updated my adb (which I don't use much). adb devices command will not detect the phone via usb.
(c) Installed adbWireless which allowed me to push a stock nandroid backup to the phone. Restored that, usb is still dead.
(d) Restored back to my superdark rom, usb is still dead.
Head scratch: I'd blame hardware except that it seems to be between the settings and execution. If it was purely hardware, I'd expect to see the usual usb notifications. Regardless, it looks like I'll have to revert back to stock and let Verizon figure it out.
Update3:
(a) switched to the new AOSP rom. Nice, but no usb.
(b) switched back to superdark since I like my speakerphone and the AOSP seems to be on hold. Still no usb.
Resolution:
My apologies for not posting a resolution. My bad. After the first few days the post kind of fell off the radar and I stopped checking.
Short version...dirty usb port.
Details...after a week or so, I saw the usb icon flash in the notification bar for a few seconds when I plugged it in for a recharge. Hadn't seen that in a week, hope springs eternal!
A thorough cleaning of the usb port using a paper swab dampened with alcohol restored usb functionality. Not much dirt came out on the paper, but it must have been enough to probably bridge the contacts somehow.
At present the phone is fully functional. The original Verizon cable seems to be a little wonky. I have an aftermarket cable that works fine. It may be that the aftermarket cable did some physical harm to the contacts in the port, or the original cable is going bad (I had something very similar happen on my Omnia). Not sure.
I now use the original verizon cable only for charging at work and use the aftermarket cable for usb connecting at home.
Bottom line...if your usb goes dead as described in the op, carefully clean the port.
My thanks to all who responded...

Download screen shouldn't have harmed you.
You probably are well aware of this, but sometimes it's the simplest solution: Is your usb cable unplugged when you are trying to turn on USB debugging? It will not let you if you are plugged into a pc or mounted for some other reason. Make sure your file manager and any other rogue app is closed. Again, it does sound like you have tried all of this, just giving my best shot ar an answer.
Other then that... Has anyone else had this problem? I haven't seen it in this forum before.
The most general solution to any issue on these fascinates is to undo whatever you did to break it, it's just difficult sometimes to isolate what that event was.
Swyped w/ XDA App. When in doubt, mumble.

Thanks for the reply.
USB is unplugged when turning on debugging. I've also tried turning the phone on with usb plugged in.
The last thing I had done (before accidently activating the download screen) was to install SiMi Folder Widget. Needless to say, it went away with the rom restore.
Also used ATK to kill running processes before turning on usb debugging. Also verified that I still have root.
I've buggered the phone up before but have always been able to figure out a way back (with help from forum searches). This one's got me stuck.
Tonight I'll try to figure out if it can be odin'd back to stock and rebuild from there.
Again, thanks. All suggestions/advice are appreciated.

See op for steps taken to (unsuccessfully) solve this.
Can anyone advise how I can flash back to stock DI01 without using odin, since it won't detect the phone? I can push files to the phone via adbWireless but that's about it.
thanx in advance...

I dont know if you fixed it or not, but here is a stupid question. Are you using the cable that came with your phone? I have several cables that will only charge my phone and only the stock one enables data transfer. Hope this helps. Good luck
Sent from my SCH-I500 using XDA App

Have you tried a factory data reset?
Sent from my SCH-I500 using XDA App

Did this ever get resolved? I hate to see an open issue die like this.

My apologies for not posting a resolution. My bad. After the first few days the post kind of fell off the radar and I stopped checking.
Short version...dirty usb port.
Details...after a week or so, I saw the usb icon flash in the notification bar for a few seconds when I plugged it in for a recharge. Hadn't seen that in a week, hope springs eternal!
A thorough cleaning of the usb port using a paper swab dampened with alcohol restored usb functionality. Not much dirt came out on the paper, but it must have been enough to probably bridge the contacts somehow.
At present the phone is fully functional. The original Verizon cable seems to be a little wonky. I have an aftermarket cable that works fine. It may be that the aftermarket cable did some physical harm to the contacts in the port, or the original cable is going bad (I had something very similar happen on my Omnia). Not sure.
I now use the original verizon cable only for charging at work and use the aftermarket cable for usb connecting at home.
Bottom line...if your usb goes dead as described in the op, carefully clean the port.
My thanks to all who responded...

This may be my problem! I'm having the same similar effects. Although mine randomly shows the symbol but also says my usb is connected when it does. I've been trying to solve this for 2 weeks now! I hope this is the solution.
Sent from my SCH-I500 using Tapatalk

common problem
This must be a common problem because I've had the same issue. switched cables and viola, all good.

My exact problem solved:
USB debugging activated on phone but computer did not detect it at all, nothing what so ever. Not even on dial-up mode, or download-Odin (yellow triangle).
Drivers installed (Fascinated and Nexus for the hell of it).
Tried to ADB my into it both from windows 7 and MAC OS-X.
Hell I even tried a different USB cord.
I would get the USB debug icon in the status bar only when on windows7 machine.
I cleaned the phones USB port with the alcohol damped paper towel/tooth pick and the **** worked, first time.
Man I gotta thanks God for this site. I been ****ing with for 2 days.
Then this lil SOB acted as if nothing ever happen. I wanted to beat the hell out the lil ****er. But we are back friends now.
Thanks dude. This **** needs publicized more. I went through a few links before I found this.
I would and tell people to use something non-metallic and removed the battery beforehand. I did just to be safe.

I think I cooked my USB functionality.

Hey gang. Wondering if you can help me with a strange issue I've got. I can't seem to connect my phone to my computer via USB. Wondering if anyone could help determine if there's a possibility of repair or not.
==Possibly relevant info==
Samsung Vibrant
Android 2.2 Froyo
Kernel version: 2.6.32.9
Build number: FROYO.UVKB5
==End relevant info==
So, my USB is acting up. Has been for the last few months, where although it charges when I plug into a computer, it's not connecting to allow data transfer. I haven't been too terribly worried, this happened before then cured itself when I did a factory reset. The thing that usually triggered it was when I tried connecting to my linux box in media player mode. The phone would just kinda lock up, I'd have to restart it and then USB wouldn't connect. But after doing the factory reset it was fine the first time. THIS time however, since I'd just left it stock now I'm itching to flash a custom rom but even though I've wiped the whole stupid phone totally clean, it still won't connect. I'm trying to follow a method on an article on dkszone.net called "Bypass E - Signature Verification Fail Issue On Vibrant Android 2.2".
So it seems I need USB for the debug mode.
What I think my main problem is, and where I need some help, is that I had purchased a super cheapwad USB car charger off of amazon for like 35 cents. Every time I connected to it, my phone would ask me if I wanted to connect using kies, media player mode, or data storage mode. I thought it was annoying but didn't really think it would harm anything. But now that I'm thinking about it, it's probably been pumping 5v into each pin on the USB port, whereas the USB functionality uses probably 3.3v, and I'm afraid I cooked something.
The random part here though is that about 5% of the time it does (sortof) connect. It brings up the USB options when I want to connect, brings up the icon saying it's using debug mode, etc. But my machine just reports that it didn't recognize the USB device. So, I'm thinking it's on the fritz, but figured I'd check here to see if I could possibly find a ray of hope.

Scooterx3 said:
So it seems I need USB for the debug mode.
Click to expand...
Click to collapse
You can use ADB over tcpip. There's many a free widget to enable it on google play or Do it manually

Thanks for that, I had been wondering if there wasn't a way to do that over wifi. My issue is that sadly I haven't even rooted the phone. ADB over WiFi requires root, whether I do it manually or use one of those super sweet apps.

So anyways, guess what?
My brother in law has the same phone I do, and I grabbed his phone one day and plugged it into my computers and had the same problem as with my own, and I know he hadn't plugged into the same charger I had, hadn't tried the media mode on Linux like I had (which were what I thought were the big contributing factors). SO, I kept digging, found that I hadn't quite yet cleaned it properly. I'd tried my best to clean it but until I swabbed it well with some rubbing alcohol it wasn't as clean as it should've been.
Long story short, I'm backing everything up so I can start flashing roms.
Moral: just clean the dang thing really well

[Q] Phone won't Turn on?

I am running SACs23 4.3V4.2 rom. I have been having now issues. I plugged my phone in to charge for a couple of hours. Came back and the notification light was blinking for sms. I unplugged the phone and pushed the power button. The screen would not turn on. The notification light died out and now nothing. I have tried booting into recovery, hard reset, and pulling the battery. When I plug the phone back in with or without a battery there is no charging indication. The phone is lifeless. Not sure what to do, I have never seen this. When I plug it into the computer, nothing happens. I can not get into recovery or download mode...the phone does nothing. Any suggestions or ideas?:crying:

The micro USB charging port appears to be not working. You can buy it on Ebay for $10 and replace it yourself. Fairly straightforward.

stupid question but I have to ask, have you tried a different usb cable?

dewrust said:
stupid question but I have to ask, have you tried a different usb cable?
Click to expand...
Click to collapse
Yes. Charging port works fine. 2hrs later, I put the battery back in and it booted. Used my phone for the next 24hrs and then put it on charger. Woke up this morning and same thing. Very odd!

This happens to me when ever I don't use the original charger

Can you get into your recovery? Sacs, has an update to v4.3 in his op that's working very well if you can download it on PC and transfer to your sd card. Dirty flash it and see what happens. My guess is, you are having the same boot lag issues as most others were having and there is a zip file you can flash in Sac's OP for that also for v4.2.
If you can get into your recovery, dirty flash his update.
Your phone, charger port and wire are fine. It's the lag everyone was getting to get the screen to come up.
Sac's is doing one more update so it may be a few minutes before the link is up, but here is the direct link for you..
http://www.androidfilehost.com/?fid=23212708291682600
Until the update is reuploaded, for the heck of it, dirty flash v4.2 and DO NOT select any of the lockscreen effects like lightening or blue orb. The lag has been narrowed down to possibly being that problem.
Lag issue flash file to be flashed in recovery
https://www.dropbox.com/s/gy2d6ajg30utnjd/lag_fix.zip

Try pulling the battery and leaving out for say ten minutes or so

Some clarification:
1. I 've pulled the battery and waited from 10min to 3hours. No change.
2. Plugging into computer and the phone nor computer responds to eachother.
3. I am using the original Sammy charger.
4. This is the 2nd time this has happened but after 24hrs of being off it still will not respond to anything.
5. I took it to Sprint today and they ordered me a replacement phone. They had 3 of their best techs troubleshooting for 2hrs and couldn't find anything wrong with the phone, except for that it doesn't do anything.:crying:
6. I am hoping my new phone doesn't suffer the same fate. I can honestly say this is my 3rd Sammy phone and the 1st time I've had to take it back for anything and I am always flashing new roms from trusted devs.
This one has me puzzeled! Oh, this happened after I updated to MJA software and firmware but no KNOX! So, maybe I am having an issue with the new MJA....sounds like a lot of phones (various carriers) are. I'll update if I learn anything new.

cyiam39 said:
Some clarification:
1. I 've pulled the battery and waited from 10min to 3hours. No change.
2. Plugging into computer and the phone nor computer responds to eachother.
3. I am using the original Sammy charger.
4. This is the 2nd time this has happened but after 24hrs of being off it still will not respond to anything.
5. I took it to Sprint today and they ordered me a replacement phone. They had 3 of their best techs troubleshooting for 2hrs and couldn't find anything wrong with the phone, except for that it doesn't do anything.:crying:
6. I am hoping my new phone doesn't suffer the same fate. I can honestly say this is my 3rd Sammy phone and the 1st time I've had to take it back for anything and I am always flashing new roms from trusted devs.
This one has me puzzeled! Oh, this happened after I updated to MJA software and firmware but no KNOX! So, maybe I am having an issue with the new MJA....sounds like a lot of phones (various carriers) are. I'll update if I learn anything new.
Click to expand...
Click to collapse
Sprint just issued an update today that is suppose to fix this issue. If you can get back to stock take the OTA and see if it helps. You have the sleep of death issue and the mk2 OTA mentions sleep issues as the main fix. Hopefully this is what they are fixing.
Sent from my GT-N5110 using Tapatalk 4

N910F - strange issues with charging

Hello everybody,
- On monday i ran into a strange problem with my N910F. At first it was just not charging whatsoever.
- after the phone ran out of power, i attempted to charge it which gave me a brick with a black screen, vibrating short every two seconds
- Fine by me i thought, went and got a replacement battery (after checking simple stuff like the physical state of the battery (normal) and killing the batterystats (which i heard both yay and nay about so i decided to give it a try).
- Replacement battery charged overnight on the USB Port of my computer (2.0, for the completionists) went smooth (didn't turn it on, just had this bubble animation of charging).
- Turned it on this morning (booting apparently took 3% off my battery) and all well so far.
- finally in my chair at work i plugged it into my power cable (genuine Samsung FastCharging adapter that came with the phone itself) and nothing happened
- tried another adapter (some cheapo 1A adapter) which started charging around 10secs after connecting but decided to stop charging after a couple of minutes
- some shaking and gentle knocking brought back the charging symbol for some seconds, seemed like some loose contact or a broken cable so i felt fancy and plugged the very same cable (the one originally shipped with the phone) to my laptop. started charging instantly and no shaking or knocking stopped this (so no loose contact or broken cable at all)
This is the story until now, put together as complete and organized as possible. For now i'm stuck to charge my phone on the laptop or computer which seems to work. In this progress above i tested around 7 chargers, 3 laptops, 2 computers, 10 cables and 3 screens with both batteries, although the workaround i have now is only tested with the genuine cable as i was just done with testing for the night.
Now for my questions (apart from a touch with the magical fix-everything tool):
- What i see as possible causes based on my very shallow knowledge are either the microUSB port on the phone or the power distribution unit. Anyone has an idea what to check?
- As i have no idea how deep the OS goes, could it be a software issue by any chance?
Even though the device is only ~9 months old, I don't like the idea of going through Samsung for this one as i tripped KNOX already.
Hope there's still hope for me
Cheers,
Fachtal

sooooooo, does nobody have an idea lying around somewhere?

Fachtal said:
Hello everybody,
- On monday i ran into a strange problem with my N910F. At first it was just not charging whatsoever.
- after the phone ran out of power, i attempted to charge it which gave me a brick with a black screen, vibrating short every two seconds
- Fine by me i thought, went and got a replacement battery (after checking simple stuff like the physical state of the battery (normal) and killing the batterystats (which i heard both yay and nay about so i decided to give it a try).
- Replacement battery charged overnight on the USB Port of my computer (2.0, for the completionists) went smooth (didn't turn it on, just had this bubble animation of charging).
- Turned it on this morning (booting apparently took 3% off my battery) and all well so far.
- finally in my chair at work i plugged it into my power cable (genuine Samsung FastCharging adapter that came with the phone itself) and nothing happened
- tried another adapter (some cheapo 1A adapter) which started charging around 10secs after connecting but decided to stop charging after a couple of minutes
- some shaking and gentle knocking brought back the charging symbol for some seconds, seemed like some loose contact or a broken cable so i felt fancy and plugged the very same cable (the one originally shipped with the phone) to my laptop. started charging instantly and no shaking or knocking stopped this (so no loose contact or broken cable at all)
This is the story until now, put together as complete and organized as possible. For now i'm stuck to charge my phone on the laptop or computer which seems to work. In this progress above i tested around 7 chargers, 3 laptops, 2 computers, 10 cables and 3 screens with both batteries, although the workaround i have now is only tested with the genuine cable as i was just done with testing for the night.
Now for my questions (apart from a touch with the magical fix-everything tool):
- What i see as possible causes based on my very shallow knowledge are either the microUSB port on the phone or the power distribution unit. Anyone has an idea what to check?
- As i have no idea how deep the OS goes, could it be a software issue by any chance?
Even though the device is only ~9 months old, I don't like the idea of going through Samsung for this one as i tripped KNOX already.
Hope there's still hope for me
Cheers,
Fachtal
Click to expand...
Click to collapse
You seemed to have tried using the cheap charger which allowed you to charge after shaking it a bit, have you tried purchasing a new genuine charger?
Sent from my trltexx using XDA Premium 4 mobile app

Tripping Knox does not necessarily mean that you've lost warranty.

Battlehero said:
You seemed to have tried using the cheap charger which allowed you to charge after shaking it a bit, have you tried purchasing a new genuine charger?
Sent from my trltexx using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried around 7 adapters (from cheap ones to genuine galaxy S3, Note2, and Note4), around 10 different cables (again, from cheap ones to genuine samsung cables), 3 Laptops (again with all cables), 2 computers (all cables) abd one of those mobile charging battery things.
The only thing that works is either the genuine cable on my computer or the same cables on my screen at work.
@geevh that's news to me. As far as i heard is tripping know equal to losing warranty.

Fachtal said:
I tried around 7 adapters (from cheap ones to genuine galaxy S3, Note2, and Note4), around 10 different cables (again, from cheap ones to genuine samsung cables), 3 Laptops (again with all cables), 2 computers (all cables) abd one of those mobile charging battery things.
The only thing that works is either the genuine cable on my computer or the same cables on my screen at work.
@geevh that's news to me. As far as i heard is tripping know equal to losing warranty.
Click to expand...
Click to collapse
Have you tried to flash stock firmware, in case it's the kernel?
KNOX warranty shouldn't void your warrant in the EU as I have gotten two knox tripped devices repaired from Samsung before.
Sent from my SM-N910F using XDA Premium 4 mobile app

Battlehero said:
Have you tried to flash stock firmware, in case it's the kernel?
KNOX warranty shouldn't void your warrant in the EU as I have gotten two knox tripped devices repaired from Samsung before.
Sent from my SM-N910F using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just flashed the official ROM using Odin. Had some problems getting the phone connected while in DL mode (didn't work at all while in normal android mode).
This seemed to be a dirty flash (already was on stock Rom, just put CWM on, rooted the phone and replaced the kernel to have SELinux permissive for Viper4Droid) as it didn't go through the setup process and was like before.
Anyway, charging still doesn't work. Is there anything else I can test? I'm nearly at the point where I migrate back to my old SGS3 and have the N910F sent to the carrier (well, in the end it will go to Samsung) to get it fixed.
Thanks about the whole Knox false knowledge.
Cheers, Fachtal

Fachtal said:
I just flashed the official ROM using Odin. Had some problems getting the phone connected while in DL mode (didn't work at all while in normal android mode).
This seemed to be a dirty flash (already was on stock Rom, just put CWM on, rooted the phone and replaced the kernel to have SELinux permissive for Viper4Droid) as it didn't go through the setup process and was like before.
Anyway, charging still doesn't work. Is there anything else I can test? I'm nearly at the point where I migrate back to my old SGS3 and have the N910F sent to the carrier (well, in the end it will go to Samsung) to get it fixed.
Thanks about the whole Knox false knowledge.
Cheers, Fachtal
Click to expand...
Click to collapse
I would just give the device in for repairs but make sure to flash a full stock rom and factory reset before giving the phone, since you have already tried everything else.
Good luck

Battlehero said:
I would just give the device in for repairs but make sure to flash a full stock rom and factory reset before giving the phone, since you have already tried everything else.
Good luck
Click to expand...
Click to collapse
Well, flashing stock ROM seems to be slightly less relaxing than I thought. It feels like I have to connect the phone to the pc, put it on the table in a very specific position/way and then hope that it doesn't disconnect halfway through flashing...
This has become quite an adventure so far and I hope I'll get this done so i can get rid of this very expensive paperweight
Thanks for all the help so far, I guess I'll add the explanation from my carrier/Samsung as soon as I (hopefully) get my device back.
Fachtal

PMIC or Charging IC is probably broken on the mainboard, i hear more N4's have this problem.
Best is to send it for warranty or let the components be replaced by a "good" repair shop.
Most service centers don't check knox status so i would go for that, if all fails take it for repairs if the costs are not too high.

Hi guys, back for a rather unexpected "solution"
When i finally freed up some time to actually get to the carrier shop to get my phone fixed, I was in for a rather embarrasing experience.
The lady in the shop pulled a charging cable and an adapter out of a box, plugged my phone in and it suddenly charged as if nothing ever happened. Now, some time later, it still works perfectly fine, as if there never were problems...
I have absolutely no idea on what happened. Before going to the shop i obviously flashed the stock rom yet again (with the usual wipe user data/cache/dalvik procedure).
Now, on what i had when the problems started: stock BOC5 ROM, touch CWM, rooted and with a custom kernel for SEAndroid permissive (emotion something i believe the kernel was called). Now during my rather extensive troubleshooting I actually flashed the stock ROM at least once and the issue persisted, which is why i just stood there, staring on my charging phone, my jaw somewhere on its way to the ground, unable to form any proper words :silly:
So basically, does someone have a possible explanation to clear this up? If not, I'll consider this thread solved i guess^^
In the meantime, I downgraded to Stock 4.4.4 with CWM, root and xposed (which i really missed on Lolli) and I'd say I'm happy with this :victory:
Fachtal

Fachtal said:
Hi guys, back for a rather unexpected "solution"
When i finally freed up some time to actually get to the carrier shop to get my phone fixed, I was in for a rather embarrasing experience.
The lady in the shop pulled a charging cable and an adapter out of a box, plugged my phone in and it suddenly charged as if nothing ever happened. Now, some time later, it still works perfectly fine, as if there never were problems...
I have absolutely no idea on what happened. Before going to the shop i obviously flashed the stock rom yet again (with the usual wipe user data/cache/dalvik procedure).
Now, on what i had when the problems started: stock BOC5 ROM, touch CWM, rooted and with a custom kernel for SEAndroid permissive (emotion something i believe the kernel was called). Now during my rather extensive troubleshooting I actually flashed the stock ROM at least once and the issue persisted, which is why i just stood there, staring on my charging phone, my jaw somewhere on its way to the ground, unable to form any proper words :silly:
So basically, does someone have a possible explanation to clear this up? If not, I'll consider this thread solved i guess^^
In the meantime, I downgraded to Stock 4.4.4 with CWM, root and xposed (which i really missed on Lolli) and I'd say I'm happy with this :victory:
Fachtal
Click to expand...
Click to collapse
It's sound strange but a couple of years ago i read somewhere,forgotten where and about the specific device. The thing was that phone wasn't charging eather ,and now it comes.....the solution was turnig around the charger in te power socket.

ludoke said:
It's sound strange but a couple of years ago i read somewhere,forgotten where and about the specific device. The thing was that phone wasn't charging eather ,and now it comes.....the solution was turnig around the charger in te power socket.
Click to expand...
Click to collapse
this indeed sounds strange. And honestly, i didn't pay attention on the orientation of the power adapter (although my stock samsung one is always in the same orientation because the cable goes out on the side (which means it worked in the same direction as it didn't before).
The only even remotely considerable approach would be that the custom kernel along with this synapse app somehow screwed with the power intake and i forgot to wipe everything when i first flashed stock over it, meaning that synapse still had its fingers in the system screwing around with that.
But then again, as I seem to be the only one with this problem and this custom kernel had more than just a few users I don't think this is the way it went (I don't even use an unusual collection of root Apps which could cause some sort of malfunctioning combination of effects).
I had a few evenings just thinking about this and draw some simple mindmaps/schematics to make some sort of a sense...