• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

Android 5.X Lollipop Discussions.....

Search This thread

Madfysh

Senior Member
Sep 22, 2011
2,453
1,486
If you are like me and you use swipe to unlock phone and you noticed that every time you unlocked phone, icon for location appear in upper right part of notification & status bar and then after second it disappears.
And in settings->location you see google play services as high battery use.

To kill that location request, go to settings->security->screen lock need to be any except none or swipe, then in "trust agents" disable smart lock, after that go back using whatever for screen lock.

I was using swipe and don't need those smart things. :) Now I even tried to put back smart lock on, and screen lock back on swipe, now I don't get location request anymore.. weird :)

Second thing, google continues to waste space on our screens.. After flash, I opened play store(its 5.1.11) and noticed bigger icons, in general space for 1 of items on screen, it wasn't like that on version I had on 5.0.. same thing happened with gmail, same story with google messanger(compared to stock messaging app). Even in old apps there is empty space above/below items but still there are more items on screen. I guess in android 6, we will have one item per screen..:)
Maybe it looks nicer(to some), but it sure isn't more useful..at least for me :)
 

pjc123

Senior Member
Feb 7, 2013
468
81
www.flaminghellmet.com
It's not needed anymore. UPDATE-SuperSU-v2.37.zip from http://download.chainfire.eu/636/SuperSU/ is working fine falshed from recovery.

As usual, glad I waited until everything settled down a bit. Between Android 5.0.1, the SuperSU 2.37 zip you posted (Would not install from Google Play on 5.0.1) and the most recent TWRP (2.8.2.0), everything went very smoothly with the upgrade from 4.4.4 to 5.0.1.. The phone is much faster and all my old apps are still working properly. I am missing Xposed/Xprivacy/GravityBox however, but I imagine something else will come along eventually.
 
Last edited:

gabriel1946

Senior Member
Mar 30, 2013
508
149
vegas baby
If you are like me and you use swipe to unlock phone and you noticed that every time you unlocked phone, icon for location appear in upper right part of notification & status bar and then after second it disappears.
And in settings->location you see google play services as high battery use.

To kill that location request, go to settings->security->screen lock need to be any except none or swipe, then in "trust agents" disable smart lock, after that go back using whatever for screen lock.

I was using swipe and don't need those smart things. :) Now I even tried to put back smart lock on, and screen lock back on swipe, now I don't get location request anymore.. weird :)

Second thing, google continues to waste space on our screens.. After flash, I opened play store(its 5.1.11) and noticed bigger icons, in general space for 1 of items on screen, it wasn't like that on version I had on 5.0.. same thing happened with gmail, same story with google messanger(compared to stock messaging app). Even in old apps there is empty space above/below items but still there are more items on screen. I guess in android 6, we will have one item per screen..:)
Maybe it looks nicer(to some), but it sure isn't more useful..at least for me :)

yo man this should be stickied somewhere.. thanks for the good info brotha
 

Ale506

Member
Dec 3, 2014
14
3
videojuegos.cr
Use fastboot to flash a custom recovery then flash the latest supersu from the xda thread.

I'm a Brazilian without English Course, sorry and be comprehensive :)

Hey man thanks, I'm root now. I use CWM but I did not flash it, I just boot it so I can still getting the OTA's but I encounter some "problem" and I just want to now if I made the right decision... after I install the supersu and try to reboot my nexus I get this:

Root Access Possibly Lost Fix?
THIS CANNOT BE UNDONE

1. NO do not fix
2. YES fix root (/system/xbin/su)

And in the guide that I was reading it did not has that, so.... I chose "No" because I was kind of scare that it will modified my system. So what's up with that?
 
Last edited:

prithvic

Senior Member
Oct 21, 2014
257
100
Mυмвαι
Redmi K20 Pro
Did 5.0.1 fix the front camera lag?

I still face it. I don't think they fixed it :(

---------- Post added at 12:43 PM ---------- Previous post was at 12:39 PM ----------

Erm.. CWM 6.0.4.7 is not working anymore with 5.0.1?:confused:
It was working on 5.0 with no problem. Now I get android with red exclamation mark, which is stock recovery if I remember correctly (it's been a while since I tried stock recovery)

EDIT: fastboot boot recovery.img seems to be working so at least I managed to flash superSU..

EDIT2: I forgot to write, during flash process I got archive does not contain 'vendor.img' but everything seems to be working (except recovery :) )

try fastboot flash recover recovery_name.img, if CWM isn't working, try TWRP, I'm running fine on TWRP & stock 5.0.1
 

Madfysh

Senior Member
Sep 22, 2011
2,453
1,486
try fastboot flash recover recovery_name.img, if CWM isn't working, try TWRP, I'm running fine on TWRP & stock 5.0.1
Thats what I did(talking about instruction to flash), few tries, but no go. So i ended up just booting CWM recovery.
Not sure what changed from 5.0 that I cant flash CWM recovery..
Would like to stay on cwm, but will try twrp if I will need it :)
 

RootNightmareX

Senior Member
Jan 7, 2012
2,228
297
Hey guys, i'm on 5.0.0 flashed factory image. I want to update to 5.0.1. via factory images, i want to dirty flash so it will wipe my data if i flash the factory image or should i wait for ota ?
 

andeld

Senior Member
Jun 19, 2009
281
46
Is this feature available on lollipop? I do not have this feature available on my Greenify menu, do I need the donation package? I mean the pull-up gesture reset.
Yes, it should work. No, you don't need the donation package. Install it, access it and select the apps you want to be hibernated then just use the pull up gesture. You will be asked to select an action and you can select to hibernate + lock screen and you can make it a default action by selecting Always when you are asked to.
 
  • Like
Reactions: shakeador

mymeatb18

Senior Member
Feb 27, 2011
1,459
274
miami
So I have been battling bad battery since lollipop. Noticed I had a lot of drain from chrome. I had the tabs in recent bull crap. Also noticed recent apps don't go away after reboot. I changed to normal chrome tabs and there were 14 tabs open polling data in the background. Battery has since been restored. Just a thought
 

Top Liked Posts

  • There are no posts matching your filters.
  • 84
    Success ! ! !

    ITS DONE! ! !

    Yes! FInally! However it is very slow currently! I am looking into it. For now you have the logcat and a snapshot!!
    70
    I would be interested :)

    Sent from my Nexus 4 using Tapatalk

    Alright it is gonna be more on the simplistic side because I don't know everyone's knowledge level.

    The boot.img consists of a kernel and the ramdisk, the ramdisk includes all the init files and basic loading of everything. When developers talk about getting something to boot, they are normally working on the boot.img and fastboot (generally depending on the platform and availability of fastboot), you can also make update.zips and flash them as usual too. The inits between kit Kat and android L are different mostly because of selinux and induction of Knox so it is taking a bit longer to get that all worked out.
    Second is the system.img that can either be fastboot flashed or turned into a zip with the proper layout and updater script to make a flash able update.zip too (once again depends on the device, some actually use tarballs)
    Now here is where it is more difficult to explain.
    Everything in a Linux file structure is a file, the ram, drivers, sdcard, all is a file. Proprietary binaries are the driver code provided in a binary file for everything from the camera to the touchscreen drivers to work the emmc hardware. Those binaries are code compiled against a certain version of the software and then distributed as closed source binary code. Google would have that code because it is provided under NDA to them to work with.

    Next we talk about libraries, libraries are either static or dynamically linked and are compiled code for the system to use, these are highly important because these control everything at the upper system level. When programs are compiled they rely on other programs or hardware to work while also talking to the kernel. Dynamic libraries intertwine throughout other files with linker files or directly into the code while static libraries are worked on and don't need other libraries to function. As far as porting goes, you normally have the code that versions are based on so you can read it and have an idea of what links to what and write linker or fake files to bypass the dynamic libraries they are built on so you can rewrite a library for the function can continue (in porting, you write it so it will work with your hardware vs the original intended hardware)
    Now the problems we are running into against say porting touchwiz to work on the n4 or even back porting. We don't have android L code at all, we don't even know what changes they made to the kernel or any code whatsoever in the source and since we can't compile our own libraries to work with our hardware because we don't have the code puts us at a distinct disadvantage against say a back port. There has been WiFi file structure change ups, selinux, Knox and art runtime changes that we don't know and can't see and we are working on unknown to us changes.

    I hope that described it a bit, I kinda rambled and didn't proofread it, there is more involved but I was just trying to explain the gist of things in simple terms

    Sent from my C6916 using XDA Free mobile app
    65
    You know what guys? We should all download the image for the nexus 5, make it into a flashable for the nexus 4 by changing 1-2 things in the updater script, post something like "done porting, will test in a bit". Then post "damn, bootloop". Later, something like "Ok, that didn't work. I'll try this tool. I hope it will boot now", etc...

    Really, there are a few people claiming to be devs and getting hopes up like this. The guy says "bootloop", "no logcat"... Bootloop?? No logcat? Wow, that's something new. I don't remember seeing anything about that like 10 pages ago. You are the first to get to that point. Awesome!

    What's more funny is that people are giving them a hell of thanks and are all like "Wow! Great job man! Keep it up. We believe in you!"...

    I'm apologizing in advance in case you find this offensive but this one person posts "porting finished now testing" when he hasn't even flashed the package yet and he gets 34 thanks points which makes it to the top of the thread, above the people who are actually working on a port and have done numerous tests. Well, we can imagine that this person is a super developer who is super confident that his port will work and doesn't need any actual testing in order to say that he has "finished" porting. However, just after a single post he says "not even sure its booting", "Zipping now", "Rebooted hope it boots". Just, what the hell?

    Now, do you see any actual devs going around the thread posting their every single status update? Do they do that? They don't, right?

    I just hope these people are just posting out of pure excitement and have no intention of making use of this chance to fill their thanks meter up for no price.
    61
    LPV79-mako-test33

    alright guys here is test 33, I'll let you guys mirror it. Tomorrow I will set up the development thread, hopefully you guys can work through of the bugs while I sleep
    http://www.firedrive.com/file/CDA508B72AF19584

    Dev-host mirror http://d-h.st/n0R
    Mega link https://mega.co.nz/#!P0o2xABR!UoRLsTmPlYyroC1JwnvsyVHWoWdxciwNALdqQRViFw4

    thanks @Cheesethief for the dev-host mirror and mega.

    google link was hit too much and dead now, thanks for the firedrive mirror @hardrockk

    FIRST BOOT TAKES ABOUT 20 MINS, wipe your dalvik-cache also since it is a new runtime

    I don't even know what will be working and not, defconoi was doing the testing and debugging while I was working on it so not exactly sure yet and as @percy_g2 pointed out there was missing vendor files that were for camera and bluetooth so they might be working.

    Dalvik-cache is working now and was a big step in towards getting the package manager to instal but it isn't yet. It is set to selinux permissive at boot now too and strict policy was turned off which will have it booting fast


    @percy_g2 pm'ed the none gapp version to you for you to help on debugging
    41
    porting finished now testing :D