yashsingh1/xdaforums huggingface dataset:
[One (M8) Q&A, Help & Troubleshooting] Andyw2100:
DJR83--Do you think the differences we are seeing could be due to different phone setups / manufacturers / rooting methods? Because if not, I'd love to get my light to be able to stay on with the screen on, the way yours does, and also come back on, after the screen has been on, once it is off again, if the alert has not been cleared.

Would you mind taking a look at the settings I described a few posts back, and see if I missed anything that you've done?

Thanks!
[One (M8) Q&A, Help & Troubleshooting] djr83:
My thoughts about this is that it's all controlled through software, even some of the limits (not the color limits of course). My old Nexus 4 couldn't have the LED on while the screen was on, yet it still happened sometimes anyway. Obviously not a hardware limit then.

Root may of course be needed (I have root) but I don't believe rooting methods matter.

If I can get it to stay on, then I'm sure you can too.
[One (M8) Q&A, Help & Troubleshooting] EddyOS:
That user is randomly replying to posts or copying/pasting replies - ignore them! :D
[One (M8) Q&A, Help & Troubleshooting] keijers:
I would really reproduce your settings. But I can't figure out how. The only thing is (maybe) that my phone is not rooted.

When I select direct mode and the alternative direct mode, it doesn't work at all. With direct mode it works only with the green light (flashing, not solid)

Could you please tell me your settings? Or make a screenshot of it?
[One (M8) Q&A, Help & Troubleshooting] djr83:
Since this seems to be a problem many are having, I've made a guide for it: http://xdaforums.com/showthread.php?p=52101531
[AT&T, Rogers HTC One X, Telstra One XL] Jaguarandine:
Hi. I'm a newbie on these forums, so please be easy on me. My father recently decided that he wanted to enter the smartphone world and decided on a One XL. He bought it on eBay from a Chinese seller, so I'm pretty sure the One XL is the Chinese variant w/ the 2600 band for LTE.

I'm generally a BlackBerry guy (currently own a Z10), but have used all the phone OSes at some point. I've been pretty comfortable modifying my own BlackBerry, I use Linux at home as my main OS, and I'm also a computer science major studying programming (so I'm not in over my head here).

There are few things that I think would be cool for my Dad:

1) LTE speeds on T-Mobile. If not, 3G or HSPA

2) Android 4.4 KitKat

3) Sense 5

I'm pretty familiar with sideloading so that shouldn't be a problem (Flappy Bird).

I hope my Dad didn't didn't mess up for himself by buying the Chinese version if he wants faster speeds (than EDGE) on T-Mobile. I appreciate any help you may give. Thank you!
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
You should have no problems getting LTE on the device. You can have KitKat but it will be via an aosp ROM, not Sense. Sense ROMs for our device only go up to Android 4.2.2 and that's probably where they'll stay.

If you want to run a custom ROM on it just head over to htcdev and unlock the bootloader, then you can install a custom recovery, and from there you can install a custom ROM. I have detailed instructions for many of these operations in my How-To Guide For Beginners thread in my signature. You should also read the Evita FAQ thread in my signature, and bookmark the resource thread.

What are the bootloader details on the device? To boot into the bootloader there are two methods.

With phone powered on

Hold the volume down button, then hold the power button (so you're holding both buttons together), the button lights will start to flash, they will stop flashing and the screen will go blank, after a couple of seconds let go of the power button but continue to hold the volume down button until you reach the white screen with text, this is your bootloader.

With phone powered off

Hold the volume down button, then hold the power button (so you're holding both buttons together), after a couple of seconds let go of the power button but continue to hold the volume down button until you reach the white screen with text, this is your bootloader.

Please post the first five lines.
[AT&T, Rogers HTC One X, Telstra One XL] Jaguarandine:
Thanks! My dad can live without KitKat. Here's the bootloader details:

EVITA PVT SHIP S-OFF RL

CID-11111111

HBOOT-1.09.0000

RADIO-0.16a.32.09.17_2

OpenDSP-v25.1.0.32.0405

eMMC-boot

Apr 2 2012,21:08:24

EVITA
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Well you got really lucky and bought a device that's been modified in the past. It already has s-off and SuperCID (11111111). That's half the work done for you. What does it say above those lines though? It should say locked/unlocked/relocked and possibly also tampered.

Your firmware is a bit outdated so you'll need to update that, which will be easy because you already have s-off on the device. Before we go any further I need the other lines from the bootloader though.
[AT&T, Rogers HTC One X, Telstra One XL] Jaguarandine:
I'm at work now, and left the phone at home. I believe it said unlocked. I'll be able to work on this some more in a few hours. Thanks for all your help so far.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
No problems. I'm subscribed to this thread so just pop in later and we'll sort you out. If it does say unlocked that leaves very little actual work for you to do, it's pretty much all been done. One thing you will need to do though is to install adb & fastboot on your PC, if you Google "minimal adb & fastboot" the first result will be an XDA thread which details how to do it, that's the easiest way. Another thing you'll need to do is install HTC drivers on the PC, the best way to do this is to install HTC Sync Manager and then connect your phone (first while booted into the OS, and secondly while in bootloader mode), this should install the drivers automatically. Once you've done that you test it by doing the following:

Navigate to the folder where adb.exe and fastboot.exe are located on your PC, shift + right click, select open command prompt here, then issue these commands:

adb devices

(While booted into Android)

fastboot devices

(While in bootloader mode, with "fastboot usb" showing on the phone screen)

Each command should return the serial number of your device. While you're issuing the adb command make sure your screen is on and unlocked because you may see a prompt asking to grant access which you need to confirm.

Before doing this you will also need to navigate to /settings/developer options on the device and enable usb debugging. If developer options doesn't appear in your settings you just need to navigate to /settings/about phone, then find the "build number" category and tap it about eight or so times, this unlocks developer options.
[AT&T, Rogers HTC One X, Telstra One XL] Jaguarandine:
So it looks like my Dad bought a used phone, right? With everything that's been done, I'm not sure if that's a bad thing or not. Since my Dad wouldn't be happy, I do think I'll keep this little detail between us though ;)

4.2.2 + Sense is better, right? I wouldn't want to shoehorn KitKat on here if there are some features missing and the performance is not as good.

Btw out of curiosity, do these programs have a Linux equivalent? If not, it's cool, I have a Windows machine at home too.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Oh yeah, the phone is without a doubt pre-owned. Whether Sense or aosp is better is a matter of taste, and your dad won't really know which one is best for him unless he's able to play with each of them for a few days to get the feel of them both.

I had forgotten you mentioned having Linux as your main OS at home, and yes adb & fastboot are Linux compatible, they're actually much easier to install because they don't require drivers on Linux. Just Google how to install them on Linux, you should get a bunch of results with clear directions.
[AT&T, Rogers HTC One X, Telstra One XL] Jaguarandine:
Well, I was wrong. The top line says *** LOCKED ***. Looking for the other programs now.

Edit: Took me a while, but I was able to find and get the drivers working in Ubuntu successfully

marcus@marcus-laptop:~$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT288W303498	device

After going into bootloader, and entering fastboot mode, I get the following:

marcus@marcus-laptop:~$ sudo fastboot devices
HT288W303498	fastboot
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Ok, that's good. Your bootloader is actually in a relocked state but the previous owner has spoofed it to say locked, that's my guess anyway. Either way, your next step is to head over to htcdev and dole the directions there to unlock your bootloader. You can skip the installing fastboot part obviously.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] Jaguarandine:
Ok, bootloader now says unlocked.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Cool. Now is the point where you need to upgrade the firmware on the device. This is pretty straight forward command line stuff using fastboot.

Download the firmware from here:

http://www.androidfilehost.com/?fid=23060877490004040

Place it in your fastboot folder (the folder where you have fastboot located on your PC). Rename it to "215firmware.zip" to make things easier later on. Open a command prompt from within that folder, or just open a command prompt and use the CD command to change directory to that fastboot directory. Connect your phone in fastboot mode and issue this command to make sure your connection is good:

fastboot devices

Once you've established a working connection (it'll show your serial number) you can start the process with this command:

fastboot oem rebootRUU

The phone will not boot into rebootRUU mode which is a black screen with the HTC logo. Now issue this command:

fastboot flash zip 215firmware.zip

If the output ends with "FAILED (remote: 90 hboot pre-update! please flush image again immediately)", run the previous command again. If it ends with "INFO..... OK", just reboot to the bootloader with this command:

fastboot reboot-bootloader

Verify everything was successful by looking at the hboot version and radio version in the bootloader screen. They should be as follows:

Hboot: 2.15

Radio: 1.31a.32.45.16_2

Now just reboot your phone by issuing this command:

fastboot reboot

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] Jaguarandine:
Very detailed instructions, thanks! everything Seems to be working well and Hboot and Radio have been updated.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
You're doing well, all that's left to do now is to flash TWRP recovery and install a ROM. You'll need to decide what kind of ROM you're going to flash because currently Sense ROMs and KitKat aosp ROMs need different recoveries.

For any Sense ROM you can use this recovery:

http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.6.3.0-evita.img

For any KitKat aosp ROM you need to ue this recovery:

http://www.androidfilehost.com/?fid=23252070760973615

Once you've installed the recovery you will need to make a backup of your current system just in case anything goes wrong in future, or if you want to use it again. Check the How-To Guide For Beginners thread in my signature for detailed instructions on how to do that.

Once you've done that you can go ahead and find a ROM you want to install and flash it. Our two develpment sections are as follows:

Android Development

(for Sense ROMs)

Original Android Development

(for aosp ROMs)

Once you've picked one you can download it and head back to my guide thread for full instructions on how to flash it.
[AT&T, Rogers HTC One X, Telstra One XL] rc420head:
[MENTION=4153349]timmaaa[/MENTION] your awesome dude, keep up the great help you offer :thumbup:

Sent from my One using Xparent Red Tapatalk 2
[AT&T, Rogers HTC One X, Telstra One XL] Jaguarandine:
I started noticing this strange flickering on the sides of the screen. The screen is fine on a white background or when the brightness is turned down. But as soon as color is introduced on a white background, the flickering starts. Is this normal? And will it go away?
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Was this happening before the firmware flash? Is it happening since the firmware flash?

---------- Post added at 04:00 AM ---------- Previous post was at 04:00 AM ----------

Thanks buddy, appreciate it.
[AT&T, Rogers HTC One X, Telstra One XL] Jaguarandine:
Well, I've never noticed it before. I am however, using the phone a lot more regularly since I started updating it. I looked around, and it seems to be an issue a number of people have with the screen. I'll deal with it for now and see if gets any better. Brightness levels won't be too high most of the time anyway.

I think I'll choose Sense 5 and start installing the recovery.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
It could simply be a mismatch between the firmware and whatever software version is currently installed on it. Or it could be a hardware defect. You could try running an RUU to rule that out, but that would require a Windows machine with adb/fastboot plus drivers.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] Jaguarandine:
Now it's gone away. I dunno. The phone otherwise seems fine. I'll keep observing and if anything happens, I'll report back here.

Recovery installation went well. Now on to flashing the ROM.

Out of curiosity, which ROM do you have on your phone?

One thing I did notice is that some ROMS recommend Jellybean should be installed. Is that an issue for this phone?
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
I'm a fan of aosp so I usually bounce between a few of the aosp KitKat ROMs, right now I'm running KarbonKat. I think what you're referring to is the Jellybean firmware, you can either get that via the 3.18 RUU or the firmware you've just flashed so you're good to go.

The advantage of flashing the firmware that you flashed is that it covers you to be able to run aosp ROMs and Sense 5 ROMs. Sense 5 ROMs actually need that specific firmware otherwise random reboots and signal losses would occur. Aosp ROMs need anything above Jellybean.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] Jaguarandine:
You're right. They were referring to the firmware. I think I'm going to install CleanROM 7.0R2.
[AT&T, Rogers HTC One X, Telstra One XL] Jaguarandine:
After installing, I've been using the phone as my main all day. On the train, at work, and back again. So far it's held up very well. Although I do miss the BlackBerry gestures, lol. That flickering has not been seen again, but it shouldn't bother my dad too much overall. This screen on this phone is still extremely nice! I'm confused about why we need 1080p again.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Cleanrom is a nice simple and stable ROM, I think you chose well. This display is 720p with a DPI (or PPI) of 320, which is perfect for a screen of this size. The human eye isn't actually able to distinguish the difference between 720p and 1080p on a display this size.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] Jaguarandine:
Do I have to do anything else for the radio to work with T-Mobile (other than APN settings)? Everything else seems to be working fine.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
All you need to do is set up the APN settings I believe.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
T-Mobile where, US?

T-Mobile is deploying their LTE network on the AWS band (1700/2100 MHz) which is a fairly unusual one, so I'd be surprised if a version you stated supports this LTE band.

Similarly, T-Mobile US uses the AWS band for HSPA, but migrating some markets to 1900MHz band (to free up the AWS spectrum for LTE). So you will need compatibility with one of those in order to get HSPA data service.

Band compatibility needs to be one of the primary things you look at before buying any device from a 3rd party source (other than your carrier).
[AT&T, Rogers HTC One X, Telstra One XL] Jaguarandine:
My Dad lives in Fayetteville, NC. With the new radio, I was able to get LTE on AT&T. I live in the SF Bay Area. My little sister, who lives with my dad, recieved an unlocked AT&T from me. She is able to pull down HSPA on that phone (Lumia 520). So the One XL should get HSPA as well. Unless there is a specific T-Mobile LTE radio out there, this should work quite well.

Btw, because the phone was used, I was able to get a partial refund of $35 from the ebay seller. So $182 for a good condition phone is pretty good.
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
If you mean your sister has HSPA on T-Mobile (using an unlocked AT&T phone), this is due to either:

1) T-Mobile is using 1900 MHz for HSPA in that area (as I mentioned). Most all smartphones from AT&T branded support 1900 MHz HSPA, as the bands they use are 850 and 1900 (depending on the market region).

2) There were a number of phone models released by AT&T that supported AWS (1700/2100) when they were planning the now aborted merger with T-Mobile. Not sure if the Lumia 520 was one of them (I don't follow Windows Phone much at all).

The phone needs to support the band(s) used by T-Mobile for LTE and/or HSPA. That is all there is to it. Speculating what "should" or shouldn't be isn't going to matter if the hardware isn't configured for it.

If the support for the AWS LTE band is not already present in hardware, flashing a radio will not change that.

There have been some instances of flashing a radio on the previously mentioned AT&T devices "unlocking" support for the AWS band on T-Mobile's HSPA network. But the support for this band was already present in hardware. It was just "hidden" by the radio software.
[AT&T, Rogers HTC One X, Telstra One XL] Jaguarandine:
Thanks, I appreciate your help.

Using gsmarena.com as a guide, the One XL supports HSDPA 850 / 900 / 1900 / 2100, which is enough for 3G and HSPA in the Bay Area. The Lumia 520 supports HSDPA 850 / 1900 / 2100, which is good enough for "4G" on T-Mobile in NC. The real question mark for me is LTE. It worked for me, but the Chinese variant probably shares the same hardware as the AT&T version. I guess we'll just have to see.
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
How are you coming to these assumptions? On the GSM Arena page, it says LTE bands 1800 and 2600 MHz. If that is true, its not the same as the AT&T's version, which supports LTE 700, 1700, and 2100 MHz.

http://www.gsmarena.com/htc_one_xl-4572.php

http://www.gsmarena.com/htc_one_x_at&t-4614.php

The 1800 and 2600 bands seems to make sense for China, according to this: http://en.wikipedia.org/wiki/List_of_LTE_networks
[AT&T, Rogers HTC One X, Telstra One XL] Jaguarandine:
The Chinese variant is the phone I have for my dad. This phone was able to get LTE in the Bay Area.
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
Then that would mean the GSM Arena specs are incorrect (not surprising, this is often the case). Unless you can find the band support specs for that exact variant, you really have no way of knowing it will get LTE (or HSPA for that matter) until your dad puts his SIM in.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
I have the Hong Kong variant and I'm pretty sure the LTE bands supported are 1800/2600, whether there's another Chinese model available I'm not sure though but I think this is it.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] Jaguarandine:
It's a mystery! Lol. The ebay seller that we bought the phone from advertises the same bands that gsmarena shows for the One XL. I really think swapping out the radio gave the XL the ability to use ATT bands for LTE.

I guess we'll find out soon enough because I just shipped the phone off to my dad. I decided to use the T-Mobile 3G APN settings rather than LTE. If he's so inclined, I'll work with him to change them should he want to test LTE down the road. But it shouldnt bother him much; he's not a power user. I'll be sure to report back here when he gets it.
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
Only if the support was already in the hardware, and just not advertised, and otherwise "hidden" by the radio software. Its possible, as I pointed out its happened on several AT&T devices during time frame of the aborted T-Mobile merger. The support for the T-Mobile HSPA bands was not in the advertised specs, but folks were able to get support by flashing a radio. So we might have a similar case here.

What radio did you flash? Did you measure LTE type data speeds, and if so what were they?

Its interesting. I also wonder if its the case where its just cheaper for them to mass produce hardware that is all identical, then disable/enable bands with software as needed. This actually happens a lot in electronics, where things like hard drives and DSLR cameras (the examples I've heard of) where the various price tiers are actually all the same hardware (cheaper for them to just manufacture them all the same), just different capacities or features are disabled with software, depending on what tier model you purchased.

Maybe more band support gets "hidden" than we know about. Of course, there isn't much way of knowing except trial and error.
[AT&T, Rogers HTC One X, Telstra One XL] Jaguarandine:
I used the radio timmaaa recommended. You can see it earlier in the thread. As for the LTE, I just saw that it had it, and was noticeably faster. I did no benchmarks.*

On another note, does the One XL have a good amount of oleophobic coating, like the other contemporary flagships? I found that it accumulated fingerprints very easily, compared to the Z10, Galaxy, etc. It could be because the phone is used. Shouldn't be a problem for my dad; I got him an Otterbox case.*

Btw, thanks timmaaa for all the help. It was very easy, following your directions. I expected at least a couple roadblocks, but everything went smoothly. Probably helped that it also had s-off and CID too ;)
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Mine shows up fingerprints pretty easily too, I don't really worry about it all that much though. I used to keep a case on it but it looked so damn ugly with it on, and it looks so damn beautiful without a case lol. You're welcome, it's no problem, I'm always willing to help out especially when the person I'm helping has more than a couple of brain cells to rub together.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] Jaguarandine:
Hi everyone. Small update. I've spent most of the time with my dad trying to get him used to the phone. It's taken hours of phone calls, but I think he's getting it. :) Anyway, after trying many APN settings, we settled on fast.t-mobile.com. In his house, he's only capable of getting EDGE. However, when he's driving around town, he can get anywhere from 3G to LTE. So LTE is confirmed I guess. I'll have him do some benchmarks on the speeds later. I have to teach him how to use the Google Play store first. ;)
[T-Mobile Samsung Galaxy S 5] njdevils28:
Hi,

Does anyone have a procedure for changing the APN Settings?

I'm trying to use the WiFi Tether for Root App and it requires the T-Mobile APN Setting to be IPV4 instead of IPV6. My APN Settings a Grayed out and I'm unable to change them.

Any Help is appreciated

Thanks,

-NJ
[T-Mobile Samsung Galaxy S 5] jpeps:
WiFi tether not working from from Google play
[Huawei Ascend P6, Mate] FranticOgre:
Hi there fellow xda users!

Today my father decided it was finally the time to root and change his rom on his ascend p6 after seeing how flawless my note 3 with a custom rom runs.

So, the problem is the following: after he had rooted his phone with kingo root (if I recall) he tried to install cwm recovery using the app on the market. During the instalation, it stucked and went into a boot loop. I tried to put in download mode tho I am not sure if it has download mode and I've searched on the internet for it and didn't find anything. I have to mention the fact that I can get it into stock recovery but from that point I can not do anything. It will show "FAIL" as soon as the recovery starts.

Any way to fix this problem?

A fast response will be much appreciated, thanks for the assistance