This is just an announcement...
Since I have to focus on my Advanced Level study in the coming term, I must apologize that the about distribution of my ROMs will be the last time within 2010.
I currently finished the cooking of ROMs based on build 21909(no 21911 as it has serious bugs), and I am going to release them now. In the future, I will release the ROMs based on builds 23127(23128 has serious bugs as well) and 23569.
On the other hand, I decided to re-cook the ROMs based on build 21057 - yes, the last build of WM6.1 - since there was fatal bug in the version WWE_040910_B2_DS. I haven't started it yet, but I will let you guys know whether the bug fixing is successful or not.
This is just a request...
Please, if anyone know how to perfectly fix the problem of "Internet Explorer cannot download blank." in the Internet Explorer in COM3 and later branches of build, tell me as soon as you can. I do not want to release a final ROM with bugs anyway...
In another word, if I cannot fix that, I may not release the COM3 and COM5 ROMs...
That's all.
Related
Just one caveat: I have done searches (read: multiple).
How in the world does CyanogenMod get to all of the supported devices? All of a sudden once CM9 is released, for phones/tablets moving from CM7 to 9, does it go out to all devices or what? Does it need to get ported from the source for each and every individual device? In general, how is CM updated and how does it get out to the officially supported phones/tablets?
Cyanogenmod ROMs do indeed have to be ported to each individual device and maintained. Once a device receives official support from the Cyanogenmod team, daily changes made to the AOSP source code (tweaks and bugfixes by the various contributing devs) are automatically compiled by a "buildbot" and released at the end of each day (thus these builds are called "nightlies"). These nightly updates are then made available for download through the Cyanogenmod website and through ROM Manager. Once code updates reach a certain plateau, a "final release"-worthy balance of features and stability, the build is released separately as a "stable" build (such as CM7.1), though you can still download it from the website or from ROM Manager just as with the nightlies. CM9 will eventually receive the same treatment and be released in the form of nightlies and stable builds.
Further (highly recommended) reading can be found here: http://www.cyanogenmod.com/blog/the-current-and-future-state-of-cyanogenmod-nightlies
Has anyone seen John Connor?
so the nightlies don't have to be ported, but every major revision does?
hugabu said:
so the nightlies don't have to be ported, but every major revision does?
Click to expand...
Click to collapse
No.
"Porting" is just a word used for the process of making the rom work on any certain device.
So to answer your question, once the work of porting CM to the certain device is done, that port is used as the base for both the stable and nightly builds.
Look at the analogy of when a new phone comes out, case manufacturers create a mold to use to make their cases fit the certain phone, and that mold is used to make all kinds of cases. Same concept
I do apologize for the early release of my ROM, in my opinion its an Alpha stage at the moment due to the fact it has no "Network Data". Which to me is a deal breaker.
List of known bugs:
-No Network Data (You can still make/receive calls & text)
-On first boot you will get a couple of FC's for Network Location (I think)
-Setting of Ringtones (I haven't bothered to seek a solution)
-MiHome is a Beta (It has Chinese mixed in, used this one as it was a simply solution to constant FC)
-Themes (Need to create a directory /data/system then setting proper permission's)
-Browser (Desktop mode?)
-Several apps still have Chinese (least of my concerns)
-Any bugs not mentioned in the latest unOfficial CM10
I do feel like the Data issue is a Framework problem
I had intended to release the ROM to a select few and get there opinion or suggestion of a solution. But decided to wait at the last minute yesterday after posting on Dev-Host, due to a conversation with the original MIUI I made the port from. He has the exact same bug with his port and spent a month attempting to correct the problem. The port he came from does not have the bug and I'm suppose to receive a copy of it soon. To restart the project from the original Port, not the Port of an Original ROM that is MIUI officially supported.
I do expect to have a complete rework within a day or two from the Original MIUI.
I'm going to attach a logcat & if a developer has time or would be interested in a link to the ROM I would happily share that with them.
A bit of my background is that I once upon a time developed for Motorola Cliq 2 and had a couple of ROM's, Mod's, Themes for it a few years back, also a Moderator for a Forum for the Cliq 2. Due to schedule changes I've gotten away from developing because of that, and had hoped to once again contribute to the android community.
CREDITS:
sportsstar89 for his work aswell and bringing hope to the device
dcacklam for all the hard work on the CM10 audio/bluetooth bugs
chiragkrishna for his allowing his work to give reboot into recovery/bootloader
cyanogenmod
MIUI
Extra special "Thanks" for letting me use their ROM to port ZeRo2o9 &
rafyvitto
Dear all,
i own an Xperia P, now after all this while i know having a novathor chipset in our device is a curse. now We have atleast 10 roms based on latest 4.4 kitkat based on CM but each of it have bugs. this has been the case with all the previous CM versions. My Question is "Is it ever gonna happen that we would get a bug free,at least all the features enabled cm 11 version or its gonna be like all the other versions where the dev skips to the next version as soon as it arrives leaving the older version behind."
if thats the case then it time to sell my device and move on to another one. !!
Regards.
Joker. said:
Dear all,
i own an Xperia P, now after all this while i know having a novathor chipset in our device is a curse. now We have atleast 10 roms based on latest 4.4 kitkat based on CM but each of it have bugs. this has been the case with all the previous CM versions. My Question is "Is it ever gonna happen that we would get a bug free,at least all the features enabled cm 11 version or its gonna be like all the other versions where the dev skips to the next version as soon as it arrives leaving the older version behind."
if thats the case then it time to sell my device and move on to another one. !!
Regards.
Click to expand...
Click to collapse
Check this out:
http://forum.xda-developers.com/xperia-u/general/aosp-xperia-p-sola-t2684583
and keep your fingres crossed
Cheers
Cwikla
Well, that's about AOSP and while getting it perfect will certainly be a major step for a perfect CM some implementations are different (in fact this was a key factor in choosing to focus on AOSP -- upstream CM changes very often)...
About Bluetooth audio, it's almost a given everyone's waiting for the next version of Bluez (which will then need porting and experimentation) while for FM some progress by trial and error is apparently being made, and thank the ex STE company and their partners for radio support not having been ready a good 2 years ago...
Hi.
I don't know if this is the right place for posting or not. But I just wanted to share it with you guys.
I was a fan of Simple AOSP ROM on my Nexus 4 back in the day. According to me, it had all the essential features for a ROM.
Now I have switched to OP2. The development of OP2 was very slow in the early stages but now it has picked up pace.
Keeping that in mind, I want to request someone to please build this ROM for our OP2. Since I have no idea or the time to build it myself, I would love to see someone take this up.
Here is the official source code - https://github.com/SAOSP-M
Regards,
Reserved.
I'm not a developer myself but I do try and flash the roms on my OP2. Not sure if you yourself are a developer so please ignore if you already have checked these, but Paranoid android, Exodus are all aosp based.. and this, http://forum.xda-developers.com/oneplus-2/orig-development/rom-aosp-caf-oneplus2-t3386553
I think is purely aosp-caf based.
I don't know if I'm out of line suggesting an alternative rom but, http://forum.xda-developers.com/oneplus-2/orig-development/rom-halogenos-oneplus-2-t3377799
Similar to the suggestion above but is way more current. June security update, beta 2 released today.
So, i saw many comments about asking about Nougat, features and stuff... that maybe could be solved all that questions in a thread. If this is pointless, just i'll ask an admin to clean this up... but the point of this thread is solve so common questions about the newer builds of nougat.
This build is stable?
The build is very stable, but not at the point of MM. There's some less battery performance but after all: that builds are in an alpha/beta stage, so... this things could happen. But after all, it works smoothly.
Nice rom, but when you can update it? When you'll fix the bugs?
Everybody's just love when there's an update date or release date, we know it. But please, don't ask ETA. It may annoy the developer, and after all, we're human and we have things happening in real life, so maybe the real life business take over the dev's time to make changes and test it. Be patient, please
There will be a fix for video recording?
The dev's (at this date) are working on it. The known workaround that could be useful is: You can use Cameringo Lite to solve it.
CM14 ONLY: There's CMTE? Can i use themes? X feature doesn't work, what's happening?
By now, the CM people it's working and rebasing their work on the new nougat AOSP. Maybe in october (or when they have it ready) they'll implement slowly all those features. And if some feature doesn't work on the CM14 version, please, remember: that's an alpha build and CM team is working to make it work. By now it doesn't seems to work but, it's an alpha build, that thing could happen.
If you want to theme your device, you could try substratum by now.
This doesn't work on X device, please help
Reporting issues are more useful to devs if you log it. If you have an USB, search in google how to install ADB and use logcat. If you can use the device, you can install catlog, record the log and replicate the issue. After that, copy or upload the log and send it to the dev.
Hope this helps!
will u build cm14 for vee3 ?