Database Users

CyanogenMod 7.0 for eLocity ?

Check this out !
Anyone in relation with those guys ? How could we get out tablet to support it ?
Pretty amazing !
Link here : http://www.engadget.com/2011/04/11/cyanogenmod-7-0-is-now-final-ready-for-your-consumption/
I know Dexter is the eLocity king atm, but it must be tirering to be a one man army !

Again and again and again...
Without kernel source we unable to do custom ROMs. Only modifications over stock.
Not a development topic...

5[Strogino] said:
Again and again and again...
Without kernel source we unable to do custom ROMs. Only modifications over stock.
Not a development topic...
Click to expand...
Click to collapse
maybe I should put my old signature back on? lol

the Synergy Bluetooth implementation is nowhere close to standard implementation, so although we might get a CM6/7 on this tablet, even without 2.6.36.3 kernel maybe, we still need more coding done to support the BT implemention otherwise the port will be without Bluetooth support..
I got, as example, the FolioMod ported easily, but Bluetooth did not work, same with the Blur port.. and since our kernel has no real loopdevice or devicemapper support and modules needs to be specifically compiled with the revisions used in our kernel, the "move2sd" function is also missing here, and other nice function as optimized filesystems using loopdevice for faster database updates etc..
it will be hard! , and the drivers without any source, makes its practically impossible to do a kernel based on nvidia's git tree alone..

Moved to proper forum

Kernel available??
Mr. Clown said:
Moved to proper forum
Click to expand...
Click to collapse
See on http://www.elocitynow.com/downloads/open-source.tar
and chacksum http://www.elocitynow.com/downloads/.checksum.md5

ming_a said:
See on http://www.elocitynow.com/downloads/open-source.tar
and chacksum http://www.elocitynow.com/downloads/.checksum.md5
Click to expand...
Click to collapse
Yep. Did you find it here:
http://www.elocitynow.com/developers.shtml
Billy

[NEWS] My new kernel can run in stock 3.1 ROM finally

Hi all,
I am so excited now, can't wait to tell all you guys that news
Maybe someone know that I have upgraded our kernel to the newest kernel tree from nvidia's git and waiting for it to be stable for daily use. However, I found it can't boot in the newest ACER's stock ROM yesterday. After one full day hack, it finally can boot in the stock ROM now.
However, the last function I can't confirm is HDMI support, so I want some volunteers to test HDMI support and the stability. If you use vache's Taboonay 0.9.x and are interested in it, please PM me
Thanks

I can test the stability, but not the HDMI output.
P.S : Nice to see you here roggin

I can test hdmi, only 720p, but at least I can verify that.

roggin said:
Hi all,
I am so excited now, can't wait to tell all you guys that news
Maybe someone know that I have upgraded our kernel to the newest kernel tree from nvidia's git and waiting for it to be stable for daily use. However, I found it can't boot in the newest ACER's stock ROM yesterday. After one full day hack, it finally can boot in the stock ROM now.
However, the last function I can't confirm is HDMI support, so I want some volunteers to test HDMI support and the stability. If you use vache's Taboonay 0.9.x and are interested in it, please PM me
Thanks
Click to expand...
Click to collapse
What kernel is it? If I may ask.
Can it OC?

Johnny0906 said:
What kernel is it? If I may ask.
Can it OC?
Click to expand...
Click to collapse
Nvidia's kernel is the ORIGINAL kernel, all others base their continued work on, so Acer use these updates as reference..

Can you check up on the bluetooth issue on this kernel you make..
I know tiamat/xoom kernel is really close to stock nvidia kernel too (or fully supported with drivers). so maybe something dirty needs changing..
havent had chance to fix..
problem for now, seems to be it can scan, but seems to timeout on transmitting, so it suddenly cannot see new units after some minutes. maybe worth doublechecking.

vache said:
I can test the stability, but not the HDMI output.
P.S : Nice to see you here roggin
Click to expand...
Click to collapse
Hi vache,
Coooool, it's so nice to see you here
I have pm you the link, please take it a try
Thanks for your help again

Johnny0906 said:
What kernel is it? If I may ask.
Can it OC?
Click to expand...
Click to collapse
sorry, I haven't added OC code in it, but I will add it when it stable enough
Thanks

Dexter_nlb said:
Can you check up on the bluetooth issue on this kernel you make..
I know tiamat/xoom kernel is really close to stock nvidia kernel too (or fully supported with drivers). so maybe something dirty needs changing..
havent had chance to fix..
problem for now, seems to be it can scan, but seems to timeout on transmitting, so it suddenly cannot see new units after some minutes. maybe worth doublechecking.
Click to expand...
Click to collapse
Hi Dexter_nlb:
I have tested the bluetooth function in this kernel, it works fine in my kernel
If you are interested in it, I can mail or share a link of my kernel source for you
Thanks

roggin said:
However, the last function I can't confirm is HDMI support, so I want some volunteers to test HDMI support and the stability. If you use vache's Taboonay 0.9.x and are interested in it, please PM me
Click to expand...
Click to collapse
Hi Roggin,
I play with versions and can test HDMI 1080P with Taboonay 0.9.1. Please send me the link to kernel. Do you make also modules, especialy for 3G?

roggin said:
Hi Dexter_nlb:
I have tested the bluetooth function in this kernel, it works fine in my kernel
If you are interested in it, I can mail or share a link of my kernel source for you
Thanks
Click to expand...
Click to collapse
please do i would love to play around with it "internally" and testing...
im little occupied atm, so hdmi can be tested, and regular use for now..
I can probably make you the oc add-ons and see how it turns out with your work and send you my diff back.. (don't know git commit)

I would be willing to due some stability testing with the acer stock rom.
Let me know.

Dexter_nlb said:
please do i would love to play around with it "internally" and testing...
im little occupied atm, so hdmi can be tested, and regular use for now..
I can probably make you the oc add-ons and see how it turns out with your work and send you my diff back.. (don't know git commit)
Click to expand...
Click to collapse
Hi Dexter_nlb,
It's a big big help that you can help me ,
I am not releasing kernel source is because I don't want to brick someone's tablet, but It's ok for power developer like you.
I am uploading the kernel, I will info you when uploading done
Thanks for your help

snickle said:
I would be willing to due some stability testing with the acer stock rom.
Let me know.
Click to expand...
Click to collapse
Hi snickle,
I think it's fine using Taboonay's ramdisk in stock rom, but not sure
If you can help me for test, I will pm the link for you
Thanks

roggin said:
I am not releasing kernel source is because I don't want to brick someone's tablet
Click to expand...
Click to collapse
If they know how to compile it, then I guess they can enjoy their brick
Just be careful not releasing the source code, as it is under a open licence. I'm pretty sure that's why thor2002ro's kernel thread was deleted by moderators off fo this forum. I don't want to see another Kernel development go south because it wasn't public .

roggin said:
Hi snickle,
I think it's fine using Taboonay's ramdisk in stock rom, but not sure
If you can help me for test, I will pm the link for you
Thanks
Click to expand...
Click to collapse
I think the usage of ramdisk should be optional, because it might not allow to encrypt your device, and as you hopefully know, encryption is necessary to allow exchange activesync connection for email push, except if somebody finds out a what has to be modified to use activesync without encryption.
I also join ShadowXVII concerning the kernel source, if somebody wants to brick his device, it's up to him, but be carefull not to get removed because you did not publish the source.
otherwise well done my friend.

zoubidou said:
I also join ShadowXVII concerning the kernel source, if somebody wants to brick his device, it's up to him, but be carefull not to get removed because you did not publish the source.
Click to expand...
Click to collapse
You only have to publicly release the source if you publicly release the binary - he's only obliged to give the source to the people he gave the binary to. So there's no problems
On that note: I've just flashed Taboonay and am happy to give your kernel a try. I don't have a dev environment set up these days, but if you can send me the boot.img I'll take a crack at it.

themono said:
You only have to publicly release the source if you publicly release the binary - he's only obliged to give the source to the people he gave the binary to. So there's no problems
Click to expand...
Click to collapse
Cool, thanks for the clarification. Just being cautious as I'd prefer Kernel development wasn't hindered at all. That being said, a public source may promote development as opposed to ending up with several different kernels by different developers. I'm all for collaboration, and it's great to see some within this thread
On a side note, any Kernel developers that may be able to shed some light onto this thread would be appreciated -- in particular, the kernel requirements for networking over USB; http://forum.xda-developers.com/showthread.php?p=15452414#post15452414

Hi all,
It's not I don't want to release it. It's almost 300+ patches between older and newer version, and include some regulator voltage patch. I want to sure not damage any part in all functions.
Give me one more days, when I collect all necessary response from tester, I will release it
Thanks

I did exactly the same on the tiamat kernel, waited and hoped to had time debugging the bluetooth issue, but got modarator complaints on not publicing any source
anyways, as long as no binary appear in this thread, i think you're safe from any mods attacking you on GPL issues (or do like thor200ro move it offsite, if you feel like breaking GPL)
Talk is just talk for now, no mods can argue against that for now..

DREAMteam Froyo source code

Hi there,
I'm trying to build some froyo rom for g1 from source. The problem is that lot of stuff lying here is old, unusable slow or hopelessly broken. The only rom that seems to work is hxxp://forum.xda-developers.com/showthread.php?t=1273549
[Rom][2.2.3 AOSP] DREAMteam Froyo v2.0.0 [9/3/2012]
The kernel source can be easy found by Ezterry
hxxps://github.com/ezterry/kernel-biff-testing/tree/ezgb-2636-v1.5.2-20111106
but I can't find any (git) repo or hint how the "DREAMteam" guys built it. :crying:
Thanks in advance for any hints,
ptau

pm the devs
Sent from my HTC Vision using xda premium

All you need for building the kernel is here at this url:
https://github.com/ezterry/manifest-gingerbread-DS/blob/gingerbread/README.mkdn
It used to be on the ezgingerbread rom thread but seems he has a link to the guide which is now on github ^_^
Sent from my GT-I9300 using xda app-developers app

xillius200 said:
All you need for building the kernel is here at this url:
https://github.com/ezterry/manifest-gingerbread-DS/blob/gingerbread/README.mkdn
It used to be on the ezgingerbread rom thread but seems he has a link to the guide which is now on github ^_^
Click to expand...
Click to collapse
Building the kernel for froyo or building the ezgingerbread rom is no problem:
http://forum.xda-developers.com/showthread.php?t=882356
Unfortunately (Ez)gingerbread is an overkill for the tiny G1
My problem is to find out how to build a froyo rom that is not
broken (e.g. cm6). The DREAMteam's
http://forum.xda-developers.com/showthread.php?t=1273549
rom seems to have the most bugs fixed, but again I don't know
how to build it. I need the right android manifest, git repo, etc.
The DREAMteam changelog is astonishingly sparse:
V2.0.0 - 2012-03-09
Update to android 2.2.3. Some changes from 1.9.2 included.
Thanks ptau

ptau said:
Building the kernel for froyo or building the ezgingerbread rom is no problem:
http://forum.xda-developers.com/showthread.php?t=882356
Unfortunately (Ez)gingerbread is an overkill for the tiny G1
My problem is to find out how to build a froyo rom that is not
broken (e.g. cm6). The DREAMteam's
http://forum.xda-developers.com/showthread.php?t=1273549
rom seems to have the most bugs fixed, but again I don't know
how to build it. I need the right android manifest, git repo, etc.
The DREAMteam changelog is astonishingly sparse:
V2.0.0 - 2012-03-09
Update to android 2.2.3. Some changes from 1.9.2 included.
Thanks ptau
Click to expand...
Click to collapse
Well I got in touch with tval aint spoke to him for a while. He said a repo was never made for DREAMteam froyo and the way in which it was created some by pushing files not everything was coding, there was not much point in a repo and he has not got around to it lol and I totally agree with him. So best thing would be to compile a rom from plain AOSP and begin to modify it yourself, this way you learn and better understand rom creation. Plus doing it straight from AOSP will give you the updates you want and in most ways will actually be better ^^ If you want any help I could always introduce you to a few devs see if they would be willing to help ^^
PS: From how you worded your first post it sounded like you were trying to compile just the ezterry kernel xD so I apologise that I misunderstood ^^

99%
xillius200 said:
As far as I remember when it was first started they never had a repository and unless it has changed they still do not lol ill email tvall later lol seems Ldrifta is gone.... :'( if not you can always just compile a normal aosp and then customize it to your liking and speed helps you learn on how to speed up roms that way unlike having an already fast rom of which you learn less from.
Click to expand...
Click to collapse
Thanks. After I looked in the zip, I thought something like that.
Seriously, you don't need speed with this hardware.
Think of cheap, stable, not battery eating
and hackable ARM11 development platform
After that incident with kernel.org they removed all the old android repos
so I have hard times to find the G1 pieces again. ezterry rocks. The kernel
changes are in his git, I could tweak+build the kernel with all the
modules I needed.
Let's see how to get the aosp together ...
(any hints greatly appreciated
PS: From how you worded your first post it sounded like you were trying to compile just the ezterry kernel xD so I apologise that I misunderstood ^^
Click to expand...
Click to collapse
I know, but my German is much better, I swear :angel:

Well.. I'd be happy to help rebuild my rom. Been wanting to set up a repo, but I'm lazy..

tvall said:
Well.. I'd be happy to help rebuild my rom. Been wanting to set up a repo, but I'm lazy..
Click to expand...
Click to collapse
Thanks for the email with tips.
I try to document the building process here:
hxxps://sites.google.com/site/aospdream/
As always, any hints or help from anybody are greatly appreciated ...
Thanks,
ptau

[ROM: DEV] CM7.2 .35 kernel

Ok, this is just something I have been playing with and thought I would share.
It is CyanogenMod 7.2, as close to stock as I can make it. I have taken a lot from Ezet and some stuff from Forumber.
This is not source based as I do not have a grunty enough system to build CyanogenMod from source.
Most importantly, I have started on a new kernel based on the TomGiordano source here:
https://github.com/TomGiordano/kernel_huawei
My Kernel Source:
https://github.com/PaulMilbank/kernel_huawei/tree/cm7-u8800-35
Will upload my source once I can sort out the sources on my computer. I am doing some mods on Aurora kernel too which I will release at some point.
After a few false starts, I compiled the source with their cyanogenmod_u8800_defconfig and it works pretty well for CM7.2.
I fixed atmel vibration using DZOs aurora commits as a guide.
Probably most broken stuff is defconfig related.
Bugs:
Keypad LED's do not work
Autobrightness does not work
Light sensors do not work- probably the cause of the above problems.
Camera force closes
You tell me
Working:
Wifi works
RIL works
Screen/video drivers work well, screen does not suffer annoying no wakeup for me like other kernels.
Atmel Virtual Key vibration works
You tell me
Get It Here:
http://www.mediafire.com/?b2dc7kdmixvas18
I will try and fix all these bugs, but I would be keen for some help too. I don't have time to be a full time dev.
As always, I am not responsible for any bricks, fires or nuclear wars that come about from installing this rom.
Please, please backup with CWM before flashing this.
Paul

PaulMilbank said:
Ok, this is just something I have been playing with and thought I would share.
It is CyanogenMod 7.2, as close to stock as I can make it. I have taken a lot from Ezet and some stuff from Forumber.
This is not source based as I do not have a grunty enough system to build CyanogenMod from source.
Most importantly, I have started on a new kernel based on the TomGiordano source here:
https://github.com/TomGiordano/kernel_huawei.git
Will upload my source once I can sort out the sources on my computer. I am doing some mods on Aurora kernel too which I will release at some point.
After a few false starts, I compiled the source with their cyanogenmod_u8800_defconfig and it works pretty well for CM7.2.
I fixed atmel vibration using DZOs aurora commits as a guide.
Probably most broken stuff is defconfig related.
Bugs:
Keypad LED's do not work
Autobrightness does not work
Light sensors do not work- probably the cause of the above problems.
Camera force closes
You tell me
Working:
Wifi works
RIL works
Screen/video drivers work well, screen does not suffer annoying no wakeup for me like other kernels.
Atmel Virtual Key vibration works
You tell me
Get It Here:
http://www.mediafire.com/?b2dc7kdmixvas18
I will try and fix all these bugs, but I would be keen for some help too. I don't have time to be a full time dev.
As always, I am not responsible for any bricks, fires or nuclear wars that come about from installing this rom.
Please, please backup with CWM before flashing this.
Paul
Click to expand...
Click to collapse
Camera issue??? Please, any issues but camera
»»Sent From My U8800««

This is just to see if I can get people interested in development. I will try document as much as possible what I do and see if we can get some people interested in building a kernel and getting a really good gingerbread cyanogenmod build out. If this goes nowhere, I will just focus on Aurora kernel and ICS. There are a few things I would like to try and include in Aurora to add some features.
We need good 2.6.35 source and this is a good source with a few small bugs, probably due to the config not being completely right. Hopefully they are minor and easily fixed. We have a lot of kernel development going on around the place and we can learn from commits to make a really good build hopefully.
Will try their 7x30_defconfig to make a kernel for my B528 rom too and see what works.
If you replace the boot.img in this rom with the boot.img in Forumber's latest cm7.2 build, it sould all work and give a 2.6.35 experience close to Ezet's 2.6.32 build. It will likely not be as stable because LEWA kernel on my phone at least, is crap.

PaulMilbank said:
This is just to see if I can get people interested in development. I will try document as much as possible what I do and see if we can get some people interested in building a kernel and getting a really good gingerbread cyanogenmod build out. If this goes nowhere, I will just focus on Aurora kernel and ICS. There are a few things I would like to try and include in Aurora to add some features.
We need good 2.6.35 source and this is a good source with a few small bugs, probably due to the config not being completely right. Hopefully they are minor and easily fixed. We have a lot of kernel development going on around the place and we can learn from commits to make a really good build hopefully.
Will try their 7x30_defconfig to make a kernel for my B528 rom too and see what works.
If you replace the boot.img in this rom with the boot.img in Forumber's latest cm7.2 build, it sould all work and give a 2.6.35 experience close to Ezet's 2.6.32 build. It will likely not be as stable because LEWA kernel on my phone at least, is crap.
Click to expand...
Click to collapse
You can use VictorTeam's source.

forumber2 said:
You can use VictorTeam's source.
Click to expand...
Click to collapse
Do you know where it is, I have not been able to find it. Thanks very much man. Keen top take a look at what they have been doing.

PaulMilbank said:
Do you know where it is, I have not been able to find it. Thanks very much man. Keen top take a look at what they have been doing.
Click to expand...
Click to collapse
They have github group https://github.com/Victor-android

.35 kernel based CM7.2 would be pretty dope to me, especially if tethering works

PaulMilbank said:
Do you know where it is, I have not been able to find it. Thanks very much man. Keen top take a look at what they have been doing.
Click to expand...
Click to collapse
here:https://github.com/Victor-android/kernel_huawei/tree/2.6.35-cm-u8800

Thanks, this will likely take a while longer than I thought it would as I am having trouble getting my sources synced locally and on github. If we can pull together all the sources into a kick ass kernel, we should have a really good CM7.2, I would like a rom with built in tethering too. It will just take some time. Running through DZOs excellent repo with a readymade .config and then making small changes is a lot easier than having to make it all up as we go and sort out sources and configs. Maybe I should not have been so cocky at the start!

PaulMilbank said:
Thanks, this will likely take a while longer than I thought it would as I am having trouble getting my sources synced locally and on github. If we can pull together all the sources into a kick ass kernel, we should have a really good CM7.2, I would like a rom with built in tethering too. It will just take some time. Running through DZOs excellent repo with a readymade .config and then making small changes is a lot easier than having to make it all up as we go and sort out sources and configs. Maybe I should not have been so cocky at the start!
Click to expand...
Click to collapse
Nice to hear that someone's still working on U8800's .35 kernel. Good job so far!

PaulMilbank said:
Thanks, this will likely take a while longer than I thought it would as I am having trouble getting my sources synced locally and on github. If we can pull together all the sources into a kick ass kernel, we should have a really good CM7.2, I would like a rom with built in tethering too. It will just take some time. Running through DZOs excellent repo with a readymade .config and then making small changes is a lot easier than having to make it all up as we go and sort out sources and configs. Maybe I should not have been so cocky at the start!
Click to expand...
Click to collapse
Do you use your vendor files for compiling CM7?

forumber2 said:
Do you use your vendor files for compiling CM7?
Click to expand...
Click to collapse
No, I am just using your and Ezets prebuilt binaries and apk's. I do not have the computer power or skill to build from source!

PaulMilbank said:
No, I am just using your and Ezets prebuilt binaries and apk's. I do not have the computer power or skill to build from source!
Click to expand...
Click to collapse
But you could compile kernel?

Compiling and downloading kernel is much smaller and faster. Also their are a lot of comments and files to follow.
Compiling cyanogenmod from source is a huge download and would take forever to compile on my computer. Plus nobody documents the process well and it us specialized to the phone.
Maybe if I can get a good kernel going, others can build cyanogenmod sources for .35 kernel. It all just takes time.
Sent from my U8800 using xda premium

PaulMilbank said:
Compiling and downloading kernel is much smaller and faster. Also their are a lot of comments and files to follow.
Compiling cyanogenmod from source is a huge download and would take forever to compile on my computer. Plus nobody documents the process well and it us specialized to the phone.
Maybe if I can get a good kernel going, others can build cyanogenmod sources for .35 kernel. It all just takes time.
Sent from my U8800 using xda premium
Click to expand...
Click to collapse
Will you try your luck with cm9/10?

PaulMilbank said:
Compiling and downloading kernel is much smaller and faster. Also their are a lot of comments and files to follow.
Compiling cyanogenmod from source is a huge download and would take forever to compile on my computer. Plus nobody documents the process well and it us specialized to the phone.
Maybe if I can get a good kernel going, others can build cyanogenmod sources for .35 kernel. It all just takes time.
Sent from my U8800 using xda premium
Click to expand...
Click to collapse
if you send vendor files to me,i can compile in my free time

forumber2 said:
if you send vendor files to me,i can compile in my free time
Click to expand...
Click to collapse
Maybe Ezets here:
https://github.com/ezeteze/android_device_huawei_u8800.
Not sure otherwise. I don't have any vendor files sorry.

Use these vendor files: click. I built CM 7.2 yesterday and it works just fine with those vendor files.

Unrealized said:
Use these vendor files: click. I built CM 7.2 yesterday and it works just fine with those vendor files.
Click to expand...
Click to collapse
but in this vendor,GPU can't run fully,has a little lag. If we solve this problem,we can make a good cm7 :good:

forumber2 said:
but in this vendor,GPU can't run fully,has a little lag. If we solve this problem,we can make a good cm7 :good:
Click to expand...
Click to collapse
Guess it has something to with the "new" Adreno drivers. Might do some benchmarking later with the older ones. I haven't really experienced lagging myself though. it's kinda the same as w/ .32 based CM7 (especially when using ADWLauncher)

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?