Database Info

[ROM] AOSP Mesmerize Vanilla Froyo ALPHA 0.1

I have finally, successfully, gotten jt1134's device tree and Froyo framework all configured for the Mesmerize. This is a Vanilla Froyo (no Cyanogenmod) build and works enough to play around with (= But, I should warn you, this isn't a terribly stable build, so don't freak out if something acts weird d= Also, I'm not responsible for any harm you may do to your devices..
It's late and I have an 8:00 am tomorrow so I haven't tested everything out yet, but what is working and not working should be similar to what jt1134 has listed over in his Fascinate thread. Here's what I've tried though:
Working:
Phone
SMS
GPS
WiFi
Not Working:
Data?
Bluetooth
Camera
sdcard?
Oh, and it may randomly 'boot loop' a few times.. don't freak out though.
For this to work you need to be using the Mesmerize Froyo kernel I recently posted. To get everything setup just download the ROM and the Kernel and put them on your sdcard. Boot into recovery and make a backup. Wipe your data and cache partition. Flash the ROM. Flash the Kernel. Reboot. Froyo! If you're going to try to adopt this ROM for everyday use (good luck), make sure you grab the GApps package and flash that last.
I haven't got a Mesmerize device tree on github yet, but you can find the alterations to the kernel up. Really, you should look at jt's source/github because that's where all the dirty work is done (= Also, some of his work is under ModADroid on github.
Download Links:
Mesmerize Vanilla Froyo ROM: http://dl.dropbox.com/u/464066/Mesmerize/ROMs/froyo_mesmerize_0122.zip
Mesmerize Froyo Voodoo Kernel: http://dl.dropbox.com/u/464066/Mesmerize/Kernels/0123_mesmerize_voodoo5.zip
I'll post a link to a nonvoodoo kernel when I get one compiled.
Froyo GApps: http://goo-inside.me/google-apps/gapps-hdpi-20101114-signed.zip
Be careful!! This kernel is named the same as jt's Voodoo Sound 2.1 Kernel that he released yesterday. You may want to rename one of the two if you plan on using both. The ROM will bootloop or freeze at the lockscreen if you mistakenly use a 2.1 kernel (=
Source:
http://github.com/jt1134
http://github.com/dcow
Credits:
jt1134 <-- for all the SCH-I500 framework work
punk-kaos <-- for his contributions to the SCH-I500 framework
phidelt82 <-- for keeping me company late at night (not like that.. ..) and for letting me bounce ideas off of him, calling me out when I'm being stupid, and flashing whatever I throw at him (=
Enjoy!

Let me be the first! Thank you so much this should hold me over until official release comes out.. Maybe even then lol, thanks again.
Sent from my SCH-I500 using XDA App

cpfeifer said:
Let me be the first! Thank you so much this should hold me over until official release comes out.. Maybe even then lol, thanks again.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Perhaps if we get a to a final release or beta then. I don't think you'll be wanting to employ this for everyday use until we get more issues fixed.

cpfeifer said:
Let me be the first! Thank you so much this should hold me over until official release comes out.. Maybe even then lol, thanks again.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
dcow90 said:
Perhaps if we get a to a final release or beta then. I don't think you'll be wanting to employ this for everyday use until we get more issues fixed.
Click to expand...
Click to collapse
It was definitely fun to play with, but yeah, as for everyday use, there is still work to do. Hopefully soon though. I know I'll be digging in some more tonight to see if I can find anything fixes.

be glad to help test things once you get a little bit more stable with this.
Sent from my SCH-I500 using Tapatalk

phidelt82 said:
It was definitely fun to play with, but yeah, as for everyday use, there is still work to do. Hopefully soon though. I know I'll be digging in some more tonight to see if I can find anything fixes.
Click to expand...
Click to collapse
The sdcard issue is just a problem with the init.rc I think.. but we'll see whats still not working after I get jt's latest source built and we can work from there.
Sent from my USCC SCH-I500..

dcow90 said:
The sdcard issue is just a problem with the init.rc I think.. but we'll see whats still not working after I get jt's latest source built and we can work from there.
Sent from my USCC SCH-I500..
Click to expand...
Click to collapse
I think it has to do with the mounting. It looked the same as the other init.rc's that I was looking at, but it was all running together at that point last night. I'll dig into it some more tonight and look at the mounting of the base init file and see what I can come up with. Hopefully something will jump out.

Dont pull bin/vold from a prebuilt image, make sure you're building the aosp version. Also, make sure you are pulling prebuilt/vold.fstab from my device repo.
Android uses the vold daemon and fstab files to manage sdcard mounts, not a simple mount command like the ones used in init.rc for other partitions.
Sent from my SCH-I500 using XDA App

Thank you guys for all the hard work!

Looking forward to trying this out! Just to be sure- when I'm done playing I can go straight back to the exact way I have it now as long as I have a nandroid backup? No harm done?
sent from my superclean mesmerize

co6alt said:
Looking forward to trying this out! Just to be sure- when I'm done playing I can go straight back to the exact way I have it now as long as I have a nandroid backup? No harm done?
sent from my superclean mesmerize
Click to expand...
Click to collapse
No, you also need to revert to a 2.1 kernel as well. I mean 2.1 will boot on this kernel, but I can't say that it will work perfectly, and I found my scdard still didn't after a restore until I reverted kernels.

So restoring doesn't change the kernels, just the rom?
sent from my superclean mesmerize

co6alt said:
So restoring doesn't change the kernels, just the rom?
sent from my superclean mesmerize
Click to expand...
Click to collapse
What you should do is download jt1134's Mesmerize Voodoo5 w/ Voodoo Sound kernel and flash it. You should then take a backup in perfect working order. If you want to play with 2.2, wipe, flash the rom, then kernel. When you're done, wipe, restore the backup, then flash the previous kernel.

Gotcha. Ha, I just found out about voodoo sound. That'll be tonights project, then 2.2 tomorrow hate this edge network junk
sent from my superclean mesmerize

co6alt said:
Gotcha. Ha, I just found out about voodoo sound. That'll be tonights project, then 2.2 tomorrow hate this edge network junk
sent from my superclean mesmerize
Click to expand...
Click to collapse
EDGE? AT&T.. What?
I've got the source downloading for jt's latest build so hopefully we'll have some improvements soon. (=

dcow90 said:
EDGE? AT&T.. What?
I've got the source downloading for jt's latest build so hopefully we'll have some improvements soon. (=
Click to expand...
Click to collapse
Sweet waiting for a few more things to be functioning before I try using it. Thought maybe about trying to tomorrow but only as a test.
Edit: I just flashes the ROM and Kernel last night 0 problems booting and starting up phone was basically functioning then when I installed the Froyo Gapps I couldn't use the phone anymore because no data connection couldn't get passed the google account setup but seemed to work.
The only thing that was weird is before I installed the gapps zip while playing around the phone kept going back to the silver Android logo seeming as if it was restarting and going back to the lock screen but I managed to test the Phone, called 611 got US Cellular so that works!
Thanks again for your work I definitely and looking forward to this.

Big thanks to the devs! This is an awesome step forward. I flashed the ROM and Kernel, and although it's definitely alpha, it's awesome progress!
<rant>
It's pitiful that team of hobbyists and enthusiasts, working for free, in their spare time can port 2.2 faster than Samsung, who employs a full staff of software and hardware engineers, armed with development tools and source code. SAMSUNG, YOU SHOULD BE ASHAMED.
</rant>

Yoder808 said:
Big thanks to the devs! This is an awesome step forward. I flashed the ROM and Kernel, and although it's definitely alpha, it's awesome progress!
<rant>
It's pitiful that team of hobbyists and enthusiasts, working for free, in their spare time can port 2.2 faster than Samsung, who employs a full staff of software and hardware engineers, armed with development tools and source code. SAMSUNG, YOU SHOULD BE ASHAMED.
</rant>
Click to expand...
Click to collapse
From what I've read, it isn't a question of capability, i'ts just politics.
Thankfully we have wonderful developers to take the crap manufacturers throw at us and turn it into what really should be!

bdemartino said:
From what I've read, it isn't a question of capability, i'ts just politics.
Thankfully we have wonderful developers to take the crap manufacturers throw at us and turn it into what really should be!
Click to expand...
Click to collapse
Oh I agree 100%. They COULD have rolled out 2.2 months ago, if they wanted to.

Yoder808 said:
Oh I agree 100%. They COULD have rolled out 2.2 months ago, if they wanted to.
Click to expand...
Click to collapse
Samsung could have rolled out an firmware update but from what I've read they leave it up to the carriers to decide when they roll out updates.. especially OTAs since its on their end. US Cellular does spend a large amount of time testing their phones before releasing anything because their still small business orientated. That said, they easily could have rolled something out for us much earlier than this, as far as the small business goes they could have released it un-supported to commercial users and told business' not to load it yet plus not shipped any phones with it.. at least we'd have the option then..

I9000 Gingerbread is out

There is a new leak of gingerbread out for the SGS over in the I9000, and apparently this is supposed to be version that will be the official release.
http://forum.xda-developers.com/showthread.php?t=1009177

Nice, hopefully it doesn't take forever to see it officially released like it did with Froyo!

Waiting for source

I'm not too worried about AT&T, I believe once the source is released we will have many official releases XDA style

once the source is out we will have it. thank god for xda! and of coarse supercurio! i have been rocking out to music for the last couple days thanks to voodoo sound, not that the sound was bad before but now i can really appreciate it. also getting some better iem's (in ear monitors) the samsung ones are ok, well for an included accessory they are amazing but nothing compared to what is out there. i wouldnt think about getting a different phone right now. but i will see if the infuse has the hifi wolfson amp in it. the galaxy s 2 looks amazing but makes me wonder what will be out when i am up for a new contract.

Neat, hope the source appears sooner rather than later after the official release.

Lol... I must be losing it. And official sgs 2.3 leaks and this is the extent of the discussion. .... Lol wtf.

most people are more excited by cm7 for some reason. this is what i will use as soon as a reorient kernel comes about, all i can do is hope the source is realesed shortly. i think it was available pretty quick after jpx/jpy were released so i think it wont take long.

Nevermind

whiteguypl said:
Lol... I must be losing it. And official sgs 2.3 leaks and this is the extent of the discussion. .... Lol wtf.
Click to expand...
Click to collapse
Probably because this is like the 5th thread this weekend about this.

Miami_Son said:
Probably because this is like the 5th thread this weekend about this.
Click to expand...
Click to collapse
Regardless... It's a big deal. And none of the other threads made it very far. At all.
Go look at the i9000 forums. They're littered with posts and 2.3 sgs roms. All we have are crickets.

To be fair, we don't have the source available, so the leaked rom is kind of useless to us. It's a neat novelty, just to flash for a few minutes to see what's in store, but it's definitely not something you would use daily.

Just downloaded the Rom.. anyone know of a good kernel to use with this rom?? will CM7 kernel work with this rom? since its 2.3.3

TriC_101 said:
Just downloaded the Rom.. anyone know of a good kernel to use with this rom?? will CM7 kernel work with this rom? since its 2.3.3
Click to expand...
Click to collapse
Highly doubtful.. It should come with a compatible kernel and modem packaged in to it.
I wouldn't flash it straight through odin if I were you, though. If you have access to a linux machine, you should repackage it as a cwm flashable zip that doesn't flash boot or sbl, otherwise you risk either perma-bricking your phone or locking your bootloader.

My memory must be going. I remember us having ported i9000 2.2 roms well before the source dropped.

TriC_101 said:
Just downloaded the Rom.. anyone know of a good kernel to use with this rom?? will CM7 kernel work with this rom? since its 2.3.3
Click to expand...
Click to collapse
Stock kernel will boot, but there will be sound logic, screen orientation, button mapping...... problem list extends
Not until Sammy realeses the source code of GS gingerbread ROM that we can have reoriented kernels.

whiteguypl said:
My memory must be going. I remember us having ported i9000 2.2 roms well before the source dropped.
Click to expand...
Click to collapse
No... We didn't have reoriented kernel until JPM source was released. And before that, we were playing with the leak JI6 Captivate Froyo.

Guess it's time to start taking vitamins.

whiteguypl said:
My memory must be going. I remember us having ported i9000 2.2 roms well before the source dropped.
Click to expand...
Click to collapse
Vibrant owners have a port of this already, so yes it would seem that reorienting can be done without source, but devs aren't touching this for some reason...I really hope that changes cause I want to try this out but don't have the knowledge base to try to reorient the kernel myself and don't have time to learn currently.

No source, no kernel, no ROM. That simple.
Sent from my Xoom.

ics port like gsII has?

i know we have a rom that is ics themed, but i just came across engadget arcticle saying ics has already been ported for gsII..
http://www.engadget.com/2011/11/18/ice-cream-sandwich-ported-to-a-galaxy-s-ii-and-the-people-rej/
IF they can port so quickly to such a new device with probably more limitations than our device, shouldn't it be also possible to get a port going for our phones?

jazzmanmonty said:
i know we have a rom that is ics themed, but i just came across engadget arcticle saying ics has already been ported for gsII..
http://www.engadget.com/2011/11/18/ice-cream-sandwich-ported-to-a-galaxy-s-ii-and-the-people-rej/
IF they can port so quickly to such a new device with probably more limitations than our device, shouldn't it be also possible to get a port going for our phones?
Click to expand...
Click to collapse
Source code for the SGSII was released before the source code for the SGS4G. Gave them more time to port. Now that GB source has been released for SGS4G I am sure someone will try to port ICS...

Also the devs are in the process of porting cm7 firat before anything..not to mention how many actual devs sgs2 has compare to this..we have a few while that forum has over 10+
Sent from my SGH-T959V using XDA App

I promise you I am working on the ICS port. I had my wedding last week and honeymoon this week. I just returned today as soon as the source downloads and I have more time to complete this I will start the work on this. Currently contacting a few kernel devs for the Galaxy S I9000 to help with a kernel worthy of our 4g. I had the Nexus Prime dev dump booting to a slash screen then immediate reboot. Give it time it will come.

dynamicj said:
I promise you I am working on the ICS port. I had my wedding last week and honeymoon this week. I just returned today as soon as the source downloads and I have more time to complete this I will start the work on this. Currently contacting a few kernel devs for the Galaxy S I9000 to help with a kernel worthy of our 4g. I had the Nexus Prime dev dump booting to a slash screen then immediate reboot. Give it time it will come.
Click to expand...
Click to collapse
how did you do that..? just curious.... mainly because at the phone's current state, you can not flash a boot.img to it....

The SGS2 is native EXT4, and uses a boot.img and not a zImage, so it's easier for them to port this stuff.

krylon360 said:
The SGS2 is native EXT4, and uses a boot.img and not a zImage, so it's easier for them to port this stuff.
Click to expand...
Click to collapse
Didn't know so you are saying that they made a touchwiz boot.img and ext4 for them, or are they AOSP?
---------- Post added at 04:37 PM ---------- Previous post was at 04:36 PM ----------
krylon360 said:
The SGS2 is native EXT4, and uses a boot.img and not a zImage, so it's easier for them to port this stuff.
Click to expand...
Click to collapse
EXT4 shouldn't be the problem on this phone if I am correct since we already know how to convert from rfs to ext4. The problem is the boot.img,
so Krylon, how is our AOSP kernel going?

I did not boot to a homescreen it did however boot right past the gs4g screen and bootloop. Until the kernel is made it will not go further. I recommend speaking to the guys doing the I9000 port for the kernel mod they did. As I have been trying to get help porting if krylon is already on that I think we should just be working together on this.
Sent from my Icrap killer

It will all come with time. Give our wonderful developers the time they need, and donations never hurt either .

[wip][aosp][port][dev] 2.6.35.7 AOSP Kernel Port [05/14/2012]

This is a development thread. If you want a conversation thread, please open one in the general forum!
I've released the source a little early of completion, so I can get others on teamacid to help out. So until we get on the android-samsung-2.6.35-gingerbread branch and changes added, tested, pushed, and tested by a more general audience, I would NOT SUGGEST FLASHING THIS. Don't expect any wiz-bang features added or anything like that. This is a port. After the port is done, we can do all sorts of stuff.
Milestones to complete:
Scrub existing code that does not relate to Galaxy S 4G (SGH-T959V/VibrantPlus) from arch/arm/...
Move architecture specific code to mach-herring.c (as it should be) and make the changes diff cleanly with the aosp samsung android-samsung-2.6.35-gingerbread branch
Scrub and import needed drivers to new android-samsung-2.6.35-galaxys4g branch with herring conversion stuff imported.
Try to get rid of dvfs stuff and move to stock cpufreq (for easier future porting to Linus's mainline, which is the goal of this kernel, amongst other modifications that will open up...)
Get all components working (wifi/bt/gps/etc. It may not be possible to use bml/fsr/rfs/ext4, because of the symbol table changing, but lets try to see if we can get it working before making the kernel compatible with cm/aosp)
investigate BML<->MTD rom conversion kernel
I have currently completed Milestone 1. I am currently running stability tests with unnamed rc2. The binary should be the same as the minimal changes to stock source to make it boot and work with a standard bml rom, but without the other board code for dempsy, kepler, vibrant, vibrantplustelus, flemming, aries ntt, and others. All code is cleaned up and specific for VibrantPlus/SGH-T959V.
I've put together a new initramfs/recovery based on v5.0.2.8 to work on BML. This does not contain the voodoo lagfix support.
You WILL have to use an updater-script that forces conversion to ext4.
GitHub:
Kernel - https://github.com/bhundven/android_kernel_samsung_galaxys4g
Initramfs - https://github.com/bhundven/android_initramfs_samsung_galaxys4g
Stay tuned... I will update with progress.

post for uploads

OP updated. Using new initramfs (gingerbread branch), some kernel and build.sh fixes.

Just a note, I've made a little progress on m2.
Looking at possibly having something releasable here in the next week or two.
I've been out of work now since may 1st and its been hard to motivate myself on anything phone related.
Much thanks to the members of teamacid and teamkickass for keeping this stuff going!
Sent from my SAMSUNG-SGH-I717 using xda premium

So these are BML kernels converted to MTD?
Sent from my SGH-T959V using XDA

smontero said:
So these are BML kernels converted to MTD?
Sent from my SGH-T959V using XDA
Click to expand...
Click to collapse
You missed the point entirely.
EDIT
Look under "Milestones to complete"

I see but I don't completely understand. I just found out the difference between BML and MTD but I was asking cause I'm using the miui MTD and i wanted to know if these kernels would work
Sent from my SGH-T959V using XDA

He hasn't posted download links to them yet.

FBis251 said:
He hasn't posted download links to them yet.
Click to expand...
Click to collapse
Right. If you know how to compile the kernel, you could. If you did, you would currently have a BML kernel. (note there is also no mtd support in the current initramfs either)
I'm not sure if Milestone 2 will be able to support RFS. I may pull in the FSR code from supercurio's repository so that we can still have BML+ext4, but that code was for a froyo kernel.
If I can't get that to work, then this kernel will be MTD only. I'm still having some problems where my current Milestone2 changes (not checked in) is not booting correctly.
As I said, I'll have an update soon.

Porting Roms Confusion

Okay this question has been bugging me for a while now. Everyone is waiting on RC aka Ricardo AKA..... on getting the ported p990 to then be ported over to p999. We have many fine Developers here like Eagleblood , Rafase282, tonyp, Kashamalaga and many MIA ones that may or may not return like nycelitemaster, owain94, x0xhellx0x and my favorite Mr. Apocalypse.
My question is simple and would love one of these guys to answer it if possible.
Why are we waiting for RC to port it over when anyone of you guy have done it before. Am I wrong when saying that most of you have ported P990 over to P999 before? I respect everyone I have named. You have brought new life to my G2X. JUst wondering why we wait for RC, like he is the only one who can do this. Please if I am missing something let me know. thanks

I believe they are waiting for a more stable release of CM10 for the P990 before they bother to port it over for the P999. They should have many of the same bugs that need to be worked out. There is no need to do it twice.

I felt the same thing. Can some of the Developers list above or others I missed confirm this? Maybe this can stop or slow down the rants. The only reason I feel it may not be a difficult thing to do it because of this guys post...
Lezo OS
Hello everyone.
This is a port of the P990 Lezo OS a CM based rom. I am not a developer, just someone who was lucky enough to have this work It's just another piece of a so called "Crack Flashing Series". There are plenty of roms provided to our community, and this also brings people with different likes and dislikes. I aim only to share some of the other roms out there with the community. Maybe you want to try something out inbetween updates from your favorite rom, well, try this.
None of this would out be possible without the help of guides from dubntz and blindndumb. If you like any of the ports thank them as well.
This guy has done it before with other p990 Roms with little experience.

When we were on Cm7 we were able to port roms by using the already created cm7 base. The problem now is we don't even have a P999 cm10 base to port with, which is why we're waiting on RC since he needs to create the base.
Sent from my Nexus 7 using xda app-developers app

That seems to make sense. thanks. Can any Developers confirm this. Is RC truely the only one? Or is he just the only one with the spare time to help us? thanks

We need kernel and some of the drivers for our device which only ricardo has for jb. Like all of you, i am myself waiting for it. I might be moving on to nexus4 depending on money in hand. 16gb will run for almost $400 after tax.
Sent via G2X-SINGH-UI

nycelitemaster said:
We need kernel and some of the drivers for our device which only ricardo has for jb. Like all of you, i am myself waiting for it. I might be moving on to nexus4 depending on money in hand. 16gb will run for almost $400 after tax.
Sent via G2X-SINGH-UI
Click to expand...
Click to collapse
Don't we already have the drivers and Kernal? They are part of p990 and then don't they just need to port it over.

More then likely it would be easier to port tonyps experimental ics. We can compile a kernel for it and have the drivers. We just need the experience lol
Sent from my LG-P999 using Tapatalk

Here's what I think based off what I have read:
I think first and foremost, our Dev's who all own P990's are working in wrapping their wits around the sources for their phones, us and our G2x's are the red-headed step-children (figuratively) of LG. The phone has potential, but gets little attention. I also believe that the Devs are waiting for a kernel to be built with the new sources, which those sources have to be altered to work with the G2x, as they did for the O2x. Something which I don't think our Devs want to do. I may be wrong, but I would think that Bene, or Dj V. have the know-how to do it. Again, we're back to the fact that they're (understandably) going to do work for their phones first.
Sent from my LG-P999 using xda premium

As far as I know, the kernel sources for su660 has some issues compiling kernel for p999. It can be one of the reason why we don't have cm10 yet. I believe the developers are working on it. Also the kernel source comes with locked boot loader. So its essential to port old boot loader which is not locked to the new kernel. This might also be preventing other developers from building kernel. If I have time, I will try to see if I can compile the kernel with old boot loader or not this weekend. I am a full time science student. I think to port the p990 ROM we just need a p999 kernel and some p999 specific drivers such as ril drivers. I do hope the cm10 comes asap though. I might be wrong.

While I do not consider myself a developer, I thank you for listing me there. I personally do not have the time and knowledge required to build a cm10 base for the p999 based off the p990. The kernel and rom needs to be change to work for our phones. Also as it was said already, it would make no sense to make an early port, based on RC work which will most likely piss him off if we start kanging and using his work while it is not even stable enough to build for our phone. So I would say that out of respect and time/knowledge required most people able to make the port would either wait for help debugging the p990 version so it can be ported to other devices without the same issues to be fixed twice or more times.

In order to port you need a current rom with jb drivers for our phone. Porting will rip the kernel out of our rom and plug it into the ported rom. Thus why we can't port yet.
Sent from my LG-P999 using xda app-developers app

guitarist5122 said:
In order to port you need a current rom with jb drivers for our phone. Porting will rip the kernel out of our rom and plug it into the ported rom. Thus why we can't port yet.
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
A regular port from one rom to another with a CM base is mostly replacing a bunch of files with the ones you which to port while keeping the specific libs and files for your particular device, so besides the kernel, you need to make a compatible base if there is not one, then the proprietary blobs and editting files to fix issues. Porting can be very easy or very hard depending what you want to port.

who wants a kernel?
I've posted a kernel built from the cm10 lge-kernel-star repo in the dev thread, maybe somebody feels like taking it for a spin.

was wonder why the mixed results on the p990 CM 10 by RC then it hit me they have like 14 basebands. Things should be better for us we only have 2.

rosevilletoyota said:
was wonder why the mixed results on the p990 CM 10 by RC then it hit me they have like 14 basebands. Things should be better for us we only have 2.
Click to expand...
Click to collapse
In theory, I believe that a main issue for our guys did have to do with the absence of lge_star_ril being not present in the sources. That then caused the data, Gps, and battery issues.
Sent from my LG-P999 using xda premium

Rafase282 said:
A regular port from one rom to another with a CM base is mostly replacing a bunch of files with the ones you which to port while keeping the specific libs and files for your particular device, so besides the kernel, you need to make a compatible base if there is not one, then the proprietary blobs and editting files to fix issues. Porting can be very easy or very hard depending what you want to port.
Click to expand...
Click to collapse
Which is the problem for the G2x when it comes to Wifi Calling for example...the Kinecto .ko is a GB module at best. Same goes for the Tegra HDMI blob(whch I monkeyed around a very LONG time with);thankfully the P990 has the same HDMI blob. We will never have as good of a port as the P990 because at least the P990 has a ICS leak so kangers for P990 can use modules that work better in ICS leak in CM while all we have to build on is GB blobs and libs.
(PS:awesome avatar...ochem was a long time ago so I can't figure out the formula and nice use of -ase in your name!)

bakedpatato said:
Which is the problem for the G2x when it comes to Wifi Calling for example...the Kinecto .ko is a GB module at best. Same goes for the Tegra HDMI blob(whch I monkeyed around a very LONG time with);thankfully the P990 has the same HDMI blob. We will never have as good of a port as the P990 because at least the P990 has a ICS leak so kangers for P990 can use modules that work better in ICS leak in CM while all we have to build on is GB blobs and libs.
(PS:awesome avatar...ochem was a long time ago so I can't figure out the formula and nice use of -ase in your name!)
Click to expand...
Click to collapse
For my name the division is Rafa-sé It is just that in many places I cant use the é. SO I left it as an e and use use é for the phonetic part.
Morphine! :highfive:

Волк said:
In theory, I believe that a main issue for our guys did have to do with the absence of lge_star_ril being not present in the sources. That then caused the data, Gps, and battery issues.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Is the lge_star_ril something LG was supposed to have included? From my (limited) kernel knowledge, that bit seems pretty vital to having a properly working phone.
Without it, how hard is it going to be to get working calls/data/gps without having serious battery and quality issues as you've alluded to?

It was missing from the old sources, and yea, like I said alot of the deal-breaking issues were due to that, the ICS (which I think was already hacked) was hacked into JB.
Sent from my LG-P999 using xda premium