MOD EDIT
Here at XDA, we try very hard to work with everyone to resolve issues before they result in actions such as banning or locking threads. Unfortunately, hard as we try, we are not always able to meet those goals via ways that would be more desirable and seemingly more peaceful.
Here recently we have been having some issues with some Android devs who work with the Android Kernel. While we were able to work out the issues with quite a few devs we were sadly unable to reach such a peaceful settlement with the Android ROM dev Feeyo.
Before we go any farther into the underlying problems that we have had getting these issues resolved with this particular Android Dev, lets go over real quick what the main concern is about.
The Android kernel which is present in EVERY single ROM is an ever-growing community project. Android devs from all around the world have put their hard work into an open source project simply in an attempt to make the Android project better as a whole. While I am sure that all of these Android devs made these contributions to the kernels as a result of things that they wanted or needed to see develop within Android, they made their work available to ALL of us so that we could ALL benefit from their talents.
That being said, the Linux kernel is released under what is called the GNU GPL. (General Public License)
Basically this license allows for the Android kernel to be freely used and modified under the condition that the source of the kernel be released to the public. This "release" can be handled two ways, by either providing a direct link to the source where it can be downloaded, modified and reused under the GNU GPL, or by a written statement that offers the to provide the kernel source to anyone whom requests it. While I realize that I have only outlined a small portion of the GNU GPL, the bottom line here is that the COMPLETE and WORKING kernel source that was MODIFIED by anyone MUST be provided to the community, for any version of publicly released software.
You can find the full text of the GNU GPL licence here:
Herein, lies our problem. We here at XDA have had MULTIPLE interactions with the Android ROM dev, Feeyo, in regards to the specific problem that he has not followed these GNU GPL guidelines. There have been multiple instances where users have requested his Kernel source and he has continually refused to provide this source, or he has provided us with non working and otherwise incomplete source, or invalid or unmodified source.
The first thing we need to show is that Feeyo was MODIFYING the Android kernel source. Below is a screenshot that proves just that.
{
"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"
}
Above, you can see the Kernel version says "2.6.29-opt-40-Cronos [email protected]#1", The only known way to put you name there, in the kernel, is to modify and compile the kernel yourself. You have to edit a file within the kernel source called .config.
We also have proof by Feeyo’s own release notes in his ROMs that he has modified the kernel source code as well. For example, the changelog for his kernel below shows the changes made between versions.
Here is another screenshot where he talks of changes he made to his kernel:
All of that being said, Feeyo has definitely made various improvements to the Android Kernel source by modifying that source and he has publicly released this kernel to the community.
In an attempt to resolve this matter we made various outreaches to Feeyo, including a moderator by the name of 12aon making several attempts to get this resolved... I’ve added some screenshots of the dialog that they exchanged...
Here we can see that we were trying to resolve the issue with Feeyo and he stated that he would no longer provide or distribute the 2.6.32 Kernel that he was working on because he didn’t intend on releasing code with he labeled as “messy”.
Feeyo did indeed stop providing that 2.6.32 kernel as far as we know, however he then continued to modify the 2.6.29 kernel source and distribute that in his ROMs again without following the GNU GPL guidelines.The sources for this 2.6.32 kernel were never released.
It is the decision of the XDA moderators that since Feeyo has no rights to use or distribute the Linux kernel without making available his valid source code and modifications, his ROMs and associated kernel releases will be treated as warez under forum rule 6
Here in this screenshot we are again trying to get him to post the sources to his Kernel after he released a ROM that mention various enhancements or modifications to the Android Kernel that he was providing in his ROM. Feeyo then sent us another PM as shown below:
In this PM Feeyo is stating that he did provide his sources... However, it was not complete and was missing many things that were needed to compile the Android Kernel in such a fashion that it would run on the Hero. Additionally, as these sources are not kept up to date, they do not meet the requirements of the GPL to release sources as used to compile the distributed binary kernel.Below is the link to the thread that he posted containing his supposed kernel source:
Supposed Sources used in Cronos Droid early releases
That thread was locked to preserve proof to the fact that the source he provided was not complete. In fact, on post #11 within that thread he even confirms that the source is not complete, again this is not following the GNU GPL guidelines.
Additionally, the screenshots below show occasions where Feeyo acknowledged he would not provide complete sources, by deliberately withholding the entire kernel source or constituent parts.
We have made this long explanation of recent events available to you, the community, for two reasons.
First of all, we realize that Feeyo is a talented dev and that his ROMs are well liked within the community. With this in mind, we wanted it to be known that the decisions that we have made here today are not decisions that have been taken lightly or irrationally made. This decision included opinions from AT LEAST 5 other Senior mods here at XDA. We feel that a full explanation of our actions is something that we owe the community and we truly regret that it has come down to this.
Secondly, this will be a marking point, I don’t want to say that this is an example because it was never intended to be an example. However the fact remains that this incident has caused quite a stir within XDA and from this point on we will be making sure whenever possible that any Android dev that modifies and publicly releases the Android kernel is following the GNU GPL guidelines.
The GNU GPL guidelines are important because they ensure that credit is given where credit is due and it also ensures that continued improvement, advancement, and development of such products under the GNU GPL continue to ensue. As part of the Android community, which is an OPEN SOURCE community, we owe it to ourselves and the ENTIRE community to make sure that we are staying true to the notion of an open source platform. Keeping your sources to yourself while working on a project that is open source and released under the GNU GPL is not staying true to what being open source is all about.
At this point in time, Feeyo has received a 30 day temporary ban for refusing to help us resolve this matter in a peaceful manner and for ultimately violating Rule #6 and Rule #9 which state:
6. Do not post warez.
If a piece of software requires you to pay to use it, either pay or find your cracks and serials somewhere else. We do not accept warez nor do we permit any member to promote or describe ways in which Warez, cracks, serial codes or other means of avoiding payment, can be obtained.
9. Don't get us in trouble.
Don't post copyrighted materials or do other things that will obviously lead to legal trouble. If you wouldn't do it on your own homepage, you probably don't want to do it here either. This does not mean we agree with everything the software piracy lobby try to impose on us, it simply means you cannot break any laws here, since we'll end up dealing with legal hassle caused by you. Please use common sense: respect the forum, its users, and those that write great code.
Click to expand...
Click to collapse
Furthermore, at this time, all ROMs posted by Feeyo that do not follow the GNU GPL where applicable will be locked and the links to the ROMs removed.
During this time that Feeyo is away, we sincerely hope that he will come around and upon his return, which we thoroughly hope for, he will post the sources to his Android kernel changes in the spirit of the open source community and the GNU GPL and participate in a more supporting manner.
Best Regards,
The XDA Moderator team
finally i download now...fastttttttt..
no greek support?
thank you sooooo much! i've been waiting for this for a loooong time... finally i have it...thanks again...
oh you made it!
Going to flash now and see if it is an improvement to the fusion!rom
Going to try it now
How about the google applications? did you include them?
Going to give it a go now. Will post impressions.
cokbok said:
How about the google applications? did you include them?
Click to expand...
Click to collapse
Yes they are included.
pornogeroc said:
finally i download now...fastttttttt..
no greek support?
Click to expand...
Click to collapse
Sorry. Language list is not complete. Greek is supported.
Does anyone else have a notification about a blank SD card due to unsupported file system?
Brooks316 said:
Does anyone else have a notification about a blank SD card due to unsupported file system?
Click to expand...
Click to collapse
EXT partitions are not supported. Froyo will see it as an unsupported Filesystem and wants to Format it. Backup your data first and then let Froyo do the formatting please.
this is a very good begin, but i wanna know, how i can enable jit, thanks for your work guy
Sow said:
this is a very good begin, but i wanna know, how i can enable jit, thanks for your work guy
Click to expand...
Click to collapse
JIT is enabled. Hardcoded into the DalvikVM sources I compiled.
Feeyo said:
Sorry. Language list is not complete. Greek is supported.
Click to expand...
Click to collapse
What other languages are missing? How about norwegian?
... and thanks for the ROM, btw!
skandahle said:
What other languages are missing? How about norwegian?
... and thanks for the ROM, btw!
Click to expand...
Click to collapse
Supported.
Great to see a new Froyo ROM on the scene! Look forward to seeing it grow into one of the best...
For now, my early impressions are that it suffers from the same problems as other Froyo ROMs have / do.
To name two (and aside from the obvious):
* LED notifications
* Google Mail App displays at incorrect resolution for Hero
It might be a funny question but... All other Froyo releases I tried have been getting really laggy after installing all the applications I like and then 3-4 hours of usage. I use a task manager to kill applications so that a lot of memory is always free.
Would I have the same problem with this ROM? I am sure you have been using it for a couple of days at least before going public.
I would test it out by myself but formatting my SD card is going to take a lot of time for backing up, etc.
BR.
cokbok said:
It might be a funny question but... All other Froyo releases I tried have been getting really laggy after installing all the applications I like and then 3-4 hours of usage. I use a task manager to kill applications so that a lot of memory is always free.
Would I have the same problem with this ROM? I am sure you have been using it for a couple of days at least before going public.
I would test it out by myself but formatting my SD card is going to take a lot of time for backing up, etc.
BR.
Click to expand...
Click to collapse
I have not yet run this build for a few days at it just came out of the oven...
But I did run some of the older builds of mine a few days and for me it stayed at the same performance. Although I do not have a lot of apps installed..
After installing apps you will need to give it a reboot to optimize the freshly installed packages.
Feeyo said:
I have not yet run this build for a few days at it just came out of the oven...
But I did run some of the older builds of mine a few days and for me it stayed at the same performance. Although I do not have a lot of apps installed..
After installing apps you will need to give it a reboot to optimize the freshly installed packages.
Click to expand...
Click to collapse
Thank you for the speedy response and support. Appreciated.
I have a few questions in addition to the ones I've already asked.
1) When you long press a textbox and select "Input Method" option, the keyboard appears twice. Is it normal?
2) The news and weather application cannot find "Sofia" or "Sofia, Bulgaria" as a location. Do you think that might be a bug in the ROM or in the application itself?
BR.
Related
MOD EDIT
Here at XDA, we try very hard to work with everyone to resolve issues before they result in actions such as banning or locking threads. Unfortunately, hard as we try, we are not always able to meet those goals via ways that would be more desirable and seemingly more peaceful.
Here recently we have been having some issues with some Android devs who work with the Android Kernel. While we were able to work out the issues with quite a few devs we were sadly unable to reach such a peaceful settlement with the Android ROM dev Feeyo.
Before we go any farther into the underlying problems that we have had getting these issues resolved with this particular Android Dev, lets go over real quick what the main concern is about.
The Android kernel which is present in EVERY single ROM is an ever-growing community project. Android devs from all around the world have put their hard work into an open source project simply in an attempt to make the Android project better as a whole. While I am sure that all of these Android devs made these contributions to the kernels as a result of things that they wanted or needed to see develop within Android, they made their work available to ALL of us so that we could ALL benefit from their talents.
That being said, the Linux kernel is released under what is called the GNU GPL. (General Public License)
Basically this license allows for the Android kernel to be freely used and modified under the condition that the source of the kernel be released to the public. This "release" can be handled two ways, by either providing a direct link to the source where it can be downloaded, modified and reused under the GNU GPL, or by a written statement that offers the to provide the kernel source to anyone whom requests it. While I realize that I have only outlined a small portion of the GNU GPL, the bottom line here is that the COMPLETE and WORKING kernel source that was MODIFIED by anyone MUST be provided to the community, for any version of publicly released software.
You can find the full text of the GNU GPL licence here:
Herein, lies our problem. We here at XDA have had MULTIPLE interactions with the Android ROM dev, Feeyo, in regards to the specific problem that he has not followed these GNU GPL guidelines. There have been multiple instances where users have requested his Kernel source and he has continually refused to provide this source, or he has provided us with non working and otherwise incomplete source, or invalid or unmodified source.
The first thing we need to show is that Feeyo was MODIFYING the Android kernel source. Below is a screenshot that proves just that.
{
"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"
}
Above, you can see the Kernel version says "2.6.29-opt-40-Cronos [email protected]#1", The only known way to put you name there, in the kernel, is to modify and compile the kernel yourself. You have to edit a file within the kernel source called .config.
We also have proof by Feeyo’s own release notes in his ROMs that he has modified the kernel source code as well. For example, the changelog for his kernel below shows the changes made between versions.
Here is another screenshot where he talks of changes he made to his kernel:
All of that being said, Feeyo has definitely made various improvements to the Android Kernel source by modifying that source and he has publicly released this kernel to the community.
In an attempt to resolve this matter we made various outreaches to Feeyo, including a moderator by the name of 12aon making several attempts to get this resolved... I’ve added some screenshots of the dialog that they exchanged...
Here we can see that we were trying to resolve the issue with Feeyo and he stated that he would no longer provide or distribute the 2.6.32 Kernel that he was working on because he didn’t intend on releasing code with he labeled as “messy”.
Feeyo did indeed stop providing that 2.6.32 kernel as far as we know, however he then continued to modify the 2.6.29 kernel source and distribute that in his ROMs again without following the GNU GPL guidelines.The sources for this 2.6.32 kernel were never released.
It is the decision of the XDA moderators that since Feeyo has no rights to use or distribute the Linux kernel without making available his valid source code and modifications, his ROMs and associated kernel releases will be treated as warez under forum rule 6
Here in this screenshot we are again trying to get him to post the sources to his Kernel after he released a ROM that mention various enhancements or modifications to the Android Kernel that he was providing in his ROM. Feeyo then sent us another PM as shown below:
In this PM Feeyo is stating that he did provide his sources... However, it was not complete and was missing many things that were needed to compile the Android Kernel in such a fashion that it would run on the Hero. Additionally, as these sources are not kept up to date, they do not meet the requirements of the GPL to release sources as used to compile the distributed binary kernel.Below is the link to the thread that he posted containing his supposed kernel source:
Supposed Sources used in Cronos Droid early releases
That thread was locked to preserve proof to the fact that the source he provided was not complete. In fact, on post #11 within that thread he even confirms that the source is not complete, again this is not following the GNU GPL guidelines.
Additionally, the screenshots below show occasions where Feeyo acknowledged he would not provide complete sources, by deliberately withholding the entire kernel source or constituent parts.
We have made this long explanation of recent events available to you, the community, for two reasons.
First of all, we realize that Feeyo is a talented dev and that his ROMs are well liked within the community. With this in mind, we wanted it to be known that the decisions that we have made here today are not decisions that have been taken lightly or irrationally made. This decision included opinions from AT LEAST 5 other Senior mods here at XDA. We feel that a full explanation of our actions is something that we owe the community and we truly regret that it has come down to this.
Secondly, this will be a marking point, I don’t want to say that this is an example because it was never intended to be an example. However the fact remains that this incident has caused quite a stir within XDA and from this point on we will be making sure whenever possible that any Android dev that modifies and publicly releases the Android kernel is following the GNU GPL guidelines.
The GNU GPL guidelines are important because they ensure that credit is given where credit is due and it also ensures that continued improvement, advancement, and development of such products under the GNU GPL continue to ensue. As part of the Android community, which is an OPEN SOURCE community, we owe it to ourselves and the ENTIRE community to make sure that we are staying true to the notion of an open source platform. Keeping your sources to yourself while working on a project that is open source and released under the GNU GPL is not staying true to what being open source is all about.
At this point in time, Feeyo has received a 30 day temporary ban for refusing to help us resolve this matter in a peaceful manner and for ultimately violating Rule #6 and Rule #9 which state:
6. Do not post warez.
If a piece of software requires you to pay to use it, either pay or find your cracks and serials somewhere else. We do not accept warez nor do we permit any member to promote or describe ways in which Warez, cracks, serial codes or other means of avoiding payment, can be obtained.
9. Don't get us in trouble.
Don't post copyrighted materials or do other things that will obviously lead to legal trouble. If you wouldn't do it on your own homepage, you probably don't want to do it here either. This does not mean we agree with everything the software piracy lobby try to impose on us, it simply means you cannot break any laws here, since we'll end up dealing with legal hassle caused by you. Please use common sense: respect the forum, its users, and those that write great code.
Click to expand...
Click to collapse
Furthermore, at this time, all ROMs posted by Feeyo that do not follow the GNU GPL where applicable will be locked and the links to the ROMs removed.
During this time that Feeyo is away, we sincerely hope that he will come around and upon his return, which we thoroughly hope for, he will post the sources to his Android kernel changes in the spirit of the open source community and the GNU GPL and participate in a more supporting manner.
Best Regards,
The XDA Moderator team
Thank you for sharing. Are you gonna post screenshots, this makes it more interesting to download.
thanks finish downloading now and will report back when flashing
Sure downloading app now.
forget the screenshots, how did you get the kernel? is it/can it be overclocked? Can it be used with other ROMs (CM5.0.7 etc.)
it sounds very interesting let me test it and tell u .
downloading now, hope it is true what you're saying...
What about the kernel?
cyberkid2002 said:
forget the screenshots, how did you get the kernel? is it/can it be overclocked? Can it be used with other ROMs (CM5.0.7 etc.)
Click to expand...
Click to collapse
I have not added any overclock options into the kernel. I think its fast enough the way it is. But try it out and let me know. Maybe I will add some patches so that you can overclock it
How did you get the 2.6.29 hero kernel sources?
this sounds great! ima try it now, is this kernel the kernel everyone's been waiting for?
I can't get it working, did a full wipe and keeps hanging on HERO logo.
Downloading and feed back
Flashing within 2 min
Get some sleep, or try it out? Guess?
started up, runs fine so long
RaduG said:
How did you get the 2.6.29 hero kernel sources?
Click to expand...
Click to collapse
From my understanding, all the OP did was take the Eris .29 kernel source & ported anything needed for the GSM Hero to run.
Is this a sense rom?
Downloading now,, hope this is the one I have been searching for....
reidefors82 said:
Flashing within 2 min
Get some sleep, or try it out? Guess?
Click to expand...
Click to collapse
Getting some sleep
Added screenshots.
Is the green/bad autofocus camera bug fixed?
hi all ...
I wanna share my kernel for GB users
What New ?
Kernel Version 2.6.35.14
Some Backport Future from Erikcas kernel 2.6.39.x
Update GPU
Add More CpuFreq
Add some Governor and I/O , SmartassH3, sioplus,Zen,etc
Zen set as Default Scaling Gov and I/O Sched
Inject Tweak on Ramdisk
More Powerfull and Smooth
Enable SWAP
Enable Deep Sleep
Save your battery
EXT4 File System
BLN Support
Custom Splash Screen and Change Android Text *this kernel i'm use on my ROM :silly:
and See By Your Self :silly:
available governor :
POWERSAVE
USERSPACE
ONDEMAND
CONSERVATIVE
INTERACTIVE
SMARTASS
SMARTASS2
INTERACTIVEX
SCARY
SAVAGEDZEN
LAGFREE
MINMAX
BRAZILIANWAX
ONDEMANDX
SUPERBAD
LILGSMART
LAZY
==================================
add :
LIONHEART
LULZACTIVE
MSM7K
SMARTASS1
VIRTUOUS
SMOOTHASS
How to :
Use CWM with support ext4
go to recovery mode
mount system
install zip on sdcard
reboot
DWYOR
This benchmark using antutu without OC
{
"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"
}
Download Here
Thank's to :
squadzone
tj_style
Erikcas
BNCrew
Galaxy Gio Community
RECOMENDED FOR ROM WITHOUT TWEAK ON INIT.D IF YOU GET LAG PLEASE REMOVE TWEAK ON YOUR /SYSTEM/ETC/INIT.D
THANKS
PM ME IF YOU WANT USING MY KERNEL ON YOUR CUSTOM ROM
Thanks
To comply with the GPLv2 you will need to link to your kernel source.
what is new in this kernel ???
andyharney said:
To comply with the GPLv2 you will need to link to your kernel source.
Click to expand...
Click to collapse
sorry i dont have connection tu upload my source ..
Msulviu said:
what is new in this kernel ???
Click to expand...
Click to collapse
you can see on add governor
Hmm, if u dont upload source mods can close this thread, gpl violation is treated as warez
A little introduction
Recently in several Android fora on XDA-Developers, it has come to the attention of the moderator team that there have been issues regarding developers’ compliance with the GPL. This post aims to clarify the position of XDA on the use of GPL sources, particularly in the development of Android kernels.
Without the GPL, the Android operating system would likely never have come about. Through the work of Linus Torvalds, the Linux kernel was made open source for all to use, share and modify. As Android runs on the Linux kernel, and features numerous modifications to these sources, it would not exist in its present state without the Open Source community.
As a result, it is in the interests of everyone who owns an Android phone, who wishes to see further development on the platform, to ensure that they play their part in upholding both the letter and spirit of the GPL.
The GNU General Public Licence (also known as the GPL) is available to read in full at www.gnu.org
To make it easy for everyone to spot a release that complies with the GPL mark the title of your release thread with [GPL]. If you find a ROM which does not comply with the GPL, or the developer does not issue sources, you can report the post as usual, using the report post button next to the post number. Alternatively you may PM your forum specific moderator.
The Rules as they apply on XDA
As XDA has no legal power to uphold the GPL (and frankly we want to stay as far away from doing so as possible), we can’t force any of our users to abide by the GPL. However it is in XDA’s interests as well as the interests of our developer-base to ensure all GPL-derived materials hosted or linked on XDA comply fully with the GPL.
[*]GPL-derived materials that do not come with the complete sources used to compile the GPL components are considered warez, and will be treated as such under forum rule 6 and 9.
[*]If you use GPL components, but do not make any modifications to them whatsoever, you should provide a link to the original source of your GPL code.
[*]Sources accompanying a release should be complete, and contain all the necessary source code for any modules, scripts or definition files. Complete sources will be defined as those which compile correctly and completely against the platform for which the software is distributed, and which contain any and all modifications made to the released General Public Licenced code. The source code supplied should be the exact version for which the source code is being requested, complete with all modifications.
EXAMPLE: Here’s a bit of code that could be used as a template to post your releases
The Very Quick Summary of General Public License (GPL)
The text of the GPL Licence itself will be used to reach any final conclusion regarding any disputes over GPL Licenced materials. The above is a summary of what XDA expects of members using GPL code, and the complete text can be read at the GNU website.
The GPL states that anyone who modifies GPL licenced code is required to make available the sources used to compile it. This is to further improve and encourage collaborative work, as well as to ensure that the best code possible is produced, and to encourage peer-review of all work. This benefits both developers and end users in numerous ways, including:
[*]Allowing anyone to verify the code they are trusting with their data, and its authenticity
[*]Encouraging community collaboration to produce faster fixes and updates, and better code
[*]Helping bring new developments from other devices and fields to your own, letting you benefit from new code that wouldn’t have been available without this sharing.
[*]The GPL imparts great freedom for GPL end users. It ensures innovation is never stifled and no project is dependent upon any single developer.
It is in everyone’s interest for the GPL to be adhered to, as it gives us all better ROMs, better transparency, and a better atmosphere for developers to work together to make great code.
Click to expand...
Click to collapse
Sent from my GT-S5660 using XDA
lemmymet said:
Hmm, if u dont upload source mods can close this thread, gpl violation is treated as warez
Sent from my GT-S5660 using XDA
Click to expand...
Click to collapse
sorry , i try to upload my source but my connection don't stabil to upload it ..
if i have stabil connection i will give my link
I used Phiexz CM7. Performance is good but very bad battery usage. Kernel on the battery is very good if you try.
Ok! I've intall this! So what is the best option for a long baterry life?
If you cannot provide source I will have to close your thread.
I'll give you a few more days to get it sorted
Mavi Tuna said:
I used Phiexz CM7. Performance is good but very bad battery usage. Kernel on the battery is very good if you try.
Click to expand...
Click to collapse
do you have calibrate your battery after flash cm7 ..?
kompressorgpl said:
Ok! I've intall this! So what is the best option for a long baterry life?
Click to expand...
Click to collapse
try to use smartassv2 or smoothass ..
but calibrate your battery before
andyharney said:
If you cannot provide source I will have to close your thread.
I'll give you a few more days to get it sorted
Click to expand...
Click to collapse
okay, if i have connection i will upload my source
kompressorgpl said:
Ok! I've intall this! So what is the best option for a long baterry life?
Click to expand...
Click to collapse
I would vote for "conservative", with the following advanced settings:
sampling rate 200000us (fastest)
up threshold 40%
down threshold 30%
freq step 10%
andyharney said:
If you cannot provide source I will have to close your thread.
I'll give you a few more days to get it sorted
Click to expand...
Click to collapse
he use my source, and only change a little like governor, so most of part is from mine,
here's the source, my github
Cheers for that squadzone.
tux-kid's - As your Kernel is based on the above source, all you need to do is provide the source to the files you edited/changed and those files only.
If you'd like I can help you get set up on GitHub, as I'm sure many others here could too. XDA is here to embrace, help & encourage development.
Damm i want to build my own kernel from source
But there are only tutorials to mod the kernel
Can anyone provide a guide/tutoial of it ?
herpderp © aint got money to pay to my fish
squadzone said:
he use my source, and only change a little like governor, so most of part is from mine,
here's the source, my github
Click to expand...
Click to collapse
wuhihi, thank's squadzone ..
soalnya ane dah tuliskan source nya dari ente ...
ntar ane coba upload dah ^^ :cipok
andyharney said:
Cheers for that squadzone.
tux-kid's - As your Kernel is based on the above source, all you need to do is provide the source to the files you edited/changed and those files only.
If you'd like I can help you get set up on GitHub, as I'm sure many others here could too. XDA is here to embrace, help & encourage development.
Click to expand...
Click to collapse
i have account on GitHub but i dont have connection to upload my source ..
i just edit some file on source from squadzone
spacecaker said:
Damm i want to build my own kernel from source
But there are only tutorials to mod the kernel
Can anyone provide a guide/tutoial of it ?
herpderp © aint got money to pay to my fish
Click to expand...
Click to collapse
and if you got the turotial.. i will be excited if you wanna share it with me too
Post Updated from Original
Cyanogen has posted a i9505 common device tree.
It is based on his working configurations for US T-mobile.
There are two ways to get this:
1) Clone these repos:
https://github.com/CyanogenMod/android_device_samsung_jf-common
https://github.com/CyanogenMod/android_kernel_samsung_jf
https://github.com/CyanogenMod/android_device_samsung_jfltetmo
2) Set up your CM environment and "breakfast jfltetmo" to pull the 3 repos above.
The first 2 are the common device and kernel. The third can be used as a base for your device.
(So fork it to your own repo and start making changes)
Hope this gets other variants up quickly! Thanks again to Cyanogen for the work to get it this far so quickly!
garwynn said:
Well, while waiting for the SPH-L720 (Sprint GS4) to come out this weekend I'm trying to do what prep work I can. I'm checking both here and #cyanogenmod-dev to see if anyone else has started this, but just in case I created jflte-common repos to start allowing collaborative efforts for GS4 work to get CM going ASAP. I'll be using these to get the jfltespr (SPH-L720) trees up and running.
Now fair warning, I'm doing this as my first port attempt but have several kernels and a few recoveries that I've done already. So please bear with the learning curve...
I9505 Common Repos:
https://github.com/garwynn/i9505_rec_ramdisk (Thanks to ewmno for posting the i9505 recovery.img!)
https://github.com/garwynn/device_samsung_jflte-common
https://github.com/garwynn/vendor_samsung_jflte-common
https://github.com/garwynn/kernel_samsung_jflte
I'm downloading the only i9505 source I saw so I can find out what linux build version they're using as a base. Figured that's a good starting point to figure out where we start for kernel dev.
Anyone interested in helping - would be most appreciated! I'll start working on the tree repos this morning (US CDT)
Click to expand...
Click to collapse
Since it's Qualcomm based - First thing you should do is fork https://www.codeaurora.org/gitweb/quic/la/?p=kernel/msm.git;a=summary
Then go to Qualcomm's CAF release list at https://www.codeaurora.org/xwiki/bin/QAEP/release and go through the tags for your SoC and Android version. Check each out one by one. I'm fairly certain you are APQ8064T. Whcih is odd, there are no tags for the T variant...
Code:
git checkout <TAG>
Drop the Samsung tarball on top of the checked out tree, and diff it.
Code:
git diff > ../<TAG>.patch
Keep going until you find the patch that is the smallest. This is likely the CAF base that Samsung started from.
Two other things:
Be warned, Samsung hacks the **** out of their bases
Also, try to coordinate with cyanogen himself, I believe he'll be working on either the AT&T or T-Mobile variants.
Entropy512 said:
Since it's Qualcomm based ................................Blah Blah
Click to expand...
Click to collapse
What if i need to make 1 for I9500
Entropy512 said:
Since it's Qualcomm based - First thing you should do is fork https://www.codeaurora.org/gitweb/quic/la/?p=kernel/msm.git;a=summary
Then go to Qualcomm's CAF release list at https://www.codeaurora.org/xwiki/bin/QAEP/release and go through the tags for your SoC and Android version. Check each out one by one. I'm fairly certain you are APQ8064T. Whcih is odd, there are no tags for the T variant...
Code:
git checkout <TAG>
Drop the Samsung tarball on top of the checked out tree, and diff it.
Code:
git diff > ../<TAG>.patch
Keep going until you find the patch that is the smallest. This is likely the CAF base that Samsung started from.
Two other things:
Be warned, Samsung hacks the **** out of their bases
Also, try to coordinate with cyanogen himself, I believe he'll be working on either the AT&T or T-Mobile variants.
Click to expand...
Click to collapse
Thanks for the starting point, Entropy! I'll start on that during my lunch break.
I'm keeping up IRC on the build box but just sent an alt contact in case anyone else you know is interested in collaborating.
I'm guessing that they're not differentiating (yet) between the APQ8064 variants.
So I'll start pulling standard APQ8064 and hopefully get lucky.
might want to look at cpu_is_apq8064ab related stuff in the jb_2.5 branch to get an idea of where stuff is - The APQ8064T may be referenced as APQ8064AB in kernel sources. Not sure.
Still doesn't answer which tag to follow.
We are lucky to have such a driven Dev. Thank you gawynn, for all you have done, and all that you will do.
Kudos from the E4GT community.
Entropy512 said:
might want to look at cpu_is_apq8064ab related stuff in the jb_2.5 branch to get an idea of where stuff is - The APQ8064T may be referenced as APQ8064AB in kernel sources. Not sure.
Still doesn't answer which tag to follow.
Click to expand...
Click to collapse
No but it does allow me to thin out the list.
{
"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"
}
Every build that I have seen so far is March so we should be able to rule out any April builds.
So once I get access to my build box again (TV died yet again...) I'll start at the bottom and work my way up.
(Edited post) So far the above (AFAIK) addresses kernels. Still haven't addressed device.
Thinking we can still use this for graphics base:
https://github.com/CyanogenMod/android_device_samsung_msm8960-common
I almost want to fork d2-common for the jflte common device and start replacing S3 with S4 details.
I have that 9505 system dump on my build box so I can start extracting stuff from there.
More as I keep reading and digging.
Looking forward to development for S4 , planning on getting it as soon as my renewal will allow .
Sent from my SPH-D710 using xda premium
Cyanogen found kernel already, head is jb_2.5, didn't get the branch point but says he knows what it is.
In the meantime I went ahead and stripped d2-common and used that as a shell for jflte-common device.
Future status updates on this will be placed here at Cyanogen's request:
https://jira.cyanogenmod.org/browse/QSDB-25
Feel free to take a look there for progress reports.
Will be requesting thread lock for now.
As far as graphics base you'll almost surely have the same flags as any other caf-display device.
Sound can get a bit more funky... I'd look at mako, Sonys, and Oppo Find5 for inspiration there as those are the current non-T APQ8064s.
Entropy512 said:
As far as graphics base you'll almost surely have the same flags as any other caf-display device.
Sound can get a bit more funky... I'd look at mako, Sonys, and Oppo Find5 for inspiration there as those are the current non-T APQ8064s.
Click to expand...
Click to collapse
i9505 Latin JB source has Alsa audio folder in the platform side - wouldn't be able to use that?
You know what? Seeing as OSRC pulled it (for now) I'll make a repo for both the kernel and platform side and add the links here in a sec.
Edited:
https://github.com/garwynn/i9505_latin_jb_platform
https://github.com/garwynn/i9505_latin_jb_kernel
Hopefully we get the L720 stuff here soon so I can compare ROMs and kernels against the ones I have already.
Should give a good idea as to what can be common vs. proprietary.
Had to change my search for the kernel based on a misunderstanding of where to start.
So I started with the jb2.5 head and pulled this list from it.
As you can see I've been trying a "divide and conquer" method to figure out where the branch point is.
Tried checkout method after cloning the repo but can't seem to get it to pull the branch source.
So for now I'm resorting to a rather tedious process of clone branch, diff, delete, repeat.
Also doesn't help that I lost the build box for a day but hopefully will be fixed by 7 pm.
So while I wait for the build box to come back I'm going to see if that AT&T dump is different from the i9505 one I have.
If so should shed some light on what in the ROM will be common and what won't be.
garwynn said:
No but it does allow me to thin out the list.
Every build that I have seen so far is March so we should be able to rule out any April builds.
So once I get access to my build box again (TV died yet again...) I'll start at the bottom and work my way up.
(Edited post) So far the above (AFAIK) addresses kernels. Still haven't addressed device.
Thinking we can still use this for graphics base:
https://github.com/CyanogenMod/android_device_samsung_msm8960-common
I almost want to fork d2-common for the jflte common device and start replacing S3 with S4 details.
I have that 9505 system dump on my build box so I can start extracting stuff from there.
More as I keep reading and digging.
Click to expand...
Click to collapse
I don't know much about porting and building CM but I noticed there was some confusion about the chipset model. I'm wondering if this might help you in any way:
http://www.anandtech.com/show/6914/samsung-galaxy-s-4-review/3
ilabs said:
I don't know much about porting and building CM but I noticed there was some confusion about the chipset model. I'm wondering if this might help you in any way:
http://www.anandtech.com/show/6914/samsung-galaxy-s-4-review/3
Click to expand...
Click to collapse
That isn't useful. We are fully aware of which chipset is in this device. What we're not entirely sure of is which release tags/branch in CAF it corresponds to (unlike most other qcom processors, there is not a direct match between the chip's identifier and any CAF tags. That said, it is starting to seem like CAF is using the apq8064 releases for both apq8064 and apq8064t)
As embarrassing as this may be for me, let my facepalm teach others...
Read advice from mentors well.
And if not sure, read it again. And if still not sure, read it again.
Bold and italics below are my emphasis.
Entropy512 said:
Since it's Qualcomm based - First thing you should do is fork https://www.codeaurora.org/gitweb/quic/la/?p=kernel/msm.git;a=summary
Code:
git checkout <TAG> [I][B](Notice no -b here like I was doing and thus causing my headaches)[/B][/I]
Drop the Samsung tarball on top of the checked out tree, and diff it. (Don't go erasing what's already there like I do with other projects.)
Code:
git diff > ../<TAG>.patch
Keep going until you find the patch that is the smallest. This is likely the CAF base that Samsung started from.
Click to expand...
Click to collapse
Why does this matter? My diffs went from 24MB to 4MB and is a lot easier to see what may be going on.
When we do get to find the branch point it will make a huge difference when I pull a more recent version and then want to apply that patch to the newer version.
Entropy, had another question... In stock kernels I would normally patch Linux before doing anything else.
I'm assuming I'll want to grab the latest jb_2.5, patch Samsung's mods in first and wait until we get stable before patching Linux versions?
Just because we add Samsung's mods in doesn't mean everything will work perfectly as-is... and that logically would need addressed before anything else.
And still waiting for my build box to come up - the host is having their ISP issues addressed. Thankfully the home dual boot works great for simple things like these kernel diffs.
garwynn said:
As embarrassing as this may be for me, let my facepalm teach others...
Read advice from mentors well.
And if not sure, read it again. And if still not sure, read it again.
Bold and italics below are my emphasis.
Why does this matter? My diffs went from 24MB to 4MB and is a lot easier to see what may be going on.
When we do get to find the branch point it will make a huge difference when I pull a more recent version and then want to apply that patch to the newer version.
Entropy, had another question... In stock kernels I would normally patch Linux before doing anything else.
I'm assuming I'll want to grab the latest jb_2.5, patch Samsung's mods in first and wait until we get stable before patching Linux versions?
Just because we add Samsung's mods in doesn't mean everything will work perfectly as-is... and that logically would need addressed before anything else.
And still waiting for my build box to come up - the host is having their ISP issues addressed. Thankfully the home dual boot works great for simple things like these kernel diffs.
Click to expand...
Click to collapse
You mean pull in patches from kernel.org? I personally don't do that any more - it usually causes more problems than it is worth. The only time I've done that was a situation when I had to match d2's wifi backport on 4412 devices.
So far, devices in CM are a mix of two approaches:
1) The old (and usually quick) approach of taking the manufacturer tarball and dropping a bulk update from mako onto it. Since this is a MUCH newer CAF base and is 4.2.2 - this may not be necessary. You may just be able to get the kernel running CM10.1 with not much modification.
2) Chunk up the manufacturer's diffs and rebase them onto the latest jb_2.5 - d2 has done this, HTCs are in the process of doing so, and Sonys are probably going to do so in the next month or two. Same for Oppo Find5 - we used approach 1 initially, but are switching to 2.
For your sanity, you probably want to chunk up the manufacturer's diffs into smaller parts if you can. The workflow I used was:
Check out the closest CAF tag once you determine it.
Check out a new branch at this point using
Code:
git checkout -b <branchname>
In my case, I named the branch for find5 find5_CAFTAGHERE so I would always remember the tag.
Drop the kernel tarball on top of the CAF tag
Commit the whole big mess
Now, here's the fun part:
Unstage some files out of the commit. For example, if you want to unstage drivers/media/video out, do:
Code:
git reset HEAD^ drivers/media/video
Then
Code:
git commit --amend
This will remove the changes from drivers/media/video from the megacommit
Then
Code:
git add drivers/media/video
git commit
Commit just those changes. Try to find associated headers if you can from include/
Now, if you just split out one commit:
Code:
git rebase -i HEAD~2
to switch the order so the megacommit is the last commit for further chunking.
It's time consuming but makes the chunks much easier to analyze.
When I get home, I'll post my bash alias 'gitshowfiles' which shows a list of all files changed by the last commit. It's hightly useful.
When you're done, you'll have a nice reference like:
https://github.com/Entropy512/kernel_find5_reference/commits/find5_A8064AAAAANLYA101034
With the build box back in business I finally got to the point Entropy was talking about.
For reference here is the commit:
https://www.codeaurora.org/gitweb/q...it;h=b5075e02c2ff1d959c589552c62329c4797b0535
And I've attached the diff file so those following along can keep doing so.
(I've posted the same stuff on CM's Jira as well)
So I'll start 2 repos next.
1) Fork current CAF jb_2.5 to a new repo.
https://github.com/garwynn/kernel_samsung_jflte
2) Fork above version to this repo:
https://github.com/garwynn/i9505_CAFDiff
...where I'll start the process of splitting the big diff into smaller ones, just in case they are needed.
Now it's possible that Sprint's kernel could have branched off differently but there's an easy way I can think of to check that. Take the i9505 kernel source I have now, drop Sprint's on top and run a diff to see how different they really are.
And just an update. Sprint's GS4 is making its way to folks today. One person already has and I'm trying to get what I need to really get going.
Update 1: Odin mode shows "Write Protect Enabled" - wondering if this means bootloader is locked.
Few updates while I get things moving.
A second look at that LA kernel had what seems to be everyone's defconfig. Added and pushed to common kernel.
You'll probably need to combine your specific additions still to jf_defconfig to get a full one.
At least the Sprint one identifies an Audience audio chip and binary that should be there.
Did an initial push of common device folder after confirming Sprint's fstab matches common i9505.... so I'm guessing they're all the same. It's very rough so wouldn't try using it yet... just want access to it in case I pull to my home box. Now working to get a device specific one up enough to try a CWM build. Going to have to hold testing anyhow until we get a full restore and figure out about that write protect.
OK, for those not following the SPH-L720 thread, I'm doing test builds of CM/CWM at the moment to see what I can get working before I move over to the kernel.
I tried including msm8960-common and it failed on kernel issues. Think I'm going to leave it out for now and try just getting the CAF jb_2.5 to build successfully first. I can leave in qcom-common and that seems to at least play nice.
CWM working for SPH-L720 but users reporting that moving up/down requires 2 key presses to get it to move. Alpha 5 was reported as losing External SD card functionality - not sure why as I didn't change the fstab. i9505 users reporting that it didn't work, suggesting there may be a difference. We better nail that down and if need to move something from common to variant, do so before others start building off of it.
I'm starting to read the Find 5 configs as it seems one of the only ones with the Adreno 320 config. But again, I've got to get the kernel to build before I start really getting into this stuff.
I'll push updates to repos tonight after I get another successful build.
{
"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-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. -
Team OctOs would like to thank Team Blackout for the use of their Blacked Out Nexus Launcher & for saving eyes one app at a time!
You can get all the TBO goodies here as well as the TBO Updater http://teamblackedout.com/ #whiteuimustdie
TBO thread http://forum.xda-developers.com/showthread.php?p=41545802
Frequently Asked Questions
Q: Is this Android 6 (Marshmallow)?
A: Yes, this is Android 6.0.1
Q: What code is Oct-M based on?
A: Starting with Oct-L, we've rebased OctOs on the CyanogenMod 12 code. Oct-M is base on CyanogenMod 13.
Q: What happened to AOSP?
A: All Android code is based on the Android Open Source Project (AOSP). Under previous releases, we tried very hard to limit the number of "Not from Google directly" repositories that we used. Unfortunately, issues with devices, the need for Code Aurora Foundation (CAF) repositories for Qualcomm devices, and compatibility issues meant fighting code more often than not. We decided that since the code-base for many repositories were the same across most ROMs, picking a starting point to build the user experience on outweighed the desire to craft code from scratch, or fix broken code to make it work with other changes we already had.
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 XYZ and 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: 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 MD5 file, and grab your favourite Opengapps 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
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 CyanogenMod 13 kernel.
Kraken kernel source code can be found here: https://github.com/Oct-mm
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
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
OpenGapps
CyanogenMod
OmniROM
LiquidSmooth
Anyone else who has ever submitted Open-Source code
Click to expand...
Click to collapse
Follow Us at the various websites below!
XDA:DevDB Information
Oct-M, ROM for the T-Mobile Samsung Galaxy S III
Contributors
bthorne79, CjKacz, canodroid15, hedwig34
Source Code: http://www.github.com/Team-OctOs
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod 13
Version Information
Status: Stable
Current Stable Version: OCT-M R2
Created 2015-02-17
Last Updated 2016-08-26
Reserved
Known Issues
A full list of Known Issues resides on our website. *In order to avoid confusion for people who skimmed the OP,
NONE REPORTED FROM TESTERS
Thanks OP
downloading now..
:good:
bthorne79 said:
Known Issues
A full list of Known Issues resides on our website. *In order to avoid confusion for people who skimmed the OP, the biggest Known Issue with the Galaxy S3 (d2lte) platform is the Camera. *It could cause Force Close issues. *This is an upstream issue, and we are working to correct it.
Click to expand...
Click to collapse
Please put this info and list other bugs in the OP so that people won't be misled. Not everyone reads past OP.
goldentequila said:
Please put this info and list other bugs in the OP so that people won't be misled. Not everyone reads past OP.
Click to expand...
Click to collapse
Sorry but the inability to read is the users issue. Half the time they don't even read the OP. Go right to the download link. I posted in the 2nd post and there is a link in op to site with bug list and change log
Sent from my SPH-L720 using XDA Free mobile app
Running nicely right now. Had a hard time getting WiFi to connect on first boot but its working now
We put the information on the website because its easier to keep track of across the multiple devices we develop for. We develop the ROM for the simple fact we want to run it, not for you, or anyone else. The ability to be cognizant on what you're doing is a primary requirement for flashing ROMs, and the inability for you to apparently read and comprehend the very simply formatted OP means you are not willing to rise to the level we seek in a user.
It would be better for everyone involved if you don't flash Oct-L. You have many ROMs to choose from, you shouldn't choose ours.
ROM Development is not a service or product industry. You are neither a customer, or a client. Your demands mean exactly nothing and we have better things to do than hold your hand.
Now, if you feel like running what we build, by all means, do so. However, your continued patronage to the thread is directly proportional to your ability to be civil and not condescending.
Enjoy, or not at your leisure, but unless you have something constructive to say, please wander to another ROM.
Toodles!
Running smooth. ^.^
lol bitter much? Don't ruin this for the rest of us who rely on devs like these guys to continue providing up to date software for our aging phones.
I'm definitely trying this ROM out.
From the Moderator
To all in this thread........
Please all remember, the Devs do this for free and out of their love for developing....
....So being rude and poor mannered...... gets you nothing but maybe one less Dev making Roms for your phone
Keep that in mind when you feel like you have some lame commentary or demand to make...
........To the trolls, rather than complaining...... show us your skills and make a ROM for us to critique.......
........oh yeah...... you have no skills other than running yer mouth and making personal demands in a thread.......
~~~ oka1
The strangest thing is him talking about the OP not listing a Buglist. The Rom that he his visiting the most does not either. With that said I'm done. Mod can in and slammed the hammer down on that issue.
Please any one using this rom if you do see anything and and are able to catch a log please report and send log to us.
Thanks for supporting Team OctOS
Sent from my SM-T217S using XDA Free mobile app
Is the nav bar included in this release? Working?
allendj81 said:
Is the nav bar included in this release? Working?
Click to expand...
Click to collapse
Sure! About the only thing that doesn't work is the camera!?
Installed this Rom and turned on wifi but after login to my account wifi stopped and grayed in off position
Rebooted device and wifi got on but every time failed to login
Again rebooted and it started working correctly
Reached office but again failed to connect to wifi
It is just an information as I read same thing happening with other cm12 build too so this may be with the cm12
anil2653 said:
Installed this Rom and turned on wifi but after login to my account wifi stopped and grayed in off position
Rebooted device and wifi got on but every time failed to login
Again rebooted and it started working correctly
Reached office but again failed to connect to wifi
It is just an information as I read same thing happening with other cm12 build too so this may be with the cm12
Click to expand...
Click to collapse
What firmware is your phone on I've noticed that the newest modems and firmware is needed for lollipop to work correctly. These builds have been in test for quite some time. Our testers have put this build through the ground with not one hick-up just camera which we have been working on getting fixed.
If you can get a log of the WiFi issue you are having we will look at it. My suggestions is to update to the latest modem firmware for d2tmo.
Sent from my SPH-L720 using XDA Free mobile app
allendj81 said:
Is the nav bar included in this release? Working?
Click to expand...
Click to collapse
canodroid15 said:
Sure! About the only thing that doesn't work is the camera!
Click to expand...
Click to collapse
The Navbar will cover the "Clear All Recents" button if you select the lower right or left position. This already has been corrected for the next release.
Thanks a lot for this amazing rom, i´ll install it as soon as it finish downloading, but one question, it´s the same instaling it in cwm? i mean, does it makes a diference like more bugs or things like that, i hope you understand Thanks a lot!
vick007 said:
Thanks a lot for this amazing rom, i´ll install it as soon as it finish downloading, but one question, it´s the same instaling it in cwm? i mean, does it makes a diference like more bugs or things like that, i hope you understand Thanks a lot!
Click to expand...
Click to collapse
Our d2tmo user still uses CWM as the team we suggest TWRP only cause CWM is almost a dead recovery and has been know to cause bad flashes..
Sent from my SPH-L720 using XDA Free mobile app
vick007 said:
Thanks a lot for this amazing rom, i´ll install it as soon as it finish downloading, but one question, it´s the same instaling it in cwm? i mean, does it makes a diference like more bugs or things like that, i hope you understand Thanks a lot!
Click to expand...
Click to collapse
Also, CWM has had historical issues with actually wiping the partitions effectively. The "Wipe system, data, cache, dalvik x3" was a reality in the past because of CWM. Those issues don't happen with TWRP.
I noticed a couple of things:
1) When flashing the ROM it takes a while. Compared to other lollipop rom's, this one takes about 3-4 minutes to flash, while others flash in like 15 seconds. Is that normal?
2) Installing apps from the play store are taking a long long time. Each app takes about 2 minutes to install, longer if it's a bigger one like youtube. I've noticed it takes long across all lollipop rom's, but one this one it seems to be longer.
3) Kernel Tweaker crashes when I try to view read-ahead and IO scheduler. This doesn't happen with any other ROM so I'm thinking there's something going on with oct os.
Any thoughts?
{
"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"
}
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, build, and use our code at CarbonROM's GitHub... and at CarbonROM Gerrit.
Disclaimer:
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!
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) Join our Discord server! There, you can connect with other Carbon users and our developers, and you can get quicker responses to your bug reports. The invite link is right below.
We recommend MindTheGApps. OpenGApps should work, but please make sure you clearly mention the GApps you're using when reporting bugs.
Get CarbonROM
Changelog
Join the CarbonROM Discord server
GitHub
Gerrit
Kernel source
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
CarbonROM, ROM for the Sony Xperia XZ1 Compact
Contributors
SirSoviet, modpunk, Myself5
Source Code: https://github.com/CarbonROM
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Nightly
Created 2018-07-17
Last Updated 2018-07-16
Changelog
July 23, 2018
Upstream changes
Switched to modpunk's kernel due to build failure, difference should be unnoticeable
July 16, 2018
Initial release
https://blog.carbonrom.org/changelog/
Bugs
CAMERA: Enabling stabilization option in camera settings under "Video camera" causes an error message and crash when attempting to record.
[*]APP: Gardenscapes connection error on all yoshino devices. Enable storage permissions for app manually.
CAMERA: Manual focus by tapping while zoomed in crashes the app.
All of these issues are present on modpunk's latest LineageOS build. I'm not a programmer, so please be patient while the issues are resolved!
Nice! Been hoping for a Carbon ROM build for the xz1c. Just flashed and looking good so far. Thanks so much!
I installed it. So far everything is working for me. Will you continue to compile new versions, especially if new patches arrive?
SkyHigh76 said:
I installed it. So far everything is working for me. Will you continue to compile new versions, especially if new patches arrive?
Click to expand...
Click to collapse
I shared my initial version with the intention of releasing new versions.
However, my only practical platforms for compiling my builds on are my laptop, which takes 6 hours to build everything without having compiled anything else and gives me only 20GB of free storage space after building, and Google Cloud Trial which is just a trial, and so it has a limit.
As long as I have access to a build server, new builds will be released for at least a while.
New build! No device-specific bug fixes just upstream changes and a kernel switch
Going on vacation so no builds until around mid-August. Sorry!
While you guys wait, I recommend installing AOSP Phh-Treble with a DRM fix, Magisk, and SELinux permissive patch. The included camera won't work, but Open Camera does and the quality will be as good as stock despite being AOSP.
Also runs noticeably smoother than other AOSP roms like AOSP compiled directly from sonyxperiadev, pretty ironic considering that Treble GSIs aren't tailored to device-specific level.
SirSoviet said:
Going on vacation so no builds until around mid-August. Sorry!
While you guys wait, I recommend installing AOSP Phh-Treble with a DRM fix, Magisk, and SELinux permissive patch. The included camera won't work, but Open Camera does and the quality will be as good as stock despite being AOSP.
Also runs noticeably smoother than other AOSP roms like AOSP compiled directly from sonyxperiadev, pretty ironic considering that Treble GSIs aren't tailored to device-specific level.
Click to expand...
Click to collapse
How did you manage that? I was on Stock rom booted into TWRP. There I did a factory reset and wiped System, Cache, dalvik and data. Then I flashed the System Image from treble project the A partition one vanille Android but it didnt boot. Am I forgetting something?
EDIT: Fixed it. You should not use a Magisk patched ramdisk before flashing or use a patched kernel. A flash after coming from a fresh stock rom worked.
weeklies.....lol....you managed to build 2 !! builds and for about 4 weeks there´s nothing new.....
very interresting that new projects die within 2 weeks *sad*
Tralien said:
weeklies.....lol....you managed to build 2 !! builds and for about 4 weeks there´s nothing new.....
very interresting that new projects die within 2 weeks *sad*
Click to expand...
Click to collapse
Hey man learn to read comments before you say anything, the dev said he is going on vacation and there won't be new updates until he is back, so stfu
Tralien said:
weeklies.....lol....you managed to build 2 !! builds and for about 4 weeks there´s nothing new.....
very interresting that new projects die within 2 weeks *sad*
Click to expand...
Click to collapse
I'm sorry for not committing to this project, but shouldn't you be grateful that I built CarbonROM for lilac and shared it with you and the rest of the community?
You've needlessly pointed out twice that progress on RR for the S9 has halted. And? Developers are humans, just like you (I assume).
I suggest that if you haven't already, you should experience what it's like to build and maintain a custom ROM, before continuing to complain about inactive developers.
I'm back from vacation now, but I really don't have any reason to continue with this project, doesn't help that I would have to share my builds with people like you if I did. Google Cloud credit is running low anyways, and I don't have access to any other solutions.
SirSoviet said:
I'm sorry for not committing to this project, but shouldn't you be grateful that I built CarbonROM for lilac and shared it with you and the rest of the community?
You've needlessly pointed out twice that progress on RR for the S9 has halted. And? Developers are humans, just like you (I assume).
I suggest that if you haven't already, you should experience what it's like to build and maintain a custom ROM, before continuing to complain about inactive developers.
I'm back from vacation now, but I really don't have any reason to continue with this project, doesn't help that I would have to share my builds with people like you if I did. Google Cloud credit is running low anyways, and I don't have access to any other solutions.
Click to expand...
Click to collapse
Anyway, thanks for your work. Some guys here may cant read your post before about your vacation.
May be you will change your opinion about not publishing any future versions.
I think that Carbon was running quite well.
Dang that sucks. I really wanted to see more from CarbonRom.
As I expected...you ask for donations in your first post and now......no more updates
you developers always ask for donation and this is one good example why many people dont donate.
Tralien said:
As I expected...you ask for donations in your first post and now......no more updates
you developers always ask for donation and this is one good example why many people dont donate.
Click to expand...
Click to collapse
Sorry, I've never shared my builds on XDA before, and I was just trying to follow other CarbonROM members' post formats. Please note that I am not a member of the CarbonROM team, these are unofficial builds.
Good news! I now have a dedicated build machine, completely separate from my main computer.
I may post more builds soon, but flashlight, RIL, and camera are currently broken in modpunk's LineageOS I built for myself (my CarbonROM uses his device and kernel trees).
Hopefully I'll be able to revert the changes and bring a build to you guys sooner.
@SirSoviet Pls I'm not being rude or bossy I just wanna ask are we going to get new builds of this rom?
Thread closed at OP request