Hi guys if you don't know what wakeblock is then it is basically amplify but for users with no xposed and users on nougat. For deodexed roms it requires a modification of the services.jar file which means you need to make a build from a computer and go through hell if you're like me. I'm taking requests though to get wakeblock on different roms.
If you would like wakeblock on a rom you are using then please tell me and tell me what device and rom you are using. Also if you can then I'd appreciate it if you link me the github repository for that rom so I can sync it easier. Thanks! So to recap, tell me your rom, device, link roms github repo (optional but recommended) and I'll send you a zip with the mod to flash. After flashing download wakeblock from the play store and service should be bound. From there you can block wakelocks.
Credit to this thread for creating wakeblock and the necessary patch file. https://forum.xda-developers.com/nexus-6p/development/wakeblock-blocking-drain-late-t3526313
Credit to the user SimoIanni for helping me understand how this works and for doing two roms already.
Just download flash and install the app. Below are the wakelocks I recommend blocking.
- NlpWakeLock -- 900 000ms
- GCoreFlp -- 900 000ms
- RILJ -- 900 000ms
- UlrDispSvcFastWL -- 900 000ms
- CMWakeLock -- 900 000ms
- *net_scheduler* -- 3 600 000ms
- Wakeful StateMachine: GeofencerStateMachine -- 900 000ms
- LocationManagerService -- 900 000ms
- SyncLoopWakeLock -- 900 000ms
- NetworkStats -- 900 000ms
- Icing -- 3 600 000 ms
- ULR_BarometerReading_WakeLock -- 900 000ms
- NfcService:mRoutingWakeLock -- 3 600 000ms
- NlpCollectorWakeLock -- 900 000ms
- wake:com.google.android.gms./ measurement.PackageMeasurementService -- Disable
- Anything with FireBaseInstantIDService -- Disable
- Anything with the word analytics in the name -- Disable
- GOOGLE_C2DM -- Disable
Thanks to @Face_Plant for suggesting 900000 instead of 600000 and for suggesting the bottom four in the list above to block.
SUPPORTED ROMS:
AquariOS (built into source code)
Pure nexus
Omni
SAOSP
Dirty unicorns
Uber
ABC (ezio84)
Euclidean N5X (built into source code)
UAOSPA
crDroid
Screwd
Dark rom (I think and might be built into source code
Carbon rom (built into source code)
S.I.X rom (built into source code)
sos rom (built into source code)
AICP (built into source code)
Keep in mind that the above roms supported may not work as I don't have time to build for every rom as that would take too much time away from my life and college/university. If you are in doubt then ask me or backup then flash it. Make sure to ask me to update it if the current posted version doesn't work.
Take in mind that this wakelocks are blocked without impacting ANY functionality of the phone. You may want to increase the time if don't use geolocation at your own risk
Here are where some more zips for more ROMs will appear as there is a limit per post of how many attachments you can attach. I'm just trying to get this and everything setup as I will soon be having a batch of new roms supported. Stay tuned, as many will appear with the coming days and weeks. Thanks for all your support guys and do remember to check out the official wakeblock thread and thanks to @KennyG123 for being such a kind soul and sorting out this thread as I stupidly forgot to make a reserved post.
Here's wakeblock for pure nexus and Uber. More will arrive here in the future as roms are requested.
Works great on Pure Nexus. Thank you very much! Amplify was one of the Xposed modules I was missing the most and I'm overjoyed to have a working alternative now
{
"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"
}
How about for Six ROM? For the nexus 6p or nexus 6?
https://github.com/SiXROM?language=java
Sent from my Nexus 6P using Tapatalk
I am on stock 7.1.2 with elementalx kernel. The wakeblock app shows unsupported rom/version. Any Guide for this?
grgsujan said:
I am on stock 7.1.2 with elementalx kernel. The wakeblock app shows unsupported rom/version. Any Guide for this?
Click to expand...
Click to collapse
Stock is harder to get working but the wakeblock team is working on it so head over to their thread
Face_Plant said:
Works great on Pure Nexus. Thank you very much! Amplify was one of the Xposed modules I was missing the most and I'm overjoyed to have a working alternative now
Click to expand...
Click to collapse
Thanks I really appreciate it. Make sure you thank and check out the actual wakeblock thread
tikizondo94 said:
How about for Six ROM? For the nexus 6p or nexus 6?
https://github.com/SiXROM?language=java
Click to expand...
Click to collapse
I will definitely try and get that done today or tomorrow if possible. I'm not sure which repo to use but I think I have a good idea.
DEVILOPS 007 said:
I will definitely try and get that done today or tomorrow if possible. I'm not sure which repo to use but I think I have a good idea.
Click to expand...
Click to collapse
That would be awesome! Much appreciated..
tikizondo94 said:
That would be awesome! Much appreciated..
Click to expand...
Click to collapse
I'm having a small issue with it right now but could you do me a favor and try the pure nexus version I posted as SiXROM is extremely similar and based off pure nexus so there is a good chance it will work.
Face_Plant said:
Works great on Pure Nexus. Thank you very much! Amplify was one of the Xposed modules I was missing the most and I'm overjoyed to have a working alternative now
Click to expand...
Click to collapse
How do you have nlp wakelock? I don't have that.
DEVILOPS 007 said:
Thanks I really appreciate it. Make sure you thank and check out the actual wakeblock thread
Click to expand...
Click to collapse
I already gave you some thanks and I follow the other thread pretty closely :good:
DEVILOPS 007 said:
How do you have nlp wakelock? I don't have that.
Click to expand...
Click to collapse
Do you have location turned on? NLP is related to location.
Face_Plant said:
I already gave you some thanks and I follow the other thread pretty closely :good:
Do you have location turned on? NLP is related to location.
Click to expand...
Click to collapse
No location services?
DEVILOPS 007 said:
I'm having a small issue with it right now but could you do me a favor and try the pure nexus version I posted as SiXROM is extremely similar and based off pure nexus so there is a good chance it will work.
Click to expand...
Click to collapse
I flashed the pure nexus version. just got a boot loop. No biggie. There must be something else in there. I appreciate you trying though!
tikizondo94 said:
I flashed the pure nexus version. just got a boot loop. No biggie. There must be something else in there. I appreciate you trying though!
Click to expand...
Click to collapse
Did you try extracting services.jar, booting into TWRP, moving the file to system/framework, and setting permissions to 0644 manually? This is the method that worked for me. Flashing the file also gave me a boot loop. Make a copy of your original services.jar just in case something goes wrong so you can move in back in recovery to avoid having to reflash your ROM.
DEVILOPS 007 said:
No location services?
Click to expand...
Click to collapse
If you have no location services then that's why you don't see the wakelock
tikizondo94 said:
I flashed the pure nexus version. just got a boot loop. No biggie. There must be something else in there. I appreciate you trying though!
Click to expand...
Click to collapse
Okay, I'll try to work this problem out. Try what Face_Plant said
Face_Plant said:
Did you try extracting services.jar, booting into TWRP, moving the file to system/framework, and setting permissions to 0644 manually? This is the method that worked for me. Flashing the file also gave me a boot loop. Make a copy of your original services.jar just in case something goes wrong so you can move in back in recovery to avoid having to reflash your ROM.
If you have no location services then that's why you don't see the wakelock
Click to expand...
Click to collapse
I mean I have it but it isn't enabled and flashing the mod worked fine for me so I'm not sure what's going on with you flashing it.
DEVILOPS 007 said:
I mean I have it but it isn't enabled and flashing the mod worked fine for me so I'm not sure what's going on with you flashing it.
Click to expand...
Click to collapse
If it isn't enabled then that's why you aren't seeing the wakelock. I use "battery saving" location services, which relies heavily on Google Play Services, so that's why I have so many of those wakelocks.
I suspect that I either got a bad download or it had something to do with the unofficial build of TWRP I was using that tends to be somewhat buggy, so that's probably why I boot looped.
Face_Plant said:
If it isn't enabled then that's why you aren't seeing the wakelock. I use "battery saving" location services, which relies heavily on Google Play Services, so that's why I have so many of those wakelocks.
I suspect that I either got a bad download or it had something to do with the unofficial build of TWRP I was using that tends to be somewhat buggy, so that's probably why I boot looped.
Click to expand...
Click to collapse
Oh okay. I tried enabling location services to get the wakelock but don't see it so I might just leave it.
Related
{
"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"
}
Flashing tips by @ramjet73, this should be read by everyone
http://forum.xda-developers.com/showpost.php?p=55228784&postcount=12583
This is an enhanced version of the 81c developer preview that google released.
It has currently been ported for Mako and Deb and improved for Hammerhead and Flo
It offers a permissive selinux policy, aosp merged in and rock solid stabilty along with drastic improvements in speed and smoothness.
It offers updated proprietary files, updated google apps, fonts, res files and animations from the newer sdks.
Click to expand...
Click to collapse
Deb does not have a working mobile radio yet, radio turns on but without access to the settings, we can't configure it. A work around is being worked on
Big thanks to @defconoi , @zyr3x , @percy_g2 , @ben1066 [MENTION=1050103] for improving and originally helping with the old lpv79 port to Mako.
Right now I rebased the entire project to clean it out and smooth it out
Huge thanks to @ramjet73 @bitstra @manueltts @skiman10 @psycho693 @jayfallen for helping me get it over to the other devices I don't have and testing everything I threw at them and the huge brainstorming and trying things I couldn't. It would have not been possible without these guys so please thank them
Click to expand...
Click to collapse
Warning. This has heavy ramdisk mods that are essential for it to work. You can flash current up to date "kit Kat kernels or L updaters only" but not full boot.imgs as this will break the ROM. If you do happen to flash a a boot.img, you can pull it out if the rom and fastboot flash boot boot.img
Hammerhead can only use L preview Kernels.
Remember, this is a port of a developer preview, there is already bugs in the official version from google and without the L code, we can not fix google's bugs. There are fixes to known problems in N7 2013 and N5 forums so if you do find them, please provide them with the bug
Click to expand...
Click to collapse
INSTALLATION INSTRUCTIONS
FIRST TIME FLASHING
Put the file onto your Internal Storage
Reboot into Recovery (CWM/TWRP]
"wipe data/factory reset"
"mounts and storage" -> "format system"
"install zip" -> "install zip from sdcard" -> choose the mako-bla-bla-zip and confirm flashing procedure
"reboot into system"
first boot may take up to 10 minutes - be patient
UPDATING
Put the latest L-bla-bla.zip onto your Internal Storage
Reboot into Recovery (CWM/TWRP)
"wipe data/factory reset"
"install zip" -> "install zip from sdcard" -> choose the [filename.zip] and confirm flashing procedure
"reboot into system"
Updater-script wipes the cache files so no need to wipe cache
Sources
Mako
GPL KERNEL SOURCE - github.com/Android-L-Porting-Team/android_kernel_mako
Flo, Deb and Hammerhead use the modifed stock preview with the kexec-hardboot patch directly provided by @tassadar to provide multirom support. Flo and Deb use the same kernel.
Hammerhead - http://forum.xda-developers.com/showpost.php?p=48508468&postcount=2
Flo - http://forum.xda-developers.com/showpost.php?p=45886584&postcount=2
We are using the rebase repos right now since they are cleaned out
Github https://github.com/Android-L-Porting-Team
Downloads
Stable - 9001
Full
Afh - https://www.androidfilehost.com/?fid=95747613655040641
Google Drive - https://drive.google.com/file/d/0By0vn8iv_zrVYUlFbmVrMEtHcDA/edit?usp=sharing
Dev-Host-
Mega-
Click to expand...
Click to collapse
Downloads
Stable - 9001
Slim -
Afh - https://www.androidfilehost.com/?fid=95747613655040642
Google Drive - https://drive.google.com/file/d/0By0vn8iv_zrVS1hDakt6VWM3WGc/edit?usp=sharing
Dev-Host
Mega-
Click to expand...
Click to collapse
slim builds have excess google apps cut out for those on a bandwidth budget or like to pick and choose their google apps from the play store
OT talk is welcomed in my threads and development is done in the open. I encourage involvement in the project in any way.
Please do not complain about OT, it encourages a fun and relaxed environment
Like the work I did, consider donating. I'm currently not working so it helps feed me
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=BPFLE54YPRV92
Yes, my PayPal account is thatguy32404, I like to keep my banking stuff separated from my social account
nexus devices threads
Mako
http://forum.xda-developers.com/nexus-4/development/lpv-79-mako-port-beta-t2807446
deb
http://forum.xda-developers.com/nex...e/l-android-lpv-dev-deb-t2856915#post55016443+
flo
http://forum.xda-developers.com/nex...id-lpv-dev-flo-enhanced-t2856920#post55016534
hammerhead
http://forum.xda-developers.com/google-nexus-5/development/l-android-lpv-dev-n5-enhanced-t2856934
Changlelog.
Changlelog.
Stable-9001
Now over 9000!!!!!!
Updated selinux security policy
tracked down some missing permissions
did some other work but can't remember
B7.0.1
Flo & Deb
removed some excess apps that were replaced and I missed in b7
B7
updated fonts, res files, animations from the latest sdk
updater-script wipes cache files
updated some more google apps.
now using smart-art
force dns to google's public dns
B6
6 finishes up the rebasing work from 5 (5.9 was just a stepping stone and getting it out to other devices so we could work out all the kinks)
(Mako only info)
The rebasing work meant a lot of clean up and trying to get it as efficient as possible so from 5 to 6 is a big step and will be quite noticeable
(mako, flo, deb)
updated egl drivers are from qcom developer are in here which are newer then the preview ones
(Hammerhead )
Proper working sound now
(All)
Built in Busybox should be working. I tested the functions and seemed good to me.
Got rid of all the looping code and debugging code to speed everything up.
Updated the preview proprietary binaries to the latest version (some can't go all the way up and are stuck on a previous set or even original preview versions)
(Hammerhead has the latest preview egl drivers)
Built in google apps have been updated.
Introduction of slim builds for those on a bandwidth budget.
Can't think of what else.
Most kinks have all been worked out
Click to expand...
Click to collapse
B5.9
Rebased completely from scratch on 81c
improved reliability and stability.
Ported to Deb, Flo and Hammerhead
Beta 5
fully permissive sepolicy based on aosp, cleaned out a lot of crud
removed reliance on n5 frameworks, merged in some current aosp
improved smoothness and increased reliability, daily driver status
Beta 4
New Kernel
more smashy smashy bugs
Dpat09 said:
For all camera issues please try this: go to the Dev settings and disable nuplayer! I'm posting it again because I think it will be lost in all the posts! If it works hopefully the contributing devs will catch it and put it in the main post
Click to expand...
Click to collapse
reserved for @defconoi kernel info
Installed it now, works great. Thank you for bringing this to deb.
Now all we gotta do is figure out how to access the radio setting outside of the setting app since they aren't there.
I had to track down the radio files and pulled them out of 4.4.3 to get the radio to start but I don't have a deb so I can't troubleshoot it as well.
I'm using the n7 as a base for mako along with all the framework files but had to use the n5's apps. The problem with deb is that if you try to use non tablet apps, it breaks the multi user feature so that might not be am option there so a script or an app that replicates the setting and configure it to the network might have to be done
sykopompos said:
Now all we gotta do is figure out how to access the radio setting outside of the setting app since they aren't there.
I had to track down the radio files and pulled them out of 4.4.3 to get the radio to start but I don't have a deb so I can't troubleshoot it as well.
I'm using the n7 as a base for mako along with all the framework files but had to use the n5's apps. The problem with deb is that if you try to use non tablet apps, it breaks the multi user feature so that might not be am option there so a script or an app that replicates the setting and configure it to the network might have to be done
Click to expand...
Click to collapse
What's the difference between your port and my
http://forum.xda-developers.com/nexus-7-2013/development-lte/android-lpv81c-deb-t2849013
Just so you all know it was me who actually did all this stuff, @sykopompos is taking all the credit ? no but really without sykopompos and his wizardly ways there would be no way this would have gotten done. He was nice enough to help with the project, then "take it over" and get it done the right way. Make sure to give him a big thanks for taking time out of his day and working on this through the nights. Without him this might have never happened. Thanks a lot man!
Sent from my Nexus 7 LTE using Tapatalk
Ansanen said:
What's the difference between your port and my
http://forum.xda-developers.com/nexus-7-2013/development-lte/android-lpv81c-deb-t2849013
Click to expand...
Click to collapse
Give it a flash and come back and give me an answer.
Oh BTW, this should have been out like a month ago but I didn't realize my really stupid derp of not modifying the bootclasspath so it wouldn't boot. I didn't realize this till after I started work on flo so if @skiman10 was helping you, you might have a part of my earlier work in yours.
Also do you have the radio files in yours?
Hoping that you guys could figure out the radio issue, soon~ thanks!
jayfallen said:
Hoping that you guys could figure out the radio issue, soon~ thanks!
Click to expand...
Click to collapse
@skiman10 is looking into our options here since he has a deb.
This is gonna be a bit of a pain to figure out how to work around this
Being that the file is almost 500mb, I assume the gapps are included in the file?
Yes @papikev thats right.
papikev said:
Being that the file is almost 500mb, I assume the gapps are included in the file?
Click to expand...
Click to collapse
Yes... Because the L apps are speeeeecccciiiiaaaaallll. Very special.
skiman10 said:
Yes... Because the L apps are speeeeecccciiiiaaaaallll. Very special.
Click to expand...
Click to collapse
oooooh, sounds phuuuuuun, Thanks guys.
Now I need L for Nexus 10 and I'll be happy
Fatal1ty_18_RUS said:
Now I need L for Nexus 10 and I'll be happy
Click to expand...
Click to collapse
Buy me a Nexus 10 and your wish will be granted lol
Once the radio gets straightened out, this will be (yet it already is) a killer rom. Very smooth. Nice new features on L. First time running it, good stuff guys. 5 star this thread. Look forward to the future with this one.:good:
skiman10 said:
Buy me a Nexus 10 and your wish will be granted lol
Click to expand...
Click to collapse
You mean buy me one...
sykopompos said:
You mean buy me one...
Click to expand...
Click to collapse
I got this one... Your apprentice is ready!
skiman10 said:
I got this one... Your apprentice is ready!
Click to expand...
Click to collapse
Good, because it wouldn't be one bit easy
[ROM][3/26/15] Pure AOSP ROM -★| 5.1.0_R3 | LMY47I | Build #6 | Proof of concept! |★-
Pure AOSP for the Nexus 6
Preface:
This is meant to be a Pure AOSP build with just minor edits to stop the stock recovery from replacing custom recovery, add some Google edits to the ROM for GPS, and modify the ramdisk so as not to preclude it from being rooted! Its not meant to be a fancy ROM, its just meant to be a baseline AOSP ROM. This ROM was produced by following the steps in the build guide I wrote. See post #2 for build guide links!
Install Instructions
Must have custom Recovery on unlocked device
Copy ROM to device (Gapps and root too!)
Reboot to recovery
Choose Factory reset (TWRP, not sure what CWM is)
Choose Install ROM
Now you can install the Gapps, and Root if you desire!
Specs and Download Link!
Android Build Version: 5.1.0_R3 / LRX22G
Current Build Date: 3/26/2015
Download: HERE!
Recommended Add-Ons
SuperSU by Chainfire here: SuperSU Stable Version
PA Gapps here: [GAPPS][5.0.x][BETA] OFFICIAL Up-to-Date PA-GOOGLE APPS (All ROM's)
Change Log
1/19/15 - Build 6 - Complete rebuild as proof of concept for 5.1.0_r3. This is PURE AOSP with no edits and no fixes.
1/19/15 - Build 5 - Fixed Youtube, Net flix DRM play back issue. Thanks to @sykopompos for pointing me to @ayysir git hub for the fix by @BeansTown106
1/17/15 - Build 4 - Fixed Browser force close in settings.
12/19/14 - Build 3 - Updated to Android 5.0.2_r1
12/15/14 - Build 2 - Switched back up to block based build for installation speed! Thanks to @hlxanthus for the 411!
12/14/14 - Build 1 - Initial build
{
"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"
}
Click to expand...
Click to collapse
Build Guide Link
Want to build this exact ROM yourself?
Here is a great build guide I wrote: [Guide][1/19/2015] Building AOSP for the Nexus 6!
Change Log
Add-Ons
Sprint Data connectivity linked by @orlzzt is HERE!
Reserved!
Hmm... I'll take this for a spin later. Thanks!
Is it safe to say with this being pure aosp shamu that it is still set to force encryption?
Also, the drawback of not doing the block style flashable is it takes several times longer to actually install via recovery.
hlxanthus said:
Is it safe to say with this being pure aosp shamu that it is still set to force encryption?
Also, the drawback of not doing the block style flashable is it takes several times longer to actually install via recovery.
Click to expand...
Click to collapse
Yes. Its pure AOSP.
Can you give me a calculation of time to install block based and file based ROM? Several times longer is a strong statement. If you could produce factual data I would appreciate.
However I am still not going block based installs because the user can take this ROM, add or remove things before it is even installed.
But I look forward to the numbers you show me! If you dont have the data that is fine. I can change the false to try in the script ota_from_tools and test it myself. Should only take a few minutes to recompile as block based.
But thanks for the input!
Took like 3-5 minutes to install your ROM and maybe 20 seconds to at most a minute to install either rastapop or cm12alpha. Honestly I thought it stalled or failed so I rebooted recovery and installed just your ROM (instead of gapps together via twrps) and it simply takes a LONG time to flash.
Great to finally see you here scrosler!!! Always great to welcome another knowledgeable developer to the forums
hlxanthus said:
Took like 3-5 minutes to install your ROM and maybe 20 seconds to at most a minute to install either rastapop or cm12alpha. Honestly I thought it stalled or failed so I rebooted recovery and installed just your ROM (instead of gapps together via twrps) and it simply takes a LONG time to flash.
Click to expand...
Click to collapse
The exact numbers your reported time can vary buy almost 66%! Thats a huge variance.
Also, you are testing differnt ROMS. For a control I need to build this exactly as it is but block based.
I will test it on my device with a high end chronograph and report my results.
Also, what recovery are you using?
Ok, I timed the file based intall, it was 2:16.08 (which was closer to your 3 minute estimate but a far cry from the 5 minute estimate)
I will build a block based ROM tonight and test to see the difference. However its still very unlikely I would change the current set up. Although I could just post both! :highfive: Win Win for everyone :good:
But once again! Thanks for your input!
scrosler said:
The exact numbers your reported time can vary buy almost 66%! Thats a huge variance.
Also, you are testing differnt ROMS. For a control I need to build this exactly as it is but block based.
I will test it on my device with a high end chronograph and report my results.
Also, what recovery are you using?
Click to expand...
Click to collapse
I can time it if that helps, or you can test yourself if you would rather. As for recovery, the only one I know of is twrp, downloaded directly via their website (only one version there) and manually fastbooted in place.
hlxanthus said:
I can time it if that helps, or you can test yourself if you would rather. As for recovery, the only one I know of is twrp, downloaded directly via their website (only one version there) and manually fastbooted in place.
Click to expand...
Click to collapse
We are cross posting. I timed it myself and it was just a hare over 2.25 Minutes. Which is not that far off from your assert of 3.0 minutes.
Im going to build the block based tonight and post it so people can have both options.
You brought a valid point. Once again, thanks for your input!
Edit: Also, wasnt trying to beat you up, I just like solid number comparisons.
Haha no worries, us old optimus s veterans need to stick together ?
Edit: if you wanted to remove the force encryption, it is a very simple fstab.shamu edit. Under the /userdata line, change "forceencrypt" to "encryptable". Looking at a few rom sources, that is how they all do it. That way if you are encrypted you will stay encrypted. If not, then it wont force encrypt you. Would save people from having to flash an alternate kernel . .
hlxanthus said:
Haha no worries, us old optimus s veterans need to stick together ��
Edit: if you wanted to remove the force encryption, it is a very simple fstab.shamu edit. Under the /userdata line, change "forceencrypt" to "encryptable". Looking at a few rom sources, that is how they all do it. That way if you are encrypted you will stay encrypted. If not, then it wont force encrypt you. Would save people from having to flash an alternate kernel . .
Click to expand...
Click to collapse
OMG!!! Optimus S? Are you serious? That was my first Android Phone / ROM!
Yeah, I know how to shut it off. But i wanted to leave this as close to pure AOSP as I could. I think I will shut it off on the next build though. I heard the encryption can slow things down a hair too.
Ok, I just got lost reading comments. Is this encrypted? If it is, does anyone mind letting me know what to do BEFORE I flash to decrypt.
Ty.
gcng said:
Ok, I just got lost reading comments. Is this encrypted? If it is, does anyone mind letting me know what to do BEFORE I flash to decrypt.
Ty.
Click to expand...
Click to collapse
You just flash a no force encrypted kernel which I basically any of them. And as @scrosler just said he may just build it into the next build.
---------- Post added at 02:55 PM ---------- Previous post was at 02:53 PM ----------
And yes, same user name over at android central, I had DanteRom that I released. ?
EDIT:
DAMN! There is no comparison from Block Build and File based build
Block build was roughly 2 minutes and 30'ish seconds
Block based build was 10'ish seconds!
Hey Scott glad you are building for the nexus 6 are you planing on a Clean Rom also? Or just keeping it aosp
scrosler said:
OMG!!! Optimus S? Are you serious? That was my first Android Phone / ROM!
Yeah, I know how to shut it off. But i wanted to leave this as close to pure AOSP as I could. I think I will shut it off on the next build though. I heard the encryption can slow things down a hair too.
Click to expand...
Click to collapse
I'd say leave it encrypted for now until faux finally makes it to the threads...from his g+ posts it seems his found a way to keep the device encrypted yet have around the speed as though it was unencrypted. And he's a very open source guy so I'm sure he'll share the magic
Well here it is... Android 5.1 build LVY47H in all its stock glory!
{
"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"
}
Preface
Stock Rooted... Busybox and init.d support already built for you!
This is based 100% on the stock Google image!
Still has the 95 Radio and bootloader but here is the actual one from the image (Flashable): LVY47H-Radio-Firmware
Thanks to @Q9Nap for the factory image.
Build Date = Tue Mar 10 01:36:04 UTC 2015
Does not enable T-Mobile WiFi calling so need to ask or state that it does.
Features
Stock
Powered by SuperSU by @Chainfire
Busybox with init.d support
No added features or mods
Persistant ADB
Decrypted boot.img
Download Odex HERE!
Download De-Odex HERE!
Hit Thanks! It cost nothing and you will feel good!
Please hit Thanks and rate the thread 5 stars!
Sharing Policy
You are free to use this ROM or any part of this ROM any way you like as long as you give proper credit! We know our work so don't try to cheat!
Consider this your permission! Please do not PM me asking if its OK to build off this ROM. Permission granted!
No, I dont know whats different. It does have an app called "Tyco". No, I dont know what it is.
Where did this build come from? Havnt even heard of it
chris6278 said:
Where did this build come from? Havnt even heard of it
Click to expand...
Click to collapse
[FXZ][OTA]Nexus 6 Recovery Flashable Fastboot Files (Unlocked Bootloader Only)
I dont know any more about it other than whats in that thread as far as how this build appeared.
scrosler said:
[FXZ][OTA]Nexus 6 Recovery Flashable Fastboot Files (Unlocked Bootloader Only)
I dont know any more about it other than whats in that thread as far as how this build appeared.
Click to expand...
Click to collapse
Oh ok thanks. I dont get why google is releasing so many different builds
chris6278 said:
Oh ok thanks. I dont get why google is releasing so many different builds
Click to expand...
Click to collapse
Could be Moto, not Google.
chris6278 said:
Oh ok thanks. I dont get why google is releasing so many different builds
Click to expand...
Click to collapse
cheep5k8 said:
Could be Moto, not Google.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
You can read my comments HERE. But yes, I believe it could be a leaked Moto build.
I flashed it and did not see any immediate difference and it is still based on the Feb Kernel.
Just flashed this build and i can confirm that it does have wifi calling. Just tried it and works great
47 Firmware-Radio is flashable?
Mervingio said:
47 Firmware-Radio is flashable?
Click to expand...
Click to collapse
Has the same bootloader and radio as all the other builds
this is awesome!
i have 2 questions. is it possible to add double tap to wake and long press back to turn screen off to the stock rom. these 2 features are so convenient to use.
thanks
I am on the E bootloader and 95r firmware. If i were to update it would this cause a brick? I am no longer on verizon and E was the best firmware/radio to use (98r). I wanna make sure my system is running up to par with att or is the bootloader the same for all the updates?
@scrosler
Its taking forever to install any System App updates like GMail or Keep for example. All other apps like Whatsapp or Facebook, etc install quickly from the Play Store, been sitting for 30 minutes now trying to get a few apps updated. Playstore gets stuck on installing and after a few minutes it jumps to the next download, which happens quite quickly, but then once again hangs around trying to get the app updated.
dhruvmalik said:
@scrosler
Its taking forever to install any System App updates like GMail or Keep for example. All other apps like Whatsapp or Facebook, etc install quickly from the Play Store, been sitting for 30 minutes now trying to get a few apps updated. Playstore gets stuck on installing and after a few minutes it jumps to the next download, which happens quite quickly, but then once again hangs around trying to get the app updated.
Click to expand...
Click to collapse
Clear play store data and try again
kidhudi
"this is awesome!
i have 2 questions. is it possible to add double tap to wake and long press back to turn screen off to the stock rom. these 2 features are so convenient to use.
thanks"
Download and flash the MCR control for Nexus 6 it has a nice little list of handy features. Also you can enable your double Tap to wake. Yes it works on this ROM I am using it now. http://forum.xda-developers.com/nexus-6/themes-apps/modpack-mcr-modpack-nexus-6-r1-t2996168
Lancez said:
Clear play store data and try again
Click to expand...
Click to collapse
Yep That Helped.
DUH... Why didnt I think of that.
dhruvmalik said:
Yep That Helped.
DUH... Why didnt I think of that.
Click to expand...
Click to collapse
Too much beer maybe? lol
JOEOZUNA4U said:
i didnt have this problem... i did a clean install
---------- Post added at 01:49 PM ---------- Previous post was at 01:45 PM ----------
looks like it works... it doesnt say wifi calling like on the HTC but when you make a call it doesnt disconnect from wifi... i turned off my cellular data and phone calling still works
Click to expand...
Click to collapse
That's not how WiFi calling works.
You will see a notifications and its not enabled by default because you need to set an E911 address. Plus, you'll see a notification at the top if it actually worked in this build, which it could possibly but it seems like its not finished yet. This build has Tycho.apk which is also called ProjectFi and requires calling/texting/voicemail/contacts permissions and such. So that's probably at least an early WiFi calling build.
Source: @askdes
Is build H 5.1.1?
Hi all.
Compatibility:
Builds from r1 to r5 are for Android 7.1 Nougat only.
Builds starting with r6 are for Android 7.1.1 Nougat only.
Builds starting with r12 are for Android 7.1.2 Nougat only.
Builds starting with r19 are for Android Pie only.
Download:
https://francokernel.app
Installation:
Flash the zip in your recovery
or
Auto-flash from FK Kernel Manager app, it's magical
Changelog:
https://francokernel.app
Scroll down, choose your device & select the latest release to see the changelog.
Source:
https://github.com/franciscofranco/marlin
Follow me on socials for updates and interesting tidbits
Twitter
FK Kernel Manager video
https://www.youtube.com/watch?v=ARdNqh71D0E
Disclaimer to moderators:
Slight OT is fine, but when users decide to act stupid they should be dealt with with the appropriate means - its really annoying for me when OT turns crazy. Please put the warning/ban hammer anytime any of you think there's lack of respect and/or too much unwanted OT crap - but if it doesn't meet this criteria let the OT posts alone. Thank you.
Cheers!
I think the only thing I haven't merged yet is controls for headphone volume boost. Other standard things are already there. Due to the unfortunate fact that we still don't have a custom recovery I haven't touched the ramdisk, so you're just flashing the actual Kernel binary (plus the device tree files that are bundled to it) through the bootloader. It's really straight forward though.
I wouldn't expect any magical battery improvements yet. Although I've made some custom patches to reduce needlessly cpu idle wakeups (don't confuse this with wakelocks, totally different things), and reducing the load average, I doubt there will be any magical enhancements. Though, I wouldn't be surprised if you get 5-10% better screen on time.
Also merged some upstream patches which gave me roughly 5-10% better Geekbench results on both single and multi threaded tests due to lower lock contention & reduced overhead.
Made sure ZRAM was properly set up too, which didn't seem to be the case by looking through the entire Google's device tree.
There's other things on my patches, but nothing groundbreaking.
Everything is in my github too. You know my approach, no bull****, so don't ask me for merge/add retarded crap.
Runs badass! Can't wait for more
Is there a feature list for this kernel? The change log 404s currently.
Nice!
Can we root with this kernel....thanks for your work
NoValidTitle said:
Is there a feature list for this kernel? The change log 404s currently.
Click to expand...
Click to collapse
Literally in the second post. I haven't added the changelog file yet.
cwalker0906 said:
Can we root with this kernel....thanks for your work
Click to expand...
Click to collapse
Yes... Why couldn't you?
franciscofranco said:
Literally in the second post. I haven't added the changelog file yet.
Click to expand...
Click to collapse
I read the second post. There isn't a feature list just says what you didn't include. I also looked at git hub and didn't see anything there either. Sorry.
franciscofranco said:
Yes... Why couldn't you?
Click to expand...
Click to collapse
Thought there was a patch that had to be made in kernel...wasn't sure
NoValidTitle said:
I read the second post. There isn't a feature list just says what you didn't include. I also looked at git hub and didn't see anything there either. Sorry.
Click to expand...
Click to collapse
I wrote a lot about what I included. I don't usually write feature lists, most of the words are just buzzwords for users to feel amazed but not actually know what they mean, so for a less biased experience I just don't have feature lists.
cwalker0906 said:
Thought there was a patch that had to be made in kernel...wasn't sure
Click to expand...
Click to collapse
Nah, you can root it.
franciscofranco said:
I wrote a lot about what I included. I don't usually write feature lists, most of the words are just buzzwords for users to feel amazed but not actually know what they mean, so for a less biased experience I just don't have feature lists.
Nah, you can root it.
Click to expand...
Click to collapse
Already running and rooted, thanks
cwalker0906 said:
Already running and rooted, thanks
Click to expand...
Click to collapse
Awesome!
Ok, I know... I am a newb! But I got a question for you Franco....
When I download the kernel I try to extract it using 7zip and get an error.
Should I not try to extract? What am I doing wrong here? Never had any issue like this before. Used your kernel on lots of devices and this is the first time I got this issue.
Anyone feel free to chime in...
{
"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"
}
-Scott
Scott said:
Ok, I know... I am a newb! But I got a question for you Franco....
When I download the kernel I try to extract it using 7zip and get an error.
Should I not try to extract? What am I doing wrong here? Never had any issue like this before. Used your kernel on lots of devices and this is the first time I got this issue.
Anyone feel free to chime in...
-Scott
Click to expand...
Click to collapse
It's not a zip, it's the Kernel binary.
Just seen this came out! Rooted and flashed FK1 Loving it so far Franco can't wait for more features! Any change of getting rid of the screen before the boot logo for it being modified? As always great work Fransisco
xReaper7x said:
Just seen this came out! Rooted and flashed FK1 Loving it so far Franco can't wait for more features! Any change of getting rid of the screen before the boot logo for it being modified? As always great work Fransisco
Click to expand...
Click to collapse
Nope not possible
franciscofranco said:
It's not a zip, it's the Kernel binary.
Click to expand...
Click to collapse
Ahhh, Thank you! I am running it now!
Sorry for being a newb, lol
-Scott
Scott said:
Ahhh, Thank you! I am running it now!
Sorry for being a newb, lol
-Scott
Click to expand...
Click to collapse
It's ok, we don't born knowning it all
The Android subreddit would always rave about your kernel during the Nexus 4 days. Excited to see future development.
To start off, credit goes to @GioBozza, @CappyT, @pioccd, @TotemFallico, @SimoIanni. They made this mod. All I did was port it to the V20.
ORIGINAL THREAD (go drop a "Thanks"): https://forum.xda-developers.com/nexus-6p/development/wakeblock-blocking-drain-late-t3526313
Next, some caveats:
Neither I nor the users mentioned above take any responsibility for anything that goes wrong with you installing this.
I have personally tested this on the H918 on the 10k firmware. I see no reason for it not to work on other variants, BUT MAKE BACKUPS!!!
This mod is unofficial, and will remain so, meaning I may not be able to update it for every release, whether that be a new Android version for the V20, or a new mod version.
This is for STOCK ONLY.
This mod requires ROOT.
Again, MAKE BACKUPS!!!!!!!!!
Instructions (READ THROUGH THEM FIRST):
Backup `/system/framework/services.jar` and `/system/framework/oat/arm64/services.odex` (The latter is only relevant for ODEXed ROMs).
Download and install the app from the linked thread.
Download the `services.jar` file attached or linked in this post.
Copy it to your device somewhere safe (such as `/sdcard/`).
Use either the command line or a root file explorer to copy the downloaded JAR to `/system/framework/`, overwriting the current one. (YOU MADE A BACKUP, RIGHT?)
Make sure its permissions are set to 0644 (rw-r--r--).
Use either the command line or a root file explorer to delete the `services.odex` file that you made a backup of I'm sure C_C.
Reboot.
(If you have TWRP 3.1.1-1, you'll have to keep the backups on your device somewhere, since it doesn't support MTP right now!)
If all went well, your phone will boot successfully and you'll have some pretty fine control over your wakelocks. If not, restore your backups using the TWRP file manager and try again.
If you have any questions about the installation process, ask here. Otherwise, ask on the linked thread.
Nice job!
Good job everyone!
Sent from my LG-US996 using Tapatalk
Excellent work! Been hoping this would get unoffiical support.
Edit: Damn, doesn't seem to boot on NotSoStock for the H918. I wonder if Tilde changed something in services.jar
@Zacharee1 nice find.
What are you using to compare before and after results of the mod?
Using the link you posted and github I've added the the mod to my rom all seems well but not sure which app will measure this best?
Also is there an app or something you are using to control which wakelock you want to block?
I tried the playstore version, but says device not supported...
Either way it doesn't seem to have any negative effects so far so I guess I'll just wait for a few days to see if there are any noticeable improvements...
Thanks for your work and contributions to this community!
Hopefully you'll still be using this device by time I finally go public with oZoP! Hopefully soon, but can't really say how much longer. Still many, many hours
stangdriver44 said:
@Zacharee1 nice find.
What are you using to compare before and after results of the mod?
Using the link you posted and github I've added the the mod to my rom all seems well but not sure which app will measure this best?
Also is there an app or something you are using to control which wakelock you want to block?
I tried the playstore version, but says device not supported...
Either way it doesn't seem to have any negative effects so far so I guess I'll just wait for a few days to see if there are any noticeable improvements...
Thanks for your work and contributions to this community!
Hopefully you'll still be using this device by time I finally go public with oZoP! Hopefully soon, but can't really say how much longer. Still many, many hours
Click to expand...
Click to collapse
I'm using Wakelock Detector Free to see which wakelocks are still happening. Some of them can't be blocked without causing systwm_server to continually crash, so you have to be careful.
The core kid is unsupported on this phone, not the app. If you swipe to the wakelocks tab, you should see a bunch.
I'm going to be on this phone for at least 2 years, so no worries there.
Aaren11 said:
Excellent work! Been hoping this would get unoffiical support.
Edit: Damn, doesn't seem to boot on NotSoStock for the H918. I wonder if Tilde changed something in services.jar
Click to expand...
Click to collapse
Did you set the permissions correctly?
d
stangdriver44 said:
@Zacharee1 nice find.
What are you using to compare before and after results of the mod?
Using the link you posted and github I've added the the mod to my rom all seems well but not sure which app will measure this best?
Also is there an app or something you are using to control which wakelock you want to block?
I tried the playstore version, but says device not supported...
Either way it doesn't seem to have any negative effects so far so I guess I'll just wait for a few days to see if there are any noticeable improvements...
Thanks for your work and contributions to this community!
Hopefully you'll still be using this device by time I finally go public with oZoP! Hopefully soon, but can't really say how much longer. Still many, many hours
Click to expand...
Click to collapse
Hi, the playstore app says "Unsupported" because it checks for official build of WakeBlock, now I am on DU wich is Unofficially supported and my home screen looks like this
{
"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 yours looks like this too you can proceed blocking wakelocks. Please refeer to this thread to see which wakelocks to block(remember that the WakeBlock app asks for the block time in milliseconds so you need to add 3 zeros to the guide's times)
SimoIanni said:
d
Hi, the playstore app says "Unsupported" because it checks for official build of WakeBlock, now I am on DU wich is Unofficially supported and my home screen looks like this
If yours looks like this too you can proceed blocking wakelocks. Please refeer to this thread to see which wakelocks to block(remember that the WakeBlock app asks for the block time in milliseconds so you need to add 3 zeros to the guide's times)
Click to expand...
Click to collapse
He changed some classpaths, so the service didn't bind. It's all working now.
Zacharee1 said:
Did you set the permissions correctly?
Click to expand...
Click to collapse
Yep. Chmod 0644
Aaren11 said:
Yep. Chmod 0644
Click to expand...
Click to collapse
Strange. If you send me the working jar, it probably won't be hard to edit, since NSS is deodexed.
SimoIanni said:
d
Hi, the playstore app says "Unsupported" because it checks for official build of WakeBlock, now I am on DU wich is Unofficially supported and my home screen looks like this
If yours looks like this too you can proceed blocking wakelocks. Please refeer to this thread to see which wakelocks to block(remember that the WakeBlock app asks for the block time in milliseconds so you need to add 3 zeros to the guide's times)
Click to expand...
Click to collapse
OP is correct... It was am error on myside and have since fixed and been blocking away those dang wakelocks!
Haven't really ever used anything that gve me control like this to pick and choose which ones! Very nice, now the problem is figuring out which ones to block! Haha
I have started lite with mainly just gms.core and will go from there.
Thank you for your work and thanks OP for bringing this here!
Awesome thank you!
Sent from my LG-H918 using XDA-Developers Legacy app
Quick update:
Don't use WakeBlock to block WifiOffDelayIfNotUsed. Your phone will reboot when connected to WiFi, disconnected from power, and put to sleep. This wakelock has been causing me some headaches, so here's an experimental JAR that just disables the wakelock altogether. Test it using the same instructions as in the OP (it does boot; I tested that far), and report any weird behavior. I won't be able to fix anything that happens because of this, but it'll be good for others to have that information.
If this goes well, I think I'll try packaging this into an AROMA installer. I've always wanted to try making one of those.
Aaren11 said:
Yep. Chmod 0644
Click to expand...
Click to collapse
Alright. I reuploaded the services.jar. Try it now.
Zacharee1 said:
Alright. I reuploaded the services.jar. Try it now.
Click to expand...
Click to collapse
Thank you! Sorry I was unable to reply yesterday. I'll give it a try
Edit: No luck unfortunately, still fails to boot. I've attached the services.jar from NSS 6.5
Just tried this on stock H910 and it couldn't get past the ATT logo. I replaced the .jar file and changed the permissions to 0644. Did I need to delete the .odex file in the .jar?
Will this work on G5?
Looks very interesting - out of curiosity has anyone had the dreaded "anx_wlock" kernel wakelock/battery drain on the V20 and managed to fix it with this?
Thanks. Works great on WETA 5.0.7 H918