After updating to official cm 12.1 my phone is charging very slowly. What to do to resolve this?
harshrajsingh44 said:
After updating to official cm 12.1 my phone is charging very slowly. What to do to resolve this?
Click to expand...
Click to collapse
I'm using Cyanogen 12.1 and I'm not facing any such issues..
Make sure you are using the charger that came with the phone (1500 mA or 1.5 Amp).
Related
Anyone else having wifi issues with using CM10 nightlies? just a question i understand that these are nightly builds and mostly broken but just askin?
calcdsatr1 said:
Anyone else having wifi issues with using CM10 nightlies? just a question i understand that these are nightly builds and mostly broken but just askin?
Click to expand...
Click to collapse
Mostly seems to be after the Oct 24 build, anybody got any good CM10 roms sugestions?
Just as an update all wifi issues seem to be resovled with newest nightlies. As far as i can tell
calcdsatr1 said:
Just as an update all wifi issues seem to be resovled with newest nightlies. As far as i can tell
Click to expand...
Click to collapse
From what I understood, they were resolved. But to make sure, turn the sleep mode off on the WiFi.
calcdsatr1 said:
Mostly seems to be after the Oct 24 build, anybody got any good CM10 roms sugestions?
Click to expand...
Click to collapse
The Nov 5th Nightly was awesome for performancebut the wifi was a bit weak... and still is ( 24-Nov nightly)
also tried RaymanFX Elite Kernel to see if that would fix the WiFi problem.... got no WiFi at all now!!
Dragonspirit 78 said:
The Nov 5th Nightly was awesome for performancebut the wifi was a bit weak... and still is ( 24-Nov nightly)
also tried RaymanFX Elite Kernel to see if that would fix the WiFi problem.... got no WiFi at all now!!
Click to expand...
Click to collapse
Damn, that sucks...I'm on the November 21st and it works fine for me. I am tethered to my Motorola Droid 4 with no issues.
Flash katkernel lid patch, flawless wifi for me
Sent from my Transformer using xda app-developers app
To be honest I've given up on cm. I'm using teameos' ROM. It's way more stable overall.
Sent from my Galaxy Nexus using Tapatalk 2
In my ace plus i have cm10.1 and my ace plus is now not showing battery stats (% of charging). How can I solve it? (dont tell me to reflash cm10.1)
Which CM are you using thewhisp's or techkang's?
If using thewhisp's try to switch to techkang's as it is latest CM10.1.3.
If using techkang's try to ask in his thread.
MegaBoyX9 said:
Which CM are you using thewhisp's or techkang's?
If using thewhisp's try to switch to techkang's as it is latest CM10.1.3.
If using techkang's try to ask in his thread.
Click to expand...
Click to collapse
I am using the Whisps' Cm bcoz camera is working in it ...Well thanks for suggestion :good:
This assembly CM 10.1 DyrtyDev? On rom CM TEchKang almost gone bugs.
Vergilliy said:
This assembly CM 10.1 DyrtyDev? On rom CM TEchKang almost gone bugs.
Click to expand...
Click to collapse
there are sam issues in techkang's rom
what interests?
hello everybody! i 've got this problem on my rzr hd with cm11. when i plug the hdmi on tv my phone turns to landscape and the tv got signal but with black screen, on stock firmware works fine. this happening someone? any solution?
tanks for yours answers.
sorry for my english
I have the same issue with HDMI and CM11
The HDMI code is proprietary code owned by Motorola. They have not released the source for it, so CM11 HDMI will not work. Any ROM that is AOSP-based will not work as they are compiled straight from the AOSP source which does not have the HDMI code. Again, the HDMI code is owned by Motorola and they have not and will not release the source since it's not open-source code.
I have an XT925 on cm11 (M5) and HDMI is working without any issues.
Have you actually tried HDMI recently on stock firmware? Perhaps is the actual port that got screwed (been there).
kernelmoron said:
I have an XT925 on cm11 (M5) and HDMI is working without any issues.
Have you actually tried HDMI recently on stock firmware? Perhaps is the actual port that got screwed (been there).
Click to expand...
Click to collapse
I remember testing the HDMI when I first flash CM11 and it was working, but now it doesn't work anymore... maybe it's an issue triggered in some point between M5 and M6 (I'm currently running M6)
I have an xt926 that runs on the Liquidsmooth ROM (AOSP-based, KitKat version) and have no problems with HDMI. It worked on the Jelly Bean version of Liquidsmooth as well.
pbosio said:
I remember testing the HDMI when I first flash CM11 and it was working, but now it doesn't work anymore... maybe it's an issue triggered in some point between M5 and M6 (I'm currently running M6)
Click to expand...
Click to collapse
I don't remember if It ever worked on cm base, but I'll try if it works on cm10.2
it now works on the latest cm11 with the 3.4 kernel so when that comes to official it will work for every one :laugh:
billycar11 said:
it now works on the latest cm11 with the 3.4 kernel so when that comes to official it will work for every one :laugh:
Click to expand...
Click to collapse
but for install cm11 with 3.4 kernel needs kitkat base y compatible recovery right?
frannq said:
but for install cm11 with 3.4 kernel needs kitkat base y compatible recovery right?
Click to expand...
Click to collapse
yes
billycar11 said:
yes
Click to expand...
Click to collapse
So, i have to wait to try
Hi, I can't seem to play SimCity Buildit on my Tab 2 7.0 because it always FC's while loading. Even after the new update, its still happening and it works fine on my Nexus 5. Anyone else having the same problem?
Which rom are you using.
I believe I'm using OmniRom, not sure what build though.
Riqitch said:
I believe I'm using OmniRom, not sure what build though.
Click to expand...
Click to collapse
What android version are you on?
Try updating to Omni 5.1 If you are on Omni 5.0
Hassan 4 said:
What android version are you on?
Try updating to Omni 5.1 If you are on Omni 5.0
Click to expand...
Click to collapse
I updated to the new version at it worked... for a while until it FC'ed one day. I am currently trying to fix it by wiping the cache, reboots and maybe considering re flashing again.
I recently installed the latest (Oct 17) Blisspop. I had a problem with the tablet not being recognized by my computer so I searched for a solution and finally after a few days flashed the Bit-O K2-005 kernel which didn't help.
Next, I flashed the DTB file which also didn't help, but it's then that I noticed a significant battery drain on idle. Since only a few hours passed between flashing the K2 kernel and the DTB file I'm not sure when the battery drain started to manifest.
Finally, I flashed the KX-060 kernel and now my tablet gets recognized by my PC and it correctly shows that it is charging while connected, but the battery problem persists.
Anyone had a similar experience and came up with a solution?
Sent from my shieldtablet using Tapatalk
Blisspop update night test cases for your tablet
I downloaded a version of 5 November - it works well! Connecting to a computer works and the sound is not distorted! http://click.xda-developers.com/api... | Nvidia Shield Tablet | XDA Forums&txt=here
That's great to hear, thanks! No problems with battery life?
Sent from my shieldtablet using Tapatalk
3ranis said:
That's great to hear, thanks! No problems with battery life?
Sent from my shieldtablet using Tapatalk
Click to expand...
Click to collapse
Good, battery holds a charge well as to the stock room!
Excellent news! Thanks for the info.
Sent from my shieldtablet using Tapatalk
3ranis said:
Excellent news! Thanks for the info.
Sent from my shieldtablet using Tapatalk
Click to expand...
Click to collapse
Checked gamepad work today - is not connected !!! Everything else works ...
I think it's the Bit-O kernel, I get massive drain on cm 12.1 after flashing it, stock kernel that is supplied is much more battery efficient.
I finally flashed the nightly build yesterday. No more battery drain. I now lose only 1% overnight compared to more than 30% I used to lose with the Oct 17 build.
Sent from my shieldtablet using Tapatalk
Bit-0