https://www.reddit.com/r/MotoX/comments/3k1xle/okay_after_quite_a_bit_of_effort_here_is_chop/
It isn't as sensitive as my 2014, feels like you're going to hurl the phone, but it does work.
Interesting. I can't get it to work using the procedure listed in the Reddit thread. You just copied the APK to the /system/priv-app/MotoDisplay directory and overwrote the existing APK in there?
dictionary said:
It isn't as sensitive as my 2014, feels like you're going to hurl the phone, but it does work.
Click to expand...
Click to collapse
I'd have to check the parameters/values it uses, but I didn't have the phone, so for the trigger I just set it to the same int value as the Moto 2014, like I did with 2013, I couldn't test the value for the Moto X play myself
nourez said:
Interesting. I can't get it to work using the procedure listed in the Reddit thread. You just copied the APK to the /system/priv-app/MotoDisplay directory and overwrote the existing APK in there?
Click to expand...
Click to collapse
Did you change the permissions to 6-4-4? (rw - r - r)
When you overwrite the file it tends to set it as (rw - rw - 0 ), also remember you need to reboot the phone as it's a system app that needs to be recompiled by ART
nourez said:
Interesting. I can't get it to work using the procedure listed in the Reddit thread. You just copied the APK to the /system/priv-app/MotoDisplay directory and overwrote the existing APK in there?
Click to expand...
Click to collapse
It is located in data/app/com.motorola.actions-2, and then you have to say the correct permissions.
mastarifla said:
I'd have to check the parameters/values it uses, but I didn't have the phone, so for the trigger I just set it to the same int value as the Moto 2014, like I did with 2013, I couldn't test the value for the Moto X play myself
Did you change the permissions to 6-4-4? (rw - r - r)
When you overwrite the file it tends to set it as (rw - rw - 0 ), also remember you need to reboot the phone as it's a system app that needs to be recompiled by ART
Click to expand...
Click to collapse
It was working last night, but not anymore. Going to try going back into the settings and seeing if that'll jog it
dictionary said:
It is located in data/app/com.motorola.actions-2, and then you have to say the correct permissions.
Click to expand...
Click to collapse
That's just the application data, not where the application actually resides, you would need to put the APK in the same location as I specified then reboot to get it to come up in Moto/Moto Actions
dictionary said:
It was working last night, but not anymore. Going to try going back into the settings and seeing if that'll jog it
Click to expand...
Click to collapse
If you only replaced it in the application data section, then you would still need to put it in the system/priv-app/MotoActions folder
mastarifla said:
That's just the application data, not where the application actually resides, you would need to put the APK in the same location as I specified then reboot to get it to come up in Moto/Moto Actions
If you only replaced it in the application data section, then you would still need to put it in the system/priv-app/MotoActions folder
Click to expand...
Click to collapse
That's what I'd figured, but we don't have that folder.
{
"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"
}
dictionary said:
That's what I'd figured, but we don't have that folder.
Click to expand...
Click to collapse
Oh wow that's kinda surreal, my bad!
In my phone, I have a MotoActions folder with an APK and the library files...
We would probably need to look at your apps in settings, so we can see what the Moto Actions package is called, then we could look in the system once we know the name
I have the folder, replaced the apk, and changed permission. Then restarted. I do not see the chop chop animation in moto actions and cannot trigger it myself by chopping the phone
My old moto voice command and moto assist locations carried over. Not sure if they were supposed to
EDIT: Reddit nourez solved it. By uninstalling Moto Actions on Google Play (it'll prompt you to just uninstall the updates, not the whole app) and rebooting the phone, Chop Chop appears Thanks for your great work
Sent from my XT1563 using Tapatalk
Strange that I don't have it. Does it work reliably for you though? For me it's extremely spotty
dictionary said:
Strange that I don't have it. Does it work reliably for you though? For me it's extremely spotty
Click to expand...
Click to collapse
It works 100% of the time. But I'm not just doing two chops. I'm chopping continuously until the torch turns on.
Just did it three times
All three instances of turning on took 4 chops (4 up and down)
All three instances of turning it off took 3 chops (3 up and down )
So while it may not be the two chops as advertised, it consistently works for me
EDIT: So I turned it on and off about 10 more times and towards the end it was getting worse and worse. Strange that it was working so reliably to begin with
EDIT2: The chop chop works great within its Moto Action page though. I can trigger it with only 2 chops
Sent from my XT1563 using Tapatalk
pyr0sphere said:
It works 100% of the time. But I'm not just doing two chops. I'm chopping continuously until the torch turns on.
Just did it three times
All three instances of turning on took 4 chops (4 up and down)
All three instances of turning it off took 3 chops (3 up and down )
So while it may not be the two chops as advertised, it consistently works for me
EDIT: So I turned it on and off about 10 more times and towards the end it was getting worse and worse. Strange that it was working so reliably to begin with
EDIT2: The chop chop works great within its Moto Action page though. I can trigger it with only 2 chops
Sent from my XT1563 using Tapatalk
Click to expand...
Click to collapse
That's basically what I was saying. It had worked great last night. Went to bed, woke up, and tried it again at some point during the day, and just wouldn't work. I could finally get it on, but it wouldn't go off. Looked like I was chopping onions with a fury, and still nothing. Maybe this is why Moto disabled it on launch.
dictionary said:
That's basically what I was saying. It had worked great last night. Went to bed, woke up, and tried it again at some point during the day, and just wouldn't work. I could finally get it on, but it wouldn't go off. Looked like I was chopping onions with a fury, and still nothing. Maybe this is why Moto disabled it on launch.
Click to expand...
Click to collapse
Similar experience. I could eventually get it on after chopping furiously but could never turn it off.
Did you try chopping in the gesture page in moto action? Worked great for me there
Sent from my XT1563 using Tapatalk
pyr0sphere said:
Similar experience. I could eventually get it on after chopping furiously but could never turn it off.
Did you try chopping in the gesture page in moto action? Worked great for me there
Sent from my XT1563 using Tapatalk
Click to expand...
Click to collapse
After it stopped working, I'd gone back there thinking enabling and disabling would bring it back. Sadly, that's when I managed to get it back on, by chopping like mad, but still no off. I've just disabled it. Not as simple as the camera twist
Haven't tried it on mine. Motorola said they didnt include it due to the lack of reliability. Maybe because it doesn't have a gyroscope?
I also find the camera action to be hit and miss and best. When you try it in the moto action app it seems to work well, but doesn't often work for me when the screen is off.
ac4tw said:
Haven't tried it on mine. Motorola said they didnt include it due to the lack of reliability. Maybe because it doesn't have a gyroscope?
I also find the camera action to be hit and miss and best. When you try it in the moto action app it seems to work well, but doesn't often work for me when the screen is off.
Click to expand...
Click to collapse
Now that you mention it, you're right. That's pretty fuddy too. Meh. Just makes me love the 2014 more, and consider getting the Style.
Works great, have to firmly hold the phone and chop twice very solidly to turn on/off the torch.
Had to uninstall via Play Store after copying in the apk and setting permissions. Looked to have hung uninstalling, I gave it 5 mins then rebooted, worked fine then
Sent from my Nexus 9 using XDA Premium HD app
I was looking more into this yesterday, I downloaded the system image of the canadian version of the Moto X Play
The version of MotoActions that came pre-installed on the Moto X Play was 1.11.26, which is a few versions behind the current Play Store version I modified 1.11.33, so I am not sure why you would have to uninstall the previous version unless it maybe had something to do with the previous app settings preventing it from loading the new version?
Digging through each of the APK's I noticed that they specifically check to see if it's a Moto X Play or Ghost device before continuing, as well as a Lolipop version check and a device check for initial triggering, basically for this step of the check, I changed the check to be another device that doesn't have any underlying code for any Moto Actions (as you can only use Motorola codenames)
Code:
public static boolean B(Context paramContext)
{
if ((b.da()) || (b.cZ()));
class b
public static boolean cZ()
{
return n("lux");
}
public static boolean da()
{
return (n("ghost")) || (n("obake"));
}
Here is the some interesting code that seems to differentiate between devices, I was thinking that this comes into play with regards to enabling/disabling the chopchop, so I just set both the Moto X Play and Moto X 2013 to use the Moto X 2014's value (where cV() == 2014 Moto X, cU() == Moto MAXX)
Code:
while (((b.cV()) && (i < 83)) || ((b.cU()) && (i < 89)));
return ChopRecognizerFactory.s(paramContext);
I'll probably have to dig a bit deeper in the factory and see what exactly is triggering each device (the parameters that is), but it's a bit difficult as each APK decompiles with different obfuscated methods/classes, so matching them all back up takes a bit of time...
The reason why you see that it works better in the tutorial is because it goes through different methods once it determines that you are in the tutorial, I can attempt to trick it so that way it always thinks its in the tutorial, but this will take quite a bit of smali code re-arranging, as well as analyzing the chop chop metrics so it doesn't throw any exceptions and errors, so don't expect a new version instantaneously, as I have a job the comes first
mastarifla said:
I was looking more into this yesterday, I downloaded the system image of the canadian version of the Moto X Play
The version of MotoActions that came pre-installed on the Moto X Play was 1.11.26, which is a few versions behind the current Play Store version I modified 1.11.33, so I am not sure why you would have to uninstall the previous version unless it maybe had something to do with the previous app settings preventing it from loading the new version?
Digging through each of the APK's I noticed that they specifically check to see if it's a Moto X Play or Ghost device before continuing, as well as a Lolipop version check and a device check for initial triggering, basically for this step of the check, I changed the check to be another device that doesn't have any underlying code for any Moto Actions (as you can only use Motorola codenames)
Code:
public static boolean B(Context paramContext)
{
if ((b.da()) || (b.cZ()));
class b
public static boolean cZ()
{
return n("lux");
}
public static boolean da()
{
return (n("ghost")) || (n("obake"));
}
Here is the some interesting code that seems to differentiate between devices, I was thinking that this comes into play with regards to enabling/disabling the chopchop, so I just set both the Moto X Play and Moto X 2013 to use the Moto X 2014's value (where cV() == 2014 Moto X, cU() == Moto MAXX)
Code:
while (((b.cV()) && (i < 83)) || ((b.cU()) && (i < 89)));
return ChopRecognizerFactory.s(paramContext);
I'll probably have to dig a bit deeper in the factory and see what exactly is triggering each device (the parameters that is), but it's a bit difficult as each APK decompiles with different obfuscated methods/classes, so matching them all back up takes a bit of time...
The reason why you see that it works better in the tutorial is because it goes through different methods once it determines that you are in the tutorial, I can attempt to trick it so that way it always thinks its in the tutorial, but this will take quite a bit of smali code re-arranging, as well as analyzing the chop chop metrics so it doesn't throw any exceptions and errors, so don't expect a new version instantaneously, as I have a job the comes first [emoji14]
Click to expand...
Click to collapse
That would be absolutely amazing. Thank you so much for taking the time to do all of this
Sent from my XT1563 using Tapatalk
pyr0sphere said:
That would be absolutely amazing. Thank you so much for taking the time to do all of this
Sent from my XT1563 using Tapatalk
Click to expand...
Click to collapse
Edit: Took a look at the jar, made a few mistakes, I guess it may need to have those parameters then :/
Related
In an effort to optimize my battery life, I've come across a few different location related settings, and I'm not sure what the differences are between them, specifically in relation to how Google Now functions. The different settings are:
(1) Main Settings->Location Access->Access to My Location
I'm pretty sure this one is the "Master" setting. Toggling this switch off will disable all location services. However, if you leave this one on, you can independently enable/disable the following settings:
(2) Maps->Settings->Location Settings->Location Reporting (under Background Location Reporting)
(3) Maps->Settings->Location Settings->Report From This Device (under Background Location Reporting)
(4) Maps->Settings->Location Settings->Latitude Location Sharing (these options are clearly specifically for Latitude, so no confusion here)
(5) Maps->Settings->Location Settings->Location History
I guess I'm most confused about settings (2), (3), and (5). What is the difference between them and what effects do each of them have on Google Now? Anyone know?
EDIT: Note that I've had settings (1) and (2) enabled and (3) through (5) disabled for a few days now, and I've noticed significant battery savings, while still keeping some level of functionality via Google's Location Services.
Very good question. I've always wondered what I can turn off and still take full benefit of Google Now's learning, etc.
So far, with items (2)-(5) disabled, Google Now is still giving me location based pop-ups, which is good. I've gotten an ETA/driving directions card and an updated weather card based on my location. Also, the maps and network services wakelocks are much better. I still don't know what these items are actually good for though.
What OS ya'll using? i am on SKY Jelly Bean 4.1.2 and only see the 1st location as a place to change. i dont see the others.
shane.kelly55 said:
What OS ya'll using? i am on SKY Jelly Bean 4.1.2 and only see the 1st location as a place to change. i dont see the others.
Click to expand...
Click to collapse
I'm on stock 4.2.1
Never mind i'm a dummy. I found it.
I have 1 and 2 enabled and the rest disabled.
What about under the main settings: Wifi and Mobile network location. Think this might help unchecked?
I do like to use Facebook "Check In' function though....
I still don't understand what the hell some of these settings do or what services they have implications for. Damnit Google, always making things confusing.
I'm pretty sure you need #5 enabled if you want Now to calculate how much you've walked, ran.. biked for the month.
ellesshoo said:
I still don't understand what the hell some of these settings do or what services they have implications for. Damnit Google, always making things confusing.
Click to expand...
Click to collapse
Yup. That's exactly why I started this thread. It's very unclear.
Sent from my Nexus 4 using xda premium
The only one you need for Google Now to function is "WiFi and mobile network location".
Sent from my Nexus 4 using Tapatalk 2
I have a Verizon GS3 on stock leak JB and was experiencing this problem. I followed the instructions in the OP and no longer have ridiculous wakelocks from signalcollector.scannerthread. Anyway, thanks OP!
nyijedi said:
In an effort to optimize my battery life, I've come across a few different location related settings, and I'm not sure what the differences are between them, specifically in relation to how Google Now functions. The different settings are:
(1) Main Settings->Location Access->Access to My Location
I'm pretty sure this one is the "Master" setting. Toggling this switch off will disable all location services. However, if you leave this one on, you can independently enable/disable the following settings:
(2) Maps->Settings->Location Settings->Location Reporting (under Background Location Reporting)
(3) Maps->Settings->Location Settings->Report From This Device (under Background Location Reporting)
(4) Maps->Settings->Location Settings->Latitude Location Sharing (these options are clearly specifically for Latitude, so no confusion here)
(5) Maps->Settings->Location Settings->Location History
I guess I'm most confused about settings (2), (3), and (5). What is the difference between them and what effects do each of them have on Google Now? Anyone know?
EDIT: Note that I've had settings (1) and (2) enabled and (3) through (5) disabled for a few days now, and I've noticed significant battery savings, while still keeping some level of functionality via Google's Location Services.
Click to expand...
Click to collapse
How do you get to settings 2-5?
That are options in the Google Maps app.
Also worth noting.. I disabled Google now yesterday and got these battery times:
{
"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"
}
View attachment 1541577
For me I just keep data turned off and quickly flip it on in the pull down widget menu when needed. My phone last days on a single charge doing it this way. And the data turns on in about 5 seconds when needed.
Sent from my Nexus 4 using xda app-developers app
Here is my battery stats
Sent from my Nexus 4 using xda app-developers app
nyijedi said:
So far, with items (2)-(5) disabled, Google Now is still giving me location based pop-ups, which is good. I've gotten an ETA/driving directions card and an updated weather card based on my location. Also, the maps and network services wakelocks are much better. I still don't know what these items are actually good for though.
Click to expand...
Click to collapse
3 weeks now on my S3 and no major battery problems but trying to maximize by analyzing using BetterBatteryStats. All seems well except the Google Maps wakelocks when phone isn't being used. Which is odd. Found a thread that pointed me back here. It makes sense that Google Now is just wanting to see where you are. Too bad there isn't a setting to change the interval it which it checks.
Anyway, I disable 2-5 also as the user did above, but now when I go to my Google Now page, it gives me a card "Improve Suggestions - To get suggestions based on your location history, such as traffic alerts, Enable location history. So I would be surprised you still get ETA/driving directions card with that setting turned off?
I guess I will just see how much of a difference it make in both battery and functionality with most the location stuff turned off (2-5).
-- additional --
You're right. I just clicked 'additional cards' and got he current commute time to my 'work' location and local weather. The thing I think disabling this history may do though is from now on, if I started driving back and forth a lot to a location, it's not going to ask me to identify that location and show me ETA, etc. However, I actually work from home, so I just set my work location to my most common destination (downtown.) And I'm used to looking up directions on Maps and just keeping the 'show traffic' option on. So, so far, I don't see any big downside to disabling most of these settings in maps. But I've yet to see if it makes a diff on battery use.
Phone's been sitting next to me, unplugged for about 5 hours and I barely have used it and it is still at 92% Surfaceflinger is #1 process, then Media wakelock, then the only app I've used, then maps is way down the list at #8. So maybe I didn't need to disable those settings in the first place. LOL. It was just when I was using GSAM instead of BBS, the higher level view of the processes taking up the apps, I always though it odd Maps was always in the top 4 when I wasn't using the phone for anything. I guess if total battery use is reasonable/expected, then doesn't matter what is the top processes using it are.
---------- Post added at 02:41 PM ---------- Previous post was at 02:16 PM ----------
You one thing, there still isn't any definitive guide that I've found that tells you the side effects that the most common apps will have (what functions you gain/lose) by turning on/off these various settings. That would be really informative. There are bits and pieces here and elsewhere but it would be a Godsend if someone published a sticky or something that tells how all these settings specifically effect Maps, Google Now, Facebook, etc.
I also want to know how these settings effect Google Now. I got 4.1.2 on my Note 2 the other day and noticed maps using the most battery when I would look in settings.
Manly the setting "Report from this Device" it reads "automatically report you're location from this device"
Does that effect Google Now? It seems with that turned off, maps isn't using as much battery at all. I just want to know how it will effect Google Now and will it effect anything else?
Sent from my SGH-T889 using Tapatalk 2
Now that XXBLL7 Android 4.1.2 Official Firmware is available for our cameras it would be interesting to see what changes it brings. As usual it's a hunt and track down for changes to upgrades but maybe we can compile a list?
So far I noticed there is now 4 new scenes in SMART mode...
"FOOD" - Take pictures that emphasise the vivid colours of food
"DAWN" - Take pictures that emphasise the dawn sky by making the blue more intense
"SNOW" - Take pictures that emphasise the brightness of snow by making the white more intense
"PARTY/INDOOR" -Take pictures of parties or other indoor activities without blurring
Also:
You can set an option to not automatically fire up the camera when you power on - very pleased by this one!
An icon has appeared on the notification bar - a battery with a recycle sign - to tell you that you have enabled 'Smart Network' mode (turns off network functions when screen is off)
Updated versions of Samsung built in apps naturally
Still looking...
Sadly the storage card dialog still pops up on a cold boot
Remote Viewfinder still not working
apprentice said:
Now that XXBLL7 Android 4.1.2 Official Firmware is available for our cameras it would be interesting to see what changes it brings. As usual it's a hunt and track down for changes to upgrades but maybe we can compile a list?
So far I noticed there is now 2 new scenes in SMART mode... "FOOD" - Take pictures that emphasise the vivid colours of food
and "DAWN" - Take pictures that emphasise the dawn sky by making the blue more intense
An icon has appeared on the notification bar - a battery with a recycle sign
Updated versions of Samsung built in apps
Still looking...
Sadly the storage card dialog still pops up on a cold boot
Remote Viewfinder still not working
Click to expand...
Click to collapse
I want to flash this firmware, but can it be rooted?
Since I've rooted my Camera with Exynos Abuse, it says it is non-standard and refuses to tell me about any updates. Do I need to back out everything before it will notice the update? Does the abuse hole still exist after the update?
Claghorn said:
Since I've rooted my Camera with Exynos Abuse, it says it is non-standard and refuses to tell me about any updates. Do I need to back out everything before it will notice the update? Does the abuse hole still exist after the update?
Click to expand...
Click to collapse
Check in settings-about device-Status If "Device Status" says "Custom" then you will not receive OTA updates. Mine says "Custom" as I rooted with odin. I don't know if Exynos Abuse changes the device status.
Is French language included in this firmware ?
Thx
robb13 said:
I want to flash this firmware, but can it be rooted?
Click to expand...
Click to collapse
I've just tried to, straight after flashing "without wipe" and the Exynoss Exploit APK from Chainfire fails to Root, but I'm going to do a wipe and see if it's a problem with some residual files or something.
Update:
With ExynosAbuse 1.40, although it detects the device as Exploitable, it's unable to Root the device.
Can't root with Exynos Abuse 1.40... But Auto-Root is working fine !
Could you check amount of ram ? I have now 755mb, and before i remember (or i'm drunk) that i had 768mb
Strange...
I downloaded from Samfirmware and installed through ODIN although I lost root I was able to re-root successfully again using chainfire's method.
Sent from my Samsung Galaxy Note II using Tapatalk 2
there are a few other settings in smart mode which are snow, home party or something, there is also a weather app that has been installed
There's a setting in the settings menu called power that I didn't notice before, that allows you to choose when the device shuts itself down. Another thing I've found is that you don't have to keep enabling voice control in the camera app every time you close and open it now.
And just the general responsiveness seems better in the camera app too.
Sent from my GT-N7100 using Tapatalk 2
Can someone check the ram available please ? 755mb max ?
luminouche said:
Can someone check the ram available please ? 755mb max ?
Click to expand...
Click to collapse
Isn't that dependant on what apps you have installed and individual set ups?
apprentice said:
Isn't that dependant on what apps you have installed and individual set ups?
Click to expand...
Click to collapse
He is talking about the max available RAM on the device that is usable.
I don't have the galaxy camera, but the RAM amount can indeed change (The S3 had 7xxMB with ICS and now has 8XXMB in JB)
Skander1998 said:
He is talking about the max available RAM on the device that is usable.
I don't have the galaxy camera, but the RAM amount can indeed change (The S3 had 7xxMB with ICS and now has 8XXMB in JB)
Click to expand...
Click to collapse
Ah, OK. In that case the total I have is 755Mb since the update.
Hope that helps.
Yeah, the value you have when you long press home (Samsung task killer).
In 4.1.1 it seems to me that i had 768 instead of 755.
After Odin update, i also had another 'camera update' during few minutes, on the 1st boot (specific to Galaxy Camera ?)
luminouche said:
Yeah, the value you have when you long press home (Samsung task killer).
In 4.1.1 it seems to me that i had 768 instead of 755.
After Odin update, i also had another 'camera update' during few minutes, on the 1st boot (specific to Galaxy Camera ?)
Click to expand...
Click to collapse
I have 780MB with the ATT stock rom. I will update later to 4.1.2 and see if it changes.
apprentice said:
You can set an option to not automatically fire up the camera when you power on - very pleased by this one!
An icon has appeared on the notification bar - a battery with a recycle sign - to tell you that you have enabled 'Smart Network' mode (turns off network functions when screen is off)
Updated versions of Samsung built in apps naturally
Click to expand...
Click to collapse
I update the rom and found new smart mode like you say, but I don't found the option for disable camra on boot and don't have the battery sign i notification bar.
Can you tell me where you found the option for disable the camera ?
Thank you
David
New Triangle Away
Just to inform the community, I've been helping Chainfire over the past day or so, to get Triangle Away working for our Cameras
And he's done it!
Pic of my camera Before:
{
"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"
}
Pic of download mode After:
He is currently tidying up a few bits but, the next release to hit the Play Store will support the EK-GC100
RavenY2K3 said:
Just to inform the community, I've been helping Chainfire over the past day or so, to get Triangle Away working for our Cameras
And he's done it!
Click to expand...
Click to collapse
Ye !!
Thank you to you RawevnYéK3 and ChainFire, this is great
About my question for how disable camera when start the Camera and where is the icon about the mode "Smart Network" in notification bar, I found the icon, in fact I expect an icon like Wifi, BT, etc, but it's only a small one inform you "Smart Network" are use when you activate it.
But I still don't found where disablecamera on boot
djudenne said:
Ye !!
Thank you to you RawevnYéK3 and ChainFire, this is great
About my question for how disable camera when start the Camera and where is the icon about the mode "Smart Network" in notification bar, I found the icon, in fact I expect an icon like Wifi, BT, etc, but it's only a small one inform you "Smart Network" are use when you activate it.
But I still don't found where disablecamera on boot
Click to expand...
Click to collapse
I've currently set the camera up with a lockscreen so it doesn't extend the lens when I hit the power button, but also, if the last thing the camera had open was the home screen, it opens back up in the home screen when I unlock the device.
Sent from my EK-GC100 using Tapatalk 2
Better Keyguard
The app is for People who dont use any security-lockscreen (like Pin, Pattern or Face unlock) and just like the fastest way to reach the homescreen after turning the device on. Many Roms allow to disable the key guard completly. So u see the homescreen right after turning on the device. But this way, unwanted misuse can happen, by accidentelly wakeing up the phone, while carrying it in your pocket.
Because of this and because iam not using a MIUI-Rom anymore (which had the very same feature), i set up a Tasker profile, which enables the proximity sensor for 1 sec, every time the display is turned on. If the sensor is not covered in that moment, nothing further will happen, if it is, the display will be turned off right away.
Later I decided to export this Profile as app via App Factory (Tasker Plugin), because I thought others would like such a feature too.
The app passed tests on my Galaxy SII (AOSP: Android 4.2.2) and on a Xperia Z (Stock Rom: Android 4.1.2) from a buddy of mine.
After Installation
1. Of course, to turn the screen off, u need to enable BK as device-admin.
2. To test: Press power button to turn off the display, keep the proximity sensor covered (usually located in right or left upper corner of the phone) while pressing the power button again to turn the display on. If its turned off again within 1 second, the test can be considered passed.
3. Note: On the Xperia Z (and some other devices), i noticed that any Lockscreen/Keyguard has to be disabled to make the App work. (It seems that the proxy sensor is not working in lockscreen)
Since Iam no programmer and the fact, that this is a Tasker-Project, my abilities for improvements or Bugfixing are very limited. Maybe some1 will pickup the idea and write a REAL app of this kind. Ofc only if the Chinese have not yet patented their MIUI-feature. :laugh:
I uploaded the Tasker-Project-Files as well.
Just would like to know ur thoughts about this.
Changelog:
1.0 - First release
1.1 - Added a UI allowing to adjust some options (show/hide notification, try to disable built in keyguard, launch on boot: Always, Never, Remember last state)
- Toggling the state shows now a tiny flash message
1.2 - Added option to show a warning message before display goes off. If the sensor is uncovered quick enough, display will stay on and the warning message will be dismissed.
(disadvantages: Tasker provides only 2 relevant massage types for that purpose. One can be dismissed by the back key, which is bad for devices with capacitive buttons, since these buttons are not locked while the warning message is shown. So I decided to go with the second type, which is not dismissable by the back key, but also not overlapping the status bar, so it is still expandable).
2nd: Somehow this version is not working along with lockscreen at all. So, if you want to see a warning message before screen goes off, u need to disable any kind of lockscreen (even normal swipe).
If you want to use it along with a lockscreen, you need to try it with Bk 1.1 or 1.0
1.3 - Added an option to show the warning message over lockscreen (only if the app is working in lockscreen at all and u need to tell it, if u are using a lockscreen or not)
Removed because of no further advantage.
1.4 - Slightly reworked UI with new Szene-elements from latest Tasker version (Checkbox and Drop-down menu). This version equals 1.1 in functionality, since i thought the app was inflated too much with stuff that actually didnt work correctly. Furthermore i also used the latest version of App-Factory to create the app, since "Pent" (the dev of Tasker) released at least two updates for Tasker and the App-Factory plugin since i uploaded BK_1.2. So this one might work more reliable now.
Here the UI
Field tests revealed that a enabled keyguard (normal swipe lockscreen or whatever) prevents Bk from working properly in some cases. If Your Rom doesnt allow to disable the key guard, try the new disable built in keyguard option. If your Rom does allow it, use the native setting to disable the lockscreen rather than Bk ones.
Reuploaded the first release, becuase the file had a Tasker created filename (Better_keyguard.4.apk) and did not reflect the actual version number.
Best regards
Chillmann
OK 9 views so far. But i would realy appreciate a response of any kind
No matter if its "... well done, working as intended" or "... fu, its chewing up all my battery"
Please, just give a response!
Thx in advance
Chillmann
i tried and test it "DO NOTHING nothing at all" jst stay @ notification saying BK is active ( i have activated system administration) probably describing how it work and what it does will be more useful some screenshot.
I am on Slimbean 4.2.2 build 4
Samsung galaxy s2 GT-I9100
Hi aryan1312,
many thx for responding!
I rewrote the introduction to better underline the app's purpose and added a "After installation" annotation with instructions of how to test the functionality.
Since the app got no menu, there would be nothing to show in a screenshot. Ill try to put a youtube video online soon, that will show what it does.
i tried and test it "DO NOTHING nothing at all" jst stay @ notification saying BK is active ( i have activated system administration) probably
Click to expand...
Click to collapse
I hope u just didnt know how to test it, because u got the very same set up as i do (sgs2 on slim beam 4.2.2+dori9.14). Would be quite strange, if its not working even with same hardware + software. On my phone, i allways notice a weak red glow coming from the proximity sensor, if its active. (during a call or if a sensor related Tasker-profile is running) Maybe u watch out for that glow right after turning on the display. That would indicate the app's functionality too.
Best regards
Chillmann
Chillmann said:
Hi aryan1312,
many thx for responding!
I rewrote the introduction to better underline the app's purpose and added a "After installation" annotation with instructions of how to test the functionality.
Since the app got no menu, there would be nothing to show in a screenshot. Ill try to put a youtube video online soon, that will show what it does.
I hope u just didnt know how to test it, because u got the very same set up as i do (sgs2 on slim beam 4.2.2+dori9.14). Would be quite strange, if its not working even with same hardware + software. On my phone, i allways notice a weak red glow coming from the proximity sensor, if its active. (during a call or if a sensor related Tasker-profile is running) Maybe u watch out for that glow right after turning on the display. That would indicate the app's functionality too.
Best regards
Chillmann
Click to expand...
Click to collapse
Thanks for giving the description more accurately. Now i have better understanding of how it work. previously i was using slide2wake (dori function) i think that y it is not workin, will try with power button now
Edit: Work absolutely fine, even with slide2wake and PIN lock
don't think it will affect much battery performance since it activate proximity sensor for jst 1 sec
Great work
New version uploaded, check OP
Greets
Chillmann
What if I have no proximity sensor? Can it work? Nah, just kidding it's a nice app but I'd really would like it if it's notification could be swiped away and if there would be a warning like in the miui because now it's more like miui idea not like a miui style. I'm still going to use this app and tell my friend which also has similar problem about this app
Sent from my R800i using xda premium
After I've watched a movie it suddenly stopped working... I've even relaunched it and nothing... I guess that reboot will help me.
Sent from my R800i using xda premium
Nope, it didn't. Actually it's not working at all now...
Sent from my R800i using xda premium
Hi olokos,
thx for testing!
olokos said:
What if I have no proximity sensor? Can it work? Nah, just kidding it's a nice app but I'd really would like it if it's notification could be swiped away and if there would be a warning like in the miui because now it's more like miui idea not like a miui style. I'm still going to use this app and tell my friend which also has similar problem about this app
Sent from my R800i using xda premium
Click to expand...
Click to collapse
I added a option to enable a warning message before screen goes off. To the non permanent notification, sorry but I can't see the advantage. Why not disable the notification completely?
olokos said:
After I've watched a movie it suddenly stopped working... I've even relaunched it and nothing... I guess that reboot will help me.
Sent from my R800i using xda premium
Click to expand...
Click to collapse
olokos said:
Nope, it didn't. Actually it's not working at all now...
Sent from my R800i using xda premium
Click to expand...
Click to collapse
uhm, thats really strange. At 1st I thought it was androids memory management who threw Bk out of the cache. But even not working after reboot is bad. As stated in the OP, iam no programmer, so I have neither a clue why it stopped working, nor I know how to fix it
I think it has something to do with the way, Tasker exports profiles into apps.
U can try to delete app data (if not already removed) to get it working again. But if it keeps stopping to work, deleting data is no real solution.
Iam sorry I did no long time testing prior to posting here. During quick tests I recognized, that Bk wouldn't show the option menu by pressing the app icon after Tasker performed one of its tasks. Removing Bk from recents app list did fix that. But this is completely different to ur experience.
I hope it is a very rarely occurring bug or related only to few devices. Otherwise the app would be unusable. :crying:
Hopefully
Chillmann
After disabling swipe unlock in JB it is working but when JB screen lock is working normally, your app is not working... I'm not using any other key lock (pattern, pin) or anything. I just have to swipe to unlock. If you are going to fix it then I promise I'll spread the word
Sent from outer space using RPG
olokos said:
After disabling swipe unlock in JB it is working but when JB screen lock is working normally, your app is not working... I'm not using any other key lock (pattern, pin) or anything. I just have to swipe to unlock. If you are going to fix it then I promise I'll spread the word
Sent from outer space using RPG
Click to expand...
Click to collapse
Hi olokos,
well, in order to make a message appear over the lockscreen, i had to use the 3rd message type, which tasker provides. I never thought it would be relevent, since it doesnt block any input. Unfortunetly, that makes this feature to an eye candy without further purpose.
As I stated in the "After installation" paragraph, i found out that some roms prevent the proximity sensor from working in lockscreen. After updating my own decive to slim bean 4.2.2 build5, Bk stopped working in lockscreen too.
In order to use the warning message over lockscreen, u need to test the functionality without the "show warning" option. If it works and ur display is turned off as intended, u can enable "show warning". But u also have to tell the app wether a lockscreen is in use or not.
hope its fitting ur desire a little more now
Edit: found out that it wasn't my rom preventing the sensor from working in lockscreen, but its not working since Bk 1.2
So, if you want to see a warning message before screen goes off, u need to disable any kind of lockscreen (even normal swipe).
If you want to use it along with a lockscreen, you need to use Bk 1.1
Sorry i couldn't turn it into real MUI style :/
Chillmann
Hey bro i have shared ur post link to slimbean post wish u dont have issue with it ... if any problem plz inform i wil remove the link :fingers-crossed:
OP updated
perfect one
Working like a charm on nexus 4 stock ROM 4.4.2 ART runtime
Works on my galaxy s4 stock rom 4.2.2. Works only without a lock screen though. Using v1.4 of better keyguard. The UI is in a mess refer to screenshot.
{
"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"
}
THX for testing! Well ur S4 got some more Pixel than my old S2 ^^
Ill try to rework the UI next time I can get my hands on a high resolution device in order to test different settings for UI creation.
Greets
Chillmann
Sent from my GT-I9100 using XDA Free mobile app
Chillmann said:
Better Keyguard
The app is for People who dont use any security-lockscreen (like Pin, Pattern or Face unlock) and just like the fastest way to reach the homescreen after turning the device on. Many Roms allow to disable the key guard completly. So u see the homescreen right after turning on the device. But this way, unwanted misuse can happen, by accidentelly wakeing up the phone, while carrying it in your pocket.
Because of this and because iam not using a MIUI-Rom anymore (which had the very same feature), i set up a Tasker profile, which enables the proximity sensor for 1 sec, every time the display is turned on. If the sensor is not covered in that moment, nothing further will happen, if it is, the display will be turned off right away.
Later I decided to export this Profile as app via App Factory (Tasker Plugin), because I thought others would like such a feature too.
The app passed tests on my Galaxy SII (AOSP: Android 4.2.2) and on a Xperia Z (Stock Rom: Android 4.1.2) from a buddy of mine.
After Installation
1. Of course, to turn the screen off, u need to enable BK as device-admin.
2. To test: Press power button to turn off the display, keep the proximity sensor covered (usually located in right or left upper corner of the phone) while pressing the power button again to turn the display on. If its turned off again within 1 second, the test can be considered passed.
3. Note: On the Xperia Z (and some other devices), i noticed that any Lockscreen/Keyguard has to be disabled to make the App work. (It seems that the proxy sensor is not working in lockscreen)
Since Iam no programmer and the fact, that this is a Tasker-Project, my abilities for improvements or Bugfixing are very limited. Maybe some1 will pickup the idea and write a REAL app of this kind. Ofc only if the Chinese have not yet patented their MIUI-feature. :laugh:
I uploaded the Tasker-Project-Files as well.
Just would like to know ur thoughts about this.
Changelog:
1.0 - First release
1.1 - Added a UI allowing to adjust some options (show/hide notification, try to disable built in keyguard, launch on boot: Always, Never, Remember last state)
- Toggling the state shows now a tiny flash message
1.2 - Added option to show a warning message before display goes off. If the sensor is uncovered quick enough, display will stay on and the warning message will be dismissed.
(disadvantages: Tasker provides only 2 relevant massage types for that purpose. One can be dismissed by the back key, which is bad for devices with capacitive buttons, since these buttons are not locked while the warning message is shown. So I decided to go with the second type, which is not dismissable by the back key, but also not overlapping the status bar, so it is still expandable).
2nd: Somehow this version is not working along with lockscreen at all. So, if you want to see a warning message before screen goes off, u need to disable any kind of lockscreen (even normal swipe).
If you want to use it along with a lockscreen, you need to try it with Bk 1.1 or 1.0
1.3 - Added an option to show the warning message over lockscreen (only if the app is working in lockscreen at all and u need to tell it, if u are using a lockscreen or not)
Removed because of no further advantage.
1.4 - Slightly reworked UI with new Szene-elements from latest Tasker version (Checkbox and Drop-down menu). This version equals 1.1 in functionality, since i thought the app was inflated too much with stuff that actually didnt work correctly. Furthermore i also used the latest version of App-Factory to create the app, since "Pent" (the dev of Tasker) released at least two updates for Tasker and the App-Factory plugin since i uploaded BK_1.2. So this one might work more reliable now.
Here the UI
Field tests revealed that a enabled keyguard (normal swipe lockscreen or whatever) prevents Bk from working properly in some cases. If Your Rom doesnt allow to disable the key guard, try the new disable built in keyguard option. If your Rom does allow it, use the native setting to disable the lockscreen rather than Bk ones.
Reuploaded the first release, becuase the file had a Tasker created filename (Better_keyguard.4.apk) and did not reflect the actual version number.
Best regards
Chillmann
Click to expand...
Click to collapse
Hi,
I just find your app. I really need n app like this, but it doesn't want to work for mi ( for test i cover the sensors and try to use the screen and i can). Is it compatible with kitkat based roms? I have a N4. Can you suggest another test method if mine is useless?
Just to let you know, I'vee take your idea and modified it.
SOme newer devices with tap-on screens can be triggered in your pocket. This app works, but it doesn't work if you have a standard slide lock screen - so I modified tasker to check for screen unlock andd proximity, rather than screen on and proximity... then if your device turns on in your pocket and then tries to unlock, it will go off again - this works around it not working with a lock screen.
Good idea checking for lock screen :thumbup:
Did you share your work somewhere?
Best regards, Chillmann
Sent from my GT-I9100 using XDA Free mobile app
Any questions, tips, etc? Let's talk here.
Sent from my SM-N900V using Tapatalk
Thanks for the help on the pie controls! I really appreciate it, it's just something I never really used on the Nexus, nor used the LMT itself. But without a pure AOSP build, I feel it needs tweaked a bit to get back to a little more familiar grounds. (No Nexus 5 on Verizon .. grrr)
I think I was getting myself confused a bit thinking those tweaks could give me our 3 normal softkeys to replace my physical and capacitive ones. I know it was possible on the Note 2 from reading but it didn't seem to happen without a bit of troubles. Either way, I am rooted now and have removed some of the bloat apps. I am now considering going back into the custom realm on ROMS.
Thanks for the tips!
Im trying to map a shortcut for screenshots but so far none of them have worked.
http://forum.xda-developers.com/showpost.php?p=37823525&postcount=3328
maybe i can just find an app and map that.
Nevermind updated to the newest build and screenshot is an option.
Is the default input device #4 the best for N3?
I replaced 1 pie button and the other defaults went missing, any way around that, I would like to replace them one at a time?
When blacklisting apps I have to scroll through ~400 app list to remove non ui sys services then select one at a time, is the list a file somewhere that can be edited by other means?
SM-N900V DE
LillieBennett said:
Is the default input device #4 the best for N3?
I replaced 1 pie button and the other defaults went missing, any way around that, I would like to replace them one at a time? ...
Click to expand...
Click to collapse
I'm not sure what you mean by 'default input device'. As you set up PIE you can customize the number of tiles (up to 5) and have up to 2 levels of tiles, for a total of 10 possible shortcuts. The first level is set by default to be Android navigation buttons (soft buttons), 'back', 'home', 'menu', 'search', 'multitasking'.
{
"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"
}
If these defaults have gone missing, or there are less than 5, PIE will reduce the number of 'buttons' that show up when activated, i.e. graphic UI will be adjusted
I could reduce each level of PIE down to 1 'button' if I choose.
Now that I'm thinking in this context, I'm guessing that is what you mean by "default input devices". If I am reading you right, you can set up to 5 and there will be no issue for the Note 3, likewise say that you only wanted three 'buttons' or 'input devices" (Home, Back, Menu) that wouldn't be a problem either. PIE will adjust the Graphic UI to match your settings, there won't be 5 'buttons' on screen if you only set 3 of them. I hope I'm being clear?
LillieBennett said:
...When blacklisting apps I have to scroll through ~400 app list to remove non ui sys services then select one at a time, is the list a file somewhere that can be edited by other means?
SM-N900V DE
Click to expand...
Click to collapse
Honestly I don't blacklist any apps from from PIE
Can I ask why you want to Blacklist an application? Once I set the apps I want in my PIE I don't worry about the other apps I have installed on my device. I set those to be my most used apps, for the particular device om setting up. For instance, my Note 3 2nd level PIE app shortcuts are these
I have them set, and if I need to change them I just sift through the apps and replace them (I agree it does take some time to load, but once you have it set as you launch PIE it is seamless). I guess I don't understand why you want to Blacklist an application, when you only need to set the ones you want to have appear on the PIE launcher. Not that you need to validate your reasons to me, unfortunately I don't use this feature myself so I don't think I can be very helpful about this. Hopefully someone else might be able to lend some advice.
Let me know if I was on target about your question on setting the 'buttons' up.
Sent from my SM-N900V using Tapatalk
harajyuks said:
I'm not sure what you mean by 'default input device'. As you set up PIE you can customize the number of tiles (up to 5) and have up to 2 levels of tiles, for a total of 10 possible shortcuts. The first level is set by default to be Android navigation buttons (soft buttons), 'back', 'home', 'menu', 'search', 'multitasking'.
If these defaults have gone missing, or there are less than 5, PIE will reduce the number of 'buttons' that show up when activated, i.e. graphic UI will be adjusted
I could reduce each level of PIE down to 1 'button' if I choose.
Now that I'm thinking in this context, I'm guessing that is what you mean by "default input devices". If I am reading you right, you can set up to 5 and there will be no issue for the Note 3, likewise say that you only wanted three 'buttons' or 'input devices" (Home, Back, Menu) that wouldn't be a problem either. PIE will adjust the Graphic UI to match your settings, there won't be 5 'buttons' on screen if you only set 3 of them. I hope I'm being clear?
Honestly I don't blacklist any apps from from PIE
Can I ask why you want to Blacklist an application? Once I set the apps I want in my PIE I don't worry about the other apps I have installed on my device. I set those to be my most used apps, for the particular device om setting up. For instance, my Note 3 2nd level PIE app shortcuts are these
I have them set, and if I need to change them I just sift through the apps and replace them (I agree it does take some time to load, but once you have it set as you launch PIE it is seamless). I guess I don't understand why you want to Blacklist an application, when you only need to set the ones you want to have appear on the PIE launcher. Not that you need to validate your reasons to me, unfortunately I don't use this feature myself so I don't think I can be very helpful about this. Hopefully someone else might be able to lend some advice.
Let me know if I was on target about your question on setting the 'buttons' up.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Input device below, default is #4:
The reason I asked is the only pie position that works is bottom center, at first the default right worked but once I changed it, I can't put it back and have it work.
I guess the button setup as you described isn't so bad.
SM-N900V DE
LillieBennett said:
Input device below, default is #4:
The reason I asked is the only pie position that works is bottom center, at first the default right worked but once I changed it, I can't put it back and have it work.
I guess the button setup as you described isn't so bad.
SM-N900V DE
Click to expand...
Click to collapse
Oh, gotcha. Gesture input is a different set of features in LMT and not invloved with the the operation of PIE. This allows you to set actions that will launch when you complete a gesture.
Much like PIE once you select one of these options it will take you to the list where you can select the action to be completed.
You don't need to set any of this up in order to use PIE, The default for all gestures is 'None'.
Sent from my SM-N900V using Tapatalk
harajyuks said:
Any questions, tips, etc? Let's talk here.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
You were right, I am using pie all the time now. It really shines for multi task where you can switch from one app to another directly, without going through recent first. Thanks for the turn on!
SM-N900V DE
LillieBennett said:
You were right, I am using pie all the time now. It really shines for multi task where you can switch from one app to another directly, without going through recent first. Thanks for the turn on!
SM-N900V DE
Click to expand...
Click to collapse
LMT/PIE is really cool and I just wanted to drop in to let you guys know about an app that's very similar called Switchr
He recently implemented an "Arc" style that's just like PIE, and which one you choose to use is just preference IMO
Big difference is the "Live switching" just imagine using PIE but as you swipe over your overlay icons, the foreground app changes instantly vs PIE where you have to release your finger to trigger the switching
To clarify, By blacklisting an app in LMT/Pie you aren't saying don't show up in the choices of apps. You are telling pie controls to not work or appear when using certain apps. So if i didn't want it to appear in Internet so I can still use its pie controls, I could black list Internet.
I don't use the feature but some people do. I never use ISA or gestures. But have been using pie since beans in the s3. Had it in my note 3 a day after the first root exploit came out after launch. So Worth it
Sent from my GlaDos Baked Potato
Legato Bluesummers said:
To clarify, By blacklisting an app in LMT/Pie you aren't saying don't show up in the choices of apps. You are telling pie controls to not work or appear when using certain apps. So if i didn't want it to appear in Internet so I can still use its pie controls, I could black list Internet.
I don't use the feature but some people do. I never use ISA or gestures. But have been using pie since beans in the s3. Had it in my note 3 a day after the first root exploit came out after launch. So Worth it
Sent from my GlaDos Baked Potato
Click to expand...
Click to collapse
I never used blacklisting. Thank you for the clarification.
Sent from my SM-N900V using Tapatalk
Today, Motorola officially posted an update regarding Android 5.0 Lollipop update for the Moto G,,
So guys,, Get ready..! The Release very soon..Hope it'll be released by Monday or ?
Source: https://motorola-global-portal.custhelp.com/app/error//error_id/1
**Note: Motorola has removed that page. If you doubt this thread, you can search online.
{
"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"
}
Complete Release Notes by Motorola Page:
Moto G (2nd Generation) - Android™ 5.0 Lollipop - Release Notes
INTRODUCTION
We are excited to announce a new software update for Moto G (2nd Generation) by Motorola. This update brings Android™ 5.0 Lollipop to your phone along with other improvements.
For more information on Motorola updates and repairs, visit us at www.motorola.com/mymotog.
NOTE: You cannot downgrade to a previous software version after installing this update.
ENHANCEMENTS
Android™ 5.0 Lollipop is one of the most significant in recent Android history. It improves your experience in many areas including visual style and how you interact with your device.
After installing the software update you may notice changes that include:
Material Design You will quickly notice a whole new colorful look and feel to your device - from fluid animations to new application and system themes, colors and widgets.
Notifications UI & Priorities
In order to alert you to the most timely and relevant information, the format and behavior of notifications have evolved:
notifications will appear on the lock screen and are intelligently ranked by type and who sent them.
you double-tap to open one, swipe left or right to clear one, or clear all notifications from the bottom of the list.
you can set the priority and privacy of notifications for each application.
very high priority notifications will pop up briefly over other applications so that you can take action.
when you dismiss a notification on one device it will be dismissed on your other Android devices, if they are connected to the Internet.
you can further tailor how notifications behave with the new Downtime and Ambient Display settings (see below).
New Interruptions & Downtime Settings You can tailor how interruptions behave, choosing to allow all, none, or only priority interruptions. You can personalize what counts as a priority interruption (reminders, events, calls, messages) and even tailor them to be from only contacts you specify. The Downtime setting will allow only priority interruptions during the times and days that you specify. e.g. allow only priority interruptions on the weekend.
Recent Apps (Multi-tasking) The redesigned Overview space (formerly called Recents) will include both applications and separate activities within those applications. For instance, each open tab in Chrome will also appear here along with recent applications; both your Gmail Inbox and a draft email message will appear as separate cards. This provides a consistent way to switch amongst tasks.
Ambient Display While your phone’s display is off, Ambient Display can show notifications without turning on the full display. This will be triggered when a notification arrives. You will see notifications similar to that shown on the lock screen. You can turn this feature on in the Display menu in Settings, and note that it will increase the power consumption of your device.
Motorola Assist and Downtime Motorola Assist integrates the new Downtime settings to control when you don’t want to be disturbed. Motorola Assist also now uses the new Interruptions settings so that you can customize exceptions, such as letting only people on your starred contacts list get through.
Flashlight Lollipop includes a new flashlight option as part of Quick settings (swipe down with two fingers from the status bar to see it).
Share your Device You can now set up multiple user accounts on your phone. Guest mode is enabled by default. You can give calling and text privileges to other users of your device, or restrict them as you like in the Users menu under Settings.
Note that the personalized Motorola experiences (Motorola Assist, Motorola Connect) are for the owner account only.
The Motorola Camera, Motorola Gallery, and Motorola FM Radio applications support multiple user accounts.
Pin a view/app Screen pinning allows you to keep a specific app or screen in view. For example, you can ‘pin’ a game and your child will not be able to navigate anywhere else on your phone.
Battery The Battery settings panel now shows an estimated projection for how much time you have left while discharging or charging. You can also enable a new battery saver mode that will save power by reducing performance and most background data operations to extend your battery life.
Smarter Internet Connections With Android Lollipop, your phone will not connect to a Wi-Fi access point unless there is a verified Internet connection. This feature improves hand-offs between Wi-Fi and cellular connections, helping to maintain your video chat or voice-over-IP (VoIP) call as you switch.
Performance Your phone now uses the new Android Runtime to help optimize application performance. After upgrading to Lollipop, your applications will undergo a one-time optimization process. Note that the optimization for ART requires more space.
Smart Lock
(Trusted Devices) Android Lollipop adds native support for allowing trusted devices to keep your phone unlocked (such as your Moto 360, a Bluetooth car kit or headset, etc.). Smart Lock replaces the prior trusted device capability in your Motorola phone. Note that you will need to add your trusted devices back after the transition to Lollipop in the Security settings menu under Smart Lock.
Security Encryption can now use a stronger 256-bit key to help protect your data. Note that the stronger key will only be used after you perform a factory reset on Android Lollipop. Otherwise encryption will continue to use 128-bit key. You can turn on encryption in the Security settings menu.
INSTRUCTIONS
For a successful installation, we recommend installing this update when the battery in your phone is at least 50% charged and you are connected to a Wi-Fi network.
If you have received a notification message for this update:
Select "Yes, I’m in".
After the software is downloaded, select "Install now".
After the software is installed, your phone will re-start automatically.
Your phone is now updated with <insert build number>
If you have not received a notification message for this update, follow the steps below to manually update your phone:
Select the Settings icon in the apps menu.
Select "About phone".
Select "System updates".
Select "Yes, I’m in". After the software is downloaded, select "Install now".
After the software is installed, your phone will re-start automatically.
Your phone is now updated to <insert build number>
Additional Information
If you have difficulty with this upgrade, visit us at www.motorola.com/mymotog.
AravindTheKing said:
Today, Motorola officially posted an update regarding Android 5.0 Lollipop update for the Moto G,,
So guys,, Get ready..! The Release very soon..Hope it'll be released by Monday or ?
Source: https://motorola-global-portal.custhelp.com/app/error//error_id/1
Click to expand...
Click to collapse
it says for Moto g 2nd gen can't you read?
And you've linked to an error page
It was put up by mistake by Motorola and they pulled it down.
burak144 said:
it says for Moto g 2nd gen can't you read?
Click to expand...
Click to collapse
The differences b/w Moto G 2nd Gen and 1st Gen are far lower and i hope they release for 1st Gen very soon after releasing to Moto G 2nd Gen. That's why i informed here. Sorry if i did anything wrong!
its a update for moto g 2014 :/
esd316 said:
its a update for moto g 2014 :/
Click to expand...
Click to collapse
Thats true, but again, the two G are 90% identical in hardware. So if L comes to 2014 variant, it wont take long to hit 2013 version. Something says to me that we are closer to get some update! :good:
They are always going to give the current phones the update first and high end would be first of them. So I'd guess we'll be after moto x first gen.
eemgee said:
They are always going to give the current phones the update first and high end would be first of them. So I'd guess we'll be after moto x first gen.
Click to expand...
Click to collapse
Something like that I guess. I think it's going like this: X (2014), G (2014), X (2013), G (2014) and last moto E
eddydc1 said:
Something like that I guess. I think it's going like this: X (2014), G (2014), X (2013), G (2014) and last moto E
Click to expand...
Click to collapse
+100...
X and G 2014 would be the first ones to get it, as we are seeing this days with soak tests and release notes. After that, X and G 2013, maybe some weeks after, one or two I dare to say, and after all the love for the bigger ones, comes E, our little brother. :good: Its incredible that mid and low end phones are getting a flagship-like update schedule with the las version of Android. Good one Motorola. And I bet that before december, we will have some sweet news about this. Be prepared and flash stock firmware until the day comes!
Another thing I was thinking about is, if bootloader isn't downgradable, then most of KK roms available today for our device will be useless, since they need KK bootloader to work propperly... Thats why we didn't see a lot of JB custom roms, because of bootloader wasnt downgradable.. It will be like a new beggining, with just Lollipop roms for those ones who update their phones!
One possible solution will be that someone provides a flashable ZIP of Lollipop, but we don't know if that will work on a KK kernel and bootloader.... We are blind regarding to that now. Lets wait.
MarckozZ said:
Thats true, but again, the two G are 90% identical in hardware. So if L comes to 2014 variant, it wont take long to hit 2013 version. Something says to me that we are closer to get some update! :good:
Click to expand...
Click to collapse
Doesn't matter, the 2013 version will get updated no matter what.
I wish some awesome developers port the aosp version first so i can finally showoff in front of my cousins who have a nexus.
Ambient display? On an LCD screen? Will that not drain a lot of battery?
Sent from my XT1032 using XDA Premium 4 mobile app
Aayushya said:
Ambient display? On an LCD screen? Will that not drain a lot of battery?
Sent from my XT1032 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That surprised me too.... It seems like an stock new Android feature. Also Motorola states in the release notes that it will increase battery consumption.. So yes, LCD active display for those that dont care about battery.. Anyway I'll give it a shot when L comes up!
I remember that somewhere in Motorola forums one support staff member said that developers had found a way to make it better on battery so we'll see once it is available
----->
http://forum.xda-developers.com/moto-g/general/moto-g-2nd-gen-moto-x-2nd-gen-lollipop-t2933495
Screenshots of the 2 pages (G and X) attached, in case the cached pages go offline.... ya know?
Lets take a look in video at how Lollipop is on Moto X 2014!! This will be very simmilar to our device's final look! :fingers-crossed:
http://www.youtube.com/watch?v=EOfCq_bR7uw
Cant w8!!!!! This is gonna be so epic!! Lollipop seems so fuking awesome! Those animations and that lockscreen my god!!
diecast said:
Cant w8!!!!! This is gonna be so epic!! Lollipop seems so fuking awesome! Those animations and that lockscreen my god!!
Click to expand...
Click to collapse
W8?
Weight?
Wait!
Saving characters is only valid when typing more of them costs more money.
glossywhite said:
W8?
Weight?
Wait!
Saving characters is only valid when typing more of them costs more money.
Click to expand...
Click to collapse
LOLOLOL He can't loose weight because of eating a lot of Lollipops... Obvious joke..