Database Users

[DEV][RC5] Team Nyx [Android 4.0.4] (ICSSGS)

Team Nyx
-- DemonWav -- Nushor -- Onecosmic -- PaulForde -- RaymondDull -- Trae32566 --​
This ROM is based directly on the source code straight from Google themselves, the way Android is meant to be. This ROM is produced by a collaboration of many different people, with the main development being done by Onecosmic himself. We strive to bring releases as often as possible and provide a stable AOSP ROM.
We are in the midst of many changes and will try to have our source code back up as soon as possible.
We do not support anything that is not produced by us!
Team ICSSGS is now Team Nyx!
We have made lots of changes, and part of that includes moving our base from XDA to our own website. All information, as well as downloads will be on our website, but please continue your discussions and we will continue our support here on the forums. Please check out our site at http://team-nyx.com/

loleverything works pretty much not a huge need for this here

The other thread needed replacing.

not that im complaining, but why did it need replacing? (in your eyes)

TRusselo said:
not that im complaining, but why did it need replacing? (in your eyes)
Click to expand...
Click to collapse
Lack of willingness from the OP to cooperate and to keep the thread updated.

TRusselo said:
not that im complaining, but why did it need replacing? (in your eyes)
Click to expand...
Click to collapse
b-eock wasn't involved with the project, we wanted a bit more control over how the OP was updated, and we didn't want someone not even contributing to make the real people behind this (mostly Onecosmic) look bad.

ytt3r said:
b-eock wasn't involved with the project, we wanted a bit more control over how the OP was updated, and we didn't want someone not even contributing to make the real people behind this (mostly Onecosmic) look bad.
Click to expand...
Click to collapse
So.... since your in charge of the kernels... any chance of a 1600Mhz over clock? Just wishful thinking..

goob1284 said:
So.... since your in charge of the kernels... any chance of a 1600Mhz over clock? Just wishful thinking..
Click to expand...
Click to collapse
The kernel wasn't changed, actually. And there is a chance, but we're focusing on the big issues now, we'll put more features in later.

is this build going to be pure ASOP first? the other thread was talking of changing the "crappy" battery icon and other stuff.
ASOP fist. right?

goob1284 said:
So.... since your in charge of the kernels... any chance of a 1600Mhz over clock? Just wishful thinking..
Click to expand...
Click to collapse
I just hope it doesn't end up like Talonmtd lol.
Herp derp Captivate XDA Premium.

TRusselo said:
is this build going to be pure ASOP first? the other thread was talking of changing the "crappy" battery icon and other stuff.
ASOP fist. right?
Click to expand...
Click to collapse
That's another thing, that other thread was complete bullcrap. We are focusing 100% on AOSP at the moment. I'm working on side flashes to try to improve the rom, but they are not a part of the rom or have anything to do with Onecosmic.

I don't know why you said it won't boot. I'm on a7 with captivate kernel you posted in google code. Can't get 3g working yet but it boots just fine

If I want to flash from apex 11 w/ dark kernel, what's the process I should go through?

jmbradd said:
I don't know why you said it won't boot. I'm on a7 with captivate kernel you posted in google code. Can't get 3g working yet but it boots just fine
Click to expand...
Click to collapse
I did the same, except none of my buttons are working? i might reflash and see what happens. Also it seems to lag more the A6. Im gonna try a reflash and see if everything gets straightend out

autocorrelation said:
If I want to flash from apex 11, what's the process I should go through?
Click to expand...
Click to collapse
Download the required files (ROM, Kernel, and SU fix), and make sure you have a GB Bootloader.
1. Backup your files, and do a Nandroid
2. Reboot to Recovery
3. Wipe Data, Cache, and Dalvik. No need to wipe system because it's done already on the updater script.
4. Install .zip from SD card. First of all flash the ROM, then go for the Kernel.
5. Reboot, the first boot takes longer.
6. Setup your account.
7. Boot to recovery, and install the SU.zip to grant you with Root access.
8. Reboot, and enjoy.
Notice I do not ask you to wipe and flash several times, it honestly works at the first attempt.
Good Luck.

dumb question is this still a port for the captivate ? and will flashing this mean you need specific boot loaders to start I run i9000 boot loaders and sorry for posting question here but never got an answer in the q&a will ICS support HSDPA like JVT did?

Just wanted to thanks guys. This is awesome.

@OP
Is it the same thing to go to: http://code.google.com/p/ice-cream-sandwich-sgs/downloads/list, download the A7 ROM "ICS_4.0.1_r1-alpha7.zip", and flash the Captivate Kernel? Or are you uploading a different version, with more changes?
I am asking because I honestly feel like this A7 update is a tad slower than the A6 i downloaded previously. (The A6 zip i was linked to already merged both the Kernel, and the ROM into one same updater script.)
---------- Post added at 10:07 AM ---------- Previous post was at 10:06 AM ----------
white00gt said:
dumb question is this still a port for the captivate ? or is phone listed in title different and will flashing this mean you need specific boot loaders to start I run i9000 boot loaders and sorry for posting question here but never got an answer in the q&a will ICS support HSDPA like JVT did?
Click to expand...
Click to collapse
Yes, It is working for the Captivate. So far, all you have to do is download the I900 ROM, and then flash the Captivate kernel.
Links: http://code.google.com/p/ice-cream-sandwich-sgs/downloads/list

everest.deth said:
@OP
Is it the same thing to go to: http://code.google.com/p/ice-cream-sandwich-sgs/downloads/list, download the A7 ROM "ICS_4.0.1_r1-alpha7.zip", and flash the Captivate Kernel? Or are you uploading a different version, with more changes?
I am asking because I honestly feel like this A7 update is a tad slower than the A6 i downloaded previously. (The A6 zip i was linked to already merged both the Kernel, and the ROM into one same updater script.)
---------- Post added at 10:07 AM ---------- Previous post was at 10:06 AM ----------
Yes, It is working for the Captivate. So far, all you have to do is download the I900 ROM, and then flash the Captivate kernel.
Links: http://code.google.com/p/ice-cream-sandwich-sgs/downloads/list
Click to expand...
Click to collapse
It is the same, I am just packaging it up to simplify it for the noobs. I just uploaded a .zip, then I realized that I had screwed up with it, so I'm re-uploading now.
EDIT: As for it being slower, Alpha 7 has some wicked partitioning changes that should speed it up. Of course we are always trying to make it better, but HW Accel. is built into Alpha 7.

everest.deth said:
@OP
Is it the same thing to go to: http://code.google.com/p/ice-cream-sandwich-sgs/downloads/list, download the A7 ROM "ICS_4.0.1_r1-alpha7.zip", and flash the Captivate Kernel? Or are you uploading a different version, with more changes?
I am asking because I honestly feel like this A7 update is a tad slower than the A6 i downloaded previously. (The A6 zip i was linked to already merged both the Kernel, and the ROM into one same updater script.)
---------- Post added at 10:07 AM ---------- Previous post was at 10:06 AM ----------
Yes, It is working for the Captivate. So far, all you have to do is download the I900 ROM, and then flash the Captivate kernel.
Links: http://code.google.com/p/ice-cream-sandwich-sgs/downloads/list
Click to expand...
Click to collapse
thanks might wait a little while before flashing but it is very tempting

[i9001]Discussions about development of CM7 and CM9

Hi to all!
I've created this topic that we can discuss about the CM7 and CM9 ROMs that are in development, and not flood the development topic with Q&As. Feel free to post!

How to avoid bricking the SGS+
I've heard that this phone is somewhat easy to brick. This made me think twice before doing some 'serious stuff' with the phone, like trying to make a CM7 or ICS ROM. Can somebody tell me how to avoid bricking this phone? And is it risky to flash source-built ROMs? It would be good if someone tell me the partitions of the phone (in which is stored what: e.g. in which partition is the kernel, the bootloader, etc.).
Thanks in advance!

You can get the most important partitions from the wiki: http://forum.xda-developers.com/wiki/Samsung_Galaxy_S/GT-I9001#Partitions
I once dumped all partitions and can verify that the most important stuff is below the kernel partition, so don't mess with them. mmcblk0p14 is a parameter partition (thx skywalker01) for the bootloader, that is what causes some devices (including mine) not to work 100% correct with CWM. You can only get out of recovery boot loop by dd'ing zeros to that partition.

despotovski01 said:
I've heard that this phone is somewhat easy to brick. This made me think twice before doing some 'serious stuff' with the phone, like trying to make a CM7 or ICS ROM. Can somebody tell me how to avoid bricking this phone? And is it risky to flash source-built ROMs? It would be good if someone tell me the partitions of the phone (in which is stored what: e.g. in which partition is the kernel, the bootloader, etc.).
Thanks in advance!
Click to expand...
Click to collapse
looking back at this post u gave very high expectations . Anyways, building a rom from source isn't hard at all, the tough part is to make the hardware work, so most probably u'll end up with a non working touchscreen for a start, not to mention u need a kernel that'll make it boot at all. As for the partitions, skywalker is the man to ask, i can tell u though that the kernel (boot.img) is in /dev/block/mmcblk0p8 .

rayiskon said:
looking back at this post u gave very high expectations . Anyways, building a rom from source isn't hard at all, the tough part is to make the hardware work, so most probably u'll end up with a non working touchscreen for a start, not to mention u need a kernel that'll make it boot at all. As for the partitions, skywalker is the man to ask, i can tell u though that the kernel (boot.img) is in /dev/block/mmcblk0p8 .
Click to expand...
Click to collapse
Thanks. I was looking for the bootloader partition, because if you mess it up, your phone wouldn't boot at all. If you mess up the kernel partition, your phone won't be able to boot into the OS, but it will be able to boot in CWM and Download mode. I'm asking this here because I heard that this phone has weird partitions, so I want to be sure I'm not going to brick my phone doing these stuff.

Hello all
Today i've made small performance comparation of CM7 KANG and Teamhacksung's ICS b14.
Please note that this KANG is used by me for everyday use with over 60 apps installed, without any scripts etc. (only Chainfire 3D @ nVidia) and ICS is freshly installed. All tests made on airplane mode.
Standard 1000MHz, ondemand, no UV/OV.
I plan to made comparation with latest Samsung ROM.

despotovski01 said:
Thanks. I was looking for the bootloader partition, because if you mess it up, your phone wouldn't boot at all. If you mess up the kernel partition, your phone won't be able to boot into the OS, but it will be able to boot in CWM and Download mode. I'm asking this here because I heard that this phone has weird partitions, so I want to be sure I'm not going to brick my phone doing these stuff.
Click to expand...
Click to collapse
as wintel already said and as it's mentioned in the wiki (WARNING: Partitions below 8 contain absolutely vital stuff like the primary boot loader responsible for low-level hardware initialization. Messing with them is what leads to fully bricked phones because you will not be able to get into download mode anymore! ) . but for any detailed info, contact skywalker

rayiskon said:
as wintel already said and as it's mentioned in the wiki (WARNING: Partitions below 8 contain absolutely vital stuff like the primary boot loader responsible for low-level hardware initialization. Messing with them is what leads to fully bricked phones because you will not be able to get into download mode anymore! ) . but for any detailed info, contact skywalker
Click to expand...
Click to collapse
Thanks, I've sent him a PM.

GIBbeerSKY said:
Hello all
Today i've made small performance comparation of CM7 KANG and Teamhacksung's ICS b14.
Please note that this KANG is used by me for everyday use with over 60 apps installed, without any scripts etc. (only Chainfire 3D @ nVidia) and ICS is freshly installed. All tests made on airplane mode.
Standard 1000MHz, ondemand, no UV/OV.
I plan to made comparation with latest Samsung ROM.
Click to expand...
Click to collapse
Are you talking about SGS i9000 or SGS+ i9001?

I'm sorry, I've missed the "1" at end of model.

well is there any hopes that the CM7 or CM9 will be issued soon for the i9001?
one more thing, should I buy the i9001 or the i9000 is better??

YMYA said:
well is there any hopes that the CM7 or CM9 will be issued soon for the i9001?
one more thing, should I buy the i9001 or the i9000 is better??
Click to expand...
Click to collapse
i think u already made ur choice. here and here

rayiskon said:
i think u already made ur choice. here and here
Click to expand...
Click to collapse
tht wasn't mine..
so what do you suggest?

YMYA said:
tht wasn't mine..
so what do you suggest?
Click to expand...
Click to collapse
neither. S2 or galaxy nexus

rayiskon said:
neither. S2 or galaxy nexus
Click to expand...
Click to collapse
what if i have to choose one of them..which one is better?

YMYA said:
what if i have to choose one of them..which one is better?
Click to expand...
Click to collapse
http://www.gsmarena.com/compare.php3?idPhone1=3115&idPhone2=3908
S+ has a stronger CPU , GPU comes about the same when u update gpu drives,other stuff are more or less similar. so S+ is a lil stronger, but if u care for community support (ICS etc..) u will go for I9000.

rayiskon said:
http://www.gsmarena.com/compare.php3?idPhone1=3115&idPhone2=3908
S+ has a stronger CPU , GPU comes about the same when u update gpu drives,other stuff are more or less similar. so S+ is a lil stronger, but if u care for community support (ICS etc..) u will go for I9000.
Click to expand...
Click to collapse
I am aware about all of this..i mean whats ur personal opinion..if u have to buy one of them which one will YOU get?

YMYA said:
I am aware about all of this..i mean whats ur personal opinion..if u have to buy one of them which one will YOU get?
Click to expand...
Click to collapse
although the lack of community support is a very big minus, but i'd still get the S+ , coz it's better. the only thing i miss is to try an ICS build, but i'm sure it will be here sooner or later.

DroidXDA
SGS+ News :: We almost to booting stage with now fixing the kernel (we hope it will work out) :: do support us by clicking our advert at our blog thanks Have A nice Days
Click to expand...
Click to collapse
Just to let you know...So hopefully they will get it working

What Build is current cm9 ?
One Question, What is the Build Number of our cm9 ? because i want to patch LunarUi Theme ,but it has many zips for many builds of cm9 , thanks

LG uploaded V500 kitkat kernel source today!

https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=lgv500
Is where you can get it (start your downloading now...)
the strange thing is they appear to have two uploads for kitkat...
Sent from my LG-V500 using XDA Premium HD app

Yay! What does it mean for the simple user? Better roms?
Sent from my iPhone using Tapatalk

All I really want is gamma correction and maybe overclocking and U/V.

This means that anyone interested in building a replacement kernel for the LG stock 4.4.2 release has a blueprint to start from. I know of two kernels that have been released for 4.2.2 stock, this release means that we may see updates of these projects to 4.4.2.
I may try and restart my own efforts in this area as well depending upon time and what kind of problems I find in the 4.4.2 US release.
M

muiriddin said:
This means that anyone interested in building a replacement kernel for the LG stock 4.4.2 release has a blueprint to start from. I know of two kernels that have been released for 4.2.2 stock, this release means that we may see updates of these projects to 4.4.2.
I may try and restart my own efforts in this area as well depending upon time and what kind of problems I find in the 4.4.2 US release.
M
Click to expand...
Click to collapse
The first and most obvious is the gamma set at 2.05 roughly. If you set it to 2.2 - 2.3, that would already be a big plus.

The source uploaded by LG didn't include the kernel source so I contacted their open source division and they've now uploaded a proper kernel source. I'm travelling for work now, but will take a look at it when I get back home next week and get something compiled.
G Pad(V500)_Android_KitKat_LGV500_v20b_Kernel
https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=v500
Sent from my LG-V500 using Tapatalk

id10terror said:
The source uploaded by LG didn't include the kernel source so I contacted their open source division and they've now uploaded a proper kernel source. I'm travelling for work now, but will take a look at it when I get back home next week and get something compiled.
G Pad(V500)_Android_KitKat_LGV500_v20b_Kernel
https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=v500
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
Good to hear that someone else contacted them as well. I have been impressed with their open source group responding as quickly as they did. They definitely respond better than several other companies when facing these requests!

:good::good: I would pay anybody to incorporate or activate the OTG+Charging in this Kernel. :good::good: :fingers-crossed:

id10terror said:
The source uploaded by LG didn't include the kernel source so I contacted their open source division and they've now uploaded a proper kernel source. I'm travelling for work now, but will take a look at it when I get back home next week and get something compiled.
G Pad(V500)_Android_KitKat_LGV500_v20b_Kernel
https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=v500
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
When if get the chance can you compare the 18a kernel to the 20b one? I like the settings the 18a kernel, the lower brightness levels are setup in a way that makes it great for night time. I have the 18a kernel running on the 20b build but after the screen is locked it and turned back on it changes to levels of the 20b kernel, but retains the gamma level. I could attach a flashable zip with the 18a kernel if you need it.

LBJM said:
When if get the chance can you compare the 18a kernel to the 20b one? I like the settings the 18a kernel, the lower brightness levels are setup in a way that makes it great for night time. I have the 18a kernel running on the 20b build but after the screen is locked it and turned back on it changes to levels of the 20b kernel, but retains the gamma level. I could attach a flashable zip with the 18a kernel if you need it.
Click to expand...
Click to collapse
Hi, I am quite a newbie. Just wondering what is the use of the kernels? Can we just flash it on custom roms like the kitkats ones done by _infected. AOKP or the Cynogenmod for the GPAD? The AOKP and the Cynogen are smooth but few features like Autorotate doesn't work and there is no gamma correction i think

I compiled a kernel using the source provided by LG, but for some reason, it doesn't boot.
I keep getting this error:
Code:
Secure booting error
Cause: boot certification verify
I noticed that the resulting "boot.emmc.win" is a lot smaller than the original boot.emmc.win (~10 MB compared to 24MB)
Another interesting thing is that if I uncompress the original 24 MB boot.emmc.win using the command "unmkbootimg -i boot.emmc.win", I get two files: kernel (7.5 MB) and ramdisk.cpio.gz (2.6 MB). If I rebuild the boot.emmc.win using these exact two files, I get an 11MB boot.emmc.win, but this one DOES boot.
It probably has something to do with the locked bootloader and the loki exploit.
Can anyone help me get to the bottom of this? I really want to solve the gamma issue.

Well, as I suspected, it was because of the locked bootloader, but using the loki_tool, I was able to bypass the bootloader check.
So I now have a working, self-compiled 4.4.2 kernel (using the eabi-4.7) , based on LG's kernel source.
Unfortunatelly, gamma is still the same (about 2 - 2.1). Need to figure out how to modify it.
If someone can and wants to help, I'd greatly appreciate it.

Can you look at the 18 Rom kernel and see what has changed?
Sent from my SM-N900W8 using Tapatalk

ruxandy said:
Well, as I suspected, it was because of the locked bootloader, but using the loki_tool, I was able to bypass the bootloader check.
So I now have a working, self-compiled 4.4.2 kernel (using the eabi-4.7) , based on LG's kernel source.
Unfortunatelly, gamma is still the same (about 2 - 2.1). Need to figure out how to modify it.
If someone can and wants to help, I'd greatly appreciate it.
Click to expand...
Click to collapse
Canadoc said:
Can you look at the 18 Rom kernel and see what has changed?
Sent from my SM-N900W8 using Tapatalk
Click to expand...
Click to collapse
Panel is very close to correct gamma when using default linear qlut, instead of MSM_MIPI_LGIT_VIDEO_WUXGA_PT_PANEL qlut.

I would definitely take a look at the 50018A kernel if someone can provide the source. I wasn't able to find it.

gin_silver said:
Hi, I am quite a newbie. Just wondering what is the use of the kernels? Can we just flash it on custom roms like the kitkats ones done by _infected. AOKP or the Cynogenmod for the GPAD? The AOKP and the Cynogen are smooth but few features like Autorotate doesn't work and there is no gamma correction i think
Click to expand...
Click to collapse
The kernel is what drives the Rom. Without the kernel sources improvements to a device are hard to make. It's AOSP ( Android Open Source Project) not AOKP.

LBJM said:
The kernel is what drives the Rom. Without the kernel sources improvements to a device are hard to make. It's AOSP ( Android Open Source Project) not AOKP.
Click to expand...
Click to collapse
Thanks. Hopefully we will have some great modified kernels for the kitkat version
Btw i was referring to AOKP (K for Kang) in this thread http://forum.xda-developers.com/showthread.php?t=2710996

gin_silver said:
Thanks. Hopefully we will have some great modified kernels for the kitkat version
Btw i was referring to AOKP (K for Kang) in this thread http://forum.xda-developers.com/showthread.php?t=2710996
Click to expand...
Click to collapse
Good to know.

20d source released
I do not know if anyone will find this of use, but they have now posted the 20d kernel source (and some other stuff).
https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=v500

ruxandy said:
Well, as I suspected, it was because of the locked bootloader, but using the loki_tool, I was able to bypass the bootloader check.
So I now have a working, self-compiled 4.4.2 kernel (using the eabi-4.7) , based on LG's kernel source.
Unfortunatelly, gamma is still the same (about 2 - 2.1). Need to figure out how to modify it.
If someone can and wants to help, I'd greatly appreciate it.
Click to expand...
Click to collapse
Hello ruxandy,
Can you explain in few words how did you manage to push the kernel to your v500?
Here is my story:
I downloaded the V500 Lollipop kernel because I wanted to compile .ko loadable modules and drivers to support RTL2832U DVB USB dongle. I successfully compiled those modules, rooted the tabled and tried to insmod them. But it failed because the modules did not find some kernel APIs.
Then I decided to build the kernel with built-in those drivers and I did it successfully, the problem now is what to do with zImage. I read there are two roads the one building own KDZ file seems very complicated and not sure if really possible. The other seems to be to extract the boot.emmc.win file using TWRP. So I downgraded the V500 bootloader from LT to KK and installed TWRT using this http://forum.xda-developers.com/lg-g-pad-83/help/v500-how-to-install-twrp-stock-lp-t3165846 but after reboot got the secure boot error you did.
So again - how to use self built zImage and is this possible for KitKat only, since installing TWRP with Lollipop does not seem possible so far?

Multirom

Is g3 multirom impossible that it work with our g2?

We already have multirom ported by @patrik.KT but we didn't break the code of how to boot stock roms with other roms. Just aosp/aosp. I'm hoping Patrik will look into what the g3 dev did and port it to us.

vPro97 said:
We already have multirom ported by @patrik.KT but we didn't break the code of how to boot stock roms with other roms. Just aosp/aosp. I'm hoping Patrik will look into what the g3 dev did and port it to us.
Click to expand...
Click to collapse
Well I hope that too but I don't know or he still follows G2. This is what the OP did in the time so we could use it also on ours by cherrypicking the commits if it's possible else we have to do it manually and give credits ofcourse.
https://github.com/Skin1980?tab=activity
Also vPro97 I didn't really did much about the dualboot patch thing yet since I am still busy with school but I promise that I will try to look tomorrow into it and I will also try that Multirom thing from Skin1980 with his patches that he gathered to get it working. Ofcourse based on the G2 sourcecode:silly: This will also function easier then the dualboot patcher we just have to wait until LG unlocks the bootloader or when someone/a team could hack the bootloader.

wulsic said:
Well I hope that too but I don't know or he still follows G2. This is what the OP did in the time so we could use it also on ours by cherrypicking the commits if it's possible else we have to do it manually and give credits ofcourse.
https://github.com/Skin1980?tab=activity
Also vPro97 I didn't really did much about the dualboot patch thing yet since I am still busy with school but I promise that I will try to look tomorrow into it and I will also try that Multirom thing from Skin1980 with his patches that he gathered to get it working. Ofcourse based on the G2 sourcecode:silly: This will also function easier then the dualboot patcher we just have to wait until LG unlocks the bootloader or when someone/a team could hack the bootloader.
Click to expand...
Click to collapse
Hmm you're right. But the G3 bootloader is locked as well and apparently multirom is working flawlessly.
Either way thanks for your efforts, if I can be if any help let me know.

Neptune Pine - Custom Rom Infomation and Testing

I'm looking at the Neptune pine to see what I can do with it.
so far I have obtained the kernel config
Configkernel3.4
This Thread is for sharing information and Q/A
My goal is to have a custom android rom compiled and then to try port different O/S's to it.

Nice! What's the status of your efforts?

How to the testing .....

JustSueMe said:
I'm looking at the Neptune pine to see what I can do with it.
so far I have obtained the kernel config
Configkernel3.4
This Thread is for sharing information and Q/A
My goal is to have a custom android rom compiled and then to try port different O/S's to it.
Click to expand...
Click to collapse
What about using the kernel source from cyanogenmod, like the dev did who released beta cyanogenmod?

F0L said:
What about using the kernel source from cyanogenmod, like the dev did who released beta cyanogenmod?
Click to expand...
Click to collapse
Ok, should have read it better. Are you able to just compile a kernel for testing. Once you have a working one, that would be a good base for updating rom.

JustSueMe said:
I'm looking at the Neptune pine to see what I can do with it.
so far I have obtained the kernel config
Configkernel3.4
This Thread is for sharing information and Q/A
My goal is to have a custom android rom compiled and then to try port different O/S's to it.
Click to expand...
Click to collapse
Any update on this?

Guess this is not going to happen. Just wish I still had the time I used to. I would have had a go my self, as the vanilla kernel is what kills this cool bit of kit.
I managed to get it to a usable state with google play installed, by installing SkyNET. Which tweaks the system on the fly when needed. Helps keep as much memory as possible.

Would the kernel source of the Nokia X help? as it uses the exact same hardware.
I have it downloaded, so if it will help, I can link.

I have given up on anyone doing anything with pine. So I tweaked stock rom as much as I could, got it running very nicely even with my 130GB storage (link2sd). I also modified the ramdisk image to support init.d on boot. Im also using kickarse kernel script.

F0L said:
I have given up on anyone doing anything with pine. So I tweaked stock rom as much as I could, got it running very nicely even with my 130GB storage (link2sd). I also modified the ramdisk image to support init.d on boot. Im also using kickarse kernel script.
Click to expand...
Click to collapse
Can you post how you did it? Thanks

@fol I would also be interested in it.

killervette said:
Can you post how you did it? Thanks
Click to expand...
Click to collapse
I used rom kichen to mess with ramdisk (it was very risky as messing with boot image can brick pine). I manually added init.d support. Then repacked it. Luckly it worked fine. I even flashed it to my sons.
I extracted stock system.zip and tweaked it the way I wanted (debloated added apps I owned), then flashed that. As I added init.d, I could use scripts on boot to alter running of pine.
Im currently using Project skynet vr4, which runs very nice.

@fol What is skynet? Do you have a link?