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
Related
Hi everyone,
I've decided to start a thread dedicated to my SDK port of ICS. I want to extend a thank you to Joel, who initially got this booting on our device.
Some of you may know that I've made some progess on one of the biggest issues with the port on our phone (and many many other HTC phones actually), which was the touchscreen. I've ported the driver from the Samsung Nexus S (uses the same touchscreen sensor as the Inc) and gotten it to work with the CM7 kernel (from cuviper). And now the touchscreen works in ICS as well!
This ROM is not a daily driver, although if we did get that far it would rock , but since we don't have the source yet I'm not expecting anything too incredible . My goal for this ROM is to get as much of our hardware working with what we have, which is existing files from GB that may or may not help, as well as kernel and driver hacking. Once the source drops for ICS, with any luck our work here will enable ICS to be ported sooner because of tweaks and modifications to the kernel that may very well be needed with a source port anyways. My idea is to get as much work done ahead of time as possible, I suppose.
So PLEASE, do not complain about features that aren't implemented yet, or other parts that don't work as you would expect. I don't expect anything to work as we expect! That's the whole point of this. And also keep your negative comments about SDK ports to yourselves if possible. As I said, this is not to create a 100% functional SDK port. It's to make as much functional as possible so that ourselves and others will perhaps have fewer hurdles and headaches to overcome when the ICS source becomes available. Especially since we can't really expect an ICS update for the Incredible or many other similar HTC phones, meaning we may never see kernel source from them to help us.
Current download links:
Here's the link to my current progress: incredible_ics_v0.01-signed.zip
This is a flashable zip for CWM. You'll need to wipe data/cache as usual.
The touchscreen currently works in "pointer" mode, meaning it acts as if its a trackball/touchpad to move the cursor on the screen. Pressing with two fingers is interpreted as a touch to select things. This is not ideal.
If you'd like to try and help out, try messing with the .idc files. I was able to get rid of cursor mode by using some others from other devices, but the touch seemed very...ehh...not correct. Messing with the values in the files seemed to change how it behaved, but we need a correct .idc file to make things work the way they should. If you find one and want to try it, you'll have to create the directory (/system/usr/idc) and push the file to it through ADB. Android loads it upon boot. Also, it must be named "mxt224_ts_input.idc" otherwise it wont load the file. I plan to work on the .idc predicament myself at some point soon, but I'm still trying to hash out a few touchscreen driver ideas that may be a better solution.
Please read:
If you figure anything out, please post here! Or if you have trouble with something, post here with a logcat and a dmesg dump. They're pretty simple to do. To get a logcat, turn off your device, then turn it on. Once the white Incredible screen is up, type "adb logcat > logcat.txt" into your terminal/command prompt. Once it's done booting you can CRTL+C to stop it from logging. After this, back on your terminal, enter "adb shell /system/bin/dmesg > dmesg.txt" to get the dmesg dump. Grab those and zip them up and post them here for someone to look at.
Source:
Incredible kernel github repo: github.com/swm5126/cm-kernel
ROM github repo: github.com/swm5126/Incredible_Ice_Cream_Sandwich
Everything else:
And finally if you're interested in the progress being made on touchscreen drivers, take a look here. Currently, I'm trying to see if instead of using the Samsung driver, we can use the HTC driver with some modifications to make it work correctly for ICS.
*This is by no means only just "my" port and work here. I encourage anyone with any knowledge, from our device or even others to add to the discussion and help out as they please. I only aim to manage mine and others progress in one place.
*I am not all that knowledgeable with kernel/driver programming and modifications. I'm versed in programming a few languages, but I've never done any system level stuff, and I'm learning (A TON by the way) of things as I go by tweaking and testing things. Which means that I may, or may not know what I'm talking about. If I've provided inaccurate information, please tell me so I can correct it!
Phew. Anyways, please try it out if you'd like.
I also added a donation email in my profile, if anyone would like to donate. I wont be hurt if you don't, but if you do, THANK YOU!
Reserved for future use
I just want to thank you for all the hard work you've been doing on this. It is projects like this that keep our devices as current as they can be, and interesting. So, thanks a lot to everyone involved.
badogg said:
I just want to thank you for all the hard work you've been doing on this. It is projects like this that keep our devices as current as they can be, and interesting. So, thanks a lot to everyone involved.
Click to expand...
Click to collapse
I couldn't have said it any better.
Sent from my ADR6300 using xda premium
badogg said:
I just want to thank you for all the hard work you've been doing on this. It is projects like this that keep our devices as current as they can be, and interesting. So, thanks a lot to everyone involved.
Click to expand...
Click to collapse
And this why I am sending him a donation right now. Thank you, your work is greatly appreciated.
Ok, I'm gonna need a little help! I tried playing around with this, but now I can't get out!! AHHHHHH!! power and volume down doesn't get me to the bootloader. What can I do?
edit - yes it did..whew!! but it was absolutely awesome!! thanks!
badogg said:
i just want to thank you for all the hard work you've been doing on this. It is projects like this that keep our devices as current as they can be, and interesting. So, thanks a lot to everyone involved.
Click to expand...
Click to collapse
amen +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"
}
I love you.
ooooooohh eeeeemmmmm geeeeeeee
<3
Tried it real quick. Nice!
I'll be the first to admit that I have no interest in trying ICS on the Inc lol BUT I have to say, thank you for working on this. I hope to see this progress tremendously once the source hits.
I installed this to check it out. Wow. I'm really excited to see what kind of ICS love is going to come to my beloved Dinc from this. I really liked the little bits I could see.
Cheers!
Good stuff man, you're a champ. Thanks for being adventurous
Sent from my ADR6300 using XDA App
Neat! I was wondering what you were up to with that clone of my repo.
I haven't actually tried your port yet, but for the touchscreen stuff, I suspect that the userspace parts are just expecting certain interfaces exposed by the kernel driver. We should know better with full source, of course. But I would guess the right answer will be changes in userspace, because obviously not all devices will be able to have the same touchscreen driver. Well we'll see. Hope to see you in CM when ICS finally comes out.
CUViper said:
Neat! I was wondering what you were up to with that clone of my repo.
I haven't actually tried your port yet, but for the touchscreen stuff, I suspect that the userspace parts are just expecting certain interfaces exposed by the kernel driver. We should know better with full source, of course. But I would guess the right answer will be changes in userspace, because obviously not all devices will be able to have the same touchscreen driver. Well we'll see. Hope to see you in CM when ICS finally comes out.
Click to expand...
Click to collapse
What you said is exactly what I've been thinking, I just haven't been able to tell what data the Samsung driver is letting the OS see that the HTC driver doesn't.
They seem very identical in terms of the output they generate and where it's stored. Obviously something is different though. And it's really annoying, because the HTC driver actually produces MORE data and is much more explicit in reporting exactly what its doing to the point that it looks very confusing and messy even when you compare to Samsung's driver. I don't think HTC would try and make it confusing unnecessarily though, and other drivers they have written look similar in the way they work and report data.
That said, I've actually been using the Samsung driver on my daily driver install of CM7 and I think it works better. It feels more responsive and can register the pressure of my touch more accurately (feels like it anyways). But it crashes maybe once or twice a day, and the screen will just stay on and become unresponsive. Haven't figured that out yet but it only does it in certain applications.
Sent from my ADR6300 using xda premium
Really looking forward to seeing what people put out when the source drops.
Sent from my Incredibly awesome Droid Incredible.
Can this help?
http://www.androidcentral.com/galaxy-nexus-boot-recovery-and-system-dumps-now-available
dunndada said:
Can this help?
http://www.androidcentral.com/galaxy-nexus-boot-recovery-and-system-dumps-now-available
Click to expand...
Click to collapse
http://android.modaco.com/topic/348194-04-nov-icl23d-galaxy-nexus-boot-recovery-system-dump/
^direct link to the thread.
Yeah. I probably wont be the first to say it will probably help Trying to get them now. Stupid filesonic. Don't know why people don't use mediafire!
I'm going to start working on this later, as I seemed to have found a better solution for the touchscreen drivers, and am now able to use the original HTC driver with a slight modification
Great.... this is helping me deal with the wait on the nexus.
Check this story. Looks like may for us.
Sorry about the sparse post but I'm on the move
http://www.androidcentral.com/list-bell-android-40-updates-appears-timelines-each-device
{
"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"
}
So, roughly May-June . . . so most likely August.
ok. we might get a leak or something by the late april and cm9 people are gonna fix the camera and we're gonna keep not caring about the stock firmware release. fingers crossed.
Bateluer said:
So, roughly May-June . . . so most likely August.
Click to expand...
Click to collapse
Actually no. If you read the article carefully, you'd expect the opposite to be true. This roll out is for Bell devices, and the Bell ROMs will be based on the stock ROM which one would assume to come out first.
---------- Post added at 12:40 PM ---------- Previous post was at 12:38 PM ----------
safir187 said:
ok. we might get a leak or something by the late april and cm9 people are gonna fix the camera and we're gonna keep not caring about the stock firmware release. fingers crossed.
Click to expand...
Click to collapse
Forget that. I'm looking forward to an Overcome ICS
CafeKampuchia said:
Forget that. I'm looking forward to an Overcome ICS
Click to expand...
Click to collapse
ok i will. i'm with you bro.
just any fully functional ics rom.
im estimating a november timeframe
Looks like we will end up waiting a while. Like usual with Samsung......
Sent from my GT-P7310 using XDA Premium HD app
I heard Samsung will make ICS available by Christmas 2013.
triften said:
I heard Samsung will make ICS available by Christmas 2013.
Click to expand...
Click to collapse
Now thats a realistic guess.
this is for i957 btw
I would expect the standard non carrier specific units to get it earlier, so April-May.
Im surprised there are no leaks though, maybe there just isnt the demand.
This was helpfull when determining when the official SGS2 ICS roms are available. I have been unable to find anyone doing this for the Tabs. I assume we have a CSC code.
http://androidforums.com/samsung-galaxy-s2-international/523455-ics-csc-you-eligible-update.html
wow just about everyone has gotten official ics now
acer released last week and now even the friggin sony tablet got ics!
samsung is the LAST of the big manufacturers to release. all because of the friggin touchwizz im guessing...
pseudoheld said:
wow just about everyone has gotten official ics now
acer released last week and now even the friggin sony tablet got ics!
samsung is the LAST of the big manufacturers to release. all because of the friggin touchwizz im guessing...
Click to expand...
Click to collapse
AFAIK, TouchWiz is working under ICS because they've upgraded the SGS2 and there've been some leaks for the Note. They're slackers.
Delays over updates in this day and age are unacceptable.
the galaxy tab 2 7" is out now, can it be helping the camera and other issues on ics?
Bateluer said:
AFAIK, TouchWiz is working under ICS because they've upgraded the SGS2 and there've been some leaks for the Note. They're slackers.
Delays over updates in this day and age are unacceptable.
Click to expand...
Click to collapse
TW for phones is VERY different to TW for tabs. Just because its working for the SGS2 it doesnt mean it is for the Tabs.
Each device is different, and requires a lot of work to be fully functional. Remember Samsung have many different devices to upgrade. Even with all the work Cyanogen have done its ROMs are still far from as slick or reliable as OEM ROMs on any device(IMHO) and the AOSP or AOKP ROMs aren't optimised that well either. They work, mostly , but are far from delivering the performance of an OEM ROM.
Its been said many times. Dont like skins like Sense or TW, dont buy an HTC or Samsung. If you still want the devices then have the patience to wait. If you hate them that much you should be using a Nexus and a Xoom.
rovex said:
TW for phones is VERY different to TW for tabs. Just because its working for the SGS2 it doesnt mean it is for the Tabs.
Each device is different, and requires a lot of work to be fully functional. Remember Samsung have many different devices to upgrade. Even with all the work Cyanogen have done its ROMs are still far from as slick or reliable as OEM ROMs on any device(IMHO) and the AOSP or AOKP ROMs aren't optimised that well either. They work, mostly , but are far from delivering the performance of an OEM ROM.
Click to expand...
Click to collapse
I guess "slick" and "reliable" when it comes to ROMs are debatable; I have always preferred custom ROMs on my Android devices (except my Nexus S). How you can say that they don't deliver the performance of an OEM ROM I can't really fathom, since everything I've seen demonstrates that they are capable of performing as well if not better than manufacturer-bloated ROMs.
You can overclock a custom ROM; that in and of itself is a pretty big performance enhancement.
Custom ROMs based on OEM base ROMs are definitely better, no question, but the ground-up ROMs like Cyanogen and AOSP or AOKP, no way, not a chance. There is usually something that doesnt work, some sort of lag, broken codec or missing feature.
Ive tried Cyanogen on numerous devices, there is always something that isnt right, always.
rovex said:
Custom ROMs based on OEM base ROMs are definitely better, no question, but the ground-up ROMs like Cyanogen and AOSP or AOKP, no way, not a chance. There is usually something that doesnt work, some sort of lag, broken codec or missing feature.
Ive tried Cyanogen on numerous devices, there is always something that isnt right, always.
Click to expand...
Click to collapse
It seems like your making a universal statement based solely on your own personal experiences. I have used CyanogenMod for years on various phones and it often worked very well with virtually no issues. In fact, on my EVO Shift there was no comparison; CM7 blew the Sense-addled OEM ROM out of the water.
Again you are missing the point. I dont like sense or TW either, but the ROM base is still vastly superior. That is why i use a non-TW Samsung base ROM based custom ROM on my SGS2.
Hello friends!
Today I release a Optimus G rom for our Nexus 4! This is a very early alpha build/port so dont expect a lot of functionality!
I AM NOT RESPONSIBLE FOR ANY BRICKED DEVICES!
{
"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"
}
Whats working in Alpha 1:
- It boots
- Screen works
- Sound works
- Charging works
- Bluetooth works
- Connecting to PC works
- LED notification works
- Anything related to CPU/GPU is working
- Navigation buttons for Nexus 4 work
Whats not working:
- GSM + WiFi
- Camera
- GPS
- Notebook FC's
- Random reboots
DO NOT FLASH THE BOOT.IMG ON NEXUS 4 ROMS, IT WILL BREAK SOME THINGS LIKE WIFI.
Code:
[CENTER]Changelog:
Alpha 1: Initial release[/CENTER]
Flash with CWM or TWRP
Download link Alpha 1: https://mega.co.nz/#!fFEEWSQS!K_3LVHkhj9Av-KpYINuSWXPK5B4VmrykdXm4ijYNUn8
OPTIONAL
Download link boot.img for Alpha 1: http://d-h.st/SsP
Donations
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=8J4B5RXM7UZKQ
Optimus G kernel or replaced with Nexus4 stock kernel? Flashing a Nexus4 specific kernel seems to be a greet idea.
We should only change the device specific parts of the rom to be fully working.
I'll try to help later today.
Tapatalk 2-vel küldve az én Nexus 4-ről
Not that I would revert back to manufacture based skinned ROMs, but +1 for the nexus dev community!
TaRsY said:
Optimus G kernel or replaced with Nexus4 stock kernel? Flashing a Nexus4 specific kernel seems to be a greet idea.
We should only change the device specific parts of the rom to be fully working.
I'll try to help later today.
Tapatalk 2-vel küldve az én Nexus 4-ről
Click to expand...
Click to collapse
Optimus G kernel.
Its pretty hard to use the Nexus 4 kernel and modules etc. since its for Android 4.2.x and this rom is Android 4.1.2 =]
Aerys said:
Optimus G kernel.
Its pretty hard to use the Nexus 4 kernel and modules etc. since its for Android 4.2.x and this rom is Android 4.1.2 =]
Click to expand...
Click to collapse
oops forgot about this..
Not trying to say this isn't awesome but I'm only interested in that damn lock screen! That unlock effect is what everyone is after! Hopefully this is the beginning of that work. Well done for this! :thumbup:
Sent from my Nexus4™
benrees21 said:
Not trying to say this isn't awesome but I'm only interested in that damn lock screen! That unlock effect is what everyone is after! Hopefully this is the beginning of that work. Well done for this! :thumbup:
Sent from my Nexus4™
Click to expand...
Click to collapse
Yea the lockscreen is really beautiful!
EDIT:
Download link Alpha 1:
https://mega.co.nz/#!fFEEWSQS!K_3LVHkhj9Av-KpYINuSWXPK5B4VmrykdXm4ijYNUn8
Have fun =]
Awesome!!! When I was deciding what my next phone would be, it was between a nexus 4, an xperia z, and an optimus g....now I can see what I missed out on!
Great work...can't wait for a stable build
Note; When you boot the device it will do a media scan. It will be VERY slow and laggy for like 10-20 seconds.
The things that i find interesting are the wonderful lockscreen and the colors on the screen looks amazing, hope the devs here can put the Optimus G RGB and gamma values into their kernels.
Can't wait. I wonder if this rom will provide better battery life. LG has some tweaks in their software that's not part of stock android.
Sent from my Nexus 4 using xda premium
NardVa said:
Can't wait. I wonder if this rom will provide better battery life. LG has some tweaks in their software that's not part of stock android.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
My generalization about lg's android experience in the past is they have no idea what they are doing with software(not that I do either) and battery life was horrific. Maybe they got better and more experienced dev teams together. We shall see. On the other hand the nexus 4 is a mighty fine experience:thumbup:
Does this rom have an optimus or a nexus kernel? If it's an Optimus one, maybe we can use some of the custom optimus kernels with it! Then we can really get some awesome stuff!
*edit*
I hadn't looked through their forums to see that they are still in development infancy stages Maybe our cooperation can be mutually beneficial!
I think we will need the Nexus 4 kernel for rild and Wifi but yeah lets experiment a little.
davwman said:
My generalization about lg's android experience in the past is they have no idea what they are doing with software(not that I do either) and battery life was horrific. Maybe they got better and more experienced dev teams together. We shall see. On the other hand the nexus 4 is a mighty fine experience:thumbup:
Click to expand...
Click to collapse
this is because (IMHO) LG are like Sony....they make some of the sexiest, best performing, highest quality hardware you can find for many different types of devices/electronics. However, they have absolutely no business making software & firmware.
Having said that, I do think they have a great deal of wonderful IDEAS that they implement into their electronics (especially android) but they are usually not polished well, and end up being unstable or just buggy as hell. I do love having those features pulled out and isolated, though, so I can have a monstrous selection of special features that were never intended to work together, though. And when they are, for example, android mods added on top of pure aosp, beautiful things happen, IMHO
Aerys said:
I think we will need the Nexus 4 kernel for rild and Wifi but yeah lets experiment a little.
Click to expand...
Click to collapse
Don't see why that wouldn't work. Same hardware
davwman said:
Don't see why that wouldn't work. Same hardware
Click to expand...
Click to collapse
that's my exact school of thought here, as well. I would think if the rom can be swapped out so easily, there's no reason why at least SOME of the kernels wouldn't work by default, as well.
I'm looking specifically at the aokp port for optimus...that's got to have a custom kernel, I would think...and it's most likely optimized for optimus (lol...say that 5 times fast )
Do you even think this will boot on a n4 kernel?
Would it be easier having a 4.2.2 ROM with the LG stuff added or what's your game plan? I'm very excited about this..
Sent from my Nexus 4
ChongoDroid said:
Do you even think this will boot on a n4 kernel?
Would it be easier having a 4.2.2 ROM with the LG stuff added or what's your game plan? I'm very excited about this..
Sent from my Nexus 4
Click to expand...
Click to collapse
My goal is to get a fully working Optimus G rom. The Nexus 4 kernel doesnt boot with this rom, so I have to look at other options.
In theory with the correct radio/kernel combo, would this rom be capable of using DC HSPA +42? I guess a better question would be is the Optimus G capable of it?
Sent from my Nexus 4 using xda app-developers app
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...
{
"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"
}
Overview
OmniROM is pretty close to AOSP, as the 4.4.4 era comes to a close I've decided to post it.
This build has nothing to do with Nobe1976.
It is not his build on Droidrzr forums and was built by me, from source. Although it is likely the same (assuming configs for our device haven't changed much the past year)
Download
Feb/27/2015: OmniROM 4.4.4
KKBL only for now folks!!!
Source
Device
https://github.com/CyanogenMod/android_device_motorola_moto_msm8960/tree/cm-11.0
Kernel
https://github.com/CyanogenMod/android_kernel_motorola_msm8960dt-common/tree/cm-11.0
Vendor
https://github.com/TheMuppets/proprietary_vendor_motorola/tree/cm-11.0
Yes JJBL people, I will build for you, but I need someone to test so OmniROM aside; IF JBBL people want these firmware I will need a tester :<
Just flashed this on my XT926 and the only issue ive had is when going into Settings>More>Mobile Networks>Carrier Settings The process com.android.phone force closes.
nice rom, works fairly well on my razr m. feels lighter than cyanogenmod and other 4.4.x roms.
lol
Do you know about Lollipop? lol
Working really great on my XT925.. I love OmniRom.. Thanks @Tqr
The fact that this base appeared here means MIUI v6 comes soon
Edit: I'm NOT heading MIUI v6 I am only working as an assistant this is not my era to shine; with that being said if I can't get a JBBL volunteer It's not likely JBBL people will get MIUI v6
kkruglov said:
nice rom, works fairly well on my razr m. feels lighter than cyanogenmod and other 4.4.x roms.
Click to expand...
Click to collapse
A lot of people use my MIUI or other fork builds but don't really have the chance to use my source-builds which are almost always nearly 'perfect' (I don't usually post them)
Some compatibility takes a huge hit after I start chopping stuff to pieces so I just wanted to throw this up for people who are the opposite of the MIUI/Lewa/Whatever crowd and just want something as close to 'stock' android as possible.
Tqr said:
but don't really have the chance to use my source-builds which are almost always nearly 'perfect' (I don't usually post them)
Click to expand...
Click to collapse
why?
kkruglov said:
why?
Click to expand...
Click to collapse
It would annoy me if someone ported a ROM I had planned to work on using a base I built.
Tqr said:
The fact that this base appeared here means MIUI v6 comes soon
Edit: I'm NOT heading MIUI v6 I am only working as an assistant this is not my era to shine; with that being said if I can't get a JBBL volunteer It's not likely JBBL people will get MIUI v6
Click to expand...
Click to collapse
Looking forward to see MIUI v6! Loved MIUI even since my evo 3d. Hope it comes soon
Sent from my DROID RAZR HD using XDA Free mobile app
dulexetina said:
Looking forward to see MIUI v6! Loved MIUI even since my evo 3d. Hope it comes soon
Sent from my DROID RAZR HD using XDA Free mobile app
Click to expand...
Click to collapse
Me too but my build configs are currently not working correctly for some devices.
It's kind of problematic on my end at this point because the past two builds of (pretty much) AOSP have resulted in failure for some unknown reason; even with supported configs.
At the same time to bring a close-to-AOSP ROM to this firmware I had to make a lot of changes in source; changes which may have caused breakage upon building for some devices so I've had to revert everything for this specific build which will probably set the process back a day or two.
But I don't want to sound over-important; the person heading v6 could have(and has) done this fully on their own power without issue and I am really contributing nothing except for build related stuff which isn't even essential It's just to save them time because a lot of time was saved in my life during v5.
It's like they say, someone does something for you and you do something for them if you can; a capacity I'm kind of failing in right now because a lot of the devices I'd like to see get hit with v6 do not have proper source bases
Thanks, very smooth... can you add HDR feature?
ikromy said:
Thanks, very smooth... can you add HDR feature?
Click to expand...
Click to collapse
Maybe, I have to address JBBL right after I finished with the device I'm building for right now.
Like a true piece of scum I neglected the JBBL folks during v5 because I wasn't aware of the exacts surrounding it and frankly was too lazy/busy to produce it.
But from here out all of my builds will also accomodate JBBL now that I know how to deal with it.
I mean it's really like a friend of mine said; that it's better to release broken things at first because If you release something right the first time your topic won't have as many views and as much attention but I've always kind of been a black sheep with my preference for (nearly fully) functional first releases
Edit: I can do MIUIv5 for JBBL if people really still care about it but I'd rather focus on getting things ready for V6, and other projects I'm working on
It's really important that ANY errors with this code-base are brought to my attention , I really do not want to find out there is some inherent error in this when V6 is released It's really important that I do this right so I don't have to bother the developer of it to do yet another build on a rebase.
I feel like I've really annoyed people because I've had multiple peers/friends/co-workers/whatever download firmware that somehow 'wasn't right' this week
Do it. It's been awhile. And that miui phone overseas is killing em softly. I'm on jbbl now to start fresh but if you decide to put out v5 I'll try it. I am ecstatic about v6 to try out.. I will be trying the omni for now. I need a real stable ROM at the moment.
Get lolly miui for mb886.
manuski said:
Do it. It's been awhile. And that miui phone overseas is killing em softly. I'm on jbbl now to start fresh but if you decide to put out v5 I'll try it. I am ecstatic about v6 to try out.. I will be trying the omni for now. I need a real stable ROM at the moment.
Click to expand...
Click to collapse
MIUI v6 is now nearly fully functioning on moto_msm8960 JBBL & KKBL, including V6 camera, scanner and all the other stuff you'd expect.
Unlike being a PatchROM build this is a direct adaptation from a Xiaomi device so there is a level of exclusivity here.
I really don't have the right to release this, It will be part of a friends multi-base thread; It'll show up at some point next month, hopefully.
I wanted to let people who are really anticipating being able to use V6 know that the codebase is finished; it does have all the features you'd expect on true stock MIUI that have never been ported (In this era):
- MIUI camera (Everything, including filters, panorama, fast&slow-motion recording mode...)
- MIUI Scanner (Everything)
- Nearly full native Xiaomi drivers (!)
- Everything, all features
TecknoFreak said:
Get lolly miui for mb886.
Click to expand...
Click to collapse
It's being worked on as well, but 4.4 takes priority because it is literally almost finished.
Tqr said:
MIUI v6 is now nearly fully functioning on moto_msm8960 JBBL & KKBL, including V6 camera, scanner and all the other stuff you'd expect.
Unlike being a PatchROM build this is a direct adaptation from a Xiaomi device so there is a level of exclusivity here.
I really don't have the right to release this, It will be part of a friends multi-base thread; It'll show up at some point next month, hopefully.
I wanted to let people who are really anticipating being able to use V6 know that the codebase is finished; it does have all the features you'd expect on true stock MIUI that have never been ported (In this era):
- MIUI camera (Everything, including filters, panorama, fast&slow-motion recording mode...)
- MIUI Scanner (Everything)
- Nearly full native Xiaomi drivers (!)
- Everything, all features
Click to expand...
Click to collapse
This is great to hear man! Now I want to try it even more.Can't wait till next month...release it tomorrow MIUI 5 was great,simple and smart,just hope that v6 is gonna be same or even better.
Sent from my DROID RAZR HD using XDA Free mobile app
Honestly I straight up lied.
MIUI v6 boots with full function except RIL- Because of the nature of this work all builds have been kept closed. I will check with the head of development and ask if beta may begin.
If anyone here feels strong in development and can address RIL both the KKBL and JBBL can have this firmware in the very forseeable future. It's because we use some kind of fked up Generic RIL and I'm not sure where to play Xiaomis invasive code because It's so different.
I do not even know how this device handles RIL in the 4.4 era, if anyone has an understanding of this please be in touch.