BASIC KERNEL
Features:
knox removal
adb insecure
selinux permissive
init.d support
busybox
frandom
ntfs rw support with app
PRO KERNEL
Features:
knox removal
adb insecure
selinux permissive
init.d support
busybox
frandom
ntfs rw support with app
synapse support (installs with kernel)
cpu oc/uv support
gpu oc/gpu support
battery tweaks
network tweaks
... and much more
This branch is mainly based on skyhigh kernel (@UpInTheAir)
PRO-VTFB KERNEL
The same as pro branch with vt and fb enabled support.
if doubt, do not use it.
note: booting is longer as usual
CHANGELOG:
v1.3:
- optimization and performance tweaks
v1.2:
- Synced with SkyHigh kernel 1.9
DOWNLOAD
Basic branch v1.0 https://yadi.sk/d/IYF-XNCGbbrPh
Pro branch v1.3 https://yadi.sk/d/SKdK47o1bwJTT
Pro-vtfb branch 1.3 https://yadi.sk/d/XbwusUz8bwJUQ
CREDITS
UpInTheAir, xluco, halaszk88, AndreiLux and many others
SOURCE CODE
https://github.com/bonuzzz/kernel_p900
Great a lot of people have been waiting for this will flash and test it out later tonight
Thanks for your work! Great to see more people with the right knowledge with their hands on a Note Pro.
Unfortunately I use the camera daily....I'll keep an eye on this, though, in case that gets worked out.
ExtremeRyno said:
Thanks for your work! Great to see more people with the right knowledge with their hands on a Note Pro.
Unfortunately I use the camera daily....I'll keep an eye on this, though, in case that gets worked out.
Click to expand...
Click to collapse
I'm a retired deveopler and don't mind helping out a little where I can. I've enjoyed tweaking my P900 to the max & I'm also glad to finally see some stuff coming out here on XDA for the P900 wifi version. Not much activity on any other forum for this device either. Most likely because of the price of the device and people worring about the Knox tripping issue. I noticed on another forum that someone had compiled a fully functional kernel however they too were experiencing issues with the camera. Anybody have any ideas of whats causing the camera issue? I can possibly help out with the developement of a AOSP rom, or a blazing fast slimmed down ROM. I have plenty of developement knowledge in this area, if there are any interest for one. As for the Kernel issues I'm not too familiar with the compiling however most likely could figure it out.
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
Flashed this kernel and my tablet won't boot
golfinggino said:
Flashed this kernel and my tablet won't boot
Click to expand...
Click to collapse
? I hope you made a backup of your stock kernel before flashing...
Has anyone else flashed this kernel and can confirm if it is booting or not?
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
I started from scratch and flashed the tweaked p900 rom and this kernel and now it is working great it seems to be much quicker then what it was I really appreciate your work and it makes this tablet what it should be
golfinggino said:
I started from scratch and flashed the tweaked p900 rom and this kernel and now it is working great it seems to be much quicker then what it was I really appreciate your work and it makes this tablet what it should be
Click to expand...
Click to collapse
Can you describe what happens when you select the "Camera" application. Does it force close, not launch, display some type of error. If you could provide the details of what happens, it may be possible to provide a working solution or "Work around."
Also, try installing another camera application from the Android Market and see if that application works. Maybe using another camera source will work and that could be a temporary work around till the issue us resolved. Let us know. Thanks!
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
Mine says warning camera failed
golfinggino said:
Mine says warning camera failed
Click to expand...
Click to collapse
Ok, Thanks. We'll see if we can figure this thing out...
Did you try installing another camera app from the play store and see what happens when you launch it?
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
here's my observations:
1. Samsung Knox does not get removed as claimed in OP
2. Knox FC every time something is installed and uninstalled (likely under different circumstances too)
3. front camera works perfectly fine
4. rear camera does indeed fail
5. Google camera and 3rd party camera apps fail too
6. Z Device Test still detects all the hardware properties of the rear camera (but maybe that info is retrieved from elsewhere in the /system)
7a. all logcat apps do not work. i waited about 3 to 4 minutes for each to load.
7b. I haven't used it on this tab in a long time so I don't know if kernel caused this
7c. yes, I granted SU to the logcat apps, and later verified that SU wasn't denied.
my relevant info:
p900 USA wifi-only 64gb model
P900UEU1ANC5 (XAR)
edit:
to anyone that cannot boot after installing:
1. try wiping cache and dalvik cache
2. re download and try again if above doesn't fix it
3. if above doesn't fix it and you're on NAE, try updating to ANC5 (or newer?) THEN flashing the kernel again
4. if you're on a version newer than ANC5 that might be the problem and you are out of luck until the kernel is updated for it.
don't ask me about how to update, that's your burden
Sterist said:
here's my observations:
1. Samsung Knox does not get removed as claimed in OP
2. Knox FC every time something is installed and uninstalled (likely under different circumstances too)
3. front camera works perfectly fine
4. rear camera does indeed fail
5. Google camera and 3rd party camera apps fail too
6. Z Device Test still detects all the hardware properties of the rear camera (but maybe that info is retrieved from elsewhere in the /system)
7a. all logcat apps do not work. i waited about 3 to 4 minutes for each to load.
7b. I haven't used it on this tab in a long time so I don't know if kernel caused this
7c. yes, I granted SU to the logcat apps, and later verified that SU wasn't denied.
my relevant info:
p900 USA wifi-only 64gb model
P900UEU1ANC5 (XAR)
edit:
to anyone that cannot boot after installing:
1. try wiping cache and dalvik cache
2. re download and try again if above doesn't fix it
3. if above doesn't fix it and you're on NAE, try updating to ANC5 (or newer?) THEN flashing the kernel again
4. if you're on a version newer than ANC5 that might be the problem and you are out of luck until the kernel is updated for it.
don't ask me about how to update, that's your burden
Click to expand...
Click to collapse
thanks for you post
indeed knox doesn't fully uninstall. i forgot two apks to delete.
what program do you test front camera? it is very helpful info to resolve problem
also i have problem with ntfs mount. i will solve on next update.
flashlight doesn't work
bonuzzz said:
thanks for you post
indeed knox doesn't fully uninstall. i forgot two apks to delete.
what program do you test front camera? it is very helpful info to resolve problem
also i have problem with ntfs mount. i will solve on next update.
Click to expand...
Click to collapse
stock, Google camera, and Z Device Test
edit: flashlight does work for me
edit #2: with stock, you can't get to front camera again after switching to rear, because the app will just close when the rear fails. mine was already on front, then I switched to rear and
Sterist said:
stock, Google camera, and Z Device Test
edit: flashlight does work for me
edit #2: with stock, you can't get to front camera again after switching to rear, because the app will just close when the rear fails. mine was already on front, then I switched to rear and
Click to expand...
Click to collapse
i think there is problem with permissions but i can't find where is exactly
bonuzzz said:
i think there is problem with permissions but i can't find where is exactly
Click to expand...
Click to collapse
probably SElinux
Sterist said:
probably SElinux
Click to expand...
Click to collapse
it's permissive
and camera works in stock kernel with selinux permissive.
z device test sees two cameras, so it doesn't kernel problem. back camera and flashlight dont work for me. front camera works fine. i dont have any ideas except permissions
if anyone want to help, this is a kernel without any mods https://yadi.sk/d/-RWbv8htbYW28
ps: replaced link above. logcat is working here
bonuzzz said:
it's permissive
and camera works in stock kernel with selinux permissive.
z device test sees two cameras, so it doesn't kernel problem. back camera and flashlight dont work for me. front camera works fine. i dont have any ideas except permissions
Click to expand...
Click to collapse
that might be the app not able to turn on this tab's LED
torch apps work
Okay, this has nothing to do with me since I have P905 with stock kernel. I just read this thread by curiosity and though one thing about camera. Can you open test menu anyway on that device which opens on 3G models (and phones) by typing *#0*# to dialer (P900 has no dialer right?) There you can perform some tests to device and one is to check does camera work right.
Hope this helps, or then it wont
Spere said:
Okay, this has nothing to do with me since I have P905 with stock kernel. I just read this thread by curiosity and though one thing about camera. Can you open test menu anyway on that device which opens on 3G models (and phones) by typing *#0*# to dialer (P900 has no dialer right?) There you can perform some tests to device and one is to check does camera work right.
Hope this helps, or then it wont
Click to expand...
Click to collapse
p900 doesn't have dialer
z device test detects both cameras..
i now realize why it seems much faster - i am running with interactive and fiops and it is contantly at 2000mhz no lower frequencies are being used - i though it was like this on performance not interactive - obviously the battery is not great right now lol
Related
As we now the fingerprint in new kernel work but not in ROM because the framework and binarys is incompitable for cyanogenmod ICS. So some months ago I started to port fingerprint in my free time and finaly I stoped to GfxEngine.apk error "Incorectly signed". At this point I undersood that there need to get correct signature or hack this verification down, and yes I made it yesterday(20.08.2013) . So now I had hacked GfxEngine.apk, FingerprintSensor.apk and incomplete framework for ICS from GB. (22.09.2013) We had gained fingerprint support on lockscreen whit some bugs need cleenup and bug reports
All sources and binarys for fp here: https://github.com/firecode95/
To clear all doubt what works for now:
Fingerprint sensor navigation
Fingerprint database managment
Fingerprint lockscreen set up
Fingerprint lockscreen finaly
Known bugs:
after instaling rom first boot makes fc on authentech apk then need to wait ~15 sec and press ok, and if framework is went down need reboot phone
if fp is enabled then after turing on phone need to relock phone with power button to activate fingerprint sensor
fingerprint lock setup setings section gives fc after setup and can't change lock methode anymore
Flashing:
Went from older build, just flash new build on top of it.
Went from other rom? Make full wipe and flash this then.
Fingerprint ROM's are located there, so want to test download latest build and if catch bug report it on this therad whit reproduction steps and logcat. Flash it on clean phone (full wipe).
Want to experiment and maybe make a bugfix for something build it yourself. Initialize android build enviroment(search in net just too many guides already) use official Cyanogenmod ICS source and add the local manifest download there, sync repo and type standart android building comands
Update (22.08.2013)
The finger lock now sets up right just settings apk crashes imediately after setup, and phone goes in soft reboot loop after locking phone because lock screen isn't finished and the new logcat, local_manifest add too + updated github.
Update (22.09.2013)
Today I am proud to say that fingerprint finaly works in cm-9 it's whit some bugs and doesn't show mesages about good or bad swipe in unlock screen but it works, need to swipe finger for 3 - 5 times(if that finger is in database it will work) the source will be available tomorow on my github acount.
Update (4.10.2013)
So I tryed to port it for JB but there is incompitability issues for GfxEngine.apk so need add fix in apk source but there comes dificult part, firs need reverse it to source (.java files) but its quiet difficult, I had decompiled many classes but some classes don't exactly 6 classes in booth apk's (fingerprintsensor.apk and GfxEngine.apk), I will try use different apk's but I think that it will not help and if someone want to help the JB (cm10.1) unfinished source will be available after 1 - 2 days in my github.
In attachment is some pics of what I got
The goal is to make ICS with fingerprint support and leater got port this to JB
And please do not ask or spam whit request when this will be merged in official Olympus kernel ICS rom because this is just a sketch and I am only kernel tester for new kernel. This thread is opened to got solution and every help will be higly evaluated.
Thanks go to @BravoMotorola for providing authentech SDK.
It's a great new! But i have a doubt, why use the frameworks from GB if we have the ones for ICS in AtrICS and works good?
douglasroos said:
It's a great new! But i have a doubt, why use the frameworks from GB if we have the ones for ICS in AtrICS and works good?
Click to expand...
Click to collapse
I will give you example. If we took the Settings.apk from AtrICS (leaked rom) the settings apk will crashes in 99,9% because they are system apk and is build with moto stuff not CM and will try to find things that doesn't exist in cm or if exist is diffrent resulting crash and and this is reason why the app hacking was already done.
Wrong Signature problem...
Thx. for your firecode, I know there were sample codes for GB laying on Atrix-Dev-Team, just too lazy to port it to cm-10.1
Anyway, you are saying 'invalid signature', i might help with this
Did you grab all the proprietaries directly from the leaked img??? i.e.
#fingerprint
bin/am2server
etc/am2server.pubkey
lib/libAuthUDMDrv_1750A100.so
lib/libam2app.so
lib/libam2server.so
app/GfxEngine.apk
app/FingerprintSensor.apk
The invalid signature will RING if you have a missigned GfxEngine.apk
E & M have extracted those proprietaries and made them available in Vendor git, BUT there are RESIGNED with testkey.pk8 for new ICS & JB platform
So you have to use the ORIGINAL GfxEngine.apk from the ORIGINAL leaked ICS img signed with Moto key
Hope you can make a JB port as well, Thx. in advance
Zn7mkUKzN1r8aCIV said:
So you have to use the ORIGINAL GfxEngine.apk from the ORIGINAL leaked ICS img signed with Moto key
Click to expand...
Click to collapse
I already used original moto GfxEngine.apk but it gived same error, the itself worked just whe thye used gfxservice class they crashed, and its no more actual because signature check is reversed now, if wrong signature apk goes right if right signature apk crashes . I think this comes up because in leak rom is apk named MotoSignatureApp.apk
Great work.
I hope you don't mind: https://github.com/CyanogenMod-Atri...mmit/fe050430b040e7cef6338433c543ae2e20fffff0
epinter said:
Great work.
I hope you don't mind: https://github.com/CyanogenMod-Atri...mmit/fe050430b040e7cef6338433c543ae2e20fffff0
Click to expand...
Click to collapse
I've tested AtrICS with new kernel, Fingerprint Sensor works good.
But I am not going to ask a dumb question like:
"Why don't you try to get it from Leaked Rom." cz ofc you already know it so I assume you cannot do such thing.:laugh:
status?
Firecode, is your github code completed for ics (navigation & fingerperint)? am planning to use in cm-10.1, Thx.
Nd
Zn7mkUKzN1r8aCIV said:
Firecode, is your github code completed for ics (navigation & fingerperint)? am planning to use in cm-10.1, Thx.
Click to expand...
Click to collapse
Not jet. The navigation and database administration works but finger lock screen need lot of work the resources and code itself need to be port so they looks and works like pattern lock screen. Gingerbred is quiet different lock functions and the time that need to spent for this is next problem because I am quite busy in these days.
Zn7mkUKzN1r8aCIV said:
Firecode, is your github code completed for ics (navigation & fingerperint)? am planning to use in cm-10.1, Thx.
Click to expand...
Click to collapse
I though epinter already included this stuff in the cm-10.1 repo?
ravilov said:
I though epinter already included this stuff in the cm-10.1 repo?
Click to expand...
Click to collapse
They just included hacked apk's but not android core framework for fingerprint, in my pc is scrach for cm10.1 but there thing go in new level from just dedicated lock screens they are converted to lock widgets and source for it is took from ics so to build cm10.1 from ginger fp code first need to make ics code.
I just posted this to cm10.1's thread, but i think it fits here as well
https://www.youtube.com/watch?v=eZUSBCZZA6c
Thanks firecode95 for your hard work!
Sent from my MB860 using xda app-developers app
andresrivas said:
I just posted this to cm10.1's thread, but i think it fits here as well
https://www.youtube.com/watch?v=eZUSBCZZA6c
Thanks firecode95 for your hard work!
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
nice i installed it but my fingerprint sensor refuses to work at times... i seriously dont know why :/ it works well while charging mostly but after i unplug it no response
So the problem with not responding sensor isn't solved by using the ported libs? It was my last hope for a properly working fingerprint sensor
johnannis said:
So the problem with not responding sensor isn't solved by using the ported libs? It was my last hope for a properly working fingerprint sensor
Click to expand...
Click to collapse
Take into consideration that those are GB libs hacked to work on a OS 3 releases above, like triying to run win 98/me drivers on windows 7
johnannis said:
So the problem with not responding sensor isn't solved by using the ported libs? It was my last hope for a properly working fingerprint sensor
Click to expand...
Click to collapse
Forget jcrahul message, I think your answer is here:
firecode95 said:
Not jet. The navigation and database administration works but finger lock screen need lot of work the resources and code itself need to be port so they looks and works like pattern lock screen. Gingerbred is quiet different lock functions and the time that need to spent for this is next problem because I am quite busy in these days.
Click to expand...
Click to collapse
Fingerprint naviguation: OK
Fingerprint lockscreen: needs lot of work because "resources and code need to be ported"
I know it but leaked ics framework isn't working properly, IF the ported libs n framework don't work properly either, that may means the problem is on newer versions of Android and their hardware management
johnannis said:
So the problem with not responding sensor isn't solved by using the ported libs? It was my last hope for a properly working fingerprint sensor
Click to expand...
Click to collapse
How do you mean not responding fp sensor? The seansor works fully just need lot of work in fp source integration for lock screen. And in leak rom isn't any problems with fp. If you had problems it culd be due hardware, try change fp sensor.
P.S
I think that I litle misunderstood you and this is more for @jcrahul
I realy need development account acces for authentech or documentation with SDK's for fingerprint, it's most important for now, because just trying figure out from code how all works is hard and time compsuming process. So please anyone who has this try to give a helping finger
Hmm, so you say that this not responding issue doesn't affect your device?
In mine this issue really exists and on some others too. It's like you don't even swipe your finger. And it happens as said above, when it shows up the only way to stop it is to plug in the charger, and most of the times after next deepsleep it shows up again.
For example, one day I tried using fp and worked well from the morning till the afternoon (when I got home to charge it). But after removing the charger it showed up.
I think I had go back to GB to test it but I ll do it again.
EDIT: So I went back to GB rom. Unlikely for my ATRIX but likely for the project the issue is still here. So it must be hardware related,I ll sent it for service (its still in warranty )
Update
The ROM manifest and source updated. The testing can start now and if found a bug please repot it
CM12.{0,1} (Lollipop) official/unofficial builds for the Droid 4
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.0/5.1 (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at any of us for messing up your device, we will laugh at you.
* Collectively, and at the same time.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review.
These are WIP builds of porting CM12.{0,1} to the Droid 4 (and also other devices using the same device/motorola/omap4-common-infrastructure). They probably won't work, so don't expect too much. Use on your own risk!
Builds:
Last official build:
http://droid.cs.fau.de/cm-12.1/official/
Old manual builds:
http://droid.cs.fau.de/cm-12.0/pre-alpha-test/new_safestrap/
Changes (only device/family specific, CM base is always synced before build and contains more changes):
2015-04-16:
Switched CM build-target, new nightlies will now be 12.1: http://review.cyanogenmod.org/#/c/94693/
2015-02-01:
No more unofficial builds! See: http://review.cyanogenmod.org/#/c/87596/
2015-01-28:
Mobile data fixes
Remaining com.android.phone crashes on VZW finally fixed (thanks @joojoobee666)
2015-01-24:
Fixed sw-keyboard popup when hw-keyboard is used (thanks @joojoobee666)
Fixed reboot to recovery
Fixed sepolicy for whisperd (dock service)
2015-01-22:
Fixed su-permissions
Crashes on Verizon most likely fixed, please report back
2015-01-20:
Fixed flashlight
2015-01-18:
SELinux updates.
This requires manual action for applications to continue being able to access their own files when upgrading from 2014-01-14 or 2014-01-15 (older versions are fine)!
Due to SELinux-bugs in 2014-01-1{4,5}, you have to relabel your data-partition on the first boot when upgrading from 2014-01-14/-15. This only needs to be done once. To do this, enable adb/usb debugging and grant root to adb (both in developer settings) and execute via an adb shell:
Code:
su -c 'for i in /data/*; do echo "${i}"; restorecon -DFrv "${i}"; done; sync; reboot'
2015-01-1{4,5}:
More fixes for {,umts_}spyder
sepolicy updates
GSM fixes
notable CM changes: su integration fixed
2015-01-11:
Updated SELinux policies (mostly for spyder/umts_spyder)
Added kernel stability fixes
Video decoding fixes
2015-01-09:
Enabled SELinux enforcing
Add SELinux-policies for motorola services
Enable ro.telephony.get_imsi_from_sim on VZW devices (thanks @joojoobee666)
2015-01-02:
Sync CM changes
2014-12-23:
Fixed stock camera
2014-12-22:
Sync CM changes
Fix build due to P2P changes (fix pushed into CM)
Enabled security for adb (keys/not root by default)
2014-11-30:
Added APN fixes for CDMA/LTE
Enabled multiuser mode (might not work yet)
Last update for a couple of weeks
2014-11-27:
Fixed graphics glitches
2014-11-26:
Fixed HW video-decoding
Enabled doze mode (no pickup sensor in the devices!)
CM resync as always
2014-11-23:
Probably fixed mobile data on LTE
Fixed WiFi-tethering
2014-11-22:
Requires a recovery supporting SELinux
What's working:
Phone (tested on Verizon and on GSM/UMTS in Europe)
Mobile data (at least on GSM/UMTS in Europe)
WiFi
WiFi-tethering
GPS
Camera
Playback of DRM-protected content (using Widevine from OnePlusOne)
What's not working:
Probably most everything else, including, but not limited to:
Some connectivity issues (should be solved now)
Data encryption
Gapps (CM-12.0):
Dhacker29 provides gapps for Lollipop:
http://d-h.st/YQG
http://d-h.st/jzr
http://droid.cs.fau.de/cm-12.0/gapps/ (Mirror)
Gapps (CM-12.1):
https://github.com/cgapps/vendor_google/releases/
Installation:
You need a new recovery supporting SELinux
An updated Safestrap (3.75) which supports SELinux can be found here: https://github.com/stargo/android_packages_apps_Safestrap/releases/tag/v3.75
Please read the instructions on how to install this version and follow the order of the steps in it.
GSM users:
To use this CM12.{0,1}-ROM on GSM-networks you should install Mentor.37's GSM patch
Source / Repositories:
maserati device-support: https://github.com/CyanogenMod/android_device_motorola_maserati
omap4-common device-support: https://github.com/CyanogenMod/android_device_motorola_omap4-common
omap4-common kernel: https://github.com/CyanogenMod/android_kernel_motorola_omap4-common
local manifest to build cm-12 for the Droid 4: http://droid.cs.fau.de/cm-12.0/pre-alpha-test/new_safestrap/local_manifest.xml
XDA:DevDB Information
CM 12.{0,1} on Motorola Droid4, ROM for the Motorola Droid 4
Contributors
stargo, Hashcode, Dhacker29
Source Code: https://github.com/CyanogenMod
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: No Longer Updated
Created 2014-11-23
Last Updated 2016-02-16
thank you @stargo, I am so pleased to see this thread, I was wondering when this thread is going to appear. Looks like I will continue to cling onto my droid 4 for a while, no virtual keyboard can beat a droid 4 keyboard.
Is data encryption enabled by default like on the nexus 6? I read that it greatly reduces the performance of the device. I meant this: http://www.xda-developers.com/android/disable-data-encryption-nexus-6/
Once again, thank you so much for your efforts in keeping this device alive.
sharptv said:
thank you @stargo, I am so pleased to see this thread, I was wondering when this thread is going to appear. Looks like I will continue to cling onto my droid 4 for a while, no virtual keyboard can beat a droid 4 keyboard.
Click to expand...
Click to collapse
Is data encryption enabled by default like on the nexus 6? I read that it greatly reduces the performance of the device. I meant this: http://www.xda-developers.com/android/disable-data-encryption-nexus-6/
Click to expand...
Click to collapse
No, data encryption is not enabled by default (and still doesn't even work for us).
Cheers,
Michael
Flipping sweet thanks y'all rock i love xda
Cast Screen
Hey stargo. thanks a lot for this! :good:
The 'Cast Screen' under settings pull-down menu is not working. It does not find any of the chromecasts that I have nearby.
Not a big deal, and not a priority at all for me, but just wanted to let you know.
Thanks again!
G'day,
just wanted to confirm the procedure for updating SafeStrap, since some people have CM11 in their stock slot:
in the first step (when you say 'go back to stock'), are you saying simply to boot the stock slot, regardless of ROM (since once SS is unistalled the 'slots' don't exist)?
Or do you mean boot to stock ROM, in stock slot?
I'm guessing it's the former, but I'd like to be sure before taking the plunge =)
thanks for your work! I gave the 2011 version a run over the weekend, it worked pretty well all things considered =)
gabhroo123 said:
Hey stargo. thanks a lot for this! :good:
The 'Cast Screen' under settings pull-down menu is not working. It does not find any of the chromecasts that I have nearby.
Not a big deal, and not a priority at all for me, but just wanted to let you know.
Thanks again!
Click to expand...
Click to collapse
May not ever work, IIRC, chromecasting the screen requires hardware we just don't have. :[
Shobai said:
G'day,
just wanted to confirm the procedure for updating SafeStrap, since some people have CM11 in their stock slot:
in the first step (when you say 'go back to stock'), are you saying simply to boot the stock slot, regardless of ROM (since once SS is unistalled the 'slots' don't exist)?
Or do you mean boot to stock ROM, in stock slot?
I'm guessing it's the former, but I'd like to be sure before taking the plunge =)
thanks for your work! I gave the 2011 version a run over the weekend, it worked pretty well all things considered =)
Click to expand...
Click to collapse
assuming that cm11 is currently installed in your stock slot and you want to update to the new test safestrap by stargo:
uninstall the existing safestrap using the original safestrap, for instance, if the existing safestrap is 3.73, you should install safestrap 3.73 and uninstall the recovery.
DO NOT REBOOT YOUR PHONE IN THE PROCESS
after you have uninstalled the existing recovery, uninstall safestrap(3.73), and then install the new safestrap by stargo, and install the recovery.
your safestrap is now updated, and nothing will be wiped.
YOU MUST NOT REBOOT YOUR PHONE DURING THE PROCESS, you can only reboot after a recovery has been installed.
hope you find this useful
thelolotov said:
May not ever work, IIRC, chromecasting the screen requires hardware we just don't have. :[
Click to expand...
Click to collapse
It need some kernel changes... but it should work...original gnex have the same cpu/gpu and they make it work... @lucize was seeing that but i dont know what happend with that
---------- Post added at 07:38 AM ---------- Previous post was at 07:37 AM ----------
By the way....thanks michael for your great work!...please make a donation link to send you some beer money!
Cheers, sharptv, much obliged =)
gabhroo123 said:
The 'Cast Screen' under settings pull-down menu is not working. It does not find any of the chromecasts that I have nearby.
Not a big deal, and not a priority at all for me, but just wanted to let you know.
Click to expand...
Click to collapse
Yes, our GPU driver does not support WFD. And in contrast to the GNEX, Motorola added much stuff to our version, so it's not easy to sync it back with the upstream kernel. Last time I tried that, I ended up with a non-working display and couldn't figure out why...
Shobai said:
just wanted to confirm the procedure for updating SafeStrap, since some people have CM11 in their stock slot:
in the first step (when you say 'go back to stock'), are you saying simply to boot the stock slot, regardless of ROM (since once SS is unistalled the 'slots' don't exist)?
Click to expand...
Click to collapse
Just boot to whatever you currently have installed in the stock slot. And I have to underline what @sharptv said, never reboot your phone in the process (it might work when you have the stock ROM in the stock slot, but it will surely break in every other case).
Cheers,
Michael
Will cm12 be pre-rooted in future? I can't seem to find anything solid on this, hopefully someone will be able to shed some light on this.
This App Camera work fine: https://play.google.com/store/apps/details?id=com.radcam.camera
---------- Post added at 11:34 AM ---------- Previous post was at 11:31 AM ----------
sharptv said:
Will cm12 be pre-rooted in future? I can't seem to find anything solid on this, hopefully someone will be able to shed some light on this.
Click to expand...
Click to collapse
See this thread: http://www.xda-developers.com/android/supersu-beta-lollipop-root-stock-kernel/
Download and install with recovery
I can confirm that at least on my phone that LTE is working. Great work .
flash these zips in recovery for root i got the from my nexus 7 root toolkit
HOPE IT WORKS FOR YOU :good::cyclops:
TheXG6HD said:
I can confirm that at least on my phone that LTE is working. Great work .
Click to expand...
Click to collapse
Yay! Thanks for confirming
It is a really bad hack, but if it works... http://review.cyanogenmod.org/78845
Cheers,
Michael
stargo said:
Yay! Thanks for confirming
It is a really bad hack, but if it works... http://review.cyanogenmod.org/78845
Cheers,
Michael
Click to expand...
Click to collapse
Data doesn't come up on its own, still needs some prodding (selecting the APN) and will go out randomly. Still not ready for prime time, sadly.... :<
It does come up a lot quicker, however.
thelolotov said:
Data doesn't come up on its own, still needs some prodding (selecting the APN) and will go out randomly. Still not ready for prime time, sadly.... :<
It does come up a lot quicker, however.
Click to expand...
Click to collapse
That's VZW weirdness
But if it comes up, then data is actually passing? Because that is what my patch was intended to fix. Before that the data-indicator would show up, but data would not actually get transmitted...
Can you probably send me the output of "ip route list" and "ip addr list" when LTE data is connected?
Would be interesting to see, what is actually happening now. I can only guess from here...
Regards,
Michael
stargo said:
That's VZW weirdness
But if it comes up, then data is actually passing? Because that is what my patch was intended to fix. Before that the data-indicator would show up, but data would not actually get transmitted...
Can you probably send me the output of "ip route list" and "ip addr list" when LTE data is connected?
Would be interesting to see, what is actually happening now. I can only guess from here...
Regards,
Michael
Click to expand...
Click to collapse
LTE was working on first build, just took 10+ mins to connect then worked good.
Sent from my XT907 using Tapatalk
stargo said:
That's VZW weirdness
But if it comes up, then data is actually passing? Because that is what my patch was intended to fix. Before that the data-indicator would show up, but data would not actually get transmitted...
Can you probably send me the output of "ip route list" and "ip addr list" when LTE data is connected?
Would be interesting to see, what is actually happening now. I can only guess from here...
Regards,
Michael
Click to expand...
Click to collapse
The deal is, the data works at first, then at random intervals it breaks and needs to be manually reset. I'm travelling right now so I can't really risk using CM12 right now, but I'll get you some logs when possible. JJB is having the same issue, I'll ask him to try and get you some details.
Make this pretty later
You just made my day
Sent from my Nexus 6
I just confused myself. Should i be flashing the bootloader, radio, etc from a nexus factory image and then flash omni? I have been using 20150605 build without doing this. Should i do this for the nightlies?
subterfugium said:
Code:
I:operation_start: 'Flashing'
Installing '/sdcard/Download/omni-5.1.1-20150623-shamu-NIGHTLY.zip'...
Checking for MD5 file...
MD5 matched
Verifying zip signature...
I:read key e=3 hash=20
I:1 key(s) loaded from /res/keys
I:comment is 1477 bytes; signature 1459 bytes from end
I:failed to verify against RSA key 0
E:failed to verify whole-file signature
E:Zip signature verification failed: 1
Error flashing zip '/sdcard/Download/omni-5.1.1-20150623-shamu-NIGHTLY.zip'
I guess zip verification fails because of test-keys or what does that zip verification stand for?
Click to expand...
Click to collapse
Honestly, I've never used zip verification for all the years I've been flashing ROMs and have never had any issues.
I'm probably wrong but.. My theory is that packed somewhere inside the zip you are trying to flash lies a key, which is compared next a second key once extracted. If they don't match it throws an error and aborts the operation.
Sent from my Nexus 6 using XDA Free mobile app
I've never used zip verification for this exact reason, and therefore have never looked into it. This sounds like something for the TWRP thread that @Dees_Troy could answer maybe.
Does anyone have a rundown of what this Rom has to offer beyond stock aosp? The Rom OP is a bit bare of info. Thanks
The Rom OP is a bit bare of info. Thanks
530farm said:
Does anyone have a rundown of what this Rom has to offer beyond stock aosp? The Rom OP is a bit bare of info. Thanks
Click to expand...
Click to collapse
Off the top of my head... battery icon customization, volume match orientation, volume wake, screenshot delete, advanced reboot menu, hide usb debugging icon, ambient display customization. Also, Omni is the only AOSP ROM where I don't get force closes when taking multiple HDR+ pictures in a row without pause.
Completely stable device functionality with whatever you see on gerrit :good:
I will make a "features list" tomorrow
I saw that the past few builds uploaded were all 0mb. Just wondering what's going on until the builds resume?
Gandalf said:
Completely stable device functionality with whatever you see on gerrit :good:
I will make a "features list" tomorrow
Click to expand...
Click to collapse
Not sure if feature requests are allowed or not, if not then just ignore this..
But I was wondering if the 5 second home button delay on app launchers (such as Swipepad) is something that may be removed? That'd make navigating the phone much quicker for those of us who do use app launchers.
I saw opendelta mentioned in the main thread but I haven't seen any indication it exists within the ROM. Am I just missing it?
Ngo93 said:
Not sure if feature requests are allowed or not, if not then just ignore this..
But I was wondering if the 5 second home button delay on app launchers (such as Swipepad) is something that may be removed? That'd make navigating the phone much quicker for those of us who do use app launchers.
Click to expand...
Click to collapse
jira.omnirom.org :good:
glockliberty said:
I saw opendelta mentioned in the main thread but I haven't seen any indication it exists within the ROM. Am I just missing it?
Click to expand...
Click to collapse
Updates to opendelta have not been merged yet
I am certainly interested in giving OmniRom a try. A couple of questions...
First, I'm attempting to download the Omni 5.1.1 20150725 Nightly (newest as of this writing) and the download is going exceptionally slow (20-30KB/s) on the official dl.omnirom.org mirror. Is there an issue with the server at current or an up to date mirror?
Next, is there an overall feature list for Omni (on Nexus 6)? Many ROMs place a list of their main features as well as any other ROMs/kernels they incorporate (ie based on CyanogenMod 12.1, with latest CM12.1 commits added on every update etc..)).
Thank you!
RanceJustice said:
I am certainly interested in giving OmniRom a try. A couple of questions...
First, I'm attempting to download the Omni 5.1.1 20150725 Nightly (newest as of this writing) and the download is going exceptionally slow (20-30KB/s) on the official dl.omnirom.org mirror. Is there an issue with the server at current or an up to date mirror?
Next, is there an overall feature list for Omni (on Nexus 6)? Many ROMs place a list of their main features as well as any other ROMs/kernels they incorporate (ie based on CyanogenMod 12.1, with latest CM12.1 commits added on every update etc..)).
Thank you!
Click to expand...
Click to collapse
The server is probably being slow. They just upgraded storage/cleaned it up a few days ago and it has been significantly faster, it might be your connection to the server or something else.
As far as a list of features, there isn't one to my knowledge but you can certainly check on gerrit to see what's been merged recently. Just flash it and see for yourself: highfive:
Does this rom have layers?
Omnirom 5.1.1 nightly sudden reboot+supersu freeze+bluetooth headset bugs
I installed Omnirom 3days ago and have to say; nice stuff. runs fluid, batterie's fine and overall i like user experience. BUT
I'm experiencing some bugs.
first of all sometimes there just are random sudden reboots. On stock rom this happened from time to time when battery was below 30% or something so i thought there has to be a powersaving feature or something in kernel that don't works correct.
Then i flashed TWRP+Omnirom and those sudden reboots started happening randomly; regardless of battery.
I googled and found that could be some setting that adapt display brightness(???) and/or some apps bugging/conflicting. and, from previous experience, i know that this could also be a hardware/battery failure(please not; can't send my phone back right now as i need it daily for work and my N5 has a broken touch )
i tried disabling that display feature and also installed and tested if 'Lux' has any impact on that as it, basically, does the same but no change.
i factory reseted my device multiple times and tried to find out what APP could force this but... right now there's only the bare minimum(contacts+ / messages+ / aquamail / maildroid / todoist /calengoo /business calender pro and google stock apps)and still same problem. sometimes even while calling what's very embarassing when having an important customer on phone ...
I gonna try Zen Kernel next just to see if different kernel with different cpu scheduler COULD make any difference.
Then the second bug is my bluetooth headset(Plantronics M165). Can't get it to pair. Before Omnirom this worked very well as it should. Now, most of time he finds nothing and sometimes he finds a mac address of the headset but not the name. Other bluetooth devices are working fine and the headset's still working perfectly well on my gf's HTC M8. Anyone any ideas?
Last bug i experienced is SuperSU. Always an app needs root i can't get SuperSU intercept my choice. I click on allow or deny but nothing happens and after 10seconds superSu autodenies(or allows; depends on settings )right after factory reset supersu just works fine but suddenly stops working. root's still there as i can perfectly tell supersu what to do in its settings. Only the on demand root question can't be answered. uninstalling/reinstalling supersu didn't change anything. It doesn't matter if i install supersu by playstore or by zip through recovery. also unrooting and rerooting doesn't help. only a factory reset helps; for a while.
I don't want to change my Superuser managment as i paid for the pro version ...
Hope to find some help here as it's one of my fav places for everything smartphone related since back in my tytn days
so much knowledge in here.
keep up the good work
update:
sudden Reboot Problem solved, Same for superSu Problem.
just the Bluetooth problem's still there. flashing back to Stock resolves the issue but... stock and I really start liking omnirom...
anyone any ideas ?
Sent from my Nexus 6 using XDA Free mobile app
nightfly.0684 said:
update:
sudden Reboot Problem solved, Same for superSu Problem.
just the Bluetooth problem's still there. flashing back to Stock resolves the issue but... stock and I really start liking omnirom...
anyone any ideas ?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
M builds will be ready soon enough :good:
great news
Do we get the Update for M through opendelta or is a factory reset + reflash needed?
and if i understand right you assume that the Bluetooth Problem should be gone with M?
would be nice as, right now, I sometimes have to pick up important calls while driving ... and... i don't like that at all....
would try the homemade M build IF i wouldn't need it daily for work. about time to repair my n5 i guess
Sent from my Nexus 6 using XDA Free mobile app
New build up at sx.ix5.org, use version 2018-10-30.
Changelog here: https://sx.ix5.org/changelog.html
Install guide: Flashing AOSP on Xperia XZ
XDA:DevDB Information
AOSP Pie based on Sony Open Devices Project, ROM for the Sony Xperia XZ
Contributors
local__hero, fastbooking, oshmoun
Source Code: https://git.ix5.org/felix/local-manifests-ix5/src/branch/ix5-customizations
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: .184 / .192
Based On: AOSP
Version Information
Status: Nightly
Created 2018-11-09
Last Updated 2019-05-17
Reporting bugs
Important: Read the bug list before posting. Anyone can add bugs to the list, just follow the rules.
If you have questions, ask them in this thread: Xperia XZ Pie ROMs Questions and Answers Thread
Don't make me ask you for logs every time!
I will repeat the rules again here:
Rules:
New bugs must include version where error popped up and which oem version you are using
Only reproducible errors
Should include adb logcat (linked in a pastebin service like https://del.dog)
Must include clear description what is wrong
If it is a visual/SystemUI bug, only report it here
If it is an internal bug(e.g. fingerprint crashes device), report it to the Sony bugtracker as well!
Always try to fix the bug yourself first! Then submit a pull request to Sony
Must search if error has already been reported (bug tracker, this document, dev buglist)
If you've reported the issue somewhere else already and just want to track it here as well, add a link
Before reporting a bug, always make sure to isolate it. That means, wipe everything, install only the ROM without GApps and Magisk and see if the problem still exists. Only then report the bug!
---
If you have questions, ask them in this thread: Xperia XZ Pie ROMs Questions and Answers Thread
---
In 9.11
1. Everything still works
2. Charging with plugged at screen off works
3. On gcam portrait mode and night photo gives purple glitched image
And phone seems to be faster.
Bug: 9.11 with oem v2- Clean install
- Hotspot not working
- Phone call issue - Mic and speaker not working, cannot hear anything or say anything << Listed in the bug
- Top speaker not working
Still testing.
An update
Yes, we know calling is kinda broken right now on both oem versions. Yes, we know you have problems with dualsim devices because you didn't flash the dualsim patcher. Yes, battery life isn't very good because we are testing out some increased CPU frequencies so video doesn't stutter. (you can go back to the 11-05 build which has the old CPU freqs and compare).
We're aware of a lot of these issues, and they are all tracked in the current buglist (see post #2).
Development happens mostly in the Sony open devices program, with a few heroic volunteers contributing. Right now, a lot of work is being done to get the current flagships(think XZ2, XZ3) to a semi-stable state, but work for our device is done as well.
You can check progress in the sonyxperiadev repos. E.g. recently, some changes to the telephony HAL integration have been made, see the common device repo.
Why is it taking so long to fix all this?
Sony buys many of their processors from Qualcomm. Lots of stuff in phones is proprietary and covered in patents, and you can only get the source code if you sign an NDA. So even if Sony wanted to, they could not release the source for a lot of things.
See all the files with the name "qti" in them? That's Qualcomm Technologies, Inc. See all the repos named something like "qcom-something-something"? That's Qualcomm.
When there's a problem, we have to report it to Sony, who report it to Qualcomm. This takes time already. And don't forget Qualcomm has suppliers as well, and so on and so on. The same is true for other parts, e.g. the Wi-Fi chips are from Broadcom.
Then, support for hardware stuff is on many levels. A lot of low-level drivers that are driving the hardware are on the /odm partition(the one that the oemv1/v2 blobs get flashed to). Then there is work to be done tweaking the actual hardware abstraction layer(HAL) interfaces that work with these driver blobs. Then there are kernel drivers that can go wrong and mess up. Then it can be a problem somewhere higher up in the Android frameworks. Lots of detective work.
If new blobs from Qualcomm come out, Sony itself needs to do some testing, and then releases a new oem version. It won't just magically work, we need to tweak the SODP vendor side as well. It could be as easy as changing a version to a newer one, but it could also be a lot harder. The sonyxperiadev crew knows what's needed to integrate these new blobs, but it still takes time and testing.
Qualcomm provide the a lot of the source code to work with their hardware and blobs from the higher-level Android side in their CodeAurora forum (CAF) repositories. The relevant changes then get merged into the sonyxperiadev repos and we can test if it works(or if something new is broken...).
For more info, read the Android documentation on hardware etc.
The chip in our phone, the MSM8996, is quite old already(even the SDM845 in the XZ2/3 is already quite old in processor standards). We can be luck that Qualcomm still provides support. But it's not a priority to them, they want to sell new
ones of course. That is also a reason updates can take longer.
Regarding full forced-reboot crashes:
Sadly, as of now, for some people the "/sys/fs/pstore" folder does not get populated after a crash. This is important to diagnose what happened.
You can apply this patch to force a kernel panic on every reboot, but I would recommend that you do
so only if you know what you are doing.
Regarding battery life:
Please install BetterBatteryStats
and find out what is draining the battery.
This could really help us out! But first, make sure you are not running any GApps, because the Google Mobile Services are a massive pile of battery drain.
If you absolutely have to use GApps, please run only the "pico" GApps version!
---
About the posts here:
Like 90% of posts here and in the old thread are full of people who just plain refuse to read, asking how to install or demanding someone help them out with something that has already been answered time and time again. This makes it extremely annoying for the us who have to scroll through pages of useless stuff to find the genuine bug reports. You do realize this site is literally named "xda-developers", right? If you're unclear on the concept, please read this: https://forum.xda-developers.com/showpost.php?p=16682226&postcount=2441
"This doesn't work!" - "This thing crashes!" - That gives us almost no clue what is happening. We need logs, or we can't do anything about it. I have only one phone, and I only use the stock ROM. There are a lot of nice testers who send others and me helpful bug reports, with detailed explanations in what circumstances it occured, with proper logs.
With that info, the Sony open devices team and us can actually look into issues.
So please, if something doesn't work AND we are not aware of it yet, post it to the bug list (not here!) and attach a link to a log that you uploaded, e.g. to a service like hastebin.com.
nhicko95 said:
how is battery life?
Click to expand...
Click to collapse
Test it out, please. And don't forget to report the diagnosed battery stats.
DarkPrinciple said:
I should be able to get to 12 lunch with my battery being more than 50%
Click to expand...
Click to collapse
I've tweaked for more performance right now, but you can use 11-05 to get old CPU freqs. Also, please help hunt down what is draining the battery, it's most likely too many held wakelocks, but it could be any number of things.
bihslk said:
So what is the latest and best working version of this rom?
Click to expand...
Click to collapse
It's literally in the first post.
bihslk said:
Rom is pretty OK but really annoying top speaker bug. Only lower one works.
Click to expand...
Click to collapse
That is already in the bug list. Please read the bug list before posting.
Update 2018-11-16
Some new developments are happening.
Oem binaries version 3 are out. This should give improved power management. The SODP team has also worked on getting audio handling during calls to work. A big thanks to oshmoun for his work on the audio manager. This change was introduced on the 11-15 build. The issue of no call audio when a bluetooth headset is connected is still present as of now.
Changed IRQ handling (PR by Angelo/"kholk"). This should give better battery life and maybe faster wakeup from deep sleep. But could also lead to instabilities and crashes. Send logs & pstore, see post #2. This change was introduced on the 11-15 build.
Testing kernel 4.9.137 i in progress (we are currently on .103). This means stability and security enhancements from upstream linux. Thanks to Nathan Chance who opened this pull request..
But some of those upstream changes might be incompatible with our Sony kernel, so we have to test that. Send logs & pstore, see post #2. This change was introduced in the 11-16 build. If the 11-15 and 11-16 builds are unstable, revert to an older one. But please be brave and run them for at least a day to get us logs of potential crashes.
---
optixperiaa said:
I am always confused about "flash latest stock ftf" part about roms as a newbie.. if we flash sony's ftf how can we flash rom ? isnt it overwrite ?
Click to expand...
Click to collapse
Your phone software is made up of many layers. The ROMs like omni or this AOSP-based one only modify your /system and /boot partitions.
But when you update your stock firmware via flashtool, you also update your phone modem firmware, your qnovo charging controller firmware, your lower-level bootloaders etc. That is why we instruct you to update to the latest stock firmware. You could theoretically skip flashing /system in flashtool(because it will get overwritten anyway, as you've already discovered) and directly flash a custom ROM afterwards.
When you're coming from omni, there is no need to flash stock firmware again in between, because your other partitions stay the same. Just a new /oem is needed.
viori said:
flash omni_kagura-2018-11-20_UNOFFICIAL_TESTBUILD-2
Click to expand...
Click to collapse
Again, please keep this thread about development for AOSP. The omni builds are not meant for you.
If you have trouble installing then simply don't use it.
DO NOT POST HERE FOR HELP OR YOU WILL BE REPORTED. Read everything before posting.
If you have questions, ask them in this thread: AOSP 9.0 Pie builds for F8331/F8332
The OP has requested that you do not post questions in this thread, please use the thread he states in the OP to do that.
If you have questions, ask them in this thread: AOSP 9.0 Pie builds for F8331/F8332
Click to expand...
Click to collapse
Thanks
Thread cleaned
General update
Newer builds will have selinux set to "enforcing". Most denials should have been fixed or are irrelevant. If you encounter any problems, selinux-related or anything else, please report them to the Sony bugtracker or - even better - submit a pull request to the selinux-policy repo.
Update 1: vendor blobs aren't binderized correctly atm, so no network. You can set selinux back to permissive to fix most issues atm.
The Wi-Fi hotspot has been fixed thanks to oshmoun. In newer builds, it should be using less battery.
Next thing we're going to tackle is deep sleep and battery drain. Big pain point and one of the last blockers, apart from the camera and bluetooth in-call audio.
You might have noticed that the omnirom device trees have been updated to 9.0. Nightly testing builds work fine, but they have the same issues as the AOSP-based ones.
Work is also under way to get a Pie-based TWRP recovery stable, with support for FDE encryption(this means that you will be able to back up your encrypted installations). Mounting /userdata works, but the builds are not ready for public release yet.
Update
New build up (2018-12-08)
Camera key works
Update to December security patch(12-05, r21)
Fingerprint should not crash device on enrollment any more
Allow setting lower minimum brightness
Double-tap-to-wake off by default(but can be enabled)
Plugging in charger with screen off should be fixed
Once again, I invite anyone who would like to help out or just learn a bit about building and tweaking to take a look at the sources posted here.
There will be a guide on how to build only the kernel and experiment with a custom boot.img shortly.
The build guide on sx.ix5.org for reproducing these AOSP builds should bring you up to speed, and if you need help building or just want to chat, the telegram group in post #1 is open to you.
local__hero said:
New build up (2018-12-08)
Camera key works
Update to December security patch(12-05, r21)
Fingerprint should not crash device on enrollment any more
Allow setting lower minimum brightness
Double-tap-to-wake off by default(but can be enabled)
Plugging in charger with screen off should be fixed
Once again, I invite anyone who would like to help out or just learn a bit about building and tweaking to take a look at the sources posted here.
There will be a guide on how to build only the kernel and experiment with a custom boot.img shortly.
The build guide on sx.ix5.org for reproducing these AOSP builds should bring you up to speed, and if you need help building or just want to chat, the telegram group in post #1 is open to you.
Click to expand...
Click to collapse
Great job.
I already built a custom Pie kernel about a week ago to gain better performance but the charging bug was driving me insane :crying:
I guess now's the time to go back to the mighty Pie and try building a nice and hopefully stable Marrow Kernel.
Cheers
Finally a new build is out!
I can't pass safety net on latest build.
Any ideas what should I use ?
Since modules for spoofing fingerprint simply don't work.
I tried universal safety net fix but with no avail.
V 12.15
Charging working fine. But i have problem with camera, photos are very dark.
Sometimes touch screen not working and i need to switch the screen and on again.
ov2rey said:
Sometimes touch screen not working and i need to switch the screen and on again.
Click to expand...
Click to collapse
Disable Dt2w
oem v4 is out
DahakePL said:
Disable Dt2w
Click to expand...
Click to collapse
Thank you It's work!
Layns said:
oem v4 is out
Click to expand...
Click to collapse
i am testing v4 on latest build aosp_f8331_2018-12-21-NIGHTLY-permissive.
Screen unable to display after update to oem v4
https://developer.sony.com/file/download/software-binaries-for-aosp-pie-android-9-0-kernel-4-9-tone/
ov2rey said:
Thank you It's work!
i am testing v4 on latest build aosp_f8331_2018-12-21-NIGHTLY-permissive.
Screen unable to display after update to oem v4
https://developer.sony.com/file/download/software-binaries-for-aosp-pie-android-9-0-kernel-4-9-tone/
Click to expand...
Click to collapse
I tried it works fine but the camera sucks and the sound is bad, the screen opening with double tap is running slow, the charge is a little quick
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?