Develop Bugs

[Concept][08/01] Android 4.0 Concept User Interface Improvements

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'll be designing various UI concept improvements for Android and I'll keep them uploaded here.
If you have any ideas then please, let me know
8th January - Notification Concept Improvements Part 1
My first concept interface is done and ready for viewing - as well as feedback and comments.
This concept goes over some of my notification concepts which I feel would make Android a little more functional and fluid. Let me know what you think.
This user interface concept improvement video covers 3 simply tweaks, which I feel improve the functionality of Android.
1) Bigger Notifications
These bigger notifications show the contact picture,and are large enough so the message can be read. They appear over the top of the default notification bar to save space.
Clicking on the notification takes you to the application for which the notification is for. In this case, its the Messaging App
2) Quick Reply
Something I feel that has been missing from Android for some time. When the message arrive, clicking on the message itself will open quick reply.
Quick Reply extends the notification area so you can reply to the message right from the notification area, without leaving the application you are currently in.
3) Swipe to Close/Mark
Notifications have already easy to close in Android by either pressing the 'X' or in Android 4.0, by swiping the notification away.
However, there is no way to mark a message or email as read if you close it from the notification area. This concept means that you can do this. Simply wipe the notification to the left to close it, or swipe it to the right to mark it as read and close it.
There were 2 other videos that didn't make it into the final video - the only reason for this is that they are longer and the size of the video came to about 600mb for a HD one. Hence why they were left out of this video.
You can find more information about these at this post: http://forum.xda-developers.com/showpost.php?p=21179299&postcount=62
Click to expand...
Click to collapse
All feedback and comments are welcome. Feel free to message me on any of the sites above.
These are just concepts, unfortunately I dont have the coding skills required to make this a reality. However if I can get ideas and make concepts up, a dev from the forums, the cyanogen mode team or perhaps Google themselves if we're lucky will see this and help make them become a reality.
If you would like to incorporate these ideas into a ROM, application etc, then please contact me first
Find me on the following websites:
Twitter
Google+
Facebook

Honestly there isn't much I'd change right now. I haven't noticed much that I would change.
In terms of performance, they NEED to fix the autorotate function. Yes, it's nice now that it shows an animation, but it takes waaaay too long to rotate. This was the same gripe I had with Honeycomb tablets. I'm positive that it's intentional by Google, because other phone running ICS with skins rotate faster (I have a Sensation to compare).
This second one is gonna get a bit long.
Second, they need to change the response time of the recent apps button. After extended use and several apps running, there will be a slight delay between pressing the button and the list opening up. I'm actually fine with the fact that there's a delay, it's just where the delay is. The way it runs is you touch the button, there's a delay(lag, whatever you want to call it), then the phone vibrates, the button lights up, and the list comes up. What google needs to do is change the way it functions. Make sure the haptic feedback functions and the button lights up the instant your finger touches it. Then it can delay and the list can come up. In other words G needs to make the illumination and haptic feedback first priority. Then it could work on the multitasking process.
I think if it was done in this manner, the lag would be much less noticeable. It's the same as showing some sort of screen or animation when starting an app. If you touch an app and nothing happens (the screen doesn't change at all, not even a press animation) until the apps fully loaded and running it'll be seen as lag. If you touch an app and immediately see a loading screen or an animation (just examples) then you know the app started up already, and it's perceived as loading instead of lag.
Phew. That was a mouthful. It needed to be said. Come on now Google. All of both of these are just a little tweak in software. Entirely doable. Or maybe it's already done. I don't know for sure since I'm still running 4.0.1
Other than that ICS is great.
EDIT: oh and Google should change the notification to mirror that of tablets. I don't see why they removed the quick settings; it seems unlike them. Just the basics like in Honeycomb: wifi toggle, brightness, bluetooth and autorotate. I've seen mods include it, so I'm sure they could come up with an elegant solution

They need to add the ability to get rid of the Google Search bar on all homescreens or make it less intrusive on the homescreen.

Evostance said:
All,
Just doing a bit of research.
Even though we all love Android, its still got its gripes. One of those for me is that the interface isn't as fluid or as function as it could be.
As many of you have seen ICS now, what type of enhancements to the interface would you like to see?
To give you an idea of what i'm after: I personally still dont like the notifications. I feel that they are a bit limited as to whats on offer, so I would like to see more function added to them
Click to expand...
Click to collapse
Fixing notifications is easy. Just drag and drop custom sounds into notifications, alarm and ringtones folder. Using same nokia notification for text ever since my first smartphone. I have the usual buzzer alarm since ics didnt include it. I would also like option of no search bar or at least pinning it to desired homescreen. It would be nice if google included more in house options for themes, colors and backgrounds. Sms, gmail, calendar and email are ridiculously white. I'd like more black background white text options. We also need a toggle for the gpu clocks or coolbho3000 to hook us up in setcpu. Options for amount of home screens. 32GB and/or micro sd. Better clock options. Damn pogo pins car dock already.
My grandma beat me down and took my nexus. Sent from a jitterbug with beats by dre.

tsunami1609 said:
Honestly there isn't much I'd change right now. I haven't noticed much that I would change.
In terms of performance, they NEED to fix the autorotate function. Yes, it's nice now that it shows an animation, but it takes waaaay too long to rotate. This was the same gripe I had with Honeycomb tablets. I'm positive that it's intentional by Google, because other phone running ICS with skins rotate faster (I have a Sensation to compare).
This second one is gonna get a bit long.
Second, they need to change the response time of the recent apps button. After extended use and several apps running, there will be a slight delay between pressing the button and the list opening up. I'm actually fine with the fact that there's a delay, it's just where the delay is. The way it runs is you touch the button, there's a delay(lag, whatever you want to call it), then the phone vibrates, the button lights up, and the list comes up. What google needs to do is change the way it functions. Make sure the haptic feedback functions and the button lights up the instant your finger touches it. Then it can delay and the list can come up. In other words G needs to make the illumination and haptic feedback first priority. Then it could work on the multitasking process.
I think if it was done in this manner, the lag would be much less noticeable. It's the same as showing some sort of screen or animation when starting an app. If you touch an app and nothing happens (the screen doesn't change at all, not even a press animation) until the apps fully loaded and running it'll be seen as lag. If you touch an app and immediately see a loading screen or an animation (just examples) then you know the app started up already, and it's perceived as loading instead of lag.
Phew. That was a mouthful. It needed to be said. Come on now Google. All of both of these are just a little tweak in software. Entirely doable. Or maybe it's already done. I don't know for sure since I'm still running 4.0.1
Other than that ICS is great.
EDIT: oh and Google should change the notification to mirror that of tablets. I don't see why they removed the quick settings; it seems unlike them. Just the basics like in Honeycomb: wifi toggle, brightness, bluetooth and autorotate. I've seen mods include it, so I'm sure they could come up with an elegant solution
Click to expand...
Click to collapse
Stole the words out of my mouth. It sounds like nit-pickey stuff but it really would bring it all together nicely.

tsunami1609 said:
Honestly there isn't much I'd change right now. I haven't noticed much that I would change.
In terms of performance, they NEED to fix the autorotate function. Yes, it's nice now that it shows an animation, but it takes waaaay too long to rotate. This was the same gripe I had with Honeycomb tablets. I'm positive that it's intentional by Google, because other phone running ICS with skins rotate faster (I have a Sensation to compare).
This second one is gonna get a bit long.
Second, they need to change the response time of the recent apps button. After extended use and several apps running, there will be a slight delay between pressing the button and the list opening up. I'm actually fine with the fact that there's a delay, it's just where the delay is. The way it runs is you touch the button, there's a delay(lag, whatever you want to call it), then the phone vibrates, the button lights up, and the list comes up. What google needs to do is change the way it functions. Make sure the haptic feedback functions and the button lights up the instant your finger touches it. Then it can delay and the list can come up. In other words G needs to make the illumination and haptic feedback first priority. Then it could work on the multitasking process.
I think if it was done in this manner, the lag would be much less noticeable. It's the same as showing some sort of screen or animation when starting an app. If you touch an app and nothing happens (the screen doesn't change at all, not even a press animation) until the apps fully loaded and running it'll be seen as lag. If you touch an app and immediately see a loading screen or an animation (just examples) then you know the app started up already, and it's perceived as loading instead of lag.
Phew. That was a mouthful. It needed to be said. Come on now Google. All of both of these are just a little tweak in software. Entirely doable. Or maybe it's already done. I don't know for sure since I'm still running 4.0.1
Other than that ICS is great.
EDIT: oh and Google should change the notification to mirror that of tablets. I don't see why they removed the quick settings; it seems unlike them. Just the basics like in Honeycomb: wifi toggle, brightness, bluetooth and autorotate. I've seen mods include it, so I'm sure they could come up with an elegant solution
Click to expand...
Click to collapse
Your second point is fixed in 4.0.3
I agree with the OP I hope google does something new with the notifications.
Even just adding them to the lockscreen like iOS would be awesome
I also dislike how the notifications have a character limit, it would be cool if you had the dropdown open long enough the text would scroll

- I'd love to have swiping away a text or email mark it as read. And while we're on notifications I don't get why contact pics don't display in the drop-down bar for texts, only for emails.
- Swiping away a recent app actually kills it
- Option to easily switch between the phone & people apps
- Option to mute shutter sound right in camera menu
- Notification bar toggles like in CyanogenMod or AOKP

daandman said:
- I'd love to have swiping away a text or email mark it as read. And while we're on notifications I don't get why contact pics don't display in the drop-down bar for texts, only for emails.
- Swiping away a recent app actually kills it
- Option to easily switch between the phone & people apps
- Option to mute shutter sound right in camera menu
- Notification bar toggles like in CyanogenMod or AOKP
Click to expand...
Click to collapse
Swiping away apps actually does kill them, you can see the process dying in the logs when removing from recent app list

I would like a new SMS app theme. The current one is pretty ugly. Something like Windows Phone 7's messaging theme would be much nicer.

BlackDino said:
Your second point is fixed in 4.0.3
I agree with the OP I hope google does something new with the notifications.
Even just adding them to the lockscreen like iOS would be awesome
I also dislike how the notifications have a character limit, it would be cool if you had the dropdown open long enough the text would scroll
Click to expand...
Click to collapse
The reason I ask is im just doing a concept design for ICS. Not a custom launcher but actual improvements to stock.
For notifications i actually meant the looks and functionality of it. The first concept ive done is to change how the text notifications work.
I don't like the character limit or how restrictive it is, so I've changed it.
Hopefully when I've got my concepts together, someone will be able to help make them a reality, be it a dev, the cyanogen team or google themselves lol.
Sent from my Galaxy Nexus using Tapatalk

I would really like a change to the lockscreen while listening to music. I want the bottom half of the screen to be transparent, or to show the wallpaper instead of beeing black. I have been searching through SystemUI, framework-res and android.policy.jar to try and find it, but haven't as of yet.

tristan202 said:
I would really like a change to the lockscreen while listening to music. I want the bottom half of the screen to be transparent, or to show the wallpaper instead of beeing black. I have been searching through SystemUI, framework-res and android.policy.jar to try and find it, but haven't as of yet.
Click to expand...
Click to collapse
Do you mean where the soft buttons would sit?
You'd like to see music controls in there?
Sent from my Galaxy Nexus using Tapatalk

Soft button area supporting gestures
I came to Android from webOS after HP shot themselves in the foot several times and one of the things I miss most is the gesture bar you had at the bottom of the screen. With the advent of the soft button area in ICS I see a real option to enable the area to work in a similar fashion.
For those that are unfamiliar with it it's basically an area at the bottom of the screen blocked off from apps that registers simple finger gestures. This made the basics of actually using a device a breeze and pleasure i.e. no looking for a particular button / tapping the wrong button when you weren't looking and the gestures were consistent no matter what app was running.
The gestures were:
A single swipe up would show you your running apps.
Swiping 2 fingers up would show you the launcher (app drawer).
A leftward swipe would go back.
A full swipe across the entire area going either right or left would take you to the next or previous running app.
Besides the wireless charging the gesture area was one of the webOS killer features you very quickly learned to take for-granted. So yeah, I'd like the soft button area to handle gestures in case you haven't guessed already

Northernmost said:
I came to Android from webOS after HP shot themselves in the foot several times and one of the things I miss most is the gesture bar you had at the bottom of the screen. With the advent of the soft button area in ICS I see a real option to enable the area to work in a similar fashion.
For those that are unfamiliar with it it's basically an area at the bottom of the screen blocked off from apps that registers simple finger gestures. This made the basics of actually using a device a breeze and pleasure i.e. no looking for a particular button / tapping the wrong button when you weren't looking and the gestures were consistent no matter what app was running.
The gestures were:
A single swipe up would show you your running apps.
Swiping 2 fingers up would show you the launcher (app drawer).
A leftward swipe would go back.
A full swipe across the entire area going either right or left would take you to the next or previous running app.
Besides the wireless charging the gesture area was one of the webOS killer features you very quickly learned to take for-granted. So yeah, I'd like the soft button area to handle gestures in case you haven't guessed already
Click to expand...
Click to collapse
Ok ill see what I can mock up. I've done a basic notification text, just need to add another feature before i finalise it
Sent from my Galaxy Nexus using Tapatalk

Go you! I was hoping this was something Matias Duarte would bring to Android himself.

Evostance said:
Do you mean where the soft buttons would sit?
You'd like to see music controls in there?
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
No, it's the black part of this screenshot I'd like changed.
Sent from my Galaxy Nexus using xda premium

tristan202 said:
No, it's the black part of this screenshot I'd like changed.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Oh wow. Thats actually what it looks like when playing music
I think that black part may be for album art?

Evostance said:
Oh wow. Thats actually what it looks like when playing music
I think that black part may be for album art?
Click to expand...
Click to collapse
No, it just shows the album art at the very top. Up where the media buttons are.

tristan202 said:
No, it just shows the album art at the very top. Up where the media buttons are.
Click to expand...
Click to collapse
How stupid. Definitely a tweak that should be there

Honestly, the only two things I want to be changed in terms of the UI are
1.) The ability to hide the soft keys at will for example, if I'm playing a game I want to be able to utilize the entire screen. I think a gesture to hide + bring back the soft keys is the solution. Highly unlikely to be implemented anytime soon
2.) Such as many launchers which have the functionality to have scrollable docks, I would like the soft keys to be scrollable. It would be pretty awesome to be able to have different toggles such as wifi, Bluetooth and even apps always available since unlike the notification bar, the soft keys never disappear regardless of the current app.
Sent from my Galaxy Nexus using xda premium

"Expanded Desktop" hidden shortcut?

There is an option in paranoiddroid rom in the power menu called Expanded desktop, for those who don't know its a really cool feature that hides the status bar and nav bar giving a very beatiful full screen. Is there any way I could make it into a shortcut or a hidden toggle(ie, like how the LMT pie can be accessed by touching the very right of the screen) where i could hide/unhide without having to open the power menu every time?

mmk92 said:
There is an option in paranoiddroid rom in the power menu called Expanded desktop, for those who don't know its a really cool feature that hides the status bar and nav bar giving a very beatiful full screen. Is there any way I could make it into a shortcut or a hidden toggle(ie, like how the LMT pie can be accessed by touching the very right of the screen) where i could hide/unhide without having to open the power menu every time?
Click to expand...
Click to collapse
To my knowledge, there is no shortcut to it. If u already know about lmt, why not just use that as your primary nav keys?
Sent from a Galaxy far far away

rice923 said:
To my knowledge, there is no shortcut to it. If u already know about lmt, why not just use that as your primary nav keys?
Sent from a Galaxy far far away
Click to expand...
Click to collapse
LMT slows touch response down, using it is VERY annoying, and an expanded desktop toggle would be much faster and provides overall much better work flow then LMT

mmk92 said:
LMT slows touch response down, using it is VERY annoying, and an expanded desktop toggle would be much faster and provides overall much better work flow then LMT
Click to expand...
Click to collapse
What??? Works fine for me. I've been using since march.
And u can probably attach a shortcut to LMT.
--------------------------------------------------
If I have helped you.... hit that sexy thanks button. ^_^

Dragn4rce said:
What??? Works fine for me. I've been using since march.
And u can probably attach a shortcut to LMT.
--------------------------------------------------
If I have helped you.... hit that sexy thanks button. ^_^
Click to expand...
Click to collapse
Same here, works like a charm. I even created the shortcut to Google Now by long pressing the home key like the normal nav keys

I'm late to this party, what is lmt?
Sent from my SCH-I535 using xda premium

Slacker101 said:
I'm late to this party, what is lmt?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
It's a type of onscreen navigation buttons.
Attached you can see what it looks like. Basically the left or right side of my screen contains hot zones that activate the 'pie' but you can also use gestures.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Galaxy Nexus using Tapatalk 2

LMT is cool and all but for someone who started using it on jellybean after a week on running bone stock gnex, it affects the touch response noticebelly and overall performance abit, its kind of like when you install too much mods off cydia on the iphone
Now if theres a way to implement an invisible trigger, lets say on the bottom right corner of the screen, you can use the nav bar as google intended it with full convinience, but when your playing a game browsing or whatever, you just toggle it off, and then back on when your done, although the LMT pie is an awesome concept, but lets be honest its not as convinient as the conventional navbar

mmk92 said:
LMT is cool and all but for someone who started using it on jellybean after a week on running bone stock gnex, it affects the touch response noticebelly and overall performance abit, its kind of like when you install too much mods off cydia on the iphone
Now if theres a way to implement an invisible trigger, lets say on the bottom right corner of the screen, you can use the nav bar as google intended it with full convinience, but when your playing a game browsing or whatever, you just toggle it off, and then back on when your done, although the LMT pie is an awesome concept, but lets be honest its not as convinient as the conventional navbar
Click to expand...
Click to collapse
Hm, lmt should not influence the performance of the device and I never saw it happening on my jb. Perhaps you did not configure it correctly? Did you use only the pie or also the gestures? Did you deactivate the gestures when not using it? Did you use the correct input device? Thanks!
Edit: And do you have a use case I could reproduce? I'd love to iron out the problem if it's really happening?
Sent from my Galaxy Nexus

noname81 said:
Hm, lmt should not influence the performance of the device and I never saw it happening on my jb. Perhaps you did not configure it correctly? Did you use only the pie or also the gestures? Did you deactivate the gestures when not using it? Did you use the correct input device? Thanks!
Edit: And do you have a use case I could reproduce? I'd love to iron out the problem if it's really happening?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
No ironing is possible, really.
The performance increased noticeably in either a recent version of LMT or just on JellyBean...
Back on ICS I couldn't stand the millisecond of lag it induced.
However; I use in on JellyBean without issues. It is slightly laggier than the stock keys but it's hardly noticeable since it's gesture based.
I.E.
Pie: you remove your finger to register a gesture.
NavBar: you tap your finger to register a gesture.
When you think about this as you're doing it...you can better visualize ho long the actions take to register and PIE is a tad bit slower...but not by much.
Again, I still use it and don't mind it in the slightest.

noname81 said:
Hm, lmt should not influence the performance of the device and I never saw it happening on my jb. Perhaps you did not configure it correctly? Did you use only the pie or also the gestures? Did you deactivate the gestures when not using it? Did you use the correct input device? Thanks!
Edit: And do you have a use case I could reproduce? I'd love to iron out the problem if it's really happening?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I configured it to run PIE only at first and i noticed a slight overall lag in touch response throughout the entre system, this lag isnt much but noticable(atleast for me), when i enabled gestures with it it induced an even bigger lag but still very small yet it is still there.
I respect the LMT concept for shortcuts and the PIE feature for extended navigation buttons, but I still think that a work around to disable/enable the native navbar on the fly is much more convenient, efficient, and wouldn't have any effect on the workflow of the entire device(maybe even improve it a bit)
But for people who need more functionality then the nav bar and don't mind the minor annoyances it provides, i strongly recommend LMT.
Jubakuba said:
No ironing is possible, really.
The performance increased noticeably in either a recent version of LMT or just on JellyBean...
Back on ICS I couldn't stand the millisecond of lag it induced.
However; I use in on JellyBean without issues. It is slightly laggier than the stock keys but it's hardly noticeable since it's gesture based.
I.E.
Pie: you remove your finger to register a gesture.
NavBar: you tap your finger to register a gesture.
When you think about this as you're doing it...you can better visualize ho long the actions take to register and PIE is a tad bit slower...but not by much.
Again, I still use it and don't mind it in the slightest.
Click to expand...
Click to collapse
Ya exactly that's what I'm talking about, that slight lag u notice i notice it even more I'm very anal about how fast my phone responds to touch thats why i got a gnex in the first place
and ya also executing a command through a gesture or the PIE feature takes around 3times longer to execute then taping an icon on the nav bar
EDIT: Also displaying the PIE by taping and holding the hidden toggle on the mid-right of the screen adds a second to the work flow, which is a lot compared to a navbar tap

I'm sorry for the double post, but this is more of a discussion thread then a Q/A thread, can it be moved back to general? as it does not belong here

You're talking about two types of lag atm. First you say when lmt is activated there is an overall system lag for touch events. This I want to analyze and fix if it is happening! I designed lmt so that there should be no influence and as I said I never saw this and no one ever mentioned it in the lmt thread.
Then you're talking about triggering actions like "back" takes longer time than the softkeys. You're right about that. For some action like "back" external apps like lmt have to trigger a hardware keyevent on a low level because android doesn't expose an api for that. This is for example one reason why lmt needs root permissions...
Sent from my Galaxy Nexus

noname81 said:
You're talking about two types of lag atm. First you say when lmt is activated there is an overall system lag for touch events. This I want to analyze and fix if it is happening! I designed lmt so that there should be no influence and as I said I never saw this and no one ever mentioned it in the lmt thread.
Then you're talking about triggering actions like "back" takes longer time than the softkeys. You're right about that. For some action like "back" external apps like lmt have to trigger a hardware keyevent on a low level because android doesn't expose an api for that. This is for example one reason why lmt needs root permissions...
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I can't really discribe the lag pricesely, but its there. It is very comparable to the lags iOS users get from theming/applying UI mods. And ya that lag when you do an action like "back" is noticable and its very obvoius for everyone. As far as LMT though i think its as good as it could get, the android OS the bottleneck at this point i guess....
Now i hope there's a way to use a trigger like the one that triggers the PIE function to turn the navbar on/off, jus tlike on the power menu. Maybe the functionality could be added to LMT? or maybe we could use the already available LMT features like hand gestures to map it to that function?

mmk92 said:
I can't really discribe the lag pricesely, but its there. It is very comparable to the lags iOS users get from theming/applying UI mods. And ya that lag when you do an action like "back" is noticable and its very obvoius for everyone. As far as LMT though i think its as good as it could get, the android OS the bottleneck at this point i guess....
Now i hope there's a way to use a trigger like the one that triggers the PIE function to turn the navbar on/off, jus tlike on the power menu. Maybe the functionality could be added to LMT? or maybe we could use the already available LMT features like hand gestures to map it to that function?
Click to expand...
Click to collapse
This could be done. Hiding the navbar on the fly was introduced/implemented in custom roms only. I don't know who initially implemented the code and who just kanged it . You need to ask the guys if that hiding is somehow exposed so that external apps can trigger it (ask for an api). If not, you could kindly ask if they would implement it. Once this is done it would be easy for me to implement an invisible activation area, etc. to trigger it. Hth...
Sent from my Galaxy Nexus

noname81 said:
This could be done. Hiding the navbar on the fly was introduced/implemented in custom roms only. I don't know who initially implemented the code and who just kanged it . You need to ask the guys if that hiding is somehow exposed so that external apps can trigger it (ask for an api). If not, you could kindly ask if they would implement it. Once this is done it would be easy for me to implement an invisible activation area, etc. to trigger it. Hth...
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I found a way, the latest Xenon ROM includes within the system UI a command(or activity) that hides/shows the navbar, I used LMT double finger gestures to swipe up to hide it, then swide up again to show it

Could you share the name please?
Sent from my Galaxy Nexus using xda app-developers app

how can the status bar show on expanded desktop?

shaider_516 said:
how can the status bar show on expanded desktop?
Click to expand...
Click to collapse
use the smart statusbar app, its on play store

No navbar gestures only N4 LMT config - copy it or help improve it if you want to

So, the nav-bar eating a portion of my screen was bothering me for a while and I wanted my device to rely on gestures only, so I decided to search for the most suitable way for me to solve this problem... LMT of course, but first I got rid of the nav-bar using FullScreen Toggle.
Big thanks to the creators of both those apps
LMT can be found here: http://forum.xda-developers.com/showthread.php?t=1330150
FullScreen Toggle can be found here: http://forum.xda-developers.com/showthread.php?t=1497558
Now, as the title says, I'd like to share with you my LMT configuration. There are many things that I'm currently unable to understand about how LMT should actually be configurated, I just used a trial&error approach, but the result I got is more then decent and worthy of being shared IMO. If I'll get some suggestion on how to improve what I did I hope to turn this post in a clean LMT ISAS guide for the Nexus 4.
PLEASE NOTICE that I didn't want to use the pie and I (almost*) didn't use LMT's gestures. The following configuration is for ISAS only.
That's because I wanted to get rid of softkeys and still have an easy to use and reliable N4. Complicated gestures tend to be hard to use and to reproduce consistently, they will give you an hard learning curve and will slow down every operation. Here I'm trying to get the benefits of gestures without making everything overcomplicated.
Now... let's get into it, I'm gonna use pictures to make everything easier to understand
This is what I ideally wanted to get:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Each colored part corresponds to a ISA on LMT
YELLOW is ISA 1 (bottom left), assigned to BACK
RED is ISA 2 (bottom center), assigned to HOME
BLUE is ISA 3 (bottom right), assigned to RECENT APPS
GREEN is ISA 9 (left bottom), assigned to OPTIONS
ORANGE is ISA 6 (top right)
this is an optional one that I wanted to add. It's assigned to search longpress, wich triggers an activity of the app "Screen Off and Lock". Basically it locks the screen with a swipe.
Sadly, if you assign the ISAS as shown without changing any value within LMT your ISAS will look nothing like the picture, you'd get something like this:
Why? I promise I don't know. I read the posts about how to use LMT, but I couldn't really understand how the 4 settings for ISAS work. So as I said, I went for trial&error. At first I thought that "Activation area thickness" was the setting I had to modify to get what I wanted, but it didn't help in any way, and the same happened with "Min bbox size", so I left those two as they were by default.
Then I found out that increasing the value for "Touchscreen to screen factor Y" reduces the colored rectangles areas. I found the value 209 to be ideal. The rectangles were now more like lines closed to the frame, but many things were still off. Here's how it looked like:
The home button is far too small, everithing is too much to the left and I don't really know what the heck orange is doing down there.
Finally, I changed the "Touchscreen to screen factor X" value to 250, and it got me to my final result
It's not perfect, but it's pretty close. I would like yellow red and blue to be better centered, but this configuration is really reliable and easy to use. It actually took me some time to realize that it's not exactly as I wanted it, the only thing that you have to remember if you you're gonna use this, is to stay well to the right when you want to swipe into recent apps.
If you apply this settings you will be able to use easy gestures that can't be activated by mistake while you are using other apps or games and you'll gain precious space on your screen.
My final LMT values are:
Min bbox size: 1 (default)
Activation area thickness: 80 (default)
Touchscreen to screen factor X: 250
Touchscreen to screen factor Y: 209
*I also enabled the X shaped gesture on LMT and associated it with FullScreen Toggle. If anything goes wrong while you are using your phone and you can't open the app drawer to get to FullScreen Toggle and enable the navbar, just perform the gesture, toggle the navbar back and reboot your phone.
Known issues with this configuration.
There are two of them.
First, since you have an ISA for options, you will be able to use the options in any app that has an option menu. The problem is that for some reason when FullScreen Toggle is activated you will not be able to see the 3-dots on-screen icon that opens the menu on any apps. That icon disappears from the top right corner or wherever it's supposed to be. That means that you will have to remember which apps have an option menu or just try to swipe and open it in case there is one.
Second, with LMT ISAS change positon properly when you go from portrait to panorama mode only if you rotate your device 90° to the left. If you rotate your device to the right ISAS from the bottom go to the top and ISAS on the right side go to the left side and viceversa.
However this is not a big problem to me and maybe it will be fixed by LMT's developer anyway.
Sorry for the long post and for any grammatical error (probably a lot). Hope someone finds this intresting and helpful

Cool guide thanks.
Did you try GMD gesture control? Seems like it would be easier to setup how you like. Complex or simple. I guess if you got LMT working fine then its all good.

jarayn said:
Cool guide thanks.
Did you try GMD gesture control? Seems like it would be easier to setup how you like. Complex or simple. I guess if you got LMT working fine then its all good.
Click to expand...
Click to collapse
I tried it but I was not satisfied with it. It's really great and extremely customizable, but in my expirience it's a bit buggy, it gave me problems right after the boot, can't remember if the auto-start was too slow or if there was actually something worse then that.
Also, it doesn't allow you to hide the navbar only, if you want to hide the navbar you have to hide the status bar too.

Marlon90 said:
I tried it but I was not satisfied with it. It's really great and extremely customizable, but in my expirience it's a bit buggy, it gave me problems right after the boot, can't remember if the auto-start was too slow or if there was actually something worse then that.
Also, it doesn't allow you to hide the navbar only, if you want to hide the navbar you have to hide the status bar too.
Click to expand...
Click to collapse
Ah ok. I dont use the hiding functions at all just use the Rom for that. The gestures aren't buggy at all and are a lot easier to set up than lmt. Also you get the launch pads.
Anyway it doesn't matter. It's a good guide and lmt is free so that's something.

Awesome post, thanks!
2 Questions...
Is there any way I can swipe back with the keyboard up without typing anything? I end up with a million drafts using LMT.
Also, is there a setting to actually see the areas like you show them for the touch locations?

ace7196 said:
Awesome post, thanks!
2 Questions...
Is there any way I can swipe back with the keyboard up without typing anything? I end up with a million drafts using LMT.
Also, is there a setting to actually see the areas like you show them for the touch locations?
Click to expand...
Click to collapse
First answer... this kind of things are the ones that bother me too with gestures, and doing what I showed in the OP I specifically tried to eliminate or reduce them. My answer to that problem was having a little line instead of a rectangle, and not so tiny that it's hard to trigger the gesture. It works well for me, and I think it requires very little getting use to.
Try it yourself if you want and maybe accomodate it to yur preference. Maybe you will type something from time to time but I hope the guide makes it so that it happens rarely.
Also, I never tried this on another N4... I don't see why it shouldn't work the same way for others, but a little feedback would be a very good thing.
As for the second question, there's no such setting that I know of, you should ask to the develoer of LMT. If there was such an option it would be so much easier to configure the app perfectly.

Fyi: touchscreen to screen factors for the nexus 4 are 200/200. It's written in the OP.
Hth!
Sent from my Nexus 4

noname81 said:
Fyi: touchscreen to screen factors for the nexus 4 are 200/200. It's written in the OP.
Hth!
Sent from my Nexus 4
Click to expand...
Click to collapse
I know that, but does it work for you? On my device it does not, if I don't mess around with X and Y I always get rectangles

Marlon90 said:
I know that, but does it work for you? On my device it does not, if I don't mess around with X and Y I always get rectangles
Click to expand...
Click to collapse
200 by 200 work best for me. OP: Are you able to simple press those hidden areas, or do you have to do a small swipe? I have to do the latter.

Yes these are the correct values to divide each side of the screen into 3 areas with equal size.
Sent from my Nexus 4

noname81 said:
Yes these are the correct values to divide each side of the screen into 3 areas with equal size.
Sent from my Nexus 4
Click to expand...
Click to collapse
Well, then I guess I'm left with a big pile of nothing... What happens to me is I have big areas in wich a swipe triggers the action. At 200 they take a big part of the sceen and if I increase Y even slightly they become lines, but some other things are off as I said. I've read around about people not being able to get ISAS to work and I thoght I was into something, but if that's just me then I'm at a loss... I guess I'll do a nanobkp and wipe and see if everything start working with 200/200

Great!, thanks for the guide.

tyraelasd said:
Great!, thanks for the guide.
Click to expand...
Click to collapse
yeah, you are welcome... read the rest of the thread, chances are this guide is useless for most people

jarayn said:
Cool guide thanks.
Did you try GMD gesture control? Seems like it would be easier to setup how you like. Complex or simple. I guess if you got LMT working fine then its all good.
Click to expand...
Click to collapse
I use both LMT and GMD for different gestures and I'm pretty satisfied, I also use glovebox for frequently used apps.
My setup is a little different, when I'm from the pc (and hopefully I'll remember XD) I'll share also my setup with you
Sent from my Nexus 4 using xda app-developers app

I personally use the Extend Desktop feature easily accessible from the power button on CM. Probably the way to go if you already have a custom ROM.

my gestures setup
I use, as I said, both LMT and GMD for my gestures setup. I tried a bit to emulate ubuntu for phones. (I also use glovebox as you see)
(In the image, the rectangles are actually the area you have to swipe to activate the gesture)
GMD custom gestures:
with a swipe from the left center you go home
with a wipe from the right center you go to the previous app
LMT ISAS:
swipe form the bottom center to go home
swipe from the bottom left to go back
swipe from the bottom right to recent apps
swipe from the top right to go back (useful when you have the keyboard open and you don't want to accidentally type)
the settings for the apps are the following
LMT
min bbox (how much do you have to swipe to activate the gesture: 5
activation area thickness: 25
touchscreen factor x,y: 200
GMD
gesture size (under "advanced"): 492
home and prevapp gesture may have to be disabled when keyboard is on depending on your keyboard
I'm pretty satisfied with this setup, only little thing that bothers me is that sometimes when I type a bottom gesture is activated, but it happens very few times

Im testing this Now, thanks

I like it. I had to use 100 instead of 80 but works mint.

issues with typing is messing with this. Also its hard to swipe up to go back on some apps. It keeps opening the keyboard.

I just wanna thank the OP and everyone on this thread. I read all the responses and was able to get it working perfectly for me. I like this setup way more than using PIE.

[4.2.2][jdq39][aosp] SHPONGLE [halo][beta][20130630]

Hello mate,
Before rushing to download this rom (I know everyone does it, I'm not an exception either), take some time to read what I'm about to write down here.
Let me introduce you to my ROM, called simply: SHPONGLE.
Its a ROM like every other one, nothing too special about it, everyone knows the features, you have seen it in every rom that its out there for other phones. So if you expect this one to be something really special, something that will blow your mind away, stop, take a long, deep breathe and close this page. This is not a ROM that makes you pancakes, nor it will transform your device in something way more cooler than a Nexus, for example.
I've spent days and nights working on this new release and I know you were waiting anxiously for me to say "Build's up", I'm sorry I kept you, mate, waiting for such a long time but you know me (do you?). If even one single bug was introduced, the build was canceled. That's why it took so long. There are numerous things changed and added that, I hope I kept track of everything. There were numerous errors/crashes/incompatibilities to squash and I'm very proud of myself right now.
So, what is SHPONGLE and why did you changed the name?
When I first worked on Evervolv and fixed almost everything in one go, I thought that I've found a gold mine. To bring an AOSP rom to life, on a legacy device, its pretty much committing suicide. Not only there are 99% chances that the build will not get past Htc's logo screen, but there is 100% chance of not having things working in it ever (take for example camera, which is pretty much hacked because HTC does its job of not releasing camera drivers).
Evervolv's base helped us so much, I want to thank them for doing a great job on keeping legacy devices alive, but, it is time to let go.
Then I started to feel "home sick" of my last ROM for Hero (its a phone) and I thought: "Why shouldn't I work myself in turning this Evervolv ROM in something totally different, in the memory of my last ROM?". So that's how, there is no Evervolv anymore, nor it will be in the near future. This right here is SHPONGLE. Welcome, to One V, Shpongle!
At its core, this ROM still remains an Evervolv, but I have faith that the birth of his child, SHPONGLE, will rock on your device even if I will be gone.
Yeah, but what SHPONGLE means, anyway?
If any of you wants to know what it really is, I suggest you go and search on Youtube. If you are a little bit like myself, you'll love it!
I feel the need to repeat myself now, mate: This ROM has nothing special in it. It's just the result of my love, passion and a bit of myself inside. You'll feel the smoothness but you will also feel some strutting. Don't blame the ROM (well, you can blame it) but blame the HW. With 512 mb of ram, you can't expect too much of it frankly.
On with the ROM we go!
Features:
Sweep2Wake, DoubleTab2Wake - Credits to our austrian guy, Maxwen
Status bar tweaks
Rotation tweaks
Lock screen custom shortcuts, custom wallpaper, maximize widgets;
LockClock app (weather, clock, calendar)
Hardware keys remapping
Power menu toggles
Expanded desktop
Clear all recents
Performance CM menu
Fast Charge
Quiet hours
Power sounds
Media scanner behavior changer
What's not working:
Code:
Native camera - I don't care right now
use a 3rd party camera
Quiet hours
A big THANK YOU for everyone who supported my work by donating!
KERNEL
boot-HELLBOY-20130629-4.2
DOWNLOAD
Mirror for roms - Thank you eoghan
GAPPS
GAPPS MEDIAFIRE LINK (thanks Lars)
Changelog:
shpongle_primou-20130630
BETA
Fix layout of MultiWaveView and GlowPadView
Remove opaque check in GLRenderer when preparing dirty region
Fix failure of cancel P2P invitation
Added HALO (thanks to ParanoidAndroid team for sources)
Don't bring home to the front if we're opening a floating activity
Give floating flag to previous activities in the stack
HALO code clean up and improvement
Settings: Halo has its own sub-menu now
Shpongle settings: New icons
HALO: Option to pause the underlying app when notification is displayed
Reworked Maximize widgets options
Added the ability to long-press on the little lock icon to unlock the device when maximize widgets are ON
Removed default camera widget from carousel lockscreen
Re-added the DIM layer on custom backgrounds in Lockscreen (thus making lock clock/clock widgets to be visible in white wallpapers).
KERNEL:
Re-added the internal task killer values (multi tasking should perform better now)
Tweaked the sched_latency_ns and sched_wakeup_granularity_ns options
Creates hwui.deny folder in local - HWA Settings should work without a problem now.
shpongle_primou-20130521
BETA
Fixed bluetooth headset issue
Fixed a condition in location manager - when the location was acquired, the manager was searching again and again for the location when it was needed. this fix stops that until a new location is acquired.
Fix a nullpointer exception in Settings
shpongle_primou-20130518
BETA
Added the kill application selection in Hardware Keys
Added "Switch to last app" action in Hardware keys
Default values for hardware keys vibration.
Smaller vibrations on virtual keyboard - the feel is AWESOME!
Fixed video playback and re-added video fixes - Thank you Jolas for spotting the files missing in previous version.
Re-tweaked the UI status bar tunables so that it works better now
Changed wallpaper with something more minimalistic
Removed Take bug report and Power menu bug report from Developers options
Switched OFF the Daydream screensaver feature - Thanks Lloir for the tip.
Fixed Accessibility menu FC
shpongle_primou-20130517
BETA
Renamed to Shpongle
Shpongle tweaks menu
Removed evervolv's bootanimation
Status bar tweaks
Status bar speed up tweaks
Fixed swipe left - right in status bar notifications area (not quite perfect, but better)
Hardware keys - 3dot menu overflow added, kill app with back button fixed
Display rotation feature added
Lockscreen customizations added - custom background, target shortcuts
LockClock compatibility
Power menu tweaks added
Expanded desktop added
Long press on clear all - clears cache
Battery LED fixed
Performance menu - Voltage settings added - Credit: Maxwen
Quiet Hours feature added
Give proper permissions to Superuser for SystemUI (needed by clear all - clear cache action)
Fixed Flingtracker hanging the Statusbar when swiping down with two fingers.
Fixes for video playback
Performance menu acts like Developers menu now
Pressing any key on the Warning message from Performance menu will exit the settings.
Volume panel style and linked volumes together
Don't adjust volume when vol-downing to vibrate or silent
Fixed color gradient issue (mainly visible in Settings - that ugly background)
GlowPadView : Re-enable magneticTargets
Option to always show battery status in lockscreen
Options to start widgets maximized (bugged)
Increased widget lockscreen limit from 5 to 9
Change the way the system calculates hw rotation
note - the red changes are somewhat important
ev_primou-3.2.0-20130511
BETA3
ADDED:
Sound Settings
Ability to enable/disable sound when adjusting volume with hardware keys.
Ability to enable/disable and choose a sound when connecting/disconnecting the usb cable.
Language & Input
Hardware keys remapping.
Development
Added ability to choose an action at boot for MediaScanner.
Statusbar
Ability to swipe on statusbar notification, left or right, to view quick settings or notification area.
Transparent statusbar notification from now on (since our device = 512mb RAM).
Recent apps window
Clear All button.
OneV settings
DoubleTap2Wake & DoubleTap2WakeDuration - all credits goes to Maxwen.
FIXED:
Recents apps window lag fix.
Status bar quick settings/notification button pressed fixed (it turns blue when pressed).
Status bar download/upload animation smoother than last time
Clear all button pressed fixed ((it turns blue when pressed).
Browser unable to copy the same text copied before.
Account malloc mmaped pages as native heap (see them as memalloc, not ashmem).
"[+>" more icon in status bar is now visible.
Fix array index oob in Matrix3f.loadRotate().
Fix NullpointerException in MediaMetadataRetriever.
Remove possible leak when exception occurred in LocalsocketImplementation.
Text2Speech memory leak.
Memory leak in ActivityStack.
A leaked partial wakelock in AbstractThreadedSyncAdapter.
Possible leak in AudioGroup.cpp.
Paint.cpp: breakText returning count of glyphs not chars.
Javacrash java.lang.NullPointerException in com.android.browser.
Correct the target app token for input method window.
CHANGED:
Write entropy data 4 times a day instead of 8 times.
Increased touch sensitivity (UI IS snappier).
Removing ineffective code in WifiService.java.
MediaScanner: delete abnormal elements in prescan procedure & Update thumbnail when file is updated.
Browser: Pinch to zoom and scrolling improvements.
ev_primou-3.2.0-20130503
BETA2
Bring up Evervolv's bootanimation.
QuickSettings: Carrier data directly switches data ON/OFF (one click to enable carrier data, long click to go to Data settings).
QuickSettings: Rotation toggle (rotations on, rotation locked).
Bring up AOKP bundled Performance Control app in Settings (VOLTAGE CONTROL GIVES FC -
Don't use this feature until I fix it in the next release).
Renamed Advanced Settings to One V and
moved below EVToolbox.
Removed Nexus livewallpaper wallpaper.
Added ability to swipe on top of fullscreen apps (games)
to see the Statusbar for 5 seconds.
ev_primou-3.2.0-20130427
BETA1
UI crashes/freezes/apps crashing/lockscreen disappearance - GOODBYE!
(ChangeID: I5ad9aa8e98eb6fd554b01022439141fe4a55bd70)
Fixed UI/status bar crash while swiping down onto the lockscreen
(ChangeID: I2a6a5c74ed22d8e6b7a3bea3424ff2879d227105)
Re-added Email apk for those of you who uses it
Removed tilerenderer from display (forgot about that)
ev_primou-3.2.0-20130426
ALPHA5
Headphones BASS fixed
ev_primou-3.2.0-20130425
ALPHA4
GPS fixed - thank you maxwen for the libraries!
ev_primou-3.2.0-20130423
ALPHA3
Browser glitches fixed
Fixed buffers allocation - UI freezes, crashes
Easter egg added! Find it!!!
Removed EVTIPS and EVwidgets - We are getting ready for next step
ev_primou-3.2.0-20131804
ALPHA2
Embedded Superuser into Settings - no need for separate apk
Added device specific Advanced settings with FAST Charge, S2W and Button Backlights
More to come in the future!
A few screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Video presentation - Thank you, @ijayesh

awesome! gonna try it right NOW!:laugh:
lol at "cumming soon" XD

Well ice must be having sex at the moment. Since he's gonna cum soon. and damn missed first comment. gonna try this out in a minute. Thinking about just using my omnia W as a camera and use 4.2 as a daily. Even though that would mean I'll have to carry two phones.
Sent from my One V using xda premium

thanks a lot matee for this
Sent from my HTC One V

gaaps??

Sorry to say this but you will get a lot of UI freezes and force closings - I don't know the cause of it YET, but you guys can get me logcat of those - PLEASE - work with each other and provide only 1 LOGCAT of the same issue, not multiple logcats for one issue. I want you to work as a team because only then this rom will get where it should be, with your help!
I want:
logcat with GPS trying to lock into satelites (using google maps or something similar while you do a logcat);
logcat with the UI freezes;
I don't want:
logcat for camera;
GAPPS for 4.2: gapps20130301

Booting my pc and gonna do logcat for GPS. Anyone else wanna take UI? Else ill take that aswell.
Edit: rom download link doesnt work for me. Anyone please confirm.
Edit 2: nvm gotta copy link and than go to the site dont click on IT IT wont work.
Sent from my GT-I8350 using Board Express

Sabbit said:
gaaps??
Click to expand...
Click to collapse
Thank you for reminding me. I can't thank you on the thread - no thanks for today.
lars1216 said:
Booting my pc and gonna do logcat for GPS. Anyone else wanna take UI? Else ill take that aswell.
Sent from my GT-I8350 using Board Express
Click to expand...
Click to collapse
Thank you as well. Take note that the status bar seems pretty laggy and unstable if you play with it. I managed to get SystemUI to restart itself while I was in the lockscreen and I wanted to slide down the status bar. I pressed and hold the statusbar for 5 seconds while in lockscreen and the UI just restarted itself.
Another issue:
When you receive a SMS and you are in the lockscreen, slide the statusbar down, and press the message. You will not be directed into the messaging app but instead you will see the lockscreen. When you will slide to go to home screen, the message saying that the sms app has stopped working will appear - This issue is easily fixed by forcing the status bar to not be accessible when in lockscreen - Need to search for the code to implement it. MINOR issue!

stupid internet being stupid, hurry up please rom is almost done but for gps i need gapps too which take a long ass time for some reason... goo.im seems to be a really slow host, everything i download from them takes a long ass time.

^^^^ NP m8!

lars1216 said:
stupid internet being stupid, hurry up please rom is almost done but for gps i need gapps too which take a long ass time for some reason... goo.im seems to be a really slow host, everything i download from them takes a long ass time.
Click to expand...
Click to collapse
i will upload the gapps to mediafire but now I need to go home. or you can do it and give me the link to post it in the OP - remember, you will be my project manager.

i'll upload it when its done downloading

OMG WOW !!!!!
Will try asap Thanks a ton ice <3 <3
Ice Gift to the community :good::good::good::good::good::good::good::good::good:

well done Ice, really a gift for us.
*mersi*

logcats for gps (2 of them) are attached. Actually to me GPS seems to be working fine since it knows exactly where i am. Gonna try to do UI in a bit if no one else wants to do, need to make some food first since i havent eaten since 8 am

lars1216 said:
logcats for gps (2 of them) are attached. Actually to me GPS seems to be working fine since it knows exactly where i am. Gonna try to do UI in a bit if no one else wants to do, need to make some food first since i havent eaten since 8 am
Click to expand...
Click to collapse
Lars, if you can, download phone tester from Play and test GPS and see if its locking.
Can't wait to try this out but as I've got to get up early must sleep now.:thumbdown:
Sent from my One™ V using xda-developers-app

Why didnt i think of that? thanks soham! that doesnt work, it says 0/0 sattelites (logcat attached as always) really weird since google maps knows my exact location which i assume it cant know with only the gsm network. well ill let 1ce look at it and find out whats causing that (hopefully) but now im really gonna make some food! hungry as hell :$
Also made a logcat for UI but dont know if i did it the right way actually, 1ce please tell me if the UI logcat is what you need it to be, if no ill try again

I'm pretty sure I did. But I'm off the pc for now. Started to get a worse headache again and don't wanna take any risks. I'll make another one if it isn't what you need. hit me up via pm if it isnt. Alright? By the way, share chicken wings!!!!!
been trying to get another logcat for you just to be sure, but cant get the ui to crash again -.-, like when you need it to crash it wont crash and ill bet you if i take it away from my pc it will crash all the time :')
Edit: still won't crash. I see that as a good thing but still it's not really good since I can't help you troubleshoot this way. I'm sorry man, been using the UI very intensively in the last few hours but it just won't crash. So that can mean two things, it's fixed or I'm just really lucky.
Sent from my One V using xda premium

lol i cant get it to FC! had a initial FC after booting but no FC after that.....if ur wondering, using this ROM for 4 to 5 hrs at least now

See I'm not the only one. Maybe 1ce his One V is cursed now? Xd
Sent from my One V using xda premium

PIE instead navbar

Anybody running PIE controls instead navbar?
First I did hide navbar by xposed and xmiui tweaks (2.0). After that I tried different apps for PIE.
Well-known LMT launcher isn't working for me. simple PIE also isn't working properly because I don't see icons and edges of my PIE.
As last I tried xposed module "unique controls". It is working fine but hasn't second or long press actions...
Has anybody similar experiences?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Thanks for sharing information, Mix's screen is great at full!

Only edited build.prop and added lmt. All works incl. user images. Only quirk I'm having is that everytime i reboot I must make sure to go into the app first, which automatically takes me to the drawing over other apps toggle. It turns off on reboot. This is something I have come across before. Only on marshmallow roms though, not on lollipop or nougat.

qemu.hw.mainkeys = 1
for hiding navbar?
That's all or changed you anything more for working LMT?

vergilbt said:
qemu.hw.mainkeys = 1
for hiding navbar?
That's all or changed you anything more for working LMT?
Click to expand...
Click to collapse
Yup. There are two empty lines at the bottom. Just add and leave one empty line. No need to add another. Doubt it matters though.
In my "short" post here:
http://forum.xda-developers.com/mi-mix/how-to/guide-flash-global-china-rom-root-gapps-t3510592/page4
I mention lmt. Just gonna quote myself:
"On lmt launcher I had to set the touch area thickness to 35 for pie to register my finger. So i checked CIT (hardware test. Go to: about phone => press kernel version 4x).
And I can see my digitzer doesn't register my finger when I slide in from the sides up until i reach 32 pixels in. If I start from anywhere else and go towards the edge, it follows me perfectly.
Can anyone replicate this? I'm guessing this has to do with not getting unwanted touches when holding the phone."
I'm not sure the same applies to the top and bottom.
And by touch area thickness I mean activation area thickness:silly:

Thx a lot...
Only to set area thickness to 35 was my solution for get working LMT...
[emoji3] [emoji3] [emoji3]

vergilbt said:
Thx a lot...
Only to set area thickness to 35 was my solution for get working LMT...
[emoji3] [emoji3] [emoji3]
Click to expand...
Click to collapse
One thing i forgot to mention. By increasing the activation area, you are also increasing the chance of triggering pie when you hit the edgekeys on your keyboard for example. I would avoid making it long enough to reach that far down (this is if you have the triggers on the sides).
If you use bottom then the same pertains to stuff you might have there. But I guess this is very obvious.
Don't you just love it. All screen, all the time. I have yet to see a perfect alternative. All app/OS solutions still make the nav bar glitch around at times.

No worries...
I'm using LMT for many years (especially on smaller screens like Nexus 4 and 5)
[emoji6]

just wondering - did you try using the gravitybox module in xposed? i use that for pretty much everything. this is the first thing i'm going to do is setup pie controls, i really have no idea why everyone doesn't prefer them so much quicker and more efficient

Using xMIUI tweaks... Heard about some issues when using gravity box...

vergilbt said:
Using xMIUI tweaks... Heard about some issues when using gravity box...
Click to expand...
Click to collapse
where is xmiui tweaks found at? i search for it on the xposed modules and i'm not finding that. is there a different place to find modules for miui? thanks
edit - ahhh...it is in the playstore

I am using simple control from the same creator of simple pie:
https://play.google.com/store/apps/details?id=ace.jun.simplecontrol&hl=en
I found this behave much better for my taste. you click the bottom to bring up the navigation bar, you set delay and auto hide to suit your taste, the bar disappear after a while to maintain the full screen experience on Mix.
With PIE, or simple PIE, you have to swipe then click, and the pie bar is gone instantly which i don't think is ideal. And more importantly, because you need to swipe and click, that's one gesture less you are free to use.
I haven't rooted my phone (still waiting for unlock code), so the swipe up action brings the navbar back if you don't use xposed modules. Simple control solve that problem as it's purely click action.

Ok, i actually found something I think that's better, FloatMenu
https://play.google.com/store/apps/details?id=com.ksxkq.floating&hl=en_GB
No more buttons what so ever, just do swipe actions from edges and you get the home/back/recent actions. Unlike PIE which you have to swipe and click, more importantly, you don't have the ugly (imo) pie overlay. There is no overlay at all if you use Float Menu. And it has some advanced options such as disable during keyboard...etc.
p.s. I am still waiting for my BL unlock code to root my phone so I can completely get rid of Mi Nav Bar, once that's done, I can test all these methods more realistically.

wu5262 said:
Ok, i actually found something I think that's better, FloatMenu
https://play.google.com/store/apps/details?id=com.ksxkq.floating&hl=en_GB
No more buttons what so ever, just do swipe actions from edges and you get the home/back/recent actions. Unlike PIE which you have to swipe and click, more importantly, you don't have the ugly (imo) pie overlay. There is no overlay at all if you use Float Menu. And it has some advanced options such as disable during keyboard...etc.
p.s. I am still waiting for my BL unlock code to root my phone so I can completely get rid of Mi Nav Bar, once that's done, I can test all these methods more realistically.
Click to expand...
Click to collapse
When do you have to click on Pie? You just swipe in from one side and let go when you reach the right key.. you can also adjust longpress time for second layer of keys. If you use lmt, you can also add custom gestures etc. But I find it better to have an overlay with quick access to fav apps. Quicker to switch that way than through recents menu.. best would be as you say to not have anything.. Pie offers more keys/shortcuts quickly. Best would be no overlay, but hardly the most functional. Can only imagine replacing all my shortcuts/keys with gestures. Seems like a nightmare to remember.
But if you don't like it, you don't like it

benziii said:
When do you have to click on Pie? You just swipe in from one side and let go when you reach the right key.. you can also adjust longpress time for second layer of keys. If you use lmt, you can also add custom gestures etc. But I find it better to have an overlay with quick access to fav apps. Quicker to switch that way than through recents menu.. best would be as you say to not have anything.. Pie offers more keys/shortcuts quickly. Best would be no overlay, but hardly the most functional. Can only imagine replacing all my shortcuts/keys with gestures. Seems like a nightmare to remember.
But if you don't like it, you don't like it
Click to expand...
Click to collapse
I think it's all down to preference, when I said you need to click in PIE, i meant you need to swipe in from side, then you need to look at overlay and locate the keys you want to press then releáse, this whole process is longer than the method I use.
So in quick summary:
In PIE, swipe->locate->release
In Floating Menu, Swipe->release
You take out the locate step and you also get rid of the ugly(imo) overlay. Downside is you also get rid of the quick access app option but i personally don't like it at all. If quick access app is a must, there are tones of app that can let you do that with swipe action, i just don't want it to mix with my nav bar bottom swipe.
I set my floating menu at the bottom, so recent app in bottom left, home in bottom mid, back key in bottom right, just like where you have the physical or Nav bottom, and I can swipe it without looking at the phone, and because there is no overlay, i don't need to locate also. In real usage, it has the least learning curve i think.
I am enjoying this method a lot more than others apps, but that's my preference.

wu5262 said:
I think it's all down to preference, when I said you need to click in PIE, i meant you need to swipe in from side, then you need to look at overlay and locate the keys you want to press then releáse, this whole process is longer than the method I use.
So in quick summary:
In PIE, swipe->locate->release
In Floating Menu, Swipe->release
You take out the locate step and you also get rid of the ugly(imo) overlay. Downside is you also get rid of the quick access app option but i personally don't like it at all. If quick access app is a must, there are tones of app that can let you do that with swipe action, i just don't want it to mix with my nav bar bottom swipe.
I set my floating menu at the bottom, so recent app in bottom left, home in bottom mid, back key in bottom right, just like where you have the physical or Nav bottom, and I can swipe it without looking at the phone, and because there is no overlay, i don't need to locate also. In real usage, it has the least learning curve i think.
I am enjoying this method a lot more than others apps, but that's my preference.
Click to expand...
Click to collapse
When you have used pie for half a day or less, your thumb can pretty quickly slide in to the right key. You don't think consciously, just muscle memory or whatever one calls it :laugh:
But you want it clean, I understand
Can you customize the looks on simple pie? It can look better than stock. At least with lmt. Just had to squeeze that in there.

benziii said:
When you have used pie for half a day or less, your thumb can pretty quickly slide in to the right key. You don't think consciously, just muscle memory or whatever one calls it :laugh:
But you want it clean, I understand
Can you customize the looks on simple pie? It can look better than stock. At least with lmt. Just had to squeeze that in there.
Click to expand...
Click to collapse
You can certainly customize the looks on simple pie, but it remain to be "pie shape" xD, which i don't like.
I would rather go with simple control which I linked a few posts above if I still want the overlay.

wu5262 said:
You can certainly customize the looks on simple pie, but it remain to be "pie shape" xD, which i don't like.
I would rather go with simple control which I linked a few posts above if I still want the overlay.
Click to expand...
Click to collapse
I think you need to try a tasty english meat pie / apple pie, to change your perceptions on this lovely shape

benziii said:
Only edited build.prop and added lmt. All works incl. user images. Only quirk I'm having is that everytime i reboot I must make sure to go into the app first, which automatically takes me to the drawing over other apps toggle. It turns off on reboot. This is something I have come across before. Only on marshmallow roms though, not on lollipop or nougat.
Click to expand...
Click to collapse
have you figured out how to make LMT automatically launch on a reboot without making you go in and toggle the overlay again? this happens to me even sometimes without rebooting i have to go in and do it again. so annoying i also can't seem to get it working on the bottom of the screen but can on the sides.

knives of ice said:
have you figured out how to make LMT automatically launch on a reboot without making you go in and toggle the overlay again? this happens to me even sometimes without rebooting i have to go in and do it again. so annoying i also can't seem to get it working on the bottom of the screen but can on the sides.
Click to expand...
Click to collapse
No, I really haven't. As long as I have it locked in the recents menu, it never fails. But have to do the toggle on reboot. Just checked, on the bottom I can put the activation area thickness down to as little as 5 and it still responds everytime. What happens when you choose bottom?
I'm on 6.12.8 now btw. What are you on?
I'm hoping this blows over when nougat builds starts coming out, but it is not that much of a pain. Takes three seconds. I have only run nougat roms on my nexus 9, but it has never happened there.
Also, after using it for years, I don't honestly find the "pie" look that great either. I often just choose transparent for all the colors, so it's just my buttons and icons showing.