Hi,
I have a samsung galaxy express i8730 with cyanogenmod 11 (4.4.4).
Does cyanogenmod work with android wear?
Sebastiaan
sebastiaann said:
Hi,
I have a samsung galaxy express i8730 with cyanogenmod 11 (4.4.4).
Does cyanogenmod work with android wear?
Sebastiaan
Click to expand...
Click to collapse
So far i know it works
Sent from my LG-D855 using XDA Free mobile app
I have an S4, and I haven't gotten mine to work on CM 11. I mean it does, but not very well. Gonna switch to a TW rom tonight.
S4 running CM11 and no issues with my LG g watch. Everything comes through with no disconnects.
Sent from my GT-I9505 using XDA Free mobile app
sebastiaann said:
Hi,
I have a samsung galaxy express i8730 with cyanogenmod 11 (4.4.4).
Does cyanogenmod work with android wear?
Sebastiaan
Click to expand...
Click to collapse
I'm using CM 11 (4.4.4) on a S4 with Android Wear. No issues that I can see so far.
On Nexus 5, anything other than stock doesn't work well. Watch disconnects too often to be usable (bluetooth stack is dodgy on aosp or CM).
The fix is to flash Elemental kernel. Problem solved. This kernel is available for both aosp and CM.
Even in stock rom, if you flash another kernel, like franco kernel, the watch becomes unusable.
Again, the fix is to flash Elemental, with gives you the added bonus of enabling screen calibration for nice poping colors.
It took me time to discover all this. And frustration.
lost network connection
Hello I installed cm 10.2 through flash recovery. Onti my galaxy ace 2GT I8160 was gingerbread 2.3.6
Now its team conja jls361 if ive looked in the rite plce i still have iemi number and can recieve messages
But when i try and send or call it say no network ive been on to 3 my provider and they say its the phone
Please could you help with thi ive read it happens alot with this release of cm.. Would installing cm 11 sort it out im a newbie to being root ive already soft bricked it once so can see it being a bumpy ride so all the help i can get the better thank you
Also I looked at the build list and the radio and boitloader are unknown the biitloader has been like that when i got the phine that's bootloader not biitloader or bout loader dam key pad lol
My kernal is a i8160xxlk8 or it was I dunno if it still is
Connecting, running sync loop
Latoc said:
On Nexus 5, anything other than stock doesn't work well. Watch disconnects too often to be usable (bluetooth stack is dodgy on aosp or CM).
The fix is to flash Elemental kernel. Problem solved. This kernel is available for both aosp and CM.
Even in stock rom, if you flash another kernel, like franco kernel, the watch becomes unusable.
Again, the fix is to flash Elemental, with gives you the added bonus of enabling screen calibration for nice poping colors.
It took me time to discover all this. And frustration.
Click to expand...
Click to collapse
Any ideas for running CM on the galaxy s3? Android wear will not switch to connected, shows, "connecting, running sync loop". Most functions work OK but the watch is dying terribly quick. I know the moto 360 battery is supposed to be iffy, but I should get more than 4-5 hours....
Garrett 77 said:
Any ideas for running CM on the galaxy s3? Android wear will not switch to connected, shows, "connecting, running sync loop". Most functions work OK but the watch is dying terribly quick. I know the moto 360 battery is supposed to be iffy, but I should get more than 4-5 hours....
Click to expand...
Click to collapse
I don't know about s3, but you should try a few kernels and see what works...
FIXED
Latoc said:
I don't know about s3, but you should try a few kernels and see what works...
Click to expand...
Click to collapse
Well,
I tried a different kernel and still same issue. I flashed a TouchWiz based rom and it WORKED. Shows "connected". Battery life on moto 360 also vastly improved. Went from dead at 3:30 PM to 45% at same time!
I'm on DarkCM(11) for the xperia z1 and can't get it to work either.
Tested on my brothers stock xperia and that worked just fine. Il try downgrading to stock as well. :'(
If anyone gets CM on the z1 running with android wear please let me know.
I have a Oneplus One CM 11S works great on my old Gear Live and my new Sony Smartwatch 3
I read that MOTO 360 has (had) issues ?? Maybe the watch not the phones OS
Hi. My first post here and very New to all this. I have Samsung S4 with cm11 just got an Samsung galaxy gear2 neo and now i have to figure out how to get it to work with cm11 ? Can some body help
TechieInAK said:
I'm using CM 11 (4.4.4) on a S4 with Android Wear. No issues that I can see so far.
Click to expand...
Click to collapse
Sorry for bringing up an old post. I wanted to check in on your Android Wear connection to CM ROMs. I have a Sprint S4 (jfltespr) running CM12. I will be getting a LG G Watch R in a few days but someone else on our ROM thread was having issues with his Moto 360 and the CM12 ROM. Have you experienced any issues not connection or remaining in a sync loop?
Has anyone else experienced Android Wear issues with CM 11 or CM 12 on S4 phones? Particularly jfltespr?
Cant speak for the S4 but my LG G3 has had nothing but issues with my G Watch R since I flashed CM12. I reverted back to CM11 (recent build) and its working great, never disconnects. With CM12 it would disconnect at least 10-20 times a day its unusable.
I just installed the Google Play Edition Lollipop on my GS4 and it paired perfectly with my ASUS ZenWatch. Lollipop AOSP is AMAZING and i am so stoked it works so great!
Garrett 77 said:
Any ideas for running CM on the galaxy s3? Android wear will not switch to connected, shows, "connecting, running sync loop". Most functions work OK but the watch is dying terribly quick. I know the moto 360 battery is supposed to be iffy, but I should get more than 4-5 hours....
Click to expand...
Click to collapse
"Connecting, running sync loop" is just a different message for the same thing - it is activated on some ROMs(?) apparently when you have Developer mode enabled. But it works the same, and this message in itself doesn't indicate there should be any battery drain.
Of course something in the ROM might be causing this problem - a logcat from the watch would help in that case, but my guess is you just need to let everything install, settle down and then reboot both devices, and the drain will be gone...
My Zenwatch works perfectly with my Oneplus One running the latest CM11S. Having bluetooth on all the time does drain a bit more battery, but that's it.
I am having an issue with google wear (zenwatch) completing some tasks:
It fails to launch a phone call from google wear (my watch simply says "try again using your phone")
It fails to launch google play for music (it gives the same error as above)
Setting reminders using google keep (same error)
Text messages sent from android wear are NOT working.
Starting navigation on my watch using voice commands works.
Other basic apps appear to be working as well.
So far I've only noticed the above listed (maybe a few others) google apps and dialer that fail to launch when initiated from the watch, I have tried another dialer to see if that was the issue.
Anyone have any suggestions or insight on what I might be able to do in order to get google wear working 100% with this ROM?
Any help is greatly appreciated.
Mine works well
I have OnePlus One with CM11 and everything works quite well so far with my G Watch R
Related
Everything was perfect when i was on Android 4.3, any skype calls working, video/audio doesn't matter.
But when i updated my wife's phone to kitkat, some skype calls making phone reboot(black screen, then its loading as usual).
It happens not always. And i have noticed that it crashes only while talking to people who have Windows XP installed(with latest version of skype, checked & updated myself).
When she talks to anyone on 7&8 Windows - everything is perfect.
I have tried all custom roms, original, rooted\not rooted, anything.
I gonna write this issue to Skype too.
Skype support asked that Skype not supporting KitKat yet.
Btw it only happens on Nexus 4, when i'm on my phone (XT910) on KitKat, it works and not hangs.
In my case occurs the same...I believe is maybe kit Kat by itself and usually happens when I leave a call in the background while I use another application. Unfortunately I haven't found any solution for that.
i have noticed that it crashes only while talking to people who have Windows XP installed(with latest version of skype, checked & updated myself).
Click to expand...
Click to collapse
Not really. The problem is a bit more serious: all ROMs (stock and custom) based on 4.3 or 4.4 are affected by this overly annoying camera bug. I obviously hope you're not, but if you end up as unlucky as I did, your camera and LED flash will soon become totally unusable (on all applications), fixable only by reverting to 4.2 or updating to L (I did and it's totally worth it)
Good luck :good:
Also another issue with Skype and N4 is that whrn listening to music and an image is being sent / received in the Skype chat window, fetching that image from the gallery/disk causes the audio system to crash. It's really annoying. Probably it's the same issue as the well-known audio stutters on changing connectivity and high cpu load.
Im using the Verizon G2 and running 4.4 2...xdabebb rom..i use skype a lot for business calls and havent come across this issue at all. On unrooted stock as well as custom. Ive also faced no issues on an S4 i9500...so it might not really be a kit kat issue but a nexus 4 specific...or an aosp based rom specific issue
Sent from my VS980 4G using Tapatalk
I have another kind of issue with my xiaomi Mi2 with MIUI Rom on kitkat 4.4.4. I have systematically a black screen when the communication is established on Skype also using test sound server. The sound is working but I can't do nothing with the phone until the end of communication decided by my correspondant.. Very annoying . I have post the question to Skype 5 days ago but no answer. Skype was working properly on my phone on miuiv5 android 4.1.2
Envoyé depuis mon Mi2 kitkat 4.4.4 Miui6
I'm having the exact same problem ... I was talking on Skype video call and the phone screen went black and I couldn't hear the other party.. I don't if they were able to hear me or not. I had to hold the power button and reboot my phone manually. I don't know what the problem is but its very annoying and it happened three times in a row. I have used multiple ROMs and it was happening on all of them and they were all 4.4.4. I don't flash kernels, I just use the kernels that come with ROM because they have obviously been tested and have been found compatible with the rom. So I know its not because of kernels. Currently I'm on Slimkat latest weekly and was thinking about going back to stock but someone said its also happening on stock ROM. I'm going to try CM11 and see if it happens there as well. Will report back soon. Hopefully it's just a 4.4.4 issue and not a phone issue.
Sent from my Nexus 4 using XDA Free mobile app
Hey All, no offense on the vast feature set of Cyanogen OS, but, I would love to have stock Google Android, preferably 5.1 on my Yureka.
I tried to find the port on net, but for no luck. Please share if someone have a clue on the Stock Google Android port for Yureka.
I agree!
maesiva said:
Hey All, no offense on the vast feature set of Cyanogen OS, but, I would love to have stock Google Android, preferably 5.1 on my Yureka.
I tried to find the port on net, but for no luck. Please share if someone have a clue on the Stock Google Android port for Yureka.
Click to expand...
Click to collapse
CM12.1 has been one long nightmare. The Camera App freezes, Blackout and wallpaper change/theme change, One App Redraw over another causes sudden screen blackout, Spontaneous Black Screen, Boot-time that takes well over 2 minutes, Black Screen doesn't let me receive calls most of the time(and its got NOTHING to do with the proximity sensor believe me! The new update is just whacky!!). I've seen around and found out that this is not an isolated case with me. Infact, there are many suffering from the same. I've been enduring for long, in hopes that a new update will come around but at this point I think I want stock android too.
So i finally gave cm 12.1 a chance because it's been rolling for a while now... and i was actually pretty impressed. The one issue i couldn't deal with is the bluetooth audio playback in my car. Basically it was playing too fast, then pausing every 10-20 seconds and then continuing to play too fast again (also at a slightly higher pitch). I was able to temporarily fix the problem by turning bluetooth off and on but it came back. other than this i didn't see many issues and thought it was pretty good, but for no i'm going to go back to stock until this issue is fixed, i did find that it was already reported to the cyanogenmod team and they are already working on a fix so i'm waiting impatiently until it's fixed and i'll probably be moving from stock kitkat as my main rom to cm 12.1. How has everyone elses experience been with cm 12.1 nightlies so far?
What doesn't work. (if i missed something here post so i can update)
- saving 4k video (1080p works tho)
Battery life ?
- used to be terrible but it's almost as good as stock now but with better performance.
hey
i would like to use CM as i was doing that on my Moto G. the questions I have to users of the newest CM version:
- does quickcircle, google text-to-speech, intelligent screen (LG app) features work?
- what is the quality of videos and pictures taken by the phone running CM opposite to android v20i?
thank you.
Brtnsk said:
hey
i would like to use CM as i was doing that on my Moto G. the questions I have to users of the newest CM version:
- does quickcircle, google text-to-speech, intelligent screen (LG app) features work?
- what is the quality of videos and pictures taken by the phone running CM opposite to android v20i?
thank you.
Click to expand...
Click to collapse
1. Quickcircle won't work. To make it work again you have to install a special app. Google text-to-speech works ok for me (I haven't test it too much). LG features/apps won't work
2.For me the quality of pics and videos are the worst I have ever seen!!!! (Much better in the stock LG)
My experience with CM12.1 was average. I was waiting for something better. Camera is awful in the Custom roms. Battery life wasn't the best. In terms of performance the cm12.1 is better than the stock lg.
i've only been running cm 12.1 for a few days now so i don't have alot of substantive input, i did find a fix for the bad bluetooth car audio using a macro/tasker app but i think they have fixed it in the nightly released today, i'm downloading it now it says bluetooth stream parameters in the patch notes so i wont bother sharing my fix until i try this nightly to see if they already fixed it. i'll give a better review of whats working and the camera/video quality after i have a chance to play around with it more.
by the way anything running ART instead of DALVIK cache/runtime is going to perform better but it's at the price of xposed modules and such, i'm not expert on it but i know they switched to ART cache/runtime to be more competitive with the iphone. On Kitkat and lower an android device needs better hardware to output the same performance as an iphone with lesser hardware. ART should fix that problem. If you are curious google ART vs DALVIK
*edit* yeah bluetooth is fixed with the newest nightly update... atleast for my car which is a mazda 3. (yay)
Avrage camera and bugs like video not saving after recording is main culpit to not use CM 12.1. Otherwise it is good as clean android can be.
it's getting alot better every day now
netmaniack said:
Avrage camera and bugs like video not saving after recording is main culpit to not use CM 12.1. Otherwise it is good as clean android can be.
Click to expand...
Click to collapse
Videos do save. It is a issue with 4K video ONLY. Switch to 1080p video and videos save just fine.
c_brown93 said:
Videos do save. It is a issue with 4K video ONLY. Switch to 1080p video and videos save just fine.
Click to expand...
Click to collapse
I found that myselfe, tnx. But I believe that issue is fixed already. Maybe Im wrong, but I did see in changelog or other forum. Maybe someone can test it?
I switched to stock kitkat, I love CM, been running CM since it was 10.1, the problem is that it starts really really fast and after a while CM 12.1 becomes laggy it drives me crazy, other than that is the camera quality which doesn't bothers me as the performance issue,
I guess we'll need to wait for LG to release the G3 source file but who know's when that's gonna happend
good news the latest daily added some balancing between power and battery life. I went from losing a huge chunk of my battery during work when my phone is in my pocket to going 9.5 hours at work and coming home with 94% battery. (that is alot of standby but i use my phone at lunch and have bluetooth running for about 50 minutes of driving). Basically it got alot better, i'm not sure what they did but i did notice that there is a balanced setting in battery screen that i didn't notice before. Anyways I think those who were concerned about battery drain my have had their wishes answered over the last few nightlies.
netmaniack said:
I found that myselfe, tnx. But I believe that issue is fixed already. Maybe Im wrong, but I did see in changelog or other forum. Maybe someone can test it?
Click to expand...
Click to collapse
i still can't get 4k video to save but 1080p did.
Do knock on and knock code work?
Lucenzo7 said:
Do knock on and knock code work?
Click to expand...
Click to collapse
Knock on works but knock code doesn't, which is quite normal considered it's an LG feature.
Lucenzo7 said:
Do knock on and knock code work?
Click to expand...
Click to collapse
Partly working. You can turn screen on by clicking anywhere, and turn it off by knocking at notification bar.
Phone encryption not working?
I've just flashed the 20150603 CM12.1 and I cannot seem to get the phone encrypted. On the reboot to start the encryption, the phone gets stuck in the CM boot animation and the encryption process never starts. Any ideas or suggestions? Many thanks in advance.
I'm on 06/05 nigthly. When I plug the phone in my computer, it's not being recognized. If I change from MTP to PTP, then it works.
I've tried going to Device Manager, and could see that my phone is being recognized as a Nexus device. I tried installing latest drivers from Google's website, but I got a message saying that I'm already on the latest version. So that didn't do anything. I've tried uninstalling that "nexus" driver and rebooting my PC, but it somehow came back when I plugged my phone in. Trying to update gave me the same message.
If I run "adb devices", I can see that there's no devices (it's enabled in developer settings). If I enable ADB over WiFi and try to connect -- it works, and I can do whatever I want. But only over WiFi and not via USB.
Tried different cable and different port as well.
Okay so I'm gonna describe my problem as clearly as possible and will hope someone can find a fix for this.
Device: Nexus 6P
OS: Android 6.0.1 (latest vendor & security patch - June 2016)
Bluetooth devices used: Sony MDR 600BT, SOL republic tracks air, jbl synchros earphones, jbl flip 2 speaker.
1) pair earphones/speakers
2) start playing music on earphones/speakers
3) works fine on first run and when screen is off
4) when I switch on my screen to change the song the music stutters for 10 full seconds, then stuttering stops.
5) I change the song and again put screen off, works fine.
6) i put my phone in my pocket and suddenly my phone audio stops skipping??? Wtf???
7) so I change my pocket and put it in my hoodie pocket. (Nearer to earphones - maybe distance is the problem I thought)
8) audio still skips............:crying:
9) put my screen on to change song, audio starts stuttering again like crazy and then stops.
10) I request anyone here to heed this request and tell me how to workaround this problem
Currently running latest android MM 6.0.1 and no improvement .....:crying:
I don't understand one thing - top of the line flagship device and still these problems? Not getting value for my hard earned money. This is wrong.
I tried it with my iPod and it works like a charm. No stutters. No skips. Nothing.
Tried different Bluetooth headphones too in case my Sony earphones were the problem. NO IMPROVEMENT SAME PROBLEM PERSISTS.
TRIED USING IT ON ANY BLUETOOTH SPEAKER THE ABOVE THINGS KEEP HAPPENING AND I AM GETTING REALLY ANNOYED WITH THIS PHONE WHEN IT COMES TO BLUETOOTH.
I'm sorry for agonizing so much. But I hope you'll can understand my problem. And hopefully there's a fix somewhere in the world.
I am having the same issue, and my searches came up with this:
http://forum.xda-developers.com/nexus-6p/help/bluetooth-audio-stutter-wake-unlock-t3384324
Is this a Play Music issue? I don't have these issues, but I don't use Play Music. usually stream through YouTube or something like that instead. Works on BT Headset and Sony BT head unit in my car.
blackwrx02 said:
Is this a Play Music issue? I don't have these issues, but I don't use Play Music. usually stream through YouTube or something like that instead. Works on BT Headset and Sony BT head unit in my car.
Click to expand...
Click to collapse
I can't speak for Zapjack12345, but I notice it with PowerAmp, Pandora, Spotify, YouTube, basically any app that is pushing audio through bluetooth. Audio is fine when the screen is off, but as soon as I pick up the phone, and turn it on to check notifications, things get screwy with the audio
Strange. I just checked with Pandora, YouTube, and IheartRadio and all seem fine with screen off and turning it on, using the pulldown menu, or changing songs. I'm using a cheap set of bluetooth earbuds from Amazon (no-name brand), and am stock with the phone, not rooted (yet) and on June updates. Phone was purchased in May new from Best Buy.
Same issue for me as well. I'm specifically using Amazon and Pandora most of the time. Its very annoying. On Chroma and franco kernel.
What rom are you using? This has been a well documented CM rom issue so any rom that uses CM as a base will and has had this issue since mid-January. Stock and AOSP based roms dont have this issue (from what I've seen and tried).
I'm currently using the 6/15 nightly for OMNIrom and do not have these issues.
As a sidenote, this was also an issue with Android N Dev Preview 2.
uodii said:
What rom are you using? This has been a well documented CM rom issue so any rom that uses CM as a base will and has had this issue since mid-January. Stock and AOSP based roms dont have this issue (from what I've seen and tried).
I'm currently using the 6/15 nightly for OMNIrom and do not have these issues.
As a sidenote, this was also an issue with Android N Dev Preview 2.
Click to expand...
Click to collapse
I'm currently on Pure Nexus 5/6/16. Nothing out of the ordinary installed. Tried clearing the Bluetooth cache, as the issue I am noticing was similar to issues that the Samsung S5 was having, but there was no difference.
I am going to look to go back to stock and see what happens, but looking at what OP posted, it looks like they're on stock, and having the same issue.
I am about to throw my phone in the sea. BT seems like it's getting worse and worse with each update. Cmon Google/Huawei. Don't make me lose faith.
Sent from my Nexus 6P using Tapatalk
krakerx said:
I am having the same issue, and my searches came up with this:
http://forum.xda-developers.com/nexus-6p/help/bluetooth-audio-stutter-wake-unlock-t3384324
Click to expand...
Click to collapse
I had a little less issues when using the Dev Preview 3 but there was another issue that arised that I hope gets fixed.
If you're using bluetooth when driving around when you lose signal or drop/gain data connection the audio skips for a quick second. Through past testing I've done working with kernel devs on 2 phones, the issue is related to how the hotplugging works for the cores. If only one core is running when the connection drops there is an issue with how the cpu ramps up and/or turns on another core to handle the workload. I thought this regression was pretty interesting seeing as one the things they were boasting about at the Google conference was how android would fix slow downs and issues when losing/gaining network connectivity with N. Hopefully it'll be fixed before final release.
akarol said:
I am about to throw my phone in the sea. BT seems like it's getting worse and worse with each update. Cmon Google/Huawei. Don't make me lose faith.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
You and me both. I am on my 3rd 6P and my BT problems are still the same. If the BT problems were only effecting one particular device I could understand but my Microsoft band, BT earbuds and car all seem to disconnect continuously on a bare/stock phone.
Okay guys. I changed my ROM from Resurrection Remix to Paranoid Android and this issue has been solved. Thank you so much for all your help and answers!
Does anyone else have any updates regarding this issue? Literally wanted to throw my phone out of the window during the morning commute.
Zapjack12345 said:
Okay guys. I changed my ROM from Resurrection Remix to Paranoid Android and this issue has been solved. Thank you so much for all your help and answers!
Click to expand...
Click to collapse
Don't use cm based roms
Smallsmx3 said:
Don't use cm based roms
Click to expand...
Click to collapse
Yep, this is 100% the reason. It is a CM issue. AOSP roms like Paranoid Android and Pure Nexus don't have this issue. I love Resurrection Remix, but this is starting to bug me. I may jump to PA rom soon...
Smallsmx3 said:
Don't use cm based roms
Click to expand...
Click to collapse
Thanks. Was about to ask this question. It is a CM issue.
I have had issues with BT dropping randomly in my car on 2 different 6P's. No rhyme or reason, and it doesn't happen often, but annoying when it does. Happened on MM and DP4 currently.
On the flip side, my audio quality went down on my S7E over BT when my smartwatch was connected. Somehow, that doesn't happen with the 6P meaning I can keep my watch on in the car, so I am happy.
Hey, I just found this thread and surprised it took me this long considering I've been having this issue since I got my phone in November.
My 64gb 6P was stock until earlier this week, when I finally rooted and flashed xposed. The issue stopped the day I rooted my phone, and I was thrilled.
After reinstalling most of my apps and getting back into my routine, the problem came back. I've tried booting my phone into safe mode several times before rooting so I'm fairly confident the issue doesn't exist because of a specific app interaction, but I can't figure out what it is to save my life. I might backup again and restore to the backup I made right after rooting to see if I can narrow down the problem.
Other than that, I am very new to this stuff and honestly just thrilled to have found other people having the same issue.
I only experience the problem while connected to my car (2015 Chevy Cruze), and not any other bluetooth device.
Let me know if you guys find/have found anything I suppose?
I kinda have up on trying to narrow down the issue. I tried PureNexus, Paranoid Android, I tried different kernels, different cases. Still kept skipping and jumping, no matter how far, or close it was to my Bluetooth device (car stereo, speakers, home audio system). I went back to stock, no root, no Xposed, pure and simple Android, and I have not had a single issue, it's beautiful.
I really still enjoy using this table and LineageOS 14.1 breathed new life into it from the stock Andriod ROM of KitKat. If not does anyone suggest anything other than LineageOS to run on my tablet that would perform any better than LineageOS.
Thanks,
Lime
Hmm nobody has any thoughts?
Resurrection Remix is a very good and stable ROM. But you leave curious...
What is lacking in Lineage that leaves you wanting?
wellersl said:
Resurrection Remix is a very good and stable ROM. But you leave curious...
What is lacking in Lineage that leaves you wanting?
Click to expand...
Click to collapse
It looks like they may not be going forward with any new releases of lineageos for the SM-T520.
LOS14 Issues
I have 3 issues with LOS14 on my SM-T520 wifi which I didn't have with a former CM Rom:
- I like to hold my Tab in different orientations and android rotates the screen likewhise. But the unlock-screen is not rotated and allways shows same orientation no matter how i hold the tab.
- I play some games on my tab with ad videos. In some games those videos are played in full volume for a fraction of a second even though my volume is low or off. This makes an irritating noise whenever one of the video starts.
- In some games android seems to overload the cpu regularly for some milliseconds and the game hangs (graphic and sound) but only when the tab had been running for a longer time. When I then restart the tab everything works fine.
I had a CM on my tab before and I didn`t have any of these issues there. But CM is no longer supported or updated so I switched to LOS14. Appart from these issues LOS14 runs very good on the SM-T520. But like limeman35 said there seem no progress in developement. At least there are nightly builds from time to time with service releases from android.
I am a newbie when it comes to rooting. I've never tried it but I have a Samsung t525 an I check all the time for system updates for this tablet but there never have one. I've even called into Samson an they told me you cant download any updates at all. That is hard for me to ac Sept. There has to be something I can to to utilise my tablet. Will you please explain how to root my tablet? Ty Pawneehappygamer