Related
STEP 1: DOWNLOAD TWRP 2.7.x.x and UPDATE (REQUIRED FOR 4.4):
EDIT: @Dees_Troy has an official 2.7.x.x w/ SElinux support here:
http://techerrata.com/file/twrp2/blaze/openrecovery-twrp-2.7.0.1-otter.img
Flash with the following adb commands:
Code:
adb shell
su
idme bootmode 4002
reboot
# back in your PC shell
fastboot -i 0x1949 flash recovery openrecovery-twrp-2.7.0.1-otter.img
If you have problems with that file and/or don't want to use adb/fastboot flash method, you can download a flashable .zip from the following locations. Use your existing recovery to flash the update:
Mirror 1: Download (Goo.im)
BEFORE FLASHING ANDROID 4.4: PERFORM A WIPE + ADVANCED->FORMAT SYSTEM TWRP.
STEP 2: DOWNLOAD A BUILD OF CM11.0:
DO NOT USE ART YET. BUGGY AND WILL PROBABLY NEED A DATA WIPE TO RECOVER FROM
NIGHTLIES:
http://download.cyanogenmod.org/?device=otter
GAPPS (Use Version "CM 11" row):
http://wiki.cyanogenmod.org/w/Gapps
Older builds are found here:
http://goo.im/devs/Hashcode/otter/cm10/
http://goo.im/devs/Hashcode/otter/cm10.1/
http://goo.im/devs/Hashcode/otter/cm10.2/
GAPPS (For Android 4.3/CM10.2 builds):
http://goo.im/gapps/gapps-jb-20130813-signed.zip
CHANGES:
[05/15] More audio updates to fix low-power states (screen off / background music)
[11/25] Released updated build for cm11.0
[08/12] Kernel updated to 3.0.72 (on par w/ Google/common kernel)
[07/30] Updated to CM10.2 build
[05/26] Backlight driver update to help w/ SODs
[05/24] Sensor updates (includes light sensor now usable in Android OS
[05/24] Reverted 2 sound driver commits in the kernel to help w/ headset function -- testing needed.
[05/14] New audio driver (WIP)
[03/27] Reboot Recovery mode is now fixed
[01/17] Updated SGX/PowerVR driver to latest binaries from omapzoom (still showing [email protected])
[01/15] CM10.1 updates + reverted some USB changes in the kernel for sleep testing
[01/07] Battery life / sleep improvements
[01/06] Update to 3.0.50 kernel
[01/06] Update wifi firmware to R5.SP3.06
[12/16] Fixed Deep Sleep
[12/15] Added multi-profile fix
CURRENT KNOWN ISSUES:
The headphone MIC input is not functioning correctly yet. Work in progress.
KERNEL FEATURES:
[08/12] Mainline version updates to 3.0.72 updated to current with Google's kernel/common
[01/06] WLAN Firmware R5.SP3.06
[11/07] Updated to SGX/IMG DDK [email protected] for Android (via omapzoom)
[11/07] WLAN Firmware R5.SP3.03
[09/05] Updated to SGX/IMG DDK [email protected] for Android
Based on TI kernel 4AI.1.7 (3.0.31 mainline) which supports 512M memory mapping needed by the Kindle Fire
Uses ducati binary from TI based on rpmsg 1.20.5.11 (replaced Archos ducati binary from ICS 4.0.3)
Kernel audio: Added a switch device "h2w" which allows the OS to recognize headset plug events and adjust audio capture routes accordingly. Translation: OS can recognize we have a MIC input via headset now. (NOTE: that audio recording is still not working at this time. Tho it is very close).
MUCH better standby / sleep function. The device will go inactive for much longer periods of time (80-100 seconds) while still waking up appropriately for wifi events, power button triggers, etc. And this is still going to get even better when I re-implement DPLL cascading and the charger fixes coming later.
Many bugfixes pulled down from TI's omapzoom sources.
RESERVED FOR NOTES
XDA:DevDB Information
Official CyanogenMod 11.0 for Kindle Fire 1st Edition, ROM for the Amazon Kindle Fire
Contributors
Hashcode
ROM OS Version: 4.4.x KitKat
Version Information
Status: Stable
Created 2014-05-01
Last Updated 2014-05-21
UPDATED 2013-11-25 for CM11.0/CM10.2/CM10.1
DEVELOPER BUILDING:
Several patches are outstanding in CM's review so building this from source is currently not an option w/o some Cherry Picks:
Patch 1: http://review.cyanogenmod.org/#/c/53917/
Patch 2: http://review.cyanogenmod.org/#/c/54562/
And I'll be updating more of the cm11.0 gits tonight w/ changes to the build / extract files processes.
Won't get a decent build till that's all done.
KNOWN BUGS:
1. EHCI USB 2.0 isn't able to be add to the kernel w/o it crashing. Need to fix for higher speed USB transfers.
6. Headset recording via the MIC input jack doesn't work
DEVS
BUILDING THIS ROM:
First, read through Google's Android website about "how to setup a build environment":
http://source.android.com/source/initializing.html
Then you can setup the Kindle Fire by doing the following:
mkdir android
cd android
(Use main repo for CyanogenMod 10.2)
repo init -u https://github.com/CyanogenMod/android -b cm-10.2
repo sync
vendor/cm/get-prebuilts
. build/envsetup.sh && brunch otter
FINALLY!
I'll see if I can help with power button LEDs.
*out-of-topic note: 3rd post!
1. The backlight doesn't sync up well with the screen. Meaning that sometimes when you bootup you won't see anything but a black screen. Once the boot is done, you can hit the power button a few times and eventually the screen and backlight will sync up and you'll get a picture.
Click to expand...
Click to collapse
I can't even get a picture.
animefun135 said:
I can't even get a picture.
Click to expand...
Click to collapse
Power button four or five times, and it'll pop up.
Edit: not having the sync issue in HC, hash, do you have the log posted on your site regarding the back light issue? I know its kernel related but 3.2 is a lil more cumbersome, so it could just be OS lag. Are we using 4.0.3 or 4.0.4?
Sent from my MB860 using XDA
Power button four or five times, and it'll pop up.
Click to expand...
Click to collapse
I tried 30+ times.
Nice job Hashcode.
Sent from my PG86100 using Tapatalk
I don't have time at the moment to pull down the sources and poke around for myself, but it sounds like #4 is a script issue of some sort.
Either one of the scripts that needs to fire for shutdown is hanging up, or the output isn't returning properly so that the master script can continue and finish pulling it all down.
If I get a chance tonight, I'll grab the sources and poke around a bit.
I deal with hanging/incorrectly-terminating script **** at work all the time, so now I might even be able to contribute, yay!
Reserving this for a complete description of the backlight driver/issue and related sources for research.
Sent from my DROID4 using XDA
Hey Hash I wanted to let you know that the charger does work for me. I don't have to boot back into twrp. Don't know if its just me or what but it works.
Edit: Didn't see that you had put its not working well instead off not at all, I'll do some more testing to see if it will give me problems. So far plugged it in about 20 times and its registering the charge.
Sent from my Amazon Kindle Fire using XDA
Let me be the first to say "Does Netflix work with this?"
Just kidding, things are coming along it appears, wish I knew more about hacking kernels, last time I did anything with a kernel I ran "make xconfig"
i just get a lit up black screen 0.0??
symbiiote said:
i just get a lit up black screen 0.0??
Click to expand...
Click to collapse
This issue is popping up with random people (myself included) and Hashcode has been made aware of it on the other thread, http://forum.xda-developers.com/showthread.php?t=1591869&page=5
The user who posted about it as well as another person as far as I know posted logs from their Kindle Fire's that depict the issue at hand. On a side note, and I know i'll get flamed for this, lets cut the arguing and just keep this thread as Hashcode requested it be, a development thread. If someone bashes you just ignore it and move on, the less clutter here the better Hashcode will be able to scan through it and pick out problems we're having and fix them.
To throw my two cents in on the issue itself:
I've noticed that when attempting to apply the suggested fix and sync up the graphics driver and the backlight I sometimes see quick glimpses of what I think are items on the screen, i'm wondering if this suggests an intermittent issue caused by the initial flash of the rom (could this explain why some are able to use the rom and some aren't). If this isn't possible please excuse my ignorance, it just made sense to me based on the limited amount of knowledge I have on this situation.
isaiahhhhh said:
I've noticed that when attempting to apply the suggested fix and sync up the graphics driver and the backlight I sometimes see quick glimpses of what I think are items on the screen, i'm wondering if this suggests an intermittent issue caused by the initial flash of the rom (could this explain why some are able to use the rom and some aren't). If this isn't possible please excuse my ignorance, it just made sense to me based on the limited amount of knowledge I have on this situation.
Click to expand...
Click to collapse
Wait, are you talking about things like large grey rows of pixels appearing on the screen? Sometimes I see gradients of monochromatic tones in addition to this. They only appear as the backlight is shutting off.
isaiahhhhh said:
This issue is popping up with random people (myself included) and Hashcode has been made aware of it on the other thread, http://forum.xda-developers.com/showthread.php?t=1591869&page=5
The user who posted about it as well as another person as far as I know posted logs from their Kindle Fire's that depict the issue at hand. On a side note, and I know i'll get flamed for this, lets cut the arguing and just keep this thread as Hashcode requested it be, a development thread. If someone bashes you just ignore it and move on, the less clutter here the better Hashcode will be able to scan through it and pick out problems we're having and fix them.
To throw my two cents in on the issue itself:
I've noticed that when attempting to apply the suggested fix and sync up the graphics driver and the backlight I sometimes see quick glimpses of what I think are items on the screen, i'm wondering if this suggests an intermittent issue caused by the initial flash of the rom (could this explain why some are able to use the rom and some aren't). If this isn't possible please excuse my ignorance, it just made sense to me based on the limited amount of knowledge I have on this situation.
Click to expand...
Click to collapse
your right, sorry, as for the rom, i noticed when i flashed hashcode's rom then reloaded rom over it youtube worked in HD, and that got me thinking, you think we can get a Flashable ZIP of the kernel?
is this the kernel that everyone was waiting for? 3.0?
@shahabk818
YES!
But it's still in development, so not for daily use!
TuikS2 said:
@shahabk818
YES!
But it's still in development, so not for daily use!
Click to expand...
Click to collapse
so this will fix the hardware acceleration problem, right?
shahabk818 said:
so this will fix the hardware acceleration problem, right?
Click to expand...
Click to collapse
So you can't read the title, right? [WIP][KERNEL][DEV-ONLY] 3.0 Kernel Development for Kindle Fire [04-10]
DEV ONLY!
OK, so compiled an aosp last night from the CM9 tree... I'm still not having a back light issue? Can't adjust brightness, but no sync issues. Could it be the ROM?
Sent from my MB860 using XDA
The Unlegacy-Android ProjectIntroduction
Unlegacy-Android started out as the OMAP4-AOSP Project. It was created in late 2015 in order to maintain a clean and organized place for pure AOSP support for various OMAP4 devices, such as the Galaxy Nexus and the Samsung Galaxy Tab 2 series. Over time this evolved to support more than just these devices, but still maintains its roots of supporting "legacy" devices that no longer receive "official" updates: hence Unlegacy-Android was born.
This organization's goal is not to create feature packed ROMs, but to create a base ROM in such a way that custom ROM developers can easily adapt the changes. We're good at (properly) fixing compatibility issues between newer Android versions and older devices, among other core things. The "bells and whistles" like themes we leave to others.
The first public build here had something exclusive for the Galaxy Nexus, yet unseen on any other OMAP4 device: all RAM carveouts reserved for Ducati (the multimedia subsystem of OMAP4, responsible for hardware-accelerated video decoding, encoding and camera functionality) have been switched over to CMA.
A few words for those who see CMA for the first time:
The Contiguous Memory Allocator (CMA) makes it possible for device drivers to allocate big contiguous chunks of memory after the system has booted.
The main difference from the similar frameworks is the fact that CMA allows to transparently reuse memory region reserved for the big chunk allocation as a system memory, so no memory is wasted when no big chunk is allocated. Once the alloc request is issued, the framework will migrate system pages to create a required big chunk of physically contiguous memory.
Click to expand...
Click to collapse
This means that a total of 996 MB physical memory is available to the system, while keeping Ducati fully working - this is a huge step forward, coming from the 694 MB available in the last factory image released by Google (Android 4.3). This gives the OS access to an additional 300MB of RAM.
While CMA was just recently implemented for this device, thanks to one of our developers (let's just call him Luden), it's quite stable: even under heavy memory pressure, the system manages to free up the required memory in order to start up Ducati and launch the requested multimedia functionality in a few seconds at most.
Installation
For Marshmallow (6.0) and below, It's important that /system needs to be unmounted before installing the ROM - some recoveries tend to leave it mounted after performing operations on it.
If you're planning to install GApps, be sure to read the second post!
Aside from these, installation and upgrading is no different than on other ROMs.
Problems
While we weren't able reproduce any CMA-related problems, hidden ones can still arise. In most cases, these problems will be either lost Ducati functionality (no multimedia capabilities) until rebooting, or a kernel panic (hard reboot) - upon noticing any of these, be sure to grab a logcat/dmesg and/or last_kmsg and send it to us (preferably by attaching it to a post in this thread).
Other than that, these are bugs we're aware of in the current build:
- The RIL on LTE devices (toro, toroplus) isn't fully working; calls and texts should be OK, but expect no data.
- Sound pops can be observed, mostly when using touch sounds (this is being investigated)
- Some exotic video formats or camera modes might not be perfect - if you notice any artifacts or green spots (the issue that happened in the past), report the details in this thread
- Inverted colors mode not working
- Tricky connection to some 5 GHz Wi-Fi networks
- SELinux is in Permissive mode (this isn't a problem for most people, just mentioned it here as extra information)
If you notice anything else, be sure to report it in this thread. While we're kind of busy, we usually read the thread and acknowledge the bug reports, even if I don't reply directly to them.
Downloads
See: http://builds.unlegacy-android.org.
As usual, feedback is appreciated
Want to support development? You can consider donating, we've spent countless of hours with this
XDA:DevDB Information
Unlegacy Android Project, ROM for the Samsung Galaxy Nexus
Contributors
Ziyan, MWisBest, Android-Andi
Source Code: https://github.com/Unlegacy-Android/
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Version Information
Status: Stable
Created 2016-03-12
Last Updated 2017-04-07
GApps
If you want to install GApps, we recommend Open GApps Nano or BaNkS GApps.
An important note: as this is a pure AOSP ROM, installing GApps tends to be problematic: in order to try to avoid installation issues, be sure to install GApps immediately after installing the ROM, before booting the system for the first time. After the initial bootup finished, be sure to go into Settings -> Apps, and grant every permission to every Google application - most importantly, Google Play services.
In the case of an upgrade, be sure to re-install the GApps package, as upgrading wipes /system. You shouldn't need to re-set the permissions afterwards.
siealex said:
One more note. DO NOT set up your Google account until you grant all permissions, otherwise you will be stuck on the initial setup.
Click to expand...
Click to collapse
Rooting
You can flash either the latest SuperSU or OpenSource SuperUser to get rooted.
Incredible work! Thank you to ALL the volunteer developers for making this FREE and OPEN SOURCE progress possible! The code is free, but your time is not! Thank you!!!
Out of curiosity, is aosp_mm_tuna_2016-03-12 running DDK1.9 or DDK1.8? I feel like it's 1.9 from your mention of recording artifacts, but I'm not an android developer, so I can't tell.
I'm running this right now, and it's awesome. Marshmallow in general seems to have much better performance than Lollipop on our device. I do miss some custom kernel flags, but I'm sure that'll come with time.
@Ziyan Which recovery do you recommend ?
DRM services not working means also Netflix doesn't work?
PythonNut said:
Out of curiosity, is aosp_mm_tuna_2016-03-12 running DDK1.9 or DDK1.8? I feel like it's 1.9 from your mention of recording artifacts, but I'm not an android developer, so I can't tell.
Click to expand...
Click to collapse
DDK 1.9 of course
Master94ga said:
@Ziyan Which recovery do you recommend ?
Click to expand...
Click to collapse
The latest TWRP should be fine. I might have not mentioned it in the OP, but the ROM supports F2FS as well.
Master94ga said:
DRM services not working means also Netflix doesn't work?
Click to expand...
Click to collapse
Possibly.
Ziyan said:
DDK 1.9 of course
The latest TWRP should be fine. I might have not mentioned it in the OP, but the ROM supports F2FS as well.
Possibly.
Click to expand...
Click to collapse
Thanks, 3.0 unofficial or your last recovery?
You are a god!
I'm downloading and will be testing this, I'm super excited about this work.
EDIT: So, first thing I've noticed is that the phone is struggling with the configuration in the first boot. Either in the "checking connection" or in the "just a sec..." loading frame, it freezes and doesn't get past it. Is it because of google play services?
diogofd8 said:
So, first thing I've noticed is that the phone is struggling with the configuration in the first boot. Either in the "checking connection" or in the "just a sec..." loading frame, it freezes and doesn't get past it. Is it because of google play services?
Click to expand...
Click to collapse
Yes Google Play Services can mess it up - I don't recall how, but I managed to press a skip button or something to easily get past it when it started looping. I guess we should add a mini how-to to the OP about it, as I really don't want to hack the framework for this.
Yep, I'm stuck in "just a sec..."
Edit: I restarted the Phone and now it works.
Netflix works too
Big thanks to @Ziyan and all OMAP4 dev for all your contribution so far ! I'll test this immediately [emoji106]
Sent from my Galaxy Nexus using Tapatalk
Ah, another thing!
When I flash the rom .zip file with all the partitions in f2fs, it auto changes to ext4 and installs. Maybe I'm being noob using TWRP so I'll say what I did here:
1) Full wipe
2) Convert system to f2fs, convert data to f2fs, convert cache to f2fs
3) Adb push rom zip file
4) Flash it
5) Check partition format, it's all on ext4
diogofd8 said:
Ah, another thing!
When I flash the rom .zip file with all the partitions in f2fs, it auto changes to ext4 and installs. Maybe I'm being noob using TWRP so I'll say what I did here:
1) Full wipe
2) Convert system to f2fs, convert data to f2fs, convert cache to f2fs
3) Adb push rom zip file
4) Flash it
5) Check partition format, it's all on ext4
Click to expand...
Click to collapse
There are a couple things going on here. The system ROM is an ext4 image, so it doesn't matter what you format it to, because it'll always become whatever is in the image.
Furthermore, only /data benefits from being F2FS, but it's not you fault for not knowing this because it wasn't mentioned in the documentation!
The other thing is that I don't know of a TWRP build that isn't buggy. When I tried to format to F2FS, it didn't work because my particular version of TWRP had a bug. So maybe your /data format failed for the same reason. I personally do not know what version of TWRP will reliably work for this. But this is a discussion for the TWRP thread.
2) Convert system to f2fs
Click to expand...
Click to collapse
Don't do this! F2FS is not supported on /system.
Wifi is extremely slow.
I can't do anything.
Google Play store can't install apps.
vipelp said:
Wifi is extremely slow.
I can't do anything.
Google Play store can't install apps.
Click to expand...
Click to collapse
Wifi works perfectly fine here ....with 2.4ghz
you using 5ghz or 2.4 ghz ?
I already tried both and it doesn't matter.
Browser times out opening google.com.
Play store doesn't load images and can't download apps
Wifi automatically disconnects....
rohitchouhan07 said:
Wifi works perfectly fine here ....with 2.4ghz
you using 5ghz or 2.4 ghz ?
Click to expand...
Click to collapse
WiFi working fine for me on 5GHz as well.
To other people: when this ROM boots, you may see the Google splash screen, then the screen will go black, and the device will act like it has died. It hasn't. Just give it a minute and the regular Android boot animation will appear.
OK i'm trying a reflash now. Complete wipe.
For me all work correctly, no problem with google play store or wifi
This release is only tested on the SM-T560NU USA (gtelwifiue).
This kernel is based on vince2678's port of LineageOS, with a couple of updates and optimizations.
This kernel has only been tested with vince's cm14.1 releases.
Flashable zips use a modified version of the AnyKernel2 system. While only tested on cm14.1, it may work on other ROMs, since it does not modify your initrd.
Very special thanks to vince2678.
Without his effort on this device, this release would not be possible.
Updates:
2017-06-10:
First build for CM14.1
Features:
DriveDroid Mass Storage and CD-ROM Support
Built with gcc-linaro-4.8-2015.06-x86_64_arm-eabi toolchain
Additional CPU optimizations
Updated CPU assembly optimizations
Various security patches
XPad (xbox 360 and xbox one) gamepad support
Known issues:
None
How to Install:
1. Download the latest release zip
2. Transfer zip to your device (or skip this step if sideloading)
3. Reboot into TWRP Recovery [Volume Up+Home] (If you need TWRP, first install mine or vince2678's.)
4a. Find the zip in the TWRP install browser, and install it
-OR-
4b. Sideload the zip using adb.
5. Reboot to system and enjoy
How much faster is it with the new optimizations?
Standard Kernel (click for full benchmark):
Noire Kernel (click for full benchmark):
What does "dirty" mean?
Whenever you modify a git repo and do not commit the changes, it will flag the kernel as "dirty".
Rather than forking the git repo, I use a clean copy of vince's repo, then apply my patches over it.
Because this isn't really how git was designed to be used, the build system sees it as "dirty".
It is nothing to worry about, as it is not harmful in any way.
Getting the kernel
Releases can be found on my site. (Check the header on the download page for a link to the source directory for tools to build your own):
https://files.persona.cc/zefie/files/cell/SM-T560NU/kernel/cm14.1
If/when there are more than one release, the most recent release should be on top, but verify the Last Modified date to be sure of the latest release.
Also be aware you will need to reflash anytime you update the main CM14.1 OS, as it will overwrite the kernel.
Bugs and issues
As vince's CM14.1 release is a rolling release, depending on many different sources, unexpected issues may come up in either the upstream code, his code, or my code.
Before submitting any reports to vince, be sure you are using his kernel (reflash the cm zip without flashing mine, preferably with a clean install)
Before submitting any reports to me, be sure the issue is not caused by the current release of CM14.1 (aka doesn't happen when you try the above).
No warranty is implied or provided. Be sure to have backups before flashing. But this is a no-brainer.
bump, because new release and target (was cm13, now cm14.1)
This kernel helped me to finally have USB OTG working by default, great job! :good:
Can you give us more detailed info about optimizations? Does your kernel have any impact on battery life?
jon355 said:
Can you give us more detailed info about optimizations? Does your kernel have any impact on battery life?
Click to expand...
Click to collapse
I haven't tested thoroughly but they shouldn't.
The optimizations are some patches that update the arm assembly functions to use features available in our CPUs that were not previously used.
As well as compiling while telling the compiler that we are using a cortex-a53 (in armv7 mode) (by default it just compiled generic armv7 with old armv5/6 assembly).
In short, they aren't overclocks, just using more of the processor's full potential, which is already sitting there doing nothing. Therefore, it shouldn't have a huge impact on battery life.
The CPU patches are here: https://files.persona.cc/zefie/files/cell/SM-T560NU/kernel/common-source/cpu_opts.patch.xz
Fun fact: Our CPU is actually armv8 64-bit, but we can't use it because we depend on Samsung's proprietary binaries, which are compiled in 32-bit (armv7 mode)
Sm-t560 <> smt560nu
Hey,
I'd like to Install this ROM, but obviously i get the message that it's not supported for my Device (in TWRP on flash attempt)
Mine is from the EU so, probably why..
Any chance to get this ROM to work for it?
Akineesan said:
Hey,
I'd like to Install this ROM, but obviously i get the message that it's not supported for my Device (in TWRP on flash attempt)
Mine is from the EU so, probably why..
Any chance to get this ROM to work for it?
Click to expand...
Click to collapse
No.
Unfortunately, Samsung made several hardware changes, including the CPU, when they brought this device to the USA.
You could almost think of the SM-T560NU as the "SM-T560 New".
It is a newer model with revamped hardware, and thus not compatible with ROMs made for the other.
Sorry.
zefie said:
No.
Unfortunately, Samsung made several hardware changes, including the CPU, when they brought this device to the USA.
You could almost think of the SM-T560NU as the "SM-T560 New".
It is a newer model with revamped hardware, and thus not compatible with ROMs made for the other.
Sorry.
Click to expand...
Click to collapse
Alright, thanks for the Quick follow-up!
zefie said:
I haven't tested thoroughly but they shouldn't.
The optimizations are some patches that update the arm assembly functions to use features available in our CPUs that were not previously used.
As well as compiling while telling the compiler that we are using a cortex-a53 (in armv7 mode) (by default it just compiled generic armv7 with old armv5/6 assembly).
In short, they aren't overclocks, just using more of the processor's full potential, which is already sitting there doing nothing. Therefore, it shouldn't have a huge impact on battery life.
The CPU patches are here: https://files.persona.cc/zefie/files/cell/SM-T560NU/kernel/common-source/cpu_opts.patch.xz
Fun fact: Our CPU is actually armv8 64-bit, but we can't use it because we depend on Samsung's proprietary binaries, which are compiled in 32-bit (armv7 mode)
Click to expand...
Click to collapse
Great info. What optimizations were done on OTG mass storage? On stock LOS 14.1 kernel, USB OTG wasn't working for me while with your kernel it works flawlessly.
Jacsd said:
Great info. What optimizations were done on OTG mass storage? On stock LOS 14.1 kernel, USB OTG wasn't working for me while with your kernel it works flawlessly.
Click to expand...
Click to collapse
Honestly none of my patches do anything USB related, except DriveDroid, but that lets the tablet be a device (by hosting disk images), not anything to do with connecting a device to it. Therefore, I cannot take the credit for that. Vince must have fixed it in his kernel. I built this with the latest code at the time, code that may have been more recent than the last lineage build of his that you tried.
zefie said:
Honestly none of my patches do anything USB related, except DriveDroid, but that lets the tablet be a device (by hosting disk images), not anything to do with connecting a device to it. Therefore, I cannot take the credit for that. Vince must have fixed it in his kernel. I built this with the latest code at the time, code that may have been more recent than the last lineage build of his that you tried.
Click to expand...
Click to collapse
I tried latest build and a few older builds, on every I was stucked in the loop of mounting and unmonting USB device. I only managed to enable USB OTG when I installed StickMount. It seems Drive Droid does the same. Will you continue work on this kernel?
Jacsd said:
I tried latest build and a few older builds, on every I was stucked in the loop of mounting and unmonting USB device. I only managed to enable USB OTG when I installed StickMount. It seems Drive Droid does the same. Will you continue work on this kernel?
Click to expand...
Click to collapse
I'll update it if there are any necessary updates for performance or security, or any issues are found, but for now it seems fairly stable and should be alright for a while.
zefie said:
I haven't tested thoroughly but they shouldn't.
The optimizations are some patches that update the arm assembly functions to use features available in our CPUs that were not previously used.
As well as compiling while telling the compiler that we are using a cortex-a53 (in armv7 mode) (by default it just compiled generic armv7 with old armv5/6 assembly).
In short, they aren't overclocks, just using more of the processor's full potential, which is already sitting there doing nothing. Therefore, it shouldn't have a huge impact on battery life.
The CPU patches are here: https://files.persona.cc/zefie/files/cell/SM-T560NU/kernel/common-source/cpu_opts.patch.xz
Fun fact: Our CPU is actually armv8 64-bit, but we can't use it because we depend on Samsung's proprietary binaries, which are compiled in 32-bit (armv7 mode)
Click to expand...
Click to collapse
Tnx for detailed answer. Btw, I tested your LOS 13 build and it's very smooth and battery life is great. Only issue I encountered so far is when charging offline, screen doesn't go off and there is no charging percents showed. Also, can you sync with the latest LIneage changes? Can you replace stock browser with the Jelly and stock camera with the Snap camera?
jon355 said:
Tnx for detailed answer. Btw, I tested your LOS 13 build and it's very smooth and battery life is great. Only issue I encountered so far is when charging offline, screen doesn't go off and there is no charging percents showed. Also, can you sync with the latest LIneage changes? Can you replace stock browser with the Jelly and stock camera with the Snap camera?
Click to expand...
Click to collapse
The thread for that is over here:
https://forum.xda-developers.com/showthread.php?t=3632745
Also, I am unable to reproduce the issue with the screen not shutting off. There is no percentage, but my screen shuts off while locked when charger is plugged in. Percentage and timeout can probably be configured in settings. I sync with Lineage every update. An update will come sometime this month with July's security patches.
As for replacing stock apps, I'll look into it. As the thread says, this is mostly for my use, hence why it wasn't publicly announced before. If I find the apps useful I will see about integration.
Wondering if this is still supported?
zefie said:
The thread for that is over here:
https://forum.xda-developers.com/showthread.php?t=3632745
Also, I am unable to reproduce the issue with the screen not shutting off. There is no percentage, but my screen shuts off while locked when charger is plugged in. Percentage and timeout can probably be configured in settings. I sync with Lineage every update. An update will come sometime this month with July's security patches.
As for replacing stock apps, I'll look into it. As the thread says, this is mostly for my use, hence why it wasn't publicly announced before. If I find the apps useful I will see about integration.
Click to expand...
Click to collapse
From the title you can tell if this still works. For example will it work with official LineageOS and what not. Hoping to get a response so I can overclock my tablet
Bigority said:
From the title you can tell if this still works. For example will it work with official LineageOS and what not. Hoping to get a response so I can overclock my tablet
Click to expand...
Click to collapse
Should still work. I haven't messed with the SM-T560NU in a while. If I recall the Lineage build system was creating broken builds, I'm running 14.1-20171121-NIGHTLY-gtelwifiue and Noire Kernel still works with that.
As for newer builds, last time I tried (some time between xmas and new years), all of the more recent Lineage builds would not boot, with or without my kernel. If trying newer Lineage NIGHTLYs, try without my kernel first, then try with if it does boot.
Vince has kinda abandoned the SM-T560NU, although I'm not sure it is a fair reason to abandon us, because we didn't test on a completely different device, but his choice is his alone, and as such, without him working on Lineage, the newer builds are likely to stay broken unless either he comes back to fix it, or someone else takes over (don't look at me).
zefie said:
Should still work. I haven't messed with the SM-T560NU in a while. If I recall the Lineage build system was creating broken builds, I'm running 14.1-20171121-NIGHTLY-gtelwifiue and Noire Kernel still works with that.
As for newer builds, last time I tried (some time between xmas and new years), all of the more recent Lineage builds would not boot, with or without my kernel. If trying newer Lineage NIGHTLYs, try without my kernel first, then try with if it does boot.
Vince has kinda abandoned the SM-T560NU, although I'm not sure it is a fair reason to abandon us, because we didn't test on a completely different device, but his choice is his alone, and as such, without him working on Lineage, the newer builds are likely to stay broken unless either he comes back to fix it, or someone else takes over (don't look at me).
Click to expand...
Click to collapse
For it to work properly should I try your port of LINEAGEOS or should I try Vince's port of Cyanogen Mod?
Bigority said:
For it to work properly should I try your port of LINEAGEOS or should I try Vince's port of Cyanogen Mod?
Click to expand...
Click to collapse
This kernel is for vince's 14.1. My 13.0 already uses Noire kernel and this release should not be flashed with that
zefie said:
This kernel is for vince's 14.1. My 13.0 already uses Noire kernel and this release should not be flashed with that
Click to expand...
Click to collapse
Alright thanks
zefie said:
This kernel is for vince's 14.1. My 13.0 already uses Noire kernel and this release should not be flashed with that
Click to expand...
Click to collapse
The link isn't working to download the kernel :l
Edit: It was working just my internet was too ****ty too load it.
An alpha build of Sailfish OS 2.1 for Nexus 10 (manta)
Its in rough shape but we are slowly but surely getting there.
YOU CAN DUEL BOOT WITH ANDROID! - See second post for info
UPDATE July 9th 2018: I am still still working on this. I have some stuff to try, mainly rebuilding the old June 2017 audio jack kernel in both hybris hal and the base rom, meaning, HOORAY - I'll be forced to start building my own android base. in the mean time things are the same in the OP, use the new build if you want the latest release and don't mind a lack of video, use the old one for creepy silent videos. I am counting down for Sailfish OS 3.0 to come out, I already know that its going to break anything I fix. And a big sigh is released.
Credits:
Lineage OS team for the LOS 14.1 Base (seriously, THANKS)
Jolla for that perfect software
followmsi for the fixed kernel sources that don't inherit those dirty lineage audio jack issues.
All the people on the #sailfishos-porters IRC who kept me motivated and full of hope (mal, krnlyng, Mister_Magister, sledges, m4r0v3r, piggz, r0kk3rs, just to name a few)
LOS14.1 Base: https://drive.google.com/file/d/1W3k2PzWKQU_-1qbhho_8MespNzr5zBlD/view?usp=sharing - I didn't make this at all.
Sailfish OS 2.1.3.7 alpha 0.1.2 rootfs: https://drive.google.com/file/d/1QKux9YkUHi7XZtGEJbUh_xYms5-BsLjo/view?usp=sharing - I did for sure make this (well, I ported it, credit to Jolla for sillica and stuff)
Sailfish OS 2.2.0.29 alpha 0.2 rootfs: https://drive.google.com/file/d/1IkWtZxAPGeiSiqCpMcbct-M43QlCsG8m/view?usp=sharing - THIS IS THE SUPER SPOOKY UNSTABLE RELEASE!!! BEWARE!
Adaptations Libhybris page: https://wiki.merproject.org/wiki/Adaptations/libhybris/Manta
My Video Review of alpha 0.1.3: https://www.youtube.com/watch?v=NmEGKZHquhQ
I have a lot to test so Ill populate this list more later but:
What works:
- Rotation
- ALS
- Magnetic Sensor
- Video
- Touch
- Hardware Keys
- Power Management and Sleep
The Checklist of What I Need to Fix
- Audio
- Video (droidmedia is broken in my latest clean build, this does not effect the rom in the OP, I would never update a rom with this many regression bugs)
- USB Charging
- Bluetooth
- GPS
- Haptic Feedback/Vibration
- Camera
CAMERA DOES NOT WORK IN THE BASE ROM SO IT WILL NOT WORK IN SAILFISH OS
Change log:
alpha0 - initial working release
alpha0.1 - added rotation fix, defined MALI_QUIRKS, applied a ton of random patches that did nothing
alpha0.1.1 - fixed taking screen shots, built gst-droid (you can now play mp3s but sound is still broken along with video)
alpha0.1.2 - built SDSVideoFix droid media! we can now play video but there is still ZERO sound at all.
alpha0.1.3 - unreleased, REGRESSION BUG: Video is broken - trying again.
alpha0.2 - Updated image to Sailfish OS 2.2.0.29, droid media still broken. I recommend staying on the old alpha 0.1.2 build.
Our device is the highest resolution device to ever run Sailfish OS (for now). Let's all feel extra special for a bit.
General About
Linux Kernel: 3.4.113
Rom Base: Lineage OS 14.1
Sailfish OS Version: Sailfish OS 2.2.0.29 | 2.1.3.7
Sources:
(This is on the to do list)
Also my Discord ID is dirtymikelikesfeet#9871
Tips and Tricks
Get landscape rotation in ALL apps
Go to warehouse, and install patch manager and autorotate anywhere (or something like that)
Reboot
voila.
Dual Boot Lineage OS 14.1 and Sailfish OS
This is super easy, so basically the Hybris installer doesn't touch /system or /data (at least none of the installed android files) so you can boot between the two rather easily. You will need a Lineage OS 14.1 boot image (Inside the Lineage OS 14.1 zip) and Hybris boot (inside the Sailfish OS zip). When you want to boot between the two, boot into TWRP Recovery, and flash the appropriate boot image. This should make it easier for testers.
Q/A
Does flashing a new Sailfish OS image wipe my android files? - As far as I know? No. But I haven't really tested this. It shouldn't.
"Is this usable as a daily driver?" - No. not right now. Once I fix audio maybe, but as it stands now, unless all you do is read emails, watch silent movies, and play simple games and read books, its pretty garbage. You can browse the web with web cat but it has 1/3 of the screen not used.
"Why did you use the LOS14.1 base you idiot? you realize we will never have working camera now right???" - Lesser of all evils. Once I get a good stable LOS 14.1 based sfos port (working everything), and a list of all my tweaks to fix everything, I will try making an LOS 13 based sfos port. I like camera too, and do occasionally use it on this tablet.
"Does it have android app support?" - No. Maybe one day I will hack alien dalvik onto it and post a concept install for Nexus 10, but no promises.
Looks interesting,I will have to follow your work to see how far this goes. ?
Yes me to. I still have my Nexus 10 but don't use it much because it's horrible for streaming videos, unless I flash gingerbread. Anyway hope you keep at this, thanks for your effort.
Sent from my LG-ls990 using Tapatalk
aheeejd said:
Yes me to. I still have my Nexus 10 but don't use it much because it's horrible for streaming videos, unless I flash gingerbread. Anyway hope you keep at this, thanks for your effort.
Sent from my LG-ls990 using Tapatalk
Click to expand...
Click to collapse
Thanks for the interest, the current thing to do is add minimer to m N10 so I can fix hwcomposer, it is wonked real bad and I think it's why jolla-startupwizard won't work right now.
*bump* because it finally ****ing works (sort of)
sailfish for nexus 10
Galaxyninja66 said:
*bump* because it finally ****ing works (sort of)
Click to expand...
Click to collapse
a better browser please??or a new version??
ted111 said:
a better browser please??or a new version??
Click to expand...
Click to collapse
browser bugs are proving near impossible to solve, and manually rebuilding qtmozembed did nothing. I am going to try and crank out a 2.2 build tonight with the vendor repos included but I doubt much will change. As far as browser, the cut off is a problem with qt that I am still figuring out how to solve.
OKAY! Building new image with mic as I type this. it's at 162/473, hope it doesn't fail but it rarely does at this point. Using followmsi's new 0611 build as a base, and I have thrown in TheMuppets vendor repos for broadcomm and the like, hopefully something cool happens, but I am 99% sure this build will be the same broken build accept based on sailfish OS 2.2. This means no gstreamer, i.e. no videos, no mp3 files, no nothing. Also I doubt Audio will just fix it self either.
Galaxyninja66 said:
*bump* because it finally ****ing works (sort of)
Click to expand...
Click to collapse
tested 2.2.0.29 ,no videos, sound, webpirate browser simple works
ted111 said:
tested 2.2.0.29 ,no videos, sound, webpirate browser simple works
Click to expand...
Click to collapse
Its terrible, I know.
and the audio isses we are no closer to fixing since I have ZERO idea what is causing them, and neither do the people I've worked with. I am reloading the CM11 based port and trying to work out the gralloc issues on it, there are a ton of dependency files missing on that port for hwcomposer, but it should be fixable. everything is fixable.
Galaxyninja66 said:
Its terrible, I know.
and the audio isses we are no closer to fixing since I have ZERO idea what is causing them, and neither do the people I've worked with. I am reloading the CM11 based port and trying to work out the gralloc issues on it, there are a ton of dependency files missing on that port for hwcomposer, but it should be fixable. everything is fixable.
Click to expand...
Click to collapse
any news about it?
123123123123123213 said:
any news about it?
Click to expand...
Click to collapse
I no longer own the device, 10.1 and 11 sources had hwcomposer errors (but working audio afaik). 12-13 sources failed to boot for reasons entirely unknown since the logs looked fine (and no, it wasn't a no UI/display error, I checked and it was in telnet still, again, for seemingly no reason). 14.1 worked like a charm but sadly the audio issues were just a mystery. Rotation was an easy fix and I think at that point GPS had very little mw so it was hit or miss and debugging it was not done often so it was mostly undocumented. Don't know about now.
tl;dr
10.1-11 - broken hwcomposer, wayland is gimped in 2.0 and beyond period, and fbdev wouldn't work either
12-13 - refuses to boot past the telnet stage for unknown reasons
14.1 - audio is broken, using followmsi and the stock lineage sources/matching base images.
I'd love to work on this again actually, but a new N10 would cost me 80 AUD and I'd have to prep a new VM since I wiped all mine switching to macOS.
Code:
*** Disclamer
Please behave responsibly and avoid thermonuclear war. I am
not responsible for any bricked devices, etc.
Introduction
This is Zest Kernel. It's an optimized kernel for our device which includes a few nifty features. Built, on every security update, you'll have the best of the best. Features will be listed below and shared, to the most of my ability, across all my supported devices. This isn't just my kernel it's yours too - request any features you like and I'll try to add them in. However, I'm also busy with studies so please don't ask for dumb stuff.
Click to expand...
Click to collapse
Images
Possibly the fastest [clean] ROM for our device, benchmarks coming soon .
Click to expand...
Click to collapse
Features
Google's exclusive features for Pixel devices (except Music Ticker and Call Screening)
Lawnchair launcher
Spoofed stock device to pass SN
Widevine L3
Faster encryption device-wide
Daydream VR
Fast, optimised Zest Kernel
EAS
Markup screenshot editing
Google Sound Picker
Google Wallpapers
Digital Wellbeing
Optimised GPU rendering for Pie
Custom Clang and GCC toolchains for building - optimised LLVM with PGO, and GCC 9.1
OpenGApps pico included
GCam HDR+ support
Click to expand...
Click to collapse
Installation instructions
* Go download https://developer.sony.com/file/download/software-binaries-for-aosp-pie-android-9-0-kernel-4-9-yoshino.
* Unzip the download to get an .img file.
* Install fastboot (drivers for this can be gotten from Google directly), drivers for flashmode for Windows can be gotten from newflasher.
* Enter your command prompt or terminal whatever and fastboot flash oem THEFILEYOUEXTRACTED.img.
* Find a decent TWRP and flash it.
* Download the ROM for your device. They are all in this folder https://jenkins.cosmic-os.org/job/zfsodp-core/ws/lastbuild so click the one for your codename (eg. G8141 is single sim maple and G8142 is dual sim maple).
* Flash it in TWRP and wipe internal storage and format data (the option that has red text and makes you type yes).
* Enjoy!
Click to expand...
Click to collapse
Download
Latest is on my Jenkins job.
Click to expand...
Click to collapse
FAQ
PM me in XDA's Sony group.
Click to expand...
Click to collapse
Special Thanks To
Code:
* @kholk for his kernel advise
* @Sultanxda for his kernel advise
* @deletescape for Lawnchair
XDA:DevDB Information
Zest-flavoured SODP, ROM for the Sony Xperia XZ Premium
Contributors
LazerL0rd, The entire SODP team
Source Code: https://github.com/ZfSODP
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest Sony OSS OEM binaries
Based On: SODP
Version Information
Status: Beta
Beta Release Date: 2019-07-06
Created 2019-07-06
Last Updated 2019-08-10
Reserved
Reserved
nice, try tonight:good:
----------------------------------------------------------------------------------------------
HAVE BEEN DELETED, I don't know what happen, his own website and his kernel is also deleted.
I have the same as the #5, but a bit different, there were 4 identical page on the screen, such like 4 1080p in a 4k screen, I think the 120HZ 1080p display driver is the reason.
I was on latest stock when flashing (following every step), when it boots and show the sony logo, it gets distorted (characters in the top and middle) and then reboots. I've reflashed stock, wiped everything including system, tried older twrp, and even flashed the G8142 image on my G8141, but i keep getting the distorted sony logo followed by a reboot. Is there anything else i have to do?
I had this issue before with AOSP but i never figured out how to fix it.
G8141, unlocked bootloader, .80 stock, twrp 3.3.1.0 and 3.2.3.0
del
Can I flash the kernel through twrp, then flash the zip?
Hey the Download Link is unavailable. Also your website is 404. I can't obtain your Kernel -OR- rom
Psychoticism said:
Hey the Download Link is unavailable. Also your website is 404. I can't obtain your Kernel -OR- rom
Click to expand...
Click to collapse
Give it a week or so mate, lazerl0rd is studying/having exams for a while.
Hey, have you tested the performance of EAS kernel ?
Could you please test the scores of GeekBench ?
BTW, you'd better remove the rqbalance in devices tree and disable cpu_quiet in kernel.
Besides, you need to replace the PowerHal in common. The PowerHal of SODP doesn't support EAS, you need to port it from Pixel 2.
All in all, well done!
Any screenshot of the performance?
It was stopped at the android logo, it ran all night and did not enter the system. please help me!
still on logo android !/
Sjll said:
Hey, have you tested the performance of EAS kernel ?
Could you please test the scores of GeekBench ?
BTW, you'd better remove the rqbalance in devices tree and disable cpu_quiet in kernel.
Besides, you need to replace the PowerHal in common. The PowerHal of SODP doesn't support EAS, you need to port it from Pixel 2.
All in all, well done!
Click to expand...
Click to collapse
SOME Screenshots here. driveDOTgoogleDOTcom/folderview?id=1rrF_kQA5sU_FIlXxERuZG0dxiX3xHn1m(Sorry but I cannot put link before I have 10 post)
It broken easily if screen off so please hold it on all the time.
With 120Hz all the gpu text showed obvious frame fluctuation.
Laplacetor said:
SOME Screenshots here. driveDOTgoogleDOTcom/folderview?id=1rrF_kQA5sU_FIlXxERuZG0dxiX3xHn1m(Sorry but I cannot put link before I have 10 post)
It broken easily if screen off so please hold it on all the time.
With 120Hz all the gpu text showed obvious frame fluctuation.
Click to expand...
Click to collapse
EAS is not stable on SODP. GPU of MSM8998 is hard to afford 120Hz.
Smooth, fast(20sec boot time including 5 second bootloader unlocked nag!) and clean rom thanks a lot! Sadly not going to be my daily driver because lack of features, and my device overheats sadly because of 120hz. Also it takes me 3 reboots to get into recovery any idea why?
Advices:
Get rid of pre installed google, allow users to install separately.
JamesDSP should be stabilized, I just get FC all time can't get it to work. (Would be better to just remove as well and allow user to install separately)
Default DPI is too low, should be 420 for ease of use.
Sony camera should be added, as in Sjll's LineageOS. ***
Ancient app logos (kitkat calendar calculator etc) should be updated.
Device-wide dark mode which includes Phone, Calendar, Settings and Files should be made. **
Phone application should be de-google-ified, Spam filter inside just feeds Google with private call data. ***
Option to switch resolution and frame rate on the go.
Heyo, wondering if you can add a quick and dirty CIFS kernel module. There are some universal versions floating around online.
Signing them is above my skill level. I don't know if the signing process has to be implemented on a device by device level. If that is an impediment, maybe consider removing the requirement for kernel modules to be signed in the first place? I don't know, I'm no expert.
Just a PSA. Someone got rclone mounts working via Magisk. Can be found in repo. Sadly, no support for cifs or nfs. But webDav works. The largest downside is that the mounts can't be mounted directly onto sdcard. Something the cifs kernel module did no problem. With rclone you'll need an app with root browsing capability. Or at least full access to /storage.
UPDATE: The rclone Magisk version has been updated to support direct sdcard mounts! Yay! So, there isn't really a need for a cifs module.
However, I'm certain the performance will be better with a cifs module. So, it's not necessary, but could be a cool benefit if added.
Thanks for all the work! It doesn't go unnoticed.
i hope you add other version special 90hz because 120hz make my device overheats and thank you
Moarten said:
I was on latest stock when flashing (following every step), when it boots and show the sony logo, it gets distorted (characters in the top and middle) and then reboots. I've reflashed stock, wiped everything including system, tried older twrp, and even flashed the G8142 image on my G8141, but i keep getting the distorted sony logo followed by a reboot. Is there anything else i have to do?
I had this issue before with AOSP but i never figured out how to fix it.
G8141, unlocked bootloader, .80 stock, twrp 3.3.1.0 and 3.2.3.0
Click to expand...
Click to collapse
Try again, a few of the previous builds were bootlooping, I'll try update instructions too.
Laplacetor said:
nice, try tonight:good:
----------------------------------------------------------------------------------------------
HAVE BEEN DELETED, I don't know what happen, his own website and his kernel is also deleted.
I have the same as the #5, but a bit different, there were 4 identical page on the screen, such like 4 1080p in a 4k screen, I think the 120HZ 1080p display driver is the reason.
Click to expand...
Click to collapse
Psychoticism said:
Hey the Download Link is unavailable. Also your website is 404. I can't obtain your Kernel -OR- rom
Click to expand...
Click to collapse
Try again, a few of the previous builds were bootlooping, I'll try update instructions too. ROM isn't on my website and never was .
wolfmanstr said:
Can I flash the kernel through twrp, then flash the zip?
Click to expand...
Click to collapse
Don't use my stock kernel with this.
Sjll said:
Hey, have you tested the performance of EAS kernel ?
Could you please test the scores of GeekBench ?
BTW, you'd better remove the rqbalance in devices tree and disable cpu_quiet in kernel.
Besides, you need to replace the PowerHal in common. The PowerHal of SODP doesn't support EAS, you need to port it from Pixel 2.
All in all, well done!
Click to expand...
Click to collapse
It performs better, battery is decent now (after a load of changes). We now (as of today) have a Power HAL (libperfmgr) which supports DT2W on supported devices too. I may or may not update it to version 1.3.
SilverGamer_YT said:
Any screenshot of the performance?
Click to expand...
Click to collapse
No, it's EAS and you could test it out.
tronganhha29 said:
It was stopped at the android logo, it ran all night and did not enter the system. please help me!
Click to expand...
Click to collapse
Yeah, I fixed that a while ago - try again please.
CRNO said:
still on logo android !/
Click to expand...
Click to collapse
Yeah, I fixed that a while ago - try again please.
Laplacetor said:
SOME Screenshots here. driveDOTgoogleDOTcom/folderview?id=1rrF_kQA5sU_FIlXxERuZG0dxiX3xHn1m(Sorry but I cannot put link before I have 10 post)
It broken easily if screen off so please hold it on all the time.
With 120Hz all the gpu text showed obvious frame fluctuation.
Click to expand...
Click to collapse
I don't get all this 120Hz issue, it's not as simple as "set 120Hz get lag" and like our phone can handle it on UI, at least. The worst case is battery but IIRC it wasn't too different from 60Hz. Anyways it's 90Hz now.
Sjll said:
EAS is not stable on SODP. GPU of MSM8998 is hard to afford 120Hz.
Click to expand...
Click to collapse
I don't get all this 120Hz issue, it's not as simple as "set 120Hz get lag" and like our phone can handle it on UI, at least. The worst case is battery but IIRC it wasn't too different from 60Hz. Anyways it's 90Hz now. EAS seems stable, here. The bugs we have aren't really EAS related.
undefine said:
Smooth, fast(20sec boot time including 5 second bootloader unlocked nag!) and clean rom thanks a lot! Sadly not going to be my daily driver because lack of features, and my device overheats sadly because of 120hz. Also it takes me 3 reboots to get into recovery any idea why?
Advices:
Get rid of pre installed google, allow users to install separately.
JamesDSP should be stabilized, I just get FC all time can't get it to work. (Would be better to just remove as well and allow user to install separately)
Default DPI is too low, should be 420 for ease of use.
Sony camera should be added, as in Sjll's LineageOS. ***
Ancient app logos (kitkat calendar calculator etc) should be updated.
Device-wide dark mode which includes Phone, Calendar, Settings and Files should be made. **
Phone application should be de-google-ified, Spam filter inside just feeds Google with private call data. ***
Option to switch resolution and frame rate on the go.
Click to expand...
Click to collapse
I don't get all this 120Hz issue, it's not as simple as "set 120Hz get overheat" and like our phone can handle it on UI, at least. I changed up the thermal driver so it should be good now. Btw those thermal modules in Magisk won't change a thing as I use sultan's thermal framework now - not RQBalance stuff. DPI has an option on setup under "vision", choose what you like. I added GCam instead, it's gonna be better quality than Sony's crappy cam app. Ancient app logos aren't gonna be updated, these are ASOP packages - instead I'm replacing them with Google packages. Also I made everything Squircle shaped too. Device-wide dark mode will be coming soon, needs some kanging [with original authorship] from Q. Phone application should be de-google-ified -> you can turn off the spam filter and install any Dialer you want. I'm not dealing with darkening AOSP's package so that's why I'm using Googles. Google can get your data if Play Services is installed anyways. Option to switch resolution and frame rate on the go -> idk why SODP removed that.
Astoras said:
Heyo, wondering if you can add a quick and dirty CIFS kernel module. There are some universal versions floating around online.
Signing them is above my skill level. I don't know if the signing process has to be implemented on a device by device level. If that is an impediment, maybe consider removing the requirement for kernel modules to be signed in the first place? I don't know, I'm no expert.
Just a PSA. Someone got rclone mounts working via Magisk. Can be found in repo. Sadly, no support for cifs or nfs. But webDav works. The largest downside is that the mounts can't be mounted directly onto sdcard. Something the cifs kernel module did no problem. With rclone you'll need an app with root browsing capability. Or at least full access to /storage.
UPDATE: The rclone Magisk version has been updated to support direct sdcard mounts! Yay! So, there isn't really a need for a cifs module.
However, I'm certain the performance will be better with a cifs module. So, it's not necessary, but could be a cool benefit if added.
Thanks for all the work! It doesn't go unnoticed.
Click to expand...
Click to collapse
For Android kernels, you can't just chuck a module in. But I'll add it to the kernel config for ya.
CRNO said:
i hope you add other version special 90hz because 120hz make my device overheats and thank you
Click to expand...
Click to collapse
Already done. And - "I don't get all this 120Hz issue, it's not as simple as "set 120Hz get overheat" and like our phone can handle it on UI, at least."