yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers HTC One X, Telstra One XL] bimmernut318:
No worries, I have been around the block a few times, this crap happens! Radios are an interesting thing. Some work for some and not for others. You are in wnc (where exactly as I lived in hendersonville) and I am in cf and that radio just had poor reception for me. It appears that this version of android has issues on our device, not the kernel or the Rom, just android 4.2.2 in general.

Whatever the problem is it will all get worked out.

Flar2 is doing an awesome job and I look forward to running this kernel as I did on all other versions of android on this device.
[AT&T, Rogers HTC One X, Telstra One XL] raymondn:
I'm over near Black Mountain... It's a small world!

It's strange because I've been in and around Asheville and Fairview today and the new radio seemed pretty good to me...
[AT&T, Rogers HTC One X, Telstra One XL] bimmernut318:
I am in central Florida now but I guess the point is that our locations will dictate what radio we use and what will give us the best performance.
[AT&T, Rogers HTC One X, Telstra One XL] ethantarheels123:
YesYesYes noticed this immediately as soon as I flashed 3.18. Kept this to myself as I thought this was just an issue on my end, but now that someone else has pointed it out
[AT&T, Rogers HTC One X, Telstra One XL] JeremyNSL:
I can confirm that the 3.18 ATT radio doesn't work properly on 2.15 firmware/Viper... So I went back to the radio that's packed with 2.15 firmware.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
It's the same in reverse for me. I'm on the 2.14 hboot and the newest radio that came with the 2.15 update was atrocious.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] 696kris969:
Was one of the reasons Zarboz got rid of cell drops because it wasnt solely based on HTC kernel but stock 4.2.2?
[AT&T, Rogers HTC One X, Telstra One XL] RC196:
On stock it also drops. Same behavior and I'm hboot 2.15.
[AT&T, Rogers HTC One X, Telstra One XL] XNine:
Install Beastmode 2.0, then BEastmode 3.5. If you want the Elemental Alpha Kernel, then flash it after that.
[AT&T, Rogers HTC One X, Telstra One XL] xstokerx:
There has got to be something fishy going on cuz once I updated to hboot 2.15 I had no problems with any Roms or kernels
[AT&T, Rogers HTC One X, Telstra One XL] raymondn:
As long as you upgrade the firmware to 2.15 and then leave the radio as the latest upgraded one, you should be fine. If you downgrade or mess with the radio it seems to cause cell signal drops.
[AT&T, Rogers HTC One X, Telstra One XL] Pdj7969:
And while that's all well and good, it still doesn't explain the special sauce that Beastmode uses to make it work. If it is truly that it's based off of stock code for 4.2.2 instead of HTC's code that's one thing, but why not share your knowledge? The implementation of s2w on that kernel is wonky at best and my battery life was abysmal. Flar2 has done it again with this kernel, and all while not even being able to test it out himself. Rockstar!
[AT&T, Rogers HTC One X, Telstra One XL] JeremyNSL:
I read only the wifi module is based of 4.2.2 AOSP in Beastmode, so I'm not sure that's relevant.
[AT&T, Rogers HTC One X, Telstra One XL] Pdj7969:
I didn't mean to infer that it was the reason it worked, only that it's the only marked difference from the base everyone else was using. I swear Zardoz employed black magic to get that working. This radio that came with the firmware sucks in my area. I usually have at least two bars of LTE in my office....now I'm on H more than anything else.
[AT&T, Rogers HTC One X, Telstra One XL] raymondn:
Sorry, but that is as far as my knowledge goes... I'm not a developer, just a user that wants to use Elementalx rather than having to use Beastmodes kernel. That is what I have worked out by testing different combinations myself.

I have been completely free of cell service drops for about 2 days now, but my reception and battery life is definitely not as good as on the 3.18 ATT radio. So I have just downloaded the 3.18 ATT radio again from the Venom Hub (previously I used the one from the radio thread - not sure if they're the same), and I am now testing again with the 3.18 radio.

I'll report back if I lose cell service again.
[AT&T, Rogers HTC One X, Telstra One XL] Pdj7969:
I

I have yet to flash 3.18 again as I don't want to mess up a good thing (over 36 hours without cellular drop or random reboot). Kudos for being brave and taking one for the team. I eagerly await your results as I hate seeing my radio being the highest source of battery drain.
[AT&T, Rogers HTC One X, Telstra One XL] raymondn:
That's exactly the problem I was having! As well as poor cell signal!
[AT&T, Rogers HTC One X, Telstra One XL] scabbard1:
On att with signal drops. Did change radio. Interested to see if going back to T-Mobile Germany radio fixes data drop

And yes firmware was updated
[AT&T, Rogers HTC One X, Telstra One XL] flar2:
From what I'm hearing:

-the stock kernel has the same problem with cell signal

-updating to latest firmware and radio fixes it

-alternatively, Beastmode fixes it

-the new radio is not good for AT&T users (or is it no good for others as well?)

Based on that, I have new questions:

-what are people doing in the Viper thread: updating firmware? using Beastmode? staying with older ROM base?

-big question: does cell signal work for everyone using Beastmode?

Zarboz patched in drivers from an earlier source release to get it working, I just want to know if doing that would cause any other problems. I prefer not to mix and match source and don't want to mess things up for those where it's working well.
[AT&T, Rogers HTC One X, Telstra One XL] Syk69:
I got the new firmware and on at&t with no signal or data issues.
[AT&T, Rogers HTC One X, Telstra One XL] bzhmobile:
I have flash in the recovery Carl1961's firmware zip and no more cell signal problem or data drop with the Urdroid, the Viper and the CleanRom ...
[AT&T, Rogers HTC One X, Telstra One XL] raymondn:
Well, within about an hour or so of going back to the old 3.18 ATT radio, I noticed my first cell signal drop :(

I am reflashing the German Tmobile radio now from the 2.15 firmware and hopefully that will eliminate the cell drops again.

It looks to me that it is definitely all related to the new build 5.08 is NOT compatible with the old radios...
[AT&T, Rogers HTC One X, Telstra One XL] Skeeterdrums:
Same here. I upgraded all firmware, did a full wipe, installed Viper 4.0 and upgraded to Viper 4.1. I have not had any signal or data issues, and I'm on ATT as well.

This has also been my experience. I tried to downgrade to the radio I had been using with the previous version of Viper, and that's when signal problems started occurring.
[AT&T, Rogers HTC One X, Telstra One XL] raymondn:
Flar,

From what I've read on the Viper and Cleanrom threads, people are just saying to either make sure they have upgraded the firmware OR install the beastmode kernel. Everyone is trying to work out a way of using the new ROM base. Few people are saying to use your kernel yet, because unless you upgrade the radio and firmware too, there are still signal drops.

My cell signal did work OK for the couple of days I was using the beastmode kernel, but I didn't like the settings and the options on that kernel. Hence why I jumped to your kernel as soon as I could!

I don't know if it's worth making the same changes that Zarboz did, or if we should just be patient and wait for a new ATT radio that is compatible with the new ROM base??? :confused:
[AT&T, Rogers HTC One X, Telstra One XL] JeremyNSL:
Well, I've updated my firmware (using the new radio too) and am on ElementalX with no data drops in 24 hours or so. Have not tried Beastmode. Battery is improved over stock, though still not at Android 4.1/ElementalX 7 levels. Maybe it will still settle more though.

The only time I got data drops was on the stock kernel and 3.18 radio.

For me the issue is how much battery drain the new radio seems to be causing... This is frustrating. Maybe when the 4.2.2 update comes to North America officially there will be better radio firmware along with it?
[AT&T, Rogers HTC One X, Telstra One XL] bimmernut318:
This is my scenario flar2.

Was on Viper 3.28, updated firmware to 2.15 using Turges instructions and DL in his stock rom thread, booted and verified. Flashed Viper 4.0 then promptly 4.1 then beastmode without ever booting to Viper and after a full wipe of everything, booted to rom and set up. After the first day without issue with anything but poor reception I flashed the 3.18 AT&T radio from the radio thread and ran with that for 2 days without issue and improved cell signal and call quality. To this point I had NO reboots, NO loss of signal, NO problems. When I saw that you were getting your kernel going I just had to have it and flashed it late at night and set it up and went to bed, woke up in the morning to get ready for work and had no signal, tried toggling airplane mode to no avail and had to reboot to get it back. About 2 hours later I had 2 reboots and a loss of signal again that airplane mode did fix.

I flashed beastmode back on the phone yesterday am after the problems and have not had any issues since.
[AT&T, Rogers HTC One X, Telstra One XL] k2ham:
My experience pretty much mirrors bimmernut318's.
[AT&T, Rogers HTC One X, Telstra One XL] tlazarus:
I am an AT&T user. I've been running the ElementalX 4.2.2 kernel all day. I haven't noticed anything odd, and experienced no reboots. I am, however, on the latest firmware. I heard a rumor the radio issue was related to some kind of power saving feature in the kernel or a mismatch between the older radios and new kernel, but I have no idea if this is true. Either way, the kernel seems to be working fine for me so far.

Edit: I was running Beastmode until today, and also experienced no drops.
[AT&T, Rogers HTC One X, Telstra One XL] scabbard1:
Mine is also same as bimmernut
[AT&T, Rogers HTC One X, Telstra One XL] raymondn:
Just a thought Flar... Is there a way you could offer two slightly different versions of your kernel?

1. As it is at the moment, that works great as long as you are running the latest baseband version

2. With the "patched in drivers from an earlier source release" as Zarboz did, so that your kernel would work with older baseband versions

I appreciate it may be some extra work for you, but at least then everyone would be able to use your kernel without a problem...
[AT&T, Rogers HTC One X, Telstra One XL] traesnaidensdad:
AT&T hboot 2.14 been using included radio with stock, elemental, and beastmode. I've had "0" issues .....zero.
[AT&T, Rogers HTC One X, Telstra One XL] ethantarheels123:
the problem i think most people are having is, they all tried another radio at some point, such as 3.18, and after finding out there are issues with the ATT radios, they wiped data, and reflashed their rom. However, radios are stored in a completely separate partition, which means the only way to get rid of the signal drops and reboots is to EITHER flash the 2.15 firmware.zip again, or go to post 1476 in the Radios thread and flash the tmobile Germany radio specifically. Me, personally, would feel more comfortable just flashing the entire 2.15 firmware zip again. This SHOULD fix the issues people are having all across different roms and kernels.

Edit: I guess beastmode kernel would be ok also
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
I'm not sure whether saying the s2w on the Beastmode kernel is wonky is entirely correct, it's always worked perfectly for me, and many others. Plus the battery life I've been seeing is great. But in saying that, not all phones are created equal.

I'm seeing a bit of dissing of the Beastmode kernel in this thread, and I'm not sure that's exactly allowed on XDA. I could be wrong but that's the reason best ROM/kernel threads aren't allowed on this site, because it leads to negative comments on one or the other. That only serves to discredit the work our developers are doing out of the love of it, and for free. Obviously this isn't a best ROM/kernel thread, but I think to post negative remarks about another piece of development isn't really allowed. Especially since the kernel is running perfectly for a great number of people. Most of the time when someone is experiencing bad battery drain it's something on the user's end, and quite often it's directly after flashing something, and before competing the necessary initial charge cycles.

By all means everyone has their preferences when it comes to ROMs and kernels, and expressing how much you love a ROM or kernel is fantastic, but I think the negative comments towards a different piece of development might fall under the respect section of the XDA rules.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] jwhood:
Awesome battery life im on viper with your kernel, ran from 6am to 10pm with heavy use and fm radio playing from 8am till 3pm with heavy internet use in evening and still had 50% left when put on charger,great kernel flar by far the best so far for sense 5!!!!!

Sent from my HTC One!!!
[AT&T, Rogers HTC One X, Telstra One XL] ringnutz:
I don't know that anyone has been dissing beast mode, most of us who use this kernel need it for the features that beast mode will never include, like fast charge. I have the utmost respect for zarboz, and likewise flar, but again I don't think anyone is dissing zarboz
[AT&T, Rogers HTC One X, Telstra One XL] Pdj7969:
Well I'm sorry you feel that the way. So someone mentions having issues with a kernel and is listing them in a thread and that's considered negative talk? That's a bit of a stretch. I never once said it sucked or was trash and have actually praised Zarboz's work on that particular kernel, but while Beastmode works for most, it didn't really do it for me. It was a means to an end for me.

And I'm not the first to say s2w didn't work as well as we were used to with this kernel on the previous ViperXL ROM. I don't know if it was a proximity sensor issue or what, but it didn't work well for me...end of story. That's, again, not negative or disrespectful.

I'm sorry if my comments touched you as disrespectful, but that was never my intention. I've had great experiences with this kernel in the past and hope to continue to in the future.
[AT&T, Rogers HTC One X, Telstra One XL] raymondn:
I'm not sure that people are "dissing" other developers work... Or just saying that they have a preference towards ElementalX? That's definitely all I have ever done.

There are certain options in ElementalX that I prefer, such as DT2W and disabling the Max off frequency, and S2W seems more accurate, etc. and with previous versions of various ROMs and kernels, I have always had great performance and battery life with Flars kernels.

That's just me :confused:
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
I wasn't suggesting what you said was disrespectful, that part of my post was an add-on and maybe should have been posted separately.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] Pdj7969:
Totally understand....done that myself. No worries. I do see what you're saying so I'll make sure I'll pay attention to the way I say things and keep on topic.
[AT&T, Rogers HTC One X, Telstra One XL] JayDream:
Just to be sure, if I have recently ran the 3.18 RUU, would I still have to flash the 3.18 radio after flashing a sense 5 ROM & kernel?? I'm still on hboot 2.14 and I absolutely refuse to upgrade the firmware for fear of compatibility issues with aosp 4.2 ROMs (4.3 ROMs are still entirely too buggy for my taste)
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
As long as you hadn't flashed a radio since the RUU you will still have the 3.18 radio, flashing a ROM/kernel doesn't touch the radio partition.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] scabbard1:
I can confirm that if you have updated firmware, flash elemental and only use most recent T-Mobile Germany radio that will keep you from having data drops
[AT&T, Rogers HTC One X, Telstra One XL] RC196:
So can you update firmware, flash a different radio like 3.18 and then flash to the German 5.08 radio and be fine with Elemental?
[AT&T, Rogers HTC One X, Telstra One XL] ethantarheels123:
Don't know if this is an issue on my end, as I was running the Cleanrom Elemental combo perfectly two days ago. But anyways, I reflashed the 2.15 firmware because I needed to revert back the radio to get rid of signal drops, and then I full wiped, then flashed cleanrom, then elementalx with essentially the default settings. When I hit reboot system in recovery, the white htc bootscreen comes up, and then the screen just goes black, and doesn't continue booting. The phone is actually on though, as I can force reboot to bootloader by holding the power button and the capacitive buttons still flash.
[AT&T, Rogers HTC One X, Telstra One XL] scabbard1:
That's what I did

---------- Post added at 11:26 AM ---------- Previous post was at 11:25 AM ----------

That's what I did
[AT&T, Rogers HTC One X, Telstra One XL] flar2:
I'm going to do a build with the older drivers like Beastmode, if that works for everyone, then we'll go with it.

I might get around to it later tonight, or more likely, sometime this weekend.
[AT&T, Rogers HTC One X, Telstra One XL] JeremyNSL:
That sounds like a good plan.

Just to check things out, I installed Beastmode last night. Indeed, it works fine without cel drops on older radios. So to summarize, on the stock kernel or ElementalX, you need the latest radio or you'll get cel drops. On Beastmode it doesn't seem to matter what radio you have. And the latest radio seems to have pretty poor reception and battery life, at least for some people.

Also, is there any way you can add the lower mhz modes like Beastmode? It goes all the way down to 162mhz. Or is there a reason why that's not a good idea for Elemental?
[AT&T, Rogers HTC One X, Telstra One XL] flar2:
I'm not going to add the lower frequencies because they have no benefit and cause instability and micro stutter. I prefer to stick closer to Qualcomm's design. 192 was always bogus, except with the overclocking module I had back when we had no kernel source. I knew this back when I figured out the oc freqs were wrong, but didn't bother taking it out because it was harmless.
[AT&T, Rogers HTC One X, Telstra One XL] JeremyNSL:
Hey thanks for the info. So by 'no benefit' do you mean they don't run at significantly lower mW than 384mhz? In Beastmode I can't see the voltage table so it's hard to know what is being saved at lower frequencies.
[AT&T, Rogers HTC One X, Telstra One XL] Genetic517:
there has been a few reports of random reboots/shut down that COULD have to do with beastmode. would using the older drivers cause this? was just something i noticed over in the viper thread. i guess well find out when you release the new build with older drivers. just fyi, im NOT trying to knock or attack zarboz' kernel. ive used beastmode in the past, great kernel, i just prefer flars elementalx.
[AT&T, Rogers HTC One X, Telstra One XL] zerocoolak:
I experianced all the issues people have mentioned in this thread. I flashed the new 2.15 firmware and beastmode and was still having signal drops etc.

I decided to start fresh with a full wipe of sdcard and factory reset with the 3.18 RUU. I then adb pushed my unlock.bin, flashed su and TWRP. I updated the firmware to 2.15 from the 2.14 that is flashed with the RUU. I then clean flashed viper 4.0 and set up manually. I then flashed beastmode 3.5 and rebooted. I then decided I would give elementalx 8.1 another shot with the clean install. I have had zero signal drops, zero reboots and zero issues with bad signal or elemental 8.1 beta since.

After the elemental kernal install I updated venom to 4.1. The only hiccup I experianced was not with the elemental kernal, but with no option for LTE in network mode settings. After turning LTE off via the LTE button in the venom quicksettings bar. I chose the GSM/WCDMA option. I then toggled and untoggled airplane mode and then turned on LTE via the venom quicksettings bar and went into the mobile data settings menu and the GSM/WCDMA/LTE option appeared. It just popped up while I was watching. Anyways, after a fresh 3.18 RUU and a clean install of venom and elemental all is running smooth with zero issues for two days now. My reception with the 2.15 radio prior to clean instal was crap, but now 2.15 radio is giving me great reception and data speeds are back to normal.

Just wanted to share what worked for me after a very frustrating couple days of poor data and signal when the new 4.2.2 Roms and kernals dropped. Hope this helps someone.
[AT&T, Rogers HTC One X, Telstra One XL] flar2:
It turns out that I got mixed up when I diffed Zarboz's code, I thought I spotted some key differences but they were not what I needed. There are literally thousands of differences in the source and there's no way I can go through them to figure out what needs to be changed. Zarboz ported the HTC One kernel, patching in parts of the older One XL kernel to make it work. I prefer to stay with clean base.

So, sorry, I won't be able to update this with changes from Beastmode. If HTC releases any new source let me know.

In the meantime, if the available firmware and radio don't work for you, you'll have to use Beastmode.
[AT&T, Rogers HTC One X, Telstra One XL] WeWearFedoras:
Is there anyway to fix the issue where the screen seems to remain active during phone calls? I'm constantly activating toggles and random apps with my cheek while I'm talking on the phone. This seems to happen on both beastmode and elemental...
[AT&T, Rogers HTC One X, Telstra One XL] ringnutz:
I thought I was the only one... Happens on every kernel and is extremely annoying
[AT&T, Rogers HTC One X, Telstra One XL] WeWearFedoras:
You're not the only one... I believe it has to do with s2w but I haven't tried installing the kernel without s2w enabled... I'll try that but I <3 s2w
[AT&T, Rogers HTC One X, Telstra One XL] flar2:
I should be able to fix that
[AT&T, Rogers HTC One X, Telstra One XL] WeWearFedoras:
That would be awesome!
[AT&T, Rogers HTC One X, Telstra One XL] flar2:
Can someone try this boot.img and see if it fixes the sweep2wake registering touch during calls.

https://dl.dropboxusercontent.com/u/83841273/test/One_XL_betas/boot.img
[AT&T, Rogers HTC One X, Telstra One XL] JeremyNSL:
Damn. Sorry to hear it didn't work out. Well, fingers crossed here that some new source appears when the official 4.2.2 update hits North America.

On the topic of Beastmode, I flashed back to ElementalX today. Beastmode's S2W is wonky, just takes too many tries. And since it does not undervolt, battery life is not as good as Elemental. Really the only thing Elemental needs is the capability to use any radio... But I understand it's a really complex problem. Thanks for all you've done and continue to do for the evita community flar!

Question for you - the latest Elemental defaults to OnDemand instead of Intellidemand. How come? And one more thing - any chance of ROW scheduler making it back in Elemental?
[AT&T, Rogers HTC One X, Telstra One XL] zrv:
Dear Flar2!

I juz flash this boot on Telstra Stock, I used kernel tuner active S2w but it didnt work , only S2L work fine.

Tks !

Gửi từ HTC One XL của tôi bằng cách sử dụng Tapatalk 2
[AT&T, Rogers HTC One X, Telstra One XL] Skeeterdrums:
Second this. Seems like Sweep2Wake no longer wants to work with this boot.img.
[AT&T, Rogers HTC One X, Telstra One XL] zrv:
But with this boot, no problem in calling like previous version.

Tks flar so much.

Gửi từ HTC One XL của tôi bằng cách sử dụng Tapatalk 2
[AT&T, Rogers HTC One X, Telstra One XL] doc_v15:
Flar...i was using beastmode, then switch to stock...and finally tried elemental...

The data is greaaat so far...

Im on vanilla settings.

1.09 hboot

Viper

S-on
[AT&T, Rogers HTC One X, Telstra One XL] flar2:
For the touchscreen active in calls issue, do you guys mean the whole screen or just the buttons?
[AT&T, Rogers HTC One X, Telstra One XL] WeWearFedoras:
It's weird. Usually the only way I know it happens is when it accidently toggles airplane mode and kills my call or when I hangup and the HTC media app or my texting app is open and active.

ViperXL 4.0 w/ BeastMode 3.5