Database Develop

[TOOL/DEV Q] My username is Cynagen, I'm a flashaholic

I've recently come to the conclusion that I'm a flash-a-holic, and in order to facilitate my need for speed from my device, extended battery performance, and just the best overall experience from my phone (it's been a LONG time since I've ever been completely happy with one of my phones), I have started drawing up specs for an all-around Thrill tool which will incorporate all the tools into a fully automated process (with prompts for certain things of course asking that you confirm the action has been done if it can't be detected) to help speed up the process and take some of the guess work out of it all.
All-in-all I've reflashed my Thrill about 20+ times in the past 3 months, and while I've 'settled' for now, I see that with the hopefully upcoming ICS release, and the daunting task of flashing that is presented to all users currently, a tool which incorporates all steps of the process and attempts to simplify it to "Select which ROM you wish to flash" "it is recommended that you use X baseband for that ROM, however you can choose another at your own risk", and click Go, the rest of the process is handled by the tool, might be desired.
The aim of this tool would be to make first time flashers a little less intimidated by the plethora of steps required by simplifying them down as much as possible and handling as much as possible in the background. However it would also provide flash-a-holics like myself a quick system by which to refresh the ROM on the phone or switch to another to try it out.
Steps I'd like to see the tool perform for folks:
Flash baseband/stock ROM
Rooting (based on which version you select, it will select either SuperOneClick or Megatron automatically.)
Installing CWM (Touch only for select ROMs (or override with warning), regular otherwise for everyone else)
Copy to phone as update.zip the desired ROM
Optionally, should an overclocked Kernel be selected, afterwards, another update.zip for the Kernel.
I'd like some thoughts on this and some guidance before I start really digging in. Couple of my main questions are as follows:
First, is this even needed anymore with the plethora of information available? Yes, it coalesces most of those steps documented into a simple interface tool, however do people prefer to keep everything broken up, I know I don't, especially when it's all towards one goal.
If there is still a need/desire for a tool like this, how in-depth on options would people like to get?
What would the developers like to see available from a developer's standpoint?
What would the end-users like to see available from the interface?
I would love any feedback on this idea before I move forward so I have a clear picture of what it is that the community would like.
Thank you for your time and feedback folks.

Welllll.
Acidhazard kitchen rom I know you have used. The build interface Is a great format to start with. Has a few automated tools built in. Probably a novice or advanced select. That would appeal to newbie and testers alike . An updatable base and tool would be great. Hunting for base bands is a pain and having it all in one handy tool would be lovely.

This is a good idea. I would make it so it cannot flash a ROM if the correct baseband isn't there to help new people avoid bricks. I think that is the biggest fear for people new to flashing.
Sent from my LG-P925g using xda app-developers app

SithLord2K said:
This is a good idea. I would make it so it cannot flash a ROM if the correct baseband isn't there to help new people avoid bricks. I think that is the biggest fear for people new to flashing.
Sent from my LG-P925g using xda app-developers app
Click to expand...
Click to collapse
The only way you would be allowed to override the baseband is if you were in advanced mode and filled in a checkbox accepting the consequences of your choice. I've had wrong baseband before and had a working phone with no service. It's possible it's not fun but it's possible, and yes, for basic mode it would be forced to only the accepted list of basebands for the ROM you wish to install.
Cab121 said:
Welllll.
Acidhazard kitchen rom I know you have used. The build interface Is a great format to start with. Has a few automated tools built in. Probably a novice or advanced select. That would appeal to newbie and testers alike . An updatable base and tool would be great. Hunting for base bands is a pain and having it all in one handy tool would be lovely.
Click to expand...
Click to collapse
The idea here is not to duplicate somebody else's work, but instead augment it and enhance it further. While his tool is awesome, it's also command line, my tool will end up being a user-friendly GUI. I would love to end up with a multi-ROM kitchen for the O3D and Thrill (P920 & P925 respectively) built into this tool, it's not a priority for the beginning. I will be studying heavily the scripts used by some of these wonderful tools in an effort to duplicate their efforts contained within a GUI. I don't plan on writing something that just runs these tools in the background and makes the selections for you, I'm talking a complete tool from the ground up. I think I may write a helper tool for inclusion to the ROMs it builds which I can use to help facilitate this process in a much more friendly manner. (So you have to touch the phone less.)

Cynagen said:
The only way you would be allowed to override the baseband is if you were in advanced mode and filled in a checkbox accepting the consequences of your choice. I've had wrong baseband before and had a working phone with no service. It's possible it's not fun but it's possible, and yes, for basic mode it would be forced to only the accepted list of basebands for the ROM you wish to install.
The idea here is not to duplicate somebody else's work, but instead augment it and enhance it further. While his tool is awesome, it's also command line, my tool will end up being a user-friendly GUI. I would love to end up with a multi-ROM kitchen for the O3D and Thrill (P920 & P925 respectively) built into this tool, it's not a priority for the beginning. I will be studying heavily the scripts used by some of these wonderful tools in an effort to duplicate their efforts contained within a GUI. I don't plan on writing something that just runs these tools in the background and makes the selections for you, I'm talking a complete tool from the ground up. I think I may write a helper tool for inclusion to the ROMs it builds which I can use to help facilitate this process in a much more friendly manner. (So you have to touch the phone less.)
Click to expand...
Click to collapse
When you ready my scripts, just know, it's in English. Lmao.
Literally, command prompt code.

The Dark Lestat said:
When you ready my scripts, just know, it's in English. Lmao.
Literally, command prompt code.
Click to expand...
Click to collapse
This isn't my first ro-day-oh here guys... I'm the bastard that wrote the PeerGuardian 2 Vista Loader to get PG2 working on Vista when it was still in beta (and buggy as hell).

Cynagen said:
This isn't my first ro-day-oh here guys... I'm the bastard that wrote the PeerGuardian 2 Vista Loader to get PG2 working on Vista when it was still in beta (and buggy as hell).
Click to expand...
Click to collapse
Oh, that's not it. Every time someone opens my script, they ask why they can understand it.
Sent from my Samsung Galaxy S II w/AOKP

The Dark Lestat said:
Oh, that's not it. Every time someone opens my script, they ask why they can understand it.
Sent from my Samsung Galaxy S II w/AOKP
Click to expand...
Click to collapse
LMFAO most languages are surprisingly in english, it's kinda weird, cause I know a couple that were NOT developed here in America or the UK.

Cynagen said:
This isn't my first ro-day-oh here guys... I'm the bastard that wrote the PeerGuardian 2 Vista Loader to get PG2 working on Vista when it was still in beta (and buggy as hell).
Click to expand...
Click to collapse
Then you are also my hero. That came in handy when the rest of us where screaming at our machines having dealt with Vista and any torrent work.
I was under the impression your original plan here was to utilize the tools and data available from various sources "AcidHazard, Megatron and so on" to achieve the wonderful multipurpose and expandable tool you have decided to develop. We are here to help. More especially since your calling upon it. Plenty of communication , feedback, and patience is what I prescribe here. That being laid out :fingers-crossed: we can continue.
Ok so with all respect, credentials, history, contribution, and hero work established and being taken in to consideration as I type lets define a few of your plans further and designs ideas further so we might better contribute to your efforts. This is an awesome idea and I think its something we all need desperately. I realise the following will seem very redundant and you may feel its unnecessary but trust me it will help everyone from this point on.
Question 1
The principal function of this tool is to perform the primary tasks associated with rooting, flashing, and customizing? This would initially entail the following core tasks?
Flash baseband/stock ROM
Rooting (based on which version you select, it will select either SuperOneClick or Megatron automatically.)
Installing CWM (Touch only for select ROMs (or override with warning), regular otherwise for everyone else)
Copy to phone as update.zip the desired ROM
Optionally, should an overclocked Kernel be selected, afterwards, another update.zip for the Kernel.
Question 2
Your plan is to use and or augment current work and material already available to achieve the majority of the above tasks essentially wrapping it all up in a very nice and tidy singe tool?
Question 3
Your goal in the front or interface is to have a GUI and stay away from automated command line ?
Question 4
How in depth and to what degree did you want to deal with any updates. Baseband and so on? Will files pull from a server, file host or other source? Or shall it be with the interface itself and the user hunts for the files then points to where they are located?
Question 5
How will devs offer there roms to your tool? Probably directly related to Q4.
Question 6
Where the heck is Waldo?
Question 7
Can you provide us with a little copy paste form for us to add feature requests? Should make things much simpler when your sifting threw the thousand posts your gonna get when this thing is live.

(continued)
Question 8: Why is this not in General?
Anyway, I think that some bits are pretty much impossible, for example flashing the baseband since you need the LGMobileTool for that or SmartFlash, command prompt or adb or fastboot won't work for this at all. Otherwise I would say it's doable, but it probably won't be from me unless I remember to do it in December and no one else has done it yet :/

Cab121 said:
Then you are also my hero. That came in handy when the rest of us where screaming at our machines having dealt with Vista and any torrent work.
I was under the impression your original plan here was to utilize the tools and data available from various sources "AcidHazard, Megatron and so on" to achieve the wonderful multipurpose and expandable tool you have decided to develop. We are here to help. More especially since your calling upon it. Plenty of communication , feedback, and patience is what I prescribe here. That being laid out :fingers-crossed: we can continue.
Ok so with all respect, credentials, history, contribution, and hero work established and being taken in to consideration as I type lets define a few of your plans further and designs ideas further so we might better contribute to your efforts. This is an awesome idea and I think its something we all need desperately. I realise the following will seem very redundant and you may feel its unnecessary but trust me it will help everyone from this point on.
Question 1
The principal function of this tool is to perform the primary tasks associated with rooting, flashing, and customizing? This would initially entail the following core tasks?
Flash baseband/stock ROM
Rooting (based on which version you select, it will select either SuperOneClick or Megatron automatically.)
Installing CWM (Touch only for select ROMs (or override with warning), regular otherwise for everyone else)
Copy to phone as update.zip the desired ROM
Optionally, should an overclocked Kernel be selected, afterwards, another update.zip for the Kernel.
Question 2
Your plan is to use and or augment current work and material already available to achieve the majority of the above tasks essentially wrapping it all up in a very nice and tidy singe tool?
Question 3
Your goal in the front or interface is to have a GUI and stay away from automated command line ?
Question 4
How in depth and to what degree did you want to deal with any updates. Baseband and so on? Will files pull from a server, file host or other source? Or shall it be with the interface itself and the user hunts for the files then points to where they are located?
Question 5
How will devs offer there roms to your tool? Probably directly related to Q4.
Question 6
Where the heck is Waldo?
Question 7
Can you provide us with a little copy paste form for us to add feature requests? Should make things much simpler when your sifting threw the thousand posts your gonna get when this thing is live.
Click to expand...
Click to collapse
Question 1
{
"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"
}
The principal function of this tool is to perform the primary tasks associated with rooting, flashing, and customizing?
Yes, with the goal of expanding over time to include such things as a kitchen for all thrill ROMs like the acidhazard kitchen. Possibly even the UOT.
Question 2
Your plan is to use and or augment current work and material already available to achieve the majority of the above tasks essentially wrapping it all up in a very nice and tidy singe tool?
That's a possibility however it makes more sense to convert most of these tools into the native language of the new tool. For initial purposes this will be AutoIt. Should enough Linux and Mac interest be generated a PHP using GTK front-end with the autoit version becoming depreciated.
Question 3
Your goal in the front or interface is to have a GUI and stay away from automated command line ?
The goal is to write one EXE to incorporate all tools needed for the basic flashing functionality needed to go from anything to stock and follow the process up to custom ROM and kernel. From there, again with sufficient feedback, development would continue and new features incorporated. Backend tools can change how they operate thus requiring a new patch every version, processes don't change too much and keeping up with developments won't be as hard. This in turn frees up time to design an actual gui over using automated command-line.
Question 4
How in depth and to what degree did you want to deal with any updates. Baseband and so on? Will files pull from a server, file host or other source? Or shall it be with the interface itself and the user hunts for the files then points to where they are located?
Updates for things such as what you listed? Basebands, ROMs, necessary tools like adb, and the like? Why not all of those wonderful ideas? This will give ease of access during operation and once depreciated for years the option to pack the tool in a zip file with their favorite ROMs and modifications ready to be used once unpacked.
Question 5
How will devs offer there roms to your tool? Probably directly related to Q4.
Many options are available, private hosting, directly submitting to the project website (which will keep the tools files up to date automatically), allowing users to download and select locally.
Question 6
Where the heck is Waldo?
I haven't the foggiest.
Question 7
Can you provide us with a little copy paste form for us to add feature requests? Should make things much simpler when your sifting threw the thousand posts your gonna get when this thing is live.
Do you one better, an email address. I use my forum posts as tech support for the application, so things don't end up cluttered. Yes it means I'm bound to get two or more emails regarding the same suggestion but that's fine by me if it means that the public information is directly useful.
Sent from my LG-P920 using xda app-developers app

moved to general.

Only thing else I can think of that would be a huge advantage would be a theme compiling tool and a debug log that could be used as a resource for you and the Devs who work on the roms. Can't wait to see what you create because even 1/2 of this would be awesome.

Cab121 said:
Only thing else I can think of that would be a huge advantage would be a theme compiling tool and a debug log that could be used as a resource for you and the Devs who work on the roms. Can't wait to see what you create because even 1/2 of this would be awesome.
Click to expand...
Click to collapse
A theme compiling tool is harder to make than you think. Even compiling a theme is hard to do if you don't know what you're doing.
Heck. I had a hard time compiling a theme, but then again, LG borked everything so I had to do the run around.

The Dark Lestat said:
A theme compiling tool is harder to make than you think. Even compiling a theme is hard to do if you don't know what you're doing.
Heck. I had a hard time compiling a theme, but then again, LG borked everything so I had to do the run around.
Click to expand...
Click to collapse
Very true. I have not done it so I can't really offer a valid opinion. Would be awesome though albeit a pipe dream lol.

Cab121 said:
Very true. I have not done it so I can't really offer a valid opinion. Would be awesome though albeit a pipe dream lol.
Click to expand...
Click to collapse
If somebody else has the process mapped out already, I'm looking at you Lestat, I can clone it and present it in an easy to manage fashion that can be adopted by many users. This is only if steps are documented, I don't exactly have time to do any research into hacking an Android.

Cynagen said:
If somebody else has the process mapped out already, I'm looking at you Lestat, I can clone it and present it in an easy to manage fashion that can be adopted by many users. This is only if steps are documented, I don't exactly have time to do any research into hacking an Android.
Click to expand...
Click to collapse
I don't have it mapped out, but I can map it out pretty quickly.
Here's a ROUGH draft.
First, there can be two types of "theme kitchens".
Automatic
Non-Automatic
An automatic theme kitchen is usually going to be for one device.
A non-automatic theme kitchen can be used for a broad range of devices.
Automatic - Not familiar with code
Non-Automatic - Familiar with code.
Here's the draft for the automatic, and yes, I'm typing this as I go. Lol
Automatic
Extract theme files from phone. (usually framework-res.apk & SystemUI.apk for Gingerbread)
Decompile theme files
Choose what theme element you want
Automatically overwrite UI element (.pngs, .xmls, and other files) - Go back to number 3 UNTIL the loop is closed. (Finished with theme)
Compile theme files
Push files to phone
Set permissions
Wipe dalvik-cache and cache
Reboot phone
/End
Here's the draft for the Non-automatic.
Non-Automatic
Extract theme files from phone. (usually framework-res.apk & SystemUI.apk for Gingerbread)
Decompile theme files
USER APPLIES THERE OWN THEME ELEMENTS
Compile theme files
If error occurs while compiling, go back to number 3.
Push files to phone
Set permissions
Wipe dalvik-cache and cache
Reboot phone
/End
Just a simple map of what to do. Of course, putting it into code is a lot easier when you have the correct files.

They need flashaholics anonymous. Then maybe I wouldn't flash people on the streets. >_>
Oops, wait. Wrong subject matter.
P.S. This was just a joke, something to get a laugh out of people.

cmarriner82 said:
They need flashaholics anonymous. Then maybe I wouldn't flash people on the streets. >_>
Oops, wait. Wrong subject matter.
P.S. This was just a joke, something to get a laugh out of people.
Click to expand...
Click to collapse
Dood, back when I had my netbook I used to flash people on the street all the time, the ones with some time and a couple bucks.
P.S. I totally loved your joke and well, had to answer honestly, as a joking response, even though I used to do this exact thing.
Anywhos... I expect to have a test-tool released next week which when you run it, it will allow me to collect some data on the environments (submitted anonymously back to my dev box), ask you a few questions, and collect some data from the phones themselves if they are connected and in debug mode at that time (which I hope everyone does as this is HUGELY important). With the test tool, I'll have it report whether or not your phone will be supported as it stands right now (plug and play), or at least recommend changes (drivers, software, phone version, etc) to make it compatible.
I'm also thinking of the name "Thrilling Toolkit" for the end product, what do you all think?

Sounds good. Can't wait to try it.
Sent from my LG-P925 using xda app-developers app

[REQUESTS]Porting I9300 Roms to I9305

For all Porting discussions and requests hopefully they get answered. I think soon once a Dev knows what they are doing, this will be the case he will work with all the i9300 Rom Devs and work on porting them to I9305.
Hopefully. . Lol

I'm suspecting not that hard - in fact i am now porting ... seems to have good progress =]

it wont be long when devs start to play with I9305, we just need to keep this forum active and help people like Kazuni with their rom testing

_ray_ said:
it wont be long when devs start to play with I9305, we just need to keep this forum active and help people like Kazuni with their rom testing
Click to expand...
Click to collapse
I can't guarantee my promptly reply on debugging and feature requests, but they are welcome. After all I have a pretty hectic daytime job

kazuni said:
I can't guarantee my promptly reply on debugging and feature requests, but they are welcome. After all I have a pretty hectic daytime job
Click to expand...
Click to collapse
any chance of ASOP any time soon? in your opinion...

Hope so, will make rom development alot eaisier if they can just port them accross for us

had hypergalaxy ported to my device... now trying to get the FC out... and trying to figure out abt the signal lost...

with so much debate of whether the I9305 supports fm radio I wonder if anyone has ported the I9300 radio app/firmware to settle the argument. not that i really care about fm radio lol...

springah said:
any chance of ASOP any time soon? in your opinion...
Click to expand...
Click to collapse
AOSP would be a bit difficult for me, as I am not very good at working on AOSP materials however I will still investigate porting something like CM/MIUIv4 over when I got some time this weekend

cyborg24 said:
with so much debate of whether the I9305 supports fm radio I wonder if anyone has ported the I9300 radio app/firmware to settle the argument. not that i really care about fm radio lol...
Click to expand...
Click to collapse
ive tried few fm radio and is not working with our stock kernel..

kazuni said:
AOSP would be a bit difficult for me, as I am not very good at working on AOSP materials however I will still investigate porting something like CM/MIUIv4 over when I got some time this weekend
Click to expand...
Click to collapse
How about AOKP? Or is CM AOKP....?
Also, which part of the rom is it that is making things like the toggle switches big, green and ugly, and not a stock JB look of small and blue?
Like this :
{
"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"
}

singlecell83 said:
How about AOKP? Or is CM AOKP....?
Also, which part of the rom is it that is making things like the toggle switches big, green and ugly, and not a stock JB look of small and blue?
Like this :
Click to expand...
Click to collapse
AOKP is a complete new set of material to work with - it requires custom kernel building and additional proprietary drivers, and fortunately samsung has provided I9305 as open source already; however, i am not familiar with kernel building on android, so I probably won't be working on CM based builds unless I can gain some more knowledge :\ Sorry.

Fm radio will not work if the kernel does not support it, and if the kernel that came with firmware which didnt have FM radio pre-installed then it wont be programmed to support it, Basically meaning no drivers. Mick.Wheels was working on compiling a kernel to support FM but he is now on holidays so gotta wait. This guy caled Weeeo was reveiwing a I9305 for his sponsor SamsungUK apparently, But I saw his video on youtube and it was showing the FM radio app , so i asked him if he could test it which he did and was working fine. so I am in the middle of asking him to create a nandroid for us to play with. He is currently waiting for a replacement phone as his screen was scratched. So will see what happens then when it returns. Exciting timessssss

btemtd said:
Fm radio will not work if the kernel does not support it, and if the kernel that came with firmware which didnt have FM radio pre-installed then it wont be programmed to support it, Basically meaning no drivers. Mick.Wheels was working on compiling a kernel to support FM but he is now on holidays so gotta wait. This guy caled Weeeo was reveiwing a I9305 for his sponsor SamsungUK apparently, But I saw his video on youtube and it was showing the FM radio app , so i asked him if he could test it which he did and was working fine. so I am in the middle of asking him to create a nandroid for us to play with. He is currently waiting for a replacement phone as his screen was scratched. So will see what happens then when it returns. Exciting timessssss
Click to expand...
Click to collapse
That would be great. On one hand we have a dev that would try to compile the kernel from source - which means we could (in future) adding overclocking support, init.d support, amongst a few things.
On the unfortunate part is that, I've contacted gokhanmoral and confirmed that works on LTE model will not be done since there are not enough time nor the actual hardware. It would be great if someone can pickup the source from git and see if there are anything we can do to make a branch.

I was also looking into porting CM. But as of today I haven't found time to get a new build environment up and running. Maybe I'll look into it later today. As far as I saw it shouldn't be too hard to port CM from 9300... But on the other hand I have less experience with Samsung phones than with their TVs Anyway, if I get some progress you will be the first to know about it.
Gesendet von meinem GT-I9305 mit Tapatalk 2

I have an i9300, and just stumbled onto this thread. If someone can give me a system dump there is a good chance I can compare both of them and see the differences between the i9300 and i9305. It shouldn't be too different, probably requiring some minor changes to get this working (the main difference here is only the radio to support LTE and the extra RAM)
Sent from my Transformer Pad Infinity TF700T using xda app-developers app

I will give you what you need, I have just PM'd you ... You have the Brain I have the Game (I9305) looll Letz Do dizzzz braaa Team LIQUID indhouse lol

hiemanshu said:
I have an i9300, and just stumbled onto this thread. If someone can give me a system dump there is a good chance I can compare both of them and see the differences between the i9300 and i9305. It shouldn't be too different, probably requiring some minor changes to get this working (the main difference here is only the radio to support LTE and the extra RAM)
Sent from my Transformer Pad Infinity TF700T using xda app-developers app
Click to expand...
Click to collapse
If that is all the differences are, and the 9305 parts can be implemented into a 9300 rom, does that mean we could convert any custom 9300 rom into a 9305 rom? Or am I just dreaming?

singlecell83 said:
If that is all the differences are, and the 9305 parts can be implemented into a 9300 rom, does that mean we could convert any custom 9300 rom into a 9305 rom? Or am I just dreaming?
Click to expand...
Click to collapse
Most of the time yes, because we just have to be careful about integrating the drivers for the modem. I'm not so sure about CM/AOKP roms since they have their own built drivers. I'm unfortunately not familiar with driver building so perhaps someone else can shed some light on this topic hopefully.

Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums & Read the Forum Rules
Thanks ✟
Moving to Q&A

[ROM][AOSP] [Nightly/Release] CarbonRom JB [MB886]

About Carbon
CarbonRom is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look at, build, and use our code on CarbonDev GitHub.
We would like to thank CyanogenMod for their device trees, framework/settings mods and their code that was incorporated into this project. We also extend our gratitude to the devs whose code that we have incorporated. Proper authorship has been maintained and can be viewed on our repository.
Special thanks also go to Slim Rom for some of their features, PA, AOKP, and anyone else we may have borrowed commits from that hasn't been mentioned here. If you feel you have been unfairly left out, please - let us know.
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.
Screenshots
{
"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"
}
Carbon Updates
Join us on these Social Media Channels to keep yourself up-to-date on all the latest Carbon news, updates, contests, and more! Join our completely open Google+ community for insider conversation with devs and other users.
Download Carbon
All Carbon downloads and further information such as features, changelog, and FAQ can be found on our goo.im page.
http://goo.im/devs/carbon
Changelog
For a detailed changelog, check out the changes made each night here:
Change Log
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 goo.im page linked above. It's new, but expanding fast. Just like us!
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Ask a question on our IRC channel. Connect to #teamcarbon on irc.freenode.net or click here. You'll find several other Carbon fans and usually one or more devs as well. Please be polite.
Who is Team Carbon?
Andros11
BigShotRob
Bionic Beast
dg4prez
Kejar31
mattmanwrx
morfic
nocoast
pixeldotz
slick_rick
winner00
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!
​

Buglist​
Some (not all) seem to experience issues with GPS. If you have issues with GPS, please flash the official JB from Moto/your provider and then flash Carbon. GPS should work now. (I've also heard you can just flash back to stock, get a lock, then flash Carbon again...)
While capturing a picture to send via MMS, ensure HDR is deselected - Gallery will cause a force close if HDR is enabled!! (Note - HDR works for normal still photos, just not MMS.)
Update Google Search (manual update), or else any voice searches will fail with FC. Update the app, and it is resolved.

Please use the provided gapps below. They are the official Google ones for 4.3.
gapps-jb-20130813-signed.zip Mirror #1 Mirror #2

Alright folks! I have submitted the merge requests, I really hope they make it for tonight's run of nightlies... I can upload the build I rolled as a test if needed, no worries!

What are the chances of gps working? And blue tooth audio lol.
Sent from my PACMAN MATRIX HD MAXX

It's nice to see some official development going on here. I'll download to test tomorrow after school.
Sent from my MB886 using xda app-developers app

deeje00 said:
What are the chances of gps working? And blue tooth audio lol.
Click to expand...
Click to collapse
Seconded on the BT audio. I don't have an aux hooked up in my car, and USB audio isn't a thing with this phone, so BT audio is how I listen to my music. Must have for me!
This ROM looks pretty nice though! Can't wait to give it a try!

deeje00 said:
What are the chances of gps working? And blue tooth audio lol.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
thedeany said:
Seconded on the BT audio. I don't have an aux hooked up in my car, and USB audio isn't a thing with this phone, so BT audio is how I listen to my music. Must have for me!
This ROM looks pretty nice though! Can't wait to give it a try!
Click to expand...
Click to collapse
You guys are going to have to tell me... I don't have the device (see the OP), and thus I cannot test.
What I can tell you is my device (Photon Q) is the same SoC... so in theory it should work the same. BT audio streaming and GPS both work great here.
If you folks have run the CM10.1 build from epinter, the buglist there basically applies here.

arrrghhh said:
You guys are going to have to tell me... I don't have the device (see the OP), and thus I cannot test.
What I can tell you is my device (Photon Q) is the same SoC... so in theory it should work the same. BT audio streaming and GPS both work great here.
If you folks have run the CM10.1 build from epinter, the buglist there basically applies here.
Click to expand...
Click to collapse
Well, from what I've understood from other posts, the BT audio is dependent on the kernel, correct? And since we don't have an official 4.2 release, and thus no kernel, BT audio is dead right now. Would the Photon still be the same kernel?

thedeany said:
Well, from what I've understood from other posts, the BT audio is dependent on the kernel, correct? And since we don't have an official 4.2 release, and thus no kernel, BT audio is dead right now. Would the Photon still be the same kernel?
Click to expand...
Click to collapse
Well a lot is dependent on the kernel. BT audio depends on many things, there are some aspects of the kernel that do depend on BT audio... the kernel is basically the interface between the OS and the hardware, so the kernel definitely touches a lot!
Perhaps I should make this more clear. If you have any issues with this CM10.1 ROM, then you will probably have the same issues with this ROM.
Again, I do not have an Atrix HD, I am only supporting this device because the SoC is identical to a moto device I do own... So help me out, run it, let me know what's wrong with it... and I can certainly try and fix it, but unfortunately without the device it won't be easy. I will do my best!

arrrghhh said:
Well a lot is dependent on the kernel. BT audio depends on many things, there are some aspects of the kernel that do depend on BT audio... the kernel is basically the interface between the OS and the hardware, so the kernel definitely touches a lot!
Perhaps I should make this more clear. If you have any issues with this CM10.1 ROM, then you will probably have the same issues with this ROM.
Again, I do not have an Atrix HD, I am only supporting this device because the SoC is identical to a moto device I do own... So help me out, run it, let me know what's wrong with it... and I can certainly try and fix it, but unfortunately without the device it won't be easy. I will do my best!
Click to expand...
Click to collapse
Thank you for the explanation! It's pretty late tonight, but I'll try to flash this tomorrow and let you know what's working and not working for me!

Thanks for the rom. Funny thing is I almost compiled this Sunday. I've seen that branch in the repos and was curious as to what it was. Gonna try it out later.
Also, thanks for the GPS tip. I was on ICS before I started playing with custom roms so I'll flash stock (ugh) and see if that helps. Probably later tonight, I just got up and need to see what needs to be done today. I don't play with my phones when crap might need to be done.

Same problem as other 4.2.2 roms, bluetooth audio does NOT work

tvd0405 said:
Same problem as other 4.2.2 roms, bluetooth audio does NOT work
Click to expand...
Click to collapse
Any issues in the CM10.1 ROM are likely going to be present here.
Interesting tho that my device, same SoC does not suffer from this bug. Will see what I can unearth.

skeevydude said:
Thanks for the rom. Funny thing is I almost compiled this Sunday. I've seen that branch in the repos and was curious as to what it was. Gonna try it out later.
Also, thanks for the GPS tip. I was on ICS before I started playing with custom roms so I'll flash stock (ugh) and see if that helps. Probably later tonight, I just got up and need to see what needs to be done today. I don't play with my phones when crap might need to be done.
Click to expand...
Click to collapse
Actually I've found going back to stock ICS fixed GPS whereas stock JB did not.
Sent from my Atrix HD using Tapatalk 4 Beta

Youngunn2008 said:
Actually I've found going back to stock ICS fixed GPS whereas stock JB did not.
Sent from my Atrix HD using Tapatalk 4 Beta
Click to expand...
Click to collapse
Its never fixed it for me. Are you doing fast boot flashes? I got laid off and no data cord so i have to wait
Sent from my MB886 using xda app-developers app

TTLayland said:
Its never fixed it for me. Are you doing fast boot flashes? I got laid off and no data cord so i have to wait
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
Yeah you have to fast boot all the ICS files from the sbf except of course the getvar and first line in the XML. That way you get all the proper drivers rolled back. Then flash the cwm recovery IMG in fast boot and boot to recovery and flash a custom ROM, usually after this it'll work at least with the xt925 ROMs.
Sent from my Atrix HD using Tapatalk 4 Beta

arrrghhh said:
Any issues in the CM10.1 ROM are likely going to be present here.
Interesting tho that my device, same SoC does not suffer from this bug. Will see what I can unearth.
Click to expand...
Click to collapse
tvd0405 said:
Same problem as other 4.2.2 roms, bluetooth audio does NOT work
Click to expand...
Click to collapse
So has this been beaten to a dead horse? Logs? Anyone made headway with it?
I've poked around a bit, but haven't put a ton of time into it yet. Any info will help shorten my task, thanks!

Running carbon right now. I lowered the CPU speed. Does the performance setting effectively control both cores? I ask because OCs make my device reboot. I'm in no need for the over clock. I recommend setting the default speed to stock speed for compatibility with options to over clock.
Update still getting the reboots. How can I provide error logs for you? FYI I am currently without any micro USB data cable.
Sent from my MB886 using xda premium

arrrghhh said:
So has this been beaten to a dead horse? Logs? Anyone made headway with it?
I've poked around a bit, but haven't put a ton of time into it yet. Any info will help shorten my task, thanks!
Click to expand...
Click to collapse
There is some info about GPS in slimbean thread...thats more like all we have now, i dont think anyone is working on BT audio...let me know if i can help...

Good bye Incredible S thread!

My device waiting for his new owner:
{
"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"
}
Yes guys, the time has come (LoL), I put my Incredible S on the market. I planned this for a long time now. My idea was to roll out a fully-working 4.3, which is probably the last Android version, which the Incredible S will run. I'm building and building, hopefully I have a proper 4.3 now with video playback fix, I won't sell my phone, till it won't work.
You may interested, why I wanna sell my phone, and here is the reason:
As we know, the hTC stopped the Incredible S's (and other msm7x30 board's) support after ICS. That means, we need to use the good old 3.0 kernel. The 3.0's support will stop in this October. We have many problems with this kernel's support. The 3.0 kernel doesn't support Jelly Bean specific things, for example the two most important: ION memory-allocator (our 3.0 kernel uses PMEM), and vsync. The vsync would be the smaller problem, it can be disabled easily, but because of the lack of vsync, our Project Butter will never work fully. The second shot into the vsync's head is that we have MDDI screen. This is a screen technology, but because of this, the vsync is impossible to port. But, as I said, the vsync is the smaller problem. The bigger is the ION. As you saw, I got it working with Sense 5. But, the camera will never work with ION on Incredible S, cause it needs a new driver, called "V4L2" (Video for Linux), which is only in the 3.4 kernel branch. To port back this driver, that would take months, and I haven't got enough knowledge to do it.
Because this bloody 3.0 kernel, the Sense 5 issues can't be fixed (at least by me). But the Sense 5 is still the smaller problem. Here is a bigger one, which makes me angry, and that's why I sell my device. For AOSP ROMs, the ION also won't be a problem, we can use it PMEM as well (as you saw), but, and here is the but... Our processor is an earlier revision of MSM8255, which doesn't support something which will be needed by Android 5.0. That means, the 5.0 won't work here, or there is only a small hope to get it working.
This is the reason, and I'm very, very said to sell my device, and I really love it! You may have the idea, why don't we port back a 3.4 CAF kernel to our device, cause they did it to Sony Ericsson and Samsung msm7x30 devices. The reason is, that the hTC has many crap in the kernels. That means, we can't port it, it would be a nearly impossible project. My DEV friend tried it, who much better than me, he has bigger knowledge, and he stopped working on it, cause he said it's impossible.
That means, the Incredible S will probably die with Android 4.3, and Sense ICS. Anyway, it had a great support period, from 2.2 to 4.3. This is quite rare.
As I said, I'll roll out a fully-working 4.3, and I hope that there will be a or some guys who will continue the building!
I'll change to hTC Desire X, which is the cheapest device which got official Sense Jelly Bean with 3.4 kernel. You see, I don't need faster, or stronger device, if the IncS would have a 3.4 kernel, I wouldn't sell it...
About the Sense 5, I gave the permission to S.a.M.e.R_d to use my files, kernel etc... Yeah, he promised that he'll fix the bugs, and he won't let you down. What should I say? I think, may you should give him a new chance, may he is true, and he'll bring bugfixes to The Unimaginable.
At last, I wanna give a huge thanks to the whole Incredible S community!!! You're great guys, I can't thank you enough, that you were with me when my thread was closed, that was a real incredible job! No homo, but I really love you, all of you guys, and I'm said that I need to leave you!
Enjoy the CM10.2 on this amazing which was the first which got Sense JB, which is a huge breakthrough, this device is really amazing, and I love it!
That was all, I hope, you understand, and I hope, I was a part of this community.
I won't go away fully, just slowly, but my first priority is the Desire X now with that bloody 3.4 kernel..
Bye guys, and huge thanks ALL OF YOU!

We love you szezso, the work you have contributed to this awesome community is something that you just cannot express in words. The way you work hard and put in countless hours. The Inc S community are the most privileged community to even recieve a piece of work from a humble developer like you. You will remain forever branded in the Inc S XDA life and hope the Desire X community can only welcome you with extreme kindness and they should know how lucky they are to have someone like you.
<3

Wow. I dont know what to say. I dont know if i am more jelly because desire x has an amazing dev at their disposal and we dont have anybody or that we are most likely not going to be supported anymore, but I guess this was expected..
But, from the bottom of my heart, Thank you so much. You have breathed new life into our phone, and tbh I wasnt expecting 4.3 let alone 5.0.. Although it is sad that Unimaginable will not be fully fixed, I dont really care.. You have done enough for us...
Unfortunately, I will be stuck with this phone until the end of next year, as I am not as rich as some people in this forum (lawl mark)
Once again, thanks so much for your work. I hope the Desire X forum recognises you as much as we did, (or more).
Farewell,
Sent from one of the few remaining Incredible S'

SZEZSO MATE just want to say thanks for what you have done for us, you have taught me a lot, I am sure a lot of people have learnt and been inspired by your work.
Even though you are relatively new to the dev scene its been amazing watching your knowledge grow, from your first ROMs to now being able to boot jb sense and 4.3 on a legacy device
We have seen many people come and go, and we might be losing one of our last true developers
I love you man
And this is for everyone else:

I just want you to know that aside from all the usual suspects you made a huge difference for all the lurkers like myself. Thanks for the dedication!

You are going, and all the Incredibles are orphaned now :crying:

its rly bad news for all of us..v all luv u szezso..watever u did for us is really incredible...as u r leaving this inc s thread ill also sell my inc s...ill miss u nd urs awsum work...feeling really bad...
Sent from my Incredible S S710e using Tapatalk 2

I teared up and almost cried :crying: :crying: :crying: :crying: :crying: :crying:
This has got to be some of the worst news I've ever read since I rooted my Incredible S. Hopefully Android 4.3 stays fast and snappy until December of next year (since that's when my contract ends and I'm allowed to get a new phone)
Respect to Szeszo!
Maybe, when you get to Desire X, you can work with Cpkv5 (or however you spell it, I forgot ). Help them get their Sense 5 like you so brilliantly gave us Maybe give them AOSP too since I see that many of their AOSP kernels don't have working WiFi and the such.
If the Desire X people doesn't like you, tell us, and we'll go over and fix'em right
SOMEBODY HAND SZESZO HIS RECOGNIZED DEVELOPER TAG. SCREW THE REQUIREMENTS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Thanks a lot Szezo.. You have been amazing for long time now and got me jawdropped when I saw Sense 5.0 and JB 4.3 Rom!! Respect for what all you have learnt and dedicated your time for us. May Desire X forum welcome you with all glory.
All the best for your Future..

It's like Ted is leaving the Stallions.
A huge desaster for us.
But we have to handle it.
Good bye szezso, and thanks for all the fi̶̶s̶̶h̶ ROMs.

Thank you Szezso for all your time you dedicate to our lovely Incredible S! And I think that all of we can courageously change IncS to Desire X, because we know that it will not die, because it will be supported buy great developer!

When you fix the video bug,I can continue to compile the new CM 10.1 or 10.2 rom

Really sad about the fact that such a great developer as you, Szezso, is leaving our community. May the luck and peace be with you and let the community of Desire X kneel down to you! (that was definitely cheesy )

@SZEZSO , Thank you for all you have done to this community
I wish all the best to you

Shock, Oh one of the best developer is leaving from here.
Thank you for all you done for community.
Sent from my Huawei MediaPad using XDA Premium 4 mobile app

Thanks guys, I'm very glad to see your comments! I can't say anything, only one thing: HUGE THANKS TO ALL OF YOU, THIS IS A GREAT COMMUNITY!!! If you want to use my new ROMs, the Desire X thread is open for everybody, you'll find me there! :highfive:
Sent from my HTC Incredible S using xda app-developers app

Thank you so much Szezso for all your work on our beloved device!
I know many people have said it but it's true: You are the reason why many of us do not have a new phone.
I hope that cm 10.2 will be fully working like you said so!

Keep in Touch
Well You might be changing your device but you will be keeping in touch. I am sure. And we all are thankful to you and we respect and love you (yeah no homo) haha and we love your work. I wish the unimaginable could get better we all do. but you described the problem pretty much. We all wished it to get fully rnning but I admit even booting sense 5 was a remarkable job.
We will miss you bro.
and as i said keep in touch.

Thank you that was with us. Please renew the kernels here http://forum.xda-developers.com/showthread.php?t=2385808
Thanks=)))

nikitos93053 said:
Thank you that was with us. Please renew the kernels here http://forum.xda-developers.com/showthread.php?t=2385808
Thanks=)))
Click to expand...
Click to collapse
What are you talking about? Those are the latest editions there. And the only Android OS that's missing there is 4.3. We only have only 1 4.3 ROM here and that comes default with TESCO V2.9++

For modders Only bug rooms STOP

I know that build a rom it's not that easy, and make it stable and fully working it's even harder. I also know that drivers and blobs are closed-source, so it's hard to make a device fully working.
But I wanna give some advice, because who want to mod his phone finds about 30/40 roms all unstable and full of bugs.
In my opinion, it's useless to release a rom if it isn't finished, wifi or bluetooth doesn't work, apps force-close, phone reboots randomly or maybe drinks the battery in 2 hours.
Lags in games, the home screen lags with 3/4 widgets. Maybe after a clean install the rom performs well but then you discover that it's not so good.
Let's not forget also that despite the roms are not finished, many times they aren't update any more to solve the bugs, or they are updated but the bugs remain.
I don't mean that ALL the roms have ALL the bugs, but each rom has at least two of those problems.
Some people may say that there are hardware limits to justify the bugs. Or maybe that the battery has to be changed. But those are only excuses considering that on three pages of roms, ONLY one performs well.
I have always been told “you have to change the battery”, or “the phone has got few ram” to justify the bugs. But why with the FluidRom gType (an Italian rom) I manage 24 hours with a normal usage (mobile data always on, wifi, background apps, little playing with games, several calls, facebook and whatsapp)? No lags in games, home and browser. So I assume that “change the battery” and “we have few ram” are only excuses.
If you release a rom only to show that you are able to develop something but then it’s full of bugs, stop. Don’t release it. Or release it when it performs really well.
The 4X it’s a 2012 flagship phone, but the roms are badly developed. So let’s not blame the hardware.
Some people may say “who forces you to change rom?” People try new roms because modders promise improvements.
Maybe this topic will be closed to restrict freedom of speech. But mine are only suggestions.

Serial67 said:
I know that build a rom it's not that easy, and make it stable and fully working it's even harder. I also know that drivers and blobs are closed-source, so it's hard to make a device fully working.
But I wanna give some advice, because who want to mod his phone finds about 30/40 roms all unstable and full of bugs.
In my opinion, it's useless to release a rom if it isn't finished, wifi or bluetooth doesn't work, apps force-close, phone reboots randomly or maybe drinks the battery in 2 hours.
Lags in games, the home screen lags with 3/4 widgets. Maybe after a clean install the rom performs well but then you discover that it's not so good.
Let's not forget also that despite the roms are not finished, many times they aren't update any more to solve the bugs, or they are updated but the bugs remain.
I don't mean that ALL the roms have ALL the bugs, but each rom has at least two of those problems.
Some people may say that there are hardware limits to justify the bugs. Or maybe that the battery has to be changed. But those are only excuses considering that on three pages of roms, ONLY one performs well.
I have always been told “you have to change the battery”, or “the phone has got few ram” to justify the bugs. But why with the FluidRom gType (an Italian rom) I manage 24 hours with a normal usage (mobile data always on, wifi, background apps, little playing with games, several calls, facebook and whatsapp)? No lags in games, home and browser. So I assume that “change the battery” and “we have few ram” are only excuses.
If you release a rom only to show that you are able to develop something but then it’s full of bugs, stop. Don’t release it. Or release it when it performs really well.
The 4X it’s a 2012 flagship phone, but the roms are badly developed. So let’s not blame the hardware.
Some people may say “who forces you to change rom?” People try new roms because modders promise improvements.
Maybe this topic will be closed to restrict freedom of speech. But mine are only suggestions.
Click to expand...
Click to collapse
Haha, there are so many angles i can take on this.
I and the other 4x developers and users don't owe you ANYTHING, dont like our roms? dont use them, Simple. It amazes me some people are so entitled...

Go and make some Roms by yourself we'll see how good they would be .
For your information bringing roms to device in long chain of more people than just our devs
Sent from my LG-P880 using Tapatalk

Serial67 said:
I know that... TL;DR
Click to expand...
Click to collapse
{
"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"
}

Wow ! Never thought I'd read something like this on the 4X forum !
You're so wrong. So so wrong !
Do you realize that when a dev releases a ROM he does this on his time and (most of the time) he doesn't expect anything in return.
Have you ever tried to build a ROM from source ? To compile ? To fix bugs ? To spend hours developing ? I really doubt since you don't realize what this is and the time it takes.
Moreover, our device is "special". The last official update we had was 4.1.2 and thanks to the dev you criticized we are now at 4.4.2 !!! I'm not sure you realized the work of these devs.
Also you say that we don't have any stable ROM but you're wrong ! For me, "stable" means that you can use the ROM daily and profit of all basic and important features of the ROM therefore there ARE stable ROMs ! Since I'm in charge of Beanstalk 4.4.2 I won't give any name but for having personally tried many customs ROMs I can say that we do have stable ROMs.
Everybody has its opinion but man... You're wrong and some devs may understand your post as an offence.
I hope you see what I'm trying to explain.
Sent from my LG-P880 using XDA Premium 4 mobile app

ectoplasma22 said:
Wow ! Never thought I'd read something like this on the 4X forum !
You're so wrong. So so wrong !
Do you realize that when a dev releases a ROM he does this on his time and (most of the time) he doesn't expect anything in return.
Have you ever tried to build a ROM from source ? To compile ? To fix bugs ? To spend hours developing ? I really doubt since you don't realize what this is and the time it takes.
Moreover, our device is "special". The last official update we had was 4.1.2 and thanks to the dev you criticized we are now at 4.4.2 !!! I'm not sure you realized the work of these devs.
Also you say that we don't have any stable ROM but you're wrong ! For me, "stable" means that you can use the ROM daily and profit of all basic and important features of the ROM therefore there ARE stable ROMs ! Since I'm in charge of Beanstalk 4.4.2 I won't give any name but for having personally tried many customs ROMs I can say that we do have stable ROMs.
Everybody has its opinion but man... You're wrong and some devs may understand your post as an offence.
I hope you see what I'm trying to explain.
Sent from my LG-P880 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Don't worry ecto, we are talking about it in the italian forum where this kind of discussion began.. And we are composing it saying exactly what you're saying right here..hope that it'll stop as a great mistake, and to go on..
Sent from my LG-P880 - Beanstalk 4.4.2 - Iodak 9.95 kernel - using XDA Premium 4 mobile app

one word, ridiculous

We should change abit this letter and sent it to the LG dev-update department so they can ask @Demetris @laufer @adam @Ectoplasma @JoinTheRealms @SnXo (and many other talented and good people) for help next time they decide to push or even make any software for any LG phone.I know.this guyment to say official software not custom one so i am just correcting his type mistake.
Послато са LG-P880 уз помоћ Тапатока

whoa, easy there, mate...
First of all, I haven't seen an unstable ROM on our phones up till now. I am personally using CM (unofficial) and SlimKat as my daily drivers, and both are rock stable. The only bugs I have personally encountered are the camera (which is extremely hard to properly fix) and the broken reboot into recovery on Slim. And that's it.
All ROMs you find on xda are made for free, you don't need to pay anything, which means you also can't demand anything. Bringing a ROM to a device can take several hours (disregarding the time the pure download of the sourcecode takes), as every ROM needs its special treatment.
Furthermore, do you have any idea how long the pure compile process takes? On my new machine (which I upgraded for development only) needs ~75min for a clean build. Before that, my lappy was working over 8 hours for a clean build...
Saying we devs wouldn't maintain our ROMs isn't really nice, nor what XDA stands for. We do our best to provide you with the best/fully functional stuff, but there are things we can't fix/improve simply because we don't experience these issues. As an example, I am debugging my kernel ATM, and @FunkyRasta and I both run the kernel, however, FunkyRasta is experiencing lags, that I never experienced. So without his reports, I wouldn't even know about that until someone else might encounter it after the release.
@Serial67, nobody forces you to use "unstable" ROMs, but please don't just complain, but rather give some helpful feedback (logs) to help solve the issues. If you're not willing to provide such info (you don't have to), please don't complain.
Thread closed.