Code:
#include <std/disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. :P
* blah blah blah you get the point.
*/
This is a simple unofficial CyanogenMod 13 build with a few small tweaks and my custom kernel.
Builds are made with that day's nightly source code, with my roomservice. I try to keep my repos up to date.
How to install this:
Download this build (and MD5, if you want to verify integrity)
Download Gapps (Optional, I use OpenGAPPS Nano)
Download SuperSU (Optional, I use SuperSU Beta 2.74)
Reboot into Recovery
Wipe /cache, /data, and /system (Should only be needed on initial flash, upgrading should be seamless)
Flash ROM Zip
Flash Gapps Zip (Optional)
Flash SuperSU Zip (Optional)
Reboot & Enjoy!
How to build this (if you don't trust my builds, or want to DIY):
Sync CM13
Add my local manifest: https://github.com/javelinanddart/roomservice/blob/cm-13.0/roomservice.xml
Sync
Go to kernel/samsung/ (you may have to mkdir samsung folder, if it doesn't exist)
Clone my kernel manually into a folder called jf
git clone https://github.com/javelinanddart/android_kernel_samsung_jf -b cm-13.0 jf
Build
Make sure you manually git pull the kernel when you run a new build.
Bug Reporting:
Please read http://forum.xda-developers.com/showthread.php?t=1520508 & http://forum.xda-developers.com/wiki/Reporting_A_Problem_-_Android
before reporting any bugs. It is incredibly frustrating and useless to receive bug reports like "bt broke plz fix thx in advance....." without any other information. I would more than like to help fix your bug for you, but I cannot help without proper information.
Credits (off the top of my head):
CyanogenMod Team
@arter97
@show-p1984
and many more I can't think of off the top of my head....
Source Code:
Kernel: https://github.com/javelinanddart/android_kernel_samsung_jf
Local Manifest: https://github.com/javelinanddart/roomservice/blob/cm-13.0/roomservice.xml (for the rest of my repos)
OP Post List:
#1: Introduction
#2: Changelog
#3: Feature List
#4: Downloads
#5: Feature Explanations
#6: Known Bugs
#7: Reserved for future use
XDA:DevDB Information
Unofficial CyanogenMod 13 with Cake Kernel, ROM for the T-Mobile Samsung Galaxy S 4
Contributors
javelinanddart, CyanogenMod Team
Source Code: https://github.com/javelinanddart/
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
ROM Firmware Required: NK2
Based On: CyanogenMod
Version Information
Status: Stable
Created 2016-06-02
Last Updated 2016-06-02
Changelog:
Aug 1, 2016
Sync with CM
Initial Rerelease
Cleaned Everything Up
Enable LiveDisplay by Default
June 7, 2016
Sync with CM
Fix 1080p Video Playback
Potentially fixed micro lag while scrolling
June 1, 2016
Initial Release
ROM Feature List:
Built with -O3 Optimization (GCC & Clang)
Built with UBERTC GCC 5.3 Toolchain
Built with Java 8
Some apk Optimizations (from @arter97)
Kernel Feature List:
Built with -O3 Optimization
Built with UBERTC GCC 5.3 Toolchain
Fsync Toggle
MSM_MPDEC
Bricked Thermal
CPU Toggle
IO Scheduler Optimizations
/dev/frandom Support
Gentle Fair Sleepers & Arch Power Toggle
MMC CRC Toggle
Dynamic Readahead
Lowered Swappiness
Aggressive Multi Core Power Saving
Simple GPU Governor
CPU Voltage Control
GPU Voltage Control
Fast Charge
Badass Governor
FIOPS I/O Scheduler
Sound Control
Backlight Dimmer
Disabled Input Boost
Added patch to fix Entropy Depletion
Potential Benefits of These Features:
Better Battery Life
Downloads:
NOTE: You will need to turn off ad block in order to download these builds. The wonderful Codefire team has provided me with access to this build server for free (thanks specifically to @thecubed) and in order to try to make it break even, they rely on ad revenue. @thecubed takes a loss on this server every month, so please help this guy to keep providing this wonderful service to developers for free. Thanks for understanding!
MIRRORS ARE NOT ALLOWED!!! (Mods: Please help me enforce this)
BUILDS PULLED
KNOWN BUGS:
Upstream CM Bugs
Micro Lag when Scrolling (Possibly)
You tell me....
Reserved 6
Reserved 7
javelinanddart said:
KNOWN BUGS:
Upstream CM Bugs
Micro Lag when Scrolling (Working on it)
You tell me....
Click to expand...
Click to collapse
Do you mind my asking if you are using this rom now or are you just working on it?
I would like to update to a 6.0 rom but don't really want to give up much functionality. I am using 5.1.1 and I do like it but would like the security updates of the newer rom while I decide which new device if any to purchase. Thanks
darazor said:
Do you mind my asking if you are using this rom now or are you just working on it?
I would like to update to a 6.0 rom but don't really want to give up much functionality. I am using 5.1.1 and I do like it but would like the security updates of the newer rom while I decide which new device if any to purchase. Thanks
Click to expand...
Click to collapse
I am both using it and working on it. As far as I know, all device features are fully functional (camera, GPS, IR, etc). Nothing I've tried has been broken, except the occasional google play services crash, which is Google's fault. As far as ROM features go, I haven't done much of a comparison with any LP ROMs.
To clarify, what I meant by working on it, I meant I was trying to fix that bug.
javelinanddart said:
I am both using it and working on it. As far as I know, all device features are fully functional (camera, GPS, IR, etc). Nothing I've tried has been broken, except the occasional google play services crash, which is Google's fault. As far as ROM features go, I haven't done much of a comparison with any LP ROMs.
To clarify, what I meant by working on it, I meant I was trying to fix that bug.
Click to expand...
Click to collapse
Thanks for the quick response. I am still on the MDL boot loader with OK3 base band is that a deal breaker?
Also is this compatible with xposed. I've read that they don't work well together. At this stage I could live without it but just for clarification and planning purposes. I like to have a path in my mind as I update.
darazor said:
Thanks for the quick response. I am still on the MDL boot loader with OK3 base band is that a deal breaker?
Also is this compatible with xposed. I've read that they don't work well together. At this stage I could live without it but just for clarification and planning purposes. I like to have a path in my mind as I update.
Click to expand...
Click to collapse
I've no idea with either, unfortunately. I've only ever had this phone with NK2 baseband, and I've never used Xposed, I've never had a use for it. Sorry.
javelinanddart said:
I've no idea with either, unfortunately. I've only ever had this phone with NK2 baseband, and I've never used Xposed, I've never had a use for it. Sorry.
Click to expand...
Click to collapse
I've spent the last several hours installing etc. This rom is GREAT! While I will have to test more, at this stage everything I've installed works perfectly and the bootloader/baseband doesn't seem to be an issue. Even AdAway has been perfect so far. I will expore the Xposed option later but if it isn't viable I can live very well with the current setup. I will report more unless someone else covers the topic. If anyone is hesitant to try this rom, don't be. Out of the box it is much more than I could have hoped for.
Disable adblock ?
Nope
Grudger said:
Disable adblock ?
Nope
Click to expand...
Click to collapse
1. Just to download the ROM
2. If you're not willing to help support the people who do this FOR FREE by turning off adblock for a few minutes, or even just on the download site, then realize that it's people like you who are going to cause free services to go extinct.
javelinanddart said:
1. Just to download the ROM
2. If you're not willing to help support the people who do this FOR FREE by turning off adblock for a few minutes, or even just on the download site, then realize that it's people like you who are going to cause free services to go extinct.
Click to expand...
Click to collapse
I just prefer donations and the thanks button
As soon as I try out the ROM though.
Grudger said:
I just prefer donations and the thanks button
As soon as I try out the ROM though.
Click to expand...
Click to collapse
I don't really care about donations, but the ad supported download page helps the owner of the build server I use, he gives it to me for free. I could not provide these builds if he wasn't so gracious as to let me use his build server for free. He consistently pulls losses from it, which makes it difficult to justify after a while. If you want to donate to someone (you'll still need to turn off adblocker on the download page, because he can't disable ads just for you unfortunetely), donate to @thecubed, it's his server.
javelinanddart said:
I don't really care about donations, but the ad supported download page helps the owner of the build server I use, he gives it to me for free. I could not provide these builds if he wasn't so gracious as to let me use his build server for free. He consistently pulls losses from it, which makes it difficult to justify after a while. If you want to donate to someone (you'll still need to turn off adblocker on the download page, because he can't disable ads just for you unfortunetely), donate to @thecubed, it's his server.
Click to expand...
Click to collapse
As I said before like this rom very much. Only issue so far is the standard CM bluetooth problem "Unfortuneatly bluetooth share has stopped". Are or have you been able to connect with BT?
darazor said:
As I said before like this rom very much. Only issue so far is the standard CM bluetooth problem "Unfortuneatly bluetooth share has stopped". Are or have you been able to connect with BT?
Click to expand...
Click to collapse
I unfortunately have not tested BT, and I don't really have any devices to test, except maybe connecting to my other phones. I will be out all of today, however I noticed a very annoying video playback bug that I will try to fix today.
New build is UP!
Changelog:
-Synced with CM
-Fix 1080p Video Playback
-Possibly fixed scrolling lag
Many thanks for your work on this ROM for our phones! :good::good:
Fingers xx'd that someday soon BT problems will be past us.
Related
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1.x (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
/*
* 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 us for messing up your device, we will laugh at you.
*/
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. You will need to provide your own Google Applications package (gapps). 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. Your changelog is whatever was merged into gerrit.
Download
RECOVERY: Androidfilehost twrp-3.0.0-0-idol347-f2fs.img
ROM: Androidfilehost cm-12.1-20160209-UNOFFICIAL-idol347.zip
GAPPS: OpenGAPPS
Changelog
Code:
Current changelog: 2016-04-05
- Security Patchlevel April
- support 6039H
- small changes from upstream
Older changelogs:
Code:
2016-02-09
- Security Patchlevel February
- fixed some selinux denials
- removed obsolete script for variant identification
2016-01-31
- added support for 6039J (thanks @Faustop)
- lockscreen rotation toggle should now work as expected
- removed some unused services (thanks @Unjustified_Dev)
- added sepolicy (might cause some issues, please test)
2016-01-14
- fix inverted camera for those with samsung rear cam (confirmation needed)
- lockscreen rotation can be toggled now
- Security Patchlevel January
2016-12-09
- Now supports A, K,S and Y models (If you have another variant, please refer to [URL="http://forum.xda-developers.com/showpost.php?p=64000973&postcount=57"]this post[/URL])
- minor changes to camera
- Security Patchlevel December
2015-11-27
- Now supports A, K and Y models (If you have another variant, please refer to [URL="http://forum.xda-developers.com/showpost.php?p=64000973&postcount=57"]this post[/URL])
- LTE can now be chosen as preferred network
- added tethering options
- fixed writing to sd card
Detailed changelog:
https://github.com/pivoq/android_device_alcatel_idol347/compare/aa2b95e...pivoq:3df7e26
2015-11-18
- fixed regression which prevented access to bootloader
- added some missing camera blobs
- removed lots of unused stuff
- added some system.prop optimizations from upstream cm
2015-11-15
- added option to disable battery light
- added support for f2fs filesystem on /data and /cache (requires recovery that supports it, e.g [URL="https://www.androidfilehost.com/?fid=24269982086999020"]this one[/URL])
2015-11-09
- initial release
Click to expand...
Click to collapse
Thanks To/Credits
Code:
@Unjustified Dev
@petrov.0
@ashwin007
XDA:DevDB Information
CyanogenMod 12.1 for Alcatel ONETOUCH IDOL 3 4.7, ROM for the Alcatel Onetouch Idol 3
Contributors
pivoq, Unjustified Dev, petrov.0
Source Code: https://github.com/pivoq/android_device_alcatel_idol347
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
Based On: CyanogenMod
Version Information
Status: Beta
Created 2015-11-09
Last Updated 2016-04-06
Reserved
As requested, here's a thread for the 4.7" device. The build runs fine on my end without any major flaws (6039Y), however I expect rough edges on other device variants, especially those featuring dual sim functionality.
So please give feedback and provide logs if you find any bugs.
I really don't want this to be a one man show, so I encourage everyone willing to build/contribute to check out my github and get involved!
Oh! great
First release going to test this
Thanks @pivoq :good:
Can someone post a fleshable kernel for this rom. I'll try to mod it a little. Maybe it can overclock a bit, just to try smth new.
P.S CM rom is great, minor bugs, but it's nothing.
Nelle9900 said:
Can someone post a fleshable kernel for this rom. I'll try to mod it a little. Maybe it can overclock a bit, just to try smth new.
P.S CM rom is great, minor bugs, but it's nothing.
Click to expand...
Click to collapse
Could you please be more specific on what bugs you are talking about
too bad there is no stock camera
pivoq said:
Could you please be more specific on what bugs you are talking about
Click to expand...
Click to collapse
Sometimes terbuchet or what else, stopped working. I do factory reset today and i didn't see again that problem. Maybe it fixed the problem, consider that solved.
Personaly i do not like dbl tap on status bar to lock screen, but better that then nothing.
One thing i noticed when i place a call, that is seems to be to quiet sound. I can't sometimes clearly hear what is person talking to me. But not a big problem, it heppens sometimes.
Problem on instagram is solved with this rom. On 5.0.2 I have video problem on instagram, video do not play always.
My recommendation is kernel tweaks, maybe some minor overclocking to cpu and gpu, just for test, maybe that will speed up a lilttle bit this respectable device we have.
Best regard man and sorry for my bad english
And can someone post fleshable kernel of this rom? Thanks in advance.
Nelle9900 said:
Personaly i do not like dbl tap on status bar to lock screen, but better that then nothing.
Click to expand...
Click to collapse
You can disable it in settings
Nelle9900 said:
And can someone post fleshable kernel of this rom? Thanks in advance.
Click to expand...
Click to collapse
What do you mean exactly? You can flash the boot.img using fastboot. And the kernel source is on github.
thanks to make this for 4.7. system working faster than stock.
- nice audio equalizer but black player got better
- there is cm camera but missing some manual options like shutter speed - so i wait for change this
- double tap to on/off - there is trick to use gesture with nova launcher and app "screen off and lock" but when you are in lock screen tap working only around status bar
pivoq said:
You can disable it in settings
What do you mean exactly? You can flash the boot.img using fastboot. And the kernel source is on github.
Click to expand...
Click to collapse
I know that u can disable it, i didn't mean that, i love that option, but personaly didn't like to tap on status bar, it's better to tap on screen (midlle of screen). But it's okay man
Kernel - i don't know how to download fleshable kernel from github
I wont to mod the kernel, set a higher freq for cpu and gpu = overclock. If you know how to download and make a flashable kernel i will mod it.
First post was updated with latest build.
Current changelog: 2015-11-14
- added option to disable battery light
- added support for f2fs filesystem on /data and /cache (requires recovery that supports it, e.g this one)
Google service isn't working.
I can't login.
"Unfortunately, Google has stopped play services."
I tried opengapps pico, nano, stock, super.
Older versions work fine
Same problem here, opengapps crashing, i will try with an older version of gapps
edit: still fc, even with 04-04-2015 gapps 5.1.1 version :-s
logs or didn't happen
hope it helps
(I archived it, because it was over the 500kb limit requested from the forum..)
Scutariu said:
hope it helps
(I archived it, because it was over the 500kb limit requested from the forum..)
Click to expand...
Click to collapse
Thank you, apparently there went something wrong building chromium webview.
I will probably have a fresh build by tomorrow. In the meantime can you try if installing "Android System Webview" from play store fixes the issue?
pivoq said:
Thank you, apparently there went something wrong building chromium webview.
I will probably have a fresh build by tomorrow. In the meantime can you try if installing "Android System Webview" from play store fixes the issue?
Click to expand...
Click to collapse
I can't acces play store, when I try to add my google account, it crashes automatically
Scutariu said:
I can't acces play store, when I try to add my google account, it crashes automatically
Click to expand...
Click to collapse
https://www.apkmirror.com/apk/googl...ebview-47-0-2526-61-arm-android-apk-download/
DISCLAIMER
Code:
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 us for messing up your device, we will laugh at you.
*
*/
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. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Steps to install:
(0. Install any 6.0 rom)
1. Factory reset
2. Make sure you format /system and /data to ext4 for the install
2. Install ROM zip, you will get a warning about partition size change of system if its the first time you flash, just flash it a second time to confirm the change, this will erase your data partition!
3. Please do NOT install Gapps (you can still do it, but at your risks)
4. Reboot
5. Wait for a long time
Known Bugs:
- First boot is slow
- RIL sudden crash (?)
- Webkit render issues with the latest cm14.1. It will be fixed in the next build.
- CM's FileManager is bugged
Features:
- Stock Cyanogenmod 14.0
- Dirty CoW patched kernel (anyone cares ?)
- kernel built with GCC 6.2.1 with -03
- F2fs support on /data but not on /system
- Bigmem enabled (no cma for now)
- sdcardfs support to come someday
- Zram enabled
Please note that this rom is not ready for daily usage yet, it's an alpha.
Downloads:
Android 7.0:
http://www.mediafire.com/file/5d1fdr0f75rywml/cm-14.0-20161120-UNOFFICIAL-galaxysmtd.zip
Android 7.1.1:
http://www.mediafire.com/file/xfcjvn1y1vjwwpu/cm-14.1-20161223-UNOFFICIAL-galaxysmtd.zip
I will provide mirrors later if needed.
Please check the MD5 !
094fa2133073f22cea28e80d18a628e5
HUGE thanks to @xc-racer99 for his AMAZING work on his variant, without him, this woudn't have been possible at all.
XDA:DevDB Information
CyanogenMod 14.0, ROM for the Samsung Galaxy S I9000
Contributors
Coldwindofnowhere, xc-racer99, sooti
Source Code: https://github.com/CyanogenMod
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Version Information
Status: Alpha
Created 2016-10-28
Last Updated 2016-12-23
Reserved
Changelog:
23/12/2016
Android 7.1.1 r6
No more crashes due to the graphic driver
Working ril (except data on the first boot apparently ?)
Fixed internal storage issues
Updated kernel
Latest TWRP (without their new app, tell me if you want me to add it back)
20/11/2016
Latest CM 14.0
As people wanted, cmc is back
Tweaked art settings (lag should be gone)
Fixed video recording
Fixed MTP crash
Fixed adb authkey issue
Disabled SDcardFS
More stable RIL (but there are still issues with 3g)
28/10/2016
Initial release
Reserved
FAQ & tips :
Where is SuperSU ?
You don't need to flash SuperSU, just enable it under the Developer options.
How to change Bigmem modes ?
You can change it in advanced parameters>Bigmem
What are the best schedulers/governors/...
That's up to you, personaly, I like the combinaison of smartassV2 and bfq.
But ... how to change them ???
You can use Kernel Adiutor or any other app like that.
When will you release the next build ?
Don't ask for ETA ..... and wait.
Something isn't working, please fix it, please PLEASE
Logcat. No logcat == no fix.
If you don't know how to logcat properly, read this.
My phone is bootlooping ,what can I do ?
Pull battery and restart. Also don't forget to do a factory reset before flashing this rom.
Can you add X feature on your rom ?
No. I wont add additional features, this is stock cm. The only thing I might add is signature spoofing support.
Here are a few additional tips to get the most of this rom :
Format /data in f2fs in TWRP
OC your cpu if it can handle it
Use Bigmem
Don't install unnecessary apps
Remove apps from startup
(Wait for the next build)
Wow!!! It is impossibly! Big thanks!!!
+1
:good:
Link is up, make sure to check the md5sum and tell me if you experience issues.
Logcats appreciated !
Ok, just tested it. Was compared with AOSP 7 from x-racer99.
Seems CM14 more laggy in games. Not so smooth like an AOSP. But problem probably is not in the kernel. Cause i was also use x-racer99 kernel on your CM14 rom. Look at this videos with Mega Jump game:
https://youtu.be/ueyjuPu3BgA AOSP rom by x-racer99
https://youtu.be/FWbCNKZdAdE Cyanogenmod 14 rom with x-racer99 kernel.
Second video is not so smooth with a lot of jerks. May be problem in low memory killer settings, or GFX drivers, or V-Sync, or build.prop tweaks, i do not know.
Also i prefer CMC instead Voodoo Color. Because VoodooColor have two bugs since android 2.x.x. It is yellowish tint of all screen (CMC have more right white balance) and green bug on low backlight with high gamma settings, look at this video:
https://youtu.be/gkP7VgWbTlY
Thanks for the feedback, I guess that's related to various properties in build.prop. I will experiement a bit to see if I can improve this.
About CMC, you can tweak voodoo by yourself, but yeah if many people want me to switch to CMC, I will do it.
Coldwindofnowhere said:
Thanks for the feedback, I guess that's related to various properties in build.prop. I will experiement a bit to see if I can improve this.
Click to expand...
Click to collapse
You can just download Subway Surfer from market or another place and try to make run this game more smoother. Some times Subway Surfer have bad responce on touch and can hung up after long play. Also can try this on Mega Jump or other dynamic game.
Thank you!
Ok, one question. I know it takes forever on the first boot, but, how long does it take? I've been waiting almost 45 minutes for it...
First boot was around 15 - 20 minutes for me.
Bugreport:
-not all apps correctly work with sd-card. I cant scan cards by MXPlayer for example.
- camera can't save videos.
What are the libs used in the rom? Pathed for bigmem or regular?
P.S. Issue with MXplayer was resolved by itself after reboot phone.
M1n3cr4f7.G4m35.2015 said:
Ok, one question. I know it takes forever on the first boot, but, how long does it take? I've been waiting almost 45 minutes for it...
Click to expand...
Click to collapse
Um pull off the battery, start the phone again. Got this issue once but no idea why.
jupiter5700 said:
First boot was around 15 - 20 minutes for me.
Bugreport:
-not all apps correctly work with sd-card. I cant scan cards by MXPlayer for example.
- camera can't save videos.
What are the libs used in the rom? Pathed for bigmem or regular?
Click to expand...
Click to collapse
Bigmem patched, I haven't tested 720p videos tbh.
This rom can run on samsung wave?
thinhx2 said:
This rom can run on samsung wave?
Click to expand...
Click to collapse
I haven't tried but as it's really similar to the i9000, you should give it a try.
Coldwindofnowhere said:
I haven't tried but as it's really similar to the i9000, you should give it a try.
Click to expand...
Click to collapse
Screen is different. You think driver display of i9000 can work on wave?
thinhx2 said:
Screen is different. You think driver display of i9000 can work on wave?
Click to expand...
Click to collapse
Um having a quick look at https://github.com/Badadroid/android_kernel_samsung_aries, looks like it wont be possible, additional kernel drivers are needed.
Coldwindofnowhere said:
Um having a quick look at https://github.com/Badadroid/android_kernel_samsung_aries, looks like it wont be possible, additional kernel drivers are needed.
Click to expand...
Click to collapse
You can public your kernel for aosp 7 of ss s1?
thinhx2 said:
You can public your kernel for aosp 7 of ss s1?
Click to expand...
Click to collapse
https://github.com/Coldwindofnowhere/android_kernel_samsung_aries/commits/staging
No way man, nice work
Android 7 N for s1
Ejgjskfkcisvjj hahah
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click here to get to the new post where we'll keep updating this rom
What it is
It is an LineageOS 14.1 alpha build from official LineageOS sources devices trees and fresh caf 3.4 kernel port. This is not related anymore (2017-03-22) to the Sony Open Device Project (sonyxperiadev). They work on a different way and we are helping each others as often as possible.
This rom is worked to be as stable as possible to be used as a daily driver. There are no changes into LineageOS sources, manifest to build is attached in this post. The idea is to share this built with the community to improve this rom. If it is good enough, maybe, someday, get official again for our D6603. Thanks a lot to @tomascus who made this possible. (his donate link)
Disclaimer
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 me for messing up your device, I will laugh at you.
*
*/
Who can use it
It is only for Z3 and UNLOCKED UPGRADED BOOTLOADERS
How to install
%= Only needed at first flash
% Update ROM to .291 with emma (or Flashtools)
% When install is done go into fastboot mode (plug usb + vol down key = blue led)
% Flash this TWRP (version 3.1.x) | If you are a Z3 Dual user, flash zip below before installing Z3 Dual version. / If you already are in .291 and have a working TWRP (modded rom/kernel/adv kernel) you can use the flashable zips below instead.
Shutdown the device
Unplug the usb cable
Maintain volume down & power until you see twrp splash screen
% Wipe system, cache and data
Install rom zip (+ % gapps if you need it)
Reboot
Rolling back to stock
Flash stock rom with emma or flashtool
If you flash with flashtool remember to check wipe apps_log and userdata partitions to get a clean install
What gapps to flash?
Use f-droid
You can flash any gapps you want, our partition is 2GB and rom is 700MB:
Code:
z3:/ # df -h
Filesystem Size Used Avail Use% Mounted on
/dev/block/mmcblk0p23 2.4G 680M 1.7G 28% /system
Just take 'arm' and not 'arm64'
Gapps need to be flashed at first rom flash!
NEW RELEASE
2017-06-13:
Xperia Z3
Download
md5: 2d4ca5f88de0303575f2ab9c249d521f
TWRP 3.1.1 - 2017/06/09
Xperia Z3 Dual
See below
md5: 360fd6f9e0e22eb4ff0de72059c7de24
TWRP 3.1.1 - 2017/06/09 | Mandatory if coming from Z3 builds or new to the rom.
Temporal Z3 Dual rom (fixes SIM problems)
nailyk said:
Many thanks to @xkeita for providing a working rom as soon as the device get delivered.
20170622 / b8a79c826ddf0a786010cc04b3943b2e
twrp / 61e8c27f19c114dc9ac1f33dd4c7fb39
Rom is tagged nailyk because I build it but everything on it is @xkeita work!
Many thanks everybody
Click to expand...
Click to collapse
What's new:
Code:
- Updated Camera profiles
- Reworked Z3 Dual RIL
- Updated Audio HAL flags
- BFQ I/O Scheduler
- Bluetooth aptX support
- Qualcomm Connectivity Engine support
- Imported audio ids from original .291
- ANC Headphones support
- Dual Mic config enabled for voice calls/audio recording
- Ok Google everywhere fixed (untested)
- Tweaked autobrightness (again)
Release notes:
2017-06-09 is just a minor update with some [experimental] tweaks for bt connections and fixed minor issues with z3dual
Older Releases
Based on Kernel 3.4
Some of these can be found here
Release History
Code:
2017-06-09:
- Tweaked a little bluetooth values (untested)
- Fixed Z3 Dual sim problems
- Latest Google source (7.1.2_r17)
- June security updates
- Permission fixes for new PowerHAL
- Z3 and Z3 Dual code cleanup
- Forced camera modes to [email protected], [email protected], [email protected], [email protected]
- Fixed all of the device sensors (they're all online and working properly now)
- Latest LineageOS updates
- Smoother UI rendering with CPU
2017-05-17:
- Tweaked general audio output processing
- Updated vendor audio libraries configs (enables qcom effects)
- Auto brightness/brightness changes
- New thermanager configs based on stock
- Changed deprecated Gello for Jelly
- Some device tree cleanup
- General radio/wifi tcp updates
2017-04-16
- Audio changes,
- NFC fixes,
- Brightness changes,
- Verbosity increased for logs after night reboot + PERISTENT_TRACER
- No more vol- buton at boot time
- A lot more
2017-04-05:
- Enforcing selinux
2017-04-01:
- Audio fixes
- Encryption fix
- A lot more that I can't remember right now
2017-03-22:
- Full rework based on stock 3.4 kernel
Based on Kernel 3.10 by @nailyk
2017-01-23:
Download
md5: 04a3a614d820df78e7a70538df61203d
sha1: 10a3ea95d823a6b87b5f5a8f79896e3dabf7a8b5
Status
Workaround for in-call reboot
Include PR1130 PR1128
2017-01-15:
Download / 2
md5: 8b8898c18d631dc7f9d78a18b1e7500f / b40c7ba870ae579827e1bd7a427afc1f
sha1: 588d2c1e0fd2ef4790706980fc1050a8d793d559 / f28ba7714987a94c5ba43a6ee39fe05f0b5a5fca
Use of the reworked device trees
Include some experimental kernel pull requests
2017-01-01:
Download
md5: 6c5abcbeda01c75344cd4296bb2358d1
sha1: a46ef81e2d26ac9610f16cb90bc13e63d58a2983
Switch to LineageOS
Bluetooth deepsleep fixed
2016-12-02:
Download
md5: 496de65608fd4236f5d451a4179e1ce8
sha1: 74a25eabc0f8ac5be3458bd9d98461f9519c7c73
Bluetooth improvements
P.S.: i'm almost affiliated to LineageOS, just like tomascus who made everything.
Sources
Manifest file.
Everything else is Lineage.
Contribute gerrit.
XDA:DevDB Information
LOS-14.1, ROM for the Sony Xperia Z3
Contributors
nailyk, xkeita
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Based On: LineageOS
Version Information
Status: Beta
Beta Release Date: 2017-06-09
Created 2016-11-27
Last Updated 2017-07-01
Thank you!
Thanks to
@tomascus
@xkeita
@derf elot
@panzerox123
@Robot76
@gr8st
@mcgi5sr2
@rcstar6696
@yecomixer
@TheAvengingTITAN
@@AdrianDC
@@doriandiaconu
@SuperLamic
@DiscMan55
@drakonizer
@aclegg2011
@DevUt
@tomascus
@blackhawk_LA
@erickas
@malacha
@jimRnor
@optimumpro
@steadfasterX
@Myself5
All the members of the ivy team: @Quarx, @Olivier, @cdesai, @Myself5 and the one I miss.
TeamWin
LineageOS
All the dev who made the downstream kernel
All of you for testing rom and supporting me
FAQ
How to post
I want to say thanks --> Thanks you. Gratitude is really important for us. Find some posts from us and hit thanks buttons. It will be most appreciated You can also use @tomascus donate link.
We are here into the dev thread, not user one. For now the rom is under development.
We wont talk here about not related to device problems (where is foo setting, how to flash bar).
Reports will simply be ignored if already answered.
Reports without logs or step to reproduce are useless (read contribute).
Substratum is officially not supported into Lineage.
You are welcome to post your review: what is working, not working, etc... Check into know issues before.
You are welcome to post your unusual and not supported use-cases (like: "I have only ipv6 at home and the RA doesn't work without IPv4")
You are welcome to report any typo, error, etc...
No variant are supported now. Only D6603. You want support for variant? Consider help on porting or a hardware donate.
My device is screwed and I need it for my job interview in 1h --> go to IRC (how to report problem, #3)
I want say how SODP is bad --> Read this and above.
This is not against you but try to keep thread clean as a dev reference. Thanks in advance.
What is not working
BT headset calls --> pending. Detailed post.
OTG --> 2017-04-16
Wifi auto connect (boot/deepsleep),
HW Encryption, --> 2017-04-16
Vibrator level
4k (unfixable without Sony camera app)
120 fps (pending)
Some volume loudness problem --> not reported
Microphone when ok google is installed (do not install gapps will fix! An app which constantly record your microphone is a malware!) -->Pending,
Slow charging,
Phone reboot at 3AM while plugged-in, --> Workaround disable "auto time" into settings.
NFC, --> topic
Wifi access point,
Adaptive brightness not good. --> Fixed by @xkeita
How to report problems
To report problems there are multiples ways, depend on each person. The How to contribute section provide information on the way to do and should be applicable to everyone. The How to get logs section is the final touch on how to report problems.
Thanks wanting reporting, as, for an early development rom, reports are a necessary step to move forward
Some examples:
I cannot record videos with open camera.
Click to expand...
Click to collapse
Is useless on a dev thread and you probably won't get an answer.
Just wanted to report that this ROM doesn't support my 128gb sandisk SD card..and gives a message, unsupported SD card and asks to format.. this is the only bug which prevents me from using this ROM.. however the same card works perfectly fine on all other ROMs like 7.1 CM or AICP ROM and also all lollipop ROMs and stock ROM.
Click to expand...
Click to collapse
Is better as there is explanation, context and cross rom tests. With log this report used to be perfect.
This guide is really detailed and explained everything about bug reports. (deserve all bug-report cases, not specially this thread or xda)
@steadfasterX write a good guide about IRC, here you can get quick support (like when your device is totally broken, etc...)
steadfasterX said:
You talked about using IRC to get support. What is this and how can I use that?
Meaning of IRC => Internet Relay Chat. A very good IRC client is this one here: hexchat <-- download it and read the quick intro to get started: Quick-Start
--> when asked if you want to join a channel type in "#LineageOS" and after connected you will be in.
If you do not want to install anything you can simply use the webchat instead directly over here: Webchat
Howto communicate? IRC means many people talking the same time and there are some goods and bads to know about using IRC.
So please read this mini and very quick overview (especially the good manners there): Good manners in IRC (matches for all OS not for fedora only)
Click to expand...
Click to collapse
How to get logs
Here you have some info about how collecting log. It is always better to include reference to the Installed version.
How to contribute
I have c knowledge:
All the sources to build this rom are public and are provided into the manifest, in the howto build section. It means all the repository are from LineageOS github, except those mentioned into this manifest. Depending on where you find the bug/improvement there is different way to contribute: gerrit, github PR, etc... Contact me to test with you patch as everyone can try and give feedbacks then join IRC to discuss the best way to merge.
Code is like hieroglyphs for me:
No worries you can contribute anyway! Install the rom, do tests, read failure logs, look at internet for potential fix/similar users experience, is the biggest part of debugging. Then collect all of this and write your results here.
Code is like hieroglyphs for me and logs are worst:
No problem, collects logs the right way if you can, explain how you encounter the problem: detailed step to reproduce could be enough: explain exactly how you encounter the error/problem, it should produce each time someone repeat your steps. Then we will be able to fix it.
Installed version
When reporting problems, specially for work in progress, it is good to provide the build version:
- 'uname -a' will give you the kernel version,
- 'getprop ro.cm.display.version' will give you the rom build version.
What is LineageOS
LineageOS is re-brand of CyanogenMOD. At the end of 2016 some bad things appends. Lineage is the same rom that CyanogenMOD so you can still dirty flash, etc... However as all *cyanogenmod.org services are down, OTA update will not work until you flash lineage one time.
Thanks for posting this rom. Thank you for your awesome developing.
Great work man!!! I hope you will continue you work on CyanogenMod for Xperia Z3!!! Thanks
great work and z3 compact?
What I don't understand is you seem to be having a whole bunch of issues with CM, whereas Rhine devices build perfectly well and all features work on them.
Have you tried building AOSP using Sony Xperia dev sources?
Back in the cm13.0 days, all I used to do to build cm13.0 was use all AOSP device trees and HALs and just make a cm.mk and include vendor/cm/common_phone.mk and everything used to work perfectly fine. Have you tried that?
Anyway, I love the way you develop and your determination. I hope to see you around here often!
drakonizer said:
What I don't understand is you seem to be having a whole bunch of issues with CM, whereas Rhine devices build perfectly well and all features work on them.
Have you tried building AOSP using Sony Xperia dev sources?
Back in the cm13.0 days, all I used to do to build cm13.0 was use all AOSP device trees and HALs and just make a cm.mk and include vendor/cm/common_phone.mk and everything used to work perfectly fine. Have you tried that?
Anyway, I love the way you develop and your determination. I hope to see you around here often!
Click to expand...
Click to collapse
Thanks a lot but your are in a position to know that all the dev had been done by others and I am only porting for now
The biggest source of issue building CM was the codename change. Into sonyxperiadev and all other close to OEM codename is 'leo'. Historically cm rename the device to 'z3' because they already have leo (HTC hd2, IIRC). Here start the pain: as you build too you know a *bunch* of files are codename dependent. Also I wonder if a codename check isn't present into blobs.
I haven't tried to build aosp for now as I didn't have enough free space and wont learn another toolchain. But I test carbon rom which is really efficient.
I tried what you said and give me the best result. Now my branch are ~even with sonyxperiadev. The problem is those version can't be pushed to official CM repo.
We are now experiencing problems on hardware accelerated display, like FPS drop, but I'm not able to fix this. So next step is deep sleep. Are you experiencing this too? Can I ask you some points about this please? Like enabling debugfs, collecting logs after tests etc...?
Edit:
mcgi5sr2 said:
We are still getting echo on the line and a static in call volume issue on the d5803 with latest sources. rancidfrog has provided logs
https://github.com/sonyxperiadev/device-sony-aries/issues/49#issuecomment-263256754
is the issue isolated to the Aries or do Leo users have this issue as well? Similar question to Honami board devices?
Click to expand...
Click to collapse
Can you report me as I can answer please?
nailyk said:
Thanks a lot but your are in a position to know that all the dev had been done by others and I am only porting for now
The biggest source of issue building CM was the codename change. Into sonyxperiadev and all other close to OEM codename is 'leo'. Historically cm rename the device to 'z3' because they already have leo (HTC hd2, IIRC). Here start the pain: as you build too you know a *bunch* of files are codename dependent. Also I wonder if a codename check isn't present into blobs.
I haven't tried to build aosp for now as I didn't have enough free space and wont learn another toolchain. But I test carbon rom which is really efficient.
I tried what you said and give me the best result. Now my branch are ~even with sonyxperiadev. The problem is those version can't be pushed to official CM repo.
We are now experiencing problems on hardware accelerated display, like FPS drop, but I'm not able to fix this. So next step is deep sleep. Are you experiencing this too? Can I ask you some points about this please? Like enabling debugfs, collecting logs after tests etc...?
Edit:
Can you report me as I can answer please?
Click to expand...
Click to collapse
As far as I know, which is from my honami tests, deep sleep issue was present only in AOSP builds. A quick look at BBS revealed that it was the radio(ProxyServer) that kept the device awake, and using the phone without SIM would let it go into deep sleep.
When I got a chance to build and test cm14.1, there was no such issue with deep sleep.
In order to figure out whether we have the same issue, could you (or someone else in this thread) use BBS and tell me what the app says?
As for hardware issues: since you're using Sony HALs and device trees, I don't understand why you're having said issues.
AOSP doesnt need any new knowledge, in fact, it should be easier to build and test. If you can clear some space, I suggest you try it. It could rule out any issues with the device trees or Sony HALs, and then you can focus on finding the issue with CM.
Hello, I dont get it, where is the download?
I want it sooo badly, but I am to dumb to find the download
Shadow of Destiny said:
Hello, I dont get it, where is the download?
I want it sooo badly, but I am to dumb to find the download
Click to expand...
Click to collapse
As you can see there are no releases in the opening post. I guess that if you really want to help testing you have to ask nialyk for a flashable version. Be aware though that, as stated by the developer, the ROM has still many bugs that harm usability.
mattia.bf said:
As you can see there are no releases in the opening post. I guess that if you really want to help testing you have to ask nialyk for a flashable version. Be aware though that, as stated by the developer, the ROM has still many bugs that harm usability.
Click to expand...
Click to collapse
Well, thanks then.
Shadow of Destiny said:
Hello, I dont get it, where is the download?
I want it sooo badly, but I am to dumb to find the download
Click to expand...
Click to collapse
Link is not yet added because I'm dealing with weird GPU issues and I'm waiting for a feedback about a fix before adding it. It should be ok in some hours.
drakonizer said:
As far as I know, which is from my honami tests, deep sleep issue was present only in AOSP builds. A quick look at BBS revealed that it was the radio(ProxyServer) that kept the device awake, and using the phone without SIM would let it go into deep sleep.
When I got a chance to build and test cm14.1, there was no such issue with deep sleep.
In order to figure out whether we have the same issue, could you (or someone else in this thread) use BBS and tell me what the app says?
As for hardware issues: since you're using Sony HALs and device trees, I don't understand why you're having said issues.
AOSP doesnt need any new knowledge, in fact, it should be easier to build and test. If you can clear some space, I suggest you try it. It could rule out any issues with the device trees or Sony HALs, and then you can focus on finding the issue with CM.
Click to expand...
Click to collapse
IDK what BBS is but the /sys/kernel/debug/wake_lock table is really instructive. From the early experiments we have two issues: like you ril is one of them, and usb is the second one. If your reboot the device in airplane mode without usb attached wake_locks are a bit better.
Yes building AOSP is a good idea but @accleg2011 never get it working so I really doubt I can. Device was really fine on CAF display, game were really smooth, menu too. With SODP display menu are ok now but game are laggy and I don't know how to check if they are software or accelerated rendered. I tried to mimic hammerhead config.mk (it is the same device than z3 except for camera) but it doesn't provide results. I'm almost sure it is another PEBKAC with a missing flag.
I have a bunch of log to analyse and will post my results a bit later. Thanks for your advice, maybe I simply should buy another ssd.
If you have some time to waste, can you try frozen bubble on your device with SODP display, please? When balls pop, it is the most GPU intensive rendering. Is it laggy for you too? (from what I see ~5FPS)
nailyk said:
Thanks a lot but your are in a position to know that all the dev had been done by others and I am only porting for now
The biggest source of issue building CM was the codename change. Into sonyxperiadev and all other close to OEM codename is 'leo'. Historically cm rename the device to 'z3' because they already have leo (HTC hd2, IIRC). Here start the pain: as you build too you know a *bunch* of files are codename dependent. Also I wonder if a codename check isn't present into blobs.
I haven't tried to build aosp for now as I didn't have enough free space and wont learn another toolchain. But I test carbon rom which is really efficient.
I tried what you said and give me the best result. Now my branch are ~even with sonyxperiadev. The problem is those version can't be pushed to official CM repo.
We are now experiencing problems on hardware accelerated display, like FPS drop, but I'm not able to fix this. So next step is deep sleep. Are you experiencing this too? Can I ask you some points about this please? Like enabling debugfs, collecting logs after tests etc...?
Edit:
Can you report me as I can answer please?
Click to expand...
Click to collapse
Hi I posted this in a different thread and am confused as to how it came up in your CM14.1 thread. I build using all the sonyxperiadev device trees
mcgi5sr2 said:
Hi I posted this in a different thread and am confused as to how it came up in your CM14.1 thread. I build using all the sonyxperiadev device trees
Click to expand...
Click to collapse
Pardon my clumsy. I quote you here because thinking that cm can provide useful results for your question as we are using the same devices trees and blobs. Won't do it again.
nailyk said:
Pardon my clumsy. I quote you here because thinking that cm can provide useful results for your question as we are using the same devices trees and blobs. Won't do it again.
Click to expand...
Click to collapse
Hey no problems, I'm actually battling just to get my latest CM build to install properly
mcgi5sr2 said:
Hey no problems, I'm actually battling just to get my latest CM build to install properly
Click to expand...
Click to collapse
Do you take a look at Myself5 repos ? You can ask him a CarbonRom test but his repo where very helpful for leo. Also, maybe you can reuse mine and we can concentrate our efforts. I try to be as close as possible to SonyCM ones.
I will update the OP with the build instructions when XDA will work.
2016-11-28 release
Rom link added.
I'm currently uploading screenshots.
A bunch of peripherals are broken. Since I test this PR bluetooth is broken.
Hardware accelerated part are missing or broken.
Camera is partially working, switching to video mode crash camera app.
Deep sleep still not working.
Gps seems to be broken too.
Don't forget we are into a dev thread please, so post comments with logs, faulty line or patches. Thanks.
This rom is not intended to be used as a daily driver and is unstable!
cm14.1 wowww :good:
After a total mess-up with bluetooth, a full rebuild make it ~work again (still some crash).
And 3D apps seems to be working too.
Can you confirm/infirm difference please?
Unofficial LineageOS 14.1 for Sony Z1 Compact
Code:
#include
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
General
This is an unofficial LineageOS 14.1 as is build for the Sony Z1 Compact, (Amami/D5503).
The builds will be builds when i want it, as long as LineageOS updates and support LineageOS 14.1 or when it goes official.
I won't include features that I dislike. If u want something else, build it.
Install
How to install:
New Install (coming from another ROM)
Do a full backup with your favorite latest Nougat compatible recovery (3.1.0.0 ATM)!
Download the Rom zip and an OpenGapps file for 7.1.2, 32 bit, Arm
Do a full wipe in recovery (data/factory reset, system)
Install the Rom zip and Gapps zip through recovery compatible with Nougat!
Enjoy!
Coming from previous version of LOS14.1
Do a full backup with your favorite latest Nougat compatible recovery!(optional, for if things go wrong)
Download the Rom zip
Install the Rom zip (and Gapps if getting erros with Google services) through recovery compatible with Nougat!
Enjoy!
Downloads
Latest-Rom: lineage-11-20170810-UNOFFICIAL-smi.zip
XDA Download Section
Github Version number is different
Project manifest
Manifest/Roomservice
Bugs/Issues
HW overlay needs to be disabled for some full screen video applications and front camera
Bluetooth may not work as expected
Reboot to recovery doesn't always work
Needs a compatible recovery to install
Camera may not work 100%
Will never pass full CTS test?
Wifi starts without data connection after reboot
NFC HCE will maybe never be supported, used for android pay
Thanks and credits
SpiritCroc
SuperLamic
All MSM8974 Maintainers
Sony (OSS)
LineageOS
All the rest that have helped to construct these builds and develop software for Z1 Compact directly or indirectly in the past.
XDA:DevDB Information
Unofficial LineageOS 14.1, ROM for the Sony Xperia Z1 Compact
Contributors
Hazou
Source Code: https://github.com/LineageOS
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Based On: LineageOS
Version Information
Status: Testing
Current Beta Version: lineage-14.1-2017080
Beta Release Date: 2017-08-10
Created 2017-07-14
Last Updated 2017-08-10
Hazou said:
Unofficial LineageOS 14.1 for Sony Z1 Compact
I won't include features that I dislike. If u want something else, build it.
2017-07-14
Click to expand...
Click to collapse
Nice, thanks. Could you summarize which features you did implement? I'm currently using LOS by Micha-Btz, and it's working great,but I might try this out if it's any different...
levone1 said:
Nice, thanks. Could you summarize which features you did implement? I'm currently using LOS by Micha-Btz, and it's working great,but I might try this out if it's any different...
Click to expand...
Click to collapse
Can't say for sure what he changes. Not all his repos are open to public.
This version is the latest updated version of lineage, at the time of build. With all the newest changes from the msm8974 maintainers to get a working Android 7.1.2 on this device. The only extra difference is that I included the smartcard API, so u could use NFC pay with a compatibele sim card.
Hazou said:
Unofficial LineageOS 14.1 for Sony Z1 Compact
Click to expand...
Click to collapse
Which kernel does this ROM use? I can't find a repository at your GitHub
Might be a good idea to link to these sources from OP as public sources are required by GPL.
Btw, this information seems to be wrong
Hazou said:
Downloads
Latest-Rom: lineage-11-20170227-UNOFFICIAL-smi.zip
Click to expand...
Click to collapse
hahnjo said:
Which kernel does this ROM use? I can't find a repository at your GitHub
Might be a good idea to link to these sources from OP as public sources are required by GPL.
Btw, this information seems to be wrong
Click to expand...
Click to collapse
Thx for sharing. Will add them right away. They are indeed not on mine or lineage GitHub. The kernel source is on another GitHub. Will add a local_manifests to the message.
Thx. Works great so far.
My findings:
- original Sony camera app has that hw overlay issue.
- automatic brightness seems to be calibrated to bright
- wlan works smoothly (current aicp has has issues with that)
Not tested Bluetooth yet
Regards
Update:
[2] lineage-14.1-20170721-UNOFFICIAL-amami.zip
Fixes:
Audio_effect fix
A tiny bit better battery life
Fix nightly reboot when charging
Thermal improvements in config
LineageOS changes
Known bugs:
HW overlay needs to be disabled for some full screen video applications
Bluetooth may not work as expected
Reboot to recovery doesn't always work
Needs a compatible recovery to install
Camera may not work 100%
Will never pass full CTS test?
Wifi starts without data connection after reboot
NFC HCE will maybe never be supported, used for android pay
Great firmware!
Problems with lineage-14.1-20170721-UNOFFICIAL-amami.zip
- I still get nightly (while recharging) and some times random reboots
- HW Overlay with Camera
I didnt have any other issues yet
@Hazou thanks for your work! This device still can work well and thanks for support LOS!
Pardon, is it possible to have this feature enabled to receive mms when data is disabled? It can be much of annoyance and inconvenience to have data always be turned on for those with limited data or having to turn data on and of manually just to receive mms
https://review.lineageos.org/#/c/172853/ I can beta test a patch if need, very useful feature. This device deserves a good maintainer like you!
Thanks again sir for attention!
echo124 said:
@Hazou thanks for your work! This device still can work well and thanks for support LOS!
Pardon, is it possible to have this feature enabled to receive mms when data is disabled? It can be much of annoyance and inconvenience to have data always be turned on for those with limited data or having to turn data on and of manually just to receive mms
https://review.lineageos.org/#/c/172853/ I can beta test a patch if need, very useful feature. This device deserves a good maintainer like you!
Thanks again sir for attention!
Click to expand...
Click to collapse
Thank you, But I am not alone Doing this stuff with many others
And yes, we could implement this, than u need to test it, will have a look at it for next update
Hazou said:
Thank you, But I am not alone Doing this stuff with many others
And yes, we could implement this, than u need to test it, will have a look at it for next update
Click to expand...
Click to collapse
Great, will test and thans much to all developers for their time and awesome work! Thanks for this very much!
is the gps working?
- GPS works
- HWOverlay needs to be disabled for Cam or Youtube
- Nightly reboots if the phone is charging over night - even with 21.07.2017 version
Hopefully the team could fix it. Great work so far
Frash said:
- GPS works
- HWOverlay needs to be disabled for Cam or Youtube
- Nightly reboots if the phone is charging over night - even with 21.07.2017 version
Hopefully the team could fix it. Great work so far
Click to expand...
Click to collapse
Yup, we are working on them. Just takes a lot off time to debug and find the issue. Also it's holiday season; sun, beach, party
New version 8-10
Changelog:
3AM bug solved
Touch firmware update (changed to stock amami)
Time correctly set at boot
Update in media codecs/profiles
BLE peripheral mode enabled
Network type change and search should be fixed
Thanks for the update!
Thanks for the update, Hazou!
Unfortunately, changing of network operator does not work with my 2 SIM cards.
I can change the network type and search for network operators, but changing the network operator is not possible.
I have tested various ROMs (AICP, Lineage - yours and Micha-Btz - and Paranoidandroid, v6.03).
Only with the stock Rom and with Paranoidandroid I can change the network operator.
The problem seems related to accessing the SIM card (at least my SIM cards). When the Z1C can read the contacts stored on a SIM card, I can also change the network operator.
Can you change the network operator without problem?
Hi Hazou,
there also seems to be a problem with the telephone function if you toggle the loudspeaker or the mute button during a call.
Once you click mute and enable the mic again, it will stay muted... Same problem seems with the loudspeaker button from time to time.
Would be great if this could be fixed.
Good work! It is really appreciated!
Hi Hazou,
I have also a problem with telephone calls. The microphone seems always to be muted.
When I use Google Duo or WhatsApp Calls if works flawlessly.
The reboot bug while charging is also still existant.
Bisides that: Nice work, thanks for that.
Introduction
nem0 Kernel is CAF based kernel aiming to provide great stability and performance while maxing out battery life!
Code:
// Your warranty is now void.
//
// I am 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 Kernel before flashing it!
// YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Main Features:
- Unified for OOS 10 and Android 10/11 Custom ROMs
- Based and upstreamed to latest CAF tags for the SD855
- Upstreamed to latest Linux-Stable
- Upstreamed to latest F2FS stable
- Compiled with Clang 13 and -O3 speed optimizations flags
- SCS, CFI, DCE, Polly optimizations
- Simple LMK driver from kerneltoast
- BBR2 TCP congestion algorithm
- 675 MHz GPU OC
- PELT scheduling mechanism
- Many scheduler backports from mainline and/or 4.19 Google kernel
- Zip made using latest AnyKernel3 release, retains root on flash (Stable Magisk 21.4 or higher reccommended)
- Zip flashable through EXKM/FKM/TWRP
*FKM over-the-air updates are supported, import the following json:
*(https://raw.githubusercontent.com/nem0-z/android_kernel_oneplus_sm8150/master/ota/update.json)
- Many more features I don't remember right now, check source if you're interested or contact me on Telegram!
Bug reports:
- If you want to report a bug, please provide some sort of logs (logcat, dmesg)
Flashing instructions:
- Just flash it through TWRP or EX or Franco's Kernel Manager apps
- No sorts of configs needed, flash and be happy out of the box
Downloads
Stable and Test builds: Google Drive
Kernel being actively tested in this group: Telegram
Donations
If you would like to keep this project going with more improvements, feel free to support it: PayPal
Thank you to:
@0ctobot(Adam Willis) for great Neutrino Kernel base
@osm0sis for AnyKernel
@nathanchance for help with upstreams
@topjohnwu for magisk
@idkwhoiam322, @KuranKaname for being good friends
@BobAzzon, @npv12, @Gabyrx7, @Reechings and rest of my dear friends that tested the kernel (really, wouldn't be possible without you guys <3)
Contributors
nem0 aka AnnoyingZlatan
Source Code: GitHub
Version Information
Status: Stable
Created 2021-01-31
Last Updated 2021-01-31
Reserved
Meh, just in case
Works fine with latest crDroid build so far, although I lost root after flashing kernel only in TWRP (using Magisk Canary).
AnnoyingZlatan said:
- Zip made using latest AnyKernel3 release, retains root on flash
Click to expand...
Click to collapse
Toutatis_ said:
Works fine with latest crDroid build so far, although I lost root after flashing kernel only in TWRP (using Magisk Canary).
Click to expand...
Click to collapse
Yeah, latest AnyKernel 3 update works best with stable Magisk, so v21.4 and higher(once that comes), sorry about that, will edit the OP.
Unified for OOS 10 and Android 10/11 Custom ROMs
so is it not for OOS 11 OB1? Sorry for bad English
Get it while it's hot, been using this for a month. Great battery, snappy as sh*t. And the overall performance is second to none.
WesTD said:
Unified for OOS 10 and Android 10/11 Custom ROMs
so is it not for OOS 11 OB1? Sorry for bad English
Click to expand...
Click to collapse
No not yet
Ok people, v1.1 is out. It's a minor update.
Changelog:
- Switched to latest Clang 13 compiler
- Disable TTWU_QUEUE (noticed some regressions with it)
- Increase limit on schedtune groups from 7 to 8
You can find the build on Google Drive as always, link in OP
AnnoyingZlatan said:
Ok people, v1.1 is out. It's a minor update.
Changelog:
- Switched to latest Clang 13 compiler
- Disable TTWU_QUEUE (noticed some regressions with it)
- Increase limit on schedtune groups from 7 to 8
You can find the build on Google Drive as always, link in OP
Click to expand...
Click to collapse
Of course, you had to push this update mere minutes after I installed V1 to try it out. I feel so silly.
Regardless, installation has been smooth, doesn't overwrite Magisk in either release case, and performance feels about the same(?) as what I last used, kernel-wise? But I appreciate niceties like USB fast charge implemented. Working well on Resurrection8.x.
Can't connect to camera on guacamoleb on crDroid 6.14.
jmax91 said:
Can't connect to camera on guacamoleb on crDroid 6.14.
Click to expand...
Click to collapse
Now that you mentioned it, Camera (GCam) crashes out when it worked earlier today with my previous kernel.
Whelp. :x
SeongGino said:
Now that you mentioned it, Camera (GCam) crashes out when it worked earlier today with my previous kernel.
Whelp. :x
Click to expand...
Click to collapse
Can you try and reflash the previous kernel and see if it still happens? If yes then please share logs of those crashes as I can't reproduce it on my end and my testers had no issues.
AnnoyingZlatan said:
Can you try and reflash the previous kernel and see if it still happens? If yes then please share logs of those crashes as I can't reproduce it on my end and my testers had no issues.
Click to expand...
Click to collapse
Flashed, and it happens on v1 as well as v1.1. Log attached, using built-in camera app as the example.
The camera worked just a few hours ago, i.e. prior to me flashing this kernel, on the very same ROM (ResurrectionRemix 8.6.6), as well as there being no other substantial change (ROM, app updates, etc.) between then and now, so the environment isn't the issue.
2MIN_EDIT: Just to be sure, I reflashed my kernel previous to nem0 with no other change, and the Camera works as it should. No Camera-related Magisk tweaks installed with either; just QuickSwitch and Universal SafetyNet Fix.
SeongGino said:
Flashed, and it happens on v1 as well as v1.1. Log attached, using built-in camera app as the example.
The camera worked just a few hours ago, i.e. prior to me flashing this kernel, on the very same ROM (ResurrectionRemix 8.6.6), as well as there being no other substantial change (ROM, app updates, etc.) between then and now, so the environment isn't the issue.
2MIN_EDIT: Just to be sure, I reflashed my kernel previous to nem0 with no other change, and the Camera works as it should. No Camera-related Magisk tweaks installed with either; just QuickSwitch and Universal SafetyNet Fix.
Click to expand...
Click to collapse
Okay, would you mind coming to the Telegram group, I would like you to test some stuff out.
AnnoyingZlatan said:
Okay, would you mind coming to the Telegram group, I would like you to test some stuff out.
Click to expand...
Click to collapse
I don't usually do this, but am willing to follow through if it helps.
SeongGino said:
I don't usually do this, but am willing to follow through if it helps.
Click to expand...
Click to collapse
Ehm just to check something real quick, what device are you running?
@AnnoyingZlatan Can confirm built-in OOS Camera that comes with crDroid 7.2 (OnePlus 7 Pro) crashes after updating to 1.1. Works fine with 1.0.
Log attached.
Toutatis_ said:
@AnnoyingZlatan Can confirm built-in OOS Camera that comes with crDroid 7.2 (OnePlus 7 Pro) crashes after updating to 1.1. Works fine with 1.0.
Log attached.
Click to expand...
Click to collapse
Did you try the good old trick of long holding camera icon and going into portrait mode? I see nothing kernel related in those logs sadly.
New test build is up in Test Builds folder on Drive. Some of my testers verified camera working, need others here to test it as well. Report back please