[ROM][Official Nightly][Android 4.4] CyanogenMod 11.0 for SGS4A (int'l)

Search This thread

snadge

Member
Dec 10, 2009
43
56
Note:

This thread started as a discussion for development of a working CM11.0 / KitKat build for GT-I9295 / S4 Active International. At first, with assistance from a CM dev who wishes to remain unnamed and does not want involvement with this, a build was produced for this device, based on work previously done by LeJay on CM10.2. Unfortunately, I have not been able to contact LeJay, which is the primary motivation for starting this thread. Since then, and in a short space of time, xda user @spegelius, has managed to progress this to a fully functional build, which some users are already using as a daily driver.

After much hard work from pretty much everyone except me, it pleases me to write that this device has reached official status, and as such one can obtain nightly builds, updates, and source code, from the official CyanogenMod sources. Congratulations to all involved, and the effort thats been put in to make this happen.

Instructions:

1. Install CWM recovery from TODO: link official CWM here
2. Download the latest official nightly from: http://download.cyanogenmod.org/?device=jactivelte

Left for historic purposes (older pre-official builds): Credit: spegelius: https://drive.google.com/folderview?id=0BzJzDM42pkRvdDR0ZE00UERGU1E&usp=sharing

3. Download CM11.0 gapps from here
4. Boot into recovery by holding the Volume Up button as the phone is booting.
5. Back up your current ROM inside CWM recovery.
6. Flash CyanogenMod ROM to your device using CWM recovery.
7. Flash Google Applications to your device using CWM recovery.
8. Do a wipe data/factory reset from within CWM recovery.
9. Reboot system.

Known Issues:

1. None that I'm currently aware of.
2. Report them. Keeping this part up to date has proven to never actually happen, so maybe just read through the entire thread. Convenient right? ;)

Build from source:

Please consult this guide for setting up CyanogenMod for compile.
Please use
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
when you initialize the CyanogenMod repository so you get the source for CM-11.0.

Run 'repo sync' and compile with 'brunch jactivelte'. Proprietary files you can find on github, or extract them from an existing rom.

This is pretty much a word for word ripoff of LeJay's cm 10.2 post. This is where one would say something like, I take no responsibility if your device explodes, catches fire, invades a foreign nation, causes your cat to get run over by a car, etc.

Thanks goes to LeJay for being pretty much the sole reason a thread was created for this device on XDA, and in turn the people he gave thanks to, primarily the CM team. Additional thanks, of course, goes to spegelius, for running with this thread, and creating something that actually works.
 
Last edited:

spegelius

Senior Member
Mar 29, 2011
779
1,443
Oulu
Interesting, good to hear there's CM dev helping :). I've been playing with the idea of trying to compile CM11 since i got AOSP 4.3 working as daily driver. I'm also using LeJay's work, without it i propably wouldn't even have strated hacking with Android. And i haven't heard from him either, i hope he is okay.
Anyways, my first idea was to try it with same jactiveltexx stuff as cm-10.2 is done and see how far that takes me, but if you have already done it and no display, it's possible that the kenel needs to be updated and newer graphics libs used. Luckily i've done some merging between S4 and S4 Active kernels and i already had a look at CM11 S4 kernel code. There are some changes in the graphics code, so there's a very good possibility to get those merged to Active kernel, to me it looks like S4 and S4 Active have same kernel, except for camera, some gpio stuff and assorted tidbits around the kernel. As for the graphics drivers, i think it should be possible to use libs from S4's CM11 build?

Gotta try this myself later this week :)
 

snadge

Member
Dec 10, 2009
43
56
Anyways, my first idea was to try it with same jactiveltexx stuff as cm-10.2 is done and see how far that takes me, but if you have already done it and no display, it's possible that the kenel needs to be updated and newer graphics libs used. Luckily i've done some merging between S4 and S4 Active kernels and i already had a look at CM11 S4 kernel code. There are some changes in the graphics code, so there's a very good possibility to get those merged to Active kernel, to me it looks like S4 and S4 Active have same kernel, except for camera, some gpio stuff and assorted tidbits around the kernel. As for the graphics drivers, i think it should be possible to use libs from S4's CM11 build?

Gotta try this myself later this week :)
I have tried compiling the stock CM jf common kernel, with s4 active config. SurfaceFlinger fails to initialise EGL libs. I have tried porting LeJay's cm-10.2 active kernel to build on cm11.0, that also fails in the same way. It seems you' are right. The graphics updates for the other s4 devices likely need to be done for active as well, which may require some new props. Jftleatt's props might be worth look at for display props, same cpu/gpu, different lcd panel.. I'm using my phone as a daily, and haven't had much of a chance to test builds.
 

spegelius

Senior Member
Mar 29, 2011
779
1,443
Oulu
I have tried compiling the stock CM jf common kernel, with s4 active config. SurfaceFlinger fails to initialise EGL libs. I have tried porting LeJay's cm-10.2 active kernel to build on cm11.0, that also fails in the same way. It seems you' are right. The graphics updates for the other s4 devices likely need to be done for active as well, which may require some new props. Jftleatt's props might be worth look at for display props, same cpu/gpu, different lcd panel.. I'm using my phone as a daily, and haven't had much of a chance to test builds.

Weel i made a build myself, tweaked the makefiles etc. but there;s a problem: i can't get past the initial text. Something goes wrong about the build and i don't quite know what. I think i'll do a clean repo sync, current source tree is from cm-10.2 and even though repo status says it's clean, i have a feeling something might be wrong with it.

I did some kernel source merging and the build process does build it, so now to get that damn thing to boot...
 

spegelius

Senior Member
Mar 29, 2011
779
1,443
Oulu
Some testing done:

  • clean CM11 repo sync, still no go with cm-10.2 jactive kernel or the one with merges from jf kernel i made. No adb connection, last_kmsg: http://pastebin.com/Nj5rStTc
  • using jf kernel and jactive config, with small mods to get it to build, goes a bit further. Screen turns black after the initial Samsung text, adb connection doesn't show up and no last_kmsg available :confused:

In he last_kmsg above, it seems that the kernel doesn't mount stuff properly or something?
 

spegelius

Senior Member
Mar 29, 2011
779
1,443
Oulu
Finally figured out why i wasn't getting past the initial boot text; a bad formatting in jf-common makefile left almost all of the qcom init files out of the boot.img so no wonder stuff didn't work... :rolleyes: teaches me to proofread stuff...

Ok, now that i got that sorted out, i get it to boot. Display stays back, but loking at the logcat, Surfaceflinger doesn't die. So it seems the problem now is that the panel isn't turned on correctly, but otherwise the thing works, maybe. I'm using a mix of blobs from Active and latest jflte CM11 nighly.

Now i need to go to sauna and drink beer ->
 

spegelius

Senior Member
Mar 29, 2011
779
1,443
Oulu
Hrmm, it seems the stuff responsible for panel is crashing. Last_kmsg: http://pastebin.com/jZyDLcXw

Code:
[   15.869781]  ======== dsi clock dump ++++  =====================
[   15.869781]  0x0130 : 00000005
[   15.869781]  0x0134 : 00000000
[   15.869781]  0x0138 : 00002003
[   15.869781]  0x004c : 00000005
[   15.869812]  0x0050 : 00000000
[   15.869812]  0x0054 : 00000003
[   15.869812]  ======== dsi clock dump ---- =====================
[   15.869842] [<c010badc>] (unwind_backtrace+0x0/0xe0) from [<c0402284>] (mipi_dsi_cmd_dma_tx+0x1a0/0x25c)
[   15.869842] [<c0402284>] (mipi_dsi_cmd_dma_tx+0x1a0/0x25c) from [<c040252c>] (mipi_dsi_cmds_tx+0xa8/0xf8)
[   15.869842] [<c040252c>] (mipi_dsi_cmds_tx+0xa8/0xf8) from [<c0402a78>] (mipi_dsi_cmdlist_tx+0x30/0x48)
[   15.869873] [<c0402a78>] (mipi_dsi_cmdlist_tx+0x30/0x48) from [<c0402be0>] (mipi_dsi_cmdlist_commit+0xd4/0x100)
[   15.869873] [<c0402be0>] (mipi_dsi_cmdlist_commit+0xd4/0x100) from [<c0402cdc>] (mipi_dsi_cmdlist_put+0xd0/0xf4)
[   15.869873] [<c0402cdc>] (mipi_dsi_cmdlist_put+0xd0/0xf4) from [<c04033c4>] (mipi_samsung_disp_send_cmd+0x188/0x1c4)
[   15.869903] [<c04033c4>] (mipi_samsung_disp_send_cmd+0x188/0x1c4) from [<c0403fec>] (mipi_samsung_disp_on_in_video_engine+0x30/0x10c)
[   15.869903] [<c0403fec>] (mipi_samsung_disp_on_in_video_engine+0x30/0x10c) from [<c0404dd0>] (panel_next_late_init+0x38/0x44)
[   15.897583] msm_ta_detect_work: USB exit ta detection - frindex
[   16.067596] mipi_dsi_cmd_dma_tx: dma timeout error
[   16.067596] dumpreg: =============IT's Fail case ==============

Same thing with cm10.2 Active code and code from S4 kernel...
 

mythi

Senior Member
Mar 1, 2013
1,429
2,016
Amman
Hrmm, it seems the stuff responsible for panel is crashing. Last_kmsg: http://pastebin.com/jZyDLcXw

Code:
[   15.869781]  ======== dsi clock dump ++++  =====================
[   15.869781]  0x0130 : 00000005
[   15.869781]  0x0134 : 00000000
[   15.869781]  0x0138 : 00002003
[   15.869781]  0x004c : 00000005
[   15.869812]  0x0050 : 00000000
[   15.869812]  0x0054 : 00000003
[   15.869812]  ======== dsi clock dump ---- =====================
[   15.869842] [<c010badc>] (unwind_backtrace+0x0/0xe0) from [<c0402284>] (mipi_dsi_cmd_dma_tx+0x1a0/0x25c)
[   15.869842] [<c0402284>] (mipi_dsi_cmd_dma_tx+0x1a0/0x25c) from [<c040252c>] (mipi_dsi_cmds_tx+0xa8/0xf8)
[   15.869842] [<c040252c>] (mipi_dsi_cmds_tx+0xa8/0xf8) from [<c0402a78>] (mipi_dsi_cmdlist_tx+0x30/0x48)
[   15.869873] [<c0402a78>] (mipi_dsi_cmdlist_tx+0x30/0x48) from [<c0402be0>] (mipi_dsi_cmdlist_commit+0xd4/0x100)
[   15.869873] [<c0402be0>] (mipi_dsi_cmdlist_commit+0xd4/0x100) from [<c0402cdc>] (mipi_dsi_cmdlist_put+0xd0/0xf4)
[   15.869873] [<c0402cdc>] (mipi_dsi_cmdlist_put+0xd0/0xf4) from [<c04033c4>] (mipi_samsung_disp_send_cmd+0x188/0x1c4)
[   15.869903] [<c04033c4>] (mipi_samsung_disp_send_cmd+0x188/0x1c4) from [<c0403fec>] (mipi_samsung_disp_on_in_video_engine+0x30/0x10c)
[   15.869903] [<c0403fec>] (mipi_samsung_disp_on_in_video_engine+0x30/0x10c) from [<c0404dd0>] (panel_next_late_init+0x38/0x44)
[   15.897583] msm_ta_detect_work: USB exit ta detection - frindex
[   16.067596] mipi_dsi_cmd_dma_tx: dma timeout error
[   16.067596] dumpreg: =============IT's Fail case ==============

Same thing with cm10.2 Active code and code from S4 kernel...

Hi sir ... As my experience with dirt porting ... You have fixed everything in kerenl as I see the issues come from different libs in /system/lib...
JFLTE libs differ a lot from ours ... Some how the screen has to with the GPU driver... I am saying this because I have tried porting a jflte cm 4.3.1 ROM using the old cm 4.3 kernel by Lejay... It booted (yay) but the screen looks orangish the WiFi doesn't work the ril doesn't work ...but replacing the nessary libs from your aosp fixed the issues (the ROM didn't boot here) I've known these details from a small debugging event I made ...

BTW is there a way of building a device tree for 4.4 ?? Wouldn't that make it easier on us ??
 

spegelius

Senior Member
Mar 29, 2011
779
1,443
Oulu
Hi sir ... As my experience with dirt porting ... You have fixed everything in kerenl as I see the issues come from different libs in /system/lib...
JFLTE libs differ a lot from ours ... Some how the screen has to with the GPU driver... I am saying this because I have tried porting a jflte cm 4.3.1 ROM using the old cm 4.3 kernel by Lejay... It booted (yay) but the screen looks orangish the WiFi doesn't work the ril doesn't work ...but replacing the nessary libs from your aosp fixed the issues (the ROM didn't boot here) I've known these details from a small debugging event I made ...

BTW is there a way of building a device tree for 4.4 ?? Wouldn't that make it easier on us ??

Hmm, i was afraid that the GPU drivers would be somehow related to to panel, even though i was thnking that they are separate stuff so if done correctly, one driver doesn't need to stuff that orher driver does...

I did a build with cm10.2 kernel and libs from the AOSP build and suprisingly same results: lcd init fails, Surfaceflinger doesn't die... i need to do more testing with using some qcom stuff from cm10.2 to help pinpointing things.

By device tree do you mean the makefiles etc. like in jf-common? Already done, they are in my github, cm-11.0 branch has been added. No repo for proprietary files yet, though, need to get something working first...
 
  • Like
Reactions: mythi

mythi

Senior Member
Mar 1, 2013
1,429
2,016
Amman
Hmm, i was afraid that the GPU drivers would be somehow related to to panel, even though i was thnking that they are separate stuff so if done correctly, one driver doesn't need to stuff that orher driver does...

I did a build with cm10.2 kernel and libs from the AOSP build and suprisingly same results: lcd init fails, Surfaceflinger doesn't die... i need to do more testing with using some qcom stuff from cm10.2 to help pinpointing things.

By device tree do you mean the makefiles etc. like in jf-common? Already done, they are in my github, cm-11.0 branch has been added. No repo for proprietary files yet, though, need to get something working first...

Why not play with the framebuffer/Screenflinger/ Surfaceflinger in the ramdisk of the kernel i think the init file has to do something for lauching the screen :laugh:

Yes the device tree with all qcom propiretory stuff etc..etc..
 

spegelius

Senior Member
Mar 29, 2011
779
1,443
Oulu
Why not play with the framebuffer/Screenflinger/ Surfaceflinger in the ramdisk of the kernel i think the init file has to do something for lauching the screen :laugh:

Yes the device tree with all qcom propiretory stuff etc..etc..

Yeah, those init files could be causing this. I tried using cm10.2 device tree (jf-common, qcom-common and msm8960) but there's to much changed and getting it to compile would be too much hassle. I'll see about swapping some init files...

Currently for jactive there are LeJay's devicetree, which contains the jactiveltexx and modified jf-common (some proprietary caera files are disabled). I've updated them a bit and added the cm11 branch. In addition, hardware/samsung, qcom-common and msm8960-common are needed, but these have nothing jactive specific, at least not yet...

---------- Post added at 09:40 PM ---------- Previous post was at 09:24 PM ----------

Holy sh*t, i got visual :cool:. Using:
  • cm10.2 jactive kernel
  • cm10.2 jactive blobs
  • hardware/samsung from cm10.2
  • otherwise all cm11 stuff

But now mediaserver crashes and system can't fully boot due to not being able to starte the service. But nevertheless, looking good! Gonna try audio blobs from jflte
 

spegelius

Senior Member
Mar 29, 2011
779
1,443
Oulu
Ok now this is getting plain weird: i can't make a build that has working display anymore. Same sources, nothing is modified. I run brunch as always and the result: no display... wtf? And, if i use the boot.img from the one and only working build with another buil, there's display :silly: :confused:. Me no understand...
 

mythi

Senior Member
Mar 1, 2013
1,429
2,016
Amman
Ok now this is getting plain weird: i can't make a build that has working display anymore. Same sources, nothing is modified. I run brunch as always and the result: no display... wtf? And, if i use the boot.img from the one and only working build with another buil, there's display :silly: :confused:. Me no understand...

Yeah, those init files could be causing this. I tried using cm10.2 device tree (jf-common, qcom-common and msm8960) but there's to much changed and getting it to compile would be too much hassle. I'll see about swapping some init files...

Currently for jactive there are LeJay's devicetree, which contains the jactiveltexx and modified jf-common (some proprietary caera files are disabled). I've updated them a bit and added the cm11 branch. In addition, hardware/samsung, qcom-common and msm8960-common are needed, but these have nothing jactive specific, at least not yet...

---------- Post added at 09:40 PM ---------- Previous post was at 09:24 PM ----------

Holy sh*t, i got visual :cool:. Using:
  • cm10.2 jactive kernel
  • cm10.2 jactive blobs
  • hardware/samsung from cm10.2
  • otherwise all cm11 stuff

But now mediaserver crashes and system can't fully boot due to not being able to starte the service. But nevertheless, looking good! Gonna try audio blobs from jflte


Hahahhaahha... Seams we are getting it near ... Could you post a ksmg/logcat or any thing helpful ...will try to help this has bright future of success if we all join
 
  • Like
Reactions: Netzvagabund

spegelius

Senior Member
Mar 29, 2011
779
1,443
Oulu
Hahahhaahha... Seams we are getting it near ... Could you post a ksmg/logcat or any thing helpful ...will try to help this has bright future of success if we all join

Yeah, here are the last_kmsg and logcat from a build that has display: https://drive.google.com/folderview?id=0BzJzDM42pkRvdDR0ZE00UERGU1E&usp=sharing

I'm uploading the build also and some other last_kmsg's + logcats

Gonna try to create a bootimg with kernel from aosp. I mean, every build i make now doesn't turn the display on. But if i swap the zImage from the only working build, then the build suddenly has display. I also tried building the kernel separately and creating a bootimg with it, no display...

Edit: with aosp zImage, display is shown... so does this mean that the CM11 gcc somehow borks the kernel build? Or wtf? The kernel i'm building has only some filesystem changes vs. aosp kernel...

Edit2: found out why display wan't turning on: when making device tree, i modified BoardConfig.mk to look as much like jfltexx BoardConfig.mk. With that, kernel variant config and kernel config strings switched places. Turns out, in those two kernel defconfig files (jactive_defconfig and cyanogen_defconfig) two different panels are configured. And when configs were switched, the wrong panel config was taken into use... aargh. Damn, i was looking at those lines and thinking if should change them or not...
 
Last edited:
  • Like
Reactions: Netzvagabund

mythi

Senior Member
Mar 1, 2013
1,429
2,016
Amman
Yeah, here are the last_kmsg and logcat from a build that has display: https://drive.google.com/folderview?id=0BzJzDM42pkRvdDR0ZE00UERGU1E&usp=sharing

I'm uploading the build also and some other last_kmsg's + logcats

Gonna try to create a bootimg with kernel from aosp. I mean, every build i make now doesn't turn the display on. But if i swap the zImage from the only working build, then the build suddenly has display. I also tried building the kernel separately and creating a bootimg with it, no display...

Edit: with aosp zImage, display is shown... so does this mean that the CM11 gcc somehow borks the kernel build? Or wtf? The kernel i'm building has only some filesystem changes vs. aosp kernel...

Edit2: found out why display wan't turning on: when making device tree, i modified BoardConfig.mk to look as much like jfltexx BoardConfig.mk. With that, kernel variant config and kernel config strings switched places. Turns out, in those two kernel defconfig files (jactive_defconfig and cyanogen_defconfig) two different panels are configured. And when configs were switched, the wrong panel config was taken into use... aargh. Damn, i was looking at those lines and thinking if should change them or not...


Okay... the translation :D ...The display is now fixed ... the rom boots up ... BUT the media thingy is still fcing and you can't get passed the error :eek:

seems it is more nearer than i thought :cool: will take a look at the files you posted above :angel:

---------- Post added at 06:55 PM ---------- Previous post was at 06:34 PM ----------

could these lines have something to do with the issue we are getting ?

these lines are from kmesg you provided

Code:
[    0.030975] AXI: msm_bus_fabric_init_driver(): msm_bus_fabric_init_driver
[    0.031341] MSM_DCVS: msm_dcvs_early_init: Unable to initialize DCVS err=4
[    0.666229] cont_splash_clk_ctrl: dsi_esc_clk - clk_set_rate failed
[    0.672607] [mdnie lite] start!
[    0.672729] [mdnie lite] end!
[    1.688598] msm8930_audio_init: Not the right machine type
[    1.693145] msm_audio_init: Not the right machine type
[   79.400085] msm_ipc_router_create: Do not have permissions

hmmm...

here are some lines from logcat i noticed

Code:
W/PackageManager(  761): Package com.android.browser desires unavailable shared library com.qrd.useragent; ignoring!
W/PackageManager(  761): Package com.android.gallery3d desires unavailable shared library com.google.android.media.effects; ignoring!
I/PackageManager(  761): Time to scan packages: 0.69 seconds
W/PackageManager(  761): Not granting permission android.permission.WRITE_MEDIA_STORAGE to package com.android.soundrecorder (protectionLevel=18 flags=0x8be45)
W/PackageManager(  761): Unknown permission com.google.android.c2dm.permission.RECEIVE in package com.cyanogenmod.account
W/PackageManager(  761): Not granting permission android.permission.GLOBAL_SEARCH to package com.android.quicksearchbox (protectionLevel=18 flags=0x8be45)
W/PackageManager(  761): Unknown permission com.google.android.gallery3d.permission.GALLERY_PROVIDER in package com.android.bluetooth
W/PackageManager(  761): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH in package com.android.providers.calendar
W/PackageManager(  761): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH.cl in package com.android.providers.calendar
W/PackageManager(  761): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH.mail in package com.android.calendar
W/PackageManager(  761): Not granting permission android.permission.ACCESS_DOWNLOAD_MANAGER to package com.android.browser (protectionLevel=18 flags=0x49be45)
W/PackageManager(  761): Not granting permission android.permission.SEND_DOWNLOAD_COMPLETED_INTENTS to package com.android.browser (protectionLevel=2 flags=0x49be45)
W/PackageManager(  761): Not granting permission android.permission.WRITE_MEDIA_STORAGE to package com.android.browser (protectionLevel=18 flags=0x49be45)
W/PackageManager(  761): Unknown permission com.android.launcher.permission.READ_SETTINGS in package com.android.onetimeinitializer
W/PackageManager(  761): Unknown permission com.android.launcher.permission.WRITE_SETTINGS in package com.android.onetimeinitializer
W/PackageManager(  761): Not granting permission android.permission.BIND_WALLPAPER to package com.android.camera2 (protectionLevel=18 flags=0x58bc45)
W/PackageManager(  761): Unknown permission android.permission.INSTALL_DRM in package com.android.mms
W/PackageManager(  761): Unknown permission com.cyanogenmod.filemanager.permissions.READ_THEME in package com.cyanogenmod.filemanager
W/PackageManager(  761): Unknown permission android.permission.MMS_PUSH in package org.codeaurora.bluetooth
W/PackageManager(  761): Unknown permission com.google.android.gallery3d.permission.PICASA_STORE in package com.android.dreams.phototable
W/PackageManager(  761): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH in package com.android.settings
W/PackageManager(  761): Unknown permission com.android.launcher.permission.READ_SETTINGS in package com.android.settings
W/PackageManager(  761): Unknown permission com.android.launcher.permission.WRITE_SETTINGS in package com.android.settings
W/PackageManager(  761): Unknown permission android.permission.CHANGE_PRIVACY_GUARD_STATE in package com.android.settings
W/PackageManager(  761): Unknown permission com.android.launcher.permission.READ_SETTINGS in package com.cyanogenmod.trebuchet
W/PackageManager(  761): Unknown permission com.android.launcher.permission.WRITE_SETTINGS in package com.cyanogenmod.trebuchet
W/PackageManager(  761): Unknown permission com.google.android.c2dm.permission.RECEIVE in package org.whispersystems.whisperpush
W/PackageManager(  761): Unknown permission com.google.android.googleapps.permission.ACCESS_GOOGLE_PASSWORD in package com.android.development
W/PackageManager(  761): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH in package com.android.development
W/PackageManager(  761): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH.ALL_SERVICES in package com.android.development
W/PackageManager(  761): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH.YouTubeUser in package com.android.development
W/PackageManager(  761): Not granting permission android.permission.DELETE_PACKAGES to package com.svox.pico (protectionLevel=18 flags=0x8be45)
W/PackageManager(  761): Not granting permission android.permission.DEVICE_POWER to package com.android.deskclock (protectionLevel=2 flags=0x48be45)
W/PackageManager(  761): Unknown permission com.android.deskclock.worldclock.permissions.WRITE_DATABASE in package com.android.deskclock
W/PackageManager(  761): Unknown permission android.permission.CANCEL_NOTIFICATIONS in package org.cyanogenmod.voiceplus
V/PackageManager(  761): Disabling com.google.android.gsf/com.google.android.gsf.update.SystemUpdateActivity
W/PackageManager(  761): Unable to disable com.google.android.gsf/com.google.android.gsf.update.SystemUpdateActivity
V/PackageManager(  761): Disabling com.google.android.gsf/com.google.android.gsf.update.SystemUpdateService
W/PackageManager(  761): Unable to disable com.google.android.gsf/com.google.android.gsf.update.SystemUpdateService
V/PackageManager(  761): Disabling com.google.android.gsf/com.google.android.gsf.update.SystemUpdateService$Receiver
W/PackageManager(  761): Unable to disable com.google.android.gsf/com.google.android.gsf.update.SystemUpdateService$Receiver

Edit1:Seems a permissions issue ??
BTW the system loops doing something ...WTF is it ?
 

spegelius

Senior Member
Mar 29, 2011
779
1,443
Oulu
Okay... the translation :D ...The display is now fixed ... the rom boots up ... BUT the media thingy is still fcing and you can't get passed the error :eek:

seems it is more nearer than i thought :cool: will take a look at the files you posted above :angel:

---------- Post added at 06:55 PM ---------- Previous post was at 06:34 PM ----------

could these lines have something to do with the issue we are getting ?

these lines are from kmesg you provided

Code:
[    0.030975] AXI: msm_bus_fabric_init_driver(): msm_bus_fabric_init_driver
[    0.031341] MSM_DCVS: msm_dcvs_early_init: Unable to initialize DCVS err=4
[    0.666229] cont_splash_clk_ctrl: dsi_esc_clk - clk_set_rate failed
[    0.672607] [mdnie lite] start!
[    0.672729] [mdnie lite] end!
[    1.688598] msm8930_audio_init: Not the right machine type
[    1.693145] msm_audio_init: Not the right machine type
[   79.400085] msm_ipc_router_create: Do not have permissions

hmmm...

here are some lines from logcat i noticed

Code:
W/PackageManager(  761): Package com.android.browser desires unavailable shared library com.qrd.useragent; ignoring!
W/PackageManager(  761): Package com.android.gallery3d desires unavailable shared library com.google.android.media.effects; ignoring!
I/PackageManager(  761): Time to scan packages: 0.69 seconds
W/PackageManager(  761): Not granting permission android.permission.WRITE_MEDIA_STORAGE to package com.android.soundrecorder (protectionLevel=18 flags=0x8be45)
W/PackageManager(  761): Unknown permission com.google.android.c2dm.permission.RECEIVE in package com.cyanogenmod.account
W/PackageManager(  761): Not granting permission android.permission.GLOBAL_SEARCH to package com.android.quicksearchbox (protectionLevel=18 flags=0x8be45)
W/PackageManager(  761): Unknown permission com.google.android.gallery3d.permission.GALLERY_PROVIDER in package com.android.bluetooth
W/PackageManager(  761): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH in package com.android.providers.calendar
W/PackageManager(  761): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH.cl in package com.android.providers.calendar
W/PackageManager(  761): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH.mail in package com.android.calendar
W/PackageManager(  761): Not granting permission android.permission.ACCESS_DOWNLOAD_MANAGER to package com.android.browser (protectionLevel=18 flags=0x49be45)
W/PackageManager(  761): Not granting permission android.permission.SEND_DOWNLOAD_COMPLETED_INTENTS to package com.android.browser (protectionLevel=2 flags=0x49be45)
W/PackageManager(  761): Not granting permission android.permission.WRITE_MEDIA_STORAGE to package com.android.browser (protectionLevel=18 flags=0x49be45)
W/PackageManager(  761): Unknown permission com.android.launcher.permission.READ_SETTINGS in package com.android.onetimeinitializer
W/PackageManager(  761): Unknown permission com.android.launcher.permission.WRITE_SETTINGS in package com.android.onetimeinitializer
W/PackageManager(  761): Not granting permission android.permission.BIND_WALLPAPER to package com.android.camera2 (protectionLevel=18 flags=0x58bc45)
W/PackageManager(  761): Unknown permission android.permission.INSTALL_DRM in package com.android.mms
W/PackageManager(  761): Unknown permission com.cyanogenmod.filemanager.permissions.READ_THEME in package com.cyanogenmod.filemanager
W/PackageManager(  761): Unknown permission android.permission.MMS_PUSH in package org.codeaurora.bluetooth
W/PackageManager(  761): Unknown permission com.google.android.gallery3d.permission.PICASA_STORE in package com.android.dreams.phototable
W/PackageManager(  761): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH in package com.android.settings
W/PackageManager(  761): Unknown permission com.android.launcher.permission.READ_SETTINGS in package com.android.settings
W/PackageManager(  761): Unknown permission com.android.launcher.permission.WRITE_SETTINGS in package com.android.settings
W/PackageManager(  761): Unknown permission android.permission.CHANGE_PRIVACY_GUARD_STATE in package com.android.settings
W/PackageManager(  761): Unknown permission com.android.launcher.permission.READ_SETTINGS in package com.cyanogenmod.trebuchet
W/PackageManager(  761): Unknown permission com.android.launcher.permission.WRITE_SETTINGS in package com.cyanogenmod.trebuchet
W/PackageManager(  761): Unknown permission com.google.android.c2dm.permission.RECEIVE in package org.whispersystems.whisperpush
W/PackageManager(  761): Unknown permission com.google.android.googleapps.permission.ACCESS_GOOGLE_PASSWORD in package com.android.development
W/PackageManager(  761): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH in package com.android.development
W/PackageManager(  761): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH.ALL_SERVICES in package com.android.development
W/PackageManager(  761): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH.YouTubeUser in package com.android.development
W/PackageManager(  761): Not granting permission android.permission.DELETE_PACKAGES to package com.svox.pico (protectionLevel=18 flags=0x8be45)
W/PackageManager(  761): Not granting permission android.permission.DEVICE_POWER to package com.android.deskclock (protectionLevel=2 flags=0x48be45)
W/PackageManager(  761): Unknown permission com.android.deskclock.worldclock.permissions.WRITE_DATABASE in package com.android.deskclock
W/PackageManager(  761): Unknown permission android.permission.CANCEL_NOTIFICATIONS in package org.cyanogenmod.voiceplus
V/PackageManager(  761): Disabling com.google.android.gsf/com.google.android.gsf.update.SystemUpdateActivity
W/PackageManager(  761): Unable to disable com.google.android.gsf/com.google.android.gsf.update.SystemUpdateActivity
V/PackageManager(  761): Disabling com.google.android.gsf/com.google.android.gsf.update.SystemUpdateService
W/PackageManager(  761): Unable to disable com.google.android.gsf/com.google.android.gsf.update.SystemUpdateService
V/PackageManager(  761): Disabling com.google.android.gsf/com.google.android.gsf.update.SystemUpdateService$Receiver
W/PackageManager(  761): Unable to disable com.google.android.gsf/com.google.android.gsf.update.SystemUpdateService$Receiver

Edit1:Seems a permissions issue ??
BTW the system loops doing something ...WTF is it ?

I compared the las_kmsg lines to AOSP bootup and those lines are there too, so nothing to worry about (well i hope at least:). It seems that the kernel spits out a lot of 'errors', hard to tell what is important and what not.

And the logcat... well to me it seems that the mediaserver is SIGSEGVaulting every now and then, causing the boot loop because servicemanager can't get all the required services running. Also the permission problems... i saw those with AOSP too, apparently they aren't bad. And do note that i haven't installed gapps, that's a fresh boot after factory reset/rom flash.

Yesterday i made a build with kernel that has most of the stuff from jf merged and with active/jf mix of blobs. Boots ok, until the same mediaserver bootloop. I added some debug to AudioPolicyManager and to my suprise it boots up to the 'Welcome to Cyanogenmod' screen, but com.android.phone keeps FCing and i can't use the phone... :(

Also, god damn Cyanogemod... why does it disable ADB after first boot? It's really frickin nice to get up to this point and then lose all the ability to debug the damn thing!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 33
    Note:

    This thread started as a discussion for development of a working CM11.0 / KitKat build for GT-I9295 / S4 Active International. At first, with assistance from a CM dev who wishes to remain unnamed and does not want involvement with this, a build was produced for this device, based on work previously done by LeJay on CM10.2. Unfortunately, I have not been able to contact LeJay, which is the primary motivation for starting this thread. Since then, and in a short space of time, xda user @spegelius, has managed to progress this to a fully functional build, which some users are already using as a daily driver.

    After much hard work from pretty much everyone except me, it pleases me to write that this device has reached official status, and as such one can obtain nightly builds, updates, and source code, from the official CyanogenMod sources. Congratulations to all involved, and the effort thats been put in to make this happen.

    Instructions:

    1. Install CWM recovery from TODO: link official CWM here
    2. Download the latest official nightly from: http://download.cyanogenmod.org/?device=jactivelte

    Left for historic purposes (older pre-official builds): Credit: spegelius: https://drive.google.com/folderview?id=0BzJzDM42pkRvdDR0ZE00UERGU1E&usp=sharing

    3. Download CM11.0 gapps from here
    4. Boot into recovery by holding the Volume Up button as the phone is booting.
    5. Back up your current ROM inside CWM recovery.
    6. Flash CyanogenMod ROM to your device using CWM recovery.
    7. Flash Google Applications to your device using CWM recovery.
    8. Do a wipe data/factory reset from within CWM recovery.
    9. Reboot system.

    Known Issues:

    1. None that I'm currently aware of.
    2. Report them. Keeping this part up to date has proven to never actually happen, so maybe just read through the entire thread. Convenient right? ;)

    Build from source:

    Please consult this guide for setting up CyanogenMod for compile.
    Please use
    Code:
    repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
    when you initialize the CyanogenMod repository so you get the source for CM-11.0.

    Run 'repo sync' and compile with 'brunch jactivelte'. Proprietary files you can find on github, or extract them from an existing rom.

    This is pretty much a word for word ripoff of LeJay's cm 10.2 post. This is where one would say something like, I take no responsibility if your device explodes, catches fire, invades a foreign nation, causes your cat to get run over by a car, etc.

    Thanks goes to LeJay for being pretty much the sole reason a thread was created for this device on XDA, and in turn the people he gave thanks to, primarily the CM team. Additional thanks, of course, goes to spegelius, for running with this thread, and creating something that actually works.
    13
    Wohoo! I was bit weary about the amount of gerrit emails this morning, but everything went better than expected :). Also the blobs were accepted and now there's a commit about adding jactive to nightlies :victory:
    13
    Success

    Annnd... it works! Cleaning the build are and rebuilding did the trick. Wohoo! :)

    It seems to mostly work, only thing that amiss is missing Camera app. But i haven't done any extensive testing, just installed gapps, logged to my Google account, installed Titanium, restored some apps, listened some music, connected to wifi, 4G.

    Uploading to google, filename cm-11-20140304-UNOFFICIAL-jactiveltexx.zip. And as it says on the original post, HIGHLY Experimental! No warranty whatsoever. But if you install, report bugs.

    The missing camera is propably because current device tree seems to favor building Qualcom camera but as i understand, Active uses different camera. I added the camera sources to the kernel and it seems to be initialized during boot, but something goes worng. Oh well, i've had enough for today
    12
    Aand it's built :). I took the stuff from here: http://xdaforums.com/galaxy-s4/i9505-orig-develop/rom-cyanogenmod-12-t2943934 and modified device files a bit and a booting cm 12.0 is reality. Not big of a suprise since most of the stuff is common between i9505 and i9295. Mostly the same bugs but nice to play around with. I'll make new thread tomorrow, no time today.
    11
    Lolipop ! Cm12

    after countless hours of porting/fixing/digging/searching/hacking i was able to produce a cm12 build for our bevolved s4 active (awesome na :confused:) but waaaait its not booting :( (atleast for the moment) , so what i want from you guys to have a look at the zip and give me some dsmeg/ksmeg love so we can collect as much data as we could , i wont release the build on public so noobs don't hurt there phones :) but if anyone is intersted shoot me a pm :fingers-crossed::fingers-crossed: