I thought with 4.4 around the corner and 5.5 landing, I wanted to know what you guys thought of the two...
Personally, I'm an AOSP guy, living life on the bleeding edge. How about you guys?
S-OFF
Boot Unlock (TAKE THAT AT&T!)
TWRP 2.6.3.0
Running something that'll probably change in a few days
Been stuck on Venom 4 goodness since release. But Beanstalk w/ jrior001's Torched B4 takes the cake. Back on da Dark Side!
Sent from my One X using XDA Premium 4 mobile app
They both have their merits. Personally I prefer aosp, it's a bit snappier, plus the advances in battery life have been pretty good recently.
Sent from my Evita
I personally prefer the functionality of the Sense camera (which I use a good amount) and a few other more minor things on Sense. But as mentioned, AOSP just feels smoother and snappier. Both have their merits (again, as timmaaa mentioned), and its just a matter of personal preference and taste.
Same here, since Venom 4 landed,Ii stayed on it.Now, I started using Beanstalk w/ Torched kernel and I must say i'm pretty impress with the result.
Before Venom 4, I kept moving from one AOSP to another (the best experience I had was with Xylon, by far, kinda sad the project died...)
I used to be an AOSP guy untill I flashed a sense 5 ROM wich I don't know if its just me but I feel sense roms are snappier and the battery life its just beter
I'm so happy that we have these amazing devs that we get the luxury of choosing this type of thing
S-OFF
Boot Unlock (TAKE THAT AT&T!)
TWRP 2.6.0.0
Running something that'll probably change in a few days
I used to love Sense.
I first tried out, and didn't like, either Cyanogenmod or MIUI. Then I loved ViperXL (Sense based).
After that I found Illusion ROM and haven't gone back to a Sense ROM since.
Other than Sense camera, I don't really miss anything from Sense.
I've noticed that AOSP ROMs "feel snappier" and my phone has stopped overheating since I flashed Illusion. My phone used to constantly overheat while on any Sense based ROM.
Viper is the the only reason I go to sense. But I am strictly aosp because the Roms are way more customizable and and I had a gnex before I got this phone.
Sent from my One X using XDA Premium 4 mobile app
I personally have always preferred sense Roms. I really like the camera, as already mentioned above. However, I am leaning on trying some AOSP. Haven't run AOSP since Gingerbeast on my retired Inspire 4G. If any of the AOSP Roms for this device are half as good as that Rom I will definitely be swayed.
Sent from my HTC One XL using XDA Premium 4 mobile app
This is a tough one. I ran with CM 10.2 for a few weeks and liked it quite a bit once I resolved the issues. I kept looking at the CleanRom page over and over ("It's a Sense Rom, are you crazy, you left that to move on to AOSP???" I kept telling myself.)
Well....I made the jump and I love Sense 5 JB 4.2.2. Now I look longingly at the Beanstalk page every other day (what is wrong with me??)
Most of my best Nandroids are AOSP. But I tell you I love Sense and have spent more time driving a Sense Rom than anything else.
One thing I can say is for me is to use Sense I require Xposed framework for Sense toolbox, Greenify, and Advanced power menu. And the fact that I'm a sucker for transparency on the launcher dock. I feel the solid launcher dock looks dated (thanks AOSP.) Cosmetic pickiness!
For me, AOSP is not an option until they fix the Exchange client. It trashes the battery and sometimes data. Downloaded over 3 Gigs of data when I was asleep one night. I am looking forward to trying ExchangeServices 6.0 in KitKat to see if the problems have been fixed.
leybove from
The biggest difference I've seen with them is the business integration. For non-business users, it doesn't matter. But Sense's email client integrates with Exchange much better. Contact lookups, thread viewing, etc.. Other than that, it's a personal preference.
Im using a stock sense 5 rom with all the latest official goodies including full 2.15 firmware, radios, etc. I love it personally but i wanna try out aosp again, first time on this phone. Is there an aosp rom i can freely switch back and forth between sense nandroid and aosp nandroid without problems caused by the 2.15? if u can understand my question please let me know.
NexusS4gFreak said:
Im using a stock sense 5 rom with all the latest official goodies including full 2.15 firmware, radios, etc. I love it personally but i wanna try out aosp again, first time on this phone. Is there an aosp rom i can freely switch back and forth between sense nandroid and aosp nandroid without problems caused by the 2.15? if u can understand my question please let me know.
Click to expand...
Click to collapse
Well, I am currently on CleanRom 7 with S-Off and 2.15 and it is rock solid after two weeks now but I have several Nandroids built with AOSP Roms. The one that worked best was Beanstalk with the Boosted kernel. I had recurring issues with CM 10.2 (I think it needs a little longer to bake and it will be better.) 2.15 HBoot didn't seem to make much difference when I tried out several 4.3 Roms but if you are S-Off you can always flash back to a previous HBoot.
Madcat8686 said:
Well, I am currently on CleanRom 7 with S-Off and 2.15 and it is rock solid after two weeks now but I have several Nandroids built with AOSP Roms. The one that worked best was Beanstalk with the Boosted kernel. I had recurring issues with CM 10.2 (I think it needs a little longer to bake and it will be better.) 2.15 HBoot didn't seem to make much difference when I tried out several 4.3 Roms but if you are S-Off you can always flash back to a previous HBoot.
Click to expand...
Click to collapse
Flashing the hboot doesn't do the job correctly, all it does is change the hboot, it doesn't give you any of the other firmware components that are required. The correct way to do it is to run the 3.18 RUU which gives you the 2.14 as well as other firmware components (for aosp ROMs), or flash the 2.15 firmware package which gives you the 2.15 hboot as well as other more critical firmware components (for Sense 5 ROMs).
The common misconception that all that's required is the hboot is being fueled by posts like this.
Sent from my Evita
timmaaa said:
Flashing the hboot doesn't do the job correctly, all it does is change the hboot, it doesn't give you any of the other firmware components that are required. The correct way to do it is to run the 3.18 RUU which gives you the 2.14 as well as other firmware components (for aosp ROMs), or flash the 2.15 firmware package which gives you the 2.15 hboot as well as other more critical firmware components (for Sense 5 ROMs).
The common misconception that all that's required is the hboot is being fueled by posts like this.
Sent from my Evita
Click to expand...
Click to collapse
Okayy so timmaaa can u answer my question? And i was 3.18 (2.14) and flashed the hboot and radio update for 2.15.
timmaaa said:
Flashing the hboot doesn't do the job correctly, all it does is change the hboot, it doesn't give you any of the other firmware components that are required. The correct way to do it is to run the 3.18 RUU which gives you the 2.14 as well as other firmware components (for aosp ROMs), or flash the 2.15 firmware package which gives you the 2.15 hboot as well as other more critical firmware components (for Sense 5 ROMs).
The common misconception that all that's required is the hboot is being fueled by posts like this.
Sent from my Evita
Click to expand...
Click to collapse
You are absolutely right. I did run the appropriate RUU package not just an HBoot flash. Thanks for pointing that out. I can see how the verbage I used can lead to some poor decisions.
Im only asking can i freely switch between aosp and stock nandroids without issue
Some aosp ROMs are 2.15 compatible, some are not. The best way to find out is to check in the ROM thread of the ROM you want to flash.
Sent from my Evita
---------- Post added at 02:38 PM ---------- Previous post was at 02:37 PM ----------
Madcat8686 said:
You are absolutely right. I did run the appropriate RUU package not just an HBoot flash. Thanks for pointing that out. I can see how the verbage I used can lead to some poor decisions.
Click to expand...
Click to collapse
Thanks, I'm just trying to make sure the correct terminology is used.
Sent from my Evita
Related
For the past 2 months I've been checking and downloading roms like JellyBam hoping that in some new revision it will support 3.17.707 . Of course, without this support; the touch screen doesn't work at all, which sucks, because I love stock jellybean, and it's all i really want to use, though I'm still very happy with venom.
Is there a reason there's seemingly a lack of support from CM10 / senseless JB roms for the 3.17.707 Build? I've asked the dev's of the roms via PM/Facebook but never get a response. If I had have known that upgrading my stock rom before trying these JB roms would have ruined my possibility i wouldn't have done it
I realise there are 1 or 2 roms in the mix that meet my criteria, however from what I've read they are rudimentary and missing some basic functionalities (camera etc). I obviously want my phone working right, with the added benefit of a passionate dev. Also quite annoying JellyBam lists nowhere the Build it uses, so I Have to download and install it, to then have it fail each revision the past few months in sheer hope that it will be upgraded to the newer build.
Also, who's a moderator I can contact. I have these harsh account restrictions and fixing typos or making basic information edits requires me to wait 5 minutes in between.
Rebelrom
not to be mean, but this topic has come up a few times. htc updated the firmware for the touchscreen in the ota. htc has yet to release the source code which, from what i hear, is against gpl. blame htc.
until they release sourcecode. desensed viper or the above mentioned rom are pretty much your only options.
i personally have tried downgrading my hboot in an attempt to work around but it did not work. i did not try running the original ruu though as my telus ruu no longer works after downgrading my hboot.
not sure if it would work but you could try relocking. use ruu, re-unlock then flash... never tried it so not sure. i also love stock android but alas thats life bud.
exad said:
not to be mean, but this topic has come up a few times. htc updated the firmware for the touchscreen in the ota. htc has yet to release the source code which, from what i hear, is against gpl. blame htc.
until they release sourcecode. desensed viper or the above mentioned rom are pretty much your only options.
i personally have tried downgrading my hboot in an attempt to work around but it did not work. i did not try running the original ruu though as my telus ruu no longer works after downgrading my hboot.
not sure if it would work but you could try relocking. use ruu, re-unlock then flash... never tried it so not sure. i also love stock android but alas thats life bud.
Click to expand...
Click to collapse
Thanks for filling me in on the situation, makes sense why there's limited support (though certainly hasn't stopped other roms). It's understandable, silly htc.
I've tried complete reset to stock, but afaik you can set everything back to out-of-the-box except for the Build... kind of blows, but i may be wrong, though I have made solid attempts to get past this issue.
Cheers for the input. I checked out RebelRom, might give it a whirl, though I'm quite tired of flashing roms back and forward, don't want to be disappointed again, and happy enough with venom; works well.
xlmama said:
I've tried complete reset to stock, but afaik you can set everything back to out-of-the-box except for the Build... kind of blows, but i may be wrong, though I have made solid attempts to get past this issue.
Click to expand...
Click to collapse
What method to "reset to stock" are you talking about? If you are talking about an RUU, there is no way to run one that has an older hboot version than what is currently installed on the phone. Downgrading the hboot might be an option, but I don't know if anyone on the 3.17 OTA has been able to do so successfully.
AFAIK, with things in their current state, there isn't much way to return anything of your phone to an "out of the box" condition.
---------- Post added at 09:08 AM ---------- Previous post was at 09:00 AM ----------
You are limited to ROMs based on 3.17 firmware, until someone figures out what was changed by the OTA to make the touchscreen not function on non-3.17 based ROMs. AOSP ROMs are not based on Sense builds, so therefore fall into the "non-3.17 based" category. As mentioned, source code will probably help the devs figure out this problem. Plus, some 2/3 of the users here are AT&T. So when that JB OTA eventually roles out, you might (probably) see more movement towards sorting the touch screen issue out.
You realize that ViperXL has an option to de-Sense in AROMA? It would still be 3.17 based, but simply replacing many HTC Sense components with AOSP-style ones. Its not true AOSP, but it might get you what you are looking for. Similar to RebelROM, which also looks very cool.
Jellybam 5.2
Sent from my HTC One XL using xda premium
DESERT.TECH said:
Jellybam 5.2
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
jellybam is aokp and touchscreen will not work. You should read threads before just replying. other wise youre just wasting your time and ops time
I started this to see if anyone can list a few ROMs that work with T-Mobiles htc one s. Please help by listing the ROM you are on and by saying if the ROM has any issues; such as WiFi not working for example.
Sent from my HTC One S using xda app-developers app
I'll be first
Cm10 nightly- works excellent but it takes WiFi about 5 mins to kick in after I toggle it. If any one knows how to fix it please reply to this post
Sent from my HTC One S using xda app-developers app
I've been using $droyd$'s AOKP 4.2.2 ROM and the only issue is that as of right now, you can't record in 1080p. Other than that, its very smooth and fast.
Also if you were unaware before, wifi-calling doesn't work on any jelly bean rom.
Good luck!
Sent from my HTC One S using xda premium
tjsinghlion said:
I started this to see if anyone can list a few ROMs that work with T-Mobiles htc one s. Please help by listing the ROM you are on and by saying if the ROM has any issues; such as WiFi not working for example.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
WIFI issues are a nuance of this phone and the tmobile seems to be the most affected - it's different for each access point, user, phone, rom and firmware. In short you'll have to try it.
My tmobile worked with wifi on CM10 and CM10.1, it would not work with Viper until I downgraded my hboot (partial s-off enables some firmware write access) and flashed my wifi firmware. It get's interesting - I then put the old firmware back and the wifi still worked!!
Did you see the S-OFF thread? This will enable you to flash the radio firmware which will solve any problems.
Remember your WIFI channels - different countries use different range of channels and some access points 'helpfull' set the channel automaticlly. I have many devices that cannot cope with channel12.
Not trying to be a buzz kill here, but what's the purpose of this thread? I mean the Dev section is right over there, and the first page is flowing with fully working or close to fully working new ROMS.
Just saying.
I see what your saying. But honestly when you go through the a certain ROMs thread, they never say how WiFi doesn't work on T-Mobile phones. Or any of the problems Tmobiles users face.And who wants to go through a thread having to look for that one specific detail about a ROM whether or not to see if WiFi works. Also when looking through these ROM threads you find people that just like to say thank you (which there is nothing wrong with) that fill up the pages, making it harder to know if everything in that ROM is really going to work on your tmobile HTC one s, because people do search through comments to see what the users say. Therefore I made this thread for all T-Mobile users who want to post and say whether their ROM they are using works perfectly or if they are experiencing problems. And who wants to go through the process of flashing a new ROM without even knowing whether something like WiFi works. So yeah that's why i made this thread
Sent from my HTC One S using xda app-developers app
I get that, ROM posts can be a little all over the place sometimes. I didn't understand at first; I'm one of the few T-Mo users with pretty much no problems. It also doesn't help that the ROM database that some guy did in the Dev section hasn't been updated for some time.
Thankyou
skyline93r34 said:
I've been using $droyd$'s AOKP 4.2.2 ROM and the only issue is that as of right now, you can't record in 1080p. Other than that, its very smooth and fast.
Also if you were unaware before, wifi-calling doesn't work on any jelly bean rom.
Good luck!
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Ok thank you. Now i think im going to go Flash that rom. And also did you do anything specific to get your wifi working. and what Hboot are you on
If you are S-ON and have high HBOOT and want a Sense-based ROM with working WiFi, you were looking at TrickDroid 7 (TMOUS based), Unknown Retribution, and I think one more (Energy Blue, IIRC) that were based on recent updates. Since they were all based on the TMOUS ROM, everything should work without doing anything super special, including WiFi-calling. Virtuous Ville+ also had working WiFi, but no WiFi-calling. Recent CM 10.1 nightlies are working really well. At least, those are the ROMs I've used.
ardax said:
If you are S-ON and have high HBOOT and want a Sense-based ROM with working WiFi, you were looking at TrickDroid 7 (TMOUS based), Unknown Retribution, and I think one more (Energy Blue, IIRC) that were based on recent updates. Since they were all based on the TMOUS ROM, everything should work without doing anything super special, including WiFi-calling. Virtuous Ville+ also had working WiFi, but no WiFi-calling. Recent CM 10.1 nightlies are working really well. At least, those are the ROMs I've used.
Click to expand...
Click to collapse
Wait are you saying that Recent cm10.1 nightlies have wifi working on our device. and by wifi working i mean it automatically turns on, and not just hangs and turns on later .
I haven't had any WiFi hangs.
I just started using Liquid Smooth. Pretty nice IMO. The only issues I've notcied were a bluetooth hang that fixed after a reboot, and Voice search keeps crashing.
ardax said:
I haven't had any WiFi hangs.
Click to expand...
Click to collapse
so let me ask you a question. What radio are you on. And also what HBOOT version are you running
tjsinghlion said:
so let me ask you a question. What radio are you on. And also what HBOOT version are you running
Click to expand...
Click to collapse
Right now I'm on Viper 2.1.0 with the full firmware from the 3.16 WWE OTA -- I only made that jump because S-OFF makes it easy to switch without having to downgrade HBOOT. So HBOOT is 2.15 and Radio is 1.11.50.05.28. But I've just started using that and can't give you much in the way of impressions on WiFi stability yet. Just flashed it last night and didn't have any WiFi problems downloading my apps last night or weather checks this morning.
Before that I was using a recent CM 10.1 nightly on the TMOUS 2.35.531.10 firmware. So HBOOT 1.14 and 1.11t. I ran that firmware combination from shortly after its release until flashing Viper. ROMs in use were either CM 10.1 nightlies or Unknown Retribution (TMOUS 2.35 based).
ardax said:
Right now I'm on Viper 2.1.0 with the full firmware from the 3.16 WWE OTA -- I only made that jump because S-OFF makes it easy to switch without having to downgrade HBOOT. So HBOOT is 2.15 and Radio is 1.11.50.05.28. But I've just started using that and can't give you much in the way of impressions on WiFi stability yet. Just flashed it last night and didn't have any WiFi problems downloading my apps last night or weather checks this morning.
Before that I was using a recent CM 10.1 nightly on the TMOUS 2.35.531.10 firmware. So HBOOT 1.14 and 1.11t. I ran that firmware combination from shortly after its release until flashing Viper. ROMs in use were either CM 10.1 nightlies or Unknown Retribution (TMOUS 2.35 based).
Click to expand...
Click to collapse
noob question- What do you mean by TMOUS 2.35 based. And how does that affect the cm10.1 nightly
I mean ROMs that were built using T-Mobile US's 2.35 ROM as a base. Other Sense-based ROMs, like Viper, start with different ROMs as a base. The different Sense bases are part of the reason people run into WiFi problems when using ROMs originally created for other regions.
CM 10.1 has an entirely different heritage so it has its own ways of dealing with those issues.
tjsinghlion said:
Ok thank you. Now i think im going to go Flash that rom. And also did you do anything specific to get your wifi working. and what Hboot are you on
Click to expand...
Click to collapse
I'm on hboot 1.09 and the wi-fi worked right from the start.
p.s. sorry for the slow reply
Gotta Tell you the Viper 2.1.0 rocks...its fast awesome battery life and its got working wifi...not wifi calling but just wifi in general...it honestly is the best sense ROM...I have tried CM 10, Virtuous Ville+, P.A.C Man and even the ICS ROMs and I gotta say the Venom team makes an awesome product...:laugh:
"[rom][S4][15FEB]Updated_4.2.2_AOKP-Working-video" seems to work great with TMOUS hboot 1.14, added the new camera (in the post) with photosphere, The only little bug I found is the bluetooth doesn't list station info on my car stereo. I saw a tearing fix using bubba kernel, but I'm just living with it for now. Everything else seems to work great!
I just flashed the LiquidSmooth JB ROM from Droyd and this thing is amazing.. Coming from a rooted Stock Sense there really is no comparison, I might give Viper a try but this is clearly gonna be my daily driver
I'm currently on a pre 3.4 kernel ROM, and I am going to be upgrading to the latest cm nightlies. I think I have a good grasp on the steps that I need to take. but I am just unsure of a couple things..
-after Im done with s-off and the 3.18 ruu, do I have to reroot by reinstalling twrp, then reflash a rooted rom?
-Do I have to upgrade/downgrade my touchscreen panel after the transition proccess? or is that only necessary if I want to use a twrp version 2.3.3.1+? and if so, am I missing anything by staying on twrp 2.3.3.0 which has worked for me for the longest time?
-is the transition to 3.4 really worth it? are the screen tearing and lag, that plagued pre 3.4 roms fixed or improved? that's my main reason of upgrading other than the obvious one which is being on the latest and greatest..
I would really appreciate any feedback on this matter. I have been procrastinating on transitioning because I just don't know if It is really necessary. my phone is working just fine, albeit with the lag and some tearing. Thanks guys!
AT&T OneX
hboot 1.09
liquidsmooth ROM
s-on
Sent from my sexy One XL
JCon0320 said:
I'm currently on a pre 3.4 kernel ROM, and I am going to be upgrading to the latest cm nightlies. I think I have a good grasp on the steps that I need to take. but I am just unsure of a couple things..
-after Im done with s-off and the 3.18 ruu, do I have to reroot by reinstalling twrp, then reflash a rooted rom?
-Do I have to upgrade/downgrade my touchscreen panel after the transition proccess? or is that only necessary if I want to use a twrp version 2.3.3.1+? and if so, am I missing anything by staying on twrp 2.3.3.0 which has worked for me for the longest time?
-is the transition to 3.4 really worth it? are the screen tearing and lag, that plagued pre 3.4 roms fixed or improved? that's my main reason of upgrading other than the obvious one which is being on the latest and greatest..
I would really appreciate any feedback on this matter. I have been procrastinating on transitioning because I just don't know if It is really necessary. my phone is working just fine, albeit with the lag and some tearing. Thanks guys!
AT&T OneX
hboot 1.09
liquidsmooth ROM
s-on
Sent from my sexy One XL
Click to expand...
Click to collapse
After RUU you just need to flash TWRP again, I recommend using version 2.6. You can find it here. It has a much better wipe interface, plus you won't need to downgrade ts firmware. Then just flash a rooted ROM.
You don't need to downgrade your touchscreen firmware, unless you want to use older 3.0 kernel ROMs, and the first generation of 3.4 kernel ROMs.
I believe it's worth it for a few reasons. There is no screen tearing on the newer ROMs, there is an increased amount of ram available, plus some have reported an increase in performance and general smoothness since running the RUU.
Sent from my Evita
Yeah, what he ^^^^^^ said.
Sent from my HTC One X using Tapatalk 2
thank you for the response. when you stated that I need to downgrade my touch panel to use older roms, I'm quite not sure what are the first Gen 3.4 roms. how do I know if it's a 1st gen 3.4 rom or otherwise? I am intending to use cm 10.1 3.4 builds.
Sent from my sexy One XL
It will say so in the ROM op
Sent from my One X using xda app-developers app
You should be fine as long as you don't flash any nightlies from more than about two weeks ago I think. You'd be better off flashing the latest anyway I guess.
Or even better, the new cm10.2 (android 4.3) should be up and running properly soon. At the moment I think the only bugs are SMS/MMS and camera not working but they should be sorted pretty quickly I'd think. Plus that'll include the new cm Focal camera which looks pretty neat.
Sent from my Evita
timmaaa said:
You should be fine as long as you don't flash any nightlies from more than about two weeks ago I think. You'd be better off flashing the latest anyway I guess.
Or even better, the new cm10.2 (android 4.3) should be up and running properly soon. At the moment I think the only bugs are SMS/MMS and camera not working but they should be sorted pretty quickly I'd think. Plus that'll include the new cm Focal camera which looks pretty neat.
Sent from my Evita
Click to expand...
Click to collapse
...and bluetooth, which is really the dealbreaker for me, and why I haven't jumped on it yet. Either way though, you'll want to run through the upgrade process. It's only a little bit painful, and it'll "futureproof" your device for whatever else is new that comes down the line in the future.
just an update, I now have s-off. my next step is to ruu. I'm just wondering, can I restore the rom that I am currently on (liquidsmooth) through twrp, in which case I have to downgrade my touchscreen panel (cause its a pre 3.4 rom) after ruu? or do I wait to ruu after the 3.4 cm nightly builds gets more polished?
Sent from my sexy One XL
It depends what you want.
If you want to restore your backup, you'll need to flash TWRP, and downgrade your ts firmware.
Or you can flash TWRP, leave the ts firmware the way it is, and download one of the latest 3.4 nightlies.
Sent from my Evita
I was under the impression that as long as I use twrp 2.3 3.0 or 2.6 that I don't have to alter my tp? just an inquiry, should I go ahead and go to the 3.4 builds, or stay on my current rom? Is the new cm builds on par if not better than pre 3.4 roms albeit both has their own bugs?
Sent from my sexy One XL
Use TWRP 2.6, it's great and has no bugs, and you won't need to alert your ts firmware. People are still reporting a few bugs on 3.4 but I've run some of the 3.4 Carbon builds and they were solid.
Sent from my Evita
nvm. I think I got it now. I think I can't use ANY 3.0 aosp roms w/o downgrading tp period.. correct? so either I stay with my current rom and downgrafe my tp, or just flash the 3.4 roms. hmm.. I'm just trying to avoid messing around with the tp if I can help it.. idk.. just lazy I guess. I think I'm just going to take the plunge and go to new cm, and go from there if I don't like it... thank you so much sir..
Sent from my sexy One XL
i just finished the ruu process. I'm currently on the stock rom w/root thanks to twrp 2.6! I can't believe how I can get root access now from recovery.. I think I'll stick with stock rom for the meantime.. Im amazed at how my phone is running like new. I missed sense for a bit. I've been on aosp since cm 10.1 nightlies initially came out the first time.. man that was awhile there.... thank you all so much for helping me out! it's great to be back in the loop of things once again here in the community! cheers!
Sent from my sexy One XL
I don't use the phone for anything except web lookup, but I like it tiptop running...
What are the benefits to the 2.15 update ? I'm on 2.14 now . I saw with 2.15 u must use a 2.15 radio for best signal.
I'm wanting to also try a aosp/vanilla Rom . I know in the past you had to downgrade touch panels... With the newest 4.3 Roms is the downgrade required? Bc I'm seeing it is and some say it isnt...
2.15 prevents signal/data drops with Sense based ROMS for the most part. The firmware package includes the new radio 1.31a....
The touch panel downgrade is no longer required.
Try out Codefire X
Sent from my One X using XDA Premium 4 mobile app
---------- Post added at 05:28 AM ---------- Previous post was at 05:26 AM ----------
S-off required for firmware upgrade
Sent from my One X using XDA Premium 4 mobile app
No ts firmware downgrade is required for the current aosp ROMs, you're better off staying on the 2.14 firmware if you want to run aosp.
Sent from my Evita
hboot 2.15 is only recommended to resolve signal and random reboot issues with Sense 5 ROMs (and Sense 5 ROMs only). If you only intend to use AOSP, then its probably better to stay on 2.14 (as suggested above).
Great thanks for all the help. My htc one is lucky and both work but I was unsure on this phone. Much appreciated
Scozzar said:
I wouldn't be so sure if it's just for Sense actually. I was having drops on CFX, and so I flashed 2.15 and I stopped having drops. I can't be sure since I flash ROMs like an addict, so it's possible it was on the ROM itself.
Click to expand...
Click to collapse
The signal drops have been attributed to the Sense 5 powersave function, and it not playing well with the pre-Sense 5 radios. I'd be surprised if this had any effect on AOSP ROMs. Might be a related or similar issue, but I doubt its the exact same issue/cause. Could also be a placebo.
Although it is interesting to hear that at least anecdotally, someone is possibly seeing some benefit to being on 2.15 and running an AOSP ROM.
redpoint73 said:
Although it is interesting to hear that at least anecdotally, someone is possibly seeing some benefit to being on 2.15 and running an AOSP ROM.
Click to expand...
Click to collapse
i like that! :laugh:
2.15 had been a mess for me every other rom than sense dint even boot up!
Sonone said:
i like that! :laugh:
Click to expand...
Click to collapse
Well, these devices have far too many nuances for me to say he is absolutely right or wrong!
Just flashed and so far running almost perfectly! Loving it. Only bug I have noticed so far is that the quick settings toggle for GPS is broken. It is stuck greyed out on "Location Off", even when GPS is toggled on, and whether it is being actively used or not. Touching the toggle doesn't seem to change anything. Also along with that I just noticed that the GPS icon never appears in the status bar when being used like it would in Jelly Bean.
What launcher is everyone using? I wanted to stay KitKat based but also want a lot of the extra functionality like gestures and such. So far it seems Holo Launcher HD best fits that. Tons of customization and KitKat based. I'm missing a couple of things, mainly the swipe left for Google Now (just has Jelly Bean home page system), and the launcher font is the old Holo, so looks just a bit different than system font. But that's just nitpicking, I really like it so far. Just curious to see what other people are using.
Thanks JoshX!
This might be a dumb question, but would it be better or even necessary at all to update to the 2.15 firmware and/ord HBoot when using an AOSP ROM? The unofficial CM11 that JoshX built specifically, if that makes a difference. I ask because for CM10.2 I believe it was necessary to run the 3.18 RUU prior in order to be on the 2.14 firmware (maybe I'm mistaken about why?). I haven't flashed or done much anything with my phone until recently, so I just noticed that there is now a 2.15 HBoot. I'm running CM11 at the moment and my bootloader shows 2.14 HBoot.
Just a bit confused and was curious, thanks in advance.
icu64 said:
That's normally the radio that handles that but keys double check. Did you do the 2.15 hboot/firmware update?
Sent from my One X using Tapatalk
Click to expand...
Click to collapse
I'm running Torched KK B2.1 with CM11 at the moment but I am on 2.14 firmware. Should I update or is it not necessary?
Chrysis said:
I'm running Torched KK B2.1 with CM11 at the moment but I am on 2.14 firmware. Should I update or is it not necessary?
Click to expand...
Click to collapse
Not necessary, it's only necessary for Sense 5 ROMs.
Sent from my Evita
@Chrysis
Please note, there is no need to repost a question that has already been answered. Please keep your questions on this subject in this thread.
Thank you
timmaaa said:
Not necessary, it's only necessary for Sense 5 ROMs.
Sent from my Evita
Click to expand...
Click to collapse
Got it, thanks! If I wanted to update to a newer radio from that firmware though, would it still be unecessary? Just read a few times that firmwares and radios are typically bundled, so wanted to double check.
TonyStark said:
@Chrysis
Please note, there is no need to repost a question that has already been answered. Please keep your questions on this subject in this thread.
Thank you
Click to expand...
Click to collapse
My bad, I didn't see the post in the kernel thread until after I started this thread. Will keep it to one place in the future!
The first post that's here now I did mean for the ROM thread though, it was separate from my question about the new hboot. Would it be alright if I posted it back to that thread? Thanks. Apologies again for repeating my question elsewhere.
It's basically suggested to use the radio (1.31) that's bundled with the 2.15 firmware for proper use with a Sense 5 ROM. In any other situation you can use whatever radio you want really. Anecdotally I have tested the 1.31 radio while on the 2.14 firmware and it performed terribly. That may have been confined to my experience though, you can always test it yourself. If a radio doesn't work well it's super easy to just flash another one.
Sent from my Evita