Z1/HONAMI/C6903 SLIMKAT LINARO/SABERMOD WEEKLY BUILDS
Weekly Build 7.4 is ONLINE
DOWNLOAD
(infected server)
(md5sum included with all builds)
kernel code compiled with linaro arm-eabi-4.9.1 201407 toolchain
rom code compiled with with sabermod arm-linux-androideabi-4.8.4 201407 toolchain
-O3 optimizations
strict-aliasing rules
custom performance flags
+30 cherry-picks used
(buildbot: intel core i7 [email protected], asus p8z77-v, 8gb corsair vengeance pro 2133mhz cl9, sapphire hd7970 dual-x, 2x samsung 128gb ssd 840 pro raid 0 array,
4x western wigital wd3200aaks raid 10 array, samsung f1 1tb, silverstone olympia 1000w psu, antec 1200 high-tower)
(wc setup: swiftech apogee xt cpu-block, black-ice gtx-lite 240 radiator, 2x noiseblocker eloop b12-3 1900rpm fans, swiftech mcp355 water-pump, danger den 5.25" reservoir bay)
(Linux Mint 17 "Qiana" x64 3.13.0)
DONATIONS NEEDED
if you can, please make a small donation... you'll be supporting my work and time spent on these projects, helping me to keep website and dedicated server up and running, so i can deliver the downloads, host the builds, and pay the webdev.
The remaining donations, if any, ill go to a "piggy bank", to buy new devices...
Many thanks.
infected_
Click to expand...
Click to collapse
Disclaimer:
These builds are freshly compiled/synced from SlimRoms open-source code:
https://github.com/SlimRoms
latest linaro arm-eabi-4.9.1 used to compile the kernel code & sabermod arm-linux-androideabi-4.8.4 toolchains to compile ROM code
Special Thanks
SlimRoms Dev Team
XDA:DevDB Information
Xperia Z1/Honami/C6903 Linaro/Sabermod SlimKat Builds, ROM for the Sony Xperia Z1
Contributors
infected_
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Latest CWM Recovery or TWRP
Based On: SlimRoms
Version Information
Status: Testing
Current Stable Version: 7.0
Stable Release Date: 2014-08-05
Created 2014-07-24
Last Updated 2014-08-19
Install instructions:
first time
- power off the phone:
- hold vol+ and plug usb to boot into fastboot (blu led)
- fastboot flash boot boot.img (extract boot.img from an official cm 11 zip)
- fastboot reboot
- enter recovery, on boot led will be violet for 3'', during this period press vol+
- flash rom zip
- flash gapps zip
- wipe
- reboot
for update just flash rom zip from recovery
Google Apps = http://forum.xda-developers.com/showthread.php?t=2397942
F.A.Q (Frequently Asked Questions)
What is the difference between these builds and the official builds?
These are unofficial builds of SlimKat for the Xperia Z1/Honami/C6903
ROM is built using the same source code (github) like the official one but with these following additions:
Compiled using linaro arm-eabi 4.9.1 14.07 (kernel code) & sabermod arm-linux-androideabi 4.8.4 14.07 (rom code) toolchain compilers
May contain some custom cherry-picks. Always see changelog for details.
Cross-compiled using those custom toolchains results in a more smoother, faster, and battery friendly ROM
What is Toolchain?
In software, a toolchain is the set of programming tools that are used to create a product (typically another computer program or system of programs). The tools may be used in a chain, so that the output of each tool becomes the input for the next, but the term is used widely to refer to any set of linked development tools.
A simple software development toolchain consists of a compiler and linker to transform the source code into an executable program, libraries to provide interfaces to the operating system, and a debugger. A complex product such as a video game needs tools for preparing sound effects, music, textures, 3-dimensional models, and animations, and further tools for combining these resources into the finished product.
Click to expand...
Click to collapse
Source: http://en.wikipedia.org/wiki/Toolchain
What is SaberMod?
The term "SaberMod" is coming from:
SaberMod is a AOSP based ROM with some extra features added in and mostly from CyanogenMod. SaberMod started out pure AOSP when android 4.2.1 launched. Originally it was pure AOSP with a few extra features I ported over from CyanogeMod and linaro optimizations. Then I rebased everything off of rasbeanjelly because I liked many features found in rasbean. Since then I've modified a lot of the code so not much of it is rasbeanjelly based anymore. But you will still find some commonly used features found in rasbeanjelly. SaberMod is not a rasbeanjelly or CM clone, or KANG. Custom kernels are included for certain devices when available. These are personal builds we make for ourselves and originally became very popular in the nexus 7 forums. Features are very rarely added, and are built to SaberMod's team members liking. Currently there are two members of SaberMod working on this project. Myself and @jarjar124 . Please understand our time is limited and we are only two people who have lives, and do not have 25-50 members like CyanogenMod to add things. And our goal is not to add a bunch of features that bloat the system of the ROM.
Click to expand...
Click to collapse
Source: http://forum.xda-developers.com/show....php?t=2158698
What is Linaro?
Linaro is the place where engineers from the world's leading technology companies define the future of Linux on ARM. The company is a not-for-profit engineering organization with over 120 engineers working on consolidating and optimizing open source software for the ARM architecture, including the GCC toolchain, the Linux kernel, ARM power management, graphics and multimedia interfaces.
Click to expand...
Click to collapse
Source: http://www.linaro.org/linux-on-arm/
About GCC main compiler cflags
-O1
Optimize. Optimizing compilation takes somewhat more time, and a lot more memory for a large function. With -O, the compiler tries to reduce code size and execution time, without performing any optimizations that take a great deal of compilation time.
-O2
Optimize even more. GCC performs nearly all supported optimizations that do not involve a space-speed tradeoff. As compared to -O, this option increases both compilation time and the performance of the generated code. -O2 turns on all optimization flags specified by -O.
-O3
Optimize yet more. -O3 turns on all optimizations specified by -O2 and also turns on the -finline-functions, -funswitch-loops, -fpredictive-commoning, -fgcse-after-reload, -ftree-loop-vectorize, -ftree-slp-vectorize, -fvect-cost-model, -ftree-partial-pre and -fipa-cp-clone options.
-Os
Optimize for size. -Os enables all -O2 optimizations that do not typically increase code size. It also performs further optimizations designed to reduce code size.
Click to expand...
Click to collapse
OMG
SLIMKAT
GOOD WORK MAN
I wonder if this build is faster than Vanir
it's super fast u must try it :good:
charging slow as turtle
Really nice man.. Slim and Linaro makes superfast
Sent from my Xperia Z1 using Tapatalk
Works well, really smooth.
Sent from my Xperia Z1 using XDA Premium HD app
Definitely a charging problem, takes a while and only reaches 98% max.
Apart from that its everything I expected
Sent from my Xperia Z1 using XDA Premium HD app
MacSeoin said:
Definitely a charging problem, takes a while and only reaches 98% max.
Apart from that its everything I expected
Sent from my Xperia Z1 using XDA Premium HD app
Click to expand...
Click to collapse
Yep everything perfect expit the charging
Sent from my Xperia Z1 using Tapatalk
weekly 6.8 is up.
regards.
ps: lots of changes to kernel ..
Is it just me or camera is flaky (freezes and doesnt work) like older builds?
Camera not work. Freeze and flashlight automatic on and off. Also charging is slow, reach 96% and slowly to 100% (2hours). Try reflash original Slimkat and not of problems happen. So must be this............
weekly 7.0 is up.
regards.
infected_ said:
weekly 7.0 is up.
regards.
Click to expand...
Click to collapse
su binary seems to be missing, so no root!
i did a clean install with the latest pa mini gapps.
steveeJ said:
su binary seems to be missing, so no root!
i did a clean install with the latest pa mini gapps.
Click to expand...
Click to collapse
Enable root on developer options...
Sent from my Xperia Z1 using Tapatalk
I see there is a slim governor, I couldnt find anything about it... Care to shed us some light about it?
And... Do you have your sources or some kind of changelog?
Builds are hella fast though, great work man!
weekly 7.2 is up.
regards.
seems there were missing some commits on Slim code, in the weekly build...
compiling 7.2.1
edit: 7.2.1 is up.
Related
Why choose for CarbonRom?
CarbonRom is an AOSP based rom, which is always compiled with the latest linaro toolchain. The kernel also is compiled with -O3 optimizations for better performance. It also gives you a great option of customization. Reasons to go for CarbonRom are:
- Compiled with Linaro, this will make your phone ultrafast and ultrasmooth
- AOSP based, s no bloatware or other stuff
- Great Customization options
- Nice look
- HALO
- ...
Current Version
CarbonRom 2.0 is still in early stages, it's Android 4.3, but not all features are implemented!
I won't manually search for all new features, just wait for an official 2.0 changelog when it is completed.
- Android 4.3
- HALO
- DSP Manager
- New battery icons
- stability and speed enhancements
- a million other little things as well - we basically don't even sleep anymore.
What is CarbonRom?
CarbonRom is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look at, build, and use our code on CarbonDev GitHub.
We would like to thank CyanogenMod for their device trees, framework/settings mods and their code that was incorporated into this project. We also extend our gratitude to the devs whose code that we have incorporated. Proper authorship has been maintained and can be viewed on our repository.
Special thanks also go to Slim Rom for some of their features, PA, AOKP, @FXP, and anyone else we may have borrowed commits from that hasn't been mentioned here. If you feel you have been unfairly left out, please - let us know.
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.
Screenshots
Download Carbon
All Carbon downloads and further information such as features, changelog, and FAQ can be found here in the second post of this thread and in the download tab.
I'll continue building nightlies as much as possible.
Support
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our goo.im page linked above. It's new, but expanding fast. Just like us!
3) Ask a question here. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
Who is the Carbon maintainer for your device?
For you guys, Xperia developer is me only, Krabappel2548. I'm the only one working for Xperia devices, maybe I'll add more devices to my support list soon. Any donations are highly appreciated, I'll always use them for my development, to buy new devices
Who are the Team Carbon members?
andros11
BigShotRob
dg4prez
Kejar31
mattmanwrx
morfic
nocoast
pixeldotz
slick_rick
winner00
Thanks to your help we now have the machines we need for nightlies. We couldn't have done it without you! Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
XDA:DevDB Information
[ROM][AOSP][UNOFFICIAL]CarbonRom 2.0 bèta[4.3.1][honami][Oct 31], a ROM for the Sony Xperia Z1
Contributors
krabappel2548
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked bootloader
Based On: AOSP, CyanogenMod
Version Information
Status: Testing
Beta Release Date: 2013-10-03
Created 2013-09-27
Last Updated 2013-10-31
Reserved
Downloads Android 4.3
Rom: CarbonRom Android 4.3 Bèta download
C6902 patch: C6902 patch for carbon thx to @MightyBear007
Gapps: Android 4.3 gapps
Installation instructions
Clean install
- Wipe data, cache dalvik cache
- Install CarbonRom
- Install gapps!
- Reboot device & enjoy!
Update:
- Wipe cache, dalvik cache
- Install CarbonRom
- Reflash gapps
- Reboot device & enjoy!
Working
- Everything that's not in the "bugs list"
BUGS?
- Camera is Berry buggy
- Maybe more, let me know
To Do List
- Readd all tweaks in the kernel
- Compile with linaro and -O3
- Maybe even more CPU Governors
- Maybe even more I/O Schedulars
- tell me!
Xperia Z1 changelog
The newer changelog can be found here: Carbon Rom
Code:
[QUOTE][B]== 11/10 Nightly ==[/B]
Updated the kernel:
- Small changes
Updated the rom:
- Android 4.3.1
- PA PIE
- Latest Carbon, CM etc changes[/QUOTE]
[B]== 06/10 Nightly ==[/B]
Updated the kernel:
- Update to Sony 15.1.G.1.534 sources
- Added MPdecision
- Added BFQ I/O schedular
- Added Badass and Lionheart CPU governors
- Adder GPU OC possibilities to 600MHz
- Booting up at 2.1GHz (stock speed)
- Add OC upto 2,342 GHz
- Added some more CPU frequencies in between to sav battery: Test!
- Initial ZUltra release
- Latest CM changed
Updated the rom:
- Initial ZUltra release
- Latest Carbon changes
[B]== 03/10 Nightly ==[/B]
Updated the kernel:
- Fixes for various stuff
- Added VDD
- Added Sound control
- Adder GPU OC and enabled it
- Add OC possibilities
- Add some more optimizations
- Latest CM changed
Updated the rom:
-[B][COLOR="Blue"] Camera is now working[/COLOR][/B]
- Working Audio and video
- A lot of improvements and fixes for Z1
- Latest Carbon changes
[B]== 27/09 Nightly ==[/B]
Updated the kernel:
- Initial Z1 release
Updated the rom:
- Initial Z1 release
== Kernel FAQ - GPU OC - Voltage Control - Sound Control==
GPU OC
OVERCLOCKING GPU WILL REDUCE BATTERY LIFE!
you can overclock/underclock GPU manually via scripts/commands...
[ how to do this manually/script ]
To check current max clock of GPU clock use:
Code:
cat /sys/devices/fdb00000.qcom,kgsl-3d0/kgsl/kgsl-3d0/max_gpuclk
To set GPU to particular frequency (overclock or underclock) use:
Code:
echo 533333000 > /sys/devices/fdb00000.qcom,kgsl-3d0/kgsl/kgsl-3d0/max_gpuclk
available scaling frequencies are:
Code:
[LIST]
[*]600000000 - 600 MHz
[*]533333000 - 533 MHz
[*]450000000 - 450 MHz (DEFAULT)
[*]320000000 - 320 MHz
[*]200000000 - 200 MHz
[/LIST]
Voltage Control
All credits for this interface go to Faux123!
WARNING!
DO NOT USE TOO HIGH OR TOO LOW VOLTAGES, SLOWLY increase the voltage one notch at a time for a particular frequency and do stability/testing for few hours. once you have verified that you CPU chip can handle that voltage ONLY then "Set at boot"/Use init.d script
You can either use an APP (like IncrediControl) [others mentioned in OP] or use an init.d script to do the work...
to see current voltage table use:
Code:
[B]cat /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels[/B]
to set voltage for a particular frequency:
Code:
[B]echo 1512000 1150000 > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels[/B]
will set 1512Mhz freq voltage at 1150mV
to reduce voltages for ALL frequencies:
Code:
[B]echo -25000 > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels[/B]
to increase voltages for ALL frequencies:
Code:
[B]echo +25000 > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels[/B]
Sound Control
Kernel level Sound Control
This feature has been added by faux123 himself!
The sources for this feature are covered under GPL and are released along with my kernel sources at my GITHUB repo.
[ WARNING ]
high volume can damage hearing!
Krabappel2548, DooMLoRD or faux123 are not to be held responsible if this damages ur headphones/speakers/etc
USE THIS AT YOUR OWN RISK!
There are two ways to use this interface.
manual control through sysfs interface
paid app (FauxSound Audio/Sound Control)
How to use the app FauxSound Audio/Sound Control is pretty self explanatory so I will write on how to control using the sysfs interface...
BEFORE DOING ANY ADJUSTMENTS EXIT THE APPS LIKE MUSIC PLAYER/etc!!
The interface to control the sound output is located at:
Code:
[B]/sys/kernel/sound_control_3[/B]
it has 4 control interfaces:
Camera MIC
Code:
/sys/kernel/sound_control_3/gpl_cam_mic_gain
Headphone
Code:
/sys/kernel/sound_control_3/gpl_headphone_gain
MIC
Code:
/sys/kernel/sound_control_3/gpl_mic_gain
Internal Speaker
Code:
/sys/kernel/sound_control_3/gpl_speaker_gain
each supports gain levels from 20 (-20) to 50 (+10), base is 40 (0)
(the number in the brackets correspond to the numbers displayed in the app)
say if u want to boost headphone output (both left and right channels) then use the following command:
Code:
echo "44 44" > /sys/kernel/sound_control_3/gpl_headphone_gain
u can also individually increase/decrease the gain for each right and left channel
similarly other interfaces can be controlled
TIP:
do not jump to maximum values as sometimes the headphones/speakers might start distorting the audio... slowly increase and do testing for the levels which suit you!
not all accessories will work well with boosted audio output
All of this wouldn't be possible without @Kali- and @Bin4ry helping with stuff and setting up device tree etc
Also big thx to @DooMLoRD for some of his kernel commits to tweak the CM kernel
Download links added, here is proof it runs:
{
"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"
}
Very good! This is one of first build for snapdragom 800.
Sent from my GT-I9500 using xda app-developers app
krabappel2548 said:
BUGS?
- Camera doesn't work due to unlocking bug
- Audio and Video Playback
- Maybe more, let me know
Click to expand...
Click to collapse
u have camera preview?
Kali- said:
u have camera preview?
Click to expand...
Click to collapse
It says: Camera not available
I'm back on stock now I need music in the bus
But I'll see what I can do for audio and video playback when I'm home
Sent from my C6903 using xda app-developers app
krabappel2548 said:
It says: Camera not available
I'm back on stock now I need music in the bus
But I'll see what I can do for audio and video playback when I'm home
Click to expand...
Click to collapse
well, the problem is not the unlock bug
Kali- said:
well, the problem is not the unlock bug
Click to expand...
Click to collapse
@Kali- Oh ok the hardware/qcom/camera then?
Anyway this was first build will check car for video and audio I'll also check for camera
Sent from my C6903 using xda app-developers app
krabappel2548 said:
@Kali- Oh ok the hardware/qcom/camera then?
Anyway this was first build will check car for video and audio I'll also check for camera
Click to expand...
Click to collapse
i have all working except camera, which fails to initialize (that's why i asked for it)
didnt got time to investigate about this issue :/ but is not related to unlock issue
Kali- said:
i have all working except camera, which fails to initialize (that's why i asked for it)
didnt got time to investigate about this issue :/ but is not related to unlock issue
Click to expand...
Click to collapse
Oh ok, nice, I'll wait for changes to be merged in CM github then and I'll look into camera right now then
Sent from my C6903 using xda app-developers app
krabappel2548 said:
Oh ok, nice, I'll look into camera right now then
Click to expand...
Click to collapse
i'm working to merge the new qcom audio/display/media but they are much different from the -caf used on CM (probably ill end to add another variant)
Kali- said:
i'm working to merge the new qcom audio/display/media but they are much different from the -caf used on CM (probably ill end to add another variant)
Click to expand...
Click to collapse
ok, no problem like this it's becoming a dev talk over here lol I'll come immidiately to irc next time
krabappel2548 said:
ok, no problem like this it's becoming a dev talk over here lol I'll come immidiately to irc next time
Click to expand...
Click to collapse
OMG!!!!!!!!!!!!!!!!!!1111
Dev talk in a dev forums! Is it possible?
Good to see all great developers didnt see any post by bin4ry rest all are here i guess..
This is GREAT!. Thanks man. Buying this phone tommorow. Will wait for new bootloader unlock with working camera and then directly flash your awesomeness.
Update coming up! Who is actually interested in this rom? Seems everyone is just running to CM since it's more known
Sent from my C6903 using xda app-developers app
krabappel2548 said:
Update coming up! Who is actually interested in this rom? Seems everyone is just running to CM since it's more known
Sent from my C6903 using xda app-developers app
Click to expand...
Click to collapse
All are interested i guess.Choice is good for all..
krabappel2548 said:
Update coming up! Who is actually interested in this rom? Seems everyone is just running to CM since it's more known
Sent from my C6903 using xda app-developers app
Click to expand...
Click to collapse
Im interested, its looking great so far. Hopefully once the camera issue is sorted a lot more people will be ready to jump to custom ROMs (myself included)
AdamCompedia said:
Im interested, its looking great so far. Hopefully once the camera issue is sorted a lot more people will be ready to jump to custom ROMs (myself included)
Click to expand...
Click to collapse
Yeah, I'm compiling new update right now will test myself and release tomorrow
EDIT: Camera works on my build I'll release tomorrow
== 02/10 Nightly ==
Updated the kernel:
- Fixes for various stuff
- Initial ZUltra release
Updated the rom:
- Camera is now working
- A lot of improvements and fixes for Z1
- Initial ZUltra release
Click to expand...
Click to collapse
Based on discussion on Semaphore Kernel thread, I'm glad that finally compiling using Linaro GCC 4.8 is possible now I've test this several months a go and still not boot until got some new idea arise in that discussion
Maybe this not a daily driver kernel, just feel free to try once and go back to other kernel :highfive:
Different from stock (changelogs):
build 20140324 for 20140323-NIGHTLY and newer
- Update iniram from 20140323-NIGHTLY
build 20140308 for 20140307-NIGHTLY and newer but not SNAPSHOT-M4
- Merge stock cm-11 & use initram 0307 nightly
build 20140214
- Revert s3cfb: tl2796: do not read calibration data on aries and use s3cfb: tl2796: detect invalid factory calibration data as on stock cm-11
build 20140211
- Add s3cfb: tl2796: do not read calibration data on aries from stock cm-11
- Use newer linaro toolchhain 14.01
- Update recovery to Mackay TWRP 2.6.3.0
build 20140111
- Update ramdisk to Tweak KSM Value
- Merge upstream CM-11
- Use newer linaro toolchhain 13.12
build 20140106
- Update ramdisk with Kitkat zRAM setting
- Fix lpm (charging when phone off)
- Cherry-picked optimize JPEG memory configuration & add ioctl to export memory configuration
- Only build with Mackay TWRP
build 20131231
- Fix outdated init file causing boot problem
build 20131221
- Ramdisk from cm-11-20131219-NIGHTLY-galaxysmtd
build 20131212/16
- Ramdisk from cm-11-20131206-NIGHTLY-galaxysmtd, unpacked using this tools.
- Compiled with linaro-toolchain-binaries 4.8 (32bit)
- Use Mackay TWRP 2.6.0.0 (-mtwrp) or Semaphore CWM 6.0.4.5 (-smcwm)
Additional changes in x-aries version:
Note: Video capture & playback (cma problem with or without ksm) mostly working.
In rare condition it need long time to start (5 minutes or more).
You can wait it if you have time (recommended) or simply restart your phone.
build 20140401
Compiled on this HEAD
- Update iniram from 20140331-NIGHTLY
- Enable KSM_CHECK_PAGE
- Enable Advanced TCP Congestion Control
build 20140324 for 20140323-NIGHTLY and newer
- Update iniram from 20140323-NIGHTLY
build 20140319 for 20140307-NIGHTLY and newer but not SNAPSHOT-M4
Compiled on this HEAD
- Add 2 patches to improve swap & revert aries-common: zRAM: only read one page at a time.
This time I prefer this kernel doc:
Code:
It is a logarithmic value - setting it to zero means "1 page", setting
it to 1 means "2 pages", setting it to 2 means "4 pages", etc.
Zero disables swap readahead completely.
The default value is three (eight pages at a time). There may be some
small benefits in tuning this to a different value if your workload is
swap-intensive.
Lower values mean lower latencies for initial faults, but at the same time
extra faults and I/O delays for following faults if they would have been part of
that consecutive pages readahead would have brought in.
over aosp guide:
Code:
By default, the Linux kernel swaps in 8 pages of memory at a time.
When using ZRAM, the incremental cost of reading 1 page at a time is negligible and may help in case the device is under extreme memory pressure.
To read only 1 page at a time, add the following to your init.rc:
`write /proc/sys/vm/page-cluster 0`
build 20140313 for 20140307-NIGHTLY and newer but not SNAPSHOT-M4
Builded at this HEAD
- Switch cflag from -Og (reverted to -O2 then) to -O3, the kernel size was much bigger & reduce user RAM to 416MB
- Use newer linaro toolchhain 14.02
- Add aries-common: zRAM: only read one page at a time
imo default linux value will give better performance, but I prefer to follow aosp guide like in stock cm.
build 20140311 for 20140307-NIGHTLY and newer but not SNAPSHOT-M4
- Add 1100 oc step from mackay and 2 other commits.
build 20140308 for 20140307-NIGHTLY and newer but not SNAPSHOT-M4
- Use initram 0307 nightly with 144 mb zram + minor change to cma & merge android-3.0 aosp
build 20140306
- Add 2 commits to improve swap/zram + ramdisk 0228 nightly with 256 mb zram size (not stable)
build 20140226
- Add 2 commits related to video for linux + merge stock cm-11 & android-3.0 aosp
build 20140214
- Same as aries version + some commits related to memory
build 20140212
- Add s3cfb: tl2796: do not read calibration data on aries from stock cm-11
- Add backport SLUB from Linux 3.3 from Hellybean GT-I9300 + another 4 commits.
build 20140209
- Merge android-3.0 kernel common.
- Enable CLEANCACHE, FRONTSWAP & ZCACHE
- Another CMA try.
build 20140207
- Add BLN & Fast Charge from Semaphore kernel.
Note for BLN: Need to manually rename lights.aries.so.bln in /system/lib/hw/ to lights.aries.so
Rename original file to lights.aries.so.cm or else for backup. Repeat this step in every rom flashing.
- Use newer linaro toolchhain 14.01
- Merge android-3.0 kernel common.
build 20140131
A bunch of patches from faux123, semaphore, codeaurora & linux-next, starting from here till this.
Some part maybe useless and here is the noticeable part:
- Update LMK, CMA and KSM.
- Use LZ4 compressor for zram.
- Add Semaphore Auto Brightness from stratosk (build as a module)
build 20140121
- Add ZRAM_FOR_ANDROID from faux123
- Remove KSM to prevent video recording failure
- Use LZ4 for initram
- Update recovery to Mackay TWRP 2.6.3.0
- Some cherry-pick related to CMA, low memory killer & binder
build 20140111
- Same as aries version exclude merge upstream (already added)
- Replace xvmalloc with zsmalloc for zram
build 20140106
- Same as aries version
build 20140105
- Add pawitp cma-test with 417mb memory (no need bigmem libs) and possible bugs.
- Fix lpm (charging when phone off)
build 20131231
- different boot logo
- add smartass2 cpu gov
build 20131221/22
- 1.32ghz OC step and revert sleep call gpio to prevent SOD
- 397mb memory (install bigmem lib by kasper_h separately for 720k video record fix)
- kernel config for smaller kernel size (mostly taken from semaphore kernel by stratosk)
- merged to aosp android-3.0 kernel common (big changes in wifi driver and interactive gov)
- update gpu driver to DDK [email protected] (as on mackay kernel and others)
- cherry-picked some commits related to zram, lzo and interactive gov
- display boot progress, etc..
Download
http://goo.im/devs/didhiy/aries_cm-11.0
http://goo.im/devs/didhiy/ariesbr_cm-11.0 (I9000B)
tips: check (sort by) modification time to find the latest build
Source:
Kernel
x-aries version
Ramdisk
Credits:
- pawitp
- stratosk
- kasper_h
- derteufel1980
- jugster
- alberto96
- unjustified dev
- all aries variant devs and community
Nice work. I have been looking at the sets of patches needed for Linaro 4.8, but didnt try building one yet.
Last I tried 4.8 was almost 3 months ago, and it didnt boot up, although it build fine.
Would you be willing to add the extra OC steps ( 1100 , 1300 and 1400 ) into the kernel ?
ts1506 said:
Nice work. I have been looking at the sets of patches needed for Linaro 4.8, but didnt try building one yet.
Last I tried 4.8 was almost 3 months ago, and it didnt boot up, although it build fine.
Would you be willing to add the extra OC steps ( 1100 , 1300 and 1400 ) into the kernel ?
Click to expand...
Click to collapse
maybe... right now, I just let it same as stock to see if there's any improvement
just flashed over mackay 4.1.3 and i get better score on antutu, 4985.
keep up good work.
florum said:
just flashed over mackay 4.1.3 and i get better score on antutu, 4985.
keep up good work.
Click to expand...
Click to collapse
thanks for testing & comparing, I think mackay compiled with linaro 4.8 will scored much better
didhiy said:
thanks for testing & comparing, I think mackay compiled with linaro 4.8 will scored much better
Click to expand...
Click to collapse
Wow!! That's amazing. See my score. I never managed to go beyond 4930 in the past.
Can you please describe me what is linaro 4.8 and how does it increase performance.
I flashed bigmem libs for KitKat by Kaspar_h but still got 368 MB of available RAM. Maybe it's my fault, but still curious to know if bigmem libs works on this kernel.
Thanks in advance
Sent from my GT-I9000 using XDA Premium 4 mobile app
Rohitdahiya said:
Wow!! That's amazing. See my score. I never managed to go beyond 4930 in the past.
Can you please describe me what is linaro 4.8 and how does it increase performance.
I flashed bigmem libs for KitKat by Kaspar_h but still got 368 MB of available RAM. Maybe it's my fault, but still curious to know if bigmem libs works on this kernel.
Thanks in advance
Sent from my GT-I9000 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
you can read the technical details here:
http://gcc.gnu.org/gcc-4.8/changes.html
in short words, it promising better optimization to the codes compiled with it
the memory size was set inside the kernel, installing bigmem libs won't change the size
This kernel is a beast,thank you very much didhiy!
@Rohitdahiya:
You should enable a bigmem setting to make the available amount of RAM bigger.
Flashing only the libs doesn't change the current configuration
Inviato dal mio GT-I9000 utilizzando Tapatalk
thank you for the wonderful kernel please make an option to enable bigmem or atleast 396mb as in case of mackay kernel... thank you
vigneshnallamad said:
thank you for the wonderful kernel please make an option to enable bigmem or atleast 396mb as in case of mackay kernel... thank you
Click to expand...
Click to collapse
I've upload a version with "x-" prefix, bigmem enable (397mb) + 1.32GHz oc steps and some configs changes to make a small kernel (mostly taken from semaphore kernel)
let me know if that version works too
download link was on op
Does this kernel have zram as it's based on stock?
Sent from my GT-I9000 using Tapatalk 4
zakitheracer said:
Does this kernel have zram as it's based on stock?
Sent from my GT-I9000 using Tapatalk 4
Click to expand...
Click to collapse
yes it have zram just like stok
didhiy said:
I've upload a version with "x-" prefix, bigmem enable (397mb) + 1.32GHz oc steps and some configs changes to make a small kernel (mostly taken from semaphore kernel)
let me know if that version works too
download link was on op
Click to expand...
Click to collapse
wow i got 5200 on antutu if u believe in benchmarks... but performance overall is wonderful...
edit : any plans of including smartass v2 and wheatly just a request as of now this is my daily kernel
edit 2 : see the score my phone is ready for android 5.0 with help of u devs
vigneshnallamad said:
wow i got 5200 on antutu if u believe in benchmarks... but performance overall is wonderful...
edit : any plans of including smartass v2 and wheatly just a request as of now this is my daily kernel
edit 2 : see the score my phone is ready for android 5.0 with help of u devs
Click to expand...
Click to collapse
temple run 2 is my only "benchmark" thanks for your nice report
Hope it's stable enough for daily driver too
I use same kernel configuration in sc-02b aries_ntt and epic4g, it's running fine for daily
Guys,
This kernel gives you to put in Mackay Rom 4.1.3 (kk 4.4)?
Thank you for your answers already.
Alexandre_Silva said:
Guys,
This kernel gives you to put in Mackay Rom 4.1.3 (kk 4.4)?
Thank you for your answers already.
Click to expand...
Click to collapse
I don't understand exactly what you mean, but I guess you can flash this kernel on top of mackay cm-11 rom and maybe mackay omni too (tested on my sc-02b only) with caution, mackay setting won't work!
didhiy said:
I don't understand exactly what you mean, but I guess you can flash this kernel on top of mackay cm-11 rom and maybe mackay omni too (tested on my sc-02b only) with caution, mackay setting won't work!
Click to expand...
Click to collapse
in mackay omni rom description kasper h has mentioned about other kernels rom not working... didnt try it yet... will test and report back if works
vigneshnallamad said:
in mackay omni rom description kasper h has mentioned about other kernels rom not working... didnt try it yet... will test and report back if works
Click to expand...
Click to collapse
I've download omni mackay 1217, after comparing initram between omni & stock cm-11 I've found no different except the binaries. Then I flashed that rom & my kernel (which have 1219 cm-11) & it boot fine.
make sure you have a backup & semaphore tar if you wanna try
didhiy said:
I've download omni mackay 1217, after comparing initram between omni & stock cm-11 I've found no different except the binaries. Then I flashed that rom & my kernel (which have 1219 cm-11) & it boot fine.
make sure you have a backup & semaphore tar if you wanna try
Click to expand...
Click to collapse
That's great will give it a try tomo of possible please include smartass v2 in our next version
vigneshnallamad said:
That's great will give it a try tomo of possible please include smartass v2 in our next version
Click to expand...
Click to collapse
no promise, but it's possible
XPERIA Z1/HONAMI/C6903 PARANOID ANDROID 4.5 LINARO/SABERMOD WEEKLY BUILDS
4.5 BETA 2 is ONLINE
Build/Sync Date: Ago 13 xxh:xx GMT+1 Lisbon
DOWNLOAD
(infected server)
(md5sum included with all builds)
CHANGELOG
http://forum.xda-developers.com/showthread.php?p=54620455
HOMEPAGE
http://infectedbuilds.net
kernel code compiled with linaro arm-eabi-4.9.1 201407 toolchain
rom code compiled with with sabermod arm-linux-androideabi-4.8.4 201407 toolchain
FEATURES
-O3 optimizations (ROM and kernel code)
strict-aliasing rules
custom performance flags (ROM and kernel code)
+30 cherry-picks used
graphite
(buildbot: intel core i7 [email protected], asus p8z77-v, 8gb corsair vengeance pro 2133mhz cl9, sapphire hd7970 dual-x, 2x samsung 128gb ssd 840 pro raid 0 array,
4x western wigital wd3200aaks raid 10 array, samsung f1 1tb, silverstone olympia 1000w psu, antec 1200 high-tower)
(wc setup: swiftech apogee xt cpu-block, black-ice gtx-lite 240 radiator, 2x noiseblocker eloop b12-3 1900rpm fans, swiftech mcp355 water-pump, danger den 5.25" reservoir bay)
(Linux Mint 17 x64 "Qiana" 3.13.0-24)
DONATIONS NEEDED
Disclaimer:
These builds are freshly compiled/synced from AOSPA Legacy open-source code:
https://github.com/AOSPA-legacy
latest linaro arm-eabi-4.9.1 toolchain used to compile the kernel code & sabermod arm-linux-androideabi-4.8.4 toolchain to compile ROM code
Special Thanks
AOSPA Legacy Dev Team
{
"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"
}
XDA:DevDB Information
Z1/HONAMI/C6903 Linaro/Sabermod Paranoid Android Legacy (AOSPAL) 4.4x Builds, ROM for the Sony Xperia Z1
Contributors
infected_
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Latest CWM Recovery or TWRP recovery
Based On: AOSPAL
Version Information
Status: Stable
Current Stable Version: 4.44
Stable Release Date: 2014-07-24
Created 2014-07-24
Last Updated 2014-08-13
Install instructions:
first time
- power off the phone:
- hold vol+ and plug usb to boot into fastboot (blue led)
- fastboot flash boot boot.img (extract boot.img from an official AOSPAL honami build zip or these builds)
- fastboot reboot
- enter recovery, on boot led will be violet for 3'', during this period press vol+
- flash rom zip
- flash gapps zip
- wipe
- reboot
for update just flash rom zip from recovery
Google Apps = http://forum.xda-developers.com/showthread.php?t=2397942
F.A.Q (Frequently Asked Questions)
What is the difference between these builds and the official builds?
These are unofficial builds of AOSPA Legacy for the Xperia Z1/Honami/C6903
ROM is built using the same source code (github) like the official one but with these following additions:
Compiled using linaro arm-eabi 4.9.1 14.07 (kernel code) & sabermod arm-linux-androideabi 4.8.4 14.07 (rom code) toolchain compilers
May contain some custom cherry-picks. Always see changelog for details.
Cross-compiled using those custom toolchains results in a more smoother, faster, and battery friendly ROM
What is Toolchain?
In software, a toolchain is the set of programming tools that are used to create a product (typically another computer program or system of programs). The tools may be used in a chain, so that the output of each tool becomes the input for the next, but the term is used widely to refer to any set of linked development tools.
A simple software development toolchain consists of a compiler and linker to transform the source code into an executable program, libraries to provide interfaces to the operating system, and a debugger. A complex product such as a video game needs tools for preparing sound effects, music, textures, 3-dimensional models, and animations, and further tools for combining these resources into the finished product.
Click to expand...
Click to collapse
Source: http://en.wikipedia.org/wiki/Toolchain
What is SaberMod?
The term "SaberMod" is coming from:
SaberMod is a AOSP based ROM with some extra features added in and mostly from CyanogenMod. SaberMod started out pure AOSP when android 4.2.1 launched. Originally it was pure AOSP with a few extra features I ported over from CyanogeMod and linaro optimizations. Then I rebased everything off of rasbeanjelly because I liked many features found in rasbean. Since then I've modified a lot of the code so not much of it is rasbeanjelly based anymore. But you will still find some commonly used features found in rasbeanjelly. SaberMod is not a rasbeanjelly or CM clone, or KANG. Custom kernels are included for certain devices when available. These are personal builds we make for ourselves and originally became very popular in the nexus 7 forums. Features are very rarely added, and are built to SaberMod's team members liking. Currently there are two members of SaberMod working on this project. Myself and @jarjar124 . Please understand our time is limited and we are only two people who have lives, and do not have 25-50 members like CyanogenMod to add things. And our goal is not to add a bunch of features that bloat the system of the ROM.
Click to expand...
Click to collapse
Source: http://forum.xda-developers.com/show....php?t=2158698
What is Linaro?
Linaro is the place where engineers from the world's leading technology companies define the future of Linux on ARM. The company is a not-for-profit engineering organization with over 120 engineers working on consolidating and optimizing open source software for the ARM architecture, including the GCC toolchain, the Linux kernel, ARM power management, graphics and multimedia interfaces.
Click to expand...
Click to collapse
Source: http://www.linaro.org/linux-on-arm/
About GCC main compiler cflags
-O1
Optimize. Optimizing compilation takes somewhat more time, and a lot more memory for a large function. With -O, the compiler tries to reduce code size and execution time, without performing any optimizations that take a great deal of compilation time.
-O2
Optimize even more. GCC performs nearly all supported optimizations that do not involve a space-speed tradeoff. As compared to -O, this option increases both compilation time and the performance of the generated code. -O2 turns on all optimization flags specified by -O.
-O3
Optimize yet more. -O3 turns on all optimizations specified by -O2 and also turns on the -finline-functions, -funswitch-loops, -fpredictive-commoning, -fgcse-after-reload, -ftree-loop-vectorize, -ftree-slp-vectorize, -fvect-cost-model, -ftree-partial-pre and -fipa-cp-clone options.
-Os
Optimize for size. -Os enables all -O2 optimizations that do not typically increase code size. It also performs further optimizations designed to reduce code size.
Click to expand...
Click to collapse
first
wow new rom i must try it
---------- Post added at 03:45 PM ---------- Previous post was at 03:15 PM ----------
install finito
start with Rom now i write feedback later
Thx , but is there anything different from the old AOSPAL we have here ?
iiD4x said:
Thx , but is there anything different from the old AOSPAL we have here ?
Click to expand...
Click to collapse
yes. these builds are cross-compiled with custom toolchains, instead of google gcc 4.6 & 4.7 "stock" ones... the gcc toolchains that can be used are linaro, sabermod, and boosted... compiling using latest gcc versions 4.8/4.9, using -O3 optimizations, strict-aliasing, and other performance/optimization flags, results in the advantages described on the third OP.. smoother, faster, and more battery friendly builds...
try it, and them give feedback...
any doubt, feel free to ask.
regards.
infected_ said:
yes. these builds are cross-compiled with custom toolchains, instead of google gcc 4.6 & 4.7 "stock" ones... the gcc toolchains that can be used are linaro, sabermod, and boosted... compiling using latest gcc versions 4.8/4.9, using -O3 optimizations, strict-aliasing, and other performance/optimization flags, results in the advantages described on the third OP.. smoother, faster, and more battery friendly builds...
try it, and them give feedback...
any doubt, feel free to ask.
regards.
Click to expand...
Click to collapse
Lol, Official AOSPAL we have here using latest SaberMod toolchain also..
OPTIMIZATION:
Offical SaberMod toolchain (GCC 4.8 for ROM , 4.9 for Kernel)
Strict-aliasing enabled
Memory optimization flags
Graphite
Click to expand...
Click to collapse
i dont mean anything, but we already have it OFFICIAL for honami.
iiD4x said:
Lol, Official AOSPAL we have here using latest SaberMod toolchain also..
i dont mean anything, but we already have it OFFICIAL for honami.
Click to expand...
Click to collapse
you must be mixing things up... Paranoid Android (AOSPA) uses google toolchains.. just check manifests.
Paranoid Android Legacy (AOSPAL) also uses google toolchains... check manifests.
Paranoid Saberdroid (AOSPAL also), i dont give a dime what they use...
i told to try ROM first...
regards.
Been waiting for this Thread.. Superlike
Sent from my Xperia Z1 using Tapatalk
Is there any disadvantage of this over the official one?
Blegh said:
Is there any disadvantage of this over the official one?
Click to expand...
Click to collapse
This will be faster
Blegh said:
Is there any disadvantage of this over the official one?
Click to expand...
Click to collapse
quite the opposite.. run for half a day with stock PA, then run the other half of the day with a PA linaro/sabermod build.
you can flash each on top of another and vice-versa.
You'll see the differences..
When I've flashed the boot.img from CM11 and try to access my sdcard from recovery I get the following error:
E: Can't mount /storage/sdcard1
Any idea on how to solve this?
Thanks
siwan05 said:
when i've flashed the boot.img from cm11 and try to access my sdcard from recovery i get the following error:
E: Can't mount /storage/sdcard1
any idea on how to solve this?
Thanks
Click to expand...
Click to collapse
Try flashing the boot.img from this rom zip
abbychauhan said:
Try flashing the boot.img from this rom zip
Click to expand...
Click to collapse
yeah.. i need to change 2nd post instructions according to AOSPAL..
You might want to change the tag to AOSPA as AOSPAL is the name for Paranoid SaberDroid. It is kinda misleading IMO.
There's new build 26 July
Sent from my Xperia Z1 using Tapatalk
if @infected_ would be kind enough to give changelogs then it would be batter
Though new build working Superb
7sen said:
There's new build 26 July
Sent from my Xperia Z1 using Tapatalk
Click to expand...
Click to collapse
abbychauhan said:
if @infected_ would be kind enough to give changelogs then it would be batter
Though new build working Superb
Click to expand...
Click to collapse
there isn’t any.. its same 4.44 build, but i only added extra cpu governors and i/o schedulers... sure there were things merged, you can check gerrit ..
its an untested build. don’t have time to do it atm...
infected_ said:
there isn’t any.. its same 4.44 build, but i only added extra cpu governors and i/o schedulers... sure there were things merged, you can check gerrit ..
its an untested build. don’t have time to do it atm...
Click to expand...
Click to collapse
it's perfect build i installed with fresh install :good: and now it's good with all cpu governors :angel:
UNOFFICIAL CyanogenMod 12.1 for the Samsung Galaxy Nexus
Introduction
I first decided to put together this Lollipop ROM using the old graphics drivers for those of us who wished to try Lollipop, but needed full camera functionality (i.e. barcode scanner apps, or any other app that uses the camera API). At this point, it looks as if the camera has been fixed to work with the newer GPU drivers. I will continue to develop this ROM using the older drivers until all of the major kinks are worked out (both DDK and non-graphics related included) and we have a 100 percent stable release. You are welcome to try my build which does offer some unique features and will continue to be improved upon and synchronized with the CyanogenMod sources.
Please note that you can NOT use any other kernels with this ROM!! I have added a number of additional features to the kernel including custom voltage, fast charge, and color adjustment so hopefully that will satisfy enough for the time being.
I welcome any and all feedback, including bug reports and feature requests. The Galaxy Nexus is my main phone, and this ROM has been stable enough to be my daily driver since I began developing it several weeks ago.
Additional Features Specific to this ROM
F2FS support for /data and /cache. System must be ext4.
LegacyCamera app included (more stable and lots of features)
Lower screen brightness during boot sequence (/etc/init.d/96screendim)
Adjusted minfrees for better multitasking
Xposed for Lollipop compatible*
Specify maximum number of recent apps (ro.config.max_recents)
AppOps control for platform signed apps (ro.appops.show_platform)
Ability to turn off the display during the boot sequence
Support for UnifiedNlp
Volume keys can wake/boot phone from offline charger mode
Additional AppOps (read phone info/other accounts)
Less frequent notifications
Emergency Battery feature
More QS Tiles: Reboot/Recovery, Screenshot, Screen Off
Setting to disable Media Scanner on boot
Volume keys can wake/boot phone from offline charger mode
Expanded Notification Panel width in Landscape Orientation
Disable USER apps from the Applications Manager
Whitelist apps to prevent them from being killed
Recents Privacy: hide app content from appearing in recents cards*
Cell/Wifi scan AppOp
Wakelock Blocker
NEW: Alarm Blocker
NEW: Marshmallow bootanimation
CyanogenMod Features
Better AppOps, including the ability to block wakelocks and alarms.
Status bar mods (brightness control, weather, battery icon style, double-tap to sleep)
Navigation bar customizations
Button mods (volume wake, volume cursor)
Color/Gamma calibration
Battery light enable/disable
CyanogenMod DSP
Scramble for PIN layout on lockscreen
Advanced reboot menu
Charging LED ON/OFF
Theme Manager
Additional Quick Settings tiles (ADB over network, compass, profiles, NFC, hotspot, AudioFX, screen timeout)
More pattern lock sizes (3x3, 4x4, 5x5, 6x6)
and more!!!
Kernel Features
CPU frequency slots: 230-1632Mhz
CPU governors: dyninteractive, interactive, conservative, ondemand, ondemandplus, userspace, powersave, performance, ktoonservative, zzmoove
Min Screen On / Max Screen Off
I/O scheduler: row, zen, noop, deadline, cfq, sioplus
TCP congestion control: cubic, reno, bic, westwood, htcp
Fast Charge (with data transfer)
GPU Overclock (max 512MHz)
IVA Overclock
SmartReflex: Core, IVA, MPU
SmartReflex: Min calibrated voltages
Custom Voltages
Custom Regulator Voltages: VAUX3_6030, VAUX1_6030, VMMC, VANA, V2V1, VDAC, VCXIO, VUSIM, VMMC, VUSB
Color Settings (gamma offset, color multipliers)
I/O Accounting (see this post for more information).
Vibrator Intensity
Headphone Volume Boost
lowmemorykiller whitelist
Emergency Battery Reserve (see this post for details)
GPU governors (on3demand, activeidle, onoff, userspace)
Instructions
First flash:
Unlock & install a recovery
Wipe data & cache partitions
Flash CM-12.1
Install the Google Apps package
Reboot
Upgrade:
Make a backup in recovery
Flash CM-12.1
Install the Google Apps package
Reboot
If you are using F2FS, boot will hang for a bit longer on the Google Logo before animation starts.
Initial boot will take longer than it does with other 5.1 ROMS because this ROM is deodexed. My main reason for doing it this way is so that I can make modifications to individual framework files without having to flash the entire /system partition. The downside is that the initial boot after a wipe of the dalvik-cache will take marginally longer because it has to rebuild the caches for all of the system apps. If you do this while you still have a full compliment of user apps installed - i.e. after an upgrade, the boot sequence could take a REALLY long time - so be prepared for that. Personally, I feel that this is a small enough inconvenience and the benefits outweigh the drawbacks.
Downloads
Latest Build
cm-12.1-20151223-UNOFFICIAL-maguro.zip
Changelog: 12/23/2015
Google Apps
http://wiki.cyanogenmod.org/w/Google_Apps
Recommended Apps
Dark Material - CM12 Theme UI (Awesome looking Dark Theme for CM12/12.1)
TouchControl (Custom wake gestures, i.e. dt2w, s2w, etc. Choose "Ponury Stock Modified" kernel module)
3C Toolbox
Trickster MOD Kernel Settings
AZ Screen Recorder - No Root
Tips / Recommendations
Bugs
Gesture typing doesn't work on stock keyboard but does work on Google Keyboard
Disclaimer
I'm not responsible for bricked devices (honestly, has anyone actually ever bricked a GNexus?), data loss, lack of rhythm and coordination. Please remember to ALWAYS make backups before you flash and if you are changing filesystems on /data, you will lose ALL DATA which includes everything on internal storage and the recovery will NOT give you any warning before it performs this highly destructive act, so just be aware! Thanks and enjoy!
Click to expand...
Click to collapse
Thanks To/Credits
Code:
[URL="http://www.cyanogenmod.org/"]CyanogenMod[/URL]
[URL="http://forum.xda-developers.com/member.php?u=3390093"]MWisBest[/URL]
[URL="http://forum.xda-developers.com/member.php?u=2633638"]Ziyan[/URL]
[URL="http://forum.xda-developers.com/member.php?u=3623306"]Dirty_Jerz[/URL]
[URL="http://forum.xda-developers.com/member.php?u=4608636"]bsmitty83[/URL]
[URL="https://github.com/Liquidsmooth"]LiquidSmooth[/URL]
[URL="https://github.com/slimroms"]SlimRoms[/URL]
[URL="https://github.com/omnirom"]omnirom[/URL]
XDA:DevDB Information
CyanogenMod 12 (UNOFFICIAL) ROM for the Samsung Galaxy Nexus, ROM for the Samsung Galaxy Nexus
Contributors
zzpianoman
Source Code: https://github.com/zzpianoman
ROM OS Version: 5.1.1 Lollipop
ROM Kernel: Linux 3.0.101
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2015-03-23
Last Updated 2015-09-15
Reserved
Previous Builds
10/7/2015
Code:
[URL="https://www.androidfilehost.com/?fid=24052804347832232"]cm-12.1-20151007-UNOFFICIAL-maguro.zip[/URL]
09/14/2015
Code:
[URL="https://www.androidfilehost.com/?fid=24052804347816180"]cm-12.1-20150914-UNOFFICIAL-maguro.zip[/URL]
08/13/2015
Code:
[URL="https://www.androidfilehost.com/?fid=24052804347793158"]cm-12.1-20150813-UNOFFICIAL-maguro.zip[/URL]
07/27/2015
Code:
[URL="https://www.androidfilehost.com/?fid=24052804347782153"]cm-12.1-20150727-UNOFFICIAL-maguro.zip[/URL]
[SIZE="2"][B]*****UPDATE*****[/B][/SIZE]
[URL="http://forum.xda-developers.com/showpost.php?p=62160732&postcount=396"]cm-12.1-20150727-UNOFFICIAL-tuna_update1.zip[/URL]
07/18/2015
Code:
[URL="https://www.androidfilehost.com/?fid=24052804347776472"]cm-12.1-20150718-UNOFFICIAL-maguro.zip[/URL]
07/11/2015
Code:
[URL="https://www.androidfilehost.com/?fid=24052804347772069"]cm-12.1-20150711-UNOFFICIAL-maguro.zip[/URL]
06/26/2015
Code:
[URL="https://www.androidfilehost.com/?fid=24052804347765291"]cm-12.1-20150626-UNOFFICIAL-maguro.zip[/URL]
06/22/2015
Code:
[URL="https://www.androidfilehost.com/?fid=24052804347763431"]cm-12.1-20150622-UNOFFICIAL-maguro.zip[/URL]
06/12/2015
Code:
[URL="https://www.androidfilehost.com/?fid=24052804347758931"]cm-12.1-20150612-UNOFFICIAL-maguro.zip[/URL]
06/04/2015
Code:
[URL="https://www.androidfilehost.com/?fid=23991606952614713"]cm-12.1-20150604-UNOFFICIAL-maguro.zip[/URL]
05/27/2015
Code:
[URL="https://www.androidfilehost.com/?fid=23991606952610816"]cm-12.1-20150527-UNOFFICIAL-maguro.zip[/URL]
[SIZE="2"][B]***UPDATE***[/B][/SIZE] - Flash in recovery over 5/27/2015 build
[URL="http://forum.xda-developers.com/showpost.php?p=61026999&postcount=291"]cm-12.1-20150527_UNOFFICIAL-zzpianoman_update1.zip[/URL] (Fix for Play Services FC)
05/15/2015
Code:
[URL="https://www.androidfilehost.com/?fid=23991606952604054"]cm-12.1-20150515-UNOFFICIAL-maguro.zip[/URL]
04/29/2015
Code:
[URL="https://www.androidfilehost.com/?fid=23991606952594303"]cm-12.1-20150429-UNOFFICIAL-maguro.zip[/URL]
[SIZE="2"][B][U]GCC 4.7 Kernel[/U][/B][/SIZE]
If your device requires a kernel that is compiled with GCC 4.7
(i.e. won't boot) then flash this kernel over the 4/29/2015 build.
[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3289957&d=1430412506"]cm-12.1-zzpianoman-kernel-gcc-4.7.zip[/URL]
[SIZE="3"][B][U]UPDATE - 5/4/2015[/U][/B][/SIZE] - Flash in recovery on top of 4/29 build.
[URL="http://forum.xda-developers.com/showpost.php?p=60534106&postcount=217"]cm-12.1-20150429_UNOFFICIAL-zzpianoman_update1.zip[/URL]
04/23/2015
Code:
[URL="https://www.androidfilehost.com/?fid=96042739161892516"]cm-12.1-20150423-UNOFFICIAL-maguro.zip[/URL]
[SIZE="3"][B][U]GPS FIX:[/U][/B][/SIZE] - (flash this over [B]ANY[/B] CM-12 build prior to
4/29/2015 to fix satellite GPS!!)
[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3279981&d=1429903277"]cm-12-maguro_gps_fix.zip[/URL]
04/18/2015
Code:
[URL="https://www.androidfilehost.com/?fid=96039337900114737"]cm-12.1-20150418-UNOFFICIAL-maguro.zip[/URL]
[URL="http://forum.xda-developers.com/showpost.php?p=60269013&postcount=124"]Update - 4/21/2015[/URL]
04/05/2015
Code:
[URL="https://www.androidfilehost.com/?fid=95916177934551453"]cm-12-20150405-UNOFFICIAL-maguro.zip[/URL]
03/27/2015
Code:
[URL="https://www.androidfilehost.com/?fid=95916177934547216"]cm-12-20150327-UNOFFICIAL-maguro.zip[/URL]
[SIZE="3"][B][U]UPDATE: 4/2/2015[/U][/B][/SIZE]
[URL="http://forum.xda-developers.com/showpost.php?p=59850356&postcount=406"]cm-12-20150327_UNOFFICIAL-update1[/URL]
03/22/2015
Code:
[URL="https://www.androidfilehost.com/?fid=95916177934545093"]cm-12-20150322-UNOFFICIAL-maguro.zip[/URL]
[SIZE="3"][B][U]UPDATE: 3/22/2015[/U][/B][/SIZE]
This update include a kernel compiled with gcc 4.7 to fix some
non-booting devices with eMMC bug. Flash this in recovery
[B]after[/B] you flash the ROM. All future builds will include this by default.
[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3225706&d=1427145252"]cm-12-20150322_UNOFFICIAL-maguro_update1.zip[/URL]
Reserved
Yeah!! I was waiting for a CM12 rom based on DDK 1.8 as I wanted my camera to function properly. I'll flash it in a few hours and report back. Thanks!
Don't boot on my VYL00M Maguro :/ Stuck on Google logo and restart :/
Tolazace said:
Don't boot on my VYL00M Maguro :/ Stuck on Google logo and restart :/
Click to expand...
Click to collapse
Did you flash any other kernels? This ROM will only work with the included kernel - any other will result in bootloops.
Nope. Just clean flash this Rom + Gapps. Without Gapps still the same problem :/
Other LP roms works great (CM, FML, AOSP, Zmod, Dreams etc)
zzpianoman said:
Did you flash any other kernels? This ROM will only work with the included kernel - any other will result in bootloops.
Click to expand...
Click to collapse
I have the same problem with my kernel ... with the old chip, goes into bootloop, and perhaps the fault of GCC 4.9, I did a build with GCC 4.7 and posted on the forum a while ago, you look news ... let you know, I just news
Fenix46 said:
I have the same problem with my kernel ... with the old chip, goes into bootloop, and perhaps the fault of GCC 4.9, I did a build with GCC 4.7 and posted on the forum a while ago, you look news ... let you know, I just news
Click to expand...
Click to collapse
Ah! That must be it. I'll build the kernel with 4.7 and post a zip. Does this only affect certain maguro devices?
So when can you upload fix kernel? I would test this CM
zzpianoman said:
Ah! That must be it. I'll build the kernel with 4.7 and post a zip. Does this only affect certain maguro devices?
Click to expand...
Click to collapse
So, the problem and the GCC 4.9, go safe with GCC 4.7 a user has just confirmed that it works. This issue and on all models with the old chip "VYL00M"... with the new chip "V3U00M" the kernel can be compiled fine with GCC 4.9 no bootloop
Tolazace said:
So when can you upload fix kernel? I would test this CM
Click to expand...
Click to collapse
Shortly! I'm working on it....
Forgive me, I'm used to working on the toro variant so this eMMC bug is all new to me!
Tolazace said:
So when can you upload fix kernel? I would test this CM
Click to expand...
Click to collapse
Here is the kernel compiled with gcc 4.7. Let me know if this works!!
Working ^^ Thanks a lot I take for testing ^^
Tolazace said:
Working ^^ Thanks a lot I take for testing ^^
Click to expand...
Click to collapse
Great! I'll add it to the OP.
zzpianoman, many thanks for having ported your work to our maguro device.
I have 2 questions for you:
- does this rom have the green line at the bottom of recorded videos?
- do you plan to update LP to 5.1?
armbold said:
zzpianoman, many thanks for having ported your work to our maguro device.
I have 2 questions for you:
- does this rom have the green line at the bottom of recorded videos?
- do you plan to update LP to 5.1?
Click to expand...
Click to collapse
The rom automatically crops the section of video where green line is present. Not a solution, but a nice workaround.
The CM sources have not yet been udated to 5.1 so we'll have to wait until sources are updated to CM12.1
After one day using:
Positive:
-Rom is smooth and fast
-Green Lines "gone" (don't see it)
-Offmode Charging work
-Lot of features
-1080p don't laggy
-DoubleTap2Wake work *.*
Negative:
-Free ram is ~200mb so if you open sms/gallery/browser and listen music - music player turn off and after back to homescreen launcher is restart
-When 3G is ON - phone little laggy
-Recent stack laggy and sometimes have a bug with app name
Rom is Great and when management Ram maybe can be better this Rom be a best lollipop rom o Gnex So I can't wait for next version
(sorry for english)
@zzpianoman Bug?
ALBIEL said:
@zzpianoman Bug?
Click to expand...
Click to collapse
What am I looking at here? Mobile data issue?
{
"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"
}
XXP/DORA/F8131 OmniROM UNOFFICIAL LINARO BUILDS
OREO 8.1.0_r42
Kernel: 4.4.144
infected_ current build: 20180810 - kernel compiled with gcc linaro 5.5
DOWNLOAD
dic1911 current build (Stock Toolchain + Framework Optimization): 20180829
DOWNLOAD
CURRENT ISSUES:
- You tell me.
KERNEL CODE COMPILED WITH LATEST LINARO AARCH64-LINUX-GNU 5.5 (201711)
KERNEL SOURCE: https://github.com/infectedmushi/android_kernel_sony_msm-omni/tree/android-8.0
BUGS REPORT
REPORT BUGS ONLY:
- AFTER A CLEAN INSTALL
- USING STOCK KERNEL
- NO MODS OF ANY SORT
OMNI GERRIT REVIEW
https://gerrit.omnirom.org/
BUILDBOT:
(amd ryzen 2700x @ stock, msi x470 gaming pro carbon, 16gb g.skill ripjaws v red 3000mhz cl16, msi gtx 1070, 1x samsung ssd 850 evo 500gb + 1x samsung ssd 850 evo 250gb + 1x samsung ssd 860 evo 500gb + 1x toshiba/ocz ssd tr-150 240gb, 3x western digital wd10ezex 1tb hdd, 1x seagate 2tb hdd, silverstone olympia 1000w psu, antec 1200 high-tower)
(wc setup: ekwb supremacy evo amd cpu-block, ek coolstream xtx 240 radiator, 2x scythe slipstream 120mm 1900rpm fans, swiftech mcp355 water-pump, danger den 5.25" reservoir bay)
DISCLAIMER:
These builds are freshly compiled/synced from OmniROM open-source code.
XDA:DevDB Information
XXP/DORA/F8131 OmniROM UNOFFICIAL LINARO BUILDS, ROM for the Sony Xperia X Performance
Contributors
infected_, dic1911
Source Code: https://github.com/omnirom
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: TWRP Recovery
Based On: OMNI/AOSP
Version Information
Status: Nightly
Created 2017-10-15
Last Updated 2018-08-29
Reserved
Raw Instructions:
- download latest build, latest ODM, and both twrp files (img + zip)
- fastboot boot twrp-3.2.1-20171218-boot-dora.img
- enter recovery (with the phone off, press volume down + power button at same time for a brief second)
- wipe all things, flash build, flash gapps, and flash recovery zip = twrp-3.2.1-20171218-fota-dora.zip
- adb push v10_tone_oreo.img /sdcard
- adb shell into the device, and: cd sdcard; dd if=v10_tone_oreo.img of=/dev/block/bootdevice/by-name/oem;
- reboot and you should be all set! enjoy.
Reserved
F.A.Q (Frequently Asked Questions)
What is the difference between these builds and the official builds?
These are unofficial builds of OmniROM for the Xperia X Performance (F8131)
ROM is built using the same source code (github) like the official one but with these following additions:
Compiled using linaro aarch64-linux-gnu 5.4.1 (kernel code) & ubertc aarch64-linux-android 4.9.x (rom code) toolchain compilers
May contain some custom cherry-picks. Always see changelog for details.
Cross-compiled using those custom toolchains results in a more smoother, faster, and battery friendly ROM
What is Toolchain?
To compile any Android project like a kernel or ROM, developers need to use a toolchain. As per elinux.org, a toolchain is a set of distinct software development tools that are linked (or chained) together by specific stages such as GCC, binutils and glibc (a portion of the GNU Toolchain). Toolchains may contain a debugger or a compiler for a specific programming language as C++ or other. Quite often, the toolchain used for embedded development is a cross toolchain, or more commonly known as a cross compiler. All the programs (like GCC) run on a host system of a specific architecture (such as x86) but produce binary code (executables) to run on a different architecture (e.g. ARM).
The most commonly used toolchain is GCC, initially released almost 20 years ago. A lightly modified GCC is used by Google during the AOSP build process. While Google’s GCC is considered to be the most stable toolchain around, it has some pretty decent competitors like Linaro and SaberMod. These projects are known to boost the overall system performance significantly on many devices. Let’s take a quick look to see the background of these projects.
Click to expand...
Click to collapse
Source: http://elinux.org
What is UBERTC?
From where UBERTC is coming from, from lead developer words:
UBERTC Background/History
After years of using different custom toolchains like Linaro and SaberMod, I found there were things I liked about both of them but also things that didn't sit quite as well with me. SaberMod always seemed to have UI lag (especially in scrolling) but opened apps well and Linaro always seemed to be buttery smooth but had terrible app opening speed. Linaro battery was also worse for me than SaberMod. After going back and forth between toolchains I finally had this epiphany! Why not just take all of the best parts of all toolchains and merge them into one? So I began bringing up my own toolchain from gnu.org. At first I patched in all of the AOSP toolchain pactches (much like how SaberMod did it originally however it is important that you realize that No! I did not copy and paste SaberMod into my source I'm simply stating that I used their idea of merging aosp into gnu.org) to my source. Then I went through and added all of the linaro patches that I could to the source. I also made sure that I had the very latest of every toolchain component. I then made very minimal changes to the aosp toolchain build folder to allow for building with these newer toolchain components and UBERTC was born!!! (Note: both Linaro and SaberMod both made lots of modifications to the toolchain build folder, UBERTC is the closest to the aosp build process)
Click to expand...
Click to collapse
Source: https://plus.google.com/communities/112152563785863538123
What is Linaro?
Linaro is the place where engineers from the world's leading technology companies define the future of Linux on ARM. The company is a not-for-profit engineering organization with over 120 engineers working on consolidating and optimizing open source software for the ARM architecture, including the GCC toolchain, the Linux kernel, ARM power management, graphics and multimedia interfaces.
Click to expand...
Click to collapse
Source: http://www.linaro.org/linux-on-arm/
Optimization Flags in GCC
What are flags?
For compilers such as GCC, flags are essentially options. A flag can enable or disable an option or feature that is used when compiling (building) code.
What are optimizations?
Optimizations, in the context of compiler flags, are flags that improve some aspect of the code, whether it be size, speed, memory use, and debugging, among other possibilities.
General Optimizations
These optimizations are basic flags in GCC, typically implemented into projects to improve an aspect of the final compiled code.
-O1: Optimization level 1, very basic optimizations, rarely used.
-O2: Optimization level 2, basic optimizations, most commonly used.
-O3: Optimization level 3, basic + experimental optimizations. Large performance boost, but can produce bugs.
-Os: Optimize for size. Most of the optimizations from levels 1 and 2, with extras added to decrease the size of code.
-Ofast: All Optimizations from levels 1, 2, and 3, with extra fast math optimizations.
Typically produces the most bugs, with a large performance gain.
-Og: No performance boost, optimizes the debugging experience, making errors and
warnings more informative to help developers.
-g0: Disables all extra debugging, usually makes code faster.
-fomit-frame-pointer: Removes frame pointers when they aren’t needed, streamlining the code.
-fipa-sra: Removes unused parameters/variables and replaces parameters with the called value, streamlining the code.
-fkeep-inline-functions: Emits static inline functions, even after they’ve been called.
-fmodulo-sched: Reorders instructions in loops in the most optimal way.
-fmodulo-sched-allow-regmoves: a more aggressive -fmodulo-sched, optimizing loops further by allowing register moves
-fgcse-sm: Moves stores out of loops to decrease the workload of loops.
-fgcse-las: Removes redundant loads after a store to reduce the workload.
-fgcse-after-reload: Removes redundant loads after a reload.
-funsafe-loop-optimizations: Optimize more by making assumptions, can create bugs from loops overflowing.
-fira-hoist-pressure: Decreases size of the code by evaluating register pressure for hoist expressions.
-fira-loop-pressure: Makes code smaller and faster by evaluating the register pressure of loops.
-DNDEBUG: Passes the variable for no debugging.
-flto: Enables link time optimizations (LTO) for improved library and executable performance.
Graphite Optimizations
Graphite is a project within gcc that uses the integer set library (ISL) and the chunky loop generator (CLooG) to improve memory use and optimize loops.
-fgraphite: Performs basic graphite loop and memory optimizations.
-floop-interchange: Switches two nested loops.
-floop-strip-mine: Splits a complex loop into a set nested loops.
-floop-block: Splits a loop into nested loops so that the memory fits into caches.
-fgraphite-identity: Creates a visual polyhedral representation of certain graphite optimizations. with some optimizations from ISL such as dead code removal.
-floop-nest-optimize: Optimizes the order of nested loops for data-locality and parallelism. This flag is experimental
-floop-unroll-and-jam: Enable unroll and jam for the ISL loop optimizer.
-floop-parallelize-all: Use graphite data to find and parallelize loops that can be.
Multithreading optimizations
Make code run in multiple jobs (threads) to use a multicore cpu to its fullest potential.
-ftree-parallelize-loops=n: Run parallelized loops is n number of threads.
-pthread: Use the posix thread system for multi-threading.
-fopenmp: Use the OpenMP thread system for multithreading. Tends to use less ram than posix.
Sanitizer Flags
These flags use libsanitizer for memory optimizations.
-fsanitize=leak: Sanitize memory leaks to reduce memory use
-fsanitize=address: Sanitize memory addresses to reduce memory use
-fsanitize=thread: Sanitize excess threads to reduce memory/cpu use. Only for 64bit.
Hardware Optimizations
These optimizations optimize code for the targets cpu, gpu, or ram.
-marm: Uses the ARM instruction set for executable code, improving performance.
-mthumb: Uses the Thumb2 instruction set, improving compatibility.
-mthumb-interwork: Improves compatibility between Thumb and ARM code.
-march=X: Optimizes code for your CPU’s arch, such as armv6, armv7-a, etc
-mcpu=X: Optimizes code for your specific CPU such as cortex-a15, cortex-a53, etc.
-mtune=X: Refer to -mcpu
-mfpu=X: Optimizes code for your CPU’s FPU such as vfpv3. vfpv4, neon, etc.
-mabi=X: Optimizes code ABI for your CPU, such as 32 or 64
Click to expand...
Click to collapse
Stuck on boot logo.
Hallon said:
Stuck on boot logo.
Click to expand...
Click to collapse
you need to flash odm before, it's like a new vendero blobs partition os sony aosp program
Flash vendor image to your device
Download the vendor image corresponding your device from List of devices and resources.
Unpack the vendor zip file to obtain the vendor image.
unzip SW_binaries_for_Xperia_AOSP_O_MR0_4.4_<release version>_<platform>.zip
Note: Release version should be equivalent to the latest downloaded image version, and platform should match your device.
On your device: Connect the device to your computer in Fastboot mode, by pressing volume up while inserting the USB cable. When the device is in Fastboot mode, the LED on the device will be illuminated in blue.
On your computer: Flash the vendor image by entering the following commands in a terminal window:
fastboot flash oem SW_binaries_for_Xperia_AOSP_O_MR0_4.4_<release version>_<platform>.img
Note: Release version should be equivalent to the latest downloaded image version, and platform should match your device.
Click to expand...
Click to collapse
convert img with simg2img before
https://developer.sonymobile.com/op...-build-aosp-oreo-for-unlocked-xperia-devices/
check at the bottom.
Hallon said:
Stuck on boot logo.
Click to expand...
Click to collapse
As stated in post above, you need to 'flash' the propriatary blobs to oem partition.
Instructions for this, you can find in my thread: https://forum.xda-developers.com/showpost.php?p=74130466&postcount=2
new build is up.
regards.
writing ‘oem’…
FAILED (remote: Command not allowed)
finished. total time: 4.967s
F8131_41.2.A.7.76_1305-2784_R2D.ftf
hellyjia said:
writing ‘oem’…
FAILED (remote: Command not allowed)
finished. total time: 4.967s
F8131_41.2.A.7.76_1305-2784_R2D.ftf
Click to expand...
Click to collapse
Dont you read ?
https://forum.xda-developers.com/showpost.php?p=74130466&postcount=2
F8132 is OK?
Must flash it on Oreo ,or it's OK on Nougat,too?
F8132 is OK,but not dual-SIM.
Would it support dual-sim in the next version?
Could U support NFC-Sim ?
or flash something to enable it ?
finigerprint isn't work.
Help!
Cannot play songs(mp3) in music player. Whichever
- new build is up!
regards.
I can't get this to boot. What am I doing wrong?
Would I flash v20180204 from 20171112 with TWRP?
I can't OTA update.
fallingandroid said:
I can't get this to boot. What am I doing wrong?
Click to expand...
Click to collapse
Check OP. You are probably missing ODM
saiz0313 said:
Would I flash v20180204 from 20171112 with TWRP?
I can't OTA update.
Click to expand...
Click to collapse
I recommend a full system wipe, coming from 20171112.
Lot of things changed.
If I am coming from another Oreo build (AOSP) and already have the latest ODM, will I have to flash it again after installing (will do a full system+data wipe)?