[mod][fix][moto g3] frequecy fix for all roms and kernels - Moto G 2015 Android Development

You may have faced this bug
-Not Able to Lock Frequencies
-Not able to Change Governor
THIS IS ONLY FOR ROMS FACING THIS PROBLEM
Disclaimer
Flash this at your own risk. Developer is not responsible for what you do on your device.
Here is the Solution
Just Boot to recovery and flash this zip
Download Link
ANDROID FILE HOST - FREQFIXbyRAZORSHARP.zip
GOOGLE DRIVE - FREQFIXbyRAZORSHARP.zip
CREDITS
VARUN CHITRE( FOR HELP)

Not to be skeptical or anything but you provide no information or disclaimers with this. I see what it does If I open the zip, but has this been tested on this phone, is it for rooted phones only, etc. I have no intention of flashing this, but if I did I would not flash it in the blind without more information, like the hundreds of zips I've probably flashed before.
Sent from my GT-P5210 using Tapatalk

Tel864 said:
Not to be skeptical or anything but you provide no information or disclaimers with this. I see what it does If I open the zip, but has this been tested on this phone, is it for rooted phones only, etc. I have no intention of flashing this, but if I did I would not flash it in the blind without more information, like the hundreds of zips I've probably flashed before.
Sent from my GT-P5210 using Tapatalk
Click to expand...
Click to collapse
You want more info .. You can Open The Zip... and see....
Thread Updated..
It just deleted the powerhals.. unnecessary one... which is not needed for your device running on custom rom...

Kiran Anto said:
You may have faced this bug
-Not Able to Lock Frequencies
Click to expand...
Click to collapse
This is caused by mpdecision/perfd, not by PowerHAL. It spams the logcat with custom kernels since they disable mpdecision/perfd to be able to change CPU frequencies
Kiran Anto said:
It just deleted the powerhals.. unnecessary one... which is not needed for your device running on custom rom...
Click to expand...
Click to collapse
PowerHAL isn't just unnecessary; it checks and optimize performances (if mpdecision or perfd is enabled). It can be removed only if replaced by a hotplug (eg intelli_plug) else removing it, isn't a good idea in my opinion

Can somebody report this guy/girl! He's been going around supposedly making roms and kernels for every phone on xda. Not only have people been complaining that he gives no info he has bricked people phones

I was going to say. This screwed my mi4i. Furthermore, this problem doesn't exist on the moto g.

Thanks!
Continues to operate in 6.0?
Enviado desde mi MotoG3 mediante Tapatalk

Related

[FW 402][UB][6502/6503]YadliKernel, almost stock, slight undervolt, notification light mod

[FW 402][UB][6502/6503]YadliKernel, almost stock, slight undervolt, notification light mod
This kernel is based on Sony .402 source.
The goal is to create an almost stock kernel with recovery, battery saving modules, and eye-candies.
Attention: Users with locked boot loader should NOT flash this, even you have recovery!
The image will be written to the correct partition, but the BL will refuse to load it!
Credits goes to @DoomLord for his wonderful guide, toolchain and various tools for kernel building.
Features:
-75mv undervolt. No sysfs interface. Taking effect from powering on.
Notification light mod. Discussion thread [v2]
A new patch to correctly cap all cores. Compatible with all frequency setting apps. [v3]
TODOs:
Nothing TODO. Any suggestions?
YadliKernelV3 pre-built image download
YadliKernelV2 pre-built image download
Github repo
XDA:DevDB Information
YadliKernel, Kernel for the Sony Xperia Z2
Contributors
glocklee, twy_2000
Kernel Special Features:
Version Information
Status: Beta
Created 2014-07-08
Last Updated 2014-07-09
Hey mate, very nice to have another developer for Z2.
It is just my opinion, but isn't -75mv will create unstable system?
TheoDores said:
Hey mate, very nice to have another developer for Z2.
It is just my opinion, but isn't -75mv will create unstable system?
Click to expand...
Click to collapse
I'm testing this all the time. Seems no problem so far.
I do experience random reboots one or two times a day with -100mv for my phone.
If you find it unstable, please post it here and I'll modify the parameters.
(Well in that case I think I'd better plug the undervolt interface back in )
Thank you so much. I shall test it right away and report if I come across any issues.
Can we use this with the newest firmware?
twolfekc said:
Can we use this with the newest firmware?
Click to expand...
Click to collapse
If you are talking about .438 (is it 438 or 437? I'm not sure ), then perhaps no.
Please wait until the source code for that firmware to be released by Sony.
I have a locked bootloader, but rooted (stock. 402) and using XZDualRecovery. Can I simply flash this kernel?
glocklee said:
If you are talking about .438 (is it 438 or 437? I'm not sure ), then perhaps no.
Please wait until the source code for that firmware to be released by Sony.
Click to expand...
Click to collapse
glocklee said:
I'm testing this all the time. Seems no problem so far.
I do experience random reboots one or two times a day with -100mv for my phone.
If you find it unstable, please post it here and I'll modify the parameters.
(Well in that case I think I'd better plug the undervolt interface back in )
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2766797
In that thread, some user experience crashes beyond -12mv.
DooMLoRD said:
for me initially -72 mV was working but not stable... for now -60 mV is mostly stable, with a rare random reboot here or there
Click to expand...
Click to collapse
nreuge said:
I was nearly stable at -36 mV with a rare random reboot here or there. Now, it's seems I'm 100% stable at -24 mV and I saw elsewhere that another user was stable at -48 mV. No luck for me... Anyway, all that confirms that each device behaves differently.
Click to expand...
Click to collapse
Just for your consideration
I'm guessing this won't work on a locked bootloader (when has it ever?)
TheoDores said:
http://forum.xda-developers.com/showthread.php?t=2766797
In that thread, some user experience crashes beyond -12mv.
Just for your consideration
Click to expand...
Click to collapse
Thanks! I'll consider changing the initial values, or bring in the interface in the next version.
Meanwhile, a lot of people are testing this in a Chinese forum (I guess they're going for the LED mod not the unstable undervolt:cyclops. If any of them report crashes I'll update at once.
Also, in the next version I'll write a patch similar to "snake charmer" but works without FauxClock.
Thus you can cap the freqs with things like SetCPU.
I personally purchased both but FauxClock refuses to work without Google stuff.
And now I'm on a Chinese FW... Well
HussainQ said:
I'm guessing this won't work on a locked bootloader (when has it ever?)
Click to expand...
Click to collapse
Hold on, I'll make a recovery zip later.
The problem is that currently I don't know how.
I'm a noob in android development
glocklee said:
Hold on, I'll make a recovery zip later.
The problem is that currently I don't know how.
I'm a noob in android development
Click to expand...
Click to collapse
Well custom kernels aren't supposed to be able to work on locked bootloaders (changes to protected partition).
How did you change the notification light mod, maybe that doesn't require an unlocked bootloader.
HussainQ said:
Well custom kernels aren't supposed to be able to work on locked bootloaders (changes to protected partition).
How sis you change the notification light mod, maybe that doesn't require an unlocked bootloader.
Click to expand...
Click to collapse
The interpolation code is written in the kernel. Linear, n=16, nothing heavy.
I've already had people to test this kernel on locked BL. It did not go through BL/fastboot. Instead I adapted @DooMLoRD's installer that flushes the image directly to the corresponding mmcblk.
EDIT:
*facepalm* It did go into the partition... But locked BL refuses to load it! :/
Are we able to change individual settings in your kernel using FauxClock like DoomKernel or are all the settings hard-coded?
Not too keen on running my phone with -75mv as anthing over -24 would make my phone reboot like crazy
drknezz said:
Are we able to change individual settings in your kernel using FauxClock like DoomKernel or are all the settings hard-coded?
Not too keen on running my phone with -75mv as anthing over -24 would make my phone reboot like crazy
Click to expand...
Click to collapse
Currently no. But I'll include that feature in the next build.
Thanks for the suggestion.
It would be really nice if you put changelog for different of each version changing.
Thanks.
It's already there pal.
Sent from my L50w using XDA Free mobile app
Sorry, I missed it
-75mV is to much undervolting!
it works fine in 99.5% of the time. But under extrem high load, like CPU Prime Benchmark apps like Qualcomm Trepn Profiler start to crash.
Thats a sign for unstable undervolting.
.314 FW is out, do you think to update your kernel to this new version?

[MOD] MultiROM (sharing kernel)

I found the bug with not isolating kernel in additional roms after posting multirom here. Unfortunately I havent solved it yet. I decided to not delele this project because the rest of this works. This is useful who want to have similar rom in on tab. For example to test apps. Sorry for inconvience.
this is beta release. for p900 only.
I'll write full instruction later. For full description see http://forum.xda-developers.com/showthread.php?t=2011403
I'm not sure that everything is stable, so I dont publish source code. I dont want to distribute buggy sources. thanks for understanding.
for stock firmware only. for now. use stock frimware as primary. you can flash cm as additional.
Installation:
1. https://yadi.sk/d/RVXpEgc6c4GKo - this is modded recovery. flash via odin
2. https://yadi.sk/d/CHl8wTYYc4GMZ - patched kernel. (patched my 1.3 pro kernel)
https://yadi.sk/d/D2riVhEgc4GPP - multirom main program
flash through modded recovery patched kernel and multirom.
uninstallation:
https://yadi.sk/d/jc4uxZeCc4GRb - flash this uninstaller through recovery, then flash original twrp
known issues:
- 1920x1200 resolution in twrp
- in List Roms installed roms dont shown
- in multirom boot menu touchscreen downt work. use buttons (vol-,vol+,power)
multirom apk from play store doesnt support this release.
reserved
more reserved
bonuzzz said:
this is beta release. for p900 only.
I'll wrote full instruction later. For full description see http://forum.xda-developers.com/showthread.php?t=2011403
I'm not sure that everything is stable, so I dont publish source code. I dont want to distribute buggy sources. thanks for understanding.
Click to expand...
Click to collapse
I saw earlier that you had plans for this, but I didn't expect it to happen this quickly.
Anyway, great initiative.
WOW
@bonuzzz,
nice to see you here. Actually I bought this high end class tablet because of its specifations and over standarts. Still is the most powerful tablet in market.. But somehow it always lacked development and support of developers. Recently maybe the price is dropped so it started make owners smile little bit.
I was almost giong to change it, but still there is no powerful alternate..
I would like to be a tester of multiboot. because I would love to see ubuntu desktop in this tablet.
Thank you!
m_carleone82 said:
@bonuzzz,
nice to see you here. Actually I bought this high end class tablet because of its specifations and over standarts. Still is the most powerful tablet in market.. But somehow it always lacked development and support of developers. Recently maybe the price is dropped so it started make owners smile little bit.
I was almost giong to change it, but still there is no powerful alternate..
I would like to be a tester of multiboot. because I would love to see ubuntu desktop in this tablet.
Thank you!
Click to expand...
Click to collapse
it's not so difficult to run ubuntu desktop here, but it wiil be very big problem with drivers. I thought about ubuntu, but now I'm not going to have a deal with it. I advice you to look linux deploy
Great job
bonuzzz said:
it's not so difficult to run ubuntu desktop here, but it wiil be very big problem with drivers.
Click to expand...
Click to collapse
Here are some drivers for the GPU. I will look into it.
http://malideveloper.arm.com/develop-for-mali/features/mali-t6xx-gpu-user-space-drivers/
ESmazter said:
Great job
Here are some drivers for the GPU. I will look into it.
http://malideveloper.arm.com/develop-for-mali/features/mali-t6xx-gpu-user-space-drivers/
Click to expand...
Click to collapse
If you could get it working it would be great.
arcadia2uk said:
If you could get it working it would be great.
Click to expand...
Click to collapse
I'm currently having a lot of work with multirom, so I think I'll not have time to deal with ubuntu
bonuzzz said:
I'm currently having a lot of work with multirom, so I think I'll not have time to deal with ubuntu
Click to expand...
Click to collapse
My appreciation was actually meant for ESmazter saying: I will look into it
oops, i haven't noticed esmazter's phrase
I found the bug with not isolating kernel in additional roms after posting multirom here. Unfortunately I havent solved it yet. I decided to not delele this project because the rest of this works. This is useful who want to have similar rom in on tab. For example to test apps.
bonuzzz said:
I found the bug with not isolating kernel in additional roms after posting multirom here. Unfortunately I havent solved it yet. I decided to not delele this project because the rest of this works. This is useful who want to have similar rom in on tab. For example to test apps.
Click to expand...
Click to collapse
I was still hoping to get the minor issues resolved, notably the issue with Rom's installer are not shown in the installed ROM's section.
Any possibility of porting this to Galaxy Note 10.1 (2014)? The hardware is almost exactly identical. Really like your work, keep it up!
hhairplane said:
Any possibility of porting this to Galaxy Note 10.1 (2014)? The hardware is almost exactly identical. Really like your work, keep it up!
Click to expand...
Click to collapse
I dont have any plans to port to other devices. It doesnt fully working and I dont have any progress with it...
Do you mean the first (pre multirom install ) flashed rom kernal is the only kernal that boots regardless of the chosen rom, is multirom a separate bootloder that is chainloaded by the original bootloader? Does multirom have a config file describing the various kernals with different filenames if so can it be manually edited? Does multirom mount emulated system partition images or are their actual multiple prexisting system partions in the mbr that multirom can choose from ? What would quilify as similar roms, stock and omni are they similar enouph ?
brock28 said:
Do you mean the first (pre multirom install ) flashed rom kernal is the only kernal that boots regardless of the chosen rom, is multirom a separate bootloder that is chainloaded by the original bootloader? Does multirom have a config file describing the various kernals with different filenames if so can it be manually edited? Does multirom mount emulated system partition images or are their actual multiple prexisting system partions in the mbr that multirom can choose from ? What would quilify as similar roms, stock and omni are they similar enouph ?
Click to expand...
Click to collapse
I dont recommend to use this multirom because it has the bug with sharing kernel. So you need to use similar roms as primary and as additional. I dont have an idea how to solve it at this moment.

[P905M LTE and P905][KERNEL] STOCK compiled with SELinux setenfoce command enabled

I am not responsible for any possible bad effects which may result from using included software! You flash it on your own risk!
Probably it will work in the P905 version, because I flashed the a P905 kernel in my P905M without problems. But, as usual, it is your risk.
User esgie confirmed that it works on SM-P905 too!
STOCK compiled with SELinux setenforce enabled
Kernel base: compiled from Samsung sources without modifications (opensource.samsung.com)
Kernel ramdisk: extracted from stock image
Features: setenforce command working
WARNING!
FLASHING THIS WILL TRIP KNOX AVOIDING YOUR WARRANTY!
Known issues
WiFi gets a little screwy. To fix it edit /system/build.prop, change the parameter ro.securestore.support from true to false and reboot.
Installation
flash using ODIN (AP/PDA)
Image sha1sum
b85360a80f6205269b75d9dfabccac211a224d46
CREDITS
- Graeme Hill`s Dev Blog (http://graemehill.ca/compiling-permissive-android-kernel)
- osm0sis user Android Image Kitchen tool (http://forum.xda-developers.com/showthread.php?t=2073775)
- Samsung (opensource.samsung.com)
- esgie Kernel STOCK RELOADED (http://forum.xda-developers.com/showthread.php?t=2771469)
No one interested?
Thanks a lot. Will try it.
Sent from my GT-N7100 using XDA Premium 4 mobile app
rodpp said:
I am not responsible for any possible bad effects which may result from using included software! You flash it on your own risk!
Probably it will work in the P905 version, because I flashed the a P905 kernel in my P905M without problems. But, as usual, it is your risk.
STOCK compiled with SELinux setenforce enabled
Kernel base: compiled from Samsung sources without modifications (opensource.samsung.com)
Kernel ramdisk: extracted from stock image
Features: setenforce command working
WARNING!
FLASHING THIS WILL TRIP KNOX AVOIDING YOUR WARRANTY!
Known issues
WiFi gets a little screwy. To fix it edit /system/build.prop, change the parameter ro.securestore.support from true to false and reboot.
Installation
flash using ODIN (AP/PDA)
CREDITS
- Graeme Hill`s Dev Blog (http://graemehill.ca/compiling-permissive-android-kernel)
- osm0sis user Android Image Kitchen tool (http://forum.xda-developers.com/showthread.php?t=2073775)
- Samsung (opensource.samsung.com)
- esgie Kernel STOCK RELOADED (http://forum.xda-developers.com/showthread.php?t=2771469)
Click to expand...
Click to collapse
Hangs on boot before the Samsung logo.
Sent from my SM-P905M using XDA Premium HD app
gorcutt said:
Hangs on boot before the Samsung logo.
Sent from my SM-P905M using XDA Premium HD app
Click to expand...
Click to collapse
Hi,
I just downloaded the file from this post and checked the sha1sum against the original file that I uploaded and it´s ok. The sha1sum value is b85360a80f6205269b75d9dfabccac211a224d46. So there is no file corruption problem.
Please check if your file has the same sha1sum.
Tonight I´ll flash this file again in my tablet and verify if it works. It´s highly improbable that I uploaded the wrong file, but I´ll check flashing it.
As soon as possible I´ll update here the result of this test.
Regards,
Rodrigo.
Awesome!
Flashed, seems to boot ok on SM-P905
Great job.
Seems to be working fine! Boots as permissive and setenforce 0/1 working fine.
Great job. Now we are waiting for at least some basic overclocking and governors implementation
esgie said:
Awesome!
Flashed, seems to boot ok on SM-P905
Great job.
Seems to be working fine! Boots as permissive and setenforce 0/1 working fine.
Great job. Now we are waiting for at least some basic overclocking and governors implementation
Click to expand...
Click to collapse
Thank you very much for confirm that it works on SM-P905, I'll include this information on the first post.
If you find some WiFi issues don't forget to edit /system/build.prop, change the parameter ro.securestore.support from true to false and reboot.
Regards,
Rodrigo.
Already had the property changed in my build.prop, so i'm not exactly sure if the wifi works out of the box or not. Although I confirm that it DOES work with the build.prop modification
And by "does work" I meant both wifi and mobile radio working flawlessly.
gorcutt said:
Hangs on boot before the Samsung logo.
Sent from my SM-P905M using XDA Premium HD app
Click to expand...
Click to collapse
rodpp said:
Hi,
I just downloaded the file from this post and checked the sha1sum against the original file that I uploaded and it´s ok. The sha1sum value is b85360a80f6205269b75d9dfabccac211a224d46. So there is no file corruption problem.
Please check if your file has the same sha1sum.
Tonight I´ll flash this file again in my tablet and verify if it works. It´s highly improbable that I uploaded the wrong file, but I´ll check flashing it.
As soon as possible I´ll update here the result of this test.
Regards,
Rodrigo.
Click to expand...
Click to collapse
Hi there, I tested here and the image is working fine here. The user esgie just confirmed that too, in a P905. Please check the sha1sum of your downloaded image file.
Regards,
Rodrigo.
rodpp said:
Hi,
I just downloaded the file from this post and checked the sha1sum against the original file that I uploaded and it´s ok. The sha1sum value is b85360a80f6205269b75d9dfabccac211a224d46. So there is no file corruption problem.
Please check if your file has the same sha1sum.
Tonight I´ll flash this file again in my tablet and verify if it works. It´s highly improbable that I uploaded the wrong file, but I´ll check flashing it.
As soon as possible I´ll update here the result of this test.
Regards,
Rodrigo.
Click to expand...
Click to collapse
I probably did something wrong.
I've downloaded again and wiill try once more.
MD5 f39207bd4c45b1854372cd519942a6c2
SHA1 b85360a80f6205269b75d9dfabccac211a224d46
Thanks.
Sent from my GT-N7100 using XDA Premium 4 mobile app
As we all can see, our devices lacks of community support.
I wonder if you are the first person on the planet who managed to prepare an environment and compile P905(x) kernel succesfuly
May I ask you if have any plans to proceed with the kernel developement?
Please integrate fauxsound
esgie said:
As we all can see, our devices lacks of community support.
I wonder if you are the first person on the planet who managed to prepare an environment and compile P905(x) kernel succesfuly
May I ask you if have any plans to proceed with the kernel developement?
Click to expand...
Click to collapse
Unfortunately I don't have enough free time, so I don't have plans to work in kernel development. I did this because I was needing it to install some stuffs in my tablet and decided to share it here o XDA where I always found useful things.
If someone wants simple modifications and points some links explaining that I can try without problems.
And if someone have problems preparing an environment to compile the kernel, let me know, I'll be very happy to help.
Regards,
Rodrigo.
koko115 said:
Please integrate fauxsound
Click to expand...
Click to collapse
Do you have a link?
Honestly, I don't know what fauxsound is!
rodpp said:
Do you have a link?
Honestly, I don't know what fauxsound is!
Click to expand...
Click to collapse
Well, i'm not the one who asked this nor I have ever heard about it, but by curiousity I googled this. Got link for this app at Google Play. There are github links in app description to patches that needs to be added to kernel to make this work.
Just can't see Note Pro in officially supported devices -list and don't know can this device even be supported. There reads "Unofficially Supporting: Any Phones using Qualcomm Audio Chip WCD93xx chipsets." But I don't know which chipset NP12.2 got.
Spere said:
Well, i'm not the one who asked this nor I have ever heard about it, but by curiousity I googled this. Got link for this app at Google Play. There are github links in app description to patches that needs to be added to kernel to make this work.
Just can't see Note Pro in officially supported devices -list and don't know can this device even be supported. There reads "Unofficially Supporting: Any Phones using Qualcomm Audio Chip WCD93xx chipsets." But I don't know which chipset NP12.2 got.
Click to expand...
Click to collapse
Thanks, it seems simple if the audio chip is compatible. I'll try to include this in the kernel.
Thanks, Rodrigo for the great work!
Finally i was able to get Ubuntu running using linux complete installer.
Its a shame there's so little development for this great device.
I wish i had skills to do some.
Thanks, from Piracicaba-SP
js345 said:
Thanks, Rodrigo for the great work!
Finally i was able to get Ubuntu running using linux complete installer.
Its a shame there's so little development for this great device.
I wish i had skills to do some.
Thanks, from Piracicaba-SP
Click to expand...
Click to collapse
Yes, one of my motivations to compile this kernel was to boot Linux images too.
Regards,
Rodrigo.
Enviado de meu SM-P905M usando Tapatalk
rodpp said:
Thanks, it seems simple if the audio chip is compatible. I'll try to include this in the kernel.
Click to expand...
Click to collapse
I tried to compile the kernel with the patches sugested by the Fauxsound developer but, unfortunately, I have no success.
Probably it will be necessary more kernel modifications to compile it with the Fauxsound patches.
Enviado de meu SM-P905M usando Tapatalk
Hi,
I have a question about your kernel.
does it contains a root feature ?
I am running XXUANI1 firmware on P900 (wifi version), and have tried the auto root from Chainfire.
it does not work well (I think it was release for a previous firmware), and give a lot of random reboot.
I was thinking that may be I could flash a kernel accepting to work with su.bin
thanks for any information.
Olivier
orobin said:
Hi,
I have a question about your kernel.
does it contains a root feature ?
I am running XXUANI1 firmware on P900 (wifi version), and have tried the auto root from Chainfire.
it does not work well (I think it was release for a previous firmware), and give a lot of random reboot.
I was thinking that may be I could flash a kernel accepting to work with su.bin
thanks for any information.
Olivier
Click to expand...
Click to collapse
The kernel is for P905M/P905...

[ROM] cm-11-20150226-UNOFFICIAL-thor

Hi,
Here is CM-11 (Android 4.4.4) for the kindle fire hdx 7" (THOR). You need a rooted hdx 7" (Thor) device with a firmware < 3.2.4 (3.2.3.2 ideally) and a signed recovery.
Todo
Bluetooth not working
Wifi won't correctly load when disabled at boot, a reboot is required
Minimal headphone volume too loud -> fixed
Incorrect color format in some scenario's ? (YouTube) -> fixed
Changelogs/Downloads
cm-11-20150226-UNOFFICIAL-thor.zip
Updated to amazon 4.5.3 binaries
Fully disable radio for now (thanks Andy-Voigt)
Fix twrp fstab (enabling twrp was breaking system rom to boot)
CM sources updated to 20150226
cm-11-20150219-UNOFFICIAL-thor.zip
CM sources updated to 20150219
cm-11-20150219-UNOFFICIAL-thor.zip
fix minimal video/media volume too high (youtube...)
switch back to tablet build
CM sources updated to 20150110
cm-11-20150108-UNOFFICIAL-thor.zip
Fix thermal engine (should give better battery life and performances)
Fix a lot of proprietary services (proprietary logs, acdb-loader, ril loading ...)
Set media volume steps to 100 instead 15 (allow finer volume control essentially for jack output)
Lowered minimal screen brightness
CM sources updated to 20150108
cm-11-20150107-UNOFFICIAL-thor.zip
Build without "hacks" (add Cuber signing and custom updater-script generation)
CM sources updated to 20150107
Enable telephony (will probably not work)
cm-11-20150101-UNOFFICIAL-thor.zip
use patched boot/recovery, thanks to @vortox
fix wrong color format ! (major bug resolved)
switch to kernel sources
cm-11-20141218-UNOFFICIAL-thor.zip
minors fixes
cm-11-20141217-UNOFFICIAL-thor.zip
fix wifi not reloading
fix overlay/rotation screen tearing
cm-11-20141216-UNOFFICIAL-thor.zip
updated binaries to amz 4.5.2
properly use precompiled kernel and headers (amz 4.5.2)
fix minimal audio volume too high
add safestrap compatibility
Sources
android_device_amazon_thor
android_device_amazon_hdx-common
hardware_qcom_display-caf-hdx
hardware_qcom_audio-caf-hdx
hardware_qcom_media-caf-hdx
I'm sure the community here respects all of the work that you do. My post in the other thread was not intended to "get you in trouble". There are a set of rules that every user has to follow, regardless of their contributions to the community. That being said, when I was a newer member, I accidentally broke the rules a couple of times (nothing major) and didn't want the same to happen to someone else. (I never contacted @Divine_Madcat about your other thread, in case you were thinking I did.)
r3pwn said:
I'm sure the community here respects all of the work that you do. My post in the other thread was not intended to "get you in trouble". There are a set of rules that every user has to follow, regardless of their contributions to the community. That being said, when I was a newer member, I accidentally broke the rules a couple of times (nothing major) and didn't want the same to happen to someone else. (I never contacted @Divine_Madcat about your other thread, in case you were thinking I did.)
Click to expand...
Click to collapse
Yep i was tinking to that... so I'm also sorry. The thing is i spent a lot, lot of time on this port, and Divine_Madcat didn't even give me the time to update the first thread with the needed files/informations and ignore my pm which was an offense to me. Well i have to complies to the rules too but was a little chocked on how the thread got mad. Well, let's hope it won't be the same here. So that said i have no problem with you !
Cpasjuste said:
Yep i was tinking to that... so I'm also sorry. The thing is i spent a lot, lot of time on this port, and Divine_Madcat didn't even give me the time to update the first thread with the needed files/informations and ignore my pm which was an offense to me. Well i have to complies to the rules too but was a little chocked on how the thread got mad. Well, let's hope it won't be the same here. So that said i have no problem with you !
Click to expand...
Click to collapse
While i am sorry you are upset, it was not a slight at you at all. While i do try to keep an eye on XDA while at work, my job does come first and foremost, and i was unable to handle anything here yesterday (what can i say, 12 hour work days suck). As it was, i have literally nothing against you; to be frank, the report on the thread was the first i had even seen.
From my perspective, we had a placeholder thread, which is not allowed, so it was closed. I fully intended to reopen it, but gave my reasons above...
Anyway, i do wish you luck, and i really dont have any ill will to you...
So....
Do we have unlocked bootloader or a root exploit for amazon firmware 4.5.2 soon? And do you have plan to release another for Apollo?
Thanks
tuanda82 said:
So....
Do we have unlocked bootloader or a root exploit for amazon firmware 4.5.2 soon? And do you have plan to release another for Apollo?
Thanks
Click to expand...
Click to collapse
Nobody knows. But there are a few people working on "unlocks" (at least booting an unsigned kernel). Maybe also jcase releases his unlock (which I doubt because of legal issues).
Hi!
I have rooted Kindle Thor. How do I install this nice piece of software?
Like the Nexus rom? Currently I am on 3.2.7...
Thanks
URBANsUNITED
URBANsUNITED said:
Hi!
I have rooted Kindle Thor. How do I install this nice piece of software?
Like the Nexus rom? Currently I am on 3.2.7...
Thanks
URBANsUNITED
Click to expand...
Click to collapse
You need to be on 4.5.2 and rooted.
cyablo said:
You need to be on 4.5.2 and rooted.
Click to expand...
Click to collapse
Mmmmmhhh
Than this rom is basically usless
Who has a 4.5.2 Base and Rooted??? I would do it if I'll get the tools, no fear of a brick
Too bad. But Nevertheless Many thanks for the work and effort!
URBANsUNITED said:
Mmmmmhhh
Than this rom is basically usless
Who has a 4.5.2 Base and Rooted??? I would do it if I'll get the tools, no fear of a brick
Too bad. But Nevertheless Many thanks for the work and effort!
Click to expand...
Click to collapse
There are a few Users which do have an unlocked Bootloader, this Rom is only for these Users, as stated in the first Post.
I decided to make the rom available in case i loose interest in this device (or if i ever die soon). This way when (if) a root exploit is available then you'll be ready to use it.
Ok... So if there IS a possibility to unlock the actual fireos, please give some hints, instead of publishings Roms that one or two users can install, the rest is completely helpless...
Sent from my Nexus HDX 7 using XDA Free mobile app
openWeb74 said:
Ok... So if there IS a possibility to unlock the actual fireos, please give some hints, instead of publishings Roms that one or two users can install, the rest is completely helpless...
Sent from my Nexus HDX 7 using XDA Free mobile app
Click to expand...
Click to collapse
Sharing hundreds of hours of work is helpless/useless for you ?
You know what ? I actually spent the whole day on porting cm-10 to current exploitable kernel for YOU :/
Everybody chill , @openWeb74, i see your point @Cpasjuste , first let me thank you for all your work, I'm pretty sure its a great Rom!
What openweb said was that maybe we should concentrate our efforts in unlocking the bootloader so even greater support can come.
Unfortunately we, the rest of us common mortals (with locked bootloaders) cannot use it.
As you said, this would work if somebody would release the bootloader-unlock , so lets play the waiting game...
The thing is I'm a common mortal like you :/ Like its said on first post, unfortunately, I do not have the tools nor the knowledge to reproduce the unlock, so I share what I can.
I really have to say sorry, if you dont know how to reproduce the hack... Mea culpa. It sounded like the hack is known, but cant be made public because of copyright issues or something like that... Then we have to wait. Nothing is secure when the right person gets a hdx... I have to say, that my actual hdx was rooted with towelroot, even easier than the nexus (less button combinations ) so i didnt expect amazon to be such a **** with newer firmwares.
Sent from my LG-D802 using XDA Free mobile app
Cpasjuste said:
The thing is I'm a common mortal like you :/ Like its said on first post, unfortunately, I do not have the tools nor the knowledge to reproduce the unlock, so I share what I can.
Click to expand...
Click to collapse
Sorry for nagging you about it, but — genuinely asking — how did you do it on your device in the first place?
dear Cpasjuste, thanks for your great work, and how to install this Rom ? I am newbie, so..
OK... So you are a newbie in reading too?
Sent from my Nexus HDX 7 using XDA Free mobile app
I may eventually move to another tablet as I'm loosing interest in this device (because cm is working fine [emoji14]). Would someone be interested to get my device (not for free )?

[EOL][MOD] BlackenedMod v3.1 (Pixel 3 / Pixel 3 XL)

Introduction:
Hello everyone!
The idea to this 'project' did blossom after having an conversation with @pkgnex in the past about the general idea of creating something else that follows what he started with his PK's Tuning Script for Pixel 2 (XL) but with a twist, mainly as a complement to his own thread that you can find here, but also with a completely different vision and focus on what the script itself should achieve (and deliver) for kind of results for myself and for all of you personally, of course, that wants to try it out and use it as a "daily driver".
Shortly explained.
These scripts is created with the goal of improving both battery life and performance on our Pixel 3 (XL) devices, and after a whole range of configurations and various set-ups, I've come up with something that, in my eyes, is worth sharing with all of you so that you can try it out yourself and judge on your own, with constructive feedback on what can be improved or added in future releases - if desired. My philosophy is, and will always be, this:
If something can be improved or altered in a positive way so the average user can feel and see a difference, then go for it. Non stop.
The latest release can be found here.
Disclaimer:
This is presented as "what if". If this modification screws up or breaks anything for you, I am not the one to be held responsible. It's a free will to try out this kind of changes/modifications/addons/tweaks, just don't blame the inventors for eventual bad results and/or screw-ups.
Note: These scripts is not recommended to be modified or customized by the user.
Features:
Reduced battery consumption
Device specific enhancements for best possible balance between battery life & performance
Enabled, and fully configured, Boeffla generic kernel wakelock blocker
Disabled a lot of useless stuff at kernel level (Improves battery life as well as performance)
CPUSet improvements & optimizations
Power efficiency enhancements
Wide IO block tuning (Reduces the possibility of hiccups, lags and overhead)
Possibly other miscellaneous things I've forgotten to write down here, both big and small.
Requirements/what you need for getting these scripts fully working:
An unlocked bootloader
Your own specific choice of kernel
Latest possible version of Magisk
Busybox for Android NDK Magisk Module by @osm0sis
Patience
Installation/How-To use & abuse:
1) Download the attached ZIP
2) Extract the scripts
3) Move the scripts to the following location;
/data/adb/service.d and give it the following & needed file permissions (0775)
4) Reboot your phone, let Android boot to the launcher and let Magisk boot service do its crucial magic (takes a few seconds before the scripts is fully up and running around behind the scenes)
5) Enjoy!
Note: If you still are unsure how to do for making my kernel configuration / modification work & be up and running behind the scenes, then please read @Phalanx7621 phenomenal guide here or check out @Phalanx7621 in-depth video here. The installation method is the same for all generations of released Pixels!
Credits:
@franciscofranco for all the information on which kernel wakelocks that is safe to block
@Phalanx7621 for his phenomenal how-to guide
@Lord Boeffla for his awesome generic kernel wakelock blocker
@pkgnex for inspiring me walking into this partially unknown territory.
@flar2 for his excellent EXKM application and ElementalX Kernel
@osm0sis for his Magisk Busybox module
Everyone that I've forgotten to mention here
Telegram:
If you want to try out betas / previews of my script before they are officially released, or just hangout and chat a little, then join the official Telegram group here
To-Do list:
Optimize and properly tune things even further for best possible balance between battery life, system responsivness and performance
Contributors:
@xFirefly93
Created: 2019-01-06
Last updated: 2019-10-25
Note: The changelogs have been strictly moved to the release posts.
Thank you for this, I will give it a try. I was hoping someone would come up with a script that we can use to automate whatever we want at the kernel level. I feel like this could make the stock kernel much better as far as battery life and performance. I know you said use whatever kernel, but Do you recommend using the stock kernel for this?
freebee269 said:
Thank you for this, I will give it a try. I was hoping someone would come up with a script that we can use to automate whatever we want at the kernel level. I feel like this could make the stock kernel much better as far as battery life and performance. I know you said use whatever kernel, but Do you recommend using the stock kernel for this?
Click to expand...
Click to collapse
Of course. BlackenedMod is universal across the whole Pixel 3 (XL) line-up, so it will work more than perfect with stock kernel, if that is what you are using!
:highfive:
On 2xl there was a file wich showed that mod works. How about 3 xl?
I remember on the pixel 2 XL there would be a file formed internal storage that showed that the script was working. That doesn't seem to happen on this device?
xFirefly93 said:
Of course. BlackenedMod is universal across the whole Pixel 3 (XL) line-up, so it will work more than perfect with stock kernel, if that is what you are using!
:highfive:
Click to expand...
Click to collapse
i was using proton kernel. so i went back to stock kernel through fastboot. upon booting the white google splash screen popped for about 1 sec then my phone rebooted and i got the your device is corrupt screen. i then rebooted to bootloader and loaded twrp img file. i then rooted the stock kernel with magisk. after that i still got the your device is corrupt message but i was able to continue after that and it booted up fine. so looks like you dont want to do this on stock kernel that is not rooted. heh.
it looks like my phone keeps saying my device is corrupted. i've restarted 2 times and both times it says that and you cant get past that screen unless you hit continue. any ideas how to get this to work without the phone doing that?
blaze9090 said:
On 2xl there was a file wich showed that mod works. How about 3 xl?
Click to expand...
Click to collapse
Gordietm said:
I remember on the pixel 2 XL there would be a file formed internal storage that showed that the script was working. That doesn't seem to happen on this device?
Click to expand...
Click to collapse
For now, you have to manually create a folder in your internal storage named "logs" (without quotes) because of some security kind of thing that Google have addee which prevents "automatically" created folders to even be made at all.
Otherwise the specific output log, that tells you if the script could execute or not, won't be generated because of a non-existing path / folder.
I will though look around for a possible workaround and see if it can be added directly within the BlackenedMod script for maximal flexibility directly on-the-fly.
freebee269 said:
i was using proton kernel. so i went back to stock kernel through fastboot. upon booting the white google splash screen popped for about 1 sec then my phone rebooted and i got the your device is corrupt screen. i then rebooted to bootloader and loaded twrp img file. i then rooted the stock kernel with magisk. after that i still got the your device is corrupt message but i was able to continue after that and it booted up fine. so looks like you dont want to do this on stock kernel that is not rooted. heh.
Click to expand...
Click to collapse
You need Magisk (=root) and the Busybox Magisk module for even being able to use BlackenedMod.
Installed in Pixel 3 with Botleggers and Proton V10, at the moment everything is perfect, thanks for the work! I will report results!
Enviado desde mi Pixel 3 mediante Tapatalk
gaseoso said:
Installed in Pixel 3 with Botleggers and Proton V10, at the moment everything is perfect, thanks for the work! I will report results!
Enviado desde mi Pixel 3 mediante Tapatalk
Click to expand...
Click to collapse
Enjoy!
xFirefly93 said:
You need Magisk (=root) and the Busybox Magisk module for even being able to use BlackenedMod.
Click to expand...
Click to collapse
it looks like my phone keeps saying my device is corrupted. i've restarted 2 times and both times it says that and you cant get past that screen unless you hit continue. any ideas how to get this to work without the phone doing that?
freebee269 said:
it looks like my phone keeps saying my device is corrupted. i've restarted 2 times and both times it says that and you cant get past that screen unless you hit continue. any ideas how to get this to work without the phone doing that?
Click to expand...
Click to collapse
Try with clean flashing stock firmware.
*Deleted*
xFirefly93 said:
Try with clean flashing stock firmware.
Click to expand...
Click to collapse
that worked. i backed up my current system image and data in twrp. then did the flash-all.bat without -w. then went back into twrp and rooted the stock kernel. then went back into twrp and restored my backup. thanks a lot. will report back on how its gone after a couple days.
Telegram:
Not for going off-topic far too much now but..
If you want to hang out a little, try previews / betas of BlackenedMod for Pixel 3 (XL) before they are officially released or just want to meet a lot of awesome people from every possible corner of the woeld - then join the official Telegram group, fully dedicated to the P3(XL) line-up here.
:highfive:
Will you eventually have different versions for different kernels or are you keeping the mod universal for the pixel 3 XL?
Gordietm said:
Will you eventually have different versions for different kernels or are you keeping the mod universal for the pixel 3 XL?
Click to expand...
Click to collapse
I am keeping it universal with everything good / great / greater than greatest from every kernel organized in the same package and place.
so i followed instructions, got it all done, rebooted, i'm good to go? don't need to do anything just set it up and go right?
Is there a way to tell if this is working?

Categories

Resources