Is there an xda thread that discusses CM releases nightlies & stable for the Nook color )Encore)? The forum on CM is not very active & I don't find many postings that say things like "Ok, I tried CM7 nightly #95 & I have encountered these problems." It would even be nice to have a running poll that rates the functionality of new releases. That way, those who don't have the time to deal with new bugs can judge whether or not to move to a new CM release & fix a bug they may have. I am trying to use my NC in a productive way, but I would like a few issues fixed, but need some of the "tools" to still work. Maybe the solution in my case is to install only stable releases, but the last stable was on 5/8 & I got impatient & installed some nightlies.
Cheers,
kev
bugeyed1 said:
can judge whether or not to move to a new CM release & fix a bug they may have. I am trying to use my NC in a productive way, but I would like a few issues fixed, but need some of the "tools" to still work.
Click to expand...
Click to collapse
A big issue is that the developers officially consider the nightlies to be a "use at your own risk" type situation. Since CM7 is a pure community project, the developers work on whatever bugs effect them directly or ones that are so egregious that they effect everyone (like SOD). There is no process for the community to decide which bugs gets fixed because that comes close to breaking the first rule of cyanogenmod.
Maybe the solution in my case is to install only stable releases, but the last stable was on 5/8 & I got impatient & installed some nightlies.
Click to expand...
Click to collapse
That is exactly what the answer is from developers that on this forum- stick to the stable releases if you want stable. Of course then the issue is that you miss out on some great improvements for a while (like working sleep), so in the end you have to chose:
A. A stable, non-fully functioning version.
B. A nonstable, functional-hopefully nightly.
For many of us used to open source development, this dichotomy between broken and stale is the norm.
If you are having real issues it is best to post them in the CM7 developers thread where they will be read, and hope that a kind developer chooses to work on that issue after you post it!
poofyhairguy said:
For many of us used to open source development, this dichotomy between broken and stale is the norm.
Click to expand...
Click to collapse
As a Debian Sid user, I would be bored if it were any other way.
The Nook has the great perk of booting off an sd card by default, which really diminished my reasons for not staying on top of the nightlies. (I grab one every few days instead of daily but that is more to conserve their bandwidth than a fear of what I will get.)
TO MODERATORS:
before you remove this thread --- please read:
I started to get a little p*ssed off regarding the infrequency of updates and lack of actual benefits to being a "groupie" for Galnet... so I posted this on the forums...
"
BBenefits of being a groupie right now:
None.
Reasons:
-there are already several implementations of MIUIV4 for the SGS2 based on work by Team Hacksung. I would have thought this was something Galnet would already have a release for with similar functionaity.... in reality... no...
-the changes made my the Galnet team are rather minimal over the weekly updates provided by the MIUI team already
-lack of frequency of updates, lack of actual changes from stock versions - half part of the previous reason, and half because you would expect a modified version of a ROM to be modified more often than it's "stock" counterpart.
-reverting to stock animations in MIUI builds... this is an attractive feature which might actually encourage more folk to sign up, yet seems to have just been excluded from weekly builds....
Can I just make raise something worth discussing please in that the reason the forums are so completely void of any discussion (which roughly translates as "interest") is because there is almost nothing happening.
If there are lots of things happening in the background, you need to let people know. Before you start flaming me, I've paid less money for PC games that took years to develop and are still being updated on a regular basis. I understand that paying to be a groupie wasn't just for our benefit, but to aid and encourage development, but it's certainly not marketed as a "donation"... it's marketed as a subscription... and since I joined.. there has been 1 or 2 releases...
Please do not flame me purely because you are passionate about open source development and because you don't think we have a "right" to complain... but I am starting to understand why Galnet has become the swear word of the XDA environment.
........ "
Don't want to discourage development and be unfair to the competion -- but my last comment pretty much sums up the issue...
EDIT:
I will not post links to what I am talking about, those who are aware will already know who/what I am referring to.
I stopped using Galnet as I found releases a number of days late and they seemed to get worse and worse (their reaction to their rom not booting correctly was 're-wipe and reflash before rebooting after first install....why not just fix that and re-upload it...).
As soon as I saw they were using their forums to advertise their web design services I decided to not bother checking back. Clearly not making enough from their groupie system...Probably for the reasons you posted.
I was "THIS" close to join the groupie back in the "chameleon" days but i was lucky that i changed my mind. Galnet has depreciated and i dont have any faith in them anymore. They used to be a quick and fast release group eventhough people label em as zipper/cooker but now, its almost dead.
Plus i live in the world where Galnet only release much for NexusS and GalaxyS so, bye bye Galnet. Your zipping work has been pleasant for me all these while curing my tears upon Bmarko leaving MIUI development
Galnet ROMs are banned from XDA for several reasons, not the least of which is GPL violations.
So, I don't see how discussing this little drama in the GSII General Section serves any purpose whatsoever but to bring nonsense that the overwhelming majority of people here could not care less about.
Closed.
This is, now, the official FAQ for the Olympus (Atrix 4G) Linux 3.1 Kernel Project. (ICS/JB Kernel)
PUBLIC ALPHA BUILD FAQ
DISCLAIMER
The kernel project waives any and all responsibility for damage to any and all devices, including your iPhone, your car keys, and your homework and your Dad's plasma. The builds provided are alpha, and represent danger. Permanent damage may result.
Q: When it will be avaliable?
CM9 (krystianp) and CM10.1 (Epinter) builds are avaliable. Kernel build was expected, but never release. However, you can compile yourself from source.
Q: It is avaliable in a ROM?
Same ask as above.
CM9 Alpha Builds here
CM10.1 Alpha Builds here
Click to expand...
Click to collapse
Q: Will CM10.2 (JB 4.3) or CM11 (KK 4.4) be avaliable for the Atrix 4g with this kernel?
It should. But right now there are 2 manteiners, krystianp, who it's focus to get a stable CM9 build, and Epinter, who is focus to get a stable 10.1. There is a Epinter's build of 10.2, but main funcions doesn't work.
If you know how to, you can do it. Please, remember you'll have to make some modifications to kernel as well to get everything working.
Q: It is stable to dialy use?
It may be. But nor me, nor the team, nor anyone will be responsable if your devices gets damage for the kernel. But you.
EDIT (02/24/2014): I don't have the phone anymore, but my brother have it. No matter what disaventage maybe left, Totally worth it. Just try it. You will be in love and will never ever left it.
AGAIN, Nobody is responsible, but you, if your device is on fire or UFO invasion begins because you flash this.
Please, read the follow
They are NOT meant to be stable or finished in any way.
They are NOT meant to be your daily driver.
They are NOT meant to be reused and modded.
They are NOT meant to serve as a base for making other custom ROMs.
The ONLY purpose of those builds is to test the kernel in the "real world" and to gather bug reports. That is all.
They can be anything of above, but right now the team is you to looking for the bugs in the official builds, and report them.
If you use it as you dialy driver, you have to know that I will chrash. If you modded, you won't be able to know if the crash if kernel or mod related.
So please, use those ROMs "vanila" as you can, and report the bugs that you found. Thanks you.
Q: Will be ever be stable build?
You may want to read this:
CyanogenMod: Tegra 2 Support
Q: That means that we will never get a stable CM10.1 or beyond?
That means that we can get closer to a stable build, but it will be somethings (Gapps mostly) that will never work properly. I think that's why krystianp is just focus to get an CM9 (ICS 4.0) because it's the one that really will be totally stable.
We can expect that CM10.1 will be stable to dialy use, but as I said, somethings won't work properly. They knew that, but I didn't matter, they are doing it right now, so why we will matter? They are awsome. .
Q: Can I submit new bugs? Where?
Testers members are the only one avaliable to do it.
Q: Can I submit bugs in this thread?
Yes. You can. But I would be wiser to report the bugs in the thread of the build that you are using.
Q: How can I submit bugs in those thread?
Please follow this little guide:
Before submitting new bug in respective thread, please search is it submitted already. If not, write all necessary data:
- memory type (Elpida, Hynix)
- panel type
- sdcard present (yes or no)
- simcard (normal/micro)
- tegra revision (e.g. A03 prime)
- atag revision
- tegrapart
- radio (e.g. 36p, 37p, 38p)
Some data above can be easily seen in settings, about. Rest from dmesg short after boot.
Also, please explain how to reproduce bug.
Click to expand...
Click to collapse
Q: How I can get any of the information you need above?
Please, use this guide our friend jhonnyx made
Q: How do I know where I have to submit it?
If you are using CM9, please report bugs to CM9 krystian's thread. If you are using CM10.1, please report to CM10.1 epinter's thread.
Anyway, you may still report bugs here, but try hard to get the info above, and addicinaly, what build are you using (exlactly name would really help, because the date and build)
Q: What can I do with the new kernel?
Please expect some misbehavor, it is in an alpha status. You can play around, and help them find new bugs to be fixed.
Q: May I use this kernel in another ROM?
Yes, you can. But please, don't report bugs coming from another ROMs as they are not supported.
Q: How can I help?
Please, check the kernel and the OS behavor. If anything goes wrong, consider to post here, steps about how to reproduce it, and if you know how, attach the log cat.
Verify that your device is entering Deep Sleep with CPU Spy or Battery Battery Stats. If you are unable to achieve deep sleep, look for wake locks in order to identify a potential misbehaving app. (OUT OF DATE - I think the deep sleep problem was solved, but I'm not sure)
Please, look at the same question in the main FAQ
Click to expand...
Click to collapse
What's the expect battery life with this kernel?
Expected battery life in CM9: (OUT OF DATE)
1.5% with cellular data disabled, 2g connection enabled, wifi disabled, sdcard removed
2% with cellular data disabled, 2g only connection enabled, wifi disabled, sdcard inserted
3% with cellular data enabled, 3g connection (2g only disabled)
100% to 0% in 3-4 hours with GPS on, cellular data enabled, 3g connection, screen on, Google Maps Navigation running
Expected battery life in CM10.1:
N/A
Click to expand...
Click to collapse
I don't know what battery life have the CM9 build, but the CM10.1 should give around 10 hours or so. At least, that's what my brother gets.
What's the expected temperature with this kernel?
CM9: It's up to 50C (see System Panel) (OUT OF DATE)
CM10.1: N/A
Click to expand...
Click to collapse
FAQ in progress...
END OF THE PUBLIC ALPHA FAQ
MAIN FAQ
Q: Where is the main thread?
Here.
Keep in mind, that it is only for development purpose, so keep it on-topic is not a choise anymore, you will be warning if you don't do so.
Q: What is the team structure?
The Project Manager:
jjwatmyself
Development team:
krystianp
lehjr
Epinter
mmontuori
Official test team
zeljko1234
Hai_Duong
upndwn4par
Cocolopes
firecode95
Matada02
IM_back!
sidVici0us
Grey.Mouser.
ovitz
Q: What is the kernel status?
Testing the public alpha.
THE PUBLIC ALPHA IS HERE! CHECK UP IN THIS POST!
Q: What is working right now in the kernel? (05/19/2013)
Initial steps
Logs via JTAG [complete]
Boot Kernel on Olympus [complete]
Boot Android GUI [complete]
Modules fully working (They may have some minors bugs)
Logs via JTAG [complete]
Boot Kernel on Olympus [complete]
USB Drivers [complete]
Boot Android GUI [complete]
Audio drivers [complete]
Headphone Jack [complete]
Accelerometer [complete]
Touchscreen [complete]
Buttons Backlight [complete]
Hardware/3d acceleration [complete]
Buttons volume up+down and power [complete]
Wi-Fi Driver [complete]
Bluetooth Driver [complete]
Modem Driver [complete]
Fingerprint Kernel Driver [complete]
Proximity Sensor Driver [complete]
Light Sensor Driver [complete]
Compass Driver [complete]
GPS [complete]
Sleep/Wake-up [complete]
A/C Charging [complete]
USB Charging [complete]
Camera/Video Camera [complete]
ROM Assembly [complete]
Mobile / Cellular voice calling [complete]
Front Camera/Front Video Camera [complete]
Modules marked as "Work in Progress" (They may work, or not, but they are not complete)
Fingerprint ROM Libs+Framework [work in progress]
Flash (Sync with photos) [work in progress]
Modules marked as "Post-poned"
(This supposed to be a "not working" feature. It wont work soon, until stable release or something)
HDMI [post-poned]
Click to expand...
Click to collapse
Q: Where are the sources now/When will be them public avaliable?
They are in a private repo. Updates will be merged into github and status posted upon completion.
Q: Where can I see the bugs reported?
Issue tracking
Q: Is stable yet to be daily used?
No. This is a big NO. We have to be patient.
Q: Does it have a name?
No. But, there is a poll to get one.
Here is it. Thanks Cocolopes.
Q: How I can help the kernel development?
Well, there is many ways you can help:
Mainly donating money with paypal.
You can do so here. This is mmontuori's paypal, but it doesn't matter because they manage the donations internally.
Also you can give your Atrix away. Doesn't matter how it is, cause even if it doesn't boot, the pieces can be used for replacement.
You can do so, here. Thanks to jjwatmyself for make this posible.
There is a Paraguayan song singer that says "not good who help, but who do not f**k". No offense. Just a reminder that they are working for their own, so don't be mean.
Click to expand...
Click to collapse
Q: Should we hate Motorola for not giving us the ICS update?
No. Acording to krystianp, Motorola helped the team, and give them a little boost. We can't say they played fair, but at least they help a little.
Q: Will this kernel have [insert a basic feature here]?
Yes. It's expected to everything work. They can't make promises, but they sure are giving their best.
Q: Will this kernel have Webtop?
Maybe. Webtop, as far I know, it's ROM related. Motorola give the source of webtop 3.0, so whoever want it, can make it. But really, I don't know if we still need it.
Q: Will this kernel have [insert any mod or tweak here]?
ex: Processor overclock/undervoltaje, I/O tweaks, GPU overclock, USB fast charge, etc...
I dunno. But, the source it's open. Even you can make it. (Please, don't try this in home. That should be done for someone that know his stuff).
Q: Will this kernel have Linaro?
1º What Linaro is?
Linaro is a not-for-profit (NFP) engineering organization that works on consolidating and optimizing open source software for the ARM architecture, including the GCC toolchain, the Linux kernel, ARM power management, graphics and multimedia interfaces.
2º Q: So, will this kernel have Linaro?
krystianp says that he will look at it. But, not right now.
Q: If there any video of the kernel working already?
Yes. Here it's the official krystianp channel on Youtube.
Or you can try out yourself if you want. Chose your flavor up in this post and test it.
Q: Will this kernel have dual sim support?
I don't think so. That's hardware related. But, if the dual sim adapters have to have a part of software/kernel related, eventually it should be done.
Q: Will this kernel have [insert any app that have any rom]?
No. This is only kernel. ROM related, and app stuff will be added later.
This is not the final FAQ. But, I think it's pretty good point to start. I'll update it with anothers questions, so they wont be redundant in discussion thread.
REMEMBER
Off-topic post in the main development thread will be deleted, and you will have a warning. So use this thread, or the discussion one to make off-topic.
If you have some questions, I'll add it with its answer.
m1k3_ said:
This is an intent to make a FAQ for the 3.1 Kernel Development...
Click to expand...
Click to collapse
Hats off dude, GREAT FAQ
m1k3_ said:
Q: What ROM do I need to test the kernel?
MROM ICS. Or any ROM based on the "leaked ROM". eprint's ROM wont boot. Any else that are not based on leaked kernel, won't boot.
Click to expand...
Click to collapse
Not any ROM based on the leaked kernel works, "Somebody's" CM10 with "those libs" won't work.
sidVici0us said:
Not any ROM based on the leaked kernel works, "Somebody's" CM10 with "those libs" won't work.
Click to expand...
Click to collapse
Noted. Thanks you.
Besides for a quick run through spell check thank you very much. Now maybe (but not likely) the dev thread might be a bit cleaner..
Great job my friend
Nice thread which we wanted.....
m1k3_ said:
Q: Where is the main threat?
Off-topic post in the main development threat will be deleted, and you will have a warning.
Click to expand...
Click to collapse
Should be thread*
Thanks for this though.
atrix4g18 said:
Should be thread*
Thanks for this though.
Click to expand...
Click to collapse
Thanks you. There were more misspellings, but I kinda fix them. Hope there is no more of them. Thanks!
m1k3_ said:
Thanks you. There were more misspellings, but I kinda fix them. Hope there is no more of them. Thanks!
Click to expand...
Click to collapse
s/market/marked/
Thanks for this great FAQ!
REMEMBER
Off-topic post in the main development thread will be deleted, and you will have a warning. So use this thread, or the discussion one to make off-topic.[/CENTER][/QUOTE]
you are so kind to contain our off-talk
According github and my test compass and GPS work
Is there any show-stopper issue in developing modules?
Yes. Time.
I don't really understand the point and purpose of this question to be honest. Are you assuming the devs have the whole entire plan laid out in front of them and know exactly what's waiting ahead? No, they don't. They work at one thing (or a few at most) at a time, and then move on to the next thing, according to priorities (often times not my priorities or yours or theirs, mind you). They can't really know almost anything about the next thing until they start working on it.
delete
Is there any possibilities to make floating touch like Xperia Sola ?
aaurnab said:
Is there any possibilities to make floating touch like Xperia Sola ?
Click to expand...
Click to collapse
No, that's hardware. This is a software project.
atrix4g18 said:
No, that's hardware. This is a software project.
Click to expand...
Click to collapse
may be it is related with hardware.... but i feel in TWRP 2.1 touch is something like Floating touch...the buttons responses from certain distance. may be it was a BUG ....i am not sure....
That would be a faulty (overly sensitive) digitizer then. The Atrix touchscreen has only two states for a given coordinate - touched or not touched. As already stated, this is a hardware thing.
kanwlw said:
you are so kind to contain our off-talk
Click to expand...
Click to collapse
I don't understand what you are saying. But, in case you don't know, mmontuori change the rules of the main dev thread, talking even with a moderator to do it. So, it's not me.
That's because the main thread were full of off.topic with 20/30 messenges per week. Now, it is only about dev, and unofficial testers.
Zeljko1234 said:
According github and my test compass and GPS work
Click to expand...
Click to collapse
Well, maybe they do, but in the dev thread their category fall under "work in progress". When mmontuori changes it, I will too. In this way we will have the same info. .
Just throwing this out there, but are CM and TW ROMs intended to be in Android Development and only ASOP be in Original Android Development? It's difficult to determine sometimes whether a ROM is a CM, TW, or ASOP ROM as they're kind of intermixed within the Android Development. I'd think that CM and ASOP ROMs should be posted in the Original Android Development forum?
i do know there's a directory, but thanks to everyone developing for the S4 on Sprint!
Original development is anything based off of google code. AOSP such as CM
Anything based off the sprint TW rom goes in the other folder.
Yes, there are some in places they shouldn't be.
Developers are not always clearly indicating what the base of their rom is.
ASOP. Is The Same As CM. I See Difference. But A Big Difference With TW. Is The Bomb!
Sent from my SPH-L720 using xda app-developers app
I think some of the ASOP/CM roms that are not in original are Kangs from someone else, or a different phone all together.
Just an FYI guys, it's AOSP (not ASOP). Android Open Source Project.
I like to think that ROMs built from source belong in Original Dev. That means CM, AOSP.
Everything else goes in Android Dev. But sometimes it can get a little hazy.
pulser_g2 made some good distinctions regarding what should go where:
The following are most likely “Original Development”:
*Official releases of highly original and upstream custom ROMs (built from the ground up with significant original development within them)
*Official releases/development of such original ROMs, perhaps posted by the maintainer or their nominated person.
*A significant “first” in development for a device. Significant is subjective, but it is likely something which took considerable time/effort, and is generally accepted by developers to be significant and non-trivial.
*Significant port of a ROM from one device to another, giving enhanced features or functionality to users of the target device. The port should be beneficial (a port from two virtually identical devices isn’t original development, it’s winzipping, and nobody really benefits from this, as it’s not development)
The following are most likely not “Original Development”, and should be posted in the “Android Development” subforum:
*Your own “unofficial” stock build of your favorite original, source-built (or otherwise) ROM, particularly where an official or maintainer-endorsed thread exists already.
*Minor derivatives of other ROMs with little or no changes, or ROMs consisting of “placebo” features as a main constituent or claim.
*Renames or rebadges of others’ work – these don’t belong on XDA at all! Refer to rule 12 for more information.
*Reposts of existing ROMs with small changes (i.e. kitchen work, such as adding a couple of apps). If you could realistically distribute your changes as an “addon pack” above and beyond a ROM, you should do so. In addition, your “ROM” would not be original development as it would be substantially identical to the original ROM.
*A thread created with unrealistic goals that are clearly unachievable by those starting the thread. This is not intended to discourage high aspirations, rather to prevent threads porting Windows Phone 8 to the HTC Wallaby. This is pretty much common sense.
*A ROM where a main or significant claim/feature is graphical changes to the user interface (ie. Themed ROM)
Click to expand...
Click to collapse
A good explanation of Android Development vs. Original Android Development can be found here by one of the mods.
http://forum.xda-developers.com/showthread.php?p=41633683
Sent from my SCH-I545 using Tapatalk
my bad, that's my dyslexia kicking in there,
one thing that maybe as a suggestion is that the ROM devs can put in the subject line [AOSP] [TW] [CM], etc with what the base of the ROM is? I know there's not too many sprint ROMs out there, but those that do exist it's still a little difficult to search for each.