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
Related
I have finally put together a ROM for us Locked Bootloader users. I used Hogwarts COLA ROM as a base for this ROM. This is my first attempt with creating ROMS. So please bear with me if you find bugs, and let me know, so i can fix them. Thanks guys, and enjoy!
**WARNING - This has only been tested on LOCKED BOOTLOADER R800X!! Install at YOUR own risk!**
Features v1
- Replaced stock Launcher with ADW
- Replaced stock Camera with Camera Mod (use "R" button to snap pics)
- Added Notification Toggles
- Removed Carrier Name from Notification Dropdown
- Themed w/ XperainceIT "Green Acid" Theme.
- Replaced Boot Animation
Updated Features v1.1
- Updated Build.prop w/ a few tweaks (see code below for a list of tweaks)
- Added Green dialer Theme
- Changed Font to stock.
Code:
Raised JPG quality to 100%
Decreased dialing out delay
Helped scrolling responsiveness
Increased overall touch responsiveness
Raised photo and video recording quality
Signal (3G) tweaks
Net speed tweaks
Disabled blackscreen issue after a call
Fixed some application issues
Known bugs:
- Factory Reset/Data Wipe, breaks the ROM. (Working on fixing 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"
}
NOTES- ROM Currently does NOT come with Titanium Back up or Screenshot, they were on my version when i took the screen shot.
Download Link:
IT ROM.v1.1**NEW**
IT ROM v1
Installation:
- Download, then extract IT ROM.
- Place ROM into /sdcard/clockwork/backup
- Boot into Recovery
- Wipe Cache / Dalvik Cache
- Restore
Future Updates:
Version 1.2- (ETA: Undetermined)
- Add Mobile Bravia Engine
- Add script for SetInstallLocation 2 (not sure if this will work as a pre-installed feature as it requires a line command prompt, then a reboot)
- Add a Theme Chooser app for the XperianceIT Themes (this one may take me a bit, not very good at app creation)
Some themes from my Theme Thread:
(Original Theme Thread)
"Purple Haze"
"Blood Lust" w/Toggles
"Pink Passion" w/Notification Toggles
"White Elegance w/Toggles"
"Blue Void" w/Toggles
"Blue Void" w/o Toggles
If any of you have any suggestions on new tweaks, mods, or would like to see certain apps included into this ROM as system apps, please let me know.
Special Thanks:
- Hogwarts, for taking the time to teach and mentor me on building a ROM. His COLA ROM can be found HERE
Nice man! My only suggestion would be to offer a CWR ZIP to change the font to something more readable.
Sent from my R800i using Tapatalk
Clienterror said:
Nice man! My only suggestion would be to offer a CWR ZIP to change the font to something more readable.
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
Ahh man, thanks, i didnt even think about that!... lol I could add Font Installer as a system app.
Different color themes would be great.
Sent from my R800x using XDA App
iceman99393 said:
Different color themes would be great.
Sent from my R800x using XDA App
Click to expand...
Click to collapse
Good idea.... Original Post edited! Now have links to my themes from my theme thread.
Coo Tool
Downloading Now. Will update after testing.
(OFF TOPIC: I need someone to pm me and let me know the process in building and posting roms.)
Thanks. I appreciate all feedback.
XperianceIT
sent from my Xplay R800X, using XDA App!
Update.
Ok, Got the "Activity Market (in app market)not responding.
Force close or wait" a few times when first
starting it, but then seemed to striaghten up after I just waited a couple mins.
Other than that, so far all is working. Talk,Wifi,Bluetooth,GPS,, All Good.
Nice Job my man.
OK awesome. I think it has to sync all your Google info first. Other than that how you like it?
XperianceIT
sent from my Xplay R800X, using XDA App!
What does this do that cola doesnt?
Milenko2121 said:
What does this do that cola doesnt?
Click to expand...
Click to collapse
Well with a locked boot loader any "custom" ROM are all going to be about the same. Since we cant overclock, or upgrade past 2.3.3 yet. They are all just tweaked a little differently, like my ROM in comparison to COLA, has only a few minor differences... IT-ROM has the camera mod built in, has toggles built in to the theme, carrier name removed, and a few other cosmetic changes.... the next update will have tweaks built into the build.prop, adds a green dialer theme, and replaces font with stock font. This is my first attempt at playing with roms. It was more of a learning tool for me to get the basics down for removing system app, replacing system app, and what not.
XperianceIT
sent from my Xplay R800X, using XDA App!
Tip: if you want to create an update.zip, pull the /system folder and make symlinks in the update script.
Logseman said:
Tip: if you want to create an update.zip, pull the /system folder and make symlinks in the update script.
Click to expand...
Click to collapse
Well you think that but it wont work
Cola has to have /data/ to work
I'm the one who design it so trust me I know.
Once you loose data the rom is broken.
Logseman said:
Tip: if you want to create an update.zip, pull the /system folder and make symlinks in the update script.
Click to expand...
Click to collapse
Hey thats awesome info! I was wanting to do something like that but wasnt sure how to make a update.zip, and really didnt want peope to have to reflash the entire ROM again, i know how frustrating it is to have to re-do all your desktops, and widgets, and re-enter al your accounts and sync info.
Would you mind PM'ing me, or post it here, on how to make the symlinks, i am 100% unfamiliar with doing that. (im still learning all of this) Even if it doesnt work with the COLA based ROM, i'd stil like to learn this for future projects, and well, just cause its something I dont know how to do, and I ike to learn.
Hogwarts said:
Well you think that but it wont work
Cola has to have /data/ to work
I'm the one who design it so trust me I know.
Once you loose data the rom is broken.
Click to expand...
Click to collapse
I know a little bit too, don't worry. You need to keep the Setup Wizard APK which, if absent, breaks the Home button in case of a data wipe. Plus, even if you put a /data folder, it can be empty.
XIT, I think the best that you can do for the symlinks is to grab another ROM (from the Play if possible), unzip it and check its symlinks. I'm not too sure of what symlinks your ROM needs. You can see the symlinks in the update script file in the Meta-Inf folder.
Logseman said:
I know a little bit too, don't worry. You need to keep the Setup Wizard APK which, if absent, breaks the Home button in case of a data wipe. Plus, even if you put a /data folder, it can be empty.
Click to expand...
Click to collapse
wont work.
locked bootloader cant flash a whole filesystem and datasystem
thats why UK rom has to be flashed as nandroid
1-2 files with the wifimodules work because your just pushing something
but when you try to
format /system
push /system
format /data
push /data
it basicly is going to wipe out CWM recovery in the process because if ur aware the CWM resides in system folder
so yes it wont work for locked bootloader
also I wouldn't keep setup wizard because it is a costly file to keep when it's never needed
the cost is about 1.2 mb not including data if i remember correctly.
so its gone.
when you use nandroid backup you dont need it anyway
I think you're right, I forgot about where the cwm was.
Logseman said:
I think you're right, I forgot about where the cwm was.
Click to expand...
Click to collapse
ya i know because i've tried it myself
i created update .zip and the CWM would always return error
i could never get it to work as many times as i tried
I like it, very nice. Plenty of space, apps and drawer loads faster. I implamented the "adb shell, pm setInstallLocation 2, exit". That way I can choose pretty much any app to be moved to sd or installed to sd. Stable rom so far today, no issues.
Sent from my R800x using xda premium
Hogwarts said:
Well you think that but it wont work
Cola has to have /data/ to work
I'm the one who design it so trust me I know.
Once you loose data the rom is broken.
Click to expand...
Click to collapse
/data/ has never been required for me.
Sent from R800x
Hey all, I thought I would put together a quick guide on how to port modules built for other devices. Since we share the same CPU as the One X and many other phones it's possible some of the mods for them are compatible with our phones too. In this case I was wanting to give coolbho3000's overclock module a try to see if it would work.
Please keep in mind that this will not always work and it's still better to try and use a module built specifically for your setup. Using a module that's not made for your device can cause all kinds of issues and seriously affect system stability. Always make sure you read the original instructions to make sure you understand how it works and how it's intended to be used.
Neither me, XDA or the module's author are responsible for anything that happens to your device. You and you alone are responsible for your actions.
First thing you'll want to do is try to load it as is, it probably won't work but it'll at least give you a place to start. In this case I'm using the overclock module from the One X so I used:
Code:
adb push krait_oc.ko /data/local/krait_oc.ko
adb shell
su
insmod /data/local/krait_oc.ko
{
"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 it is successful it won't say anything, but there you can see it failed as expected. In order to find out why it failed we'll need to run dmesg and look for where it tried to load it.
Code:
dmesg | grep "krait_oc"
There we can see module_layout is where the issue is. What we can do now is pull one of the already installed modules off of the device and use it as a reference, in this case I used lcd.ko since it has an easy name to type. Grab your two modules and using linux run modprobe to find a value for module_layout. (If you only have Windows available skip to next step)
Code:
modprobe --dump-modversions lcd.ko
Now that we know what to look for open up the module in a hex edit and search for "module_layout." Immediately before it you will see the value that needs to be changed, but, keep in mind that it is little endian so the bytes are read backwards. In the view of lcd.ko on the right you can see the value we previously got of '37 19 bc d3' is saved as 'd3 bc 19 37'.
Change those four bytes to match and then save the module under a new name so it is not confused with the original.
Once you save the edited module its time to push it to the device again and try once more.
And success! Sometimes you'll also need to edit the module to accept the current kernel version you are using, but the process should be similar as to what's here.
So, uhhhh . . . you gonna share that modded kernel?
utnick said:
So, uhhhh . . . you gonna share that modded kernel?
Click to expand...
Click to collapse
Kernel is still the same, this is just for the modules
*sigh* I wish I knew what that meant. Can I ask to you to explain it to me please? And does this mean you have the ability to port the kernel to OC an EVO LTE?
Got overclock working fine. Great thanks Haus
Can anyone make a zip? Pretty please.
You can't make a zip. you have to mod the ko file yourself and launch it yourself.
utnick said:
*sigh* I wish I knew what that meant. Can I ask to you to explain it to me please? And does this mean you have the ability to port the kernel to OC an EVO LTE?
Click to expand...
Click to collapse
Think of modules as sort of like an add-on for kernels, except that they're saved as part of the ROM instead of on boot. I used the one-x overclock module here, but since it's not made for the evo it may not be completely stable. Plus there are other changes that need to be made to the thermal profiles according to his original post.
Ideally coolbho3000 will be willing to create one for us and officially support it. I've already reached out to him about it so hopefully we'll hear something back soon.
Hey I know quadrants don't mean much but do you think you could get us a screenshot of our phones scores when overclocked?
Thanks for the guide by the way I will definitely try this when I have time...
Red.
So glad you're here haus :thumbup:
Sent from my EVO using xda premium
it there a way to remove a module, and replace a new edited ported *.ko?
all of this is done in recovery?
if trying to replace a module should just get to modding the kernel itself?
Great guide, I've been looking for something like this. So could I use this method to get USB hosting working? I know the one x (AT&T), has a custom kernel that supports it.
XDA University is Coming! Can't wait to learn more...
Immediately before it you will see the value that needs to be changed, but, keep in mind that it is little endian so the bytes are read backwards. In the view of lcd.ko on the right you can see the value we previously got of '37 19 bc d3' is saved as 'd3 bc 19 37'.
Click to expand...
Click to collapse
That's not little endian and reading backwards is not little endian when the original is not big endian. Little/big endians are in terms of byte size orders.
Good tutorial.
exSD said:
That's not little endian and reading backwards is not little endian when the original is not big endian. Little/big endians are in terms of byte size orders.
Good tutorial.
Click to expand...
Click to collapse
Thank you, but "byte size orders?"
xHausx said:
Thank you, but "byte size orders?"
Click to expand...
Click to collapse
Byte value order. Hex value.
thanks a lot
thanks a lot for your tutorial, and congrats,
i tried your tutorial and i cant modprob on linux, i atached the screenshot of what happenz,
i try "modprobe --dump-modversions usbhid.ko" and i receive a blank line with nothing, i tried with other modules and it do the same, but for the one who was extracted from my phones modules folder, it works,
and i also have a daught, i search for "module_layout" only or any other values?
hackerse7en said:
thanks a lot for your tutorial, and congrats,
i tried your tutorial and i cant modprob on linux, i atached the screenshot of what happenz,
i try "modprobe --dump-modversions usbhid.ko" and i receive a blank line with nothing, i tried with other modules and it do the same, but for the one who was extracted from my phones modules folder, it works,
and i also have a daught, i search for "module_layout" only or any other values?
Click to expand...
Click to collapse
Make sure you have spaces between your arguments. It also depends on what value it's telling you is incorrect, it may be different depending on which one you're trying to use.
xHausx said:
Make sure you have spaces between your arguments. It also depends on what value it's telling you is incorrect, it may be different depending on which one you're trying to use.
Click to expand...
Click to collapse
i already did that i think itś something wrong with the module because i put them i the same directory and the exact same commands and it just dont work, i atached some screenshots and the modules.
thanks for helping me
hackerse7en said:
i already did that i think itś something wrong with the module because i put them i the same directory and the exact same commands and it just dont work, i atached some screenshots and the modules.
thanks for helping me
Click to expand...
Click to collapse
i just cant undestand, if someone can help me.
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.
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.