Related
Has anyone else run into this problem? Care to list such apps?
Google Music's interface is much different on the Note than it is on an S2 (at least for me). Where on the S2 artists, albums, etc are displayed in a long list of names, on the Note they are displayed in a long list of thumbnails of the artist, album, etc. This layout would make sense on a full size tablet and horizontal scrolling but it is very inefficient on the Note. Also much more taxing on the hardware (not that the Note is lacking in this department though). I would much prefer the S2's layout to quickly find an artist or scroll through the list.
Swiftkey X gives a warning when installed saying the phone version is incorrect for this device (the Note), use the tablet version. However, skipping the warning is not detrimental and the phone version works perfectly on the Note (have not tried the tablet version).
I assume this has to do with the resolution of the Note and apps confusing it as a Full Size Tablet. Anybody else seen this problem? On what apps? Workarounds?
JoyR2 said:
Has anyone else run into this problem? Care to list such apps?
Click to expand...
Click to collapse
I don't know if it's a 'problem'.
I don't necessarily like it with certain programs (some games are a bit painful to play), but I don't consider it a bug or anything.
It's a matter of detected screen resolution and how the app decides to use it. I don't see any workaround for it, unlike windows where you can use a selected resolution.
It would be nice for there to be an option to set screen resolution.
I imagine there are some people interested in the note because they want the larger size (larger icons/text/buttons/etc) but not necessarily the higher resolution. You can't always set that.
- Frank
it has full tablet resolution so it should run like that
kromosto said:
it has full tablet resolution so it should run like that
Click to expand...
Click to collapse
Ya, I know. But for some apps it really is not optimal. Just trying to get a feel for how many apps are going to encounter this "problem" (for lack of a better word).
Use spare parts to make the adjustment
Sent from my ADR6400L using xda premium
Plume thought that my note was a tablet. However the support team gave me a corrected version and said that it will be sorted in their next release
http://www.onskreen.com/cornerstone/
would be fantastic to have this capability on the Nexus 10. but nobody ever seems to work with it. any particular reason why?
>http://www.onskreen.com/cornerstone
>but nobody ever seems to work with it. any particular reason why?
No interest. Probably why it went open-source (it wasn't originally). My guess is that pushing bits for 3 concurrent apps would require more than a simple launcher swap, ie low-level optimization, and the OnSkreen peeps weren't up to it. Something like this would need to be done by Google.
The reason for lack of interest is obvious. Up till recently, Android's focus has been on phones, and muti-windowing is irrelevant on those. Even now, phone is Android's primary focus given its market size. The tablet's unique traits are still mainly left unexplored. Witness that multi-user acct--an arguably essential feature--was implemented only now in the latest 4.2 release.
IMO, the 3-pane fixed layout looks clunky (and ugly, but aesthetics can change). The need to configure each panel is clumsy as well, as opposed to, say, Win8's split-window scheme where one can config each window on-the-fly. Win8 does have the advantage of edge-swiping, which gives it an extra layer of configurability.
The underlying weakness of both this and Win8's fixed dual-windows layout is the Achilles' heel of touch UI (relative to mouse UI)--the lack of a precise pointer that would allow easy manipulation of multiple, possibly overlapping windows. Pen input is an option, but is likely not the answer.
The issue is resolvable, and for mobile OS'es to take the next step up from phone displays to larger form-factors, it will need to be resolved. Take this and Win8's split-screen as the first baby steps.
e.mote said:
>http://www.onskreen.com/cornerstone
>but nobody ever seems to work with it. any particular reason why?
No interest. Probably why it went open-source (it wasn't originally). My guess is that pushing bits for 3 concurrent apps would require more than a simple launcher swap, ie low-level optimization, and the OnSkreen peeps weren't up to it. Something like this would need to be done by Google.
The reason for lack of interest is obvious. Up till recently, Android's focus has been on phones, and muti-windowing is irrelevant on those. Even now, phone is Android's primary focus given its market size. The tablet's unique traits are still mainly left unexplored. Witness that multi-user acct--an arguably essential feature--was implemented only now in the latest 4.2 release.
IMO, the 3-pane fixed layout looks clunky (and ugly, but aesthetics can change). The need to configure each panel is clumsy as well, as opposed to, say, Win8's split-window scheme where one can config each window on-the-fly. Win8 does have the advantage of edge-swiping, which gives it an extra layer of configurability.
The underlying weakness of both this and Win8's fixed dual-windows layout is the Achilles' heel of touch UI (relative to mouse UI)--the lack of a precise pointer that would allow easy manipulation of multiple, possibly overlapping windows. Pen input is an option, but is likely not the answer.
The issue is resolvable, and for mobile OS'es to take the next step up from phone displays to larger form-factors, it will need to be resolved. Take this and Win8's split-screen as the first baby steps.
Click to expand...
Click to collapse
It doesnt help that when Cyanogenmod was considering baking Cornerstone into their builds, Google threatened to blacklist their roms from accessing the market/Google Play if they didnt change their mind due to potential compatibility issues... since then its seemed nobody wanted to risk touching it. Too bad, while I agree three panes were clunky, two panes like WinRT does could have been quite nice.
>It doesnt help that when Cyanogenmod was considering baking Cornerstone into their builds, Google threatened to blacklist their roms from accessing the market/Google Play if they didnt change their mind due to potential compatibility issues...
Didn't know that, but it makes sense. Fixed layouts like this (and Win8's) rely on specific criteria to work, ie a widescreen aspect in landscape mode. While MS can dictate the form-factor for Win devices, Android devices come in varying shapes, and fixed layouts are doomed to fail.
For multi-windowing to work, layout needs to be adjustable, as well as dynamically adjusts to both portrait and landscape orientations. Secondly, multi-window needs to be supported by all apps, not just some (like in Samsung's implementation). This means it needs to be in the OS, not an add-on.
Samsung's multi-window scheme is a more elaborate version, and is probably a precursor of what we'll see in Android. Note however that the Galaxy Note 10.1 in this example has pen input support, which obviates the Fat Finger syndrome. A platform-wide scheme will need to accommodate "imprecise" adjustments, which IMO will likely mean a snap-to-grid windowing system.
Edit: I added video for the 5.5" Galaxy Note 2 below. Even though the Note 2 supports S-Pen, apparently the cascading/adjustable window portion was dropped, and only the adjustable dual-window remains.
This makes sense for screen sizes 7" or smaller, and would be an improvement over Metro's current scheme. But the missing piece is for larger sizes WITHOUT the precision (and fiddliness) of pen input. This matters especially when tablets gain the use of external displays via Miracast. Again, my opinion is that cascading/overlapping windowing is still doable for Sausage Styluses, rather than just tiled, but snap-to-grid would be needed.
Unfortunately Niantic contacted me to abort this mod. More info: http://forum.xda-developers.com/showthread.php?p=42027875#post42027875
TL;DR version: I have created an Ingress app mod, it is awesome and will make you coffee. You can download it below.
OVERVIEW
Hi,
after more than a 2 years of inactivity in the modding field I'm back with a new mod. This time it's Ingress app. I think and hope it'll be much greater and more advanced than Google Maps mod. There are a lot of things to improve and I think some of them won't be ever added by Niantic, so it's a good idea to mod this app.
First I want to clarify I will never add any kind of cheating to this mod. My goal is to make Ingress game more enjoyable, not less. Questions about location faking, items cloning, etc. are not welcome here. I'm serious. Still if you think this mod is a bad thing and/or if you're from Niantic then please read a section about my motivations below and feel free to ask, suggest or criticize. I make it for Ingress players and I'm very interested in their opinions.
DOWNLOAD
First: you do this at your own risk! I'm sure it won't brick your phone, but remember you may be banned by Niantic. My mod doesn't do any kind of cheating behavior, it doesn't do anything that original app doesn't do, but there is always the risk.
Also if you downloaded apk from different site then check sha1 of this file to make sure it's ok. Unfortunately such mods create good opportunity to inject some malware, because users search for an application in the internet and anyone can redistribute it. I sign this app with my own keys, so if you have installed my mod earlier, now you have downloaded newer version from the internet and Android says it has different certificates then don't install it!
"Mute" variant has all sounds removed, so apk is ~2.5 times smaller and most likely it uses less memory.
ingress-1.26.1-broot-0.2.0-mute.apk
SHA1: 976342081c963998f8a6e56b735fe97581ab335f
ingress-1.26.1-broot-0.2.0.apk
SHA1: dce5399802c8f11287a7cf399c1bb5265f8251e2
Older versions:
ingress-1.26.0-broot-0.1.0.apk
SHA1: ea95d8e36324c6c4a175e0cf254cd65a4797049f
If you have original Ingress app installed then you have to uninstall it first. Same if you want to install original app over a modded one.
FEATURES / TODO LIST
I know simplifying and automation of too many things may be considered cheating, so I have divided all features into several categories: from the most "innocent" ones to some smart assistants. As I stated above, if you think some of them are just too much then feel free to write about it. For me features up to 3. category are ok. Category 4. may be controversial and I'm not sure if I want to implement it. I'm glad for your opinions. Some features (e.g. 2.11., 3.7.) aren't actually related to category descriptions, but I "feel" them as category 2., 3., etc.
I don't want to force people to use every modification, I'll try to make them all opt-in, so modded app will work exactly as the original one until you change this in the mod menu. If you see e.g. "Fullscreen" feature below then read it as "An option to enable fullscreen mode".
Below is just a list of features to make it clear. Descriptions, notes, statuses, implementation proposals, etc. are here.
Legend:
green - completed
orange - not sure about it
red - rejected
black - waiting / todo
1. Changes strictly technical and/or 4fun - they don't affect gameplay at all:
UI for small screens, but this is never ending task
Disable some graphics effects to make it less GPU consuming:
portal particles
xm particles
Fullscreen.
Remove globe intro.
Change colors of factions.
Exit confirmation dialog - it's good for low memory devices.
Keep sceen on.
Disable vibrator.
2. UI changes: new screens, shortcuts, etc. - it makes things easier, but it won't do anything for you:
New screen with mod settings, credits, etc.
New inventory screen with items presented as a clear table.
Number of all items in the inventory - it's very important because of items limit.
New portal keys screen.
Remove original items screen.
Shortcuts to various actions from the main screen.
Modify chat to make it easier to read and harder to accidentally send private message to public channel.
Link to portals from system messages in the chat.
Real-time distance to portal on details and upgrade screen - its necessity is obvious to anyone who played Ingress
Additional info about the portals directly on the map screen.
Logging and statistics.
Circles around the player similar to one at 40m - just for better feeling of the distance.
Number of keys on portal info, upgrade and linking screens.
Config: update interval.
Config: maximum scanner zoom out.
Deploy button uses highest available resonator, not lowest.
3. Automation of some more complicated or repetitive tasks - it delegates multi-clicking to the squad of highly trained monkeys, but it won't think for you:
Dropping/recycling multiple items of the same type at once.
Firing multiple XMP
Picking up all items in the range - with above it's very easy to give items to other agents.
Hacking all portals in range - not very useful because of timers
Auto deploy resonators using a template.
Templates specific to a portal.
Other agents presence detector.
4. Smart assistants:
Hacking timers for each portal: both 5m and 4h ones.
Auto hacking portals in range while moving (using timers).
Smart auto-deploy.
XMP damage assistant.
Linking assistant for optimum CFs in a specific area.
Continuous linking assistant.
Bugs:
The maps are gray when submitting new portals or reporting bad ones.
NEWS
v1.26.1-broot-0.2.0 has been released!
2013.05.26
Updated Ingress to 1.26.1.
Added layouts for small screens: Eugene's 1.26.0.20130526
Added mute version - for smaller size and likely smaller memory usage.
Added fullscreen mode.
Added option to disable portal particles and xm particles.
Added restart button - it's useful for reloading UI changes (fullscreen mode, layouts, etc.).
Fixed gray maps problem.
v1.26.0-broot-0.1.0 has been released!
2013.05.22
Initial version.
New screen with mod settings, credits, etc.
New inventory screen with items presented as a clear table.
Number of all items in the inventory.
CREDITS
Eugene Kartashov - layouts for small screens.
Of course Niantic Project for this awesome game!
Thanks!
FEATURES DESCRIPTION AND NOTES
1.5. Change colors of factions.
I did this before and it's kind of cool: https://plus.google.com/u/0/106080343103638200670/posts/a9krpWApjz5
2.4. New portal keys screen.
I have some ideas, e.g.:
keys grouping/tagging
group/tag keys manually or automatically by their location, name, etc.
filters and sorting by: name, distance, level, owner, etc.
, but I think Niantic want to improve keys management, so I wait for their move.
2.5. Remove original items screen.
For now even if you prefer new items screen the original one is still needed to access portal keys. We can wait for 2.4. or at least add an option to limit original items screen to portal keys and rename it accordingly.
2.6. Shortcuts to various actions from the main screen.
I think it's one of the most important additions, so it has to be well designed. I see it as a HUD-like buttons similar to "FIRE XMP" when you long-press on a map, but much smaller, probably square with icons. Things to consider:
toolbar at the top or the bottom of the screen - I think it's better than left/right
fixed with 5-6 icons (4" screen) or scrolling horizontally
fixed icons or customize them and their positions
an option to open a full semi-transparent menu with all available actions
Actions could be:
fire last XMP
fire highest/lowest XMP
fire XMP of specific level
same for power cubes
hack portal - click button then click portal. This way you don't have to enter portal details screen which is faster and you don't lose the map.
link portal - same as above
set target? It's in a long-press menu already, but we can add it here for consistency and maybe to remove long-press menu.
actions from other mod additions
2.7. Modify chat to make it easier to read and harder to accidentally send private message to the public channel.
Current problems are:
is there anyone who has never sent a private message to the public channel? Is there anyone who did this only once or twice?
it's hard to read conversations between agents, especially public ones, because they're mixed up with system messages
I was considering adding some kind of filters to select which types of messages you want to see, but it doesn't fix first problem. Now I think of something else - 4 tabs/channels:
faction - as normal
public - public conversation only, so system messages won't disturb you and you don't accidentally respond [secure] messages
system - you can't send a message here
all - all above, so it's similar to current "All", but you can't send a message here - you have to choose proper channel intentionally. It can have additional filters to select messages to show.
This feature may be hard to do or even impossible, because most probably Ingress server doesn't have API to filter messages as above. Of course I can read "All" channel and filter it on the app side, but it may not be that good.
Also I won't be surprised if Niantic itself will redesign chat in the near future, because it's definitely wrong.
2.10. Additional info about the portals directly on the map screen.
E.g.: level, if you have a key (how many?), etc. It could be customizable and there could be a shortcut to toggle showing this info.
2.11. Logging and statistics.
I love this one I can log all kind of actions like: hacking, attacking, dropping and picking up items and XM, deploying resonators and portal mods, adding custom "snapshot points" to organize above, etc. and then create a lot of various statistics:
how many hacks did you do (faction, enemy, neutral) today, in last week or month?
how many items did you get from these hacks?
what were the levels of hacked portals and items?
how many XM did you get?
how did you spend this XM?
how many resonators did you deploy and what were their levels?
how many resonators did you destroy, how many portals did you capture?
how many links and CFs did you create/destroy, what were their MU values?
which portals do you hack/attack/build most often?
how much time you was playing?
what items did you spend to build up a farm and what items did you get from it?
Statistics could be tabular, graph, pie and very flexible. I'm also considering two things:
sending some of above statistics to my server to create global statistics for all users. It would let us do some research, e.g.: what is the probability to get L7 item from L6 portal, etc. Of course sending these statistics would be fully optional, you would have to enable it by yourself.
optional paid application to read these statistics - in addition to the free one. It could let you remove ads or just say "thank you" (i.e. it would be the same as free one), but I don't want to piss off someone in Niantic. I think it would be fair, because statistics app would be quite complicated and time consuming and there will be free version, but you never know what's the opinion of other people.
What do you guys think about above two things?
3.5. Auto deploy resonators using a template.
Agent can configure multiple templates and choose one of them when doing an auto-deploy. Template could be defined by:
its name
minimum and maximum level for each resonator
prefer lower/higher level for each resonator
Examples:
"Lowest portal" - each resonator set to L1-L8 and prefer lower for all - it's the same as clicking "deploy" 8 times.
"Highest portal" - L1-L8 and prefer higher for all
"Highest <L7" - L1-L6, prefer higher for all
"Standard L4" - L1-L6, L1-L4, L1-L5, L1-L4, L1-L6, L1-L4, L1-L5, L1-L4, prefer higher for all - it's standard 4xL4 2xL5 2xL6 and it'll use lower resonators if you don't have all of them
another "Standard L4" - same as above, but L6-L6, L5-L5 and L4-L4 - it won't automatically downgrade resonators, but warn you about the lack of resonators
Also some templates could be predefined by default.
It won't work well with existing resonators, it won't choose optimal way to upgrade them, but this is how it should be - it's just: "do it using a template", not: "Calculate optimal situation".
3.6. Templates specific to a portal.
Extension to above: sometimes you know that e.g. NE resonator of some portal is harder to destroy, so you want to place highest resonator there. You can create a template specific to a portal, so it won't mess up main list of templates and it will be auto selected when doing auto deploy for this portal.
3.7. Other agents presence detector.
It read system messages log to find the last actions and positions of other agents (actually positions of portals they've built/attacked). This information could be used to e.g.:
show last position and action of specific agent
show a list of nearby agents: allied or enemy
alert if some other agent will show up below specific distance from you
4.3. Smart auto-deploy.
E.g.:
calculate max level of a portal that you can build alone - depending on your inventory and already deployed resonators
deploy minimum number and optimum resonators to get to specific portal level
prioritize excess resonators and save scarce ones
deploy high and low resonators evenly to make attacking a little harder
if upgrading existent resonators, prefer to upgrade ones with low XM
4.4. XMP damage assistant.
E.g.:
approximate damage dealt using specific XMP in current position
calculate the best spot to fire XMP of some level
4.5. Linking assistant for optimum CFs in a specific area.
You select a group of nearby portals, assistant build links and guide you through place to get as many CFs and AP as possible.
4.6. Continuous linking assistant.
You see an icon near the portal if it's possible to create a link(s) from it to create a CF. It let you create this CF with few clicks.
It may be not possible to do, because it would have to scan big area to know if there are a link between remote portals.
MOTIVATIONS AND FEW WORDS TO NIANTIC
As I stated above my goal is to make Ingress game better and more enjoyable for people. If you think it's evil then please read my motivations and explanation below:
There aren't and never will be features for cheating: location faking, sending same action several times, automatic passcode submitter, etc.
As I said above I have divided mod features into categories of different "dirtness level". I focus on "clean" features and I'm open to suggestions or criticism from players or even from Niantic itself.
I don't share my code and I obfuscate it to not make Ingress easier to hack by other people.
A whole game and world of Ingress is about hacking and reading between lines. I think my mod fits this world perfectly. There are some people who leak Ingress app from NIA and there is some guy somewhere in the internet who tries to get even more from it. It makes perfect sense
I think there are many good features that will be never added by Niantic. I see several reasons: statistics won't be added because it doesn't make much sense for storyline. Why NIA would add such feature? Intro skipping or new items screen won't be added because these features prioritize quick access over a nice look. Niantic can't do the same because Ingress would look like a game for nerds. But there are many people who don't care about the look because... they're nerds ;-P
And finally: I won't fight Niantic, so if they don't like my mod and decide to react then there will be no mod anymore.
If you're from Niantic then please think what is the best for Ingress users. If you don't like one or two of my features then I'll remove them and keep the valuable ones. If you still think this mod isn't good and it's a matter of time before you react then please do it sooner, not later. Mod won't be very popular yet, Ingress players won't be disappointed so much and I won't lose a lot of my time
FINAL NOTES FOR USERS
Once more: feel free to suggest new features or changes to existent ones. You can also criticize a whole mod idea. I want to know what do you guys think about it.
If you get a force close then post a logcat and mod version here.
If something doesn't look ok then post a screenshot. I have a 320x480 and 480x800 devices, but I can't test it on 240x320 and >480x800 resolutions.
You can also report language faults in the app or even here. English isn't my native and I often write something that doesn't seem natural even to me. I would be happy if someone would suggest better names or descriptions for configuration options, etc.
Of course you can redistribute this mod, but please don't do that if you don't have a good reason. I just want to know how popular it is. Also if you redistribute it then please add a link to this thread to give users a full context.
If you want to make a donation then link is in my signature, but remember that this mod may be killed by Niantic at any time.
[RESERVED]
[RESERVED2]
Very amazing
I'm gonna try it out on a new account just to be safe, but I love the work and holy cow you did a lot and I can't believe it.
Niantic better sit down and learn some must needed features and options. The globe one for sure
Sent from my MI 2 using Tapatalk 2
Keep up outstanding work. I just installed this mod and I confirm that it works flawless.
I'm looking forward to future updates.
iBotPeaches: I did a lot? But you have noticed that above features list is mostly a TODO and for now there are just new items screen and intro skipping? I'm not sure if this is clear from above posts.
I wanted to release it early to get some ideas from people.... or be banned
What about a nosound version? It reduces the app size and removes the annoying sounds for people that are tired of hearing those squeaks
Please find attached a nosound version prototype.
it will be possible to have screen: "exit. are you sure?" when accidentally using back button?
Brut.all said:
iBotPeaches: I did a lot? But you have noticed that above features list is mostly a TODO and for now there are just new items screen and intro skipping? I'm not sure if this is clear from above posts.
I wanted to release it early to get some ideas from people.... or be banned
Click to expand...
Click to collapse
Ahh, I thought you did all that stuff that was bolded in the features list Guess I didn't read it well enough.
Hi, on mine HTC Desire it crash suddnly..
EDIT: Reinstalled, work like a charm..
One thing possibly worth pointing out: I think this version will not handle the new push messages, as I believe those are restricted by the certificate used to sign the app. Are you able to confirm this?
Otherwise, very cool work
phyreskull said:
One thing possibly worth pointing out: I think this version will not handle the new push messages, as I believe those are restricted by the certificate used to sign the app. Are you able to confirm this?
Otherwise, very cool work
Click to expand...
Click to collapse
They do work for me, at least the "@" notifications
Needs further testing.
Jackos said:
What about a nosound version? It reduces the app size and removes the annoying sounds for people that are tired of hearing those squeaks
Click to expand...
Click to collapse
Usually more variants = more problems, but I think mute version may be worth it. It's almost 3 times smaller and space is crucial on many devices. It might also use less RAM and start up faster, because sfx are usually preloaded into memory. I'll do some benchmarks.
ataru said:
it will be possible to have screen: "exit. are you sure?" when accidentally using back button?
Click to expand...
Click to collapse
Sure, but what for? If you accidentally exit application, you can return to it in no time.
phyreskull said:
One thing possibly worth pointing out: I think this version will not handle the new push messages, as I believe those are restricted by the certificate used to sign the app. Are you able to confirm this?
Click to expand...
Click to collapse
I'm not sure about it. I got comm notification today, but I was using Ingress just moments earlier, so it might be background service, not push. We'll see.
Brut.all said:
Usually more variants = more problems, but I think mute version may be worth it. It's almost 3 times smaller and space is crucial on many devices. It might also use less RAM and start up faster, because sfx are usually preloaded into memory. I'll do some benchmarks.
Click to expand...
Click to collapse
Exactly my point of view
However it's a pity that the app uses this same amount of RAM. It might get better if you remove corresponding baksmali lines, I just removed the sound files.
Brut.all said:
Sure, but what for? If you accidentally exit application, you can return to it in no time.
Click to expand...
Click to collapse
I guess it's because on low ram devices the app gets closed instantly. So a back fail-safe button would save him the app loading time.
Impressions and suggestions
Nice mod!
I am an addicted Ingress player and I really appreciate your work!
The new item tab is awesome!!
I only want you to know that there is a G+ user that is modding Ingress too:
Have a look here.
He did a version even for 240x320 screen.
Maybe you can have a look at his work
I hope you can keep this up to date
Works perfectly!
I'll keep an eye on that, your features list sounds extremely promising!
ingress-1.26.1-broot-dev1.apk
It's muted and should work on all screen sizes. Layouts for 240x320 and 320x480 were created by Eugene Kartashov (thanks!), but I have integrated them into single universal apk. It's just ~0.5MB larger than Eugene's separate apks. I can't test it on 240x320 because I don't have such device. Please confirm if it's ok or not. I'll add fullscreen feature before 0.2.0 release, so upgrade button won't overflow on some devices.
Also I can confirm sounds are loaded on demand, they aren't preloaded, so muted version shouldn't boot up faster. It should take less memory though.
Is there anyone who miss these sounds? As I said I would like to avoid fragmentation and I think muted version is just better.
And if you have 240x320 device then please tell me if new items screen looks ok, especially if you have 100+ items of one type. 320x480 seems to be ok.
[redacted]
Some cool ideas there. A few comments (posted here because I don't see a way to leave feedback on the site):
1) I'd put the Charms bar on press-and-hold of a button, probably Search (which doesn't currently have any Hold action assigned). Double-tapping is an action that literally nothing else on the Windows Phone OS uses, and especially a button that is sometimes capacitive and sometimes physical (depending on phone model) it's not something I advocate adding now. I like the idea a lot, though, especially for its tie-in with Win8. One thing to add to the Charms bar though: as on Win8 (where it shows a bunch of status info when you open Charms), the Status Bar at the top of the screen should be always visible when showing Charms.
2) There's already a way to get to the task switcher; while it's OK to have multiple methods for achieving the same goal, it seems like there might be something more useful to do than duplicating functionality through a more round-about approach.
3) There should be a more visible cue about the notifications center. Either have something drop down from the top (perhaps a "you have <X> notifications" bar with an appbar-like pull indicator?) or add a button specifically for notifications (two-level Charms bar? Move it to the right edge of the screen? Not sure how best to handle that).
4) I know the whole "swipe down to close an app" thing is very commonly requested, and comes from WebOS, and vaguely resembles Win8, and... I still don't know if I want it. Closing an app is pretty close to literally never needed; backgrounded apps are not generally allowed to use any system resources (they may hold onto some RAM, but the system will take it from them if a foreground app needs it). Closing an app the "usual" way - by switching to it if needed, and then tapping Back until it goes away - also works, although it's more actions. My biggest concern would be that right now, it's not really possible to ever do the wrong thing on the task switcher view. Closing an app, though, is a destructive behavior - you lose the app's current state - and is something that would need to be carefully implemented to make sure it never happens by accident... or perhaps make it optional entirely.
5) The Xbox Music feature looks pretty good, although the drop-down switch between Albums/Songs/Artists/etc. might be a bit too... background. Also, the really basic problems of the new UI - things like songs getting duplicated when they exist both on the phone/SD card and on the "Music Cloud" - really need to be addressed. Highlighting the Search thing - I know you mentioned it earlier with global search, but it's good to have more focused search capabilities too - as the current lack of Search in the music app is a Problem.
6) "Windows and Windows Phone share the same store" is way, way more complex than anybody might be realizing. Leaving aside the fact that most Windows Store apps aren't written for the resolution or aspect ratio of Windows Phone and would therefore possibly look kind of crappy if they were usable at all, and the fact that app models of the two OSes are pretty different (for example, Windows Store apps are allowed to request filesystem access and are required to implement the Settings charm, while WP apps have neither of those things), the APIs are just different. WP8 can use a sort-of-subset of WinRT (the API for Win8 apps) but it's not the same thing (and Win8 can't run WP7 apps at all, not even close). Finally, there's the issue that even the most powerful WP8 are half as powerful as even the lowest-end WRT tablets, and that's going to make a lot of things that perform fine on things like Surface RT be unacceptably slow on a Lumia 920 and impossible to run on anything with lower specs.
7) IE11 is coming for sure. The sync feature would definitely be nice. I'd also like to see some version of (desktop) IE's feed reader (shared with desktop Outlook) get integrated into WP8.
8) Integration with photo services, in the same way as other parts of the phone are integrated with Facebook and LinkedIn and Twitter and so on... that is an excellent idea. Come to think of it, Facebook pictures are already integrated (a feature I never really use) so adding others should definitely be possible. It would be cool if apps could integrate that kind of stuff without explicit OS support, but that may be aiming too high.
Thanks for the good feedback!
Hmmm, concept by who?
that'd be me.
The sync of bookmarks from Desktop IE to WP IE has already been confirmed for a future version of WP. They didn't say which one exactlly so it might take until WP Blue.
I personally don't like the idea of having the icons in the settings - at least not at the end, just looks kinda weird. Perhaps it would work better if you put them in front and aligned them properly on a grid.
Camera settings actually return back to the defaults when you relaunch the Camera App (and didn't save your changes as defaults).
As for the charms bar - I like the idea of a universal sharing and search feature but I don't particularily like the implementation of it with the charms bar on Win8 and I really don't see it work well on WP.
I like it but MS always let's its users down and dismisses the best ideas and concepts. WP will go now where higher that where it currently is now because of MS's ignorance. The next 2 updates for Luminas that includes the Amber and the GR2 or whatever its called don't really bring much to WP at all; who cares about another clock on the screen or data sense? Or more camera tricks...? Really now!!
@sinister1: Does that post really help? Come on, there's no value in just being negative everywhere.
Also, you call Microsoft "ignorant", but I guarantee that they know far, far more about the smartphone market than you do. If you want to be persuasive, you need to come up with arguments that have more substance to them than effectively just calling MS names.
@KlausWidraw: I think I'm with StevieBallz on the suggestion to have the Settings icons be left-aligned; they do make the items easier to identify, but having a consistent horizontal position to look for them at would help. That said, the ability to re-order the options would be huge; I use some all the time (like Cellular, which is annoyingly just off the bottom of my screen) and others not at all (like "lock screen", "tap+send", or "theme") once I've set them up initially, and would like them out of the way to make room for the options that I care about.
GDR2/Amber as well as GDR1 before it and GDR3 after it are mere maintenance releases. No one expects an Update from Android 4.2.0 to 4.2.1 or 4.2.2 to bring major new functionality. No one expects updates from iOS 6.0 to 6.1 to bring major new features. Somehow everyone (contrary to all reporting on those topics) expects those maintenance releases in WP to do just that. Really new functionality will only arrive with WP8.1/Blue and this has been known pretty much since the WP Blue name first appeared in leaks.
GDRs mainly serve the purpose of fixing some bugs and enabling new hardware functionality that is required for device launches. It has been the same with WP7. There were updates like Tango that served to enable LTE. GDR2 now mainly serves to enable the new capabilities that Nokia required for their Lumia 925 and Eos Camera phones and to keep Google Mail usable. GDR1 was mainly bugfixes, GDR3 will enable new hardware like even higher resolution screens.
Amber then is bundled with the GDR2 update rollout but IS NOT a WP update. It is a device specific capability update like we have seen them by all OEMs in the past.
If there are two things I would change about WP (from a user perspective) those are:
1) A clock tile that updates real time, like the HTC one (srsly want one).
2) Battery saver profiles that let me choose what i want to remain active (bluetooth, wifi, mobile data, background tasks)
That's about it.
From a developer point of view, things are very, very different xD
GoodDayToDie said:
@sinister1: Does that post really help? Come on, there's no value in just being negative everywhere.
Also, you call Microsoft "ignorant", but I guarantee that they know far, far more about the smartphone market than you do. If you want to be persuasive, you need to come up with arguments that have more substance to them than effectively just calling MS names.
@KlausWidraw: I think I'm with StevieBallz on the suggestion to have the Settings icons be left-aligned; they do make the items easier to identify, but having a consistent horizontal position to look for them at would help. That said, the ability to re-order the options would be huge; I use some all the time (like Cellular, which is annoyingly just off the bottom of my screen) and others not at all (like "lock screen", "tap+send", or "theme") once I've set them up initially, and would like them out of the way to make room for the options that I care about.
Click to expand...
Click to collapse
Sorry for being so negative but this is really how I feel and what's wrong with that? I know that not everyone will agree with my views or me with views of others but my negative feed back is feed back just like positive feed back is also feed back. I'm pretty sure that you have your gripes with other things.
I'm just feed up that devs come up with some of the brightest ideas and MS simply ignores them. Tell me what is so hard for them to open the OS just a little more for people to be creative? Seriously? Now the truth is the best substance. And of course if you still don't agree with me that's okay; I won't hold it against you because those are your opinions and the way you feel. Please don't take any of my rants personal as all they are, my personal opinions.
sinister1 said:
I'm just feed up that devs come up with some of the brightest ideas and MS simply ignores them. Tell me what is so hard for them to open the OS just a little more for people to be creative? Seriously?
Click to expand...
Click to collapse
I have to agree with you on this one. There are some understandable things for security's sake, but its ridiculous how complicated it is to customize Windows Phone 8 or even WP7. With WP7, you could only have a static lockscreen (ignoring LockWidgets from WPH) and couldn't set a custom text notification sound (besides MS' and HTC's.) I could add a custom ringtone, but it was a pain to do, period. With WP8, its a tad easier. You can just copy and paste ringtones, lock screens are customizable, and alarm can be customized as well, as well as the battery percentage can be pinned to the lockscreen/start screen. But compared to the other 3 platforms (Andriod, iOS, and now discontinued Symbian) could virtually anything could be changed. I remember when the 7.8 Beta was out and there were swapped fonts in the roms. Its something that no one had even thought about modifying until it was an issue.
I do have to say the native apps ability is appreciated, but it seems that Interop is still an issue (except I have no idea how problematic it still is). I do have to say I don't know much of whats been going on, due to jumping ship getting Verizon's Trophy late in the game (like when I first signed up here) and then finally moved to WP8 with their 928. So I'm kinda in the dark as to what has been added from the GDR1, Nokia's supposed Amber update, whats in GDR2, future FM support, ect. I really just wish that MS would be a little more verbal about whats in WP8's updates. They were bad with WP7 and they aren't any better now.
Another feature that MS is completely missing is Xbox Video. Seems stupid for them to say their experience is coherent between all their devices when its clearly not.
Can u guys tell me ....which phones will get windows 8.1 update .????
Sent from my HTC Explorer A310e using xda app-developers app
Some people don't like customization.
Customization comes with the cost of performance. I had an android with "customization" and whenever i "customized it" it became really, really, really slow.
In order to even have customization working, the system has to waist a lot of CPU cycles on stuff like checking 1000000000000000 settings to figure out what it should render next, swap a gazillion artifacts from storage to memory etc etc.
I want my phone to do what I tell it to do. I don't give a damn about more customization than it already has, and so are 99% of all windows phone users, whom increase in numbers day by day.
If you are going to give feedback disguised as QQ, then you should head over to microsoft's site and make your voice actually count. You complaining here all day, on a freeking developer/hacker forums, will not help!
Windows 8.1 blue will probably loosen up the developers a bit, if they are going to implement all our suggestions. Which will come for all windows phone 8 phones.
@mcosmin: The conecpt the you trade performance for customization really isn't true. Yes, the phone could eke out a trivial amount of better performance by hardcoding its UI styles, but they don't do that. Things like accent colors, background colors, text styles, etc. are all stored in the registry; you don't have to modify a single line of system code to modify or create themes of your own, and they'll run just as fast. Other forms of customization, such as replacing some of the builtin libraries with custom ones, might be slower in certain circumstances, but only if the custom library either added new features (not just new customizations, but actual functionality that wasn't present before) or is simply very poorly coded. The first of those is a tradeoff, the second is easily fixed if people just share their source code.
@sinister1: It's not that I don't agree with you - I do, in fact, and frequently quite vociferously - I just don't see what value you're adding to this conversation by proclaiming it. This thread is to discuss mockups of UI changes to WP8, not to complain about OS lockdown in WP8 and Microsoft's apparent unwillingness to implement some requested changes.
GoodDayToDie said:
@mscosmin: The conecpt the you trade performance for customization really isn't true. Yes, the phone could eke out a trivial amount of better performance by hardcoding its UI styles, but they don't do that. Things like accent colors, background colors, text styles, etc. are all stored in the registry; you don't have to modify a single line of system code to modify or create themes of your own, and they'll run just as fast. Other forms of customization, such as replacing some of the builtin libraries with custom ones, might be slower in certain circumstances, but only if the custom library either added new features (not just new customizations, but actual functionality that wasn't present before) or is simply very poorly coded. The first of those is a tradeoff, the second is easily fixed if people just share their source code.
@sinister1: It's not that I don't agree with you - I do, in fact, and frequently quite vociferously - I just don't see what value you're adding to this conversation by proclaiming it. This thread is to discuss mockups of UI changes to WP8, not to complain about OS lockdown in WP8 and Microsoft's apparent unwillingness to implement some requested changes.
Click to expand...
Click to collapse
And how many people do you think will be able to do proper customization? Windows Phone shouldn't be Android with squares instead of rounded edge widgets.
And solid colors like the ones WP uses will always be faster than a image on the background, or some sort of gradients or whatever they they propose to have around the phone.
How many people will do "proper" customization? As many as want to. Who are you to say what is or is not "proper" for how I want my phone to look?
Of all the things wrong with Android (the battery drain due to background services not exiting automatically, the more stuttery UI on all but the highest-end phones due to poorer optimization, the ability for malicious apps to send premium SMS completely invisibly to the user, etc.) you choose to pick on the customizations? Nobody is suggesting that we want Android with WP-like tiles; in that case we would have bought Android phones and installed one of the several Metro-style home screen customizations. On the other hand, if I want a Windows Phone with "rounded edge widgets" and am willing to put in the effort to develop them, I see no reason I shouldn't be allowed to.
WP uses the graphics processor for its UI. Those "solid colors" are just textures like any other. A gradient, an image, a partially translucent image... they're all the same to the GPU. The performance cost would be unmeasurably small.
GoodDayToDie said:
How many people will do "proper" customization? As many as want to. Who are you to say what is or is not "proper" for how I want my phone to look?
Of all the things wrong with Android (the battery drain due to background services not exiting automatically, the more stuttery UI on all but the highest-end phones due to poorer optimization, the ability for malicious apps to send premium SMS completely invisibly to the user, etc.) you choose to pick on the customizations? Nobody is suggesting that we want Android with WP-like tiles; in that case we would have bought Android phones and installed one of the several Metro-style home screen customizations. On the other hand, if I want a Windows Phone with "rounded edge widgets" and am willing to put in the effort to develop them, I see no reason I shouldn't be allowed to.
WP uses the graphics processor for its UI. Those "solid colors" are just textures like any other. A gradient, an image, a partially translucent image... they're all the same to the GPU. The performance cost would be unmeasurably small.
Click to expand...
Click to collapse
It's not about the GPU.
It's about the CPU. The more complex the image is, the bigger the size, the more time wasted for CPU to process it.
Add to that the fact it needs to purge/load from memory several times a day (in the case of a background wallpaper for startscreen), and the performance loss and battery drain is suddenly no longer unmeasurably small.
You're talking about a difference of microseconds. Not milliseconds, microseconds. Several times a day. And telling me that this is *not* below the noise threshold of any measurement system we have today, never mind human perception?!?
Also, consider people who use apps (with their own tiles, not just system tiles that are mostly blank and therefore rendered as mostly a solid color) on their lock screen. You know, the whole "meet <person>" advertising campaign Microsoft has been running for this OS? Those app tiles take just as long for the CPU to decode and send the texture to the GPU as the customized tiles we're talking about here...
Except, customized tiles aren't even the point. If you don't want to customize your tiles because saving a few millionths of a second per day - a saving which will never amount to a whole second over your entire lifetime, much less that of the phone - you don't have to. The rest of us want features; customization is merely one of those features. It gets a lot of discussion because:
A) It's an obvious feature to have. MS advertises personalization. People like being able to change how things look, be it their clothing or their front yard or their Windows background. For some reason, though, they can't change their Windows Phone background.
B) It's really, really simple to implement. I mean, there are tons of third party apps, some rather sophisticated, to do this. Microsoft doesn't have to jump through the crazy hoops that we did, and they have the documentation on how the OS works as well.
c) It really does not affect performance. There's no cost. Look at the custom themes and custom system tray icons and so forth on WP7, and try telling me with a straight face the percentage by which it impacts performance to use them.
GoodDayToDie said:
You're talking about a difference of microseconds. Not milliseconds, microseconds. Several times a day. And telling me that this is *not* below the noise threshold of any measurement system we have today, never mind human perception?!?
Also, consider people who use apps (with their own tiles, not just system tiles that are mostly blank and therefore rendered as mostly a solid color) on their lock screen. You know, the whole "meet <person>" advertising campaign Microsoft has been running for this OS? Those app tiles take just as long for the CPU to decode and send the texture to the GPU as the customized tiles we're talking about here...
Except, customized tiles aren't even the point. If you don't want to customize your tiles because saving a few millionths of a second per day - a saving which will never amount to a whole second over your entire lifetime, much less that of the phone - you don't have to. The rest of us want features; customization is merely one of those features. It gets a lot of discussion because:
A) It's an obvious feature to have. MS advertises personalization. People like being able to change how things look, be it their clothing or their front yard or their Windows background. For some reason, though, they can't change their Windows Phone background.
B) It's really, really simple to implement. I mean, there are tons of third party apps, some rather sophisticated, to do this. Microsoft doesn't have to jump through the crazy hoops that we did, and they have the documentation on how the OS works as well.
c) It really does not affect performance. There's no cost. Look at the custom themes and custom system tray icons and so forth on WP7, and try telling me with a straight face the percentage by which it impacts performance to use them.
Click to expand...
Click to collapse
Don't compare the WP7 theme mods and stuff like that which were made by hackers that knew what they were doing.
If Microsoft allows this officially on the marketplace, it will be flooded by poor apps.
Anyway, we seem to not be talking about the same thing. We should let it rest.
anyone who did the nougat update, can you post some screenshots? i am debating whether to do the upgrade or leave well enough alone. one post mentioned that th recent apps window was sub-standard. any other good and bad?
mark2573 said:
anyone who did the nougat update, can you post some screenshots? i am debating whether to do the upgrade or leave well enough alone. one post mentioned that th recent apps window was sub-standard. any other good and bad?
Click to expand...
Click to collapse
Yeah, I'm curious as well..i want to know if this update is going to be worth it
I did update to Nougat. My use is very limited but I find battery timing much improved and multi window is way better.
first of all - if you're satisfied with your device as it is don't update! It (unfortunately) doesn't get any better. They removed two important features - at least for me. There are no floating apps anymore - so if you want to use the small version of (for example) the google play music player while you're browsing you will have to use the splitscreen with dramatically decreased space for your browser left. So basically this means less convenience for you. The other thing is the (absolutely) useless "recent apps" view. In the past the whole screen was used by displaying the apps as tiles - now you only see them in the (for big tablet screens) useless card view.
Sorry - i always hate it when something really good just gets abandoned and replaced by something far inferior
I also found out, that manufacturers of 10"+ Tablets are encouraged to implement the native Android N freeform mode - so why has lenovo left this out of their update? I hope it gets back on the device with a later update.
P.S.: Android 7.0 CDD states that:
Device implementations with screen size xlarge SHOULD support freeform mode.
In the parlance of this CDD, there appear to be three levels of endorsement: SHOULD, STRONLY ENCOURAGED, and MUST. SHOULD is the weakest of the three, but it is still an endorsement.
NiffStipples said:
first of all - if you're satisfied with your device as it is don't update! It (unfortunately) doesn't get any better. They removed two important features - at least for me. There are no floating apps anymore - so if you want to use the small version of (for example) the google play music player while you're browsing you will have to use the splitscreen with dramatically decreased space for your browser left. So basically this means less convenience for you. The other thing is the (absolutely) useless "recent apps" view. In the past the whole screen was used by displaying the apps as tiles - now you only see them in the (for big tablet screens) useless card view.
Sorry - i always hate it when something really good just gets abandoned and replaced by something far inferior
I also found out, that manufacturers of 10"+ Tablets are encouraged to implement the native Android N freeform mode - so why has lenovo left this out of their update? I hope it gets back on the device with a later update.
P.S.: Android 7.0 CDD states that:
Device implementations with screen size xlarge SHOULD support freeform mode.
In the parlance of this CDD, there appear to be three levels of endorsement: SHOULD, STRONLY ENCOURAGED, and MUST. SHOULD is the weakest of the three, but it is still an endorsement.
Click to expand...
Click to collapse
Thanks buddy. I think I'm better off skipping this update.
Wrong, wrong, wrong
NiffStipples said:
first of all - if you're satisfied with your device as it is don't update! It (unfortunately) doesn't get any better. They removed two important features - at least for me. There are no floating apps anymore - so if you want to use the small version of (for example) the google play music player while you're browsing you will have to use the splitscreen with dramatically decreased space for your browser left. So basically this means less convenience for you. The other thing is the (absolutely) useless "recent apps" view. In the past the whole screen was used by displaying the apps as tiles - now you only see them in the (for big tablet screens) useless card view.
Sorry - i always hate it when something really good just gets abandoned and replaced by something far inferior
I also found out, that manufacturers of 10"+ Tablets are encouraged to implement the native Android N freeform mode - so why has lenovo left this out of their update? I hope it gets back on the device with a later update.
P.S.: Android 7.0 CDD states that:
Device implementations with screen size xlarge SHOULD support freeform mode.
In the parlance of this CDD, there appear to be three levels of endorsement: SHOULD, STRONLY ENCOURAGED, and MUST. SHOULD is the weakest of the three, but it is still an endorsement.
Click to expand...
Click to collapse
First of all, updates are really important for android devices in general. And especially for manufacturers like Lenovo which is known to let their product outdated pretty early. Personally, I'm impressed this time they updated to Android N even before schedule, and I'm hoping they continue releasing updates not to let this amazing product die.
As for the features you talk about:
1) floating windows in freeform is natively supported in android N and just need to be enabled in developer options (one of the last entries under App category). You can install "Taskbar" app to launch all of your apps in window mode by using the native method, and resize them as you like by dragging on the bottom-right corner (which previously was not possible).
2) It is true that Task manager with tiles view was a more clean way to switch between apps on this device, but the needing of double-pressing the TAB button when alt-tabbing beween apps, always made it uneffective and uncomfortable to me. Now ALT-TAB switch between apps just flawlessly as in a standard computer. Hence, i'm really happy with that.
3) I find overall performance have gotten slightly better with the recent N update: i can notice that in the UI and in games too! other users on other threads are talking about a slightly better battery performance too, so it seems like they optimized the hardware support somehow.
morrolinux said:
First of all, updates are really important for android devices in general. And especially for manufacturers like Lenovo which is known to let their product outdated pretty early. Personally, I'm impressed this time they updated to Android N even before schedule, and I'm hoping they continue releasing updates not to let this amazing product die.
As for the features you talk about:
1) floating windows in freeform is natively supported in android N and just need to be enabled in developer options (one of the last entries under App category). You can install "Taskbar" app to launch all of your apps in window mode by using the native method, and resize them as you like by dragging on the bottom-right corner (which previously was not possible).
2) It is true that Task manager with tiles view was a more clean way to switch between apps on this device, but the needing of double-pressing the TAB button when alt-tabbing beween apps, always made it uneffective and uncomfortable to me. Now ALT-TAB switch between apps just flawlessly as in a standard computer. Hence, i'm really happy with that.
3) I find overall performance have gotten slightly better with the recent N update: i can notice that in the UI and in games too! other users on other threads are talking about a slightly better battery performance too, so it seems like they optimized the hardware support somehow.
Click to expand...
Click to collapse
Thanks for the suggestion of taskbar - i've already tried it before and imho it's just not that convenient as a rom included solution. Beside the fact that you would have to use an unnecessary extra app for a native android function, it's not really intuitive in it's handling - but i have to admit, that every user will see that different depending on their needs My question is just why lenovo hasn't implemented this standard feature in a neat and handy way?
Speaking of different user needs/requirements - i've personally never used the Alt-Tab combi on my tab. In my daily use i use it most of the time in tent mode without the keyboard.
As to the performance - i didn't really noticed a change here. But in my opinion it was already really snappy before the update so maybe i can't rate that improvement. Maybe the animations between app switches got nicer but it's possible that i deactivated them before the update by myself - so nevermind
Guys, can somebody upload Noughat update otapackage?
I do not have a device but i need this to borrow graphic drivers.
After update to Nougat, battery drain in idle status doesn`t happen anymore. After a day idle, it takes only like 1-2% of battery. At least it is worth to me.