yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] aga2:
Is there any way to hide notification icon from Privacy Guard or it is under development? (like CM12.1's Show Notification: OFF in Privacy Guard settings).
[Nexus 5 Original Android Development] trees247:
How come when I update to a new nightly my phone keeps getting a google play services has stopped. How can I prevent this from happening?
[Nexus 5 Original Android Development] Axel85:
Is It ok if I do a logcat With elementalx kernel installed? The problem is The same With both cm and elementalx kernel
[Nexus 5 Original Android Development] :
Use stock kernel please! :) If you already flashed ElementalX you can just flash your current nightly (or a newer one) on top - it will then replace your kernel with stock CM kernel again :)
[Xperia Z5 Q&A, Help & Troubleshooting] alishmufan:
Hello everyone,

I have had my E6653 since mid October, and it was working well, however once I flashed a Taiwanese 32.0.A.6.152 firmware I have this bug. Let me describe what actually happens:

1. All stamina modes turned on (clock, extended standby, extended usage)

2. Start using the phone after it sat idle for some time, sometimes even 10 minutes is enough

3. Whatever app you were in, if it requires internet connection, it won't work. Switch apps, try to use internet connection and it still won't work.

4. Wait for somewhere around 15 seconds, and internet connection kicks in.

It happens when I'm both on LTE and Wi-Fi. I have already tried repairing my phone, and flashed 3 different firmwares (CE, Taiwan, UK), but nothing helps. I have seen someone on reddit with a similar problem, but for them it only occurred when they were connected to Wi-Fi.

Has anybody else experienced this? If yes, were you able to fix it?

Thanks for your time!
[Xperia Z5 Q&A, Help & Troubleshooting] ricodredd:
I was able to fix it by waiting 15 seconds.

Seriously, turning back on the radios and acquiring an IP address isn't instant. Just be happy you have a phone with Stamina mode available if you want it.
[Xperia Z5 Q&A, Help & Troubleshooting] alishmufan:
I don't think you understood what the problem is. I have LTE and Wi-Fi turned on all the time, never turn either off. Stop using a phone for 10 minutes, turn the screen back on, unlock it, try to use internet connection and then it fails. It hasn't happened on the previous version of the firmware when I had all stamina modes turned on, and it certainly isn't normal. It's a bug, and I was asking if anyone knows the fix. Waiting 15 seconds is not one, unfortunately.
[Xperia Z5 Q&A, Help & Troubleshooting] ricodredd:
Well one of us isn't getting the issue for sure and I don't think it's me. However, I've been wrong before ;)

You said:

"1. All stamina modes turned on (clock, extended standby, extended usage)"

but also:

"I have LTE and Wi-Fi turned on all the time, never turn either off."

Stamina mode says about Extended standby: "Saves power when the screen is off by temporarily disabling Wi-Fi and mobile data".

These two statements are in disagreement.

So you put the phone down for a few minutes (presumably the screen goes off too), then Stamina mode kicks in and turns off Wi-Fi and mobile data. You wake up the phone after 10 minutes or so => you need to wait for radios to fire up and acquire IP address.

I'm not seeing anything wrong or unexpected with this behaviour... :confused:
[Xperia Z5 Q&A, Help & Troubleshooting] gamer649:
I've noticed this more aggressive stamina mode myself. In all honesty I can't see a problem with it, it's putting the phone into deep sleep a lot faster (10 seconds or so in most cases) than it was on the firmware before. If it is happening across many different firmwares it is safe to assume that's how it is meant to be functioning. If, in the next firmware, it goes back to how it was it was a bug.
[Xperia Z5 Q&A, Help & Troubleshooting] andiling:
This behavior is different to earlier Xperias so it surprised me as well. In addition the phone shows you still connected to the network which makes it more difficult to determine.
[Moto X Q&A] Saloedov:
Hello, guys and ladies.

I have some weird behavior of my XT1058 when I watch video from network. So, when I open video in MX Player or even in Chrome's videoplayer, it works perfectly, but when I try to move across the video, my phone comes crazy. At first few times I can do it without any problems and then scrolling causes freeze and then phone performs a reboot.

I'm using stock CM12.1 without custom kernel.

Need your gelp to solve this problem.

Thanks!
[Galaxy S II Q&A, Help & Troubleshooting] bel432:
my gt i9100 does not show screen on recieving a call so could not adjust the setting like speaker or other option usually appearing on recieving a call this is befor and even after rooting to 4.4.4 any help to control call setting
[G 2014 Q&A, Help & Troubleshooting] dexter1123:
Hi,

I am using LuK1337's AOSP ROM (5.1.1) on my Moto G 2014. Whenever I connect my bluetooth headset with my phone my phone's performance goes down...it takes long time to open apps and becomes laggy.

My friend used the same bluetooth headset on Redmi Note 2 and it was smooth, he can even play games smoothly while connected to bluetooth headset.

I am not sure what is casing this and what is the solution.

Please advise..thx
[YotaPhone] SteadyQuad:
Update: Yota did something unusual: they communicated! :p An employee contacted me with a request to remove the download link. He hints that an official release is not that far away anymore, and that the RU1.1.81 version in this post still has some open issues, so I decided remove the download link for now.

A little something to play with for those who are interested: Yotaphone 2 firmware 1.81 (Russian)

What is it?

- An (as of yet unreleased) yotaphone 2 firmware by Yota Devices

- still based on Lollipop 5.0

- unknown quality: My guess is beta+ quality, maybe some issues

- Russian (RU) version (hardly noticable, some russian apps, additional Cyrillic characters in dialpad of dialer), but runs fine with English language/other locales

- modem firmware is same as e.g. EU, I've had no network connectivity issues so far

- it's a full firmware, so it's not dependent on your current firmware version.

- contains from some new features, like double-tap-to-wake, new widgets and widget sizes, panels background selection, app improvements, security fixes (and who knows: some new Russian backdoors to match? :eek: )

- From Yota Devices themselves (signed).

Issues/warnings:

- for some reason unknown to me, Xposed framework won't run on recent versions. Boot never finishes with Xposed installed, the boot animation keeps playing, some background services get restarted over and over.

- This firmware has unknown quality, I've been using this one for a few hours now, looks pretty OK so far.

- If you're not comfortable using TWRP and flashing firmware images, it's probably easiest and safest to wait for an official OTA update.

- My phone showed a missed alarm this morning after having snoozed the first one, not sure if related to this firmware, but be careful not to lose your job ;)

- <download link removed>
[YotaPhone] SteadyQuad:
A detail which I may have missed until now: YotaReader in ROM 1.8x renders text in high quality (16 colors). See an example of the quality difference in this post here.

It may have been in the app for some time already, did anyone notice this? Backscreen browser does not do the same unfortunately, but at least reading ebooks is nicer now! :good:
[YotaPhone] zute333:
Thanks for this dude, very exciting news. Did you get a look at any of the new features / fixes in the new firmware?

Nice that at least some people are paying attention to here :P..
[YotaPhone] SteadyQuad:
I mentioned some new features above, I especially like the double-tap-to-wake (better than swipe gesture) and the improved text quality in YotaReader.

In other news: Xposed (latest version: v78) seems to work again in combination with recent firmwares (it stopped working somewhere after 1.60), so that's good news too for users attached to Xposed.
[Android One (Second-Generation) General] Cyntil8ing:
For those that are not yet informed, this is an important article as to how Google will proceed with the Android One program.

Android One 2nd Gen may be the last of it's kind in terms of a unified, inexpensive Android platform with top to bottom hardware and software standards.

Article Link
[Android One (Second-Generation) General] ondoy1943:
the original and very essence of the android one program will be marginalized and eventually die a natural death. long live the android one. apple has the last laugh. lol...
[Android One (Second-Generation) General] boborobo:
WSJ article, which is the source of the arstechnica oped, is paywalled. So I don't know for sure whether this is just a special exception made by Google for one particular market.
[Android One (Second-Generation) General] Cyntil8ing:
Yeah, I sure hope that's true but, ARS Technica is usually dependable on their reporting and the chances of them omitting that detail's unlikely. Emerging and small economy OEMs are notorious for for pushing crap stock firmware and even worse security/update policies if any.

I hope google keeps pushing all OEMs to comply to a standard when it comes to security and updating instead of opting in. They've started implementing stricter policies regarding MM in that regard and I hope they keep following through in that direction. It's not like OEMs really have a choice if Google decided to implement higher standards.
[Android Q&A, Help & Troubleshooting] jmarques00:
Hello,

I have one serious probleme !! When i use adb shell with root i can't remove files from one folder named clockwordmod in sdcard. I've tried chmod permissions of files and then does not work to :/ the output (name of file): permition denied . And the output of ls -l is -rw-rw---- root sdcard_r (size) (date) (name of fil) any one can help me with this situation? Thanks

Regards
[Galaxy S 5 Q&A, Help & Troubleshooting] chris.arney:
I've got a 128GB microSD card that I've been using for a while with CM12.1 on a 900T. I just flashed CM13, and it says that it doesn't support the card. I swapped the card out with a smaller one that's FAT32, and it reads it fine. Is this an exFAT issue? Is this just CM13, or does Marshmallow itself not support this? Any idea?
[Galaxy S 5 Q&A, Help & Troubleshooting] Zehlek:
You have to select it under storage and format as portable make sure you backup anything stored on it as it will erase it
[Galaxy S 5 Q&A, Help & Troubleshooting] chris.arney:
I selected it as portable, but that doesn't address the formatting issue. It wants to reformat the card, saying that it's incompatible. I've got another card in the phone that I've gone through the process, and it didn't ask to reformat the card. The other card works fine. The 128GB exFAT card worked fine before I flashed CM13, and is what I had the CM13 image on when I flashed it (so it works in recovery). The exFAT card is also read fine by my computer. I understand the implications of the exFAT format, but everything else seems to read it fine. I'm looking for confirmation for the symptoms I'm seeing, and wondering if there's a work around to using the card as is without reformatting it.
[Galaxy S 5 Q&A, Help & Troubleshooting] aha360:
I don't like to hop onto other people's topics, but seeing as I too suffer from the same issue as you are, I also want to know if there is a fix that will allow people to use micro SD cards without formatting it in Android Marshmallow as I think it is absolutely stupid for the OS to ask users to format it before using it in Android Marshmallow.
[Galaxy S 5 Q&A, Help & Troubleshooting] kenkiller:
Marshmallow wants to format it to FAT32, which is stupid I agree. Whether a fix will come or not is up to CM - I doubt Google will do anything about it.
[Galaxy S 5 Q&A, Help & Troubleshooting] gustavargas:
I had to backup everything and let the phone reset the SD, it was a Transcend 64GB exFat.
[Galaxy S 5 Q&A, Help & Troubleshooting] chris.arney:
Thanks. I thought that was probably the case, but I wanted verification. Any idea if it supports other formats besides FAT32?
[Galaxy S 5 Q&A, Help & Troubleshooting] kenkiller:
It's not that CM doesn't support exfat - external usb in exfat is recognized and read. But using it as portable storage seems to make it want to format to fat32.
[Galaxy S 5 Q&A, Help & Troubleshooting] Arunscape:
Update: marshmallow converted my sd card to fat32 :(((

I was wondering why the speeds were a bit slow...
[Galaxy S 5 Q&A, Help & Troubleshooting] ad astra:
Well f***... I'm having the same issue. Seems like I'm stuck without ex_sdcard, as when I try to format the storage via android it gets stuck at 20% (cm13 + samsung 64 class10). Fortunately I could re-format the card with a card reader to exFAT and now I can use TWRP to send my previous CM12.1 backup and restore it. Really glad I dumped that backup to my pc :D

Can anyone confirm if this is a CM13 related issue or a marshmallow one? The former would be great, as there are more chances of getting a "fix" form them than from google.

Thanks a bunch.
[Galaxy S 5 Q&A, Help & Troubleshooting] Ookpic:
I hate to drum up an old thread but I see it's only a few weeks old and never got an answer....

If I'm not mistaken, exFat is not recognized by Google Android natively. Some hardware manufactures (like Samsung) bake exFat support into their version of Android but I understand this is at a cost as they have to pay MS for licensing and MS is keeping a firm hold on it. Since CM is based from Vanilla Android, it too won't have native support for exFat. It will however support Fat32 but that sucks because it is slow and has a 4GB file limitation. I have read that ext4 is mountable with Marshmellow but it is not compatible with Windows natively. So the option then becomes how to get large files onto the extSD card if it is formatted to ext4 if you have a windows machine? This is where I'm at. I'm currently formatting a microsd card to ext4 to try and see if I can still wirelessly transfer directly to my extsd card or if I can transfer to the internal storage and then transfer from internal to external storage within the phone.

I'm sure there is a fix for getting exFat compatibility somewhere though.
[Galaxy S 5 Q&A, Help & Troubleshooting] gtdRR:
I'm running 6.0.1 stock on my Nexus 7 and was able to access my 64GB exFat microSD via OTG using Solid Explorer and it's OTG plugin. Paid app but completely worth all the features.

Solid Explorer - https://play.google.com/store/apps/details?id=pl.solidexplorer2

Solid Explorer USB OTG Plugin - https://play.google.com/store/apps/details?id=pl.solidexplorer.plugins.otg
[Galaxy S 5 Q&A, Help & Troubleshooting] r25txe:
Yes, but that is as an OTG device, not a portable sd card directly in a slot on the device. Apples and oranges.

I've just met this regression on my SIII, it's Google not coughing up the licensing for exFAT. Perhaps not surprising.

It's going to be fun working with painfully slow FAT32 after 3/4 years without it.

---------- Post added at 04:22 ---------- Previous post was at 04:18 ----------

If you are lucky enough to be running a Motorola stock ROM you can set your card as portable storage and your phone will

not

reformat the card.

Can someone confirm this and will Moto phones support exFAT natively?

https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/109134/p/1449,9582
[Galaxy S 5 Q&A, Help & Troubleshooting] dnkidd:
From clintonfitch.com, not verified by me: "But there is another feature that Android users have long wanted out of the platform that has come with Marshmallow: Native USB On-the-go (OTG) support. ... it appears that the only devices that this works on with Marshmallow are Nexus devices: Nexus 5, Nexus 5X, Nexus 6, Nexus 6P, Nexus 7 (2013), Nexus 9 and Pixel C. I can confirm that I was able to connect a USB drive and a mouse successfully to my Nexus 6 and Nexus 7 while I was equally able to connect both to a colleague who as the Nexus 6P and Nexus 9. " I have not verified this; I use a rooted Marshmallow with stickmount and that works with exFAT 64GB cards formatted on my GoPro.
[Galaxy S 5 Q&A, Help & Troubleshooting] magicmanfk:
Try formatting it as FAT in TWRP and booting back.
[Galaxy S 5 Q&A, Help & Troubleshooting] keymanhattan:
I confirm Solid Explorer unlocked read and write exFAT USBstick via OTG. Maybe the only solution till now.
[Galaxy S 5 Q&A, Help & Troubleshooting] fizzingbees:
same issue

i am also having this same sd card issue on resurrection remix -marshmallow v5.6.7 where 128gb exfat card ask for format and erase for both portable and internal storage options whereas old 2gb FAT card works fine

i guess this is marshmallow problem.cause lollipop was fine too

now i looking to make my sd card work without formatting it...but i guess thats not possible
[Galaxy S 5 Q&A, Help & Troubleshooting] Chaitanyapatel8880:
I was able to make it work with boeffla kernel
[Galaxy S 5 Q&A, Help & Troubleshooting] r25txe:
Using it as portable storage or OTG?

What ROM? Galaxy S5?
[Galaxy S 5 Q&A, Help & Troubleshooting] fizzingbees:
can you give us a direct link ?

Agni kernal also supports exfat but its just my sd card doesn't work even with it. i talked to kernel developer and he said that the rom must utilize this kernel feature in order to support exfat card and since vanilla android doesn't support exfat so flashing kernel that supports exfat without rom that doesn't is futile attempt. i know this coz i have tried it and given up

---------- Post added at 03:12 PM ---------- Previous post was at 03:06 PM ----------

i guess you could make exfat work in otg with correct app e.g solid file explorer with its USB OTG plugin or with stickmount app by chainfire in CM based roms.

its the portable storage that gives problems

samsung galaxy series with touchwiz based rom support exfat. Samsung baked this support into their roms ,but CM based roms on galaxy devices give problem with exfat cards since exfat file system is not native in vanilla android
[8525, TyTN, MDA Vario II, JasJam ROM Development] gunigugu:
Has anyone been able to get MMS working on Three Australia??

I've been trying for the last few days and it's work with pretty much all other customized roms.. but this one is giving me issues? Maybe something to do with device identity on three servers or maybe this new version of arcsoft broke something???

I'm 100% certain settings are correct. I've tried with network setup wizard, and the following:

Gateway: 10.176.57.25

Port: 8799

Server address: http://mmsc.three.net.au:10021/mmsc

Connect via: (3 services connection, whatever it's called?) Mine is MY ISP

also tried with:

Server address: http://mmsc.three.com.au:10021/mmsc

No juice at all.. anyone else want to confirm on three Australia?? Oh and sorry about making a new thread for this.. I tried posting this in schaps thread but no response many times. I'm just looking for ANYONE to test and confirm this.
[8525, TyTN, MDA Vario II, JasJam ROM Development] bigruss:
Also on Three Australia, running Schaps 3.54c. I don't usually use mms but just tried to send and it didn't work, using settings from the network wizard (checked against what I had previously sourced from aussie3g)

So it's not just you....
[8525, TyTN, MDA Vario II, JasJam ROM Development] gunigugu:
Hey thanks for that.. just wanted to make sure I wasn't going crazy... It annoys me a bit, because I'm really REALLY loving this rom.. besides the mms thing, not one glitch and has everythign i need...
[8525, TyTN, MDA Vario II, JasJam ROM Development] drooch:
im running 3.54c and i am getting MMS with 3 Australia no issues at all. the settings are correct but as it has been posted before on other sites, you have to ring 3care and report a fault. tell them mms doesnt work just play along with them with regards to OS (stock 3 ROM) and settings.

they need to reset your 'individual profile' on the server. i had to get this done as MMS were not sending at all. it took about 3-4 days but i got fixed and MMS are working fine, send and receieve with only a minimal delay (2min max) between send and recieve.

just make sure your connect via settings has the APN 3services. Also WAP 2.0 and 300kb limit.

.... on another note 3.60a beta did not work with 3australia and the MMS settings, so i had to go back to 3.54c.....

Drooch
[8525, TyTN, MDA Vario II, JasJam ROM Development] gunigugu:
That's really strange... because the simcard and network is fine, i've tested it in other phones without issue.. i've been tru hell with mms before where it wouldn't send and then three did reset the profile and all was good. but this is a different issue and it's strange how it didn't work in the beta but it's working for you in 3.54c as techincally their both the same, it's just 3.60a beta is based on a new build of wm6.... and both are using the same version of arcsoft as well.
[8525, TyTN, MDA Vario II, JasJam ROM Development] gunigugu:
Oh and one other thing I noticed... if you change to wap 2.0 so does the port number from 8799 (which it's supposed to be) to 8080 (which is the default for wap 2.0). I would double check your settings and see what their set to because it's not making much sense...
[8525, TyTN, MDA Vario II, JasJam ROM Development] drooch:
thats why the 3.60a ROM doesnt work.... it auto selects the port based on WAP version. the 3.54c version does not do this and therefore still works

Drooch
[8525, TyTN, MDA Vario II, JasJam ROM Development] bigruss:
argh, why did I test this for you?! It's bugging me too now. I have the same situation where the port changes based on the wap version, running 3.54c (just checked in case I was being really stupid)

so it looks like we either have the wrong port or the wrong wap....

strange that it is working for one person.
[8525, TyTN, MDA Vario II, JasJam ROM Development] gunigugu:
Well actually 3.54c does do this (change the port to 8080 on wap2.0). Everyone else's post in here confirm this.

And too be honest.. i don't think that's what's causing the issues, because well wap1.2 should still work...
[8525, TyTN, MDA Vario II, JasJam ROM Development] drooch:
yes it does auto select a port number when u select the Wap version but if u overwrite it, it does not revert back to the original number, so u can select wap 2.0 and then overwrite the value back to 8799 and select ok. it should then stay on that port number.

I work in the industry and i must say that this issue only arises on cooked ROMS. i dont know if this will help but i have attached a hutchison file that was from the extrom of the dopod rom. i dont know what it contains but it may help

Drooch
[8525, TyTN, MDA Vario II, JasJam ROM Development] gunigugu:
hmm.. well i'm running 3.54c and i can confirm.. if you change the port then hit ok.. go back into the settings and you'll see the port / wap version has been changed automatically for you...
[8525, TyTN, MDA Vario II, JasJam ROM Development] drooch:
well i dont know why thats happening.

did you set up a new configuration or overwrite the sample one??

ive been testing my phone since i saw this post and for some reason, if i select WAP 2.0 it will select Port 8080. i then overwrite it to 8799 and select ok.... never changes back to 8080 (unless i select WAP 2.0 again)
[8525, TyTN, MDA Vario II, JasJam ROM Development] bigruss:
same happens with me, if I overwrite it will revert to the original. This happens with new and existing mms servers
[8525, TyTN, MDA Vario II, JasJam ROM Development] gunigugu:
Are you sure your running 3.54c because outside of your post, no one else can confirm what your reporting...

Seems a bit strange...