Database Info

Sense vs AOSP

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

[Q] 2.15 HBoot for AOSP ROM?

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

[Q&A] [ROM][UNOFFICIAL][4.4.4][OCT-16] CyanogenMod 11 HTC One S [hboot 2.16]

Q&A for [ROM][UNOFFICIAL][4.4.4][OCT-16] CyanogenMod 11 HTC One S [hboot 2.16]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

where is 16/10 nightie?
cikoleko said:
#Added 16/10
#NOT Tested
Last commit:
Click to expand...
Click to collapse
I only see 17/10 night build and surprisingly links to 18/10, althrough these 18/10 links leands to 404 - page not found.
I'm asking because I believe something goes wrong with latest build.
my android.phone app keeps crashing all the time even after I reinstall M11 from scratch.
and maybe it's only a side effects of my todays experiments, but after fastboot flash boot boot.img I see that HBOOT still stays with version 2.15, instead of expected 2.16.
is it normal? or is it my own fault?

pavel.bosco said:
I only see 17/10 night build and surprisingly links to 18/10, althrough these 18/10 links leands to 404 - page not found.
I'm asking because I believe something goes wrong with latest build.
my android.phone app keeps crashing all the time even after I reinstall M11 from scratch.
and maybe it's only a side effects of my todays experiments, but after fastboot flash boot boot.img I see that HBOOT still stays with version 2.15, instead of expected 2.16.
is it normal? or is it my own fault?
Click to expand...
Click to collapse
Check both links and double check the latest files:
https://drive.google.com/?usp=chrome_app#folders/0B_THDHRTYTJTQlBlb0lqYXJjTWs
http://forum.xda-developers.com/devdb/project/?id=2604#downloads
The ROM in this thread is made for HBOOT 2.16 users, if you have HBOOT 2.15, this ROM isn't compatible with your firmware. There's official CM11 thread for HBOOT 2.15
Basically if you're on HBOOT 2.15 you use OFFICIAL builds, if you're on HBOOT 2.16 you use UNOFFICIAL BUILDS.
I only see 17/10 night build and surprisingly links to 18/10, althrough these 18/10 links leands to 404 - page not found.
Click to expand...
Click to collapse
From what I understand you are referring to CMXLOG, if you have HBOOT 2.16, this is only to show what changes have been made to the ROM as they are identical to what is included in the OFFICIAL CM11 ville builds but you can't download and flash it on HBOOT 2.16. Again it's just to check what has been added to the build.
So because my builds are UNOFFICIAL, I build when I can. For example if the OFFICIAL NIGHTLY was released on 17/10 but the latest commit of that NIGHTLY was merged on 16/10 and straight away I built that, that's why the date differs.

cikoleko said:
Check both links and double check the latest files:
https://drive.google.com/?usp=chrome_app#folders/0B_THDHRTYTJTQlBlb0lqYXJjTWs
http://forum.xda-developers.com/devdb/project/?id=2604#downloads
The ROM in this thread is made for HBOOT 2.16 users, if you have HBOOT 2.15, this ROM isn't compatible with your firmware. There's official CM11 thread for HBOOT 2.15
Basically if you're on HBOOT 2.15 you use OFFICIAL builds, if you're on HBOOT 2.16 you use UNOFFICIAL BUILDS.
From what I understand you are referring to CMXLOG, if you have HBOOT 2.16, this is only to show what changes have been made to the ROM as they are identical to what is included in the OFFICIAL CM11 ville builds but you can't download and flash it on HBOOT 2.16. Again it's just to check what has been added to the build.
So because my builds are UNOFFICIAL, I build when I can. For example if the OFFICIAL NIGHTLY was released on 17/10 but the latest commit of that NIGHTLY was merged on 16/10 and straight away I built that, that's why the date differs.
Click to expand...
Click to collapse
thank you for such detailed answer. indeed I felt into huge hole full of interconnected misunderstandings. for some reason I decided that official only supports 2.16 and also makes lot of such wrong assumptions.
I don't know that happens with my official CM11, but really android.phone app on it started to crash again and again after some update. nothing helps.
hopefully my journey finished successfully. I'm now S-OFF, rooted, superCIDed and on HBOOT 2.16 with almost latest nightly _unofficial_ CM11 build. two days lost on that way.
sorry if my post makes any confusion and thank you for your patience and every day job on handling this builds.

Just tested SNAPSHOT-M11/PA-GApps (stock package) clean install after factory reset, everything is working fine.

cikoleko said:
Just tested SNAPSHOT-M11/PA-GApps (stock package) clean install after factory reset, everything is working fine.
Click to expand...
Click to collapse
so I'm on 11-20141016UNOFFICIAL-ville. Phone works, no problem, thanks
if I press "system update" I see cm-11-201410[17, 18, 19]-NIGHTLY (3 updates), are they all compatible, i.e. unofficial? or this is not how it's supposed to work with unofficial ROM? is the update procedure for UNOFFICIAL differ from OFFICIAL one?

pavel.bosco said:
so I'm on 11-20141016UNOFFICIAL-ville. Phone works, no problem, thanks
if I press "system update" I see cm-11-201410[17, 18, 19]-NIGHTLY (3 updates), are they all compatible, i.e. unofficial? or this is not how it's supposed to work with unofficial ROM? is the update procedure for UNOFFICIAL differ from OFFICIAL one?
Click to expand...
Click to collapse
I actually already explained it in the thread, if you read below 'installation instructions' you'll see it:
NOTE: Don't install updates offered by OS as they are official updates and are not compatible with hboot 2.16
Click to expand...
Click to collapse

cikoleko said:
I actually already explained it in the thread, if you read below 'installation instructions' you'll see it:
Click to expand...
Click to collapse
got it, thanks. I was mistakenly thinking that you talk about market apps updates and I was trying to escape them.

Wow, having FM supported sound very promising.
Is it my only experience of sound during the call is really low?
Both loud speaker and phone are difficult to listen during the call.
But navigator application which I use, speaks very loud, just as it did on stock FW.
is a problem with application? How can I tune it to work better?

the FM app you mentioned works fine with 16-10-2014 nighty build
thanks for pointing out. I only doubt why it request so lot of capabilities, like root (?), blue tooth, calls and so on
but it seems to work, which is avesome.

cikoleko said:
After I done it my phone is stuck on boot animation
Click to expand...
Click to collapse
as I understand, default editor for some reason fails during save of that file, I edited it using laptop and put it back in recovery, setting 755 permission. After that phone boot up successfully.
You can "repair" stucked phone next time with original file from ROM image.
mikronac.ns said:
Hey HBoot 2.16 lovers. Have you random reboots sometimes?
Click to expand...
Click to collapse
yes, I see about 3 times per week, and not sure how much times I just don't see it, since I don't set up any PIN lock
not sure what is the reason and that are the circumstances

cikoleko said:
#Added 02/11
#NOT tested
Click to expand...
Click to collapse
please have a look at next nighty, seems like this bug-fix http://review.cyanogenmod.org/#/c/76150/ could make voice during the call sounds better, isn't it?

cikoleko said:
#Added 08/11
#NOT tested
Click to expand...
Click to collapse
I couldn't comment on main thread. Just wanna say I flash this ROM and this time sound is much louder, it is such good as it should be.
so if you or someone else have same problem with volume as I did, try this ROM, hopefully it is better.
I've not tried anything else so far, at least it started and could answer and make a call

[ROM][UNOFFICIAL][4.4.4][OCT-16] CyanogenMod 11 HTC One S [hboot 2.16]
Hi,
I installed CM11 a week ago and I noticed that the phone does not vibrate! Today I did the update to the latest version and still doesn't work .. I have searched on the internet but cant find a solution.
Any tips?
Thanks

[Q&A] [ROM][OFFICIAL][KitKat 4.4.4][Ville] PAC-ROM 4.4.4.RC-2

Q&A for [ROM][OFFICIAL][KitKat 4.4.4][Ville] PAC-ROM 4.4.4.RC-2
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

atrus5 said:
New build is up. Just some minor changes and fixes to the build. Here is the link. https://s.basketbuild.com/dl/devs?dl=pacman/ville/dev/pac_ville_4.4.4.RC-2_20141019-003708.zip
Click to expand...
Click to collapse
Bluetooth is really broken for me.

Pilipin said:
Bluetooth is really broken for me.
Click to expand...
Click to collapse
Can you send a logcat of what happens when you use Bluetooth

@atrus5 Have you added a custom kernel yet? If not, i'm working on one with @javelinanddart and possibly @AKToronto, but I'd need help compiling it. It always fails for me.

josepha19223 said:
@atrus5 Have you added a custom kernel yet? If not, i'm working on one with @javelinanddart and possibly @AKToronto, but I'd need help compiling it. It always fails for me.
Click to expand...
Click to collapse
I don't add custom kernels to the build. I guess I could but I feel the user can add whatever they want afterwards instead of having one built in. I am not the best person to ask for building a kernel as I don't do that kind of thing. I just like building the roms and testing them.

atrus5 said:
I don't add custom kernels to the build. I guess I could but I feel the user can add whatever they want afterwards instead of having one built in. I am not the best person to ask for building a kernel as I don't do that kind of thing. I just like building the roms and testing them.
Click to expand...
Click to collapse
Well let me know if you want to. you did add a poll so i was just wondering

josepha19223 said:
Well let me know if you want to. you did add a poll so i was just wondering
Click to expand...
Click to collapse
Yeah sorry that poll was from the very beginning of the thread and I can't get rid of it

hello got error flashing Lates PacMan build 4.4.4 pac_ville_KK.RC-3.dev_20141129-123111
E:Error executing updater binary in zip
Click to expand...
Click to collapse
Hboot 2.15, S-off, radio 1.11, TTWRP 2.5.0.0
pls help
upd. Flashing TTWRP 2.8 - fixed problem. Sry for diturbing

BorHblK said:
hello got error flashing Lates PacMan build 4.4.4 pac_ville_KK.RC-3.dev_20141129-123111
Hboot 2.15, S-off, radio 1.11, TTWRP 2.5.0.0
pls help
upd. Flashing TTWRP 2.8 - fixed problem. Sry for diturbing
Click to expand...
Click to collapse
yeah i was gonna say just update your recovery but you got it

Calling out gives blank screen
Hey - new to the forum here, and I know this rom is discontinued for the ville, but perhaps someone can point me in the right direction;
When I want to place a call, the screen goes blank. The call itself is being made, but I cannot get the screen to work again. Even after the call disconnects. Only way, is to lock screen with power button (still blank) and press power button again to go to unlock screen.
This problem is also for incoming calls only after picking up the phone.
This is what I did to the phone so far:
- Unlock bootloader via HTC site
- Root phone
- Install TWRP
- Flash PACROM , PA GApps, Update-SuperSU, flash boot.img in fastboot
My setup:
HTC One S S4
HBOOT 2.15
Radio: 1.11.50.05.28_10.27.50.08L
Kernel: 3.4.82
ROM: pac_ville 4.4.4 20141231
S-ON
TWRP: 2.8.6.4
SuperSU 2.46
I have looked around in the threads here but seems no-one else is having this problem.

Can you try to use a different gapps. Pa adds info to there gapps. Use the gapps from the op.

Actally it was the proximity sensor that was giving issues, I used a calibration app to set it manually and since have been using Pacman happily. God it would be great to see a LP PACMAN for the Ville

krillin2112 said:
Actally it was the proximity sensor that was giving issues, I used a calibration app to set it manually and since have been using Pacman happily. God it would be great to see a LP PACMAN for the Ville
Click to expand...
Click to collapse
Glad you found the problem and fixed it.
It won't be me making the build. If anyone else wants to that would be great.
Sent from my Nexus 5 using XDA Forums

Yeah I read you no longer have a working Ville. I really do like the ROM and maybe one day someone can make a LP build. There is one for the HTC One (m7 & m8). Don't know how much work it would entail to adapt that to Ville.

Where to find a htc sense-based/stocknear rom?

Right now I am running Cyanogenmod 12 on my HTC One S.
In terms of getting hboot 2.16 (to get more app storage) I need my phone to be S-OFF.
So now I am trying to get S-OFF using SunShine.
The problem: «SunShine encountered problems with your rom. Please flash a stock, or more near stock rom and try again.»
So where to find a nearstock rom? Is it the right approach to just try some random rom with sense in its name?
Thanks for any help!

The "random rom with sense in its name" you've linked is a Sense-based ROM. Its safe to use.

Renan Lazarotto said:
The "random rom with sense in its name" you've linked is a Sense-based ROM. Its safe to use.
Click to expand...
Click to collapse
I have tried to go with that one. Unfortunately it seems to only work with Hboot 2.16. I do only have Hboot 2.15 ... Any other ideas which rom is stock rom enough?

Castor-designs said:
I have tried to go with that one. Unfortunately it seems to only work with Hboot 2.16. I do only have Hboot 2.15 ... Any other ideas which rom is stock rom enough?
Click to expand...
Click to collapse
There is a thread fixed somewhere with stock RUUs to download. Use them to return your phone to stock.

Renan Lazarotto said:
There is a thread fixed somewhere with stock RUUs to download. Use them to return your phone to stock.
Click to expand...
Click to collapse
I feel like I have tried every rom with sense in its title. Either I suck at finding this thread you are talking about or it does not exist or it does not work? :/ thanks for your help anyway