[DEV][CRACKFLASHERS] 4.1 Jelly Bean JRN84D (Gnex)/ JRN84C (SDK)

---

Successfully ported. Partially working.

Whats working?

-Touchscreen
-Bluetooth
-GPU
-Camera
-Softkeys
-NFC
-Butter
-SDcard
-ADB
-USB

What's not working?

-Audio
-Wifi
-GSM
-libwvm
-More stuffs not working.



More Proper Screenshot





Download: http://files.mrks.me/JRN84D_NS.zip (md5: 28e935c14c31f38940b0c9ced0778766)
----------------------------------------------------------------------------------------------------------------------

SDK port by Steve676 (Wifi Working)

http://forum.xda-developers.com/show...&postcount=258 No Gapps

Originally Posted by DaXmax

Hey guys, i eventually trying to port Jelly Bean on our device, but its a no go, anyone can help here?

I/Netd    ( 9965): Netd 1.0 starting
I/mediaserver( 9964): ServiceManager: 0x40ce2d80
I/AudioFlinger( 9964): Using default 3000 mSec as standby time.
I/CameraService( 9964): CameraService started (pid=9964)
W/AudioFlinger( 9964): findSuitableHwDev_l() loading well know audio hw modules
E/AudioFlinger( 9964): int android::load_audio_interface(char const*, audio_hw_d
evice_t**) wrong audio hw device version 0000
I/AudioFlinger( 9964): loadHwModule() error -22 loading module primary
E/AudioFlinger( 9964): int android::load_audio_interface(char const*, audio_hw_d
evice_t**) wrong audio hw device version 0000
I/AudioFlinger( 9964): loadHwModule() error -22 loading module a2dp
E/AudioFlinger( 9964): int android::load_audio_interface(char const*, audio_hw_d
evice_t**) couldn't load audio hw module audio.usb (No such file or directory)
I/AudioFlinger( 9964): loadHwModule() error -2 loading module usb
E/AudioPolicyManagerBase( 9964): Failed to initialize hardware output stream, sa
mplingRate: 0, format 0, channels 0
E/AudioPolicyService( 9964): couldn't init_check the audio policy (No such devic
e)
E/SchedPolicy( 9964): open of /dev/cpuctl/apps/bg_non_interactive/tasks failed:
No such file or directory
E/BandwidthController( 9965): runIptablesCmd(): failed /system/bin/iptables -t r
aw -N bw_raw_PREROUTING res=256
E/BandwidthController( 9965): runIptablesCmd(): failed /system/bin/ip6tables -t
raw -N bw_raw_PREROUTING res=256
D/MDnsDS  ( 9965): MDnsSdListener::Hander starting up
E/Netd    ( 9965): Unable to start MDnsSdListener (Invalid argument)
E/SocketListener( 9965): Obtaining file descriptor socket 'mdns' failed: Invalid
 argument
I/Netd    (10086): Netd 1.0 starting
I/ServiceManager(   72): service 'media.audio_flinger' died
I/ServiceManager(   72): service 'media.player' died
I/ServiceManager(   72): service 'media.camera' died
I/ServiceManager(   72): service 'media.audio_policy' died
I/Netd    (10112): Netd 1.0 starting

Is this the whole log?

Originally Posted by rlasalle15

Is this the whole log?

Yes, i already fixed the kernel boot already, thats only the starting, do you want to work together so we can served a working JB till the official one comes?

Originally Posted by DaXmax

Yes, i already fixed the kernel boot already, thats only the starting, do you want to work together so we can served a working JB till the official one comes?

yea I will send you a PM with my gmail addy

I'm not much of a expert but ,
something with audio drivers ? have you tried replacing them

E/AudioFlinger( 9964): int android::load_audio_interface(char const*, audio_hw_d evice_t**) wrong audio hw device version 0000

and also check files on bin folder . can't say much without goods on hand unfortunately , doesn't have the bandwidth to download the files right now

Originally Posted by Oodie

I'm not much of a expert but ,
something with audio drivers ? have you tried replacing them


and also check files on bin folder . can't say much without goods on hand unfortunately , doesn't have the bandwidth to download the files right now

yea tons of fmjar edits are in order in addition to the audio files

I'm not good at this part, but one korean developer(jijonheyoni, galaxy s2 korean varient dev) said that this problem can be caused because kernel's library and platform library is not corresponding.....(I'm just translating..)
Sent from my Nexus S using xda app-developers app

Originally Posted by ioplkj13

I'm not good at this part, but one korean developer(jijonheyoni, galaxy s2 korean varient dev) said that this problem can be caused because kernel's library and platform library is not corresponding.....(I'm just translating..)
Sent from my Nexus S using xda app-developers app

yeah , quite possible , since JB kernel is updated ( as i think lookin @ GN's screenshots ) & the kernel should correspond with audio/video drivers
& also there are huge improvements in video & audio in JB even wifi & network i guess .

There are multiple devs for One X and SGS3 that's got a booting and functional port of JB to their devices. You could try contacting one of them.

Sent from my Nexus S using Tapatalk 2

Originally Posted by Oodie

yeah , quite possible , since JB kernel is updated ( as i think lookin @ GN's screenshots ) & the kernel should correspond with audio/video drivers
& also there are huge improvements in video & audio in JB even wifi & network i guess .

The ramdisks arent to much different. There are few new files though. init.trace.rc and init.usb.rc...but other then those its pretty close. Shouldnt we be able to use an ICS boot.img? I could be way off here but we are kinda backporting from a totally different device then what we have. I think a lot of fmjar edits could get it closer.