Database Users

[Dev] Porting Roms, Error on loading natives

I'm not sure this is the right place, If it doesn't please remove my posts.
However..
I'm trying to make Oxygen 2.3.2 port for 2.6.35 kernel. (For test myself.)
I make zip and flashed it. It seems flashed and boot but got bootloop on that error code.
I/Netd ( 443): Netd 1.0 starting
I/rmt_storage( 446): rmt_storage user app start
I/rmt_storage( 446): rmt_storage open success
E/rmt_storage( 446): rmt_storage shared memory ioctl failed
Click to expand...
Click to collapse
Its looping..
Is there anyone to give some direction to me? I googled it many times, didn't find anything.
Notices:
I'm using latest libs, stock usr directory with oxygen apps, framework and busybox.
I don't have a linux and my this is not my computer, so I can't edit or touch the kernel. So I'm using stock kernel.

Ozgur desirenin .35 kernel icin olan romu var(son cikan) ona cm7 nin kerneli ni at calisir. Portlamak zor deil kerneller ugrastiriyo. Cm9 simdi biterdi ama kerneli duzenleyemedim. Turkce kaynak yok. Anlayamadim nasil duzenlendigini
Sent from my u8800 using XDA App

Do you have the partitions set for rmt_storage? Perhaps rmt_oeminfo is also needed?
Sent from my U8800

Try adding /system/bin/rmt_oeminfo and /system/bin/oem_rpc_svc

oguzhan mobile said:
Ozgur desirenin .35 kernel icin olan romu var(son cikan) ona cm7 nin kerneli ni at calisir. Portlamak zor deil kerneller ugrastiriyo. Cm9 simdi biterdi ama kerneli duzenleyemedim. Turkce kaynak yok. Anlayamadim nasil duzenlendigini
Sent from my u8800 using XDA App
Click to expand...
Click to collapse
You are allowed to speak other languages on the forum but please say the same in english also. Because if someone else is looking for help for the same question they find it and don't need to make another thread.

Blefish said:
Do you have the partitions set for rmt_storage? Perhaps rmt_oeminfo is also needed?
Sent from my U8800
Click to expand...
Click to collapse
Actually not. I try to use stock rmt_oeminfo and storage.
dzo said:
Try adding /system/bin/rmt_oeminfo and /system/bin/oem_rpc_svc
Click to expand...
Click to collapse
I try it Its worked but this time its got bootloop on Netd server start. So I'm starting over.
Something wrong with abd too. Sometimes Its not recognize the phone and not show it. Its make me crazy
Seems like I need to wait my pc because Its not getting any better for now and I must really learn how to /bin and /xbin works.

I found the problem about not recognizing the device on android. Its stock kernel problem. It disables the debug by default. Damn stock! I'm so nevbie at this =)

Sounds like you are doing fine. Keep it up
Sent from my u8800 using XDA App

arveparve said:
Sounds like you are doing fine. Keep it up
Sent from my u8800 using XDA App
Click to expand...
Click to collapse
Thanks.
Its looping again. Much work to do.
Code:
I/Netd ( 298): Netd 1.0 starting
W/dalvikvm( 303): ERROR: Unable to find decl for native Landroid/content/res/AssetManager;.initWithoutDefaultAsset:()V
E/JNIHelp ( 303): RegisterNatives failed for 'android/content/res/AssetManager'
E/AndroidRuntime( 303): Unable to register all android natives

[GUIDE] How to port AOSP ICS roms to your Device

How to port any ICS AOSP based roms to your Device (AOKP, CM9 & many other)
- for best compatibilty
--> use same android versions. (4.0.4 -> 4.0.4 example)
--> use latest base from CM9 (is best choose for port) or any AOSPbased ICS ROM
--> use each brand for port (mean Desire HD -> Desire S or other HTC devices). you also can port other roms, but you will have issues.
PORT:
-> download latest cm9 base and extract it
-> download target rom and extract it
for Camera
use Camera.apk from base rom for camera issues fix.
Click to expand...
Click to collapse
copy
/app
/framework
/media
/fonts folders and replace in cm9 folder.
repack your zip and let it boot.
if it doesn't boot then copy /system/lib/libandroid_runtime.so from target rom and repack your rom.zip and install again.. if you get bootloop anyway, then just type in adb "adb logcat" and share it with us in this thread..
if you dont get success dont cry, just try to port another rom you can not port all roms
for HTC Devices
to fix network auto select,
decompile framework-res.apk
go to \framework-res\res\values\bools.xml change
<bool name="skip_restoring_network_selection">true</bool>
to false.
Click to expand...
Click to collapse
to fix graphichal issues,
decompile framework.jar
change these files with cm9 base
smali\smali\android\os
Environment
SystemProperties
smali\smali\android\view
HardwareCanvas
HardwareRenderer$Gl20Renderer
HardwareRenderer$GlRenderer
HardwareRenderer
Click to expand...
Click to collapse
Click to expand...
Click to collapse
enjoy!
if you like this guide, just give 5 stars to thread and click thanks button

hi, there, and i own a huawei u8800, we allready have a aosp ics 4.0.4 aurora room but i would like to have cm9 or aokp into our phone. in this case based is aosp ics aurora and ported will be cm9 or aokp for example? i´m right?
maybe is better port cm9 from desire z to my huawei u8800, since they have the same cpu and gpu.
dont want tou build a rom, just port.
please i need help. thanks anyway.

lol be thankful you have an ICS rom.. Huawei X6 users like me are trying our best to port from u8860's ICS.
I'd like to ask if the method works for a device that does not have official ICS? i.e. porting an ICS rom to official GB?
Kindly advise sir, and thanks again!

I get the same that in miui v4... boot loop and adb says no device

I get AtCmdFwd error.

Could you post the link of latest cm9 base?

im getting stuck in a bootloop...
INFO:
Device-Samsung Infuse
CM9 Base being used to port- http://forum.xda-developers.com/showthread.php?t=1601844
Rom trying to port- http://www.slimroms.com/ (the i9000 version aka galaxy s)
What i did:
1) opened cm9 base with 7zip, deleted app, framework, fonts, media folders
2) replaced deleted folders with app, framework, fonts and media folders from slim ics base 3.6
3) opened up slim ics 3.6 i9000 essentials with 7zip
4)navigated to app folder and moved apks files from ther to the cm9 base - did the same with framework, fonts, and media folders (I did not just copy the folders this time! i only copied the files inside the folders)
5) put zip on sdcard
6) rebooted and started log cat
any help would be apreciated if i dont answer back right away its because i have to pick my sister up from school
Here are the logcats: (All are the same logcat...but two of them are filtered)

I think I kniw what the problem is...gonna attemot a fix after dinner
EDIT i got out of the boot loops and booted into my portes slimics...now to fix the bugs...there is ALOT
thanks for the guide will def give you some credit once i get this stable...may be getting some help from another dev

So as long as the base and ported roms are from the same manufacturer, this will work?
Sent from my LG-E739 using Tapatalk 2

how to port aosp ics to cm9?

good guide
You can add
Copy etc\cron
And etc\init.d files to run RomControl fix

Am stuck at logo screen.
Can't get logcat because ADB can't find my device.
What to do?
Sent from my LG-E739 using Tapatalk 2

mg2195 said:
I think I kniw what the problem is...gonna attemot a fix after dinner
EDIT i got out of the boot loops and booted into my portes slimics...now to fix the bugs...there is ALOT
thanks for the guide will def give you some credit once i get this stable...may be getting some help from another dev
Click to expand...
Click to collapse
Can you please tell what was the problem and how did you fixed? Thanks.

medicjunKie said:
So as long as the base and ported roms are from the same manufacturer, this will work?
Sent from my LG-E739 using Tapatalk 2
Click to expand...
Click to collapse
It would be sane screen res e.g HDPI to HDPI
And also the same processor type too helps
Sent from my LT15i using xda premium

see i hve a question...., what does base mean? does it mean the ics rom which i hve for my device already ported or any ics rom available for my device's manufacturer?
like my phone is samsung galaxy 3....so shud the base be the rom which is available for my g3 or it can be any ics rom like say ics rom for samsung galax s?
---------- Post added at 09:37 AM ---------- Previous post was at 09:36 AM ----------
i m seriously cponfused with that part..... m not gettin g what the base and the rom to be ported shud be?

My logcat ...?? what can i do? http://www.embedupload.com/?d=4HKCKXGIK2

I'm trying to port slimICS and it gets stuck at boot. Here's my logcat if it helps.
http://logcat.miui.us/893012

Zorua said:
I'm trying to port slimICS and it gets stuck at boot. Here's my logcat if it helps.
http://logcat.miui.us/893012
Click to expand...
Click to collapse
see here
Code:
169: E/dalvikvm( 1190): ERROR: couldn't find native method
170:
171: E/dalvikvm( 1190): Requested: Lcom/android/server/PowerManagerService;.nativeStartSurfaceFlingerOffAnimation:(I)V
172:
173: E/JNIHelp ( 1190): RegisterNatives failed for 'com/android/server/PowerManagerService', aborting
baksmali classes.dex of services.jar
find PowerManagerService.smali file in the path com/android/server
add line
Code:
.method private native nativeStartSurfaceFlingerOffAnimation(I)V
.end method

tathanhlam66 said:
see here
Code:
169: E/dalvikvm( 1190): ERROR: couldn't find native method
170:
171: E/dalvikvm( 1190): Requested: Lcom/android/server/PowerManagerService;.nativeStartSurfaceFlingerOffAnimation:(I)V
172:
173: E/JNIHelp ( 1190): RegisterNatives failed for 'com/android/server/PowerManagerService', aborting
baksmali classes.dex of services.jar
find PowerManagerService.smali file in the path com/android/server
add line
Code:
.method private native nativeStartSurfaceFlingerOffAnimation(I)V
.end method
Click to expand...
Click to collapse
I don't have the folder com/android/server/. What am I doing wrong?
EDIT: Wow, I sound so stupid. Nvm, I did that edit. I had to look up smali and baksmali guides. I'll flash it and see if it boots.
Okay, still refusing to boot.
New logcat: http://logcat.miui.us/894002
EDIT 2: Booted but storage isn't working.
Logcat: http://logcat.miui.us/889025

Zorua said:
EDIT 2: Booted but storage isn't working.
Logcat: http://logcat.miui.us/889025
Click to expand...
Click to collapse
Try decompiling the framework-res.apk and change the storage-list.xml in the xml folder.

Porting Android 4.1, Jelly Bean to Desire HD

Hi Guyz,
This is kind of my Ambitious Project of Porting Jelly Bean to our Desire HD ... while I cannot do this on my own, I would be happy if other developers can help me in this. Most of our TOP DEVS have moved on to the Sensation and One series ... I think others (NOOBS like ME) should take an initiative to learn more about Deving.
I am currently trying to get the device Booted....will let know about the progress ...

Good luck to you sir. It sounds ambitious, but everyone has to start somewhere.
Maxy
Sent from my HTC Desire HD A9191 using xda premium

i also want to try, i know C basics. it helps?
any tips from the expert devs?

I'll happily be a tester once you guys get it up and running (I don't know any programming, sorry)
Sent from my Desire HD using xda premium

i an very skeptic about getting it booting up. but ill try my best.
i will also ask from help from an expert Linux and C programmer
EDIT: wow... i got thankses XD
obviously it didn't boot, and im not an expert so i have no idea whats wrong it kernel / rom.
sorry everyone, i think we should wait for the source code and for an expert developer..

DubelBoom said:
i an very skeptic about getting it booting up. but ill try my best.
i will also ask from help from an expert Linux and C programmer
EDIT: wow... i got thankses XD
obviously it didn't boot, and im not an expert so i have no idea whats wrong it kernel / rom.
sorry everyone, i think we should wait for the source code and for an expert developer..
Click to expand...
Click to collapse
One of the biggest issues you have will be the display drivers that on the SDK are made for the worst chip when it comes to Android/linux. I wil be honest with you. Until the source for the ICS kernel is released in a few months you will be fighting to even get the basic things working. Gonna need to spend lots of time fighting in linux for it to happen.

zelendel said:
One of the biggest issues you have will be the display drivers that on the SDK are made for the worst chip when it comes to Android/linux. I wil be honest with you. Until the source for the ICS kernel is released in a few months you will be fighting to even get the basic things working. Gonna need to spend lots of time fighting in linux for it to happen.
Click to expand...
Click to collapse
yeah zelendel .. u are right.. display is a problem..
first my DHD was stuck at HTC logo.. after a few changes. it moved past the logo.. i think it booted without any display..
here is the logcat
https://www.dropbox.com/s/yngiqzp70iut3lq/logcat.txt

zelendel said:
One of the biggest issues you have will be the display drivers that on the SDK are made for the worst chip when it comes to Android/linux. I wil be honest with you. Until the source for the ICS kernel is released in a few months you will be fighting to even get the basic things working. Gonna need to spend lots of time fighting in linux for it to happen.
Click to expand...
Click to collapse
i tried porting the Galaxy Nexus's rom.
i have no idea what to do so it will boot...

Hey man! Nice initiative!
You read this? http://forum.xda-developers.com/showpost.php?p=28020178&postcount=36
He's already ported it to two devices, so you should be able to get some help there !

riteshbendre said:
yeah zelendel .. u are right.. display is a problem..
first my DHD was stuck at HTC logo.. after a few changes. it moved past the logo.. i think it booted without any display..
here is the logcat
https://www.dropbox.com/s/yngiqzp70iut3lq/logcat.txt
Click to expand...
Click to collapse
Read some of log and noticed some htc apps were being used..but why? This is AOSP
Sent from my Desire HD using xda app-developers app

david.degraw54 said:
Read some of log and noticed some htc apps were being used..but why? This is AOSP
Sent from my Desire HD using xda app-developers app
Click to expand...
Click to collapse
Because it wansnt ported right...he added HTC apps
Sent from my Desire HD using xda app-developers app

The biggest issue might be get gralloc working right...
E/HAL ( 1526): load: module=/system/lib/hw/gralloc.msm7x30.so
E/HAL ( 1526): Cannot load library: link_image[1891]: 1199 could not load needed library 'libQcomUI.so' for 'gralloc.msm7x30.so' (reloc_library[1306]: 1199 cannot locate 'eglGetRenderBufferANDROID'...
That is libs searching other libs, meaning, compiling is the easiest way to fix thoose. but for that.. need source
You can easly get boot withought gralloc and egl... but, that will only bring a lot of fcs

rom stuck on splash screen.
logcat: https://dl.dropbox.com/u/22680754/logcat.txt
(i didn't do any changes on ramdisk or boot.img. if one of them is the problem, just say that and when ill figure out how to edit them, i will post here again )
thanks

http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
Check this link it will help with ramdisk
Sent from my Desire HD using xda app-developers app

im about to edit ramdisk. i haven't did that before. there should be files, with of them i need to edit? how to edit?
and im going tomorrow morning to a 3 days trip. i hope i will edit the ramdisk today

riteshbendre said:
yeah zelendel .. u are right.. display is a problem..
first my DHD was stuck at HTC logo.. after a few changes. it moved past the logo.. i think it booted without any display..
here is the logcat
https://www.dropbox.com/s/yngiqzp70iut3lq/logcat.txt
Click to expand...
Click to collapse
Gimme your ROM so far, I'll try to get it working

how is the porting going

f_E_a_R_e_D said:
how is the porting going
Click to expand...
Click to collapse
Boot animation is displaying, current error is
Code:
E/mDnsConnector( 1326): Error in NativeDaemonConnector: java.io.IOException: No such file or directory
---------- Post added at 07:51 PM ---------- Previous post was at 07:47 PM ----------
quinny899 said:
boot animation is displaying, current error is
Code:
e/mdnsconnector( 1326): Error in nativedaemonconnector: Java.io.ioexception: No such file or directory
Click to expand...
Click to collapse
i have a boot
-EDIT- May be a false alarm, stuck on Starting apps...

can a bad ramdisk brick my phone?
because on all guilds i see they are saying to be careful with editing the ramdisk....

Starting apps may take a while (from my experiance anyway) cause its the first, fresh boot. Screenshots (if you can)? Getting really excited about this already (flashaholic senses are kicking in, lol)
Sent from my Desire HD using one thumb

[Thinktank]Bringing Jellybean to the Play -- Alpha GSM/CDMA [8/22]

Xperia Play Users,
I am currently working on bringing CM10 to the Play, and I'm looking for input from anybody else who has ideas.
The Rules:
Post something constructive, no "Good Luck" "reserved" etc. this thread is for working through problems when building CM10
That said.
Update: I'll be posting errors here, so it'll be easy to keep track of.
First error I hit (& fixed? (compiler hasn't failed yet on this one)) deals with hardware/qcom/display/libcopybit where copybit_c2d.cpp fails to compile with a couple of errors related to "KGSL_USER_MEM_TYPE_ION" is not declared. (iirc)
I fixed this (I think) by replacing CM10's qcom/display with caf's qcom/display
Second error: (Erroring out right now)
In-line kernel building. I'm getting a (possible) GCC compiler false error where it says
Code:
/home/paxchristos/Android_Source/cm10/kernel/semc/msm7x30/drivers/net/wireless/bcm4329/wl_iw.c: In function 'wl_iw_set_pmksa':
/home/paxchristos/Android_Source/cm10/kernel/semc/msm7x30/drivers/net/wireless/bcm4329/wl_iw.c:5335:5: error: array subscript is above array bounds [-Werror=array-bounds]
/home/paxchristos/Android_Source/cm10/kernel/semc/msm7x30/drivers/net/wireless/bcm4329/wl_iw.c:5338:5: error: array subscript is above array bounds [-Werror=array-bounds]
/home/paxchristos/Android_Source/cm10/kernel/semc/msm7x30/drivers/net/wireless/bcm4329/wl_iw.c: At top level:
cc1: error: unrecognized command line option "-Wno-unitialised" [-Werror]
Possible fix: for now turn off in-line kernel building until either error is solved.
Error 3 -- Removed in-line kernel building, but forgot to set device/semc/zeusc/prebuilt/kernel to copy to out/target/product/zeusc/kernel ... whoops
Error 4 -- The way things are sent to logcat has been changed from ICS
Code:
/home/paxchristos/Android_Source/cm10/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: out/target/product/zeusc/obj/SHARED_LIBRARIES/lights.semc_intermediates/lights.o: in function write_string:device/semc/msm7x30-common/liblights/lights.c:87: error: undefined reference to 'LOGE'
/home/paxchristos/Android_Source/cm10/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: out/target/product/zeusc/obj/SHARED_LIBRARIES/lights.semc_intermediates/lights.o: in function write_int:device/semc/msm7x30-common/liblights/lights.c:66: error: undefined reference to 'LOGE'
/home/paxchristos/Android_Source/cm10/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: out/target/product/zeusc/obj/SHARED_LIBRARIES/lights.semc_intermediates/lights.o: in function set_light_backlight:device/semc/msm7x30-common/liblights/lights.c:131: error: undefined reference to 'LOGV'
Fixed by copying over liblights/ from jellybean version of msm7x30-common/
Error 5 -- Same error happens with msm7x30-common/libsensors/
Fixed the same way as error 4
Error 6 -- Last error I'm gonna talk about tonight:
I did (apparently) a half baked revert to using a prebuilt kernel & it just bit me in the butt. I'll fix it tomorrow & keep updating this.
Fixed it by using half of FXP's custombootimg.mk where it calls (PRODUCT_OUT)/kernel instead of (TARGET_PREBUILT_KERNEL)
Anybody else up for learning with me & briniging JB to the Play?
Pax
UPDATE: Pre-alpha release are available here: http://www.mediafire.com/?6ggud46a7c6cq
Latest kernel is here: http://forum.xda-developers.com/showpost.php?p=29498363&postcount=233
Remember, this is an alpha, a lot of stuff does not work. Please logcat any errors you find, otherwise (unless it's something like baseband unknown) I WILL IGNORE THEM
What Works:
CDMA Data
Calls
SMS
AUDIO!!
HW Video
GPS
What Doesn't Work:
Haven't tested to much, you guys tell me

I came across this by googling, hope that helps :
http://forum.xda-developers.com/showthread.php?t=1104142&page=4
Cheers, I'm willing to learn if you don't mind teaching a newbie in dev
Sent from my Play using xda app-developers app

sasukekun67 said:
I came across this by googling, hope that helps :
http://forum.xda-developers.com/showthread.php?t=1104142&page=4
Cheers, I'm willing to learn if you don't mind teaching a newbie in dev
Sent from my Play using xda app-developers app
Click to expand...
Click to collapse
Thank you, I think for JB CM wants to use -O2 when compiling so I'm not gonna touch that one (for now)
A Good place to start would be with Keiran's building ICS tutorial with some changes.
First off, I'm using Ubuntu 10.04 LTS, but Ubuntu 12.04 LTS *should* work (no guarantees)
To download the vendor tree (vendor/semc)
use this instead of what Keiran has (koush cleaned out a lot of the vendor trees out of his git, and mine is outdated)
Code:
git clone https://github.com/kali-/proprietary_vendor_semc.git -b ics semc
also, I'm using the ICS device tree (same as keiran) instead of JB because the JB tree's are not 100% functional right now.
Pretty much if you follow that (& I suggest instead of doing make -j# bacon do mka bacon) & run into any errors, i'll help with whatever suggestions I might have (or anybody else)
Note: If somebody needs help trying to build AOKP, I'll help, but I'm not as familiar with the source as I am with CM
Pax

Also, before I forget, here a how-to sync caf's (code aurora forums) repo (similar to cm/AOSP/etc)
https://www.codeaurora.org/xwiki/bin/QAEP/
The branch I synced was jb.
Pax
Sent from my R800x using Tapatalk 2

First build is complete, I'm need to make a nanadroid & flash a new kernel (I'm on keics/CNA right now so it'll be a little bit before I post results )
Pax

hi,
it won't boot on sony ericsson hdpi devices without msm.... changes (look at mini pro thread you will find a lot of usefull information about it)
you need to enable triple buffer in the kernel

Thanks Nickholtus, i'll look into it.
Status 6 error in the update-script (really? off the cm-10 building ?!?!) so i'm working on that now...

if you can fix the framebuffer error in the kernel we have a fully booting rom
kamarush made a build for me (from cm10 sources) with play device tree (his own)
only that error is preventing a boot
edit: can you upload your current kernel?
i know a ugly fix to get it at least booting, but i am on holiday now and i only have a windows pc with slow internet and no kernel

nickholtus said:
if you can fix the framebuffer error in the kernel we have a fully booting rom
kamarush made a build for me (from cm10 sources) with play device tree (his own)
only that error is preventing a boot
edit: can you upload your current kernel?
i know a ugly fix to get it at least booting, but i am on holiday now and i only have a windows pc with slow internet and no kernel
Click to expand...
Click to collapse
I'll probably base it off either FXP or Mjolnir's kernel (sorry Lupus)
[sritke]Do you have a link with a how-to add in triple buffer? [/strike] CAF!! - https://www.codeaurora.org/gitweb/q...it;h=50c3bc621e2cf0c3587b1827d931738d148c33d8
UPDATE: Nickholtus, it's not this easy, is it?!?! https://www.codeaurora.org/gitweb/q...;hpb=1125e58c5744e1ad833e30e5d2a74eb6dca1ca20
Also, if anybody wants to try to fix the update-script, i've attached it

no i don't know, we think it is in msm_fb.c in the kernel source
see this post for more info: http://forum.xda-developers.com/showpost.php?p=29062634&postcount=177
edit:
i don't think so, but i can't try it.
kamarush couldn't find it (how to enable triple buffer) but if that's it it is an easy fix

nickholtus said:
no i don't know, we think it is in msm_fb.c in the kernel source
see this post for more info: http://forum.xda-developers.com/showpost.php?p=29062634&postcount=177
---------- Post added at 09:03 PM ---------- Previous post was at 08:58 PM ----------
i don't think so, but i can't try it.
kamarush couldn't find it (how to enable triple buffer) but if that's it it is an easy fix
Click to expand...
Click to collapse
Here's the best diff (all 3) i've found for the commit
https://www.codeaurora.org/gitweb/q...ff;h=acffb1675f468a85f528e01707f3fa98f45b77f8

i am going ask kamarush and see what he thinks
he thinks it can probaply fix it

While I'm no help for this, for the script stuff, can't you enlist the help of the supercharger guy? He seems to be pretty adept with script lark.
Obviously, that's coming from an outsider.

Sythedragon said:
While I'm no help for this, for the script stuff, can't you enlist the help of the supercharger guy? He seems to be pretty adept with script lark.
Obviously, that's coming from an outsider.
Click to expand...
Click to collapse
hahaha, different type of scripts, but thanks for the idea
Pax
Also: Made the changes in the kernel I have on hand, fxp's from cm9/10 source. I've added in the correct stuff to cyanogen_zeus_defconfig & mach-msm/board-semc_zeus.c as soon as I'm done downloading Doom's ndk, i'll try & build it & see if it works
Pax

kamarush is making the kernel for me, with triple buffer enabled
edit: haha you was faster

nickholtus said:
kamarush is making the kernel for me, with triple buffer enabled
edit: haha you was faster
Click to expand...
Click to collapse
I was, then I got arrowed in the knee
Or i would be, but then my git clone downloads at ~200 kb/s

Nickholtus,
Here's a test kernel, the changes are in the zImage, the ramdisk is FXP's from well, it's a source build off code from yesterday.

thanks
going to try it now
still the same error
edit: i need to get adb working
doesn't find the device

Lemme look into it, i'll test it out shortly (trying to get my build of cm10 to install )
Pax
Edit: Nickholtus, could you post a link to your build, mine just doesn't want to work
Pax
Edit 2: I think it's because i'm coming from CNA to CM10, i'm gonna build cm9 then retry with that
Pax

i can't upload my build, the upload speed here is 15kbps atm

Porting sense 4 [HELP NEEDED]

Hello all,
@thehacka1 is now working on a Sense 4 port for armv6. @xizt1boy, @4ndaKava and me are helping him.
Until now, everything went OK. There was a lot of smali editing (thehacka1 is amazing cause he spent hours and hours in front of his computer, working ), but errors disappeared one by one, and we hoped to finally make it boot.
But we're now facing an error :
logcat said:
E/JNIHelp ( 104): Native registration unable to find class 'com/android/server/NetworkManagementSocketTagger', aborting
Click to expand...
Click to collapse
Whatever we've tried didn't work. At first, we thought the class wasn't there, but it is there (in framework.jar) and contains exactly the same code that is in Sense 3.5 and cm9. Then we thought there was a problem with JNIHelp. We located JNIHelp.c in libnativehelper.so, and we replaced this lib with Sense 4 one (libc SIGILL), cm10 one (Netd error) and Sense 3.5 (also Netd error). Then we realised that some framework jars were not DexOpted at the first boot. So we modded BOOTCLASSPATH in init.rc to add the new jars, but it still doesn't work.
Do you guys have any ideas about how to fix this error ?
Thanks a lot !

izi501 said:
Hello all,
@thehacka1 is now working on a Sense 4 port for armv6. @xizt1boy, @4ndaKava and me are helping him.
Until now, everything went OK. There was a lot of smali editing (thehacka1 is amazing cause he spent hours and hours in front of his computer, working ), but errors disappeared one by one, and we hoped to finally make it boot.
But we're now facing an error :
Whatever we've tried didn't work. At first, we thought the class wasn't there, but it is there (in framework.jar) and contains exactly the same code that is in Sense 3.5 and cm9. Then we thought there was a problem with JNIHelp. We located JNIHelp.c in libnativehelper.so, and we replaced this lib with Sense 4 one (libc SIGILL), cm10 one (Netd error) and Sense 3.5 (also Netd error). Then we realised that some framework jars were not DexOpted at the first boot. So we modded BOOTCLASSPATH in init.rc to add the new jars, but it still doesn't work.
Do you guys have any ideas about how to fix this error ?
Thanks a lot !
Click to expand...
Click to collapse
maybe post the full logcat? ive helped port sense 3.5 and 4 to the epic 4g. libnative.so, libc net.d and a few other files are linked together which means you have to copy all of the ones together( or merge them which takes quite a while). a full logcat will help wonders though. thanks

Here is the requested logcat sir. Hope you know how to fix it.

Andy_nu said:
maybe post the full logcat? ive helped port sense 3.5 and 4 to the epic 4g. libnative.so, libc net.d and a few other files are linked together which means you have to copy all of the ones together( or merge them which takes quite a while). a full logcat will help wonders though. thanks
Click to expand...
Click to collapse
Which libs are linked together ?
Envoyé depuis mon HTC FeuSauvage S avec CM10.1

izi501 said:
Which libs are linked together ?
Envoyé depuis mon HTC FeuSauvage S avec CM10.1
Click to expand...
Click to collapse
try using lib.c, libnativehelper.so, libandroid_runtime, netd from sense to your base. then post another logcat.

Andy_nu said:
try using lib.c, libnativehelper.so, libandroid_runtime, netd from sense to your base. then post another logcat.
Click to expand...
Click to collapse
I added libnativehelper, libc, libandroid_runtime, libnetutils, libnetlink, libnetmgr, libnetmonitor and the bootanimation doesn't appear. It bootloops the kernel, in fact.

izi501 said:
I added libnativehelper, libc, libandroid_runtime, libnetutils, libnetlink, libnetmgr, libnetmonitor and the bootanimation doesn't appear. It bootloops the kernel, in fact.
Click to expand...
Click to collapse
give me
adb shell dmesg
and
adb logcat