14Jul test kernel

JetKernel testing releases will be posted here by the DevTeam. This forum is open for feedback from test users.
Forum rules
Dev Team members can post testing releases here. Please give a link to the source base that was used for a release or post patches / changelogs along with your binary packages.

Registered users can reply with their test feedback. Please only post test feedback here. For general (e.g. install related questions) please use the support Q&A section.

14Jul test kernel

Postby MadRocker » Thu Jul 14, 2011 8:04 am

Okay do not expect too much.

Experience will vary with each Android version for S8000....

Modules is any in all recent Android version for S8000 btgpio, camera, battery, amk8973, ak8976, ak8973b, radio-tea5764, si_47* radios and a few more. xsr and rfs is not in this kernel so you might need the module if you are testing that.

The kernel "Dopi 24March2011 experimental branch" .config is in each zip file only major change was the sound/soc/codec "Makefile" to get rid of the #wm8990 rest should be default.
Still need to fix the USB gadget OTG non android errors for each sub option m / * items.

There is 2 zImages:
1. Both zImages has the s3c battery enabled as module and fake batter is off.
Does this mean the battery work = no but it will show other options and give android.log / kernel.log alternative output.

2. A few other small changes, ignore the audio codec that loads and fails in the logs as Dopi has fixed this already, mic input error is still the same.

Differences:
1. Has the usb -> gadget -> OTG set as "cdc composit Eth acm"
2. Has the usb -> gadget -> OTG set as "usb gadget serial cdc acm"

If you want to test this and post output please include the specific android version and changes you made to the init.rc and content of the modules folder + specific important .ko files dates.

What you need to look for in android.log and kernel.log:
GPS, Bluetooth, Radio, gprs, Mac addresses, serial, pretty much anything that is related to usb and communication devices in this phone.

Example:
Code: Select all
<6>[    1.233819] radio_tea5764: v0.01: A driver for the TEA5764 radio chip for EZX Phones.
<4>[    1.235887] g_cdc gadget: using random self ethernet address
<4>[    1.236131] g_cdc gadget: using random host ethernet address
<4>[    1.237415] MAC 1e:07:**:**:**:**
<4>[    1.237571] HOST MAC 66:a2:**:**:**:**
<6>[    1.240215] DUN is registerd
<4>[    1.240366] usb_add_config finished
<6>[    1.240492] g_cdc gadget: CDC Composite Gadget, version: King Kamehameha Day 2008
<6>[    1.240722] g_cdc gadget: g_cdc ready


Code: Select all
<6>[    1.187690] s3c64xx-uart.1: s3c_serial0 at MMIO 0x7f005400 (irq = 20) is a S3C64XX
<6>[    1.189451] s3c64xx-uart.2: s3c_serial1 at MMIO 0x7f005800 (irq = 24) is a S3C64XX
<6>[    1.191342] s3c64xx-uart.3: s3c_serial2 at MMIO 0x7f005c00 (irq = 28) is a S3C64XX


Code: Select all
<7>[    3.236444] Registering 'BT GPIO is a success'  The major device number is 207


Code: Select all
D/CameraService( 1807): CameraService::connect E (pid 1992, client 0x15970)
D/CameraService( 1807): Client::Client E (pid 1992)
D/CameraHardwareStub( 1807): initHeapLocked: preview size=176x144
D/CameraService( 1807): Client::Client X (pid 1992)
D/CameraService( 1807): CameraService::connect X
D/CameraService( 1807): getParameters(picture-format=jpeg;picture-size=213x350;preview-format=yuv422sp;preview-frame-rate=15;preview-size=176x144)
D/CameraService( 1807): getParameters(picture-format=jpeg;picture-size=213x350;preview-format=yuv422sp;preview-frame-rate=15;preview-size=176x144)
D/Camera  ( 1992): app passed NULL surface
D/CameraService( 1807): setPreviewDisplay(0x0) (pid 1992)
D/CameraService( 1807): getParameters(picture-format=jpeg;picture-size=213x350;preview-format=yuv422sp;preview-frame-rate=15;preview-size=176x144)
D/CameraService( 1807): setParameters(preview-size=176x144;preview-format=yuv422sp;jpeg-quality=85;picture-size=213x350;picture-format=jpeg;preview-frame-rate=15)
D/CameraHardwareStub( 1807): initHeapLocked: preview size=176x144
V/camera  ( 1992): startPreview
D/CameraService( 1807): startPreview (pid 1992)
D/CameraService( 1807): startCameraMode(0) (pid 1992)
D/CameraService( 1807): mSurface is not set yet.
D/CameraService( 1807): startPreviewMode (pid 1992)
D/Camera-JNI( 1992): dataCallback(16, 0x136020)


Code: Select all
E/BatteryService( 1819): acOnlinePath not found
E/BatteryService( 1819): usbOnlinePath not found
E/BatteryService( 1819): batteryStatusPath not found
E/BatteryService( 1819): batteryHealthPath not found
E/BatteryService( 1819): batteryPresentPath not found
E/BatteryService( 1819): batteryCapacityPath not found
E/BatteryService( 1819): batteryVoltagePath not found
E/BatteryService( 1819): batteryTemperaturePath not found
E/BatteryService( 1819): batteryTechnologyPath not found


Temp on google code:
http://code.google.com/p/mad-rocker-s80 ... loads/list

HAVE FUN :D
MadRocker
Dev Team
Dev Team
 
Posts: 528
Joined: Sun Dec 12, 2010 7:15 am

Advertisement

       

Re: 14Jul test kernel

Postby Byeranger » Thu Jul 14, 2011 1:11 pm

Ah an update :D Testing it right away
Byeranger
Forum Moderator
Forum Moderator
 
Posts: 162
Joined: Thu Oct 21, 2010 3:26 pm
Location: Holland

Re: 14Jul test kernel

Postby Gotomtom95 » Thu Jul 14, 2011 6:47 pm

eeh... can someone explain to me how and what to download?
JETDROID WOOOT
User avatar
Gotomtom95
Freshman
 
Posts: 5
Joined: Thu May 05, 2011 1:49 pm

Re: 14Jul test kernel

Postby MadRocker » Sat Jul 16, 2011 4:46 am

The audio files needs some love maybe someone can get audio working from the attached "2.6.24 Samsung-s3c6410" kernel files. This is kernel files not android files.

They have lin in and mic in we just need to get this MIC-IN / LINE-IN from the wm8990 or other sound-soc-codecs to the JetKernel MAX8990 or something.
This should be good examples to patch our MAX8990 with.

If you want to build a zImage from this audio files keep in mind this error below.
Code: Select all
  CC      sound/soc/s3c64xx/s3c6410-i2s-v32.o
sound/soc/s3c64xx/s3c6410-i2s-v32.c: In function 's3c_i2s_hw_params':
sound/soc/s3c64xx/s3c6410-i2s-v32.c:268:28: error: 'S3C_GPB5_I2C_SCL' undeclared (first use in this function)
sound/soc/s3c64xx/s3c6410-i2s-v32.c:268:28: note: each undeclared identifier is reported only once for each function it appears in
sound/soc/s3c64xx/s3c6410-i2s-v32.c:269:28: error: 'S3C_GPB6_I2C_SDA' undeclared (first use in this function)
make[3]: *** [sound/soc/s3c64xx/s3c6410-i2s-v32.o] Error 1
make[2]: *** [sound/soc/s3c64xx] Error 2
You do not have the required permissions to view the files attached to this post.
MadRocker
Dev Team
Dev Team
 
Posts: 528
Joined: Sun Dec 12, 2010 7:15 am

Re: 14Jul test kernel

Postby Carlos_Manuel » Sat Jul 16, 2011 1:35 pm

Nice...
If you add Samsung M900/M910 Kernel audio files mic-IN and other audio files and M900/M910 Mic-IN and line-IN text to zImage..
Do you still get the Error or Does it work then... Did you tested it? :)
JétDroid ROMs, stuff... http://code.google.com/p/android-for-jet/
My YT Channel: http://www.youtube.com/user/CarlosJacksonHD
Github: manumanfred
XDA-Devs: Carlos_Manuel

Galaxy Nexus:
ROM: My own ROM 'Dreams', (KTU84P) KitKat 4.4.4
User avatar
Carlos_Manuel
Dev Team
Dev Team
 
Posts: 883
Joined: Tue Mar 29, 2011 11:50 am
Location: Estonia / Finland

Re: 14Jul test kernel

Postby Byeranger » Sat Jul 16, 2011 6:43 pm

The second zImage gives an error while booting , the first zImage works like usual,
Byeranger
Forum Moderator
Forum Moderator
 
Posts: 162
Joined: Thu Oct 21, 2010 3:26 pm
Location: Holland

Re: 14Jul test kernel

Postby MadRocker » Sat Jul 16, 2011 10:04 pm

Carlos the audio we need to add some of the text from that audio files to the Jetkernel MAX8990 then it should fix the mic-in / lin-in error. Only tested it in the 2.6.24 Samsung-s3c6410 and the error is in 2.6.24 "not working on s8000" yet.

Byeranger I think it might be something to do with the JetQi version.
I think I have the Dec JetQi or the Feb full JetQi.
I have seen something similar in some of the newer Jet* platform versions some work or give different output as a result of the JetQi version that is on the phone.

Easiest is to check if you have the /d folder in the ext3 JetDroid after first boot then it should work.
This /d folder is as a side effect of the specific JetQi that we are using, older before Feb JetQi does not have this or this is how I presume it is.

Any other good or bad results in kernel.log or android.log from your testing ?
MadRocker
Dev Team
Dev Team
 
Posts: 528
Joined: Sun Dec 12, 2010 7:15 am


Return to JetKernel Testing

Who is online

Users browsing this forum: No registered users and 1 guest

  • Advertisement
cron