Related
I am typically a silent browser. However I need some assistance.
I currently have a t mobile Sensation and naturally s-off(Perm).
I am very familiar with flashing roms as I must have flash at least 20 roms with my N1.
If Sense is any different, regarding flashing then I'm having issues with my current speed.
All directions on downloading the latest rom and kernal have been followed, which prompted me to test my Dl/Ul speeds with speed test. I'm in a very good coverage area and on a stock rom I was averaging literally 8 dl/1.75 ul.-Mbps. No wifi.
On my modified rom I cannot get past 4 dl/0.75 mbps.
Now I understand we have a new set of oc that is built into the rom, however before I installed setcpu my speeds were not all the different.
Please advise what I am doing wrong.
Sent from my HTC Sensation Z710e using XDA Premium App
wrong radio?
i have to agree, it might be your radio..make sure it is the newest radio and check your tmobile apn settings. try internet2.voicestream.com
hope this helps.
mofoahh said:
i have to agree, it might be your radio..make sure it is the newest radio and check your tmobile apn settings. try internet2.voicestream.com
hope this helps.
Click to expand...
Click to collapse
internet2.voicestream.com is NOT for 3G/HSPA/4G (whatever you want to call it). Must be epc.tmobile.com.
mofoahh said:
i have to agree, it might be your radio..make sure it is the newest radio and check your tmobile apn settings. try internet2.voicestream.com
hope this helps.
Click to expand...
Click to collapse
Fair enough, and appreciate the help. Now, this was a concern of mine prior to flashing as I did not even flash a new radio, as opposed to my N1 where I would go with the latest CM radio suggestion.
Where would I locate a radio as I still don't have rights to ask a Question in A&D, but interactions > date of registration.
you could try finding one in the custom rom topic you are using. Usually they will recommend which radio to go with the custom rom.
cheers!
Confirmed on the slower speeds, also using LeeDroid. My APN is epc.tmobile.com. Have flashed the latest radio..audio went back to shipping radio but problem persists.
Sent from my HTC Sensation Z710e using XDA Premium App
Guys, try to manually put APN in.
thats why im still on stock rom s-off perm root. wants you start flashing custom roms thats when you lose everything your phone had from the start. its still in the early stage for custom roms for the sensation i will wait till around december before i flash thats enough time for devs to really work out the kinks. remember most off the roms here were maid before s-off so the devs really did not have a system to work on intill now
phonegod said:
thats why im still on stock rom s-off perm root. wants you start flashing custom roms thats when you lose everything your phone had from the start. its still in the early stage for custom roms for the sensation i will wait till around december before i flash thats enough time for devs to really work out the kinks. remember most off the roms here were maid before s-off so the devs really did not have a system to work on intill now
Click to expand...
Click to collapse
December wow lol. I'm running LeeDroid v1.1 w/ kernel v1.2 and it's already amazing. Everything works flawlessly and he got rid of the lag that was in the Stock TMo ROM. Plus Overclock'ed kernel w/ UV coming soon. ROM is super stable, fast as hell, and battery life is much better. To me it's a no brainier, nothing to lose.
Some of the Devs had S-OFF before we did, and most have been putting out ROMS long before the Sensation. No reason to wait til December but hey that's just my opinion!
bigmase521 said:
December wow lol. I'm running LeeDroid v1.1 w/ kernel v1.2 and it's already amazing. Everything works flawlessly and he got rid of the lag that was in the Stock TMo ROM. Plus Overclock'ed kernel w/ UV coming soon. ROM is super stable, fast as hell, and battery life is much better. To me it's a no brainier, nothing to lose.
Some of the Devs had S-OFF before we did, and most have been putting out ROMS long before the Sensation. No reason to wait til December but hey that's just my opinion!
Click to expand...
Click to collapse
dude i check every rom thread everyday i always read threw people have problems on all thows roms. yes they fast etc. but some how i still read about a problem i dont have right now and i dont fill like trouble shooting everyday right now i did that with the hd2 it can be a pain. so im good for now i will still wait i love my stock rom i just got it de-odex so i can theme it also i want a tmobile us rom tweak not a euro rom
phonegod said:
dude i check every rom thread everyday i always read threw people have problems on all thows roms. yes they fast etc. but some how i still read about a problem i dont have right now and i dont fill like trouble shooting everyday right now i did that with the hd2 it can be a pain. so im good for now i will still wait i love my stock rom i just got it de-odex so i can theme it also i want a tmobile us rom tweak not a euro rom
Click to expand...
Click to collapse
I understand where you're coming from but the issue of people having problems isn't ever going to go away. That doesn't mean it's the ROMs/Devs fault. There are so many variables involved including a big one - the user.
Everything might work perfectly for one person, while there is a "bug" for another. Well that person may not have read the entire thread/wiped when supposed to/cleared data etc. All the things many of us who have been flashing a long time have learned to do by default before asking questions. I don't check all the other threads that often so I don't doubt you, but you never know until you try. You may flash now and have no problems. It's sorta like, if you don't want to "troubleshoot", why are you flashing ROMs to begin with?
Either way your answer of "this is why I haven't flashed a custom ROM" isn't helpful to the OP or any of us because we HAVE flashed custom ROMs
I'm toying with some build.prop settings as I did on my Nexus One and I'm seeing some improvement in speeds on LeeDroid.
I'll post more in a bit..
bigmase521 said:
I understand where you're coming from but the issue of people having problems isn't ever going to go away. That doesn't mean it's the ROMs/Devs fault. There are so many variables involved including a big one - the user.
Everything might work perfectly for one person, while there is a "bug" for another. Well that person may not have read the entire thread/wiped when supposed to/cleared data etc. All the things many of us who have been flashing a long time have learned to do by default before asking questions. I don't check all the other threads that often so I don't doubt you, but you never know until you try. You may flash now and have no problems. It's sorta like, if you don't want to "troubleshoot", why are you flashing ROMs to begin with?
Either way your answer of "this is why I haven't flashed a custom ROM" isn't helpful to the OP or any of us because we HAVE flashed custom ROMs
Click to expand...
Click to collapse
dude i was just saying get off it already
The problem has to do with the EURO base. After all my testing, this is why I am purely making TMOUS based roms.
XDA Member: Rsotbiemrptson - wrote to me, what discovered that all .RIL files and build prop from TMOUS had to be transferred to the EURO based rom for the speeds to match TMOUS HSPA+ speeds. Then repacked the zip, resigned and flashed.
az93civic said:
The problem has to do with the EURO base. After all my testing, this is why I am purely making TMOUS based roms.
XDA Member: Rsotbiemrptson - wrote to me, what discovered that all .RIL files and build prop from TMOUS had to be transferred to the EURO based rom for the speeds to match TMOUS HSPA+ speeds. Then repacked the zip, resigned and flashed.
Click to expand...
Click to collapse
Hmmm, interesting. Care to share? We could pass it on to LeeDroid for his ROM as well?
I think he is right
I believe the issue lies in not having the correct RIL, along with a few tweaks to the build.prop... Only thing is how do you extract the RIL from the stock ROM? I pulled the files I think go with it from \system\lib and \system\bin but I am kinda scared to flash this zip I made... haha
Oh just an FYI you can run getprop "gsm.version.ril-impl" on the Terminal Emulator and/or ADB shell the stock ROM is HTC-RIL 2.2.0159HMQ so I just need to learn how to pull the needed files and create a flashable zip that would install the correct RIL into a custom ROM... if someone far more experienced could tell me how... or if they just wanted to do it, have at!
Just ran a few Speed Test runs with the new LeeDroid ROM, and my TMOUS 4G speeds seem to be right where they should be for my signal strength here (at 2 bars, I'm getting about 4-5Mbps down, 2-3Mbps up).
I did do a Super Wipe before installing the ROM - could that have been a factor?
I'll try to do some more testing when I'm in a 4-bar signal area, just to be sure.
kevsteele said:
Just ran a few Speed Test runs with the new LeeDroid ROM, and my TMOUS 4G speeds seem to be right where they should be for my signal strength here (at 2 bars, I'm getting about 4-5Mbps down, 2-3Mbps up).
I did do a Super Wipe before installing the ROM - could that have been a factor?
I'll try to do some more testing when I'm in a 4-bar signal area, just to be sure.
Click to expand...
Click to collapse
I did a Superwipe, had no affect
So I found a tool on XDA that allows me to put the ROM of choice to be ported and the base ROM. I'm trying to port Paranoid Android 2.00 since we don't have it, and now that we have somewhat steady CM10 nightlies I *should* be able to use it as a base. (The tool is called RomPorter)
So I went ahead and compiled a ROM, but I'm not sure if I should flash. I mean if it was this easy to port ROM's wouldn't we have ROM's just popping up everywhere? I used the HTC One X International version's PA 2.00 as the input ROM btw. I have some coding experience in Java but if it's this easy to port without any coding required why hasn't it been done yet? Just curious. I looked at the CM9 guide to porting PA and I have to make a linux portal and all those things. Basically my main question is, will this work? I don't want to flash and end up hard bricking my phone. I went and checked the build.prop, and framework and it all seemed like a hybrid of CM10 nightly and Paranoid Android 2.00 but is there something I'm missing?
Thanks a lot guys! I'm tired of just being somebody who stands on the side and waits for things to get ported or created. I'm taking a heavy load in college but I want to try and port something at least to contribute.
Using the international base could cause a brick unless you ported an evita kernel too. The international one x has a different partition layout as well.
Read read read, check, double check and triple check. When your confident its possibly bootable, sure that it is not harmful THEN flash it to your device first. Ports are always going to start with bugs. Don't expect perfection, expect a WIP. Importantly, have fun learning. Most importantly , FIRST FLASH IS ALWAYS YOURS :beer::beer:
Added People port roms all the time for themselves. Now posting one on xda and maintaining a thread with dozens-hundreds of followers is a WHOLE DIFFERENT STORY
I just want to try it but I'm afraid it'll brick. I mean what's the worst case scenario? Boot loop then restore to my nandroid? Or being stuck with a brick forever? I don't have a backup phone at the moment lol. Maybe I should invest in one.
If you flash something that overwrites hboot you're hard bricked. That's what I meant by different partition layout.
Here's a easier start for jb paranoid Android port.....dload the HTC evo 4g lte jb paranoid port rom, unzip it, delete the included boot.img, use a hox boot.img from a hox jb rom to replace it with. Zip it and flash it.(use the one XL cm10 boot.img) It will give u a bootable port of jb paranoid Android. Then like most ports, you will start fixing bugs. Camera and wifi won't work, you will need to fix those for sure. But a lot will work so start with priority bug fix#1 and keep on goin
Added: paranoid android rom I would consider the land of the brave for first time porting. U may encounter fixes to be harder than some less modified roms.
I understand now what the scare was. But when taking the Evo LTE ROM and pushing our own boot.img it'll allow me to at least get it started to see what I need to get going and fix! That's a fantastic idea. I'm going to head over there now and see what ROM's they have. I mean technically we share very similar devices internally right? I haven't looked into the Evo specs much.
Shaddy-Z. said:
I understand now what the scare was. But when taking the Evo LTE ROM and pushing our own boot.img it'll allow me to at least get it started to see what I need to get going and fix! That's a fantastic idea. I'm going to head over there now and see what ROM's they have. I mean technically we share very similar devices internally right? I haven't looked into the Evo specs much.
Click to expand...
Click to collapse
make sure you pull out any radio images you find in the roms you look at.
Could I push the ones from a cm10 nightly?
No idea. Probably. Or just don't include one.
getting in contact with the developer for the Evo PA ROM. Hopefully this goes somewhere.
Don't we already have a pa rom? You've inspired me though. I'm going to look at porting roms too.
The PA ROM is still ICS, and the biggest killer is that the multi-touch fix is not incorporated because the ROM was cooked pre kernel release unfortunately. The latest update the dev was supposed to release didn't boot and I don't know what happened after that.
And do it! The more devs the better. I want some variety in this little community.
By the way, PARANOIDANDROID 2.00 is not out yet. The last OFFICIAL release is 1.992: Changelog. As for the port, I would love to port roms to our device, since it is my primary device.
I already port ROMs from the i9100 to i777(SGSII Internation to AT&T US Version), but this is a VERY simple operation. And you can use a pre-made program to port by ktoonsez called Flashaholics, but it is only for porting to the i777. I hope we eventually get that far but these 2 devices are far more similar that the One X/OneXL or Evo LTE/One XL.
Just use the latest paranoid rom with the latest cm10 boot.img. I did it a few times when I had my hox. And gunny is right. Either pull the radio or flash a hox radio after u flash ur port and u will get signal with working talk, text. 3g should work too, mms won't, streaming video will be iffy. Just run thru the major stuff, write down what's broken, prioritize it, then always make a nandroid of your previous build so u can revert back if fixes make things worse
---------- Post added at 01:09 AM ---------- Previous post was at 01:03 AM ----------
He's gonna work off a unofficial paranoidandroid jb 4.1 from the evo lte. It'll boot but there will be plenty of fixing to do. I think its for his use/learning, not sure if he plans on putting it up on forums
I don't plan on uploading it to the forums unless I get the features working. I'm off all day tomorrow so I'll probably give it a shot to see what I can do.
I also realized PA is not 2.00 after I posted that, buts its still a JB Paranoid ROM so it'll do for now while I learn.
It's really good seeing someone (who isn't a regular dev that I know of?) taking such initiative and asking the right questions and such in order to get some dev'ing underway.
Great job! :good:
stnguyen09 said:
It's really good seeing someone (who isn't a regular dev that I know of?) taking such initiative and asking the right questions and such in order to get some dev'ing underway.
Great job! :good:
Click to expand...
Click to collapse
Thanks! I appreciate it So I got a little ahead of myself and tried it tonight, I'm slowly following a guide and I THOUGHT I was doing everything correctly but it won't flash after "Verifying system partition size" and I got an error. This seems to be a common problem that leads to the updater script, so I'm going to take a look at it when I get up. Could just be a syntax error, or maybe I'm just building it wrong I'm kinda tired
U can always nab the updater script from cm10 hox also. Its been a while and I forgot to mention that. I had the same issue with the evo rooms and that did the trick:beer:
I tried: using the ports updater, the base, and a collaboration of the two and it still didn't go through. Maybe its something else ? I'll try it again to double check.
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 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