*DISCLAIMER* This is a VOLUNTARY Fundraising to help Henrique Pereira to buy a Mi9SE to bring *OFFICIAL* Pixel Experience Rom.
You can already find all information here, and check the fundraising-status: https://telegra.ph/Mi-9-SE-Grus-fundraise-05-31
Hlcpereira said:
Hello everyone my name's Henrique Pereira, also known as Hlcpereira. I'm nowadays part of PixelExperience Team, as the Mi 8 (dipper) maintainer. An user asked me about the possibility of having PE for Mi 9 SE. Though I'd like to help, I wouldn't do blind builds, due a lot of reasons, but mainly because it's against my principles, and also because PixelExperience doesn't allow from now on build without the device anymore.
After some time and talking, at the end a bunch of people asked about crowdfunding a Mi 9 SE. I don't like the idea of opening a fundraise, but as it's the only way that I can imagine of me getting the device, decide to open that fundraise campaign.
The goal is about 1500 BRL (~377 USD). That price does include fee taxes (~90 USD), as Mi 9 SE isn't available officially in Brazil (and if it was it would cost more than 400 USD easily).
The device will be used to development proposes only, as the development and maintainship of the PixelExperience ROM for Mi 9 SE and also maybe for some kernel development only.
Click to expand...
Click to collapse
You can donate:
Paypal: http://bit.ly/hlcpereira_paypal
Picpay (Brazil Only): http://picpay.me/hlcpereira
Can we see how many people have contributed and how much money has been collected or missing?
Thanks
You can already find all information here, and check the fundraising-status: https://telegra.ph/Mi-9-SE-Grus-fundraise-05-31
Click to expand...
Click to collapse
Just open the link, bottom
I´am sorry link do not work me at work (my mistake). I keep my fingers crossed.
THE GOAL HAS BEEN REACHED. YOU CAN STOP DONATING. NOT A SINGLE CENT IS NEEDED ANYMORE!
Some things I'd like to make clear before anything.
1 - As per XDA rules and as it was also request by anothers moderators in the past (Copy and pasta ftw): There is absolutely NO obligation on the developers part to release a final product. Although this is what everyone wants, including myself, @Hlcpereira, the entire reason for a donation drive in the first place is because it's not the easiest thing in the world to do. This means it may not even be possible in the long run. There's a great potential for hurt feelings and "bad juju" if people donate with the expectation that a final product will 100% be released. Donations should be seen as support towards a best-effort on the part of the developer. Yes, I'll try my best and put all my efforts on it, but you must be aware that I also have a life. Android custom ROMs development is considered a hobby and not a job.
2 - The goal might get reduced in the meanwhile due possible money that I get to cover taxes and/or part of the device cost, or if I find a good deal for example. The goal previously was at ~377 USD as is in the OP, now is at ~339 USD.
3 - In case that the goal won't beat within sometime I will return the money of each one that donated, and that's mainly why I'm using PayPal (and Picpay for those who live in Brazil). If that happens and you didn't receive your money back I'd kindly ask you to PM me in here or at telegram.
4 - As soon as the amount funded reach the goal, I will stop the fundraising and I will request to close this thread.
For those interested, I've worked on Motorola Moto Maxx/Droid Turbo, Xiaomi Mi 5/5s/5s Plus and OnePlus 5/5T previously, and nowadays I'm working on Xiaomi Mi 8, as stated in the OP.
For those who can't/couldn't open the telegraph article the current status is: 339/~339 USD.
I'll be keeping that status up-to-date here and at telegraph article.
My github profile: https://github.com/Hlcpereira
Current donators:
* @ale.giordano
* 国枢 刘 (Some other donators used that same Paypal account)
* Dovy Maman
* Fabrizio Tomassini
* Zen Bahalwan
* Berry Pille
* Marco Dalla Stella
* Giulio Mattoni
* Vincenzo Fina
* 楽天 昴 新井
* Maximilian Riefer
* Gilmar Pelegrini Júnior
* Björn Krebs
* Jan Vecek
* @phidung3721
* @e_henning
* @dbjungle
* Paweł Bittner
* Tommaso Nannetti
* Mohamed Shanooz
* @asseroin
* Kay Füssel
* Jakub Čeppan
* @moorware
* Sebastian Schmidtke
* Maxim Bodgan
* José Angel Pérez Velázquez
* Bálint Szabó
* @piter5533
* @vikla
* @bertl7
* @Hobby-Student
* Jordaen Davids
* Abel Lencz
* PERFUMUM
* Joachim Frischknecht
* 和豊 清水
* Ireneusz Gawłowski
* @sjlim
* Bastian Ackermann
* Juan Lexu
Honestly I'm kinda lineage fans since it doesn't/or at least it has less-proprietary software.
But hey, it maybe a good start to trigger the others.
Any development for this device is extremely valuable. Count me in.
I'm on board!
donated… great idea… love to see PE for Mi9SE...
Donated ... It's time slowly to do bye miui :laugh:
Donated!
MIUI is so unsatisfying. Hope to see PE for the Mi 9 SE in the near future
I am working on bringing PE for our Mi 9 SE . I don't need money , I need help .
Minhaz Ahmed Muhe said:
I am working on bringing PE for our Mi 9 SE . I don't need money , I need help .
Click to expand...
Click to collapse
Please, entry in Mi9SE global Telegram @GrusFamily
Minhaz Ahmed Muhe said:
I am working on bringing PE for our Mi 9 SE . I don't need money , I need help .
Click to expand...
Click to collapse
What I recommend you to do then.
First: start learning about git stuff. Using the github web interface is asking for trouble, since authorship of the commits, which you can be accused of kanging (which is pretty much a reason that all ROMs are not accepting some people) and also because you're not showing any skills, You'll may turn into reason of joke around the Android Custom ROM development community. There's a lot of material about git around the internet. Here at XDA has a pretty much nice guide about git.
Second: By your XDA profile you have never tried build even a single unofficial ROM build, you are a simple user (yet). I recommend you to "start little". Unless you're a guy that came from the future, and that already saw everything of grus sources (device trees) and everything necessary for it in the ROM side sources (like indisplay fingerprint stuff), I'd rather say to wait for the stable device sources and then start taking "baby steps", building the ROM that the devices trees were made/adapted for, and looking/searching to know what does every single stuff/part of the sources. Ofc I don't know everything about Android itself and maybe will never know.
The only thing about that I'll really complain a lot and say that's a must is: You must never be a dickhead, acting like you're a fricking pro developer, while you're just a newbie, arguing with and pissing off more experienced guys; or an scammer, just to fool users not inside custom ROM development stuff itself or that are ingenuous, bcz of money, all that as some "developers", as they like to be called themselves, are (or were, because some gave up of doing that thankfully) doing.
I would help but I don't have a paypal account
@givemerobot You can donate without PayPal account via payment card or you can easy create your own account: http://bfy.tw/OExT
fewer words and more deeds :good:
Donated, thank you for your initiative!
Hlcpereira said:
What I recommend you to do then.
First: start learning about git stuff. Using the github ..................
Click to expand...
Click to collapse
I've already uploaded my Device tree and proprietary blobs on my github account , Synchronized PE repos . Since this is my first attempt to build a rom for an unsupported device , of course I had to kang some stuffs from a similar device like Mi 8 SE .
Right now I am trying to fix some errors which appear while entering the final build command .
[email protected]:~/android/PixelExperience# mka grus
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=9
CUSTOM_VERSION=PixelExperience_grus-9.0-20190623-1223-OFFICIAL
TARGET_PRODUCT=aosp_grus
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=kryo300
TARGET_2ND_ARCH=arm
TARGET_2ND_ARCH_VARIANT=armv8-a
TARGET_2ND_CPU_VARIANT=cortex-a75
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-4.18.0-22-generic-x86_64-Ubuntu-18.04.2-LTS
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=PQ3A.190605.003
OUT_DIR=/root/android/PixelExperience/out
============================================
ninja: no work to do.
ninja: no work to do.
$(shell date -u +%d) was changed, regenerating...
$(shell date -u +%d) was changed, regenerating...
[95/961] including device/xiaomi/grus/Android.mk ...
device/xiaomi/grus/rootdir/Android.mk: error: init.qcom.rc: No source files specified
build/make/core/prebuilt_internal.mk:35: error: done.
18:29:19 ckati failed with: exit status 1
#### failed to build some targets (05:43 (mm:ss)) ####
[email protected]:~/android/PixelExperience#
---------- Post added at 12:40 PM ---------- Previous post was at 12:31 PM ----------
NOW THIS :3
[961/961] including vendor/xiaomi/grus/Android.mk ...
ninja: error: unknown target 'grus', did you mean 'run'?
18:40:06 ninja failed with: exit status 1
moorware said:
Donated a penny, thank you for your initiative!
Click to expand...
Click to collapse
Are you serious? If you don't want to contribute, then bug off. Don't be disrespectful.
Related
About Carbon
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. and on our Gerrit CarbonDev Gerrit.
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, 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.
Features
All of our features can be found on our site here:
Carbon Features
Here are some screenshots:
Carbon Screenshots
Carbon Updates
Join us on these Social Media Channels to keep yourself up-to-date on all the latest Carbon news, updates, contests, and more! Join our completely open Google+ community for insider conversation with devs and other users.
Download Carbon
All Carbon downloads and further information such as features, changelog, and FAQ can be found on our website.
Carbon Downloads
Changelog
For a detailed changelog, check out the changes made each night here:
Carbon Changelog
Support
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
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 website. Carbon FAQ
3) Ask a question in your device forum. 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.
4) Ask a question on our IRC channel. Connect to #teamcarbon on irc.freenode.net or click here. You'll find several other Carbon fans and usually one or more devs as well. Please be polite.
Who is Team Carbon?
Find out here:
Carbon Team
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][Nightly/Release] CarbonRom KitKat [i9100], ROM for the Samsung Galaxy S II
Contributors
CarbonDev, Myself5
ROM OS Version: 4.4.x KitKat
Based On: AOSP
Version Information
Status: Beta
Created 2014-02-14
Last Updated 2014-06-07
Reserved
Reserved
Hello Guys.
I'm your i9100 device maintainer.
I meanwhile tweaked the Rom specially for the i9100 so its difference to our other devices is:
Compiled using SaberMod arm-eabi 4.7 (Kernel code) and SaberMod arm-linux-androideabi 4.8 (ROM code) toolchain compilers
Cross-compiled using those custom toolchains results in a more smoother, faster, and battery friendly ROM
F.A.Q.:
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
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
Greetings
Myself5
Nice Work Dude !
Mine
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Whats Up Whith "Mine" ?
great ...thanks ....will try it surly
Great!! carbon finally arrived gonna try
Sent from my GT-I9100 using Tapatalk
im not able to see the download link in carbon page, i select our device but the links to download the ROM doesnt appear, can someone share the download link?
attack11 said:
im not able to see the download link in carbon page, i select our device but the links to download the ROM doesnt appear, can someone share the download link?
Click to expand...
Click to collapse
I have found that this link:
http://carbon-rom.com/downloads/?device=i9100&type=nightly&country=US
Showing some dates but still no luck with working link...
Послато са GT-I9100 уз помоћ Тапатока
Will this rom contain the tweaks/things that Myself5 added to his unofficial build?
It seems like we're currently having some issues with our download page getting accessed by mobile browsers. Please use your computer to download until we fixed it.
@GreekBlood: All in all the most tweaks I made were coommits from gerrit, so sooner or later they will be included
http://carbon-rom.com/downloads/?device=i9100&type=nightly&country=BE
Here i can see the downloads perfectly and they also work.
And here is the latest nightly for our SII :> http://eu1.dl.carbon-rom.com/files/i9100/nightly/CARBON-KK-NIGHTLY-20140215-0148-i9100.zip
congrats myself5 on getting to be the maintainer for this great rom on our s2.
i think i will just dl from the official carbon page,and then just use the updater to get all the improvements and fixes moving forward!!
well first hour whit this rom.and everything seems good after all! just one question,how i can enable wheater widget in the lockscreen? i cant find an option..
also some translations are missing (in spanish) i can help if you want.
also another question Halo will be added on the future?
i flashed newest rom all good.kernel included is not compatible with stweaks.
I plan on flashing gustavo 2\09 kernel.
will nightly updates flash a another kernel each update??
thnx
A little problem
I have a little problem,when i try to install gapps it says that i have insufficient space. How would i fix that? I`m using PA-GOOGLE APPS (FULL MODULAR PACKAGE) .
And another question. Previous versions that were unofficial had TWRP, how could I get that back too?
@attack11 the Weather Widget is called cLock. HALO will be added it just has some small bugs ATM we need to fix. Thanks for your help, I will later PM you all files you need to translate.
@saskrider: It will flash a new Kernel every Update. However when you later (as soon as it's working) use CarbonDelta to update there will be a option to add Custom Zip's to flash after the Rom (like GApps and Custom Kernels)
@Pecka40: the S2's Sytem Partition is to small for these GApps, use some smaller ones
Greetings
Myself5
Sent from my GT-I9100 using Tapatalk
Myself5 said:
@attack11 the Weather Widget is called cLock. HALO will be added it just has some small bugs ATM we need to fix. Thanks for your help, I will later PM you all files you need to translate.
@saskrider: It will flash a new Kernel every Update. However when you later (as soon as it's working) use CarbonDelta to update there will be a option to add Custom Zip's to flash after the Rom (like GApps and Custom Kernels)
@Pecka40: the S2's Sytem Partition is to small for these GApps, use some smaller ones
Greetings
Myself5
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply! And there is no way of making it bigger?
And could you please answer the other question. About how can I get TWRP on it.
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at 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.
Download Links
Make sure you're on an M-gen baseband
Links: http://forum.xda-developers.com/showpost.php?p=66760703&postcount=1270
CyanogenMod:
Nightly: http://download.cyanogenmod.org/?device=m8&type=nightly
Google apps addon:
OpenGapps: http://opengapps.org/ (you'll want a zip for the ARM platform, Android version 6.0)
HEADS UP: Be sure you flash the gapps package with your rom. If you boot your rom, then go back and try to flash gapps after the fact, you're gonna have a bad time.
Misc Links
Unoffical changelog:
Link: http://www.cmxlog.com/13/m8/
Learn to build yourself:
Link: https://wiki.cyanogenmod.org/w/Build_for_m8
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
[ROM][OFFICIAL] CyanogenMod 13.0 Nightlies for the HTC One m8 , ROM for the HTC One (M8)
Contributors
invisiblek
Source Code: http://www.github.com/CyanogenMod
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Version Information
Status: Nightly
Created 2015-11-25
Last Updated 2015-11-24
Says 12.1 still - I'm first!!!
Invisiblek, you made the thread before the CM13 nightlies even started! Silly goose <3!
Opticuhl said:
Invisiblek, you made the thread before the CM13 nightlies even started! Silly goose <3!
Click to expand...
Click to collapse
meh
lol looks like it missed the nightly list this time too...dang...well i guess this thread is useless until tomorrow
invisiblek said:
meh
lol looks like it missed the nightly list this time too...dang...well i guess this thread is useless until tomorrow
Click to expand...
Click to collapse
No worries.
Gonna back up all the goodies tonight
Sent from my HTC One_M8 using Tapatalk
So how many times do you think someone is going to ask where the downloads are because they can't find the right link? Lol! I'm betting at least 10 haha
Where's the links I can only find cm 15.1?
Joking aside, I can't wait. Looking forward to the 13 nightlies on my M8. Good job to everyone involved.
Ooooooo lucky 13. Can't wait to try this out!! I'm on the stock rooted version of MM right now. Anxious to see what CM has added!
Sent from my HTC One_M8 using Tapatalk
Hey @invisiblek
Thank you so much for bringing the m8 to cm13!
I'm trying to build a copy (just for fun, and see if I can play around with some toolchains) and I have a quick question.
(The last time I built cm was over a year ago, so I'm a bit rusty.)
How do I include the Muppets proprietary blobs in my build? I'm Googling it and I think that I need to add a few lines to my repo manifest. Can you share with me the correct project lines to add?
Thanks!
David 617 said:
Hey @invisiblek
Thank you so much for bringing the m8 to cm13!
I'm trying to build a copy (just for fun, and see if I can play around with some toolchains) and I have a quick question.
(The last time I built cm was over a year ago, so I'm a bit rusty.)
How do I include the Muppets proprietary blobs in my build? I'm Googling it and I think that I need to add a few lines to my repo manifest. Can you share with me the correct project lines to add?
Thanks!
Click to expand...
Click to collapse
Something like this in local manifest.
Code:
<project name="themuppets/proprietary_vendor_htc" path="vendor/htc" remote="github" />
Darknites said:
Something like this in local manifest.
Code:
<project name="themuppets/proprietary_vendor_htc" path="vendor/htc" remote="github" />
Click to expand...
Click to collapse
Thanks! One more question, how do I reset my local repo so I can erase changes I made?
David 617 said:
Thanks! One more question, how do I reset my local repo so I can erase changes I made?
Click to expand...
Click to collapse
You can do a force sync or you just delete the folder. It should tell you how if it runs into any issues with your changes.
I made an updated cm build. I don't know if I'm allowed to post a link here, but if anyone is interested pm me and I'll upload it to dropbox or something.
I'm gonna try to get a linaro build up and running this weekend. I've never done something like that, so it should be fun
wifi calling
wifi calling dream might still be alive?
Perhaps we'll get some nightly love tonight...
Dan Tekle said:
Perhaps we'll get some nightly love tonight...
Click to expand...
Click to collapse
I believe we will, I think we didn't make it last night because the commit to add M8 to the CM13 build list missed the deadline.
Latest build seems to be CM12.1 still. So hyped for these nightlies ! Great work everyone who is contributing!
Hope this is ok with the OP, (just tell me if you want me to remove the link or open a separate thread)
I built a copy of CM13 just now. I used the UBER Toolchain. I benches a tad bit higher in Antutu, but honestly Marshmallow is so smooth that I can't tell the difference.
Here is the link - https://dl.dropboxusercontent.com/u/25650355/cm-13.0-20151126-UNOFFICIAL-m8.zip
Question for the devs:
Is it correct the Doze is off by default? It appears that we need to set config_enableAutoPowerModes to True.
As per the Android Guidlines over here there are 2 requirements for doze.
Device implements the significant motion detector (SMD) APIs in the Sensor HAL. Devices that do not implement these APIs cannot support Doze.
Device has a cloud messaging service, such as Google Cloud Messaging (GCM). This enables the device to know when to wake from Doze.
When I run "adb shell dumpsys sensorservice | grep significant" I get -
Significant Motion| HTC Group Ltd.| version=1 |android.sensor.significant_motion| 0x0000000e | "" | type=17 | one-shot | maxDelay=0us |minDelay=-1us |no batching | wakeUp | last=<>
which would appear that the m8 does have this 'significant motion detector'
I don't know what the second requirement is referring to, is it on the app-level, that the app my have gcm to wake the device up?
Anyways, I'm making a build with Doze set to true (in framworks/res/values/config.xml) to see what happens
Alllllright, here we go, booting up now, clean flash with gapps and SuperSU!
Introduction
Hello everyone, this is a thread to introduce both users and kernel developers to the concept of linux-stable as well as give developers some tips and a tree to either merge into their own, use as a base, or just as a reference. Feel free to ask questions and enjoy!
What is it?
linux-stable is, as the name implies, the stable branch of the Linux kernel, the base of Android. The phone could not run without the Linux kernel (at least not without reworking a lot of stuff). The Android kernels are based on the longterm stable trees:
Longterm
There are usually several "longterm maintenance" kernel releases provided for the purposes of backporting bugfixes for older kernel trees. Only important bugfixes are applied to such kernels and they don't usually see very frequent releases, especially for older trees.
Click to expand...
Click to collapse
Source: https://www.kernel.org/category/releases.html
All Linux development happens on the master branch, which is governed by Linus Torvalds. When issues are discovered there, the fixes are applied then backported to these various stable trees for consumption. It is not uncommon for a fix to need to go back a few years.
There is a LOT more information available in the notes repo in the android-linux-stable organization if you care to learn more in-depth: https://github.com/android-linux-stable/notes
What does this mean for me?
If you are a developer, this means you should be merging these changes into your own tree. These are vetted, stable fixes to real world problems and they are being handed out for free. It does not take long to get up to date (as you can just merge this tree directly into your own or do it yourself using the tree as a reference) and once you are up to date, there is usually a release once every two weeks, give or take. I provide a rebuttal to a lot of various complaints here. If you still feel like there is a good reason not to do this, please let me know, I'll be happy to try and debate on it!
If you are a user, it means that you should be looking for and using kernels that have these fixes, as it shows the developers care for your security and stability. The current version for this device is 4.4.78 on OOS and 4.4.100 on Lineage while the current version upstream is 4.4.162 so all you need to do is go into Settings > About phone and look at the kernel version to know if you are up to date.
How do I use?
If you are a developer, the reference tree is located in the android-linux-stable organization: https://github.com/android-linux-stable/op5
There are three branches, one for OxygenOS 8.0 stable, one for OyxgenOS 8.1 beta, and one for Lineage 15.1.
This can either be merged into your existing kernel tree if you have one or be used as a fresh base. You do not need my permission to use it nor do you need to give me credit (although it would be appreciated).
If you are a user, use a kernel that has the changes added in!
Getting notified about updates
There are a few ways to get notified of linux-stable updates:
The linux-kernel-announce mailing list: http://vger.kernel.org/vger-lists.html#linux-kernel-announce
The android-linux-stable Telegram channel: https://t.me/alsupdates
Subscribe to this thread
Follow me on Google+ or Twitter
Getting help
If you have any issues with getting these changes into your tree or want to ask a question, there are a few different ways to do it:
Post in this thread
Join the linux-stable support chat on Telegram: https://t.me/joinchat/C1UAJ1EMSX31PCFdwLnOSg
File an issue either in the android-linux-stable notes repo or the android-linux-stable repo for this device
When requesting help, please give some solid details as to what you are struggling with, as I am happy to provide assistant and clarity but not to do something for you (unless I screwed up).
The OP has been updated, including some more information for users as well as some more ways of getting help and notified of updates! Enjoy
Very Nice.!!! :fingers-crossed:
nathanchance said:
The OP has been updated, including some more information for users as well as some more ways of getting help and notified of updates! Enjoy
Click to expand...
Click to collapse
Thanks for everything Sir.
You really are techno-Jesus, here to teach the ways of kernel perfection. I love your work, dedication, and care for your kernel users. Flash4lyfe.
Yes, please flame me for being a fanboy. You can never show enough appreciation for our beloved xda developers (especially the ones that don't treat users like ****).
Many thanks for your work and initiative @nathanchance :good: appreciated :highfive:
Currently giving a try to make a kernel version based from linux .116 of your op5 branch and looks like I have the following error :
Code:
fs/f2fs/f2fs.h:136:20: error: static declaration of 'inode_nohighmem' follows non-static declaration
Any idea ? I was thinking of a "KBUILD_CFLAGS" addition into Makefile (or something like that), but I'm probably wrong I guess.
FYI I'm using stock 4.9 android google toolchain
AndroidGX said:
Many thanks for your work and initiative @nathanchance :good: appreciated :highfive:
Currently giving a try to make a kernel version based from linux .116 of your op5 branch and looks like I have the following error :
Code:
fs/f2fs/f2fs.h:136:20: error: static declaration of 'inode_nohighmem' follows non-static declaration
Any idea ? I was thinking of a "KBUILD_CFLAGS" addition into Makefile (or something like that), but I'm probably wrong I guess.
FYI I'm using stock 4.9 android google toolchain
Click to expand...
Click to collapse
Wow I am so sorry about that, I must not have built 4.4.116 I removed all of the upstream f2fs code in my own kernel tree so I didn't encounter this error. I have pushed the fix that popped up in kernel/common, should be able to pull and build successfully now :good: :highfive:
nathanchance said:
Wow I am so sorry about that, I must not have built 4.4.116 I removed all of the upstream f2fs code in my own kernel tree so I didn't encounter this error. I have pushed the fix that popped up in kernel/common, should be able to pull and build successfully now :good: :highfive:
Click to expand...
Click to collapse
No worries
Thanks, it works like a charm now (currently trying my kernel on .116), again good job :highfive:
Cheers'
4.4.117 has been merged in.
4.4.118 has been merged in (conflict notes).
4.4.119 and OOS 5.0.4 have been merged in.
4.4.120 has been merged in (conflict notes).
thanks for making this, trying to build lineage and I keep getting the following error:
Code:
drivers/bluetooth/btfm_slim.c:26:23: fatal error: btfm_slim.h: No such file or directory
Any ideas?
---------- Post added at 10:47 PM ---------- Previous post was at 10:20 PM ----------
lol, found one of your comments on another post that helped
Use an out folder.
mkdir out
make O=out mata_defconfig
make O=out -j$(nproc --all)
Click to expand...
Click to collapse
new problem, the kernel compiles into an Image.gz, how would I go about getting a zImage for use in AnyKernel
aeppacher said:
thanks for making this, trying to build lineage and I keep getting the following error:
Any ideas?
---------- Post added at 10:47 PM ---------- Previous post was at 10:20 PM ----------
lol, found one of your comments on another post that helped
new problem, the kernel compiles into an Image.gz, how would I go about getting a zImage for use in AnyKernel
Click to expand...
Click to collapse
That is the zImage (you'll actually want to use Image.gz-dtb), you can just add it to the AnyKernel2 zip as is, the backend handles that name.
Sent from my Google Pixel 2 XL using XDA Labs
nathanchance said:
That is the zImage (you'll actually want to use Image.gz-dtb), you can just add it to the AnyKernel2 zip as is, the backend handles that name.
Sent from my Google Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
It booted perfectly, thanks so much! I would use the thanks button but it doesn't seem to be working :/
4.4.121 has been merged in.
I will have a new tree based on the 8.1 sources out tonight.
Sent from my Google Pixel 2 XL using XDA Labs
I have added a new branch for the 8.1 beta source; I will continue to update both 8.0 and 8.1 until 8.1 goes stable.
https://github.com/android-linux-stable/op5/commits/oneplus/QC8998_O_8.1
4.4.122 has been merged in.
4.4.123 has been merged in.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
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.
*/
SUPPORTED DEVICES
- LEX720 (ZL1_CN)
- LEX722 (ZL0_CN)
- LEX727 (ZL1_NA)
SCREENSHOTS
3rd PARTY ADDONS/MODS
While we have no issues with people using supersu/magisk/xposed/custom kernels/etc, we can't provide support for users who have them installed.
This thread is not the right place to discuss about mods/addons.
HOW TO INSTALL LINEAGEOS
- Make sure your phone is running firmware from at least 20S
- Download the LineageOS zip(s). (see Downloads)
- Copy the LineageOS zip to internal sdcard.
- Unlock bootloader and install TWRP 3.2.3 or higher.
- Boot into TWRP.
- Perform a backup of your current ROM. (Optional)
- RECOMMENDED: Do a factory reset! No support if you didn't!
- Flash LineageOS.
- Optional: Install the Google Apps addon package. (see Downloads)
- Reboot
HOW TO UPDATE LINEAGEOS
- Download the LineageOS zip(s). (see Downloads)
- Copy the LineageOS zip to internal sdcard.
- Flash LineageOS.
- Reboot
DOWNLOADS
LineageOS 16.0: Official | Unofficial
Migration-Tools: https://androidfilehost.com/?w=files&flid=254680 (Unofficial->Official, Official->Unofficial)
SU-Addon: Official | Unofficial
Google Apps: http://opengapps.org/
TWRP: https://sourceforge.net/projects/lineageos-on-leeco/files/twrp/
Firmware: https://sourceforge.net/projects/lineageos-on-leeco/files/firmware/
DEVELOPER RESOURCES
https://github.com/lineageos/android_device_leeco_msm8996-common
https://github.com/lineageos/android_device_leeco_zl1
https://github.com/lineageos/android_kernel_leeco_msm8996
HOW TO CONTRIBUTE?
Send your patches up for review: https://review.lineageos.org/
KNOWN ISSUES
- Some banking apps refuse to work
Treble pie? You are a master, sir!
*reserved*
Thanks for keeping this wonderful device alive, I'm going to try it, ... downloading now
Thanks codeworkx for your unbeliveable support on Le Pro 3!
Thanks @codeworkx for your great work !! Installed with mini gapps, everything worked! at the moment :
- on the style menu does not work, although the menu is present
- The camera gave an initial error by starting it, then after closing it went right, the rear / front camera change can sometimes seem slow, just have a little patience ..
Despite an experimental version, I would say the impression of stability for daily use ..
For the rest the various menu functions, no problem.
Thank you!
Wooow good @codework
In the first start I see this "Process System is not responding" constantly, then the fingerprint process does not work, the system is quite fluid, the mobile data works well "H +", in other rom does not come out, I could not follow testing, the poster "Process System is not responding" Close or Wait is quite annoying.
AlexCuban said:
In the first start I see this "Process System is not responding" constantly, then the fingerprint process does not work, the system is quite fluid, the mobile data works well "H +", in other rom does not come out, I could not follow testing, the poster "Process System is not responding" Close or Wait is quite annoying.
Click to expand...
Click to collapse
Same here, Please a solution, iit is a good project, thanks
Thanks for your great work! I will test and feedback the info about NFC Card Emulation.
@codeworkx Feedback:NFC works(always auto close itself),but NFC-SIM based CardEmulation does not work.IR works. Thank you!
That's good news. For Pro3, thank you for your contribution.
Great work. GCam mod works fine, phone runs smoothy.
experimental LineageOS 16.0(Pie) for LeEco Le Pro3
Thank you very much, but my device lepro3 x720 after brushing the twrp 3.2.3 on the post, brush lineage os 16 prompt "failed to update image updater error: 7"
Thanks for your work!
@codeworkx thank you for all your great work on this device.
---------- Post added at 10:14 AM ---------- Previous post was at 10:12 AM ----------
ToBeAnt said:
Thank you very much, but my device lepro3 x720 after brushing the twrp 3.2.3 on the post, brush lineage os 16 prompt "failed to update image updater error: 7"
Click to expand...
Click to collapse
Did you flashed this TWRP before flashing LOS 16.0? If not do so.
https://forum.xda-developers.com/le-pro3/development/recovery-twrp-3-x-p-codeworkx-t3844528
will test for further feedback thanks for the great work
ZenitoSS said:
Great work. GCam mod works fine, phone runs smoothy.
Click to expand...
Click to collapse
So the NFC works for you? I saw your message in the morning that it does not work, but you edited it later.
@codeworkx Thanks a lot to you and everyone contributing. Just wanted to let you know the link in the OP is wrong (https://sourceforge.net/projects/lineageos-on-leeco/files/lineage-15.1/ -> https://sourceforge.net/projects/lineageos-on-leeco/files/lineage-16.0/).
neonncz said:
So the NFC works for you? I saw your message in the morning that it does not work, but you edited it later.
Click to expand...
Click to collapse
Yes, it works, but little bit laggy.
Nice Rom installed it and works wonderfull i only cant reg a fingerprint it is loading and then there is coming APP is not responsable.
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.
*
*/
MoKee OpenSource is based on the Google AOSP. We update our source code frequently to keep up with the latest development, and not forgetting to merge in special features of our own at the same time.
A small group of people from around the world who are interested in Android launched this project on the 12th of December 2012, and is committed to make this ROM better and better. Like most contributors of open source projects (Omni, CyanogenMod, Slim AOSPA etc), we are doing all these in our free time as our passion...
Since this project is open source, anyone interested can participate in the development (maintain new devices, contribute code etc). Newcomers are always welcomed!
Read here for developer application; with this, you can host your unofficial MoKee builds on our server!
Important information:
This thread is for official MoKee builds for Huawei C8817D, C8817E, G620S, G621, Che1_CL10, Che1_CL20, Che1_L04. The following will not be supported here:
Custom kernels
Mods
Xposed
We don't support Xposed and any logcat which includes a Xposed module will be ignored. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files
Supported device:
C8817D
C8817E
G620S-UL00
G620S-L01/L02/L03
G621-TL00
Che1_CL10
Che1_CL20
Che1_L04
Baseband requirement:
If you can't hang up, install this baseband via TWRP and it should be solved.
Known bugs:
Some minor bugs
Installation:
First time flashing MoKee 9.1 on your device, or coming from another ROM?
Download the zip(s)
Install a compatible Recovery, e.g., my TWRP: http://forum.xda-developers.com/android/development/recovery-twrp-3-0-0-0-touch-recovery-t3309504
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash MoKee
Optional: Install the Google Apps addon package
Reboot
Source code:
https://github.com/mokee
Download:
http://rom.mk/?device=cherry
http://rom.mk/?device=che10 (Che1_CL10)
Credits:
MoKee Developers: https://github.com/orgs/MoKee/members
Code Aurora Forum
LineageOS
AOSP
Slim Roms
OmniROM
@Blefish We won't have the usable nougat port without his efforts!
@paranoia_gu Add Honor 4x support
XDA:DevDB Information
MoKee, ROM for the Honor 4x
Contributors
dianlujitao
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
Version Information
Status: Nightly
Created 2019-05-15
Last Updated 2019-05-14
Thank dev.
Nice job! I'm going to have a try!
xingyunjohn1 said:
Nice job! I'm going to have a try!
Click to expand...
Click to collapse
It is fine!Nice job!
Very nice. I try to install the weather but API Code for openweathermaps it is not valid. And for the Google weather there is Google App missing (which cannot be installed on this phone) .Any idea ?
Suddenly weather appeared. Perfect !!! API from homepage open weather works.
kharuba said:
Suddenly weather appeared. Perfect !!! API from homepage open weather works.
Click to expand...
Click to collapse
Great! - api code sometimes takes hours to be validated initially. PW.
pndwal said:
Great! - api code sometimes takes hours to be validated initially. PW.
Click to expand...
Click to collapse
We can have a personal API code from the mentioned website. It's easy to get one.
xingyunjohn1 said:
We can have a personal API code from the mentioned website. It's easy to get one.
Click to expand...
Click to collapse
True. But if you enter api key manually or copy and paste it, it can still take minutes or hours to validate and activate. PW
Standby is better if not flashed to Android Go. With lowram enabler standby time decreased. Maybe not optimized for Android 9. Works great this ROM !!!
kharuba said:
Standby is better if not flashed to Android Go. With lowram enabler standby time decreased. Maybe not optimized for Android 9. Works great this ROM !!!
Click to expand...
Click to collapse
Thanks for pointer!
It may be battery / increased activity is the tradeoff for responsiveness with low-ram set. Just guessing...
Did you notice improvement in responsiveness with low-ram flagged? PW
File sharing via bluetoooth?
Hello community!
First of all thanks @dianlujitao for this ROM - I have to say it is faster than expected on this old device!
One issue I came across is: When I try sharing a file (e.g. a picture) with another already paired device via bluetooth I do not get the bluetooth selection in the pop-up? Also pairing itself does not seem to be very stable. Did anyone else observe that as well?
Bro it's still getting pie support. We're thankful for the devs. i hope 10 also works this way
Can someone please tell me about unlock bootloader of Honor(che1-L04) I want to flash custom Rom (Mokee 9.0)
S_T_A_R said:
Can someone please tell me about unlock bootloader of Honor(che1-L04) I want to flash custom Rom (Mokee 9.0)
Click to expand...
Click to collapse
Search 'unlocking bootloader' in this thread. Hope it helps. PW
https://forum.xda-developers.com/ho...-lineageos-14-1-huawei-g620s-honor-4-t3547682
can this ROM be installed on ascend g760-L01 (msm8916)?
ananiaanania said:
can this ROM be installed on ascend g760-L01 (msm8916)?
Click to expand...
Click to collapse
I have same question!
Hi
I guess this ROM does NOT support CHe2-L11 Honor 4X (Kirin 620 CPU), right?
Best,
-a-