yashsingh1/xdaforums huggingface dataset:
[Galaxy S 5 Q&A, Help & Troubleshooting] Delran:
bump for some help
[Galaxy S 5 Q&A, Help & Troubleshooting] Commodore 64:
I know Sprint operates on CDMA while T-Mobile uses GSM technology.

I don't know if the G900P has the hardware capabilities to operate on GSM LTE bands. But it is interesting that you got the voice to work!

Try this page. He had a Verizon (CDMA) phone and got it to work on the AT&T (GSM) network. So apparently it is possible, and your situation is similar in trying to use a cdma phone on a gsm network.

http://xdaforums.com/showthread.php?t=3291026
[Galaxy S 5 Q&A, Help & Troubleshooting] Delran:
Thanks for the link!

I already had tried what he did previously, adding the APN, sadly that didn't work for me . And once I had unlocked the phone I enabled GSF and got the voice to work. But sadly that's the farthest I've gotten
[Galaxy S 5 Q&A, Help & Troubleshooting] Delran:
bump
[AT&T Samsung Galaxy S 5] JerryGNYC:
Hi. I have a new stock (not rooted) AT&T G870A running 5.1.1 with OJ3 baseband. I've noticed 2 apps, Instagram and Followers+ run very slow when the phone is connected to WiFi. If I turn off WiFi, they work fine. But as this phone is from my job, switching to cellular data for these 2 apps isn't really an option (nor is rooting it). Anybody run into anything similar (and fixed it)?

TIA,

-Jerry

PS... and like my Sprint S4 before this, it's rockin' a really sweet wallpaper from [MENTION=4513677]rwilco12[/MENTION] pro wallpaper app... :D (shameless plug for forum mod... :eek:)
[AT&T Samsung Galaxy S 5] rwilco12:
I wish I had the answer to your problem but I don't. :(

I do however appreciate your shameless plug! Thank you for the support! :)
[AT&T Samsung Galaxy S 5] JerryGNYC:
No problem and my pleasure! Thanks for all the great wallpapers! :good::good:
[AT&T Samsung Galaxy S 5] JerryGNYC:
Found an answer....

After lots of Googling/reading, I found many dead ends. One of them said to disable IPV6 on your router. Didn't try it as the problem happened at home and at work. Then, the other day, things started working properly at my job. OK, maybe it is the network... When I got home, I disabled IPV6 on my internal router, and voila! Problem solved!

HTH,

-Jerry
[Galaxy Note5 Accessories] ekerbuddyeker:
Anyone know a way to stream any sound output over WiFi to a dongle I can ug into my slightly old reciever? Sort of like a blutooth dongle with output incan plug into my reciever.

Does this exist in a Bluetooth form?

Any ideas?
[Galaxy Note5 Accessories] naturecannon:
You look at Chromecast Audio?

https://www.google.com/chromecast/speakers/
[Galaxy Note5 Accessories] 954wrecker:
Something like this would work

http://www.amazon.com/gp/aw/d/B00MJ..._UL100_SR100,100_&refRID=08HXMB4VGMKFK8ZAHDWC

You just need to use an adapter like a left/right rca cable to a mini plug.

http://www.amazon.com/gp/aw/d/B000I23TTE/ref=pd_aw_fbt_107_img_2?ie=UTF8&refRID=0ZVB24PF5ER3EDSATVTG

OR

http://www.amazon.com/gp/aw/d/B00004Z5CP/ref=pd_aw_fbt_23_img_2?ie=UTF8&refRID=153TYK2CSTNN6N7T8GMC
[Sprint Samsung Galaxy Note5] sjr19:
Hey all. I have the stock OK3 .tar.md5 file. I've flashed it with Odin, making sure Auto Reboot and F. Reset Time is checked - everything goes fine, the phone reboots and there's no setup wizard or anything because all the stuff i had previously on my phone is on there, account info and apps.... any idea why? How can I go back to stock WITH a wipe of the phone?
[Sprint Samsung Galaxy Note5] weavr:
Factory reset first then flash with ODIN?
[Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot] DJ_URAN:
Hi all!

Does anybody know, is it possible to unlock bootloader on galaxy A3?

I try use QPST utility foк backup and restore QCN file from NV. It only possible read info from phone to file, but not write to phone.

Can anybody, who have rooted A3 with TWRP recovery help to try write QCN file to phone?

Thank you!
[Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot] tahmid_shahriar:
Samsung doesn't have bootloader actually?
[Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot] DJ_URAN:
ok. i mean if it possible to write qcn file to phone? how?

qpst utolity say write error.
[Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot] PlutoDelic:
Samsung doesnt lock bootloaders. The only locked ones i've seen are Verizon Samsung Phones.

I havent heard nor researched QCN files, care to elaborate?
[Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot] audit13:
Att also lock down some of their phones.
[Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot] DJ_URAN:
i read by qpst QCN file from phone, then try to write it to phone, but it come with error.

i want write normal imeis to qcn file (my imeis is 000000 after upgrade A3 by OTA).
[Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot] PlutoDelic:
I might be wrong, but i think the IMEI stuff is stored on the EFS partition...

Try reflashing a Stock ROM, with the Bootloader Update ticked in Odin. If that won't do it, try doing the same with a Stock ROM through SamFirm, the difference is that it doesn't download the rom as a single package, and i have managed to rescue a few Samsung phones with this method...
[Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot] DJ_URAN:
I tried use ODIN and SamFirm, but nothing. IMEIs also are zeros.

Maybe it is possible to read EFS, modify it and write to phone?
[Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot] PlutoDelic:
Im not sure, give this a try: Phone ID Changer

You are going to need Xposed Framework from arter97, and for that your rom needs to be deodexed.

Ps, i havent tried the module, but the description is quite bold.
[Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot] DJ_URAN:
Does this utility change second IMEI or just one?

My phone is dual SIM. I never saw utility for change both IMEIs.
[Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot] vishwasyd786:
Plz help me

How to unlock bootloader on my galaxy A700fd:(
[JAM, MDA Compact, S100 General] aVoKaDo-MaN:
hello i need to know i can i do my imate jam simfree

some1 maybe got tutrial?

tnx
[JAM, MDA Compact, S100 General] jaugusto:
go here:

http://wiki.xda-developers.com/index.php?pagename=xdadev_all_unlock

follow instructions for magician.
[Nexus 5 Q&A, Help & Troubleshooting] Dzinic:
I've been trying to use my Moto 360 to play music on Spotify using the OK Google function, but whenever I tell it to play a song I have to unlock my lockscreen for the song to start. As soon as I unlock the lockscreen, the song starts playing no problem. I've tried using multiple different launchers, doing clean ROM flashes and factory resetting my Moto 360 many times but the issue never goes away. I'm using the latest Cataclysm ROM and latest Android Wear. I'm starting to believe that this may be an issue with voice searching due to living in a non-US country. Has anyone else experienced this?
[Nexus 5 Q&A, Help & Troubleshooting] Chaos2Theory:
Okay so, this is actually just a problem with the spotify app(and almost all music player apps) and the way it communicates with your phone from your smartwatch. instead of having permissions to unlock your phone the app does not request them and as a result spotify lacks the permissions to do so. However in android wear you can only open up apps on the phone if you unlock the phone. Spotify may be different than other apps meaning you dont have to hit the open on phone button to sent it to your phone to work when unlocked but in general this is an issue with all android wear apps and applets.
[Nexus 5 Q&A, Help & Troubleshooting] Dzinic:
It seems when I look around on other threads people are able to play the music from their watches without a problem. I've been searching for a thread about this issue for months but haven't been able to find one.
[Desire 820 Original Android Development] fergy:
Hello there.

Here is device tree:

DOWNLOAD

from My github.

It is in Alpha (developers) release as probably You will need to fix few errors by hand....but, anyway, someone must to start with something....

Kernel is in this moment not released by HTC, but We can do some things with prebuilt kernel.

PREPARATION:

Please, after You pull it inside cm-13 source, GET VENDOR FILES by cd into device/htc/htc_a51ul and

./extract-files.sh

(with connected phone in adb enabled mode)

Second, please comment out in BoardConfig.mk following line:

TW_THEME := pure4

and uncomment:

TW_THEME := portrait_hdpi

as I wasn't release yet pure4 design skin to github.

Third, if You cannot handle "BSP" (and it's about 99% that You can't :D) comment out:

TARGET_USES_QCOM_BSP := true

and remove flag

-DQCOM_BSP

from COMMON_GLOBAL_CFLAGS

Then You are ready to build (until first error come) :p

PLEASE, don't take advantage with this if You really don't know how to handle errors as I will NOT help or respond on PM's regarding help about building this.

When something come up, will make post/and/or attach possible working image.

Cheers

EDIT1: dts is attached, so if someone like to play with kernel... Check it out. I will put changes to 64bit kernel on My github soon with this device tree.

EDIT2: kernel is updated. You can grab it on

MY GITHUB

EDIT3: BoardConfig.mk is changed, so no need to change twrp skin and BSP (steps second and third).
[Desire 820 Original Android Development] SK00RUPA:
Thank you, btw. great job! ;)
[Desire 820 Original Android Development] kinghunki:
Great beginning!
[Desire 820 Original Android Development] fergy:
So, things changed... Kernel updated, device tree updated, read.me updated.

Please be free to pull Kernel and make changes so We can got it working. I was made first steps and don't have so much time to make all this together work but if few of dev's come aboard and take work, We can make it work soon.
[Desire 820 Original Android Development] Thecrazyskull:
So i am quite interested in this device, don't own it yet so [MENTION=352916]fergy[/MENTION] would appriciate it, if you could push vendor (too much work to do it all manually, especially the makefile :p).

Thanks.
[Desire 820 Original Android Development] fergy:
List of vendor files are under my github device tree... When you extract files, makefile will be builded under vendor/htc/devicename ;)
[Desire 820 Original Android Development] Thecrazyskull:
I know that, but since i don't own the device i can't pull blobs using the script (obviously), so it would be awesome if you could create the vendor (run the script), git init and push :)

btw i remade the device tree based on the htc a5, looks much better now: https://github.com/Thecrazyskull/device_htc_a51ul

Thanks.
[Desire 820 Original Android Development] SK00RUPA:
https://github.com/Skorupa123/vendor_htc_htc_a51ul

Recently I uploaded it, so, enjoy! :D
[Desire 820 Original Android Development] Thecrazyskull:
Thanks a damn lot!!!
[Desire 820 Original Android Development] Dragonfail:
[MENTION=5083850]Thecrazyskull[/MENTION] Do you make cyanogenmod?
[Desire 820 Original Android Development] Dragonfail:
[MENTION=5083850]Thecrazyskull[/MENTION]

I know that fergy aboneded our project.. But you.. Do you continue? Can i help you?
[Desire 820 Original Android Development] Thecrazyskull:
I pretty much lost interest, especially since i dont want to develop without owning the device.
[Desire 820 Original Android Development] Dragonfail:
I can help you.. please.. continue...
[Desire 820 Original Android Development] Thecrazyskull:
Its a pain for myself, and i don't wanna go through that so i won't be developing for this device anymore unless i can get my hands on one (very unlikely)
[Desire 820 Original Android Development] chitranjn_k:
What is thts device tree not understanding
[Desire 820 Original Android Development] Thecrazyskull:
This is not really the place to ask...
[Desire 820 Original Android Development] QkiZMR:
If you don't understand it you don't need it.

Wysłano z Tapatalk / Sent with Tapatalk
[Desire 820 Original Android Development] nilaydani:
Any idea about htc desire 826 dual sim i.e. a52_dtul device tree ?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] LysolPionex:
I successfully installed Safestrap and it never really seemed to work (some ROMs would load and not everything on the phone worked, some ROMs just bootlooped etc.), so I just used stock.

I tried installing a rooted Lollipop stock ROM to a different safestrap partition, and when I restarted the phone Safestrap no longer started up. I could get into download mode and recovery mode (not TWRP/CWM just regular recovery), but the normal boot would show a screen saying "System software not authorized by AT&T has been found on your phone."

Since Safestrap was no longer loading, I tried flashing the stock jellybean kernel with ODIN, and is gave me a FAIL! (Auth) (Complete(Write) operation failed). I then tried repartitioning with the pit file, and it gave the same error.

It seems I can't flash with ODIN (I'm guessing because of Safestrap?) and for some reason Safestrap won't show up either. Any ideas?

Edit:

When trying to use ODIN, my phone displays:

ODIN MODE

PRODUCT NAME: SGH: I337

CURRENT BINARY: Samsung Official

SYSTEM STATUS: Official

KNOX KERNAEL LOCK: 0x0

KNOX WARRANTY VOID: 0x1

CSB-CONFIG-LSB: 0x30

SECURE DOWNLOAD: ENABLE

WRITE PROTECTION: Enable

eMMC BURST MODE : enabled

START [224, 1440]

SW REV. CHECK FAIL: fused: 5, Binary: 4
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] jmjoyas:
You have to flash a higher version. The last line in the output indicates that the fuse count of the bootloader on the phone is 5 vs the one you are flashing is 4
[Xperia Z5 Q&A, Help & Troubleshooting] EricLeRouge:
Hi folks,

I've been reading a lot about rooting android phones and now that I have a Z5 Dual, I would like help to define if it is pertinent or not to root my Z5.

Context: I haven't bought mine through a carrier, I do not have bloatware (but Sony's).

And with recent Android releases and the M forthcoming, why should I be rooting my Z5.

I've seen posts here about people doing so with their Z5. I would like to know why also.

Is looking to use orbot and orbweb for increased anonymity a sufficient motivation?

Thanks for your advices.

Eric
[Xperia Z5 Q&A, Help & Troubleshooting] Hobbes2099:
The only way to root the device -as of today- is to open the unlocked bootloader of your device. This means losing permanently your DRM Keys which reduces photograph quality and access to PlayStation services (PSN app, Remote Play, among others).

If you plan on reselling your Z5 for maximum profit, losing your DRM keys will significantly lower the value of your device.

I would recommend remaining unrooted for a couple of months and wait for more refined rooting methods to emerge.
[Xperia Z5 Q&A, Help & Troubleshooting] EricLeRouge:
Thanks for this answer, it gives me a good "cons" - as of today - like you say.

But considering that one day a proper rooting method is found, what would be the "pros" of rooting, regarding all the options already in stock android.

What would I be getting more ?

Have a good day

Eric
[Xperia Z5 Q&A, Help & Troubleshooting] Lambo16:
Nothing if you don't what to use root access for, I would say it's for more advanced users that really want to maximise their device's potential and customise it to their likes
[Xperia Z5 Q&A, Help & Troubleshooting] EricLeRouge:
Thank you.

I understand your answer and it does make sense. I won't consider myself as an advanced user indeed, but I would like to know what I would have access to doing so.

I am interested in diving into rooting and as my readings went I understand that I can (most of the time) increase the efficency of the phone and this is what I am looking for. (i.e battery usage, reception, etc...).

However I am also interested in more secure ways to communicate and is rooting an answer to that ? I am curious.

Thanks.
[Xperia Z5 Q&A, Help & Troubleshooting] Lambo16:
What do you mean more secure ways to communicate? And as another user said rooting is not worth it at the moment as you loose DRM key. I would wait for a better root exploit and also if I were you I would also wait for your device's warranty to run out.

At this point, there is not much I would root my device for apart from trying to get extra battery life. I used to have a rooted Xperia Z1 mainly so I could over clock it and install camera mods, which I don't need anymore.

tl;dr I would wait till your warranty runs out (1 year for me) and wait for a better root exploit.
[Xperia Z5 Q&A, Help & Troubleshooting] mohiuddin1111:
dont do it. it will void warranty... And stock is not bad i guess.
[Xperia Z5 Q&A, Help & Troubleshooting] Hobbes2099:
Eventually you'll be able to root with no consequences; DRM keys will be left untouched and dependant apps will perform as always. Just not yet.

Regarding the abstract benefits of rooting the Z5? Better control of OS components and a general feeling of self realization.

Specifically, after rooting, you could install the xposed framework and tinker with every minutia imaginable. My Z3 lasts 3 days with no charge. While I can barely make it through the day with my Z5. To paraphrase The Martian, I'm gonna science the **** out of it.
[Xperia Z5 Q&A, Help & Troubleshooting] mrbubba999:
Did this happen for the Z3?

I'm about to upgrade from a Nexus 5, I've always rooted my phones, ran a stock rom and then used xposed to customise the look.

I'm hoping I can eventually do this with the Z5, but I guess its a waiting game, will just have to get used to non root :D
[Xperia Z5 Q&A, Help & Troubleshooting] EricLeRouge:
Thanks for your answer, it gives much more visibility on what I should be able to tinker with after root - when available in a proper form.

As for Lambo16, I was reading about being able to get more security after rooting as you get more control over kernel and so. Then I was wonderring how much of a difference it would do with actual android stock rom.
[Xperia Z5 Q&A, Help & Troubleshooting] Lambo16:
You still need to know what to do. I wouldn't know how to change any of that stuff.

I will probably root my device as soon as I loose warranty and when there is a better exploit.
[Xperia Z5 Q&A, Help & Troubleshooting] Hobbes2099:
Eventually it did. Rooting for locked bootloader was available for the Z3 by the time I got my Z3. I was able to get my Z5 much earlier this time.

Through a combination of Prime Launcher and disabling specific apps and disabling app notifications, I was was able to mask bloat ware (Xperia care, Xperia lounge, what's new, others).

Unfortunately, this superficial tweaking kept the battery untouched. So I wait. Meanwhile, I enjoy my Sony Xperia Z3, rooted, hibernated and xposed.
[Nexus 6 Q&A, Help & Troubleshooting] Rbh50815:
OK I got the notification to update today it's MMB29S, I am on K. I am rooted but stock, unlocked using systemless root for root. I've always been rooted and expected it to fail and have to install manually but this time because I'm not rooted like the old way. So i downloaded and went to install to my surprise dead Android with the triangle didn't show but it went to custom recovery screen twrp. I just hit restart because I've never not had a fail and never seen it do this before. Well when it restarted I was not updated and still on K. I also for the life of me can't get it to redo the ota. Tried to clear system service in apps and recheck but nothing.

So my question is since I'm new to systemless root what should I have done when it went to custom recovery? So that way if I can get it to pop up again I can be updated. Thank you in advance for any help and it would be awesome if possible to update this way without having to manually do it.
[Nexus 6 Q&A, Help & Troubleshooting] dahawthorne:
My best guess, based on what Chainfire replied to me when I asked about OTA, is that because you're somehow rooted the OTA will refuse to install. He said that using the "unroot" function in v2.63 (and I suppose in subsequent versions) he was able to apply the OTA and then just had to re-root.

As to the OTA, I read in the long-distant past that once it's been provided to your device you sort of go to the back of the queue, and even pressing the "check for system update" button has no effect. One day your turn will come again. When it happens, before you press the "install now" button, use the unroot function, reboot, and give it another go.

And I would really appreciate it if you could report back on the success or failure, just so we all know - thanks...

And before I close... your alternative is just to download the full ROM from Google, unzip everything in sight (including the zip within the zip), copy system.img to a convenient folder, and use Fastboot to flash system. After that you'll need to re-root (simple flash) and when you reboot everything will be as it was, apart from the version and security update date. I did it myself to MMB29S a week or so ago.

But my lawyer advises me to advise you to take a full backup first and store it off your device before you do anything to your device - just in case, you know? :)
[Nexus 6 Q&A, Help & Troubleshooting] Rbh50815:
I will definitely reply if I get the update again in a few days. If it doesn't I'll probably do it manually. I was just really surprised I hadn't gotten the error, just so used to it. Thank you for the info though.
[Nexus 6 Q&A, Help & Troubleshooting] butterbeanmash:
Correct me if I'm wrong, but to install an OTA don't you need to be completely stock, including recovery?
[Nexus 6 Q&A, Help & Troubleshooting] Rbh50815:
If I'm not mistaken but since 4.3 (I'm probably wrong) if your rooted (before systemless root) when you try to the ota you will always get the dead Android because rooting changes the system files causing the update when it does is checks to think your system is corrupt.

Also it was really bad when people tried going from 5.x.x to 6.x even doing it manually some of us got bootlooped or when starting the phone up after updating manually saying system is corrupt but still starting up fine. Leaving like me having to completely clear out everything and installing the factory image just to not be corrupt and able to use Android pay.

Systemless root though I've not had a single problem and still able to use AP. And is also the first time in years I've gotten as far as I did with the OTA.
[Nexus 6 Q&A, Help & Troubleshooting] StykerB:
These small ota's can be done with boot modifications because they don't include any boot.img changes and if they do then they just blanket overwrite what's already there. The only part that is checked is /system. However TWRP won't ever install an ota update for compatibility reasons. Even if you reflash the stock recovery then you'll fail the ota because when you installed TWRP it protected itself (by modifying /system) from being overwritten by the stock recovery which is what unmodded stock android will always do on boot by default. And there are 2 things the ota verification looks for when updating: 1. It looks for whether /system has been ever mounted as Read/Write. 2. It hash checks the /system, if it finds any mismatch it fails. As for the update not showing up again, the ota checker hides the update after a failure to stop from flooding the download server. If you want to extract the update zip you can look in /cache for the zip. But since you don't have an unmodded /system you might as well just download the newest factory image and manually flash the system.img
[Nexus 6 Q&A, Help & Troubleshooting] aiiee:
You can use Wug NRT, unroot with MMB29S provided in the NRT , then root.