Related
{
"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"
}
Disclaimer: OctOs is a WIP. It has been evaluated as being stable, and is suitable for daily use in most cases. While it may be considered stable, there may be unknown bugs. The development team is not responsible for any damage to your device or your information.
Click to expand...
Click to collapse
Team OctOs presents Oct-N.
We maintain a current release record and change-log on our website: http://www.teamoctos.com
We have Gapps here.
http://opengapps.org
***USE Gapps of your choosing, we prefer Open Gapps***
- Please Do Not Mirror our files without talking to us. We can do that ourselves should we desire to. -
Feature List
Substratum rootless theme engine support (must install Substratum from play store)
Tentacles settings!
Pixel Launcher Included
OmniSwitch
Power menu options
Screenshot
Screen record
DPI settings
Status bar time and date options
Status bar network traffic indicator
Status bar notification settings
Quick tile settings
Volume button playback control
Volume button wake
DUI (fling, pulse, smartbar)
Screen record
And much more!!!!
Click to expand...
Click to collapse
Frequently Asked Questions
Q: Is this Android 7 (Nougat)?
A: Yes, this is Android 7.1.2
Q: What code is Oct-N based on?
A: This version of Oct-N is based on LineageOS 14.1
Q: Why isn't there XYZ feature?
A: Shoot us a Suggestion if you want to see something added. While we are not going to promise to implement, we will always look into it
Q: But all the others have..
A: ROM developers, build something they want to use. The ROM developer that includes something they won't run implies less than 100% effort to ensure it does work. As a team, we have similar goals and objectives. If XYZ ROM has a feature you want, and we don't include (or don't want to include), feel free to use XYZ ROM, or build your own custom version of Oct-N.
Q: What about root?
A: Root is removed by default (user will be able to flash which ever root zip they want)
Bugs:
Bugs happen. Our testers are very good at breaking things, but no where near as good as the rest of the Android public. In order to investigate and fix issues, we need the help of the users who are going to report them. The Android OS has many nifty features to help us in this, but only if we can engage the user to assist us.
Logs, Logcat, and the Android Debugging Bridge (ADB)
Like any other OS, Android has multiple log files that are generated and record the goings-on of the system. As a user, you have two basic ways to view and pull these to send to us. Without the information in the logfiles, there simply is not a whole lot of information to go on.
Log file APKs
Team OctOs recommends SysLog from the Android Market. This application will allow you to selectively pick any (or all) of the system logs, compress them into a .ZIP file, and allow you to save, email, move to your Copy/DropBox/Cloud Storage account, etc.
ADB Logcat
The Android Debugging Bridge (ADB) is a powerful tool available from Google as part of the Android Software Development Kit (SDK). Used for many things, being able to selectively see, in real-time, what your device is doing cannot be downplayed. While there is more setup involved, if you are doing consistent ROM flashing, you really should invest the time to get setup properly to do it.
ADB Logcat tutorial here: How to create a logcat log
Basic Instructions:
Download ROM .zip file and MD5 file, and grab your favorite Open Gapps package http://opengapps.org
Reboot to Recovery (Note: Use Reboot to Recovery from Power Menu, Hardware-based boot to recovery, or adb reboot recovery - ROM Manager or similar software is NOT supported)
--- TWRP is the ONLY recovery Team OctOs uses - We do not support flashing on CWM ---
The Oct-N ROM installation script will automatically wipe /system, /cache, and /dalvik-cache. There is no need to do these before or after flashing the ROM unless you are instructed to by your Gapps Provider. When dirty flashing weekly updates, you MUST reflash Gapps along with any other files, apps, custom mods or kernels etc.. (anything that resides in system partition)
Flash ROM, GApps and any additional .ZIP files
Reboot
Download
Download from Team-OctOS web site!
Change log
View change log on Team-OctOS web site!
The foundation of the Android OS is the fact that is it open-source. We have all code we use internally in the creation of Oct-N available on our GitHub repositories.
Unless otherwise specified, all Oct-N builds kernel souce can be found on github at Team-OctOS.
Team OctOs GitHub - http://www.github.com/Team-OctOs
Team OctOs Gerrit Review - http://www.teamoctos.com:8080
Team OctOs GPLv2 License - http://www.teamoctos.com/license/
Team OctOs Patreon Campaign - https://www.patreon.com/TOctOs
Donate to OctOS Development (PayPal)
Want To Build Your Own?
Check out the ReadMe on our GitHub for Instructions
Special thanks to
Our testers, without which, there would be no public releases for OctOs
We would also like to thank
AOSP
Open Gapps
LineageOS
Anyone else who has ever submitted Open-Source code
Click to expand...
Click to collapse
Follow Team-OctOS!
XDA:DevDB Information
Oct OS, ROM for the Xiaomi Mi 3
Contributors
aniket.lamba, manfromgta
Source Code: https://github.com/Team-OctOS
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: A custom recovery (TWRP preferrable),ROM and Gapps zip file,knowledge on how to flash zip files.
Based On: Lineage
Version Information
Status: Stable
Created 2015-12-26
Last Updated 2017-04-29
OctOS 6.0.1
Team OctOs presents Oct-M.
We maintain a current release record and change-log on our website: http://www.teamoctos.com
- Please Do Not Mirror our files without talking to us. We can do that ourselves should we desire to. -
Frequently Asked Questions
Q: Is this Android 6 (Marshmallow)?
A: Yes
Q: What code is Oct-M based on?
A: Starting with Oct-M, we've rebased OctOs on Aosp code.
Q: What happened to CM?
A: Octos was originally formed as an AOSP source rom. We have returned to those roots.
Q: Why isn't there XXXXXXX feature.
A: Shoot us a Suggestion if you want to see something added. While we are not going to promise to implement, we will always look into it
Q: But CM and all the others have..
A: ROM developers, including CM, build something they want to use. The ROM developer that includes something they won't run implies less than 100% effort to ensure it does work. As a team, we have similar goals and objectives. If XYZ ROM has a feature you want, and we don't include (or don't want to include), feel free to use XYZ ROM, or build your own custom version of Oct-M.
Q: Superuser or SuperSU?
A: Team OctOs uses SuperSU and is installed automatically.
Bugs:
Bugs happen. Our testers are very good at breaking things, but no where near as good as the rest of the Android public. In order to investigate and fix issues, we need the help of the users who are going to report them. The Android OS has many nifty features to help us in this, but only if we can engage the user to assist us.
Logs, Logcat, and the Android Debugging Bridge (ADB)
Like any other OS, Android has multiple log files that are generated and record the goings-on of the system. As a user, you have two basic ways to view and pull these to send to us. Without the information in the logfiles, there simply is not a whole lot of information to go on.
Log file APKs
Team OctOs recommends SysLog from the Android Market. This application will allow you to selectively pick any (or all) of the system logs, compress them into a .ZIP file, and allow you to save, email, move to your Copy/DropBox/Cloud Storage account, etc.
ADB Logcat
The Android Debugging Bridge (ADB) is a powerful tool available from Google as part of the Android Software Development Kit (SDK). Used for many things, being able to selectively see, in real-time, what your device is doing cannot be downplayed. While there is more setup involved, if you are doing consistent ROM flashing, you really should invest the time to get setup properly to do it.
ADB Logcat tutorial here: How to create a logcat log
Basic Instructions:
Download ROM .zip file, and grab your favourite gapps package
Reboot to Recovery (Note: Use Reboot to Recovery from Power Menu, Hardware-based boot to recovery, or adb reboot recovery - ROM Manager or similar software is NOT supported)
--- TWRP is the ONLY recovery Team OctOs uses - We do not support flashing on CWM ---
Factory Reset from TWRP
Flash ROM and GApps .ZIP files
Reboot
* Weekly Builds
* Release Builds
* Gapps 6.0 Mini
The Oct-M ROM installation script will automatically wipe /system, /cache, and /data/dalvik-cache. There is no need to do these before or after flashing the ROM unless you are instructed to by your GApps Provider
The foundation of the Android OS is the fact that is it open-source. We have all code we use internally in the creation of Oct-M available on our GitHub repositories.
Unless otherwise specified, all Oct-M builds use the device's stock kernel.
Team OctOs GitHub - http://www.github.com/Team-OctOs
Team OctOs Gerrit Review - http://www.teamoctos.com:8080
Team OctOs GPLv2 License - http://www.teamoctos.com/license/
Team OctOs Patreon Campaign - https://www.patreon.com/TOctOs
A Special thanks to @audahadi for his device sources.
Want To Build Your Own?
Check out the ReadMe on our GitHub for Instructions
Follow Us at the various websites below!
Kernel source - https://github.com/kernel-hut/android_kernel_xiaomi_cancro
Device - https://github.com/audahadi/android_device_xiaomi_cancro
Vendor - https://github.com/audahadi/proprietary_vendor_xiaomi
Bugs/Issues
[*]You tell me
Some ss
Rom is great for now.. all basic things works .. that is for now xD
Trying this rom for a few hours, I observed the followings:
The rom is smooth and rather fast.
Almost everything works properly.
Xposed works on this rom without any problem.
Battery life is reasonable.
Thank you so much, aniket.lamba.:good:
@aniket.lamba hi bro, I have a query.
But before that thanks a ton for the wonderful work you have done with this ROM :thumbup: Your Metallium ROM was my favorite LP ROM and I used it as my daily driver from the time it got released and never had to look at any other ROM after that as it was rock stable and super fast
Now for the query, was going through a post by John Cannon Jr on TeamOct G+ community where he mentioned that for non-nexus devices CM will be the base going forward. So for cancro-marshmallow will you continue the AOSP base or will change the base to CM in future? Asking this as there are lot of CM based ROMs available for cancro-marshmallow but not many AOSP based.
Cheers
rajib4 said:
@aniket.lamba hi bro, I have a query.
But before that thanks a ton for the wonderful work you have done with this ROM :thumbup: Your Metallium ROM was my favorite LP ROM and I used it as my daily driver from the time it got released and never had to look at any other ROM after that as it was rock stable and super fast
Now for the query, was going through a post by John Cannon Jr on TeamOct G+ community where he mentioned that for non-nexus devices CM will be the base going forward. So for cancro-marshmallow will you continue the AOSP base or will change the base to CM in future? Asking this as there are lot of CM based ROMs available for cancro-marshmallow but not many AOSP based.
Cheers
Click to expand...
Click to collapse
Initially it'll be CM based.As the ROM development progresses further,we might shift to the AOSP base.
marko94 said:
Some ss
Rom is great for now.. all basic things works .. that is for now xD
Click to expand...
Click to collapse
Are there CM themes? The app drawer shows it is, ur settings screenshot (might have missed), doesn't show that. Also the ROM is AOSP based.
No slow charging bug?
---------- Post added at 03:56 PM ---------- Previous post was at 03:48 PM ----------
aniket.lamba said:
Initially it'll be CM based.As the ROM development progresses further,we might shift to the AOSP base.
Click to expand...
Click to collapse
"might shift", does that mean it is CM based right now. The FAQ question and the 'based on' posted on the op shows AOSP atleast.
Me_Ashish_ said:
Are there CM themes? The app drawer shows it is, ur settings screenshot (might have missed), doesn't show that. Also the ROM is AOSP based.
No slow charging bug?
---------- Post added at 03:56 PM ---------- Previous post was at 03:48 PM ----------
"might shift", does that mean it is CM based right now. The FAQ question and the 'based on' posted on the op shows AOSP atleast.
Click to expand...
Click to collapse
For the initial stage it is CM based,this build which I've posted is an initial build (considering it still has issues) so we chose CM base as we draw more support of non-nexus devices,we'll shift the base to AOSP.I'll change the thread title so the users won't have a problem figuring out.
I have a doubt...does ambient display has a BUG or it's not working just for me.
nirjharmistry said:
I have a doubt...does ambient display has a BUG or it's not working just for me.
Click to expand...
Click to collapse
Never heard of someone who got Ambient Display working anytime. It just shows the, doesn't supports though.
Is it only me or the ROM doesn't support extended partition?
I tried flashing twice, but after installing GAPPS. Xposed doesn't get installed due to no space.
Also the maximum CPU frequency doesn't change at all
Me_Ashish_ said:
Is it only me or the ROM doesn't support extended partition?
I tried flashing twice, but after installing GAPPS. Xposed doesn't get installed due to no space.
Also the maximum CPU frequency doesn't change at all
Click to expand...
Click to collapse
Apparently you're not on extended partition. Your system is only 660mb instead of 1.2gb which means you're on stock partition. Did u flash MIUI recently? It might've reverted your partition to stock.
Sent from my MI 4 using Tapatalk
diongdyh said:
Apparently you're not on extended partition. Your system is only 660mb instead of 1.2gb which means you're on stock partition. Did u flash MIUI recently? It might've reverted your partition to stock.
Sent from my MI 4 using Tapatalk
Click to expand...
Click to collapse
That's not the case. Some ROMs work at stock even though you are on extended partition. Though I knew it's not my phone I still anyways re flashed extended partition ZIP leading in same result.
BTW installing MIUI or any other ROM via recovery doesn't make you loose ur extended partition.
Me_Ashish_ said:
That's not the case. Some ROMs work at stock even though you are on extended partition. Though I knew it's not my phone I still anyways re flashed extended partition ZIP leading in same result.
BTW installing MIUI or any other ROM via recovery doesn't make you loose ur extended partition.
Click to expand...
Click to collapse
If you've flashed the extended partition and it's still in 660mb means that you've failed. I know only flashing miui through fastboot gets you to stock partition. The point is you're on stock partition.
Sent from my MI 4 using Tapatalk
diongdyh said:
If you've flashed the extended partition and it's still in 660mb means that you've failed. I know only flashing miui through fastboot gets you to stock partition. The point is you're on stock partition.
Sent from my MI 4 using Tapatalk
Click to expand...
Click to collapse
Nope. I'm on extended partition since months. You haven't come across that kind of ROMs I mentioned it looks like. And I can't remember the exact name of few ROMs which had that issue right now.
And for the record after that ROM I installed CM12.1 without installing any repartition ZIPs and I had a 1.2G system size.
Me_Ashish_ said:
Nope. I'm on extended partition since months. You haven't come across that kind of ROMs I mentioned it looks like. And I can't remember the exact name of few ROMs which had that issue right now.
And for the record after that ROM I installed CM12.1 without installing any repartition ZIPs and I had a 1.2G system size.
Click to expand...
Click to collapse
Ooh did u mean that after flashing this ROM your system partition got reset to default (660mb)?
Cuz in the screenshot you attached it shows that you only have 660mb.
Sent from my MI 4 using Tapatalk
Me_Ashish_ said:
Nope. I'm on extended partition since months. You haven't come across that kind of ROMs I mentioned it looks like. And I can't remember the exact name of few ROMs which had that issue right now.
And for the record after that ROM I installed CM12.1 without installing any repartition ZIPs and I had a 1.2G system size.
Click to expand...
Click to collapse
yeah,same happened to me.. I am also on extended , but after flashing this rom , my partition go back to stock.. easy fix for that, go to recovery, backup rom, restore rom,reboot and now all is fine xD
marko94 said:
yeah,same happened to me.. I am also on extended , but after flashing this rom , my partition go back to stock.. easy fix for that, go to recovery, backup rom, restore rom,reboot and now all is fine xD
Click to expand...
Click to collapse
I too faced the same issue and with other ROMs too. There is an easy fix. If you are using twrp, go to Wipe->advanced Wipe Select "System" and click "repair or Change File system" below. Then Select "Resize". The issue will now be fixed.
If you are flashing ROM and Gapps, do the above step after flashing ROM before installing the Gapps.
Is this rom cm based or aosp based?
Sorry to tell this, but KudKernel development on j2lte family has been abandoned due to fact that I couldn't give make any of my current builds to boot and I don't have any device to test. Thanks for your support all. Hope we could meet again on another device development. :fingers-crossed:
Introduction
KudKernel is a custom kernel that built straight from the official sources with slight modifications to keep it as stable as stock, but with some additional features that won't impact the stability overall.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this KERNEL
* before flashing it! YOU are choosing to make these modifications, and if
* you point your finger at me for messing up your device, I will laugh at you.
*/
Kernel features
Compiled from J200FXXU1AOI6 kernel sources
Compiled using UberTC 4.9.4 with -Ofast and -fgraphite flag for fast and smooth experience
Using AnyKernel2 script for unified and easy installation (@osm0sis)
Kernel.org version 3.10.22
Kernel is compressed using LZMA
SELinux is set to permissive by default
ADB full root access
Enabled all CPU governors
Disabled root restrictions (enjoy fully rooted experience!)
And more features to come soon...
Supported devices
Thanks to AnyKernel2 script, all devices on j2lte family running TouchWiz 5.1.1 are able to run KudKernel.
Downloads
All downloads are located in multiple providers, so in case there is a problem on one provider, you could download KudKernel from the other one.
All releases on OneDrive
All releases on Google Drive
Installation instructions
Make sure you've unlocked your bootloader via this simple instruction and have your stock boot.img backed up (so you could revert back to stock kernel at any time) before proceeding.
Make sure you've the latest version of TWRP.
Reboot to Recovery mode by combination of Power+Home+Vol(+) buttons.
Select Install from TWRP screen.
Select KudKernel .zip file.
Swipe button to install. (you could enable zip signature verification if needed)
Finally wipe cache and dalvik.
Reboot to system.
Kernel source
You could use my source for studying purposes before you develop your own kernel project. Rebuilding any kernel with my sources is strictly prohibited. Kernel source is here.
Special thanks
Samsung Open Source Resource Center Team
UBER TOOLCHAINS - Their powerful toolchain!
@osm0sis - AnyKernel2 script - XDA thread
@5mohsen5 - Testing my first undocumented test build and J200F stock kernel
@zephy09 - J200GU stock kernel
@Rachav2 - J200M stock kernel
Update logs
Last release:
r6 [17-05-2016]
Reworked from original Samsung's source
Source bring up to GitHub
Switched kernel compression to LZMA
Enabled all CPU governors
Disabled root restrictions
Revert all AnyKernel2 script changes
Older releases:
r5 [05-05-2016]
I announced that KudTW is renamed to KudKernel! Why? Because I don't want everyone misspell this kernel name as KudTV (this isn't a television channel lol)
Unified support for all j2lte variants using AnyKernel2 script by osm0sis
Compiled using J200FXXU1AOI6 kernel sources
Kernel is compressed with xz compression
Added all flags from the original unmodified sources
Added -fgraphite optimization flag
Added back ondemand CPU governor (no guarantee that it would work) (@zephy09's request)
Added default.prop patch to disable Secure Storage support (not tested)
Older releases (KudTW):
r4 [08-04-2016]
Kernel.org version 3.10.22
Compiled using UberTC 4.9.4
Added support for SM-J200M
Added some gcc optimizations from Intel's official documentation
r3.1 [27-03-2016]
Now comes only via .img file. It's easier than ever!
Added and set interactive governor as default
Removed ondemand governor (deprecated)
Added missing compilation flag
r3 [21-03-2016]
Kernel.org version 3.10.20
Added support for SM-J200GU
Revert back ramdisk compression to gzip
ondemand is now the default CPU governor (please check it via CPU-Z)
r2 [18-03-2016]
Compiled using UberTC 4.8 with -Ofast flag
Added support for SM-J200G
Ramdisk is compressed with xz compression
ADB full root access
Removed all CPU governors except performance and ondemand
r1 [12-03-2016]
First stable release.
Nothing changed from test release, only changed version tag.
test [11-03-2016] - Non-public release
Initial bringup for j2lte, only tested on J200F; thanks to @5mohsen5 for testing the test release!
..
..
krasCGQ said:
ROMs whose include KudTW as the default kernelReserved for now
Click to expand...
Click to collapse
tanx a lot bro [emoji106] [emoji106] [emoji106]
Sent from my SM-J200F using Tapatalk
First test build is up!
Update log:
Kernel.org version 3.10.20
Compiled using UberTC 4.8
Enjoy the first test build~~
Edit: J200G/GU/Y users, anyone?
Sent from my ASUS_Z00AD
thanks for the making stable kernel. im waiting for this good kernel for us (J2 users.) i think more will come.
slowly slowly we greeting Development support for our Device,
thanks master,
will this kernel work on J200G?
my j2lte status
full rooted (SuperSU)
Bootloader OEM (Unlocked)
latest Recovery Installed (TWRP v3)
RaKesh said:
slowly slowly we greeting Development support for our Device,
thanks master,
will this kernel work on J200G?
my j2lte status
full rooted (SuperSU)
Bootloader OEM (Unlocked)
latest Recovery Installed (TWRP v3)
Click to expand...
Click to collapse
I don't know. Just test it and report. If it's not working, give me your stock boot.img and I will make one for you.
Edit: And also, extend support to all J2 LTE families!
Edit #2:
Okay, so he sent me a PM with a Google Drive link (that unfortunately also contains latest Odin and stock recovery altogether!). I'll compile a J200G test build tommorow morning UTC+8. Stay tuned.
Sent from my ASUS_Z00AD
@RaKesh
A test build for J200G is now available. Check test builds link on OP. It contains everything on r1.
{
"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"
}
Flashed Successfully using TWRP
Terima kasih bro :highfive:
I 'm a little worried about the warnings Knox
Is this a safe file ?? [emoji29] [emoji18]
Sent from my SM-J200F using Tapatalk
5mohsen5 said:
I 'm a little worried about the warnings Knox
Is this a safe file ?? [emoji29] [emoji18]
Sent from my SM-J200F using Tapatalk
Click to expand...
Click to collapse
It's safe to ignore. Samsung are just trying to scare everyone...
If I can, might be I'd develop a script to get rid of Samsung bloats + Knox xD
Sent from my ASUS_Z00AD
The kernel has a bug
when I restart my phone
All wifi saved pass will be removed
Sent from my SM-J200F using Tapatalk
krasCGQ said:
@RaKesh
A test build for J200G is now available. Check test builds link on OP. It contains everything on r1.
Click to expand...
Click to collapse
i think found a problem about wi-fi. if you restart the phone (or close the wi-fi) you need to login wi-fi again. thanks again:good:
5mohsen5 said:
The kernel has a bug
when I restart my phone
All wifi saved pass will be removed
Sent from my SM-J200F using Tapatalk
Click to expand...
Click to collapse
NeverDeadTR said:
i think found a problem about wi-fi. if you restart the phone (or close the wi-fi) you need to login wi-fi again. thanks again:good:
Click to expand...
Click to collapse
Could you both try t1 test build and report back?
I'm thinking that toolchain caused this issue (I compiled r1 with GCC 4.7 instead of 4.8 ). I compiled t1 with UberTC 4.8.
Sent from my ASUS_Z00AD
krasCGQ said:
Could you both try t1 test build and report back?
I'm thinking that toolchain caused this issue (I compiled r1 with GCC 4.7 instead of 4.8 ). I compiled t1 with UberTC 4.8.
Sent from my ASUS_Z00AD
Click to expand...
Click to collapse
im tested but it doesnt work. still same.
krasCGQ said:
Could you both try t1 test build and report back?
I'm thinking that toolchain caused this issue (I compiled r1 with GCC 4.7 instead of 4.8 ). I compiled t1 with UberTC 4.8.
Sent from my ASUS_Z00AD
Click to expand...
Click to collapse
In the test version, my phone was turned off every few minutes.
---------- Post added at 02:13 AM ---------- Previous post was at 02:06 AM ----------
I do not understand Samsung policies .
Why a low-end phone should be at this level of security ?
NeverDeadTR said:
im tested but it doesnt work. still same.
Click to expand...
Click to collapse
5mohsen5 said:
In the test version, my phone was turned off every few minutes.
---------- Post added at 02:13 AM ---------- Previous post was at 02:06 AM ----------
I do not understand Samsung policies .
Why a low-end phone should be at this level of security ?
Click to expand...
Click to collapse
Damn, I'd stop patching this stupid sources...
I've upgraded to 3.10.24, but I faced building errors on ipv4 and ipv6 -_-
I'll keep on releasing test builds with updated kernel patches, but stable release will keep the sources as it should.
Is this build.prop editing method work?
Code:
ro.securestorage.support=true -> ro.securestorage.support=false
Edit: This is why I never want to produce a kernel from Samsung sources directly...
Sent from my ASUS_Z00AD
I think it would be better just delete the selinux option .
but this kernel has another changes .
{
"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"
}
Disclaimer: OctOs is a WIP. It has been evaluated as being stable, and is suitable for daily use in most cases. While it may be considered stable, there may be unknown bugs. The development team is not responsible for any damage to your device or your information.
Click to expand...
Click to collapse
Team OctOs presents Oct-N.
We maintain a current release record and change-log on our website: http://www.teamoctos.com
We have Gapps here.
http://opengapps.org
***USE Gapps of your choosing, we prefer Open Gapps***
- Please Do Not Mirror our files without talking to us. We can do that ourselves should we desire to. -
Feature List
Substratum rootless theme engine support (must install Substratum from play store)
Tentacles settings!
Pixel Launcher Included
OmniSwitch
Power menu options
Screenshot
Screen record
DPI settings
Status bar time and date options
Status bar network traffic indicator
Status bar notification settings
Quick tile settings
Volume button playback control
Volume button wake
DUI (fling, pulse, smartbar)
Screen record
And much more!!!!
Click to expand...
Click to collapse
Frequently Asked Questions
Q: Is this Android 7 (Nougat)?
A: Yes, this is Android 7.1.2
Q: What code is Oct-N based on?
A: This version of Oct-N is based on LineageOS 14.1
Q: Why isn't there XYZ feature?
A: Shoot us a Suggestion if you want to see something added. While we are not going to promise to implement, we will always look into it
Q: But all the others have..
A: ROM developers, build something they want to use. The ROM developer that includes something they won't run implies less than 100% effort to ensure it does work. As a team, we have similar goals and objectives. If XYZ ROM has a feature you want, and we don't include (or don't want to include), feel free to use XYZ ROM, or build your own custom version of Oct-N.
Q: What about root?
A: Root is removed by default (user will be able to flash which ever root zip they want)
Bugs:
Bugs happen. Our testers are very good at breaking things, but no where near as good as the rest of the Android public. In order to investigate and fix issues, we need the help of the users who are going to report them. The Android OS has many nifty features to help us in this, but only if we can engage the user to assist us.
Logs, Logcat, and the Android Debugging Bridge (ADB)
Like any other OS, Android has multiple log files that are generated and record the goings-on of the system. As a user, you have two basic ways to view and pull these to send to us. Without the information in the logfiles, there simply is not a whole lot of information to go on.
Log file APKs
Team OctOs recommends SysLog from the Android Market. This application will allow you to selectively pick any (or all) of the system logs, compress them into a .ZIP file, and allow you to save, email, move to your Copy/DropBox/Cloud Storage account, etc.
ADB Logcat
The Android Debugging Bridge (ADB) is a powerful tool available from Google as part of the Android Software Development Kit (SDK). Used for many things, being able to selectively see, in real-time, what your device is doing cannot be downplayed. While there is more setup involved, if you are doing consistent ROM flashing, you really should invest the time to get setup properly to do it.
ADB Logcat tutorial here: How to create a logcat log
Basic Instructions:
Download ROM .zip file and MD5 file, and grab your favorite Open Gapps package http://opengapps.org
Reboot to Recovery (Note: Use Reboot to Recovery from Power Menu, Hardware-based boot to recovery, or adb reboot recovery - ROM Manager or similar software is NOT supported)
--- TWRP is the ONLY recovery Team OctOs uses - We do not support flashing on CWM ---
The Oct-N ROM installation script will automatically wipe /system, /cache, and /dalvik-cache. There is no need to do these before or after flashing the ROM unless you are instructed to by your Gapps Provider. When dirty flashing weekly updates, you MUST reflash Gapps along with any other files, apps, custom mods or kernels etc.. (anything that resides in system partition)
Flash ROM, GApps and any additional .ZIP files
Reboot
Download
Download from Team-OctOS web site!
Change log
View change log on Team-OctOS web site!
The foundation of the Android OS is the fact that is it open-source. We have all code we use internally in the creation of Oct-N available on our GitHub repositories.
Unless otherwise specified, all Oct-N builds kernel souce can be found on github at Team-OctOS.
Team OctOs GitHub - http://www.github.com/Team-OctOs
Team OctOs Gerrit Review - http://www.teamoctos.com:8080
Team OctOs GPLv2 License - http://www.teamoctos.com/license/
Team OctOs Patreon Campaign - https://www.patreon.com/TOctOs
Donate to OctOS Development (PayPal)
Want To Build Your Own?
Check out the ReadMe on our GitHub for Instructions
Special thanks to
Our testers, without which, there would be no public releases for OctOs
We would also like to thank
AOSP
Open Gapps
LineageOS
Anyone else who has ever submitted Open-Source code
Click to expand...
Click to collapse
Follow Team-OctOS!
XDA:DevDB Information
[ROM][7.1.2]Team OctOS Oct-N, ROM for all devices (see above for details)
Contributors
NATO66613, NATO66613, manfromgta
Source Code: https://github.com/Team-OctOS
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: OCTO-OS
Version Information
Status: Stable
Created 2017-02-08
Last Updated 2017-05-14
reserved
ROM is only for HUAWEI Y500 devices
ROM is coming out on 10.02.2017
@NATO66613
Device sources ? anyway wifi fix no required?
ZjemCiKolege said:
@NATO66613
Device sources ? anyway wifi fix no required?
Click to expand...
Click to collapse
On team octo device github. And no rom will be released on Friday with weakly build
NATO66613 said:
Team OctOs presents Oct-N.
We maintain a current release record and change-log on our website: http://www.teamoctos.com
We have Gapps here.
http://opengapps.org
***USE Gapps of your choosing, we prefer Open Gapps***
- Please Do Not Mirror our files without talking to us. We can do that ourselves should we desire to. -
Feature List
Frequently Asked Questions
Q: Is this Android 7 (Nougat)?
A: Yes, this is Android 7.1.1
Q: What code is Oct-N based on?
A: This version of Oct-N is based on LineageOS 14.1
Q: Why isn't there XYZ feature?
A: Shoot us a Suggestion if you want to see something added. While we are not going to promise to implement, we will always look into it
Q: But all the others have..
A: ROM developers, build something they want to use. The ROM developer that includes something they won't run implies less than 100% effort to ensure it does work. As a team, we have similar goals and objectives. If XYZ ROM has a feature you want, and we don't include (or don't want to include), feel free to use XYZ ROM, or build your own custom version of Oct-M.
Q: What about root?
A: Actually this version of OCT-N uses embedded root acccess which can be enabled in development settings.
Bugs:
Bugs happen. Our testers are very good at breaking things, but no where near as good as the rest of the Android public. In order to investigate and fix issues, we need the help of the users who are going to report them. The Android OS has many nifty features to help us in this, but only if we can engage the user to assist us.
Logs, Logcat, and the Android Debugging Bridge (ADB)
Like any other OS, Android has multiple log files that are generated and record the goings-on of the system. As a user, you have two basic ways to view and pull these to send to us. Without the information in the logfiles, there simply is not a whole lot of information to go on.
Log file APKs
Team OctOs recommends SysLog from the Android Market. This application will allow you to selectively pick any (or all) of the system logs, compress them into a .ZIP file, and allow you to save, email, move to your Copy/DropBox/Cloud Storage account, etc.
ADB Logcat
The Android Debugging Bridge (ADB) is a powerful tool available from Google as part of the Android Software Development Kit (SDK). Used for many things, being able to selectively see, in real-time, what your device is doing cannot be downplayed. While there is more setup involved, if you are doing consistent ROM flashing, you really should invest the time to get setup properly to do it.
ADB Logcat tutorial here: How to create a logcat log
Basic Instructions:
Download ROM .zip file and MD5 file, and grab your favorite Open Gapps package http://opengapps.org
Reboot to Recovery (Note: Use Reboot to Recovery from Power Menu, Hardware-based boot to recovery, or adb reboot recovery - ROM Manager or similar software is NOT supported)
--- TWRP is the ONLY recovery Team OctOs uses - We do not support flashing on CWM ---
Factory Reset from TWRP
Flash ROM and GApps .ZIP files
Reboot
Download
Download from Team-OctOS web site!
Change log
View change log on Team-OctOS web site!
The foundation of the Android OS is the fact that is it open-source. We have all code we use internally in the creation of Oct-N available on our GitHub repositories.
Unless otherwise specified, all Oct-N builds kernel souce can be found on github at Team-OctOS.
Team OctOs GitHub - http://www.github.com/Team-OctOs
Team OctOs Gerrit Review - http://www.teamoctos.com:8080
Team OctOs GPLv2 License - http://www.teamoctos.com/license/
Team OctOs Patreon Campaign - https://www.patreon.com/TOctOs
Paypal - https://www.paypal.com/us/cgi-bin/we...37e57608011f58
Want To Build Your Own?
Check out the ReadMe on our GitHub for Instructions
Follow Team-OctOS!
XDA:DevDB Information
[ROM][7.1.1]Team OctOS Oct-N, ROM for all devices (see above for details)
Contributors
NATO66613, NATO66613
Source Code: https://github.com/Team-OctOS
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: OCTO-OS
Version Information
Status: Stable
Created 2017-02-08
Last Updated 2017-02-08
Click to expand...
Click to collapse
Sounds good! Will There be Nightly or OTA Updates too?
Gesendet von meinem Y550-L01 mit Tapatalk
Felix__L-01 said:
Sounds good! Will There be Nightly or OTA Updates too?
Gesendet von meinem Y550-L01 mit Tapatalk
Click to expand...
Click to collapse
Nigtly now are weakly
Which file Rom should be download from web site for Huawei Y550-L01
Nice
Bad news rom will be delayed. Since i encountered unexpected issues with system.
NATO66613 said:
Bad news rom will be delayed. Since i encountered unexpected issues with system.
Click to expand...
Click to collapse
:c
Gesendet von meinem Y550-L01 mit Tapatalk
Weekly 02/11
Weekly is up on site
Download: https://www.teamoctos.com/download/oct-14.1/Y550/OCT-N-WEEKLY-20170211-2137-Y550.zip
Md5sum: https://www.teamoctos.com/download/oct-14.1/Y550/OCT-N-WEEKLY-20170211-2137-Y550.zip.md5sum
Changelog: https://www.teamoctos.com/download/oct-14.1/Y550/OCT-N-WEEKLY-20170211-2137-Y550-changelog.log
manfromgta said:
Weekly is up on site
Download: https://www.teamoctos.com/download/oct-14.1/Y550/OCT-N-WEEKLY-20170211-2137-Y550.zip
Md5sum: https://www.teamoctos.com/download/oct-14.1/Y550/OCT-N-WEEKLY-20170211-2137-Y550.zip.md5sum
Changelog: https://www.teamoctos.com/download/oct-14.1/Y550/OCT-N-WEEKLY-20170211-2137-Y550-changelog.log
Click to expand...
Click to collapse
Big thanks!! I am Test It now
Gesendet von meinem Y550-L01 mit Tapatalk
---------- Post added at 02:17 PM ---------- Previous post was at 01:32 PM ----------
manfromgta said:
Weekly is up on site
Download: https://www.teamoctos.com/download/oct-14.1/Y550/OCT-N-WEEKLY-20170211-2137-Y550.zip
Md5sum: https://www.teamoctos.com/download/oct-14.1/Y550/OCT-N-WEEKLY-20170211-2137-Y550.zip.md5sum
Changelog: https://www.teamoctos.com/download/oct-14.1/Y550/OCT-N-WEEKLY-20170211-2137-Y550-changelog.log
Click to expand...
Click to collapse
Hey. I found one bug. In file manager I can´t access to sdcard it says i need root access but normally you dont need them to access sdcard. i granted file manager root access but I still cant access to sdcard via file manager
but when i use other file manager from play store everything works.
Felix__L-01 said:
Big thanks!! I am Test It now
Gesendet von meinem Y550-L01 mit Tapatalk
---------- Post added at 02:17 PM ---------- Previous post was at 01:32 PM ----------
Hey. I found one bug. In file manager I can´t access to sdcard it says i need root access but normally you dont need them to access sdcard. i granted file manager root access but I still cant access to sdcard via file manager
but when i use other file manager from play store everything works.
Click to expand...
Click to collapse
Its normaly and is CM/LineAge bug.
For people who have bootloop.
I downloaded File from this link:
http://r.srvtrck.com/v1/redirect?url...ink&ad_dt=link
Then i made a folder in the in my sdcard called dload an put this file which was downloaded in it.
then insert sdcard to phone.
then press home button, vol up and vol down button and phone will start into upgrade mode and will restore stock 4.4.4 firmware. then you have to flash recovery and modem again and then try again flashing OctOS. It should worked then it worked for me.
By the way at the update.APP file you have to see in which region you are living to see what build you have to download, simply google it.
Felix__L-01 said:
For people who have bootloop.
I downloaded File from this link:
http://r.srvtrck.com/v1/redirect?url...ink&ad_dt=link
Then i made a folder in the in my sdcard called dload an put this file which was downloaded in it.
then insert sdcard to phone.
then press home button, vol up and vol down button and phone will start into upgrade mode and will restore stock 4.4.4 firmware. then you have to flash recovery and modem again and then try again flashing OctOS. It should worked then it worked for me.
By the way at the update.APP file you have to see in which region you are living to see what build you have to download, simply google it.
Click to expand...
Click to collapse
For me no update.app work,i test in one month ago
But stock recovery cant flash it(logo oem error)
Simple fix for bootloop is unclean flash,flash rom without wipethen work fine.i tested it.
manfromgta said:
Weekly is up on site
Download: teamoctos download o...-2137-Y550.zip
Md5sum: teamoctos download o...550.zip.md5sum
Changelog: teamoctos download o...-changelog.log
Changelog:
Click to expand...
Click to collapse
Thanks.
On my Y550 L01:
Incoming calls do not dismiss
Outgoing calls do not hanging up
------
wifi ok
wifi hotspot ok
radio FM ok
mpisole said:
Incoming calls do not dismiss
Outgoing calls do not hanging up
Click to expand...
Click to collapse
( @NATO66613 ) no bug on my device,may you flashed a custom kernel or wrong modem...
LTE no work for me :/
{
"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"
}
AICP
Android Ice Cold Project
AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago (2012) and since then evolved into a mature ROM with the BEST community you can find!!!
Until Lollipop, the Rom has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM when it comes to hardware, drivers and some features.
With the rebrand of CM to LineageOS (LAOS) we are now actually LAOS based with some tweaks from AOSP.
If there are any bugs, either we will sort them out or the LAOS team will if it concerns their code base. This rom isn't LAOS supported, so no need to report errors or bugs to them!!
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. Hard & a lot.
*
*/
Feature list (rough Overview)
In the beginning we would like to thank:
LineageOS & CM (R.I.P.) team
Maxwen and the rest of the OmniRom team
DU team
SlimRoms team
Resurrection Remix team
Community
...
@LorD ClockaN
@zipsnet
@eyosen
@semdoc
@Drgravy
@Hashbang173
@SpiritCroc
@wartomato
@eboye
plus the rest of the crazy bunch that we call "team"
...
We are paying for servers that build nightlies/weeklies and everything that comes with it, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 12.1
Download link: http://dwnld.aicp-rom.com/?device=santoni
Full Changelog link: http://dwnld.aicp-rom.com/
Google Apps:
Beans gapps
Or
Open GApps (ARM or ARM64 7.1 pico or nano, depending on your phone's architecture)
Things Working:
WiFi
RIL
Camera
FPS
Mtp
VoLTE
You tell...
FAQ:]
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look in the OP to see, if your device is build on a nightly or weekly schedule.
Q. Does this ROM support custom kernels?
A. No. You can still use them (as long as they are LOS based), but discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter using them!
Q. Why doesn't this ROM support Xposed?
A. Xposed is a hack that is geared towards AOSP, custom ROM's modify the framework a lot, so Xposed can cause a ton of issues on custom ROM's. Now it might work for you, however it is not to be discussed in this thread, and you should refrain from posting bug reports.
Q. Alright, but I still want to flash Xposed, so which version do I need to install?
A. Xposed is not yet available for nougat (officialy), however there are unofficial versions. You will need to use the version arm64/arm for SDK 25.
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the install instructions in the first post...
Q. Can the builds be dirty flashed over each other?
A. Yes, however make a nandroid first as there is a chance of getting a bootloop or encountering bugs. Also bugs may only be reported on a clean flash.
Q. How do I dirty flash builds?
A. Wipe System, Cache and ART/Dalvik cache. Flash the ROM, your preferred root solution and reboot. Or you might just use the OTA app to preform that task for you.
Q. How do I flash kernel builds?
A1. Boot into TWRP and go to the install page in TWRP, in the bottom right corner select "install image", select the desired kernel, then select "boot", then swipe to flash, then go back to the install screen and install your root method again if you don't want to loose root, and then reboot.
A2. LOS based kernels sometimes come as a flashable ZIP file too. You can flash them together with a ROM update or separately. Go to the install page in TWRP, choose the kernel zip (or add it to the flash queue right after the ROM zip). Then add your root method to the queue, if you don't want to loose root. Now swipe to flash, clear Cache & ART/Dalvik cache and then reboot.
Using the ROM:
Q. How do I enable software buttons?
A. Settings -> Navigation -> Enable navigation bar. The bar can be configured separately in its settings.
Q I installed a bad theme and now I'm getting a bootloop, how do I fix it?
A In TWRP, flash the substratum rescue zip in the substratum folder on the internal storage.
Q I keep losing root with Magisk, how do I fix it?
A Check this out, if that doesn't work for you ask for help in this thread, read or ask in the Magisk thread on XDA or just flash Magisk again!
Q I'm having issues with WhatsApp, how do I fix it?
A Read this
Q. Do I need to provide a logcat if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat. (Note: Please just link the logcat from your GDrive, Dropbox, etc. and do not post the content here. Thanks.
Q. How do I get a logcat, what type should I get and more questions that can conveniently be answered by my pre-determined answer?
A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog
A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the root section in the AICP Extras menu.
The ROM should contain everything you need to enjoy Android Nougat. You don't need to install any Add-Ons, simply download the latest ROM, GApps, flash it and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM Zipfile.
It is STRONGLY recommended to fully wipe your device before flashing, and if possible avoid restoring system apps and system data with Titanium Backup as this can cause stability issues that are very hard to debug.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash:(Again: Don't do it if you don't know it!)
1. Download the ROM and GApps and transfer them to your device
2. Boot to recovery (TWRP recommended)
3. Wipe system, Cache, data and ART/Dalvik cache
4. Flash ROM Zipfile
5. Flash/Install GApps (optional, needed for e.g. Google Playstore to work)
6. Flash/Install the root solution of choice (optional)
7. Reboot to system
The ROM has GApps persistance in between dirty flashes, so you only have to flash them once!
The root solution should be flashed together with every OTA update (= ROM Update)!
Supported root solutions:Magisk v13.x
SuperSU - stable and beta available (Site by CCMT that took over the the marketing from chainfire)
SuperSU - direct download link for the latest SuperSU directly from the dev (chainfire)
Lineage SU-addon (check your needed version: 14.1 arm or arm64) -> the removal zip is available here too.
KERNEL:
The kernel in this ROM follows LAOS source with custom additions from AOSP.
PREREQUISITE FOR OTA:To be able to flash using the buildin OTA app that needs TWRP recovery installed to work.
You can still use LAOS recovery and OTA app, but you will need to download the zip file and flash it manually from within your recovery. Zip gets saved in the "AICP_ota" folder on your internal storage.
Please be sure that you are on the latest TWRP recovery.
If you want to contribute to the AICP or wanna see what is being worked on/merged, feel free to visit our Gerrit review system. (Link is at the bottom!!!)
Kernel source:
Santoni Kernel
ROM & Additional links:
Gerrit Code Review
Github
IceColdJelly AICP G+ community
Contributors
@wzedlare , @Nik001 , @abhirajsinghofficial for using their vendor/device source and for all who helped me to build this Rom.
ROM OS Version: 7.1.x Nougat
ROM Kernel: Linux 3.18.xx
ROM Firmware Required: Unlocked bootloader, MIUI 9
Version Information
Status: Stable
Creation date: 05-09-2017
Last Updated: Nightly
You want to see a normal night at the "DEV office", click here!!
XDA:DevDB Information
AICP 12.1, ROM for the Xiaomi Redmi 4X
Contributors
hemantbeast, wartomato
Source Code: https://github.com/AICP
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
ROM Firmware Required: MIUI 9
Based On: LineageOS
Version Information
Status: Nightly
Created 2017-09-06
Last Updated 2018-01-15
Reserved
MIUI 9 Firmware:
https://www.androidfilehost.com/?fid=889764386195925068
Flash this zip file first if you are coming from MIUI 8.
Then flash the rest of the zips like Rom, Gapps, etc.
Reserved
AICP 12.1 last build
https://www.androidfilehost.com/?fid=673956719939818403
When trying to flash: Updater process error code 7
tenoce said:
When trying to flash: Updater process error code 7
Click to expand...
Click to collapse
Unzip the Rom file and remove the first line from META-INF/com/google/android/updater-script. Remove the assert(); line.
zip it again and then flash the Rom.
hemantbeast said:
Unzip the Rom file and remove the first line from META-INF/com/google/android/updater-script. Remove the assert(); line.
zip it again and then flash the Rom.
Click to expand...
Click to collapse
Thank you Sir. Just found this solution on the net. Will try it again.
---------- Post added at 01:37 PM ---------- Previous post was at 01:22 PM ----------
Unfortunatelly I got stuck at MI boot-logo.
tenoce said:
Thank you Sir. Just found this solution on the net. Will try it again.
---------- Post added at 01:37 PM ---------- Previous post was at 01:22 PM ----------
Unfortunatelly I got stuck at MI boot-logo.
Click to expand...
Click to collapse
Tell me your Rom flashing procedure. Or try again by flashing Firmware (updated) first, then Rom and gapps.
IR works?
Fast discharging rate and the recents key works as a menu key.
Would love to know if anyone confirms that Fingerprint and IR works.
There's a bug in music player. When i play then pause a song on headphones, the volume goes up then goes back to normal. Front camera is not working. When i open camera app then switch to front cam, it crashes. Also, IR doesn't work.
ram
ram management is so bad, please fix it and add feature to clean ram usage. tx
Xiaomi Redmi 4X Santoni, latest build.
novlyp said:
ram management is so bad, please fix it and add feature to clean ram usage. tx
Xiaomi Redmi 4X Santoni, latest build.
Click to expand...
Click to collapse
Does your IR works?
I don't know why, but for me all works great) Expext RAM management and some bad translate in settings) Its good that nightly build appear every day) Respect!
hope this rom has good support going forward and frequent updates,
I noticed that all the firmware assemblies come with the same problems. I suggest assembling boot.img with a working IR.
https://drive.google.com/open?id=0B6hJK_LrW2nbZi1UeHl1MXcxY0E
Ruzik said:
I noticed that all the firmware assemblies come with the same problems. I suggest assembling boot.img with a working IR.
https://drive.google.com/open?id=0B6hJK_LrW2nbZi1UeHl1MXcxY0E
Click to expand...
Click to collapse
does it works for you?
psdashing said:
does it works for you?
Click to expand...
Click to collapse
Yes.
Ram management problem will be there because we don't have our kernel, as we are using prebuilt miui kernel.
Ruzik said:
I noticed that all the firmware assemblies come with the same problems. I suggest assembling boot.img with a working IR.
https://drive.google.com/open?id=0B6hJK_LrW2nbZi1UeHl1MXcxY0E
Click to expand...
Click to collapse
What have you done in it? Pm me.
Ruzik said:
I noticed that all the firmware assemblies come with the same problems. I suggest assembling boot.img with a working IR.
https://drive.google.com/open?id=0B6hJK_LrW2nbZi1UeHl1MXcxY0E
Click to expand...
Click to collapse
it worked bro :good::good:
{
"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"
}
AICP
Android Ice Cold Project
AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago (2012) and since then has evolved into a mature ROM with the BEST community that you can find!!!
Until Android Lollipop, the ROM has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM.
With the re-brand of CM to LineageOS (LOS) we became LineageOS based with some tweaks from AOSP and we are now based on the "Ground Zero Open Source Project" (GZOSP) for Android Pie.
If there are any bugs, either we will sort them out or the GZOSP team, if it concerns their code base. This ROM isn't GZOSP supported, so there is no need to report errors/bugs to them!!
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. Hard & a lot.
*
*/
Feature list (rough overview)
In the beginning we would like to thank:
GZOSP team
LineageOS & CM (R.I.P.) team
@Maxwen and the rest of the OmniRom team
DU team
SlimRoms team
Resurrection Remix team
Community
...
@LorD ClockaN
@zipsnet
@eyosen
@semdoc
@SpiritCroc
@wartomato
@eboye
plus the rest of the crazy bunch that we call "team"
...
We are paying for servers that build nightlies/weeklies and everything that comes with it, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 14.0
Download link: https://www.androidfilehost.com/?w=files&flid=291290
Please note that official builds will be deleted from our servers every month due to maintenance services.
We advise everyone to keep at least the latest or best working build on their device as a backup.
Maybe copy it to a cloud service or USB too.
Full Changelog link: https://dwnld.aicp-rom.com/
(Just click the changelog button next to the download link in the list of builds available for your device)
Google Apps:
GApps from opengapps.org is almost always a good choice
You tell...
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look in the OP to see if your device is built on a nightly or weekly schedule.
Q. Does this ROM support custom kernels officially?
A. No. You can still use them, but discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Q. Why doesn't this ROM support Xposed?
A. Xposed is a hack that is geared towards AOSP. Custom ROMs modify the framework a lot, so Xposed can cause a ton of issues on custom ROMs. Now it might work for you, however it is not to be discussed in this thread, and you should refrain from posting bug reports.
Q. Alright, but I still want to flash Xposed, so which version do I need to install?
A. You will need to use the version arm64/arm/whatever for SDK 28.
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the install instructions in the first post...
Q. Can the builds be dirty flashed over each other?
A. Yes, however make a nandroid backup first as there is a chance of getting a bootloop or encountering bugs. Also bugs may only be reported on a clean flash.
Q. How do I 'dirty flash' builds?
A. Wipe the System, Cache and ART/Dalvik cache. Flash the ROM, GApps (only needed if you wipe the system), your preferred root solution and reboot. Or just use the OTA app to preform that task for you.
Q. How do I flash kernel builds?
A1. If it's a .img file, boot into TWRP and go to the install page in TWRP, in the bottom right corner select "install image", select the desired kernel, then select "boot" as the destination, then swipe to flash, then go back to the install screen and install your root method again, if you don't want to loose root and reboot.
A2. If it's a flashable ZIP, you can flash it together with a ROM update or separately. Go to the install page in TWRP, choose the kernel zip (or add it to the flash queue right after the ROM zip). Then add your root method to the queue if you don't want to loose root. Now swipe to flash and reboot afterwards.
Using the ROM:
Q. I installed a bad theme and now I'm getting a bootloop, how do I fix it?
A. In TWRP, flash the substratum rescue zip that's in the substratum folder on the internal storage.
Q. I'm having issues with WhatsApp, how do I fix it?
A. Read this
Q. Do I need to provide a logcat if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat. (Note: Please just link the logcat from your GDrive, Dropbox, etc. and do not post the content here. Thanks.)
Q. How do I get a logcat, what type should I get and more questions that can conveniently be answered by my pre-determined answer?
A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog (Root needed).
A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the others section in the AICP Extras main page.
The ROM should contain everything you need to enjoy Android Pie. You don't need to install any Add-on's, simply download the latest ROM, GApps, flash it and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM Zipfile.
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup as this can cause stability issues that are very hard to debug.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash for the first time:
(Again: Don't do it if you don't know it!)
1. Download the ROM and GApps and transfer them to your device.
2. Boot to recovery (TWRP recommended).
3. Wipe the System, Cache, and Data (you might need to format the data partition!).
4. Flash the ROM Zipfile.
5. Flash the GApps (optional, needed for e.g. Google Playstore to work).
6. Reboot and set up your device, enable developer settings and in them OEM unlock/Advanced reboot/USB tethering.
7. Reboot back into TWRP recovery.
8. Flash the root solution of your choice (optional).
9. Reboot your device.
The procedure might vary from device to device and is a bit different on system updates!
The ROM has GApps persistence in between dirty flashes, so you only have to flash them once! This might differ on AvB Devices.
The root solution can be flashed together with every OTA update (= ROM Update).
Currently supported Root Solution:
Magisk stable
Magisk versions >= 17.2 don't usually require to be flashed on every dirty flash.
Depending on the device, you may need to flash it every time.
Unless your maintainer says otherwise, you should be fine.
PREREQUISITE FOR OTA ("Over-The-Air" Updates):
To be able to flash using the built-in OTA app, TWRP recovery is needed.
Please be sure that you are on the latest TWRP recovery. Keep in mind that this could also be an unofficial version!
On encrypted devices you will have to enter your PIN/password in TWRP before the process starts.
If you want to contribute to the AICP or want see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)
Kernel source:
https://github.com/icxj1/android_kernel_htc_msm8960/tree/p9.0
Device tree source:
N/A
Vendor source:
https://github.com/icxj1/proprietary_vendor_htc/tree/p9.0
ROM & Additional links:
AICP's Homepage
AICP Gerrit Code Review
AICP sources on Github
AICP Download page for official builds and media content
AICP Discord Community
Contributors:
@icxj1
The following informations are ONLY needed, when you are not opening up a devdb thread on XDA!
ROM OS Version: 9.0.x Pie
Kernel: Linux 3.4.x
Version Information:
Status: Development
Release Date: 03-10-2019
You want to see a "normal" night at the "DEV office", click here!!
XDA:DevDB Information
HTC ONE M7ul,wlv,wls Pie testing, ROM for the HTC One (m7)
Contributors
icxj1
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.4.x
ROM Firmware Required: latest GPE
Based On: GZOSP
Version Information
Status: Testing
Current Stable Version: N/A
Current Beta Version: UNOFFICIAL
Beta Release Date: 2019-03-10
Created 2019-03-12
Last Updated 2019-03-12
reserved
reserved again
reserved 1 more
thx for the build.i will try it when the files are up
Android 9 on the 2013 HTC One? This cannot be real?!!
daywalk3r666 said:
thx for the build.i will try it when the files are up
Click to expand...
Click to collapse
I will get test build up soon guys having trouble with uploads past 2 days. Keep dropping out at 65%.
clarkgable said:
Android 9 on the 2013 HTC One? This cannot be real?!!
Click to expand...
Click to collapse
Hello nice news,i want test android P,please give me link for downloading, thanks
Great!
Looking forward to test the rom.
Here is the sneak peak test build as promised, i am sure it will have plenty of bugs to work through. Make sure yo have a good backup of whatever rom you use as a daily driver. i will update thread with screenshots & bug list as we go. This build is for m7u-ul only, no vzw or sprint for now.
m7 += https://www.androidfilehost.com/?fid=1395089523397918526
I've tried out the test ROM, with:
- OpenGAPPS (ARM, 9.0, stock)
- Magisk 17.1
- TWRP 3.2.1.0
So far I've been having difficulty even trying to get through the Setup Manager.
There has been multiple reboots, the lag can definitely be noticed, and the overheating is there.
I hope most of these bugs can be fixed and patched soon.
[UPDATE]
Got through the Setup Manager, however the reboots are still occurring.
Also I remembered that icxj1 created TWRP 3.2.3.0 that supports the 9.0 device tree so I'll try flashing that and then reflashing the ROM.
I had the same problems so what I did was install the ROM and magisk without gapps. It booted normally but it was laggy. So I installed the LKT module and choose the performance profile to give me better experience ( less lag). After that I installed the gapps (pico) and everything is fine. No reboots so far.
vincenzo697 said:
I had the same problems so what I did was install the ROM and magisk without gapps. It booted normally but it was laggy. So I installed the LKT module and choose the performance profile to give me better experience ( less lag). After that I installed the gapps (pico) and everything is fine. No reboots so far.
Click to expand...
Click to collapse
I'll try doing it that way, If it still doesn't work well then I guess I'll go back to my daily driver of Lineage OS 14.1 for a while.
---------- Post added at 05:22 AM ---------- Previous post was at 04:57 AM ----------
There might be a reason as to why it keeps rebooting, and it might be the D2TW function which ruins the performance, it overheats a lot and the reboots do occur. icxj1 can you please make a flashable zip to disable D2TW?
---------- Post added at 05:59 AM ---------- Previous post was at 05:22 AM ----------
AICP - 14.0: First impressions
Problems with this ROM:
- The main issue with this ROM is the random reboots that occurs when you stress it (possibly RAM management).
- Very laggy / slow start: shown in the bootanimation, no wallpaper shown on lockscreen and home until it blanks out and wallpaper suddenly works again.
- The quick tiles shows 6 which overlaps the width of the taskbar.
- UI is usually very slow and laggy and touch response isn't too great.
- Wi-Fi problems occur, my network didn't save after a random reboot.
But even still, it's lovely to see some of that sweet, sweet Pie on my M7.
Don't waist time with root and gapps. Should have know from dealing with you guys on Oreo that the word testing goes in one ear & out the other. And not even a single log.
icxj1 said:
Don't waist time with root and gapps. Should have know from dealing with you guys on Oreo that the word testing goes in one ear & out the other. And not even a single log.
Click to expand...
Click to collapse
Sorry buddy. We are excited about pie!!!
Last but not least
For now didn't manage to make it to the launcher. Reboots at welcome and choose language screen. If I can help some way on this step, guide me to log it
Hi, are you planning to compile to sprint and verizon, and when? I have both, so i can test it
P.S.Good job, you are awesome