Database Users

CyanogenMod 6.1 is on its way! And its easy to get on Captivate!

Sorry if this has already been posted.
I apologize for not keeping the site up to date, I’m a slacker We also had a database issue and lost the last post about 6.0′s release, if you were wondering why it went missing.
6.1 is the current work-in-progress and is coming together nicely. There’s a few new features like touch-to-focus in the camcorder, dismiss notifications by swiping, kernel updates for most devices, and improved performance. There will also be support for a few new devices- Acer Liquid, HTC Wildfire and Samsung Vibrant. My eye is also on the new HTC phones that are about to get released like the G2.
A lot of people ask me about adding support for their phone, but we can only support phones that we actually own. The CM team is always looking for new hackers to join up with us to add support for their favorite device. Get in touch with me if you’d like to help.
CyanogenMod is open source. The quality of code being added to CM has vastly improved because of the code review system that we’ve put in place, Gerrit. It’s the same system used by Google to manage the Android Open Source Project. It allows anyone to submit code to the project in a highly-visible way and gives us a way to examine and improve it before it’s actually merged. We want your code, so send us your patches. If there’s something you don’t like, change it.
Nightly builds of CM are always available if you’re brave and want to try out the latest code. If you’re running nightly builds, the best way to stay up to date on new changes is to follow @cmsrc on Twitter.
Our user base is approaching a quarter of a million users. This project has come a long way Thanks for all the support, we are only as strong as the community!
Source- Cyanogenmod.com
Porting a vibrant rom to the captivate is not hard

no wayyyy this is finally coming to our cappy, i'd be beyond happy

Hate to sound like a douche, but is there anything in there (besides maybe some of the features of CM6.1) that we havent known for a long time? No release date, we know thier working on it, and we know they are working with the vibrant.

Well if you look here it still shows as in progress for version 6.0...They have said in the past that the vibrant won't be supported till 6.1 and then someone will still have to port it to the captivate..
https://spreadsheets.google.com/lv?key=0Aledx886TFpZdHdwNzNKZzJLczJjTnA5ekFWRzNxX2c&hl=en&authkey=CNf7ie8G
So I don't think we will be seeing anything soon...

so, i'm sure everyone will get a good laugh, because everyone talks about how this is the best thing about to come since sliced bread........
but what is SO great about this?

buddy17 said:
so, i'm sure everyone will get a good laugh, because everyone talks about how this is the best thing about to come since sliced bread........
but what is SO great about this?
Click to expand...
Click to collapse
Froyo! Plus lots of custom stuff.

well i knew it was based on 2.2....but the "custom stuff" is what i meant. What are some of the big things it does that are so great

I'm new to the whole Android scene so excuse my ignorance but can someone explain how CM6.1 can possibly be put on a GalaxyS phone when there is no source code for the kernel?
Sent from my SAMSUNG-SGH-I897 using XDA App

sdotbrucato said:
I'm new to the whole Android scene so excuse my ignorance but can someone explain how CM6.1 can possibly be put on a GalaxyS phone when there is no source code for the kernel?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
The other custom roms seem to use the 2.1 kernel.

I checked that spreadsheet about 3 weeks ago, and it was still in development like it is now for the vibrant.

buddy17 said:
well i knew it was based on 2.2....but the "custom stuff" is what i meant. What are some of the big things it does that are so great
Click to expand...
Click to collapse
Its not really about a wealth of extra features. Cyanogenmod has extra configurability. In addition it is a bit more cohesive than typical roms. I definitely preferred it over the stock Nexus One rom and the stock nexus one rom is better than stock Captivate.
The rapid updates and support is enough for me to use Cyanogenmod.

z28james said:
The other custom roms seem to use the 2.1 kernel.
Click to expand...
Click to collapse
But 6.1 is Froyo, all the ROMs I've seen are Eclaire... How are they using a 2.1 kernel with Froyo?
I was under the impression the reason for no Froyo ROMs on the Captivate was due to lack of source from Samsung?
Sent from my SAMSUNG-SGH-I897 using XDA App

Who needs this when we have cognition?!

designgears said:
Who needs this when we have cognition?!
Click to expand...
Click to collapse
exactly

designgears said:
Who needs this when we have cognition?!
Click to expand...
Click to collapse
i'm sure when this comes out you'll be able to strip the FroYo out of it and make it your own, and better

CM6.1 will come to the captivate after is released to the vibrant, kernel differences are minimal between the two so porting CM6.1 to the captivate will only require few kernel changes.

yeah i'm sure the port will be done in the time it takes to heat up a pop tart.

designgears said:
Who needs this when we have cognition?!
Click to expand...
Click to collapse
+1 Finally got my Cappy right where I want it. CM is awesome, I'm just tired of all the hype, not to mention the waiting for this stuff to happen.

designgears said:
Who needs this when we have cognition?!
Click to expand...
Click to collapse
Everyone who is waiting to use Voice Actions, Chrome-to-phone, and any other cool 2.2-only apps.

Yeah, like real Flash or having the speed boost of the JIT compiler.

Very important. please read. x10 source petition.

This is for the benefit of all x10 Xperia users.
Sign this petition so we can gain any and all source or tools for our x10 from
Sony / Sony Ericsson.
This petition includes libraries for the camera, the screen or gpu and the touch input driver.
Only with your help can we truly make a difference.
http://www.change.org/petitions/sony-sony-erricson-source-code-if-any-available-for-the-x10-xperiahttp://www.change.org/petitions/sony-sony-erricson-source-code-if-any-available-for-the-x10-experia

Good idea.
Even today, our 4" screen, 1 GHz CPU, 8-32Gb SD machine is not that bad.
It's a sad thing that we bought a good Sony hardware limited by a very lame software.

Andre Verissimo said:
This is a temporary message, and I will edit it if somebody answer the question bellow.
Sometime ago, due to Android license, Sony posted in a technical site the source code file called
x10_x10mini_X10minipro_x8_eclair_2.1.A.0.435.tar.gz
that seems to have all the Eclair C-language source code, resources and makefiles for everything (including all the drivers [8,338 files], libs, scripts, kernel, firmware etc) inside our "Rachael" X10, and also for X10mini and X10minipro.
Is this what you're looking for?
Click to expand...
Click to collapse
Yes... but not exactly.
We also talking about getting these features working.
I believe we may be missing a few things.
There must also be 2.3 sources somewhere.
For interest sake.. could you link me to that source?
So far thanks for doing your best to free our device.
Would someone be so kind as to post this link on modaco?

Please, take a look at
http://developer.sonymobile.com/cws...load/x10x10minix10miniprox8eclair21a0435targz

Andre Verissimo said:
Please, take a look at
http://developer.sonymobile.com/cws...load/x10x10minix10miniprox8eclair21a0435targz
Click to expand...
Click to collapse
The question now... is everything truly there?

We are talking about 46,194 files inside 3,212 folders.
We need a real top developer / elite hacker (like z, The_Laser or DoomLord) to check it for us. Maybe this is what they were looking for.

Andre Verissimo said:
We need a real top developer / elite hacker (like z, DoomLord or The_Laser) to check it for us. Maybe this is what they were looking for.
Click to expand...
Click to collapse
It's very possible they already have it...
But i want to look deeper into the hardware.

They knew about that package long time ago in the kernel and bootloader passing thread.
Also, we WILL not have true multitouch cause this type of touch screen does not support it, all it can do is fake the dual touch. (As you see in new Xperia 2012 Sola phone, SONY combines this type of touch screen with new type (Arc type till now) so they can using without touch the screen, you will notice that you can use a soft cloth and touch the screen too)
About 16M colors, I'm not sure cause some source say this screen can display, some not.

silveraero said:
They knew about that package long time ago in the kernel and bootloader passing thread.
Click to expand...
Click to collapse
That means we are missing parts from the puzzle.
Continue voting please..
:edit
Thanks for editing after me hitting thanks.
Others are saying the opposite of what you have posted about the touch input.
We can still use the rest of the files.
Continue voting please..

Just wrote there some words from my heart . Best wishes about this petition. I hope Sony make some surprise for us. I really count on it, cause I wanted it so long, to make my projects better .

DiKeJ said:
Just wrote there some words from my heart . Best wishes about this petition. I hope Sony make some surprise for us. I really count on it, cause I wanted it so long, to make my projects better .
Click to expand...
Click to collapse
I'm out of thanks..
Thanks allot.
we need all the support we can with this.

Oh ya, I wanna vote too but that site require postal code or zip code that my country does not use and keep saying not recognise. What the hell?

Andre Verissimo said:
Please, take a look at
http://developer.sonymobile.com/cws...load/x10x10minix10miniprox8eclair21a0435targz
Click to expand...
Click to collapse
I just had a quick glance over the included kernel, which is of version 2.6.29 (As expected)
It's codename is "Temporary Tasmanian Devil"
As far as I can see with this quick glance, I cannot find any Sony / Sony Ericsson specific patches that might be needed for some of the devices hardware, such as the wireless and camera. The default source from the official kernel is there.
I haven't checked it out thorough yet, but It might be as some of us suspect: Some needed patches or "addins" might not be included at all.
I cannot find any separate patch files either, nor any signs where they could be.
It simply could mean that this included kernel is pre-patched, so someone need to extract these patches by comparing it to standard/official Android Linux 2.6.29 kernel sources.
Someone might ask: -"Isn't it the case that the default/standard Android Linux kernel 2.6.29 is the proper one?"
Well if that was the case, many problems would have been solved a long time ago. We know how hard it was to get the camera, wifi, bluetooth and some other hardware to work properly, as people either needed to pull small parts out of SE's developers, or simply reverse-engineer them.
My suspicion after the quick glance over:
We're having a default Android 2.6.29 Linux kernel without patches.
There's some included code in sub-folders under vendor/semc folder. Glansing that one over, it also appear to be some default sources. Nothing that stands out. But then I'm no expert in this.
I can be completely wrong here, as I just glanced it all over. Please do correct if I'm wrong (Which I hope to be ).

Signed and wrote a few words. I hope to God that our phones could be what they were meant to be or at least could be. Good luck Omega.

voted!!
Hope for the best

thanks guys keep it up.

Interesting comment from DooMLoRD.
yes i know... Sony is ahead of others in this matter... their low end device Tapioca (ST2x/WT2x) is going to have ICS!!! and trust me its going to create a HUGE uproar by users of X10, X10 mini, X10 mini pro, X8 as they have similar hardware to Tapioca...
Click to expand...
Click to collapse
we have better processor and screen than rumoured Tapioca but less ram.

OmegaRED^ said:
This is for the benefit of all x10 Xperia users.
Sign this petition so we can gain any and all source or tools for our x10 from
Sony / Sony Ericsson.
This petition includes libraries for the camera, the screen or gpu and the touch input driver.
Only with your help can we truly make a difference.
http://www.change.org/petitions/sony-sony-erricson-source-code-if-any-available-for-the-x10-xperiahttp://www.change.org/petitions/sony-sony-erricson-source-code-if-any-available-for-the-x10-experia
Click to expand...
Click to collapse
Will this really work.
Petition signed
Sent from my LT26i using xda premium

THeLogiC said:
we have better processor and screen than rumoured Tapioca but less ram.
Click to expand...
Click to collapse
It's just business. They won't relase official ICS for device which has 3 years. Of course it's possible, but then they won't sell newer devices from 2011 or 2012 line. All what they can do is give us sources - then we start magic .
BTW: I can tell that many polish people signed on this petition - I think my forum made a trick . Thank you all patriots!

Hoping this comes to life
Sent from my X10S using xda premium

Looking For Tablet ROM With More Complete S-Pen Support

Hello. I have written an app that helps to improve the accuracy of the S-Pen. It works only on Note phones because Samsung has compiled some S-Pen device driver interfaces out of the tablet ROMs. It is not clear why they did this. I have asked Samsung but gotten no replies. I have confirmed that parts of the kernel code is commented out in the open source kernel code (and you can see that some of the interface files found on phones do not exist on the tablets). It seems that the tablets suffer from the same issues related to the S-Pen as do the phones and I have many people asking me to make my app work on their tablets. I cannot do so with the stock ROMs because of the missing interface files.
So I am wondering if there any non-stock ROMs in which the S-Pen is more fully supported. The missing files are located on my phone in /sys/class/sec/sec_epen/ and the two files I need are called epen_hand and epen_rotation. If anyone knows of any ROMs for the S-Pen equipped tablets that provide these interface files, I would appreciate knowing and may be able to direct some folks to using them.
Thanks

I can confirm that neither are present in Baked build 8, it might be worth checking a dump from the note 8.0
Regards
Jack

JSale said:
I can confirm that neither are present in Baked build 8, it might be worth checking a dump from the note 8.0
Regards
Jack
Click to expand...
Click to collapse
Jack, some replies to postings in the Note 8 section indicate that the two files are present on the stock ROM there. Interesting... I am downloading a dump of the 10.1 now to see if I can see anything. Thanks

Any progress on this? It looks quite promising in the note 8.0 forums.
Regards
Jack

whitedavidp said:
I have confirmed that parts of the kernel code is commented out in the open source kernel code (and you can see that some of the interface files found on phones do not exist on the tablets). ... The missing files are located on my phone in /sys/class/sec/sec_epen/ and the two files I need are called epen_hand and epen_rotation ...
Click to expand...
Click to collapse
Well, since this is presumably a kernel issue, I'll look into it (PM me with your E-mail address) and IF there's anything that can be done about it (i.e., if the corresponding actions are available in the pen driver; it's not enough to just be able to integrate the sysfs entries) I'll add it into the kernels I release for the Note 10.1

kcrudup said:
Well, since this is presumably a kernel issue, I'll look into it (PM me with your E-mail address) and IF there's anything that can be done about it (i.e., if the corresponding actions are available in the pen driver; it's not enough to just be able to integrate the sysfs entries) I'll add it into the kernels I release for the Note 10.1
Click to expand...
Click to collapse
Hello and thanks for responding/helping out. I am certainly no kernel programmer. But I have downloaded the kernel sources for a couple official Note devices/versions. I have been reading files located in kernel/drivers/input/touchscreen/wacom paying particular attention to the file wacom_i2c.c. I cannot help but note that some of the functions which appear to reference the driver i/o files that are missing are #def'ed out of certain devices - see line 837 #if defined(CONFIG_MACH_P4NOTE).
I have no idea if the Wacom devices used in the various Note models are the same (except for size) or are similar enough to be treated as the same by programs like mine. Heck, I am not even sure if Wacom devices are being used in all the Note models. So I am afraid I am not much in the way of technical help here.
What I do know is that some custom ROMs for Note I and II phones seem to have been created with drivers that DO support and create the needed driver i/o files but which lack the device settings and other mechanisms which actually take advantage of these i/o files. Basically, they do not offer a dominant hand setting nor do they seem to communicate to the Wacom device when an orientation change is detected. I have been able, through my app, to compensate for these lapses on those devices and thereby improve the SPen's accuracy.
I have had users wanting to get the same effect on Note tablets with my app. So I presume they are experiencing the same type of problem on their tablets that I experienced on my Note I phone that led me to get into all of this. But I know that my app cannot help them unless the i/o files are there.
I was surprised to hear, over in the Note 8 forum that the files do exist on those devices. I know from a tester that my app at least runs on the Note 8. But I don't know if it helps any since that tester was not seeing the problem my app is designed to fix. But I read here that the files are not on the larger Note tablets. I don't know why and have asked Samsung and get basically no answer. My underlying assumption is that the Wacom devices are basically the same but I cannot answer why Samsung treats them as different.
I am sure all of this doesn't help much. Sorry. All I would like to do is try to find a way to offer support to the tablet users who want it.
Cheers!

Try this kernel: http://goo.gl/OBJ4O (PM also sent).

kcrudup said:
Try this kernel: http://goo.gl/OBJ4O (PM also sent).
Click to expand...
Click to collapse
Im going to quickly revert from baked to android revolution to test this
I will let you know what I think.
Regards
Jack

JSale said:
I'm going to quickly revert from baked to android revolution to test this
Click to expand...
Click to collapse
No, this is just a kernel- you won't have to change distributions to try this.

kcrudup said:
No, this is just a kernel- you won't have to change distributions to try this.
Click to expand...
Click to collapse
But baked is based on CyanogenMod, unless this kernel is compatible?

kcrudup said:
Try this kernel: http://goo.gl/OBJ4O (PM also sent).
Click to expand...
Click to collapse
Sadly, I don't own one of these tablets (yet). But I have passed this on to a user who previously asked me (and got this thread rolling as a result). So perhaps he can check it out and try my app on it. If he does, I will certainly report back here. Thanks for your efforts.

JSale said:
But baked is based on CyanogenMod
Click to expand...
Click to collapse
Oh, then yeah- as I suspect CM won't have any of the SPen goodies. My bad.
In any case, let me know. It was a very trivial fix and didn't appear to break anything. I don't use the SPen much at all, but a quick test with SNote appears that everything still seems to work OK.
(But I did notice that the stock Samsung ROM (CMD2) does set these variables, which is unusual as these sysfs entries "shouldn't exist", but it seemed to (re)set them to default values. I wonder if this is used as part of a version check of some sort?)

Well, after a little bi of testing, I can conclude that this fix has indeed improved the accuracy of the s-pen. It is hard to tell by how much, as I never had very terrible offsets myself, but at the edge of the screen, this has reduced the offsets by an observable amount.
Would it be possible to get the kernel fix implemented into the app so that I can use it on Baked rom ?
Many regards for all the hard work
Jack

JSale said:
Well, after a little bi of testing, I can conclude that this fix has indeed improved the accuracy of the s-pen. It is hard to tell by how much, as I never had very terrible offsets myself, but at the edge of the screen, this has reduced the offsets by an observable amount.
Would it be possible to get the kernel fix implemented into the app so that I can use it on Baked rom ?
Many regards for all the hard work
Jack
Click to expand...
Click to collapse
Wow! Thanks for the testing and for the feedback on your results. This is quite interesting. I am not quite sure I can integrate this sort of thing into my app although it may be possible. The kernels for the Samsung devices I have looked at seem quite monolithic rather than modular. But I do know that one app, TouchScreenTune, does something that fiddles with the kernel in some way I do not fully understand. So perhaps. I would sure need help and direction. But it would be very cool indeed.

JSale said:
Would it be possible to get the kernel fix implemented into the app so that I can use it on Baked ROM?
Click to expand...
Click to collapse
Well, the "kernel", the "ROM" and whichever app it uses are quite different things, but at least I can offer up the "commit" that makes it possible in the kernel (which has to then be pasted into a ROM). Have a/the Dev PM me.
whitedavidp said:
But I do know that one app, TouchScreenTune, does something that fiddles with the kernel in some way I do not fully understand.
Click to expand...
Click to collapse
Most likely via a "sysfs" file, which seems to be the preferred method for this driver.

kcrudup said:
Well, the "kernel", the "ROM" and whichever app it uses are quite different things, but at least I can offer up the "commit" that makes it possible in the kernel (which has to then be pasted into a ROM). Have a/the Dev PM me.
Most likely via a "sysfs" file, which seems to be the preferred method for this driver.
Click to expand...
Click to collapse
If I want to point users of my app to your kernel as a means of gaining more SPen support, where should I send them? Does the Kernel have a main web page? And if so, what version should I point them towards? Thanks

whitedavidp said:
If I want to point users of my app to your kernel as a means of gaining more SPen support, where should I send them?
Click to expand...
Click to collapse
Well, right now the only kernel that's got this particular support is the one I've posted here- but every now and then I post up a kernel boot.img file for the latest Android Revolution ROM and for Darkman's latest Stock ROM and this patch will be included in those going forward. Most boot.img files among the various Note 10.1 devices are close enough that they'll almost always work for any ROM, Stock or Custom.
I don't keep any seperate thread or site for my kernel, as I'm really just sharing my own personal (yet improved and faster) kernel for Note 10.1 devices (and frankly don't feel like dealing with the inevitable newbie questions that a standalone offering would generate).
But I have a number of commits I'm about to push to my GitHub page; once I do that (give me a day or two, I've made some major changes to the kernel source and I'll need to verify all's well before I make them Public) I'll come back here with the GitHub commit web-page URL, then you can pass that to any ROM/Kernel dev and they can easily incorporate it in their particular builds (it's a really trvial patch, too- I just removed the 3 "#else" directives embedded in the "#ifdef CONFIG_MACH_P4NOTE" conditionals).

kcrudup said:
Well, right now the only kernel that's got this particular support is the one I've posted here- but every now and then I post up a kernel boot.img file for the latest Android Revolution ROM and for Darkman's latest Stock ROM and this patch will be included in those going forward. Most boot.img files among the various Note 10.1 devices are close enough that they'll almost always work for any ROM, Stock or Custom.
I don't keep any seperate thread or site for my kernel, as I'm really just sharing my own personal (yet improved and faster) kernel for Note 10.1 devices (and frankly don't feel like dealing with the inevitable newbie questions that a standalone offering would generate).
But I have a number of commits I'm about to push to my GitHub page; once I do that (give me a day or two, I've made some major changes to the kernel source and I'll need to verify all's well before I make them Public) I'll come back here with the GitHub commit web-page URL, then you can pass that to any ROM/Kernel dev and they can easily incorporate it in their particular builds (it's a really trvial patch, too- I just removed the 3 "#else" directives embedded in the "#ifdef CONFIG_MACH_P4NOTE" conditionals).
Click to expand...
Click to collapse
Thanks very much once again!

whitedavidp said:
Thanks very much once again!
Click to expand...
Click to collapse
The app seems to work with this kernel :good:
kcrudup said:
Well, right now the only kernel that's got this particular support is the one I've posted here- but every now and then I post up a kernel boot.img file for the latest Android Revolution ROM and for Darkman's latest Stock ROM and this patch will be included in those going forward. Most boot.img files among the various Note 10.1 devices are close enough that they'll almost always work for any ROM, Stock or Custom.
I don't keep any seperate thread or site for my kernel, as I'm really just sharing my own personal (yet improved and faster) kernel for Note 10.1 devices (and frankly don't feel like dealing with the inevitable newbie questions that a standalone offering would generate).
But I have a number of commits I'm about to push to my GitHub page; once I do that (give me a day or two, I've made some major changes to the kernel source and I'll need to verify all's well before I make them Public) I'll come back here with the GitHub commit web-page URL, then you can pass that to any ROM/Kernel dev and they can easily incorporate it in their particular builds (it's a really trvial patch, too- I just removed the 3 "#else" directives embedded in the "#ifdef CONFIG_MACH_P4NOTE" conditionals).
Click to expand...
Click to collapse
I really want to know what are the features of this kernel ... would i keep it or there are other ones that have this functionality right now?? OR could just this changes be added to the Stock kernel to only have Spen support .. as i dont want any OC or custom governers :good: :good:

whitedavidp said:
If I want to point users of my app to your kernel as a means of gaining more SPen support, where should I send them? Does the Kernel have a main web page? And if so, what version should I point them towards? Thanks
Click to expand...
Click to collapse
May I ask you what application you are talking about?
@kcrudup Have you already decided to release your kernel in a separate thread or not?

BeanStalk port worked! Waiting for Scott's permission to post in dev section

I used this rom on my Samsung infuse and it would be awesome if a dev could port it to the s4!
If you look on the original thread in the infuse forums you can see step by step instructions on how to port it.
I tries to do it, but don't know how to do step 6.
It turns out I was able to do it on my own!

chrisc93 said:
I used this rom on my Samsung infuse and it would be awesome if a dev could port it to the s4!
If you look on the original thread in the infuse forums you can see step by step instructions on how to port it.
I tries to do it, but don't know how to do step 6.
Click to expand...
Click to collapse
That rom is AOSP-based. So why don't you just try one of the other AOSP-based roms around here, such as AOKP or SlimBean?

mattdm said:
That rom is AOSP-based. So why don't you just try one of the other AOSP-based roms around here, such as AOKP or SlimBean?
Click to expand...
Click to collapse
I am currently running Task's AOKP and it is really nice (i found it better than Slim on the s4), but BeanStalk has more features.
I was just wondering if it would be possible to get BeanStalk ported.
Thanks for the reply!

chrisc93 said:
I am currently running Task's AOKP and it is really nice (i found it better than Slim on the s4), but BeanStalk has more features.
I was just wondering if it would be possible to get BeanStalk ported.
Thanks for the reply!
Click to expand...
Click to collapse
It's not really easy whatsoever to port a Rom that is for a different device especially if the resolution is different for the other Phone.
Sent from my SGH-M919 using Tapatalk 2

I am unfamiliar with porting, so it is good to know it's not an easy task.
Thanks for your answer!

jetlitheone said:
It's not really easy whatsoever to port a Rom that is for a different device especially if the resolution is different for the other Phone.
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
That's where source comes in handy...it eliminates a lot of those issues, really all we need is xxhdpi (we should be able to cherrypick that from cm when needed) to be added into aosp and then source porting should be a breeze for the most part - if you know how to build from source that is...actually building a custom aosp rom like scotts, that's a different story
Zip porting is where resolution and all that stuff makes it hard/not possible
Just look at cm...its available on nearly every device...why? Because its got its source up. Basically all you need to do is add in all the correct hardware source, kernel sources, device sources and proprietary files and your good...not saying its easy, as you do need to figure out what you need to add in, as well as edit a few files...but its definitely not really hard (although some of those errors you run into do make you want to throw your computer out a window)
-I guess it is a little hard, but for the most part its pretty much the same for any source port...trial and error your way through errors until it builds
Anyways, I'm sure someone will get around to it...I was gonna try and compile pure aosp...but my dev environment needs to be updated before I can start compiling again (been months since I compiled anything)
If it can be ported to the galaxy s3, than it can be ported to the galaxy s4 (I'm not saying the two are similar, but both are completely different from the Samsung infuse)
Sent from my HTC PH39100 using Tapatalk 2

mg2195 said:
That's where source comes in handy...it eliminates a lot of those issues, really all we need is xxhdpi (we should be able to cherrypick that from cm when needed) to be added into aosp and then source porting should be a breeze for the most part - if you know how to build from source that is...actually building a custom aosp rom like scotts, that's a different story
Zip porting is where resolution and all that stuff makes it hard/not possible
Just look at cm...its available on nearly every device...why? Because its got its source up. Basically all you need to do is add in all the correct hardware source, kernel sources, device sources and proprietary files and your good...not saying its easy, as you do need to figure out what you need to add in, as well as edit a few files...but its definitely not really hard (although some of those errors you run into do make you want to throw your computer out a window)
-I guess it is a little hard, but for the most part its pretty much the same for any source port...trial and error your way through errors until it builds
Anyways, I'm sure someone will get around to it...I was gonna try and compile pure aosp...but my dev environment needs to be updated before I can start compiling again (been months since I compiled anything)
If it can be ported to the galaxy s3, than it can be ported to the galaxy s4 (I'm not saying the two are similar, but both are completely different from the Samsung infuse)
Click to expand...
Click to collapse
Wow this was some great info!
I've never built from source, but I'm going to give it a try with TMO's cm 10 for the s4. Just to get a grip on dev'ing.
Thanks.
EDIT: Actually, it looks like cyanogenmod has the galaxy s4 AT&T github repo up to date. I may just try to build using that source.

chrisc93 said:
Wow this was some great info!
I've never built from source, but I'm going to give it a try with TMO's cm 10 for the s4. Just to get a grip on dev'ing.
Thanks.
EDIT: Actually, it looks like cyanogenmod has the galaxy s4 AT&T github repo up to date. I may just try to build using that source.
Click to expand...
Click to collapse
Please keep in mind, in order to build from source you must have linux...actually I think Mac works too...but windows won't
Follow the link in my signature, its full of a bunch of tutorials, somewhere close to the top should be a thread called compile jb from ubuntu or something like that...follow that thread to get you started and get you build environment set up
-it is very confusing at first especially if your new to linux, bit once you get going it gets easier
Anyways, good luck!!! The great thing about porting from source is it gets your feet wet, gets you used to the basics with source...and eventually you can get experimental and start creating your own source roms...also, it is kinda addicting lol, for a while I was compiling non stop...I went from a flashaholic to a compileaholic lol...now, I'm neither due to my busy schedule but summer is just around the corner for me so that should change
Sent from my HTC PH39100 using Tapatalk 2

mg2195 said:
Anyways, good luck!!! The great thing about porting from source is it gets your feet wet, gets you used to the basics with source...and eventually you can get experimental and start creating your own source roms...also, it is kinda addicting lol, for a while I was compiling non stop...I went from a flashaholic to a compileaholic lol...now, I'm neither due to my busy schedule but summer is just around the corner for me so that should change
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
Thanks! I'm looking forward to the challenge! Who knows, maybe I'll become a compileaholic too :laugh::laugh:

There is a build for the gs2 skyrocket here
http://forum.xda-developers.com/showthread.php?t=2249072
Not sure if that helps at all...
Sent from my AT&T Galaxy S4 Running AOKP 4.2.2

Just wanted to check in and let you all know that I successfully built cm10 for the galaxy s4! Used the source from the official branch. It's a pretty neat feeling knowing that I built the rom from source (and it's really neat seeing my name in the build date ) :victory:
I'm going to be contacting scott to see if he can help me build his rom. I already synced his repo on my computer, so I'm hoping the rest won't be too hard. :fingers-crossed:
Thanks @mg2195 for the help! :highfive:

I did it!
I am running the latest version of BeanStalk on my s4!!!!
I will make a new thread in the dev section as soon as I get permission. This rom is awesome!
:victory:

Felt like this deserved some attention

As johnny drama would say.... VICTORYYYYYY!!
Sent from my GT-I9505 using xda premium

I'm am on my infuse ATM and am running Beanstalk. My S4 is on the fedex truck on the route to my house and I'm super excited and pumped to see this may be coming to the S4 if it does I may just keep my phone
Sent from my SGH-I997 using xda premium

Fx0/Madai Kernel: Version WTF?

The kernel source that LG posted on their opensource distribution site is not the code for the latest shipping version. Is that cool? Do they have any responsibility to provide the source for the newest version the shipped?
I wonder if the code they released matches earlier versions even. If only I could track down a rip of the system & boot images from the original version that shipped in Dec. 2014. Or even for the version after that. If anyone has one of those laying about, thanks, yo.

I have no idea, but that doesn't sound right.
Are you looking to unlock the bootloader so people can flash updated FFXOS ROMs to the device?

Saijin_Naib said:
I have no idea, but that doesn't sound right.
Are you looking to unlock the bootloader so people can flash updated FFXOS ROMs to the device?
Click to expand...
Click to collapse
Actually, I think I was wrong. Gah! I didn't realize that the prima_wlan stuff could be included included from outside the kernel tree. A qcom opensource repo is maybe where they built it from maybe?
> unlock the bootloader
No problems there, the Fx0 is wide-open. Like other LG devices, once you clear the CAF you gain Fastboot, and from there this device is splayed all day. You lose Download Mode, but since neither Mozilla or LG have seen fit to provide any of the usual KDZ images for that, I can't see any downsides. Maybe if they decide to update the Fx0 it would get used? I think it'd update in recovery instead though, yes?
Still want rips of Japanese system partition though. I wonder if the hiddenmenu is also stripped from those versions with v2.1 also? I want that hiddenmenu.

I have no idea. I'm not familiar at all with setting up a repo or anything. I've only ever build the ZTE Open repos provided by Mozilla, haha.
Oh, that is promising. What is the CAF?
Are you looking to get your Fx0 up and running with nightlies? If things actually work, I might grab one from eBay as a development/testing device as well.

Saijin_Naib said:
I have no idea. I'm not familiar at all with setting up a repo or anything. I've only ever build the ZTE Open repos provided by Mozilla, haha.
Oh, that is promising. What is the CAF?
Are you looking to get your Fx0 up and running with nightlies? If things actually work, I might grab one from eBay as a development/testing device as well.
Click to expand...
Click to collapse
Err, I meant LAF, its the partition on some LG devices where the Download Mode boot image lives. I've been spending a lot of time with my head buried in Codeaurora(CAF) repos, it's on the tip of my tongue.
Are you looking to get your Fx0 up and running with nightlies?
Click to expand...
Click to collapse
I already have to some extent. I should have a fully-functional test build any day now. Been codeblocked by some frustrating commits from Mozilla lately, broke my crap like 3 damn times in the last week. Refining the whole build setup now, trying to minimize reliance on prebuilt stuff, building as much as can, hence the interest in the pronto_wlan module, which I assumed was something that was exclusively build in the kernel tree (as seen on other LG devices), but apparently there's a CAF repo for that. Anyway, yeah.

culot said:
Err, I meant LAF, its the partition on some LG devices where the Download Mode boot image lives. I've been spending a lot of time with my head buried in Codeaurora(CAF) repos, it's on the tip of my tongue.
Click to expand...
Click to collapse
Ah, good to know. I'm a bit saddened to see that the prices on the Fx0 have gone up since just this past weekend. These must be getting more and more popular...
As an aside, you wouldn't happen to be knowledgeable about how to root the LGE LGL15G (LG Sunrise, 4.4.2, TracFone). I bought one as a beta testing device and as an Android Tablet/Wi-Fi toy, but there is no space on it due to the included bloatware O_O
culot said:
I already have to some extent. I should have a fully-functional test build any day now. Been codeblocked by some frustrating commits from Mozilla lately, broke my crap like 3 damn times in the last week. Refining the whole build setup now, trying to minimize reliance on prebuilt stuff, building as much as can, hence the interest in the pronto_wlan module, which I assumed was something that was exclusively build in the kernel tree (as seen on other LG devices), but apparently there's a CAF repo for that. Anyway, yeah.
Click to expand...
Click to collapse
I was reading on the Mozilla wiki that they've been doing some code cleanup to transition FFXOS to B2G, and to make it so the community can maintain it. Apparently, they've been a bunch of busy bees debranding everything and settling dependencies. Is this why your builds have been busted?
Do you think the Fx0 could replace the Flame as the defacto B2G development/testing device?
I'm torn between getting one for grabbing yet another ZTE Open and smashing my face against the wall trying to get it to fully work with nightly builds.
What's in that hiddenmenu? That isn't the normal developer tools menu I'm used to, right?
Is it the Blaze Initiative stuff (themeing, hacking, add-ons, mods, etc)?

Saijin_Naib said:
Ah, good to know. I'm a bit saddened to see that the prices on the Fx0 have gone up since just this past weekend. These must be getting more and more popular...
As an aside, you wouldn't happen to be knowledgeable about how to root the LGE LGL15G (LG Sunrise, 4.4.2, TracFone). I bought one as a beta testing device and as an Android Tablet/Wi-Fi toy, but there is no space on it due to the included bloatware O_O
I was reading on the Mozilla wiki that they've been doing some code cleanup to transition FFXOS to B2G, and to make it so the community can maintain it. Apparently, they've been a bunch of busy bees debranding everything and settling dependencies. Is this why your builds have been busted?
Do you think the Fx0 could replace the Flame as the defacto B2G development/testing device?
I'm torn between getting one for grabbing yet another ZTE Open and smashing my face against the wall trying to get it to fully work with nightly builds.
What's in that hiddenmenu? That isn't the normal developer tools menu I'm used to, right?
Is it the Blaze Initiative stuff (themeing, hacking, add-ons, mods, etc)?
Click to expand...
Click to collapse
Do you think the Fx0 could replace the Flame as the defacto B2G development/testing device?
Click to expand...
Click to collapse
Considering how much proprietary LG stuff is on the Fx0, I doubt it. Dunno. Since FxoS is transitioning to B2G is there even a need for a official dev device? I have no idea really.
What's in that hiddenmenu? That isn't the normal developer tools menu I'm used to, right?
Click to expand...
Click to collapse
Just the usual LG-specific hiddenmenu stuff. It seems like it was included in the initial release version for the Fx0... but from there, I don't know. Too bad I can't find any of the previous versions anywhere. Somebody must have them, somewhere.
Is it the Blaze Initiative stuff (themeing, hacking, add-ons, mods, etc)?
Click to expand...
Click to collapse
I have no idea what that is. Tell me more!
root the LGE LGL15G
Click to expand...
Click to collapse
No, I don't know anything about that. I did try one once, seemed like a decent value for the $15 or so it was selling for.

culot said:
Considering how much proprietary LG stuff is on the Fx0, I doubt it. Dunno. Since FxoS is transitioning to B2G is there even a need for a official dev device? I have no idea really.
Click to expand...
Click to collapse
Drat. I was hoping they (LG) had opened up some of the binary blobs in their source release. I guess you're right in that there is no need for an official dev device, but much like with LuneOS, I think there is a need for a "supported" target/reference device that sets the baseline for functionality. I was hoping the Fx0 could be this device, but with your evaluation of it being still a highly closed, it sounds like a poor choice.
culot said:
Just the usual LG-specific hiddenmenu stuff. It seems like it was included in the initial release version for the Fx0... but from there, I don't know. Too bad I can't find any of the previous versions anywhere. Somebody must have them, somewhere.
Click to expand...
Click to collapse
I've never seen this menu. Do the new Fx0 devices sold on eBay have this OS image installed, or is it something that was only shipped on the KDDI carrier sold devices?
culot said:
I have no idea what that is. Tell me more!
Click to expand...
Click to collapse
The Blaze initiative was a path Mozilla were looking to take FireFoxOS on by allowing the OS to be customized and tweaked much like the desktop browser. The device would have the ability to call up the DevTools to edit the code of any running webapp to modify the appearance and functionality of the program. From what I had read, this would extend to even privileged/system apps. In this manner, the user could add something to say the Messages app (like a timestamp for how late a message arrived), change the background color of the messages thread, etc. These add-ons could be submitted to the Marketplace for certification and download. Also, it was likely that users could directly share these modifications by Sharing activities including Email, SMS, etc.
There was also talk of migrating over various XUL add-ons from the desktop browser that would be compatible with FFXOS. That alone would have made the platform borderline unstoppable, as the possibilities for expansion of utility, safety, and aesthetics would be nearly endless.
All of this being said, I can't currently find the articles about this initiative anymore. I'll keep looking.
culot said:
No, I don't know anything about that. I did try one once, seemed like a decent value for the $15 or so it was selling for.
Click to expand...
Click to collapse
I got mine for $9.99, and it benches out to being fairly comparable to the Moto E, which is not a bad performance point to be at for around $10. Shame it is SIM-locked and very difficult to root and take the garbageware out of.

Saijin_Naib said:
I've never seen this menu. Do the new Fx0 devices sold on eBay have this OS image installed, or is it something that was only shipped on the KDDI carrier sold devices?.
Click to expand...
Click to collapse
It looks like maybe the hiddenmenu was removed with a FxOS v2 update that added the ability to edit APNs, something that had to be done in the hiddenmenu previsouly. Maybe...

Ah, crap, I was wrong: the hiddenmenu, along with a ton of other LG & KDDI stuff, was stripped out of the international/unlocked version, leaving it a slow, featureless shell. It's disgusting actually. I feel acutely slighted. It's amazing the difference between both the speed and the features of the Japanese and unlocked versions. Apparently in Japan this is actually a decent phone. Too bad the international/unlocked peeps got the shaft.
And here I thought FxOS in general was just slow and terrible: turns out that was just result of the hatchet job pulled on the unlocked variants of the Fx0.
I wonder if it would be possible to overcome the mozfree issue that prevents the old libs from working on newer B2G?
Gah! I feel angry.

Hey. Do you still want the original jap 2.0 images?

aflaton said:
Hey. Do you still want the original jap 2.0 images?
Click to expand...
Click to collapse
If you have a retail firmware, it would be much appreciated.