Develop Bugs

[Q] Hack for enabling landscape in Sense?

Sorry if this has been raised elsewhere, but I couldn't find it anywhere...
I know many don't like HTC's Sense. Personally I like it fine, with the huge exception that I can't use my phone in landscape half the time. I don't suppose it would be possible to enable landscape would there?
I'm running rooted stock 2.2.

Do you mean on the home screen???
Sent from my PC36100 using XDA App

jm5503 said:
Do you mean on the home screen???
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
yeah the home screen for sure, but since contacts, calendar, music, etc... are all modified by sense then none of them can go landscape either.

This is the number 1 reason why I don't use sense/Rosie. Its utterly ridiculous that sense doesnt do landscape.

MSmith1 said:
This is the number 1 reason why I don't use sense/Rosie. Its utterly ridiculous that sense doesnt do landscape.
Click to expand...
Click to collapse
The sad part is all the images are there (in the framework) for Rosie to go into landscape, they just don't let it. I've seen a mod done that accomplishes this but it looked terrible and would have taken a lot of work to get all the elements to look right. Maybe they gave up and decided to focus on a more important project.. like Sprint Nascar.. or the Sprint Promotion app..
Rosie has such potential but is such a let-down. If they weren't going to go the extra mile and make Sense own everything else then they shouldn't have wasted their time on such a crippled UI.

Sense for Windows mobile does landscape. Why not the Android version HTC? Thats one of the reasons I use adw
Sent from my Evo 4g using Tapatalk

nebenezer said:
The sad part is all the images are there (in the framework) for Rosie to go into landscape, they just don't let it. I've seen a mod done that accomplishes this but it looked terrible and would have taken a lot of work to get all the elements to look right. Maybe they gave up and decided to focus on a more important project.. like Sprint Nascar.. or the Sprint Promotion app..
Rosie has such potential but is such a let-down. If they weren't going to go the extra mile and make Sense own everything else then they shouldn't have wasted their time on such a crippled UI.
Click to expand...
Click to collapse
I completely agree. Its like they got to a point that they were happy and just gave up. The fact that landscape wasn't a high prirority is either lazy or dumb or both. This is basic functionality. As soon as I found adw way back when, Rosie has never touched my phone.

Yeah it does seem pretty dumb. Well I wonder if when the G2 comes out with an actual keyboard it'll mean that we finally have a landscape Rosie...

http://i.engadget.com/2010/09/15/htc-desire-z-is-the-qwerty-slider-your-androids-been-waiting-fo/
Sent from my PC36100 using XDA App

bonikowsky said:
Yeah it does seem pretty dumb. Well I wonder if when the G2 comes out with an actual keyboard it'll mean that we finally have a landscape Rosie...
Click to expand...
Click to collapse
Id hope. You'd think that the Evo would have had it since they promoted the hell out of the kickstand. What good is a kickstand if you have to turn the phone vertically to use its most basic functions? Thank God for ADW.

Htc sense like keyboard for CM7 (Q)

I have seached every where to find a keyboard like the sense one that comes stock for evo to run on CM7. I have found the htc_ime kitchen which is pretty close but they dont have the arrow buttons to move the cursor.
Anyone have any idea where i can get a keyboard with arrow buttons to move the cursor for CM7?

The arrows are Sense only, I think. Some of the 3rd party keyboards may have the arrows, though.
However, I use the HTC_IME keyboard in CM7/MIUI with no issues. You can set the volume rocker keys to move the cursor back and forth.

serdna75 said:
The arrows are Sense only, I think. Some of the 3rd party keyboards may have the arrows, though.
However, I use the HTC_IME keyboard in CM7/MIUI with no issues. You can set the volume rocker keys to move the cursor back and forth.
Click to expand...
Click to collapse
I will dig this, because there's no still any IME mod with cursor keys, and I believe it can be done, we just need gingerbread base for this one, not the foryo's, and maybe more, I don't know, but it should be possible. There are much more ppl who will use it.
By the way, "swipe" actions allow to move a word back and forth. It's not the same, but may ease your life.

SwiftKey X has Cursor arrows

Edit: nvermind lost
Sent from my HTC Evo 4G using Tapatalk 2

HipKat said:
SwiftKey X has Cursor arrows
Click to expand...
Click to collapse
I know, but it's worse than IME. That;s why I look for IME with arrows

HipKat said:
SwiftKey X has Cursor arrows
Click to expand...
Click to collapse
I was going to say that but try Swiftkey beta 3.its pretty awesomer and i think u can add the arrows as a add-on

AwesomeEvo said:
I was going to say that but try Swiftkey beta 3.its pretty awesomer and i think u can add the arrows as a add-on
Click to expand...
Click to collapse
Again, Swiftkey X is worse. I see no other Swiftkeys in the market. By the way, Swiftkey is not free. Sense is... I had it on my phone as a factory default, so not discussing the licensing too deeply, it's like it would be free ;>. I just would like HTC DHD IME ported to CM7, or something very, very similar in the layout and features.

krzych said:
Again, Swiftkey X is worse. I see no other Swiftkeys in the market. By the way, Swiftkey is not free. Sense is... I had it on my phone as a factory default, so not discussing the licensing too deeply, it's like it would be free ;>. I just would like HTC DHD IME ported to CM7, or something very, very similar in the layout and features.
Click to expand...
Click to collapse
Just out of curiosity, what don't you like about swiftkey? I've tried out just about every keyboard there is over the last few years and I keep coming back to swiftkey x. The customizations, themes and predictions are top notch imo.

Dannyman23 said:
Just out of curiosity, what don't you like about swiftkey? I've tried out just about every keyboard there is over the last few years and I keep coming back to swiftkey x. The customizations, themes and predictions are top notch imo.
Click to expand...
Click to collapse
Layout is worse. Some functions are not present (don't remember which ones, tested quite a few weeks ago). It's not free, it's a trial only which will stop working at some point leaving a user which used to it with a choice of paying or getting used to another - not worth of the time if you won't like it, if you will, then it's just a luck. It would be much better to make featureless free version than time limited trial (called "free" in the market by the way - not very polite to lie...)

krzych said:
Layout is worse. Some functions are not present (don't remember which ones, tested quite a few weeks ago). It's not free, it's a trial only which will stop working at some point leaving a user which used to it with a choice of paying or getting used to another - not worth of the time if you won't like it, if you will, then it's just a luck. It would be much better to make featureless free version than time limited trial (called "free" in the market by the way - not very polite to lie...)
Click to expand...
Click to collapse
To each their own, I suppose. I find that the location of the comma and period on the main screen (without having to long press or go to a page 2) makes this one of the best layouts out there.
happy hunting!

Dannyman23 said:
To each their own, I suppose. I find that the location of the comma and period on the main screen (without having to long press or go to a page 2) makes this one of the best layouts out there.
happy hunting!
Click to expand...
Click to collapse
Yep, I maybe just used to it too much, but it's too late now ;P. Thanks, but I do not know honestly I will stay with CM, so maybe I will just switch back to Sense... CM is buggy .

krzych said:
Yep, I maybe just used to it too much, but it's too late now ;P. Thanks, but I do not know honestly I will stay with CM, so maybe I will just switch back to Sense... CM is buggy .
Click to expand...
Click to collapse
If you are looking for another option outside of sense, I've been running Decks reloaded for a few weeks now and it is awesome. I've had trouble with CM being buggy in the past, and I get bored on sense roms but this sucker is slick and FAST. I've been flashing roms on this baby for nearly 2 years now and this is by far the fastest and most stable rom I have ever run:
http://forum.xda-developers.com/showthread.php?t=1661605
Of course, this doesn't help your keyboard issue

Dannyman23 said:
If you are looking for another option outside of sense, I've been running Decks reloaded for a few weeks now and it is awesome. I've had trouble with CM being buggy in the past, and I get bored on sense roms but this sucker is slick and FAST. I've been flashing roms on this baby for nearly 2 years now and this is by far the fastest and most stable rom I have ever run:
http://forum.xda-developers.com/showthread.php?t=1661605
Of course, this doesn't help your keyboard issue
Click to expand...
Click to collapse
Heheh, thanks, but it seems it doesn't help at all - I have HTC Desire HD, and there's nothing about Decks working on my phone

Test kernel: Zoom bar acting as multitouch pinch to zoom

Someone asked what the point of the new .39 kernel is, well here's a new feature I've coded up that was made possible due to the more modern kernel.
I have modified the touchscreen driver in the kernel so that the zoom bar is now working, and it sends signals to Android that make it think you're sending a multitouch pinch-to-zoom.
I've got it set so that it sends an input from the center of the screen. As you slide right, the driver tells Android two fingers are moving apart from the center. As you slide left, the driver tells Android two fingers are sliding from the sides towards the center. The net result is that the zoom bar works in any app that supports pinch to zoom.
I've uploaded a video showing it in action:
http://www.youtube.com/watch?v=GRWUzPveU14
I'm going to submit this patch soon, and I'd like it if some people would try it out and give any feedback before I do so. I suppose things to pay attention to would be any increased wonkiness in the touch response, as well as boundaries for the zoom bar. Also, if you have a better idea on how this should work, it's now or never.
Unfortunately, this is a modification of the new .39 kernel, which means that a lot of things are not working on it, and this test kernel will most likely not be suitable for daily use if you like wifi and the other things that don't work on .39 yet.
In order to install you must do the following:
1. Replace your zImage with the one attached.
2. Use the .39 haret (included in the zip for your convenience) with the .39 startup.txt line (set initrd_offset 0x00a00000)
3. Place the included android.hardware.touchscreen.multitouch.xml under /system/etc/permissions. I tried bind-mounting it from conf, but for some reason that did not work for me. If you don't do add this permission file, the multitouch points will still be sent to Android (and will show up in the app Multitouch Test), but Google's own apps like Browser will ignore them.

Amazing.
First time, I can use this since ages.
Unfortunately, my phone has become very sluggish with this test kernel.

Tippfehler said:
Amazing.
First time, I can use this since ages.
Unfortunately, my phone has become very sluggish with this test kernel.
Click to expand...
Click to collapse
I totally agree with that!
Rhod100_nl
Nice work!

I assume pinch-to-zoom is pretty well supported in Android. Does this mean the zoom bar is now more supported (for zooming, button hacks aside) in XDAndroid than it ever was in officially baked HTC WinMo?
Impressive. Thanks for the vid.
I'm planning to give the .39 kernel a quick test run, hopefully this weekend. There's some software that crashes on me on open now and I'd like to see if its any different with .39. I'll try to give this a whirl then.
As for functionality, the p2z is cool, but not something I've been pining for. I don't know exactly what your plans are, but I'd love it if that function could be switched off easily (a line in startup.txt?), so future hacks creating, say, soft buttons on the bar instead could be more easily implemented.

fortunz said:
I'd love it if that function could be switched off easily (a line in startup.txt?), so future hacks creating, say, soft buttons on the bar instead could be more easily implemented.
Click to expand...
Click to collapse
well that bar has been designed to be a zoom bar. you can do whatever you want with it but always a zoom bar remains using it as a "virtual button" is possible but on the phone you will always have the magnifying glasses printed
What you suggest is an hack to the original zoom bar design and it's not as useful as the zoom function (that on our resistive single touch screens is missing)

LinoX said:
What you suggest is an hack to the original zoom bar design and it's not as useful as the zoom function (that on our resistive single touch screens is missing)
Click to expand...
Click to collapse
All I suggest is flexibility. I'm not trying to steal your zoom

fortunz said:
All I suggest is flexibility. I'm not trying to steal your zoom
Click to expand...
Click to collapse
All you are actually suggesting is complexity, indeed. A "soft" array button must be handled properly by the kernel / os / applications and it is a lot more than "one hack" for a function that will be probably not used because the zoom is a bit more important than a button

I'm going to have to break out the bold, aren't I? I'm not asking for soft buttons. I'm asking that this implementation be flexible enough to allow for future hacks like soft buttons, whether they are your favorite or not. I don't even know if the request is necessary, but I never imagined it would be controversial. If that flexibility really is too complex, forgive the request and ignore it.

It's "controversial" because you are asking for a strip of capacitive touch to turn into buttons. As the OP indicated, implementing this requires not only a new kernel+touch, but files in system.ext2, so the system _thinks_ you have p2z when you still have a resistive screen. So what you are asking for is to make that "flexible" when the base feature has barely been coded+tested.
If you truly want capacitive soft buttons, look at the DIAM or RAPH. Back way then (2.0ish), the LED on the bottom button-panel/scroll would light up on finger contact (not pressed) when running xdandroid. It was more of a "wow it's cool" thing because it was a strip of capacitive touch with 5+ LEDs. I don't remember if the p2z worked with the center scrolly or not...
-- Starfox

fortunz said:
I'm going to have to break out the bold, aren't I? I'm not asking for soft buttons. I'm asking that this implementation be flexible enough to allow for future hacks like soft buttons, whether they are your favorite or not. I don't even know if the request is necessary, but I never imagined it would be controversial. If that flexibility really is too complex, forgive the request and ignore it.
Click to expand...
Click to collapse
Alright, settle down children.
I think you're looking a little too far ahead fortunz, but that's just my opinion.
To manekineko - holy crap dude, that was fast! Nice work, definitely want to check it out.
But if you're on CDMA... then I'd imagine the experience is painful with data connected... still, great work. I'm sure the .39 kernel folk will gladly accept your patches, that's seriously cool!

arrrghhh said:
Alright, settle down children.
Click to expand...
Click to collapse
Bu... but... even with the bold starfox still couldn't get it Nevertheless, I am reaching out for my zen.
I think you're looking a little too far ahead fortunz, but that's just my opinion.
Click to expand...
Click to collapse
Fair enough. I was just trying to avoid any potential "now or never" deadline issues.

arrrghhh said:
Alright, settle down children.
I think you're looking a little too far ahead fortunz, but that's just my opinion.
To manekineko - holy crap dude, that was fast! Nice work, definitely want to check it out.
But if you're on CDMA... then I'd imagine the experience is painful with data connected... still, great work. I'm sure the .39 kernel folk will gladly accept your patches, that's seriously cool!
Click to expand...
Click to collapse
Yeah, after I got the .39 kernel, it took me like 30 minutes to get it working for the first time, and then a bit more time to clean up the code to look nicer.
Whereas I'd spent hours banging my head on the wall with .27, never quite sure where the problem was, since I thought I was sending all the right events in the driver. Now I know I was sending the right events (because it works in .39) which means that the problem must have been something in the kernel not passing along the multitouch sync events (I know it's that event missing from debugging the userland). That narrows things down quite a lot, but I don't think I really want to go back and spend the time fixing things up in the obsolete .27 kernel though.

Awesome work Manekineko!
I think the zoom bar code will be a fun addition to future cooks. It will be fun to see what uses people come up with. Be it soft buttons or just a zoom bar. Either way, cool stuff.

There never is and will never be a "now or never" with Android. If you want a feature and it can be coded, take the source and run with it. You may run into walls, and there will be many, but at least you can try - that's the beauty of open source.
-- Starfox

fortunz said:
I assume pinch-to-zoom is pretty well supported in Android. Does this mean the zoom bar is now more supported (for zooming, button hacks aside) in XDAndroid than it ever was in officially baked HTC WinMo?
Click to expand...
Click to collapse
Yes it does
fortunz said:
As for functionality, the p2z is cool, but not something I've been pining for. I don't know exactly what your plans are, but I'd love it if that function could be switched off easily (a line in startup.txt?), so future hacks creating, say, soft buttons on the bar instead could be more easily implemented.
Click to expand...
Click to collapse
Thanks for the suggestion. I'm not going to be implementing it at this time, but the way things are structured in the code, it wouldn't be hard for it to be done by someone interested in the future.
When I was fighting with getting .27 working, I considered at one point simply turning the zoom bar into soft buttons. However, I was never able to come up with a practical use for soft buttons on the zoom bar. The thing that makes it hard is that the list of keyevents Android understand are extremely limited.
You can see for yourself here:
http://developer.android.com/reference/android/view/KeyEvent.html
Set the filter level to API level 8 to see what's available on Froyo. Unfortunately, really useful keyevents like button zoom in/out only became available in Honeycomb (API level 11).
I'm not sure that soft buttons for things like home or power or search would be very convenient when they're not visible on the physical device, are right next to the screen, and could instantly rip you out of what you're doing.
Just in case anyone happens across this that is interested in doing so, here is how you'd probably want to do it:
Android's KeyInputQueue.java, which handles inputs from the touchscreen (and everything else). Do a search for readVirtualKeys and see that it reads from /sys/board_properties/virtualkeys.tssc_manager. Edit the driver so that it generates the virtualkeys file in the format specified in KeyInputQueue, and disable all of the topaz/rhodium zoom bar code.

manekineko said:
the way things are structured in the code, it wouldn't be hard for it to be done by someone interested in the future.
Click to expand...
Click to collapse
Flexible structure is really the only thing I was after. Glad it was already in the plan. And thanks for laying out some possible paths to additional features as well.

Thanks button activated! Great work!
whoops thanked fortunz accidentally -1 buddy

If anybody could find an app that supports touch pressure on a regular kernel on XDAndroid, that would be really helpful. I need to check how much we support pressure to start with and make sure that still is the case with this patch.
I tried Crayon Doodle Lite from the Market, which claims to support pressure, but I'm not seeing any pressure on a regular no-zoom-bar build, so that's not working as a test. Or it may simply be the case that pressure touch has always been broken.

arrrghhh said:
I think you're looking a little too far ahead fortunz, but that's just my opinion.
Click to expand...
Click to collapse
+1
Developing in a way that MAYBE, ONE DAY, SOMEONE, WILL (or just will not) adds unuseful complexity to every software.
BTW: Great work manekineko

Good job, but....
Broke my internet (is zoom tested with gprs or is it CDMA only ?)
Kernel.39+RIL2+F22 is running fine on my R100. After drop in of the Zoom-zImage, connection died.
Without zoom with working connection (SMS error is my operator NOT android):
k39_no_sms_log(537).txt
Zoom added - go to line 552
k39-zoom_no_data(552).txt

wallpaper resize box

Can anyone tell me what the boxes to each side of this home screen resize tool means, since the home screen doesn't rotate what is their purpose? Thanks

Well, the non-rotating thing is more a touchwiz design choice by Samsung. In a nonTouchwiz, such as AOSP, there is rotating. And what you're seeing came in Android 4; it's possible maybe Android 3.1, but I never was on it so I don't know.
Personally, I don't like it. I preferred the old way.
As for the purpose, I haven't clue. When I was AOSP Android 4 based ROMS, the only time I saw the whole home screen was when I was in the mode to pick which page I wanted to jump to. Otherwise, it didn't matter if portrait or landscape mode, I only saw a small bit.

lovekeiiy said:
Well, the non-rotating thing is more a touchwiz design choice by Samsung. In a nonTouchwiz, such as AOSP, there is rotating. And what you're seeing came in Android 4; it's possible maybe Android 3.1, but I never was on it so I don't know.
Personally, I don't like it. I preferred the old way.
As for the purpose, I haven't clue. When I was AOSP Android 4 based ROMS, the only time I saw the whole home screen was when I was in the mode to pick which page I wanted to jump to. Otherwise, it didn't matter if portrait or landscape mode, I only saw a small bit.
Click to expand...
Click to collapse
Oh ok Thanks that sheds a Lil light

Note 2 - a few annoyances (coming from a Nexus)

I only just recently got my Note II and it has got ARHD on it, which I installed because it's a rom based on samsung software with no comptability issues and great battery life.
I also have a Galaxy Nexus and I noticed a few "problems" the Note 2 has and the older Nexus doesn't:
the browser on the Note 2 looks okay but the pointer precision is just very bad. To give an example: if you swipe your finger up or down vertically for a few centimeters, and then you start sliding diagonally (without having lifted off your finger off the screen in the meanwhile), it will only continue to keep scrolling vertically, it won't "follow" your left or right (or diagonal) movement. When you lift off your finger from the screen, retouch it and then scroll diagonal right away it will follow the movement. I find this very annoying, it prevents me of having a smooth browsing experience. My older Nexus with stock android 4.2.2 and stock browser is smooth as butter and follows my swiping movements 1 to 1..
I tested Dolphin browser, Maxthon.. all still bad pointer precision.. Chrome seems to be the least bad of all the browsers, but then on the other hand I find it very choppy.
PS. I already tried an AOSP/CM rom (Sentinel ROM), and there the browser was smooth, yet, non-touchwiz roms are not bugfree and the battery life is nowhere as good as with a samsung based rom.. And especially that last factor is really important to me. (Unless anyone can advise me a bugfree AOSP rom with batterylife that is as good as a samsung based rom).
SOLVED, SOLUTION IN POST #15
Then something else that annoys me quite a bit: when the screen is off and I press the wakebutton, it takes like 1 to 2 seconds until it actually wakes.. I've read I'm not the only one with this problem but I find it kind of unacceptable for a quad core phone with 2GB of ram.. Same problem when you are in an application and you press the homebutton to go to the homescreen, it sometimes takes like a second or more too.. Once again, stuff like that on my simple dual core nexus with half the amount of ram doesn't happen.
UNDERLINED PART SOLVED, SOLUTION IN POST #3 (thanks Kremata)
Then the good stuff has to be said too: homescreen-scrolling is insanely smooth, watching videos is awesome, the camera is great (so is the samsung camera app) and not to forget, the battery life is a revelation to me, I get through the day easily with hardcore use of the phone (that cannot be said of my old Nexus..).
I really like the Note II, but these few problems really crash the party for me.. Also I never thought I'd say it as a Nexus-fan but I generally find Touchwiz pretty cool and suiting on the Note 2.. So I'd prefer to stay on a samsung based rom like ARHD if possible.
Hope there's some experts here who can give me advise on how to handle these little problems.

For the record, I managed installing the AOSP browser, and the bug is still there. So it must be rom/kernel related, not app-related..

The HOME button problem is not a bug. It is because you have set your S-voice to open by double pressing the Home button. So the lag comes from TW waiting for a second press before doing anything.
Just uncheck "Open via the Home Key" in S-voice setting.
For the browser thing I don't know. I never felt it was a problem for me.

Kremata said:
The HOME button problem is not a bug. It is because you have set your S-voice to open by double pressing the Home button. So the lag comes from TW waiting for a second press before doing anything.
Just uncheck "Open via the Home Key" in S-voice setting.
Click to expand...
Click to collapse
One problem solved already, thanks for that!

I placed a video of the pointing precision problem on youtube. Btw I checked if the touchscreen is ok by using "show touches", and it followed my touches 100% perfectly, so it's not the phone, it's definitely some software problem..
This is the video

Could anyone with a samsung-based rom try to reproduce the above problem and see if it happens or not ? If not, could you tell me what rom + kernel you are using, would be much appreciated..
I repeat that when I tried an AOSP rom on my Note II, this issue did not happen.

I'm on DLL4 and before this was on 4.1.1 and do not have this issue.

whisky_ said:
I'm on DLL4 and before this was on 4.1.1 and do not have this issue.
Click to expand...
Click to collapse
Could you give me more information on DLL4 ? Maybe a link to such rom, etc. How is your battery life ?
PS. I have the international (european) version.

wtr_dhd said:
Could you give me more information on DLL4 ? Maybe a link to such rom, etc. How is your battery life ?
PS. I have the international (european) version.
Click to expand...
Click to collapse
I have the exact same thing on my phone (ARHDv18). A work around is to start with a diagonal instead of a vertical line then it works fine

Kremata said:
I have the exact same thing on my phone (ARHDv18). A work around is to start with a diagonal instead of a vertical line then it works fine
Click to expand...
Click to collapse
Thanks, I'll sleep a bit better now tonight
Yes I know.. but it's very annoying.. Since years I used stock android/AOSP, now I went to the dark side P) to use a TW device, so this "problem" kind of annoys me.. I wonder if one of our awesome developers would be able to make a samsung based TW rom with an AOSP-like smooth browsing experience..

wtr_dhd said:
Thanks, I'll sleep a bit better now tonight
Yes I know.. but it's very annoying.. Since years I used stock android/AOSP, now I went to the dark side P) to use a TW device, so this "problem" kind of annoys me.. I wonder if one of our awesome developers would be able to make a samsung based TW rom with an AOSP-like smooth browsing experience..
Click to expand...
Click to collapse
I just realized this problem. I'm using Crash ROM, and sometimes it will happen like in the video, but sometimes it work perfectly.

So weird that I seem to be the first one remarking this problem as imo it's quite annoying, and I'm definitely not alone here.

wtr_dhd said:
So weird that I seem to be the first one remarking this problem as imo it's quite annoying, and I'm definitely not alone here.
Click to expand...
Click to collapse
You must be more picky than most of us as I never noticed this before either.

Kremata said:
You must be more picky than most of us as I never noticed this before either.
Click to expand...
Click to collapse
You don't forget the good stuff of stock android! But the samsung rom has some pretty cool features too..

HOORAY.
With "Chrome Beta" the swiping "bug" is not present! /me happy
Now my Note 2 is "perfect"