[HTC One S] Rapier:
Sorry but it sounds like a ****. No offense to you, I really appreciate your work but those ARE bugs and noone can tell me that if it is an option to always keep the hardware buttons lights on and it doesn't, this is intended behavior...or the font size option. Really? This is how it should be? Pretty amazing setting then if it doesn't do anything. Maybe it's time for other devs on which ROMs these ARE working, to make some changes and make those settings do nothing. I would rather appreciate a straight answer like "I don't care" or "it has a low priority" than such bull****. Too bad some ROMs are good but are dragged down by devs attitude

Sent from nowhere over the air...

---------- Post added at 02:46 PM ---------- Previous post was at 02:42 PM ----------

Now I am on latest 4.4.240 and font setting does not change anything even after a reboot. I wasn't using Beanstalk lately since 4.4.200 cause I lost my backup as I said. This is first build I tried in the last period

Sent from nowhere over the air...

EDIT: OK, I was pissed of. Now I'm calm :) I see Scott took a closer look and he does admit that the font resizing doesn't work

I can understand a devs anger when someone is just saying bad things about his ROM but the fact is I DO like this ROM. Beanstalk and Twised are my favorites and I switched to Beanstalk from Twisted yesterday just to try to flash this last build and test it. I can't build, I'm not a dev but I can hel with advices where I know and by finding bugs to help improvement of the ROM. I would love to see a perfect software but there's no such thing. In my day to day job I manage an IT Quality Control team so testing is what I do every day.

Now back to the list with some arguments...If I may and won't be considered offending:

- the "network event notification" is not working...it doesn't do anything OR it was removed from the dialer settings in some ROMs. This is not "intended behavior" for sure.

- the font resizing and "huge font" option in accessibility does not work. This was confirmed by Scott so I can only say I've notced on this last build. Unfortunately I didn't test 4.4.225 or 4.4.230 because I couldn't flash them

- opening a messaging app like Messaging or Whatsapp by tapping on the Halo notification, opens the app in the small window but clicking on the text input field does not open the keyboard. It takes several taps/long taps to open it. Also the "send" arrow does not work to send the whatsapp message or SMS. I also doubt this is intended behaviour. What's the point in opening the app from Halo notification if I can only read it and not reply? I can just check the status bar notification for that. Having keyboard not opening or having the "send" arrow not active, makes replying a difficult task

- the option to keep hardware button light on all the time (in Settings-Buttons), does not work. The light goes off after approx 5 secs regardless of the setting. This also is a bug...it's not related only to this ROM, I found this issue in several others, but it is a bug. Dragging the timing slider all the way to the right should keep the lights on as long as the display is on. And YES, some want it like this and that's why the option to change the timing exists. I don;t care about the battery saving of 0.00001% due to the fact the lights goes off earlier, I care more about the fact I have to dig after the buttons location when I'm in a dark room. If a dev would like to have it off after 5 secs in his ROM as an intended behaviour, he could just set it like this and take out the setting. But if the setting is there it should work

- in Settings-Battery, the device is shown as "awake" all the time. No need to comment here, is confirmed and set as low priority

- when setting a "Custom carrier label" (in Settings-Beanstalk Options-Misc options), the name is shown twice if "show WiFi network name" is active. OK, I can accept this is an intended behaviour if the dev say so

- when setting a "Custom carrier label" (in Settings-Beanstalk Options-Misc options), the name is shown in ALL CAPS regardless of the way it's written. (for ex it displays "ASSASSINS" even if it was written as "AssaSsinS". OK, I can accept this too as intended behaviour

- there is no "kill app by long press of back button" in either Settings-Buttons or in Developer Options OK, if the dev doesn't want it in his ROM is his decision. I've not posted it as a bug, more like an useful feature that is missing and most have it incorporated especially if they have included hardware remapping functionality

- "Large text" option in Settings-Accessibility has no effect (related to the "Font size" issue). This is confirmed not working

- when Active Display is on and receive a notification, in most cases dragging the handle to the left (to open the notifying app), brings first the lock screen instead of directly going to the app. It is a bug and it's also not present only here. On ALL KitKat ROMs is the same. And it is not intended like this because SOMETIMES the app opens directly sometimes not...so eitherway it is a bug. And on previous Android versions, also on Beanstalk 4.3 it was always opening the app directly. Now someone will tell me THIS is the way it should work and before t was bugged? Really?

- when Active Display is on, and the app that generates the notification is open, you cannot type and reply, the text input field is "frozen" (nothing can be typed). You have to press back and close the app completely, then open it again to be able to reply (tested with Messaging/SMS and whatsapp. Same as the above comment

Now counting the above, I can see only THREE issues that could be considered "intended behaviour" from a list of 11 initially reported. I can also admit that some are not valid due to the fact I didn't flash the ROM clean, Ville is not supported officially and so on...But at least Scot could have said that, not that this is how they should work

Sorry again for the trouble I make but I'm used to fight for my opinions and lame excuses or objections not sustained by facts or proofs don't change my mind

EDIT: I've created an account and replied to Scott there just to make it quicker. Now if he will take them into consideration or not, it's a different story...will see