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.
Related
yea thats right. kk on your jewel. If you dont know what your doing, stay away! I am too lazy to update this post for now, so here are links and let the trolling begin!
whats working you ask? just about everything and then some. Remember, some apps wont work until they are updated, so dont go poppin off on meh.
gtfo meh shirt.
recovery: http://d-h.st/SUc
cm-11: http://d-h.st/u26
gapps: http://d-h.st/eWW - 12-9-13 thanks dhacker29.
ill update this post accordingly soon, but for now, foaf.
all source is on cyanogenmod's and/or my github for the device tree and kernel.
https://github.com/CyanogenMod/
https://github.com/kushdeck/
Donations are VERY much appreciated.
deck
Donate me all teh bitcoins~!
enjoy,
-deck
Hey everybody, there's a user managed wiki, check it out, contribute if you can.
http://cm11-jewel.wikidot.com/
Hey everybody looking for help with the nightlies, or discussion about the nightlies, please go here instead:
http://forum.xda-developers.com/showthread.php?p=48316114
I AM NOT LIABLE FOR ANY CONTENT IN THE WIKI
Latest IRC Build:
2/4: http://d-h.st/7T0
Bugs:
Dock audio doesn't work unless connected through Bluetooth
FAQ:
Q1: When I try to flash the ROM in TWRP, it fails. Why?
A: You MUST flash a recovery built with an SELinux kernel in order for the ROM to flash. There are 3 I know of: One is in the OP of this thread. One is in post #2 of the OmniROM thread (thanks to xHausx). The 3rd is here, built by me with Flemmard's kernel (split from deck's version). I also have one built with CM11, available upon request.
Q2: I enabled ART and now I can't boot up my device without getting a bunch of force closes. How do I fix it?
A: Go back in time and don't enable it. But seriously, the best workaround I found is to pull the build.prop out of the ROM zip, update the runtime from libart.so to libdvm.so, and push it to the ROM while in recovery. Change permissions to 644, wipe caches and reboot. You'll be back to dalvik, and back in business.
Q3: What's the difference between these builds and Nightlies?
A: The builds posted here and on IRC will include patches that haven't yet been merged into CM, and thus will be missing from the Nightlies. deck gives us a "sneak peek" of those options first, and allows us to test and provide feedback to ensure everything is working well before being merged for the masses. That being said, remember that this is a Development thread, so if you're going to provide feedback, please make it useful.
Q4: Why are you telling me I'm posting in the wrong thread? I'm running CM11. Aren't they all the same?
A: See the above question and answer for the difference. This thread is for the builds posted by deck in the OP and in IRC. The thread for the Nightly builds is linked in Post 2.
Come hang out on IRC in #htc-evo-4g-lte if you'd like to discuss the ROM (and also, likely get trolled, lol)
ALSO, please consider donating to the devs that helped make this happen on our Zack Morris device!
[email protected]
[email protected]
[email protected]
{
"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"
}
Hell ya, thanks deck
Sent from my EVO using Tapatalk
just have to post HOLY SH*T nice work
I am so in love with you right now...
Sent from my EVO 4G LTE using Tapatalk
Hell yeah! Thank you sir.
Sent from a haunted carbon image of an EVO LTE
Oh yes. let the fun begin. Thank you.:good:
Unable to get complete download. keeps stopping at 20mb.huh?
HOLY S...!!!!!
Xmas came early this year... AWESOME... D'Ling as I speak.
Is there a separate irc room for this or same as always?
[email protected] said:
HOLY S...!!!!!
Xmas came early this year... AWESOME... D'Ling as I speak.
Is there a separate irc room for this or same as always?
Click to expand...
Click to collapse
Same room.
Ugh, I'm having some bad luck with TWRP 2630. Everything I do keeps failing. Hopefully I can get this straightened out and try it soon.
ew2x4 said:
Ugh, I'm having some bad luck with TWRP 2630. Everything I do keeps failing. Hopefully I can get this straightened out and try it soon.
Click to expand...
Click to collapse
You updated to the one in the OP, right?
I take it the topic link in IRC will now be kk only builds right?
Captain_Throwback said:
You updated to the one in the OP, right?
Click to expand...
Click to collapse
Yeah. I'm going to reflash it. It's having issues wiping the system.
Captain_Throwback said:
Stuff not yet ported over from CM10.2:
Button Settings
Notification/Status Bar Modifications
Storage Mount Swap
There's probably more, too.
Bugs:
You tell me
Come hang out on IRC in #htc-evo-4g-lte if you'd like to discuss the ROM (and also, likely get trolled, lol)
ALSO, please consider donating to the devs that helped make this happen on our Zack Morris device!
[email protected]
[email protected]
[email protected]
Click to expand...
Click to collapse
When you reference one of the unported parts being the storage mount swap do you mean that we can't mount the external SD card or we can't use the external SD at all?
LemonNinja said:
When you reference one of the unported parts being the storage mount swap do you mean that we can't mount the external SD card or we can't use the external SD at all?
Click to expand...
Click to collapse
Neither of those things. I'm talking about the feature that allowed you to swap internal for external cards so you could use the external as internal storage.
This doesn't refer to something that is broken; this was an additional feature. If it was a bug, it would be in the bugs section.
Redownloaded and reflashed everything. It's all groovy now. Thanks a ton, Deck, and Cap!
Wow. Amazing job!
Sent from my EVO 4G LTE using xda app-developers app
Captain_Throwback said:
Neither of those things. I'm talking about the feature that allowed you to swap internal for external cards so you could use the external as internal storage.
This doesn't refer to something that is broken; this was an additional feature. If it was a bug, it would be in the bugs section.
Click to expand...
Click to collapse
Woops totally misinterpreted that sorry but thanks for that
Anyone having an issue side loading apps? Keep getting a parsing error.
Hi everyone!
You may have doubted us, but here we are with a MAJOR release - Bump! Read on to learn more...
{
"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"
}
What is this?
This is Bump! A new and easy way to sign boot images for most modern LG phones so they'll boot on any locked phone.
Bump an image once, and flash it to however many phones you please.
Click to expand...
Click to collapse
How does this work?
Simply create an account on the site, click "Bump!", upload the boot/recovery images (also known incorrectly as 'kernels') and the service will automatically Bump them for you.
Click to expand...
Click to collapse
Is this project open source?
No, this project is not open source. We are however an "open" project, as we are all for transparency and user discussion. With that in mind, we'll be participating in user discussions and providing bugfixes and changelogs when possible.
Click to expand...
Click to collapse
Who made this?
Team Codefire, of course!
Bump would not be possible without the help and support of many people.
Please consider donating something to the people listed below to help them to continue to support your LG phone and to show your appreciation of all the hours they've put into this awesome unlock!
@thecubed - Paypal Donate - That'd be weird if I wrote something nice about myself here
@Shelnutt2 - Paypal Donate - This guy nearly single-handedly wrote the entire Bump site in a few days, and was stuck waiting for me to be around before we could test. He's awesome.
@IllegalArgument - Paypal Donate - Special thanks here, IllegalArgument really helped out and brought us across the finish line here. It's safe to say that we have the unlock today because of him - show him some love!
@autoprime - Paypal Donate - Generally awesome. Always helpful, always willing to test things, and a great guy to have on the team!
@AnimatronicRocketReptile - Paypal Donate - Crypto help, thanks!
@Dees_Troy - Paypal Donate - For building all these TWRP images for us, thanks so much!
Click to expand...
Click to collapse
I'm just a user, do I need this?
Most likely not. If you're just flashing ROMs, this is a tool for developers only. There is no need to Bump ROMs yourself if you're not editing anything in the kernel, recovery, or ramdisk.
Click to expand...
Click to collapse
How do I know if something is Bump'd?
Look for the word "signed" or "bumped" in the filename. We will create a new section of the site soon that allows you to verify that a file is bumped soon enough.
Click to expand...
Click to collapse
Okay, I'm a developer, and I want this now!
Great! Go here and register, and Bump away!
Code:
[URL="http://apps.codefi.re/bump"]http://apps.codefi.re/bump[/URL]
Please be sure to check the "About" section for answers to more Frequently Asked Questions!
Click to expand...
Click to collapse
Have fun, guys!
Beautiful. Thank you @teamcodefire
o.o
Is it just me or can nobody log in yet ? Getting told my info is wrong
Nexus11 said:
Is it just me or can nobody log in yet ? Getting told my info is wrong
Click to expand...
Click to collapse
They are having issues with the login.
Login fixed! Sorry about that!
Awesome! Can't wait to try out CM 11 on this phone. Just in time for the android 5.0 once it's released.
About to sign up and see if I can't get a CM11 build to complete now that I remembered to add TheMuppets vendor tree <-- Super-Derp
Its on now!!!
Sent from rotary technology Phone
What's the turn around for a Rom being bumped...I'm curious because cm nighties.
wojo797 said:
What's the turn around for a Rom being bumped...I'm curious because cm nighties.
Click to expand...
Click to collapse
I think it's as quick as upload and download.
Sent Via Morse Code (-.. .- -.)
wojo797 said:
What's the turn around for a Rom being bumped...I'm curious because cm nighties.
Click to expand...
Click to collapse
Mahapederdon said:
I think it's as quick as upload and download.
Sent Via Morse Code (-.. .- -.)
Click to expand...
Click to collapse
It is. You upload the boot.img from the ROM you've compiled, which is about 5-6 MB. In a few seconds, you get a download link for the bumped boot.img. Then reinsert that into your ROM
Never doubted you guys once. Thanks for the time and effort you and your team had put into this and continues to invest in it for our benefit.
Can't wait for A.O.S.P Roms to hit the Sprint G3 I see they have a few for Verizon and other carriers already.
The new ZV6 kernel for Sprint won't bump. It says something like "unexpected size".
It seems to be working fine so far though, so maybe @autoprime Bumped it before uploading?
TWRP has about a 5 sec delay when you first start it. Then it's fine. So I thought this might be the problem.
Thanks for all your work!
Zv6 kernel? Looks like I'm going to have to do some looking for that.
RandomPooka said:
Zv6 kernel? Looks like I'm going to have to do some looking for that.
Click to expand...
Click to collapse
If you can fix it, that would be much appreciated. I don't know if you're a member of the team. lol
Nope. I'm just curious about what changes in ZV6 can be applied to the AOSP builds to get things like NFC, BT, GPS, and the compass working
Hi guys!
You might have noticed that the Bump site is dead.
Please thank Cybojenix and EnderBlue for the kindness.
For reference, see this post and the context therein: http://forum.xda-developers.com/showpost.php?p=56991448&postcount=8
Yes, this is harsh, and yes I do feel bad about it. However, I am sick and tired of people accusing me and my team of things we're not doing, and sick of people being entitled to things that we do in our spare time.
As usual, everyone who's supported us and the team - Thank you! You're the lifeblood of this community.
Sadly though, I'm done. I'm done with Android and I'm done with rooting and unlocking phones. The G3 is the last phone I will root or unlock publicly.
Sorry guys that it had to come to this.
thecubed said:
Hi guys!
You might have noticed that the Bump site is dead.
Please thank Cybojenix and EnderBlue for the kindness.
For reference, see this post and the context therein: http://forum.xda-developers.com/showpost.php?p=56991448&postcount=8
Yes, this is harsh, and yes I do feel bad about it. However, I am sick and tired of people accusing me and my team of things we're not doing, and sick of people being entitled to things that we do in our spare time.
As usual, everyone who's supported us and the team - Thank you! You're the lifeblood of this community.
Sadly though, I'm done. I'm done with Android and I'm done with rooting and unlocking phones. The G3 is the last phone I will root or unlock publicly.
Sorry guys that it had to come to this.
Click to expand...
Click to collapse
WOW... that's about all I can say after reading what you posted and your conversation you had with them.
I just wanted to express my thanks to you and all of Team Codefire. Again, thanks for getting all of us G3 owners rooted and unlocked.
Disclaimer:
This package is for the Sprint Galaxy S5 (SM-G900P) only. Your device, your responsibility - not ours.
Do not flash this if you do not know what you are doing or have any doubts/concerns about doing something unofficial.
This is a test build so understand YMMV and any use of this is at your own risk without official support available.
Credits:
Anonymous Sources (for providing and verifying the leak's validity)
@Chainfire (CFAR Prep & Testing Coordination - See post #2)
Rwilco12 (Hosting)
Samsung/Sprint (for hopefully not coming after anyone for this leak!)
This is a test build for the Sprint S5. This will not be the OTA release and may have issues.
Nevertheless... it is Lollipop.
I've tested calls, SMS and other functions and they seem to work.
I have not tested all of the sensors and their functions.
I'm also releasing this as a full restore only so it will wipe data.
{
"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"
}
Link to build:
Full Restore Tar (in self extracting EXE) - Rwilco12
MD5 Checksum: 58cb28a69b14f0bbfe82b590301cb416
Steps to Flash:
1) Place phone in download mode.
2) Open Odin (I tested using 3.04 and 3.07)
3) Extract tar.md5 file and select in PDA slot.
4) Start Flash and wait for process to complete. (You will see 2 reboots in the process)
Additional notes and links provided in Post #2.
Root Information & Other Notes
Rooting Information
Thanks to Chainfire's assistance a CF Auto Root package is available for this build.
You can download it by clicking here.
During testing SuperSU did not pick up that it stuck properly initially.
After KNOX started throwing the warnings it finally settled in. So you may need to play with it to get it to work.
This will likely be the case until an official Lollipop build is released so again, you're warned in advance.
Other Notes:
I cannot stress this enough - these sources took a very significant risk in providing this to the public and helping verify it.
And while we're thankful for it, this is the only 5.0 leak I will post prior to an official release.
Let's not get greedy and let's not get these sources in trouble.
Reserved
This post is reserved for possible future use.
Wow, very nice release dude!
You also have this for SM-G900F?
Really want the new touchwiz thing to try a few of my apps out!
Awesome
encryptie said:
Wow, very nice release dude!
You also have this for SM-G900F?
Really want the new touchwiz thing to try a few of my apps out!
Click to expand...
Click to collapse
Unfortunately this is only US carrier... I think that for international version there is by wait again more....
Mario9662 said:
Unfortunately this is only US carrier... I think that for international version there is by wait again more....
Click to expand...
Click to collapse
Hoping someone is going to port this to sm-g900f or someone leaks a firm for the g900f
encryptie said:
Hoping someone is going to port this to sm-g900f or someone leaks a firm for the g900f
Click to expand...
Click to collapse
I hope with all my heart.....
Can someone who flashes this please post links to the SystemUI, framework, twframework, settings, contacts and dialer so that I can use them for my theme?
Thanks in Advance
I like to be on the leading edge, bleeding edge I'm a little leery of. Thank you to everyone involved with this. I cannot wait to hear if everything is working, or what is broke, this community is awesome!
Damn, waiting for G900T
@garwynn Any idea on how to deodex Lollipop apk?
Well Sammobile linked you up, so this is going to catch fire pretty quickly in the news as it'll get regurged by Android Central, AP, etc. I hope that doesn't put any pressure on your sources.
Thanks again. Was on ND4 stock, Used odin 3.09 to load this rom. So far so good. Too much white, though. Still testing stuff.
Is there anything of the new Samsung stuff included like theme choser or flow?
theoretically this version should work on international version also... both P &F have the same specs only diference from what is see is GSM bands...
Can someone upload the notocoloremoji font?
Mass reply:
smalldookie said:
Is there anything of the new Samsung stuff included like theme choser or flow?
Click to expand...
Click to collapse
Haven't tested and I'm using my last days with my spare S5 to work on AOSP projects using these blobs.
mmark27 said:
Well Sammobile linked you up, so this is going to catch fire pretty quickly in the news as it'll get regurged by Android Central, AP, etc. I hope that doesn't put any pressure on your sources.
Click to expand...
Click to collapse
Let's hope. But this is again why I said I won't support another public leak even if a source provides it. It's in the best interest of all involved.
Albe95 said:
@garwynn Any idea on how to deodex Lollipop apk?
Click to expand...
Click to collapse
Sadly no, but sure someone will be working on it soon.
Phone_Guru said:
Can someone who flashes this please post links to the SystemUI, framework, twframework, settings, contacts and dialer so that I can use them for my theme?
Thanks in Advance
Click to expand...
Click to collapse
You could get all the tools to extract these from the system.img even on Windows. simg2img is available in a jar executable, 7-zip and DiskInternals Linux Reader to open/pull the files.
encryptie said:
Hoping someone is going to port this to sm-g900f or someone leaks a firm for the g900f
Click to expand...
Click to collapse
encryptie said:
Wow, very nice release dude! You also have this for SM-G900F? Really want the new touchwiz thing to try a few of my apps out!
Click to expand...
Click to collapse
Sadly no, and word via sources is that Samsung is clamping down security. The attention this will attract will probably only tighten that grip.
My guess is the rom would work but you would have no data, modems are different.
rhadee said:
theoretically this version should work on international version also... both P &F have the same specs only diference from what is see is GSM bands...
Click to expand...
Click to collapse
rhadee said:
theoretically this version should work on international version also... both P &F have the same specs only diference from what is see is GSM bands...
Click to expand...
Click to collapse
There are some other h/w differences as we learned during CM bringup.
The ROM itself could probably run on other variants but would have dialer and a few other issues.
Someone may find a way to bring it to the other devices. Where there's a will, there's a way.
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?
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