yashsingh1/xdaforums huggingface dataset:
[G3 Q&A, Help & Troubleshooting] KronicSkillz:
just buy a 64gb micro sdcard... or even a 32gb if you don't need much more, they are really cheap.

part of the missing space is the partition information space and the space used by the system/recovery/cache etc. on android 6.0 you can format it as internal.
[G3 Q&A, Help & Troubleshooting] MichelN:
How can i format that space ? I am running CM13 that uses Android 6.0.1
[G3 Q&A, Help & Troubleshooting] MichelN:
Here another screenshot from the recovery, why does the recovery not say i have 16GB ???? i don't really understand why it's not listed.
[G3 Q&A, Help & Troubleshooting] TheMadScientist:
Because it shows available storage not total
[G3 Q&A, Help & Troubleshooting] MichelN:
Oke thanks for the answer.
[Nexus 6P Q&A, Help & Troubleshooting] gaming09:
anyone get a ps4 controller to work (wired or wireless) no root on their 6p? if wired which connector did you use
[General Topics] Emil Borconi:
Hi.

I have read the rules of the sites but I'm not able to decide what is the best course of action here, so I need some advice please:

There is a piece of software out there, which I do like and I think it is very useful, BUT it has some serious limitation, for example is not able to run on Android 5.0 or higher and it cannot be automated. I have contacted the software developer and I have asked for support but I was turned down. After this I have reverse engineered the application and started making the modifications myself (editing smali files), now the application works on Android 5.0 and can be automated, but it does not work on anything below 5.0, plus some of the procedures have been totally rewritten. The question is in this case is it ok for me to remove the original license and share the app, or not? It is the same application, yet it isn't because it is targeting different platform.

Your input is highly appreciated.

Thank you.
[General Topics] Magnum_Enforcer:
No, this is not okay. You're essentially taking someone else's work and modifying that work. Without the original app, you would have nothing to begin with.

Thread closed.
[General Topics] Neo:
Let me re-ask the question in this way:

An individual is producing and distributing a vehicle called Neo-is-teh-Awesome-one, but it only runs on jet fuel. Along comes a smart individual who knows that people are starting to use water for fuel these days and it's much cheaper! This change would actually make more people want to buy and drive tehawesomeone and it would really help the other guy out a lot! However, he refuses to assist the smart guy for whatever reason about the potential modifications, yet the smart individual figures it out on his own anyway. The only problem now however, is that it now ONLY runs on water which is ok quite frankly because water is the future!

My question is this: Can he re-name the car to Water-Hydrates-FTW and go ahead and re-distribute/produce it for everyone as his own creation? :)

Have a pleasant day and congrats on making whatever it is work for 5.0 :good:
[Galaxy S 4 Q&A, Help & Troubleshooting] xdajuecat:
Hi,

I had several problems with custom rom, so I went back to stock ROM (latest MOB version) to start everything new.

Now I got the problem that it is not possible to flash CWM or TWRP again (tried different versions to flash with odin). I also tried to get back to UHOL2 bootloader and modem, bootloader is now UHOL2 but also custom recovery not working.

Any ideas how to get TWRP working again?

Thx

Jürgen
[Galaxy S 4 Q&A, Help & Troubleshooting] Rhoban:
Can you root it?

Then you might be able to use flashify to flash the recovery.img
[Galaxy S 4 Q&A, Help & Troubleshooting] Lennyz1988:
Uncheck auto-reboot before flashing TWRP trough Odin.
[Galaxy S 4 Q&A, Help & Troubleshooting] xdajuecat:
used CF Auto root - Phone Info says that root is working

which recovery.img should I try - CWM or TWRP doesn't matter for me
[Galaxy S 4 Q&A, Help & Troubleshooting] Rhoban:
TWRP. CWM is outdated.
[Galaxy S 4 Q&A, Help & Troubleshooting] xdajuecat:
Uncheck auto-reboot before flashing TWRP trough Odin and removing battery was the solution!

Thx
[Galaxy S 4 Q&A, Help & Troubleshooting] audit13:
Selecting auto reboot after flashing twrp causes the stock recovery to overwrite twrp and this is why the phone should be booted into twrp right after flashing.
[Elephone P8000] calebccff:
After FINALLY figuring out how to root this (the No Command recovery screen :mad:)

I was happy to get my root apps working and I had everything working perfectly...

The screen suddenly goes blank, at first I thought it had run out of power so I plug in the charger and nothing happened, it had been on 20% last time I checked so this seemed unlikely...

After several attempts to do a hard restart (Vol- and Power) I held down Vol+ and Power to access the boot mode selector and selected normal boot, the screen goes blank. Logically I then tried to boot into recovery (I have Philz Touch) and the screen goes blank, I was getting worried now (I have only had this phone for 3 weeks!). As a last ditch effort I tried fasboot but to no avail, If anyone else has had this issue and can help that would be greatly appreciated, I do not know what to do next...

Thanks,

Caleb
[Elephone P8000] calebccff:
[SOLVED]

After leaving it on charge overnight it started up normally, I have no idea why this happened?!

Leaving this thread here in case anyone else finds it useful.....
[Elephone P8000] calebccff:
I am using Nova launcher and I think this is related to the battery drainage once you go below 15%.
[Elephone P8000] amigo1:
I have the same problem :(

Fev times go to selector "Recovery Fast boot Normal boot"

But after that, noting happens, when charging led not light, but charger is hot and near camera board (cpu is warm too).
[HTC Tornado] lixxus:
the tomtom is abit outdated..

and i want it to work with pocketgps POI for speed cameras
[HTC Tornado] Bustard:
What I can tell you is that route66 mobile 7 works perfect but when you quit it you have to reboot the phone because it messes up quite good.

does this work with what you need?
[HTC Tornado] ddhytz:
I don't have this problem.
[HTC Tornado] maxima00se:
Is there a cab for this? I found the ones for S60 on N75, but I'm not sure if those will work.
[Samsung Gear S2] andrespos:
Probably a shot in the dark. A couple weeks ago i misplaced my gear s2. I cannot use the find my watch feature because the batteries are dead and its not in range,etc. Is there a log on the phone app or somewhere where i can see the watches last gps coordinates?
[LG V10 Q&A, Help & Troubleshooting] whatsinaname:
I have a VZW LG-V10 and love it.

Yesterday I tried to use the slow motion video, and it doesn't work. I select "mode" then select "slo-mo" and it says hit the button to record in slow mo. I record the video. After I record I use the gallery app, (stock) and it plays back normal speed with sound. Others that I saw having this problem say use the "stock gallery" but that doesn't do any thing for me.

I tried recording to sd and to internal just to check. Thanks for any help you give.

Also I have the newest update recently released.
[LG V10 Q&A, Help & Troubleshooting] blackhemi4x4:
Clear you gallery default apps. Sounds like it's playing in a non stock video player.
[LG V10 Q&A, Help & Troubleshooting] trungvov10:
yea you need to play it with stock video player
[LG V10 Q&A, Help & Troubleshooting] whatsinaname:
Thank you, I think mx player was default.... Thanks it works now! Happy camper
[Sprint Samsung Galaxy S6] besotsima:
Hello

As i know our phone has a hardware with abilty to function on all bands, vut it's need to be unlocked :(

Can anyone help me to open lte bands? Any tutorials?

Thanks
[Sprint Samsung Galaxy S6] 1619415:
What do you mean by all bands?
[Sprint Samsung Galaxy S6] besotsima:
I mean for example open LTE band 3. I know that device is capable to receive network on that band and it is blocked by the operator.
[Sprint Samsung Galaxy S6] 1619415:
In guessing idoneapps is what y you want, or would be able to help
[Sprint Samsung Galaxy S6] besotsima:
Nope, I have unlocked globally my phone. problem is that In my country LTE cellural band is LTE 3 only that's why I want to open all cellular bands.
[Sprint Samsung Galaxy S6] gugamaxara:
I have same question :(

please help us guys....... :crying:
[Sprint Samsung Galaxy S6] jeff83nz:
BUMP bands 3 & 7 :)
[Sprint Samsung Galaxy S6] koop1955:
This might be the place to get started: http://xdaforums.com/galaxy-s5/general/how-to-add-rf-lte-frequency-bands-to-t2886059

The process seems complicated, so good luck.
[Sprint Samsung Galaxy S6] jeff83nz:
Thanks. Yeah I saw this thread, but wondered with the S6 using Exynos processor instead of a Qualcomm processor if it stil could work.
[Sprint Samsung Galaxy S6] koop1955:
I can't advise you on that. I would reach out to the Original Poster on that thread and ask.
[Sprint Samsung Galaxy S6] besotsima:
I would pay if someone could open LTE band 3.

As i read there is DIY option only for Qualcomm processors.
[Sprint Samsung Galaxy S6] 1619415:
There is for Qualcomm but not Samsung processors because there is no source for them. Without that, we just can't do it. Your better of just buying an S6 with band 3 or and international one.
[Sprint Samsung Galaxy S6] besotsima:
If there is no other way, I will stick with 3G - gives almost 10mb ;)
[Sprint Samsung Galaxy S6] zazabichi:
Did you get any success regarding adding LTE bands?
[Galaxy Note 3 Q&A, Help & Troubleshooting] djnuffsaid:
I just got my phone fixed by a repair shop and they had to replace the motherboard. So when I got it back it has 5.0 on it instead of my KitKat ROM I like. I'm trying to get into Odin so I can reflash a stock kitkat rom but no matter what driver I put on my computer when ever I plug my phone in Windows says Unrecognized Device and Odin doesn't pick it up either. Please help!! I am dying without being able to revert back to KitKat and my favorite rom.

The driver I am trying to install is SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.45.0

By the way it's a T-mobile Note 3.
[Galaxy Note 3 Q&A, Help & Troubleshooting] kpirnie:
u got the right driver bud... snatch up all yur usb cables, and try them all in all usb ports on your pc... one of em's bound to work...

if not, call up the people that "fixed" your phone and explain
[Galaxy Note 3 Q&A, Help & Troubleshooting] Mustafa Jafri:
Its probably the cable.

Few days ago I was trying to connect my phone with PC but wasnt able. I tried 3 different cables. But 2 days before I bought an original new cable and it was working fine for me.
[Xposed Framework Modules] crackers8199:
this xposed module is based on the MagnetOff module built by XDA use dubidu - however, that module was broken as of android 6.0. since dubidu has not contributed on the forums in a few months, i decided to write my own version of this module that works for both android 5.x as well as 6.x. i did not use any of dubidu's code (since it's not open source as far as i can see), but i do give full credit for the idea and where to look to disable the sensor (based on reading the thread related to that module).

this is confirmed working on nexus 6, both 5.1.1 (by myself) and 6.0.1 (by xda member porkisyummy). as far as i can see, it should work on any nexus device (and probably others as well)...but of course i can't confirm that and am not responsible if you break your phone trying to use this module.

changelog:

v1.0 (1/18/2016):

- initial release

v1.1 (1/18/2016):

- bug fixes

dubidu's MagnetOff module thread: http://xdaforums.com/showthread.php?t=2621807

XDA:DevDB Information

Magnet Sensor Control, Xposed for the Nexus 6

Contributors

crackers8199, dubidu

Xposed Package Name:

Version Information

Status: Stable

Current Stable Version: 1.0

Stable Release Date: 2016-01-18

Created 2016-01-18

Last Updated 2016-01-19
[Xposed Framework Modules] crackers8199:
reserved
[Xposed Framework Modules] jaibar:
Oh, this is great!

I am suffering from the magnetic car mount havoc ? (nexus 5).

Going to test it on next drive

[EDIT] Works great. However, could be nice to have a minimal user interface with a master switch. Thus, one can readily switch it on/off (for the sake of people who want to use magnetic cover, and turn on the module at will). At the present, one needs to enable/disable the module in xposed installer, then reboot..
[Xposed Framework Modules] pirasalbe:
Thank you very much, it would be useful to choose to activate sensor for sleep or wake
[Xposed Framework Modules] porkisyummy:
Thanks again for taking this project on! I tested it out on my drive home last night and was very pleased. I did notice one issue--when the screen turns off, the power button doesn't turn the screen back on while a magnet is present.

I can imagine that this might have been a problem with the original MagnetOff module as well. It seems that in addition to hooking into lid close events, hooks on power button events might be necessary as well. If you're willing to share source I'd be happy to contribute. Otherwise, I can look at the OS source and try to suggest changes.

[EDIT: to clarify, these issues were with the first release. I re-tested with the latest release and can confirm the power button works correctly when docked to a magnet.]
[Xposed Framework Modules] xk0niR:
This might be stupid but does it save battery to turn it off?
[Xposed Framework Modules] kalhimeo:
Hi crackers,

Thank you very much for taking over with the development of this xposed module !

Is there any chance you can have a look why it's not working with the Galaxy S4 Google Play Edition (LP 5.1) ? Let me know if I can help anyhow.

Best regards,

Laurent
[Xposed Framework Modules] tbv2005:
Hi,

works perfectly on Nexus 6P with latest firmware installed.

Just hope the magnet I'm using is not to strong to destroy something in the phone :D
[Xposed Framework Modules] jaibar:
Part of my research is in MRI environment, so over time I had the pleasure to put lots of cellphones into b rather strong magnetic fields (somewhere between 1.5-3 Tesla).

Surprisingly, they seem to survive mostly without noticeable damage. In an old Nokia 3210 I managed to get the speaker fubered. Other than that, I can't recall any other damages.
[Xposed Framework Modules] crackers8199:
that's already on my to-do list, in fact i started working on it last night. no ETA, though...

i know you've seen the newest version fixes this, but i wanted to chime in :) that's actually one of the first things i noticed on my first drive with this active. came home and found the other function i needed to hook to fix that, and voila...tested again on my trip to the store last night and saw no issues at all. seemed to be working flawlessly...

the GPE phones use AOSP with no modifications, right? or are there still some tweaks samsung puts into the code? what build are you on?
[Xposed Framework Modules] crackers8199:
to turn off the sensor? i'm not sure (that isn't really the point of the module)...this is more to stop the screen from going crazy when using a magnetic car mount.
[Xposed Framework Modules] kalhimeo:
GPE Android phones should be AOSP (no touchwiz and other crap), but I can't tell if everything really is exactly stock. I am on build LMY47O.S008.151001 (using this rom http://xdaforums.com/showthread.php?p=63349301).

Thanks for your fast reply !
[Xposed Framework Modules] crackers8199:
i'll take a look when i get a chance today or after work. i can't make any promises though, i'm guessing it has something to do with the fact you're on a custom ROM (so far i think this has only been tested and confirmed working on stock ROM 5.x and 6.x)...

from looking at the code, it looks like his ROM implements the lid switch control stuff in a different place from stock android. that's why it's not working. i could probably hook the method it looks like they use and it might work, but i won't have the time to put out a new version every time a custom ROM uses a different function to control the sensor... :(
[Xposed Framework Modules] kalhimeo:
Sure, I can understand that it s not ideal... I think that Samsung is the culprit in changing the way it handles the lid for this GPE (which is a shame), because this other GPE rom announced as "untouched" seems to be affected the same way.

Anyway, thank you very much for taking the time to check it !
[Xposed Framework Modules] crackers8199:
if it's something that's present in all samsung GPE phones, i could probably put out a version with a setting to control it (at least that's something i would consider since it's more of a phone or segment of phones rather than putting out a new version for every custom ROM that comes out). i'll take a look at this tonight after work and see what i can come up with...
[Xposed Framework Modules] crackers8199:
try this one and let me know if it works (and anything you see from my module in the xposed logs)...
[Xposed Framework Modules] kalhimeo:
Hi crackers,

Although logs show that your module has loaded and hooked successfully, the screen still turns to "s-cover" mode when the device is put close to a magnet.

Full log included below.

Thank you for trying and let me know if there is anything else I can test.
[Xposed Framework Modules] crackers8199:
alright, attempt #2....
[Xposed Framework Modules] kalhimeo:
got an error this time :

01-20 10:03:44.996 I/Xposed ( 949): MagnetSensorControl: attempting to hook Samsung GPE
01-20 10:03:44.997 I/Xposed ( 949): MagnetSensorControl: java.lang.NoSuchMethodError: com.android.internal.policy.impl.sviewcover.SViewCoverManager#updateCoverState(boolean,android.content.ComponentName)#exact
01-20 10:03:44.997 I/Xposed ( 949): MagnetSensorControl: unable to hook Samsung GPE, moving on...
01-20 10:03:44.997 I/Xposed ( 949): MagnetSensorControl: attempting to hook PWM lollipop
01-20 10:03:45.004 I/Xposed ( 949): MagnetSensorControl: success hooking PWM lollipop, magnetic sensors disabled

Full log included although nothing else special
[Xposed Framework Modules] crackers8199:
hmm...alright. i'll take a look again after work and see what i can find.
[Xposed Framework Modules] crackers8199:
okay, let's give this one a shot...
[Xposed Framework Modules] kalhimeo:
This one works better, since it prevents the screens to turn black with the magnet, but the touchscreen is still locked (so I see my home screen but whatever I touch makes no effect). No errors in the xposed logs.

Keep up the good work ;)
[Xposed Framework Modules] faderrific:
I'm running rooted stock 6.0.1 with Feb update and Xposed ver 78. This module works perfectly! Ive been waiting for a magnet sensor control app for months! Finally i can use my sweet mount again!

So how do I buy you a beer?

Edit-figured it out
[Xposed Framework Modules] crackers8199:
another attempt...lol i'll keep working at it
[Xposed Framework Modules] kalhimeo:
Thanks for keeping on trying :) This one has the same behavior has the previous one : no black screen, but no touch. no errors in xposed.

When the device is hold on a magnet, I noticed that when I press the area where the clock on the S-cover screen is meant to be, it will start the clock app. It looks like an invisible layer on my home screen with a touch zone in the middle-top. I also noticed that it shows a blank icon in the notification bar. Maybe this "layer" could be some sort of app forced in the foreground. Hope this can help :p
[Xposed Framework Modules] crackers8199:
next man up...
[Xposed Framework Modules] kalhimeo:
same behavior as the 2 previous versions.

Sorry that this takes you so much time :/
[Xposed Framework Modules] crackers8199:
no worries...try this one. behavior should be the same, but i need the logs from this one (i threw a bunch of logging stuff in)...
[Xposed Framework Modules] kalhimeo:
Here it is ! Tapped and removed my device once from the magnet

01-24 01:36:40.768 I/Xposed ( 323): -----------------
01-24 01:36:40.768 I/Xposed ( 323): Starting Xposed version 79, compiled for SDK 22
01-24 01:36:40.769 I/Xposed ( 323): Device: GT-I9505G (samsung), Android version 5.1 (SDK 22)
01-24 01:36:40.769 I/Xposed ( 323): ROM: LMY47O.S008.151001
01-24 01:36:40.769 I/Xposed ( 323): Build fingerprint: samsung/jgedlteue/jgedlte:5.1/LMY47O.S008/151001:user/release-keys
01-24 01:36:40.769 I/Xposed ( 323): Platform: armeabi-v7a, 32-bit binary, system server: yes
01-24 01:36:40.769 I/Xposed ( 323): SELinux enabled: yes, enforcing: no
01-24 01:36:42.866 I/Xposed ( 323): -----------------
01-24 01:36:42.873 I/Xposed ( 323): Added Xposed (/system/framework/XposedBridge.jar) to CLASSPATH
01-24 01:36:43.487 I/Xposed ( 323): Detected ART runtime
01-24 01:36:43.536 I/Xposed ( 323): Found Xposed class de/robv/android/xposed/XposedBridge, now initializing
01-24 01:36:43.894 I/Xposed ( 323): Loading modules from /data/app/xposed.mjg8.magnetsensorcontrol-1/base.apk
01-24 01:36:44.152 I/Xposed ( 323): Loading class xposed.mjg8.magnetsensorcontrol.SensorControl
01-24 01:36:45.435 I/Xposed ( 945): MagnetSensorControl: magnetic sensor control start
01-24 01:36:45.435 I/Xposed ( 945): MagnetSensorControl: attempting to hook Samsung GPE
01-24 01:36:45.444 I/Xposed ( 945): MagnetSensorControl: success hooking Samsung GPE, magnetic sensors disabled
01-24 01:38:07.320 I/Xposed ( 945): MagnetSensorControl: sViewCoverManager constructor | param: de.robv.android.xposed.XC_MethodHook$MethodHookParam@7b29b46
01-24 01:38:07.321 I/Xposed ( 945): MagnetSensorControl: sViewCoverManager constructor | mContext: android.app.ContextImpl@1ea237cd
01-24 01:38:07.321 I/Xposed ( 945): MagnetSensorControl: sViewCoverManager constructor | mHandler: Handler (com.android.internal.policy.impl.sviewcover.SViewCoverManager$3) {107fa107}
01-24 01:38:07.321 I/Xposed ( 945): MagnetSensorControl: sViewCoverManager constructor | mGoToSleepRunnable: com.android.internal.policy.impl.sviewcover.SViewCoverManager$1@3bd1e234
01-24 01:38:07.321 I/Xposed ( 945): MagnetSensorControl: sViewCoverManager constructor | mSviewCoverManagerInstance: com.android.internal.policy.impl.sviewcover.SViewCoverManager@1381585d
01-24 01:38:07.321 I/Xposed ( 945): MagnetSensorControl: updateCoverState | param: de.robv.android.xposed.XC_MethodHook$MethodHookParam@2bed25d2
01-24 01:38:14.755 I/Xposed ( 945): MagnetSensorControl: updateCoverState | param: de.robv.android.xposed.XC_MethodHook$MethodHookParam@2f9526cc
[Xposed Framework Modules] sousaptak:
Tested with my One Plus One 6.0.1 MM.. working perfectly... thanks mate.. please add the links for download in the first post ...:)
[Xposed Framework Modules] Waterickson:
Love my magnets

Super module. Thanks. I had the scosche steel plate behind my N3 cover and really got hooked with the versatility. I even have mag mounts on a folding mighty lite work light. Secures my phone anywhere there is a steel surface or I just fold it like a dock.

Just got a nexus 6 and temporary freaked out over the screen off. I use my custom mag mounts everywhere. At first eyes roll like I'm a 5 year old with a toy... Then people see how cool it is. I even have a pocket mag for the gym. Sticks hard to the steel frames and no irritating arm case!

Thanks
[Xposed Framework Modules] killchain:
Just chiming in to say it works for me. Stock 6.0.1 on a Nexus 6P, using a phone wallet with some magnets that were occasionally waking up the phone.

Like other people said, it'd be nice to have the ability to turn it on and off on the go, although I personally am happy with the module as it is now.
[Xposed Framework Modules] kliu888:
Thank you so much for making this module available in 6.0. Is it possible to disable only sleep but keep the wake function? I was using the original MagnetOff and was able to do that via checkboxes, but this module disable both sleep & wake. Thank you.
[Xposed Framework Modules] copota:
Thanks for the module! Works perfectly on my Galaxy S4 running the latest CM13.

I have magnets mounted on my wall, next to my bed, which is where I attach my phone when not in use. It was so freaking annoying, every time I placed my phone on the magnet mount, the screen would turn on. This module fixes that problem.

Thanks again!