yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers HTC One X, Telstra One XL] undivide:
I have this problem connecting to my 5ghz network at home though I'm not sure if this is a cm11 issue as my wife's nexus 5 can see the 5ghz network but wont connect to it either (stock 4.4)

I don't have any other devices to test on this ea2700 router. I'm just using good old 2.4ghz for now.

update: would like to mention after performing a 30-30-30 reset on my router and reconfiguring the wifi settings my phone now connects to the 5ghz band again here at home.
[AT&T, Rogers HTC One X, Telstra One XL] SoulSurvivors:
Question

Hi!

I have issue with installing CM11. Log says "Unable to find partition for path /sdcard"

I have a little bit of **** ups due to me being an idiot such as ruining sdcard to the point of it refusing to be mounted to pc or opened via TWRP file explorer.

Now it can be mounted to PC and can be explored via TWRP.

My device info:

sdcard partition type: FAT32

bootloader version: 2.14

Security-OFF

CID: 11111

Custom recovery: TWRP 2.7.00
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
You just need to update your recovery to the 2.7.0.8 version.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] marknoll:
Yes. I'm aware of those posts. But they still don't explain it..well.thank u anways.
[AT&T, Rogers HTC One X, Telstra One XL] tjhooker73:
What are you looking for then? It explains it fine.
[AT&T, Rogers HTC One X, Telstra One XL] marknoll:
Wow. No need to be rude
[AT&T, Rogers HTC One X, Telstra One XL] undivide:
numbers not responding.

not sure why this happens but it only occurs in the dialer from within a call not the dialer used to make an initial call.

most of the time the "3" key is completely unresponsive and sometimes the 6 key as well and further complicating things the 9 key sometimes gets hung or stuck on after it is touched. all of the numbers in the middle are hit or miss and the numbers to the far left work with no issues.

running latest snapshot with torched kernel though this issue shows up on the cm kernel as well.

I've also had this occur on some nightly builds though I haven't flashed a nightly since the last snapshot came out.

update: just wiped everything and installed a fresh 5/24 nightly - number keys still not working from within a call. this proves very difficult to access my voicemail... ugh, should I go to a CM10 rom?
[AT&T, Rogers HTC One X, Telstra One XL] marknoll:
Yea. Unresponsive screens happen on these builds. A simple reboot will fix it
[AT&T, Rogers HTC One X, Telstra One XL] felixrising:
freezes continue

Hi,

I updated to 2.7.0.8 a few weeks ago but am still seeing the same freezes and random lock-ups and sponteneous reboots... I'm posting bug reports as often as it happens but still no dice after almost a month of daily hell.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Which build are you running?

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] felixrising:
CM Version: 11-20140523-NIGHTLY-evita cm_evita-userdebug 4.4.2 KVT49L 45c2548437

Baseband version: 1.26a.32.45.19_10.134.32.34aL
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Interesting, you shouldn't be experiencing those bugs on that build. Are you running the stock kernel or custom? Do you experience the same issues on other aosp ROMs?

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] felixrising:
I have not tried any other ROMs, I only use stock kernel.

It's anecdotal but my colleague is running similar recent build on his Samsang Galaxy Nexus (maguro) and also experiences this freeze/reboot issues.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
I'd suggest maybe testing another ROM, like Carbon or EOS, just to see if you encounter the same problems.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] Notorio:
Never mind...
[AT&T, Rogers HTC One X, Telstra One XL] dr.scofield:
Hi

I'm trying to edit updater-script so i can install cm on my 2.10 hboot and its related firmware .. so i replaced hboot lines in updater-script file (2.14 , 2.15 , 2.16 ....) with 2.10 but it gives me error related to updater-binary while installing .. any suggestions ??
[AT&T, Rogers HTC One X, Telstra One XL] marknoll:
Idk if altering that is gonna help. Why don't u just run 5.18 ruu and new recovery twrp 2.7.0.8?
[AT&T, Rogers HTC One X, Telstra One XL] dr.scofield:
Because i have a different variant ..mine is Evita_utl not ul
[AT&T, Rogers HTC One X, Telstra One XL] marknoll:
From what I understand an Evita is an Evita. Long as ur s off u could just flash that ruu..but I could be wrong
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Whoa! Noooooo, you're very wrong, that advice will cause a brick. The middle eastern variant (Evita utl) cannot install any firmware, hboot, radio, or RUU from the standard Evita. Only ROM installs are ok.

Sent from my Evita

---------- Post added at 09:45 PM ---------- Previous post was at 09:45 PM ----------

Which version of TWRP are you running?

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] marknoll:
Omg. I am so sorry. I must've misinterpreted..
[AT&T, Rogers HTC One X, Telstra One XL] dr.scofield:
Don't worry .. I already bought this phone bricked by flashing this ruu and i fix it

thanks for reply timmaaa .. mine is official 2.7

openrecovery-twrp-2.7.0.0-evita.img
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
No harm done.

Sent from my Evita

---------- Post added at 10:15 PM ---------- Previous post was at 10:15 PM ----------

You need to update your recovery, the 2.7.0.8 version is required.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] dr.scofield:
Ok I will ,but one thing .. when i was on 2.18 hboot I installed this rom with 2.7.0.0 twrp !!!!!!!

and my error right now after editing updater-script is related to updat-binary
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Things have changed, the latest builds use an updated fstab layout so you need a recovery version that is compatible with that.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] dr.scofield:
in 2.7.0.8

E:Error executing updater binary in zip '/sdcard/cm11.zip'

Error flashing zip '/sdcard/cm11.zip'

same error in 2.7
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
What exactly did you change in the updater script?

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] dr.scofield:
assert(getprop("ro.bootloader") == "2.14.0000" ||
getprop("ro.bootloader") == "2.15.0000" ||
getprop("ro.bootloader") == "2.16.0000" ||
getprop("ro.bootloader") == "2.17.0000" ||
getprop("ro.bootloader") == "2.18.0000");

to:

assert(getprop("ro.bootloader") == "2.10.0000" ||
getprop("ro.bootloader") == "2.10.0000" ||
getprop("ro.bootloader") == "2.10.0000" ||
getprop("ro.bootloader") == "2.10.0000" ||
getprop("ro.bootloader") == "2.10.0000");
[AT&T, Rogers HTC One X, Telstra One XL] marknoll:
Anybody ever hear of the twisting thing? Like sod. Anyone know what may cause this?
[AT&T, Rogers HTC One X, Telstra One XL] jrior001:
Just remove the assert completely, no need to try to modify it.
[AT&T, Rogers HTC One X, Telstra One XL] dr.scofield:
Woooohooo .. that's worked .. thanks tima and jrior001 for help

---------- Post added at 04:17 PM ---------- Previous post was at 04:10 PM ----------

By this we can install any rom on this variant (Evita_utl) ;)
[AT&T, Rogers HTC One X, Telstra One XL] jrior001:
Tell me more about this utl varient? No s-off? No firmware upgrade ability? You can flash kernels though I assume or this ROM wouldn't boot.
[AT&T, Rogers HTC One X, Telstra One XL] dr.scofield:
Ok .. First of all this rom booted .. And this variant has nothing related to firmwares published .. No ruu and ota

So unlocking bootloader is working like your variant evita and s-off with rumrunner is working too but facepalm isn't

The block table differince with evita is radio and modem stuff and hboot

I bought this phone bicked and fixed it by working dump from another working phone.. And now every thing related to (system,data,cash,recovery,boot) is working like evita excactly and modifying any other block will cause problemes or brick

Facepalm isn't working because it require flashing zip that's for mid: jp83200 and this variant mid:jp83500 and this zip includes imgs for your variant so if try to modify mid in this zip you will end with brick

CID can be changed via adb command like evita_ul so you can supercid

Changing mid in hex via adb work too

Unbricking via linux by unbrick tool for evita will work if your partitons table appear and you must have a working dump for damaged block
[AT&T, Rogers HTC One X, Telstra One XL] twistedddx:
Facepalm does not require the zip it suggests, it just needs an official unmodified firmware.zip from ruu or ota. If you could get your hands on such a firmware.zip intended for your device it might work.

It just needs a signed zip to get it into its update state where it turns off some security.
[AT&T, Rogers HTC One X, Telstra One XL] tjhooker73:
Do you mean physically twisting the screen and it going black?
[AT&T, Rogers HTC One X, Telstra One XL] shyamk:
Is there a recommended Hboot/Radio for this ROM ?

I tried using the following combinations:

hboot: 2.15.0000

radio: 1.31a.32.45.16_2_10.141.32.34a

and

hboot: 2.18.0000

radio: 1.35a.32.45.27_10.144.32.34a

With both these pairs as well as CM-11-M6, I get severe lag while unlocking the phone, as well as huge battery drain with 3G.

Is there a recommended firmware pair of hboot, radio and dsp for this rom ?

If yes, can someone please point me to it ?

Thanks

Shyam
[AT&T, Rogers HTC One X, Telstra One XL] marknoll:
Like if I press on the left side of the phone the screen turns off. Capacitive buttons work..kind of like an sod..then I have the do the bend thing for the display to work
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
That sounds more like a physical fault to me, I don't see how that could be related to a certain ROM.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] marknoll:
Kind of like this guys problem..but mine stems from gently squeezing the lower left side.

http://m.youtube.com/watch?v=8xbPCiNg148

---------- Post added at 11:04 AM ---------- Previous post was at 11:03 AM ----------

Yea ..good point..just noticed it doing it on this ROM. So I flashed a different one and problem still exists. What could cause this if it isn't ROM related?
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
There is no best radio to use. Radio performance can vary wildly from user to user as it depends on carrier, exact geographical location, environmental disturbances, among other factors. Someone in the same suburb (even street) as you can have a very different experience on the exact same radio. What I'm saying is you need to test for yourself. You don't need to stick to your carrier's radios, you should test a variety of radios and see what works best for you (performance vs battery drain).

The other thing you need to worry about is your firmware, not just the hboot, the hboot is just one component of the firmware. Any firmware package since 3.17/3.18 (comes with 2.14 hboot) is fine.

Sent from my Evita

---------- Post added at 08:08 PM ---------- Previous post was at 08:05 PM ----------

My guess is that by twisting the device you're partially severing a connection. As long as it doesn't happen during normal use I wouldn't worry about it, your device shouldn't really be twisting anyway.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] marknoll:
Funny thing is..it does happen during normal use. Can't bring in for repairs as warranty is done. Called HTC and it'll cost 200$ to fix it. The screen thing happens on recovery and boot loader as well. I really love this phone. Ugh. I hear that this fault is common with the HTC one x. I'm just wondering what could have caused this.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
You're definitely experiencing a physical defect. If you can't have it repaired I think you'll just have to live with it. This isn't something you can attempt to repair yourself.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] marknoll:
I also read on google that one could open device and make sure the cables from motherboard to the LCD aren't bent and/or seated properly
[AT&T, Rogers HTC One X, Telstra One XL] shyamk:
So is there a location where I can get images of Radio and its corresponding RIL's ? There used to be a thread for my previous phones over at xda, but I do not seem to find an equivalent for this phone.

Shyam
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
You'll find the radios in the radio thread. Go to the resource link in my signature, you'll find a link to the radio thread there. Only use the radios from the very top section.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] tjhooker73:
You can, but it's a pain in the ass and you won't be able to tell.

I have the same issue, it was caused by my ballistic case, it squeezes the phone to hard and messes up the LCD. The issue is so bad now that I have to have the cover of my phone partially off.

I'm waiting to get a new phone before I attempt a complete disassembly.
[AT&T, Rogers HTC One X, Telstra One XL] marknoll:
Omg. No way. My ballistic case did it too

---------- Post added at 02:17 PM ---------- Previous post was at 02:15 PM ----------

Does screen go off when you squeeze the bottom left?
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
I've seen other people report ballistic cases causing screen issues on their Evita.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] AlxMAX:
Off topic: Guys, don't use your phone with a ballistic case to protect you against bullets. Buy real Kevlar bulletproof vest!

On topic: I have noticed some new files in the CM OTA firmware: recovery-from-boot.p, install-cm-recovery.sh. As far as I could understand, they are part of a mechanism to update the recovery with the help of OTAs. Couldn't this be replaced with a simple warning for the users to update their recoveries and let the users update? It is always possible to put an assert in the updater-script in order to test if a recent recovery was installed.
[AT&T, Rogers HTC One X, Telstra One XL] marknoll:
Last time I knew this was a q&a thread. This topic was brought up as I was running this ROM when the issues began. People were polite enough to offer suggestions and other info. That's nice to hear
[AT&T, Rogers HTC One X, Telstra One XL] tjhooker73:
Yes I have that portion slightly more out of the back plate then the rest. Its the only way to have the LCD on. Can't wait for my att contrat to end so I can get me a One Plus or an HTC One M8 then fix this one.
[AT&T, Rogers HTC One X, Telstra One XL] marknoll:
Good luck ?
[AT&T, Rogers HTC One X, Telstra One XL] marknoll:
m.youtube.com/watch?v=VBhKRQavQzo&hl=en&gl=US&client=mv-google&guid=
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
That's a private link.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] marknoll:
Ugh. let me repost. It's my YouTube channel

m.youtube.com/watch?v=VBhKRQavQzo&hl=en&gl=US&client=mv-google&guid=
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Nope.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] marknoll:
Sorry. I will do it on a PC. Just wanted to show u the prob I'm having

---------- Post added at 02:28 PM ---------- Previous post was at 02:05 PM ----------

http://m.youtube.com/channel/UCBiH2a_WZX5n4-IaZWFIPeQ
[AT&T, Rogers HTC One X, Telstra One XL] AlxMAX:
Why isn't my message suitable for this section? Did I offend you somehow? My off topic remark was intended to be a joke and I did ask a question afterwards. I admit, the question was not related to your problem but it was related to CM.
[AT&T, Rogers HTC One X, Telstra One XL] marknoll:
I never said it wasn't suitable. U didn't offend me. :)
[AT&T, Rogers HTC One X, Telstra One XL] marknoll:
Can anybody see my video on bsod?
[AT&T, Rogers HTC One X, Telstra One XL] AlxMAX:
I could see them both. That's a nasty hardware problem. I guess the entire phone body was under stress from the moment you have put it in that case. I guess the real cause was there for a long time and you noticed its effects later.
[AT&T, Rogers HTC One X, Telstra One XL] marknoll:
How u think I can fix it?
[AT&T, Rogers HTC One X, Telstra One XL] AlxMAX:
There's no easy way to fix it given it is a hardware problem. You might bring it somewhere to be repaired but it is difficult even for a professional to see if the cause is the weakened chassis or a loose contact (and where this one occurs). In my opinion, you should start looking for another phone.
[AT&T, Rogers HTC One X, Telstra One XL] marknoll:
Thanks. I appreciate the response. I think its crappy of HTC to not fix it. Phone never been dropped or mistreated. Pretty sad that this phone was cheaply built. I love HTC,but really? Lol
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Not really crappy of HTC, they're not responsible or liable for damage caused by a case manufactured by a third party.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] marknoll:
Yea. I know. But I did research and its been said its a build quality of htc

---------- Post added at 01:20 PM ---------- Previous post was at 01:20 PM ----------

And I mean its crappy that they won't fix it. Its even under the two year warranty.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
"It's been said" basically amounts to people's opinion though, it's anecdotal, and most likely from grumpy people who have had cases damage their phone. The fact is that it's always the same case that causes the damage, it doesn't take a genius to work out that it's the case at fault, not the phone. HTC in particular are heralded for their build quality.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] JBLogic:
Sent mine in to HTC. I'll let others know how that works out when I get a response after they receive it.
[AT&T, Rogers HTC One X, Telstra One XL] averylowiq:
Actually didn't need to - my replacement refurbished phone came with RUU 3.18.
[AT&T, Rogers HTC One X, Telstra One XL] PUfelix85:
When I went to install the updated rom 8/6 I could not get to the reboot menu. I would press and hold the power button but it would not come up. I had to move the file into the cmupdate folder and update using the built in updater.
[AT&T, Rogers HTC One X, Telstra One XL] h8rift:
The brick bug has been stomped.

see here http://xdaforums.com/showpost.php?p=44466947&postcount=230
[AT&T, Rogers HTC One X, Telstra One XL] edditnyc:
Important update on the bricks.

Real quickly for those who haven't kept up, there is a new build 20130809 build that addresses an issue affecting a small number of handsets. All of the s4 devices (m7, evita, ville, etc) uses a Samsung chipset and some have a bug in the EMMC chip. So [MENTION=1815755]intervigil[/MENTION] merged a fix and now we're all protected and we shouldn't see any more bricks. We highly recommend everyone on CM10.2 to update to the latest unofficial build 20130809. Also, CM10.1 is not affected.

If you have any questions feel free to ask or join us in IRC.

UPDATE: For more info on the EMMC brick bug, read up on it here. http://xdaforums.com/showthread.php?t=1693704
[AT&T, Rogers HTC One X, Telstra One XL] xetrev:
Is there anyway to add a toggle to increase bluetooth volume past normal presets?

I do a lot of driving on the highway at 80+mph and it would be nice to be able to increase that up a bit.

Its usually fine during normal city driving but on the highway it can be a bit low and depending on the person on the other end as well.
[AT&T, Rogers HTC One X, Telstra One XL] thewaronerror:
fstrim worked for me?

GotBrick? 1.2 reports my eMMC device as MAG4FA rev 0x20 and says that it probably has the brick bug. However in both the Aug. 6 and Aug 9 builds I have successfully run fstrim in a root shell on /system /data and even /dev/mmcblk0p36 (after unmounting the sdcard and reformatting the partition with mke2fs on the Aug 6 build). I got my HOXL from AT&T in May 2012. Just an FYI for anyone with the same version and bad storage performance who wants to try fstrim. Of course there may be some subtle difference on yours that causes a brick.
[AT&T, Rogers HTC One X, Telstra One XL] lauterm:
Mine showed MAG2GA, which is unknown. I never bricked.
[AT&T, Rogers HTC One X, Telstra One XL] twistedddx:
Just to clarify 10.1 on 3.4 kernel is affected if trim apps are in use, right?

I think a few bricked on 10.1 but only with 3rd party apps installed.

Should we bother trying to figure what devices have bad chips?

My release hong Kong device from june is apparently a sane chip.

From what I hear most have fine chips, what devices have bad chips?

At&t early devices or late devices?
[AT&T, Rogers HTC One X, Telstra One XL] exad:
H8 said the bugs been squashed. I don't see any reason to care if your phone has it or not at this point.
[AT&T, Rogers HTC One X, Telstra One XL] thewaronerror:
Because fstrim improves storage performance and the block in the kernel may be overbroad?
[AT&T, Rogers HTC One X, Telstra One XL] beankid:
I just updated to the new CM 4.3 and I am having problems with WiFi again. I had these problems on old stock 4.1 ROMs but I had assumed they where fixed. Has anyone experienced problems where enabling WiFi kills your data connection?

Also how do I get past the initial screen with Google voice. I have the voicemail set up but I cannot launch the program at all as it won't let me get past the "voice+" setup.
[AT&T, Rogers HTC One X, Telstra One XL] utdps:
Can someone help me on the steps needed to go from Sense based roms to AOSP for the first time? I have a 1.09 hboot and my wife has the newest one. So it looks like I have to RUU mine and not hers. I'm S-OFF, so it looks like I fastboot oem lock, run the RUU. Then what are the steps after that? How do I unlock it again and will I have to put TWRP back on it? I have the newest CM10.2 build and GAPPS on the SD card so it looks like those should stay on there as my SD card won't be deleted, right?

And then for the other phone that's on the newest hboot and S-OFF, I should just be able to flash CM10.2 normally, correct?
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
You don't need to fastboot oem lock to RUU. All your do is connect your phone in fastboot mode and run the exe file. Afterwards you'll just need to flash TWRP again. Then you can flash CM 10.2 from TWRP. Running an RUU shouldn't touch your sd card, but make a backup just in case.

And yes, it's fine to flash now on the other phone.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] exad:
placebo.
[AT&T, Rogers HTC One X, Telstra One XL] thewierdone:
thanks

Thank you. just trying to get settled into things here in the community. love this community and all it provides I just have been hesitant to join. but thanks again zodiac.:highfive:
[AT&T, Rogers HTC One X, Telstra One XL] edditnyc:
Don't worry the fix squashes the EMMC bug, it's not disabling fstrim.
[AT&T, Rogers HTC One X, Telstra One XL] thewaronerror:
It wasn't a placebo on the Nexus 7.

http://www.xda-developers.com/android/yet-another-reason-to-update-to-android-4-3-trim-support/

---------- Post added at 10:08 PM ---------- Previous post was at 10:01 PM ----------

I believe it does have the effect of making fstrim a no-op as far as the eMMC is concerned. See this thread:

http://xdaforums.com/showpost.php?p=26751098&postcount=394

Have you looked at the brick fix commit for our branch of CM 10.2? If the repo is on github it's not linked in the main thread so I couldn't find it.

Also regarding the efficacy of Android 4.3's automatic fstrim on our devices, I think it will fail on our sdcard partition..

Running fstrim manually against /mnt/sdcard or /sdcard always gives an error like "FITRIM: Not a Typewriter." I think this is because it either does not support FAT32 or it doesn't support the way the internal sdcard is mounted. I worked around it by unmounting the sdcard in the settings app and then formatting /dev/block/mmcblk0p36 with mke2fs and mounting it manually before running fstrim which then worked.