[DEV] LG P350 general dev thread - CM 7 & 9 or kernel development - LG Optimus Me P350

THIS THREAD IS FOR DEVELOPERS ONLY!
Please do not post your problems with ROM here.
Post your ideas about working on ICS or CM7 and your problems with compiling sources or similiar.
I posted my p350 sources on github:
https://github.com/pax0r
You will find an instruction how to download mine soruces and compile it by yourself at:
https://github.com/pax0r/android_device_lge_pecan
Here we can speak how to improve this ROM ( 7.2 ) and also how to work on ICS. On my github you can find branch "ics" - it is somehow releated to my work on ICS but it's not complete.
So let's make our device EPIC!

For the begining I will post my problems releated to working on P350:
The problem I have with 7.2 release is that BT is not working - drapalyuk fixed it somehow in last release but I don't know how. If any one have idea what was changed from 1910 to 2010 drap release please let me know!
Also I started to port .35 kernel for our phone - but it's not working yet. Kernel boots and console via adb is usable at this moment but Android itself does not start on it. I will post more in this topic later.

now syncing the source

hi pax0r,
I'm trying to build CM 7.2 using your guide and source code but I notice a couple of issue that maybe create problems to someone beginner like me:
1) if you run ./extract-files.sh on a phone with CM 7.2 (vivekkalady) the extraction will fail on 3 files: libloc-rpc.so, libloc.so, libcommondefs.so. Maybe they are located in a different path.
2) I think this line of code in extract-files.sh is wrong:
Code:
adb pull /system/lib/hw/gralloc.default.so ../../../vendor/$MANUFACTURER/$DEVICE/proprietary/lib/hw/gralloc.default.so
it should be:
Code:
adb pull /system/lib/hw/gralloc.default.so ../../../vendor/$MANUFACTURER/$DEVICE/proprietary/lib/hw/gralloc.pecan.so
to avoid issue later.
I'd like to try to compile ics. What do you think is missing to make it works?
Best Regards,
Gabriele

hi pax0r,
the market crash few times at the begin but after I reboot it seems to be fine.
I attached the logcat.
Gabriele

megasoft78 said:
hi pax0r,
I'm trying to build CM 7.2 using your guide and source code but I notice a couple of issue that maybe create problems to someone beginner like me:
1) if you run ./extract-files.sh on a phone with CM 7.2 (vivekkalady) the extraction will fail on 3 files: libloc-rpc.so, libloc.so, libcommondefs.so. Maybe they are located in a different path.
2) I think this line of code in extract-files.sh is wrong:
Code:
adb pull /system/lib/hw/gralloc.default.so ../../../vendor/$MANUFACTURER/$DEVICE/proprietary/lib/hw/gralloc.default.so
it should be:
Code:
adb pull /system/lib/hw/gralloc.default.so ../../../vendor/$MANUFACTURER/$DEVICE/proprietary/lib/hw/gralloc.pecan.so
to avoid issue later.
I'd like to try to compile ics. What do you think is missing to make it works?
Best Regards,
Gabriele
Click to expand...
Click to collapse
Thanks for your contribute
For me there are no missing libs - I was running it on 7.1 so mby Vivek 7.2 is missing them?
About gralloc - there should be two libraries gralloc.default.so and gralloc.pecan.so
About ICS I have no idea yet and now no time to look at it - studies, work and 7.2 rom is everything I can do at once ;P

pax0r said:
Thanks for your contribute
For me there are no missing libs - I was running it on 7.1 so mby Vivek 7.2 is missing them?
About gralloc - there should be two libraries gralloc.default.so and gralloc.pecan.so
About ICS I have no idea yet and now no time to look at it - studies, work and 7.2 rom is everything I can do at once ;P
Click to expand...
Click to collapse
I think the problem about missing libs is related with vivek 7.2 rom.
it's strange but I can't see gralloc.pecan.so. Anyway I'll check it this evening.
I was able to build everything using your tutorial but now I want to try with ICS. I need a bit of searching on internet.
Thank you for your work,
Gabriele

Hm I've checked it and it fact there were no gralloc.pecan in extract - it was obviously a bug, I pulled everything from device, then I was making some refactoring and I didnt check it after that. I will push commit with fixes today.
Thanks for pointing it!

I see a keylayout headset push, how did you make the headset button works? I replaced both keylayout (qwerty with the haptic fix and 7k), but the dammed button still with problems =/
Thanks
PD: The new implementation of gralloc will fix the dammn warning of prelink? (on the log)

I'm not sure if this keylayout will make headset work as I don't have one but it was suggested that it may help but this need test. New gralloc is because it is open source comparing to the original propriety one and I'm testing its speed - it is at least the same so I will leave it
To solve a problem with prelink there should be a prelink.map created but I dont know exatly how to build one. It is not a critical error but with prelink.map the boot process could be faster.
I still didnt fixed copybit ;/
If you have some idea how to help refer to this post:
http://forum.xda-developers.com/showpost.php?p=21592280&postcount=28
EDIT: copybit fixed
hey could some one with the headset use this app:
https://market.android.com/details?id=aws.apps.keyeventdisplay
click headset buttons few times and post output of this app (if any)?
BTW do the headset buttons works on Vivek ROM?

Let me compile it with the new changes and I will try
At least, I'm currently using 7.1.0 (your 7.1.0) and nothing happens. (EDITED)

call\music button problem
paxor can u rectify the call\music button for wired headset

Can you compile ICS with your new files and send it to me ??
I will try to port ICS with your new files

Hey pax0r, are you sure with the fix? Compiled, installed... but I get a weird screen on menu =S
Thanks

I get a minor success at porting .35 kernel for p350. It boots and works but it still to bugged to public release. However if you have any dev experience you can grab it here https://github.com/pax0r/lge-kernel-msm7x27 and help me fix it!

I don't know exactly how Android handles GUI, IDK how to help right now, but I just can told you about the bug when android it's displaying interface.

Can you upload your compiled ICS so that we can tweak it to get it working!

I've removed my built version and now my source code wont even build :/

Hi Pax0r! well, i want to become a dev, i have some kind of linux knowledgement and have a good willing to learn, could you please point me out to some basic tutorials about building from cyanogen source? i've searched myself in the wiki but i didnt saw anything about lg pecan, any information you can give me, I will study it and maybe then become of help in dev community! thanks in advance!!

There is not much info about anything for P350 as it is not very popular device. Everything you need to start building CM for P350 is here, in mine Readme file:
https://github.com/pax0r/android_device_lge_pecan/blob/gingerbread/README.mkdn
Everything else you need to get by yourself =p but I will try answer all your questions
I learned everything by checking avaibale info for similar devices (MSM7227 board, for example: LG P500, ZTE Blade) and source codes.

Related

[ROM][11/24/2011] UNOFFICIAL CM7 G2/Vision Kang's Built from Source

This thread is for everyone who compile's Cyanogenmod Kang build's from source and would like to post/share with everyone. If you want your build included in this post just pm me and I will update this post asap.
Warning these are unofficial CM7 build's (with myself cherry-picking comments from CM's Gerrit for testing) which may have unfinished mods and/or broken code that is continually changing, ONLY THOSE WHO KNOW WHAT THEY ARE DOING SHOULD FLASH THEM. Don't file bug reports on the Cyanogenmod issue tracker from any of these build's. Please don't bother cyanogen or #teamdouche as you have been warned these build's are unofficial and come with no support except on this thread. If you have any question's try searching as your question might have been already asked and answered. Note: I, nor is anyone else is/are responsible for any bricks or problems you may encounter.
I no longer have a G2 as I gave it to my mom, but will update this periodically. Sorry for the delay I have been super busy with the move, my new job and fixing this house I am now living in.
All credit goes to cyanogen & #teamdouche, thank them not me as all I do is compile
Items from CM's Gerrit that I cherry-picked:
* Give me time
Last Commit repo synced before building-
* Enable access to Audio Effects Settings
I understand that this build is unofficial and I take no responsibility if you brick your phone- Will be update in about an hour and half as I plan on running it when I get home
Please visit @cmsrc, CM's Gerrit or Nightly Device Changelog for a complete list of changes or commits.
Also those who don't know a Kang is an unofficial nightly that someone builds from CM's github.
I will update this post as often as needed to stay current or change as necessary.
Hey everyone, here are the kangs and cherry picks that i will be providing. I want to thanks plasmadragon007 for allowing me to post here.
Everything in the above post applies to here. We will most likely be making these at a different time of day with possible different commits. I do not own a g2 but i do have a couple of decent guys willing to test each kang before posting. If they are not available, i will let you know that the build has not been tested. I do this because i enjoy it and want to. I hope you enjoy it also.
All credit goes to cyanogen & #teamdouche.
Items from CM's Gerrit that I cherry-picked:
Lockscreen background http://goo.gl/5p5Np
you can find my builds on Euroskank http://goo.gl/U7xx6
Hey Guys,
I figured i would share this.
All credit goes to cyanogenmod team. and cyanogen for being a killer coder
All Builds + recoveries can be found here. I have included a date + md5sum
http://xdafiles.net/rhcp/
More Builds/Gapps can be found here:
gridlock32404 - cm7rc0 built by gridlock will be http://www.crackflashers.com/ cause of dropbox excessive traffic, will build new ones tonight if new commits
I uploaded it just now.
You will need to flash CWRecovery 3.0+. Which can be found at
http://xdafiles.net/rhcp/
This has been all built from source.
You need to put your phone in fastboot.
1) fastboot flash recovery recovery.img
2) reboot into recovery
3) backup your current rom
4) adb push the zip
5) flash the zip
As for gapps I can not post any gapps here. (Hint Paul obrians dump of the nexus S)
Notes: I am not responsible for any bricks or problems you may encounter I am just sharing this. If you follow the step you will have 2.3.1 on your phone.
Please help the devs who put this togther for us. fix some bugs. If you know how.
so far, It seems the video has been fixed up a bit. and the wifi works. So, Far the only thing not working video cam. (which is under works so i hear)
Also. Protected apps do not show since this is 2.3.1 (You can fix this by modding your build.prop or wait for google to add 2.3.1)
Thanks and I hope you enjoy this. Please someone mirror the build. I dont think mediafire will keep it up.
If you want to see protected apps. You need to edit your build.prop in system with the following:
Code:
ro.build.description=soju-user 2.3 GRH55 79397 release-keys
ro.build.fingerprint=google/soju/crespo:2.3/GRH55/79397:user/release-keys
This is built from current src as of 30 mins ago.
So, there is a few video fixes and others.
You can read the updates at: http://r.cyanogenmod.com/#q,status:merged,n,z
I appreciate it man. I just moved and I don't have an internet connection yet. It's hard to repo sync on a 1mbps Android tether.
Is there any difference between this one and the other one?
Sent from my HTC Vision using XDA App
smjfosho said:
Is there any difference between this one and the other one?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
This one is more recent, with the newest commits.
Is your link supposed to point to recovery.img?
bivio said:
Is your link supposed to point to recovery.img?
Click to expand...
Click to collapse
Thanks. I mistyped fixed now.
Camcorder still borked?
rhcp0112345 said:
Hey Guys,
I figured i would share this.
All credit goes to cyanogenmod team. and cyanogen for being a killer coder
The rom can be found at: http://www.mediafire.com/?15l284rnq1zjt1h
I uploaded it just now.
You will need to flash this with CWR 3.0. Which can be found at
http://mrcellphoneunlocker.com/recovery.img
This has been all buit from source.
You need to put your phone in fastboot.
1) fastboot flash recovery recovery.img
2) reboot into recovery
3) backup your current rom
4) adb push the zip
5) flash the zip
As for gapps I can not post any gapps here. (Hint Paul obrians dump of the nexus S)
Notes: I am not responsible for any bricks or problems you may encounter I am just sharing this. If you follow the step you will have 2.3.1 on your phone.
Please help the devs who put this togther for us. fix some bugs. If you know how.
so far, It seems the video has been fixed up a bit. and the wifi works. So, Far the only thing not working video cam. (which is under works so i hear)
Also. Protected apps do not show since this is 2.3.1 (You can fix this by modding your build.prop or wait for google to add 2.3.1)
Thanks and I hope you enjoy this. Please someone mirror the build. I dont think mediafire will keep it up.
Click to expand...
Click to collapse
the link to the recovery img is broken because it says reovery not recovery
Im in no rush. Im just going to wait for the cyanogenmod team to fully finish it & wait for RC1.
Vandale said:
Im in no rush. Im just going to wait for the cyanogenmod team to fully finish it & wait for RC1.
Click to expand...
Click to collapse
Sure your not Thats why your watching these threads like everyone else, including me!!
Downloading now, Thanks for the build!
Been waiting for this all day. Thank you!
[ROM]cm7 gingerbread flavor
[Recovery]clockwork 3.0.0
Glad everyone likes.
My pleasure
Sent from my HTC Vision using XDA App
do you know if usb issue was addressed in this build
Have not tested it. Nor do I see any commits. So I assume same issue.I don't mount usb so doesn't bother me. I use adb
Sent from my HTC Vision using XDA App
is the "unknown" thing still showing up in phone number? its the only thing keeping me from sticking with Gingerbread @[email protected] silly, i know.
having problem flashing the img help
I get an assert failed error trying to flash the ROM, too bad I was really looking forward to trying CM7 .
cough..... cough http://forum.xda-developers.com/showpost.php?p=10083640&postcount=151 cough..... cough... man I'm really sick

Compile CM9 with CMParts included

Hi all,
I've managed to properly build CM9 so far, but I noticed somehow CM settings aren't included. Does anyone know how to add this to the build? What I tried so far:
Downloaded the source files for CMParts from CM github, placed them in /packages/apps/CMParts/ and added CMParts to the core.mk file in build/../.
It starts compiling, but always returns an error complaining about deprecated API's.
Hope someone can give some advice here! Been searching like crazy the past few days, but cannot seem to find the answer. Thanks in advance...
(oh, and while I'm at it: after a build I have to manually add a couple of libs to /system/vendor/firmware/ -bcm4330 and some others-. Is there anyway to include them in the source so that they are automatically added? Thanks! )

AOKP ICS preprepre alpha

This is a very pre-alpa build of AOKP ROM.Known serious issue are h/w buttons,not all are working correctly,use onscreen ones.More functional update will be very soon
Credits
Goes to everybody working on ICS for hero and heroc
P.S I took updater-script from HeroICS ROM,hope guys wouldn't shot me
http://www.mediafire.com/?2qb7fk2w8dyiibw
:/
ported from where? more details..
1ceb0x said:
:/
ported from where? more details..
Click to expand...
Click to collapse
This one is ported from WFS,now compiling new wersion from sources
not bad few issues\recommendations after installing:
Max speed of 710 is a bit keen (default of 691 ?)
Recommend latest Nova Launcher (1.2 - lots of bug fixes)
SuperSU rather than SuperUser
Remove pointer following boot-up
Updater script saying installing CM 4.0.3 needs edit as 4.0.4 is installed ...
Advise that gapps are not included
Please dont take this as criticism, I certainly couldn't do this (tho i might have a bash somepoint)
I'd be happy to be guinea pig for testing further builds if you'd to pm me.
awesome! glad to see you guys have an aokp port now.
about the hardware buttons, wouldnt that have to do with the /usr folder? try to replace key layout related stuff with ones from heroics, and it should work.
if you need any help let me know
Download link not work correct..and one question if i understand good this is new port from new HTC Desire C ROM....ICS 4.0.4?
Thanks
P.S.Good will be to make your tread with more exact info like ROM version images from phone,change log and e.g
What works and what not?
jogai said:
What works and what not?
Click to expand...
Click to collapse
Hardware buttons except for menu, home and back (correct me if I'm wrong) don't work. However Keynrtracker (or check here for more information and keynrtracker.apk) resolves all the buttons. The problem doesn't seem to rely in /system/usr/keylayouts, but somewhere else.
Haven't had time to try this ROM out any further.
Build now maintained under:
http://forum.xda-developers.com/showthread.php?t=1795990

SU640/P930/VS920 Bringup for 3.4 jb kernel

This thread is for developers to discuss bringup for the 3.4 jb kernel on various devices in the Nitro HD "iproj" family. These include P930, SU640, VS920, and LU6200.
Downloaded the su640 jb sources and compiled for ijb_skt. Tried to boot on my "gimpy" p930. No boot.
Enabled console framebuffer and snapped a pic just before reboot. It's complaining about fatal regulator error (msm_rpm_err_fatal). Anyone else get this far and/or see anything similar?
If anyone wants to use a console framebuffer, here's how:
1. Enable CONFIG_FRAMEBUFFER_CONSOLE and CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY.
2. Modify console_setup() in kernel/printk.c. Delete the function body and replace it with just "return 1".
Be prepared with a camera to snap an image of the screen before it reboots.
tdmcode said:
Downloaded the su640 jb sources and compiled for ijb_skt. Tried to boot on my "gimpy" p930. No boot.
Enabled console framebuffer and snapped a pic just before reboot. It's complaining about fatal regulator error (msm_rpm_err_fatal). Anyone else get this far and/or see anything similar?
If anyone wants to use a console framebuffer, here's how:
1. Enable CONFIG_FRAMEBUFFER_CONSOLE and CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY.
2. Modify console_setup() in kernel/printk.c. Delete the function body and replace it with just "return 1".
Be prepared with a camera to snap an image of the screen before it reboots.
Click to expand...
Click to collapse
Working on bringing this up for the vs920 as that's the only one I've got.
So far I've copied the ijb_skt bits over to ijb_vzw and used a bit of grep/sed magic to replace the skt bits to vzw in the files, and add ||'s for ijb_vzw wherever ijb_skt was a condition. I'm getting successful builds But they won't boot (yet). I'll keep you updated. I'll be pushing to here as I make any changes/progress.
Got past the RPM error with a hack.
In arch/arm/mach-msm/clock.c @ clock_late_init(), remove the list_for_each_entry_safe block.
Obviously, this is just a hack. We need to figure out what's causing the issue.
Next up is the display. The kgsl driver in this kernel does not match the kgsl libs in CM10. I'm going to download the 4.1 flashable rom from this forum and see if I can update the drivers to match.
I think kgsl is happy now. Next up is the msm video driver.
tdmcode said:
I think kgsl is happy now. Next up is the msm video driver.
Click to expand...
Click to collapse
Man, You're a machine... Here I'm still trying to get something that'll boot past the LG logo lol
Got boot animation and home screen. Then it reboots after a minute or so. The shell in adb gets really laggy right before reboot. Likely causes are a kernel hardware driver failing somewhere or a massive memory leak.
I see touch events logged but by the time the home screen shows I think it's too far gone to act on them. Same with hard buttons and capacitive buttons.
Oh .. by the way I'm using CM10 not CM10.1. It matches better since it's a 4.1 kernel.
Gotta stop for the day. Here's what I've got so far...
http://androidrepo.net/roms/quattrimus/iproj/iproj-3.4-checkpoint1.diff
tdmcode said:
Oh .. by the way I'm using CM10 not CM10.1. It matches better since it's a 4.1 kernel.
Gotta stop for the day. Here's what I've got so far...
http://androidrepo.net/roms/quattrimus/iproj/iproj-3.4-checkpoint1.diff
Click to expand...
Click to collapse
Nevermind. I thought the link I just posted was for someone working on another 3.4 kernel... it wasnt.
*Edit*
I'm obviously doing something horribly wrong by trying to borrow/reuse the ijb_skt files, because I can't get a kernel that even tries to boot (gets off the first LG logo)... and don't really have the know-how to reconstruct the files.
Didn't get a chance to work on this today I was busy on another project. But I'll be back on it Monday for sure.
@Yoinx: you are going to have a harder time with the vs920 because the hardware is different and it won't boot the su640 kernel.
I do not know the approach of developing cm10 kernel from stock kernel.
According to miroslav_mm,
http://forum.xda-developers.com/showpost.php?p=42075037&postcount=40
I tried using stock 3.4 zImage + cm10 ramdisk + required libs. It boots with blackscreen
lyfkevin said:
I do not know the approach of developing cm10 kernel from stock kernel.
According to miroslav_mm,
http://forum.xda-developers.com/showpost.php?p=42075037&postcount=40
I tried using stock 3.4 zImage + cm10 ramdisk + required libs. It boots with blackscreen
Click to expand...
Click to collapse
You need to change the kgsl and msm video code to match cm10. See my patch.
tdmcode said:
You need to change the kgsl and msm video code to match cm10. See my patch.
Click to expand...
Click to collapse
The boot.img provided by @navik
Same approach, i.e. stock zImage + cm10 ramdisk
I can boot into home screen with my su640 now.
Signal, wifi work.
but laggy, blinking screen(check hw overlay setting in option can fix), no sound, no bootanimation (black screen)
----------------------------------------------------
edit:
Merged your patch
able to see boot animation
Sent from my LG-LU6200 using xda premium
LU6200 jb source is released
https://wws.lg.com/global/support/opensource/opensourceList?types=ALL&search=lu6200
lyfkevin said:
I do not know the approach of developing cm10 kernel from stock kernel.
According to miroslav_mm,
http://forum.xda-developers.com/showpost.php?p=42075037&postcount=40
I tried using stock 3.4 zImage + cm10 ramdisk + required libs. It boots with blackscreen
Click to expand...
Click to collapse
I finished my new build CM10, on 3.4 kernel, with new JB camera libs, and other new properitary stuff. Dont have any problem with 3.4 kernel on CM10 (4.1.2), I didnt patch any KGSL driver, sources from my Github working, it dont have last updates but it working. I cant upload new ROM for test now, I dont have internet at home, when I fix my provider I will upload it.
lyfkevin which display libs did you use? Did you complete build CM10 with new kernel and headers?
Take this variant:
1.) display libs: copybit.msm8660.so, gralloc.msm8660.so, hwcomposer.msm8660.so, libgenlock.so, libhwcexternal.so, libhwcservice.so, libmemalloc.so, libqdutils.so, libtilerenderer.so, and libqdMetaData.so take from official STOCK 4.1 + take Adreno libs with MetaData support from my last CM10 or from STOCK 4.1 (older version) = its working on CM10
miroslav_mm said:
I finished my new build CM10, on 3.4 kernel, with new JB camera libs, and other new properitary stuff. Dont have any problem with 3.4 kernel on CM10 (4.1.2), I didnt patch any KGSL driver, sources from my Github working, it dont have last updates but it working. I cant upload new ROM for test now, I dont have internet at home, when I fix my provider I will upload it.
lyfkevin which display libs did you use? Did you complete build CM10 with new kernel and headers?
Take this variant:
1.) display libs: copybit.msm8660.so, gralloc.msm8660.so, hwcomposer.msm8660.so, libgenlock.so, libhwcexternal.so, libhwcservice.so, libmemalloc.so, libqdutils.so, libtilerenderer.so, and libqdMetaData.so take from official STOCK 4.1 + take Adreno libs with MetaData support from my last CM10 or from STOCK 4.1 (older version) = its working on CM10
Click to expand...
Click to collapse
is your 3.4 kernel compatible with your previous cm10 builds? a lot less MBs, easier to upload.
tdmcode said:
This thread is for developers to discuss bringup for the 3.4 jb kernel on various devices in the Nitro HD "iproj" family. These include P930, SU640, VS920, and LU6200.
Click to expand...
Click to collapse
Exece me,I want to build aosp of su640 based on LG offical open sourse. I have try serverl times,but end with failure.
Should you give me some advices or guide? Thanks for your reply!
navik said:
Exece me,I want to build aosp of su640 based on LG offical open sourse. I have try serverl times,but end with failure.
Should you give me some advices or guide? Thanks for your reply!
Click to expand...
Click to collapse
You cannot do this. There are many changes to files which are not gpl .
It takes a lot of work to make an aosp ROM. You need most of the cm hardware changes and various other changes through the system. I have done it for 4.1 with only one bug: the front camera does not work. I have not tried with 4.2 yet.
tdmcode said:
You cannot do this. There are many changes to files which are not gpl .
It takes a lot of work to make an aosp ROM. You need most of the cm hardware changes and various other changes through the system. I have done it for 4.1 with only one bug: the front camera does not work. I have not tried with 4.2 yet.
Click to expand...
Click to collapse
Thanks,but I want to build aosp based on LG open sourse instead of porting.
Do you have read the guide of LG offical open sourse?It say we can build stockrom based on LG official open sourse and Google android open sourse,we just need to copy LG open sourse into android open sourse. then breakfast and lunch.but I fail,I think I didn't pick up the guide of LG open sourse 。Do you have some good advices?Thanks again!
Sent from my LG-SU640 using xda premium

[ROM][Unofficial/Experimental][Android 4.3] CyanogenMod 10.2 for SGS4A (int'l)

-------------------------Warning!-------------------------------------
This ROM is for SGS4A (int'l) ONLY. Does not work on SGS4 from AT&T as it has a locked bootloader.
Please refer to this thread for a bounty on the bootloader.
-------------------------Please note---------------------------------
This is an experimental build of CyanogenMod 10.2 running Android 4.3.
Meaning there's a couple of known issues with the camera. It is my hope these will be sorted out over time.
If anyone has any interest in helping out, please PM me. Or simply fork the code if you want.
-------------------------Instructions---------------------------------
Install CWM recovery from here.
Download most recent ROM from here.
Download most recent Google Applications for Android 4.3 from here.
Boot into recovery by holding the Volume Up button as the phone is booting.
Back up your current ROM inside CWM recovery.
Flash CyanogenMod ROM to your device using CWM recovery.
Flash Google Applications to your device using CWM recovery.
Do a wipe data/factory reset from within CWM recovery.
Reboot system
---------------------------Known issues-----------------------------
Several camera functions such as HDR don't work.
---------------------------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-10.2
when you initialize the CyanogenMod repository so you get the source for CM-10.2.
Download roomservice.xml (see below) and put in ~/android/system/.repo/local_manifests/.
Run 'repo sync' and compile with 'brunch jactiveltexx'. You can get the proprietary files from the ROM.
As always, I take no responsibility in case your phone blows up.
And thanks to the CM team for all their hard work.
Downloads
---------------------------CM-10.2 ROM (Android 4.3) -------------------
---------------------------cm-10.2-20130917-----------------------------------
CyanogenMod 10.2 - 20130917
CyanogenMod 10.2 - 20130917 (mirror - thanks to mrvovven)
---------------------------cm-10.2-20130910-----------------------------------
CyanogenMod 10.2 - 20130910
CyanogenMod 10.2 - 20130910 (mirror - thanks to mrvovven)
---------------------------CM-10.1 ROM (Android 4.2.2) ----------------
CyanogenMod 10.1 - 20130810
----------------------------Google apps -------------------------------
Download the official Google apps. Need to download this in order to have apps like Google Play.
For CM-10.1 choose Android 4.2 apps.
For CM-10.2 choose Android 4.3 apps.
http://goo.im/gapps
------------------------------------- KERNELS ---------------------------------
- SGS4A android 4.2.2 kernel for CM10.1
https://www.dropbox.com/s/oo1hr2n6evp3zu9/sgs4a-cm10-1kernel.zip
----------------------- Changelog--------------------
-------CyanogenMod 10.2 - 20130917----------
- Fixed video preview resolution
- Disabled zsl for slightly more stable camera app.
-------CyanogenMod 10.2 - 20130910----------
- Updated kernel to most recent version of cm-10.2 for SGS4.
- Replaced all sensor drivers with SGS4A kernel sources.
- Replaced several camera blobs in /system/lib/* with SGS4A versions enabling basic camera functionality.
-------CyanogenMod 10.1 - 20130810----------
Initial build.
Good job.
Sent from my Nexus 7 using Tapatalk 4
hello
anyone tried this out ?
feedbacks ?
thanks in advance
pdf5 said:
hello
anyone tried this out ?
feedbacks ?
thanks in advance
Click to expand...
Click to collapse
This is not something you should install unless you want to be compiling and debugging yourself. It's far from usable as day to day rom. I hope I'm clear on that.
Fixed wifi and a number of small issues. Should be a lot more stable. Seems the main remaining issue is, not surprisingly, the camera. If anyone knows how the entire camera driver setup is supposed to work in android, I'd love some help
LeJay said:
Fixed wifi and a number of small issues. Should be a lot more stable. Seems the main remaining issue is, not surprisingly, the camera. If anyone knows how the entire camera driver setup is supposed to work in android, I'd love some help
Click to expand...
Click to collapse
Call it just a hunch. But have you tried the camera drivers from the s3 ? I would say that it's basically the same camera and has been added in s4 active because after 1 year it became very cheap to continue manufacturing and this way compensate for the more expensive case and water proofing.
aurelm said:
Call it just a hunch. But have you tried the camera drivers from the s3 ? I would say that it's basically the same camera and has been added in s4 active because after 1 year it became very cheap to continue manufacturing and this way compensate for the more expensive case and water proofing.
Click to expand...
Click to collapse
Honestly, not exactly sure how the setup is. I assume it's mostly in some proprietary libs separate from the kernel, but it's hard to find good information on it.
Sent from my GT-I9295 using xda premium
Thank you for you work!!
But search another File hoster!! DropBox close your account if the trafic is to big!!
So S4 Active Original is the intl i9295 ?
EDIT: oh ok the real dev thread
Sent from my GT-I9295 using xda app-developers app
I've a MicroSD in my SGS4A and i can't choose the external_sd in the CM File Explorer.
Is there any solution?
For example creating symlink or mounting in /sdcard
I've never tried anything of that!
It's working really well Wifi works yay, well done! Hopefully you can get the camera working too.
Building from source
Hi,
I'm happy to see such great progress already, and am only diving in to this because I'd like to be able to lend a hand in any way I can.
Is it too soon to be asking questions about how to build for 10.2? I'm having a go at it right now, and if I use Lejay's kernel and device configuration (jactivelte), the kernel fails to compile, something about BUG_ON rcu error, I can come back to that if its relevant. So I tried Epsylon3's suggestion to use tpruvot's kernel and device config. This builds a rom, but black screen, can't see anything or get into adb. If I flash Lejay's kernel over the top of my 10.2 build, it boots. Phone (dialer) keeps force closing in a loop, which is annoying, but asides from that it seems to boot.
Keep up the good work, can't wait to get some 10.2 love.
snadge said:
Hi,
I'm happy to see such great progress already, and am only diving in to this because I'd like to be able to lend a hand in any way I can.
Is it too soon to be asking questions about how to build for 10.2? I'm having a go at it right now, and if I use Lejay's kernel and device configuration (jactivelte), the kernel fails to compile, something about BUG_ON rcu error, I can come back to that if its relevant. So I tried Epsylon3's suggestion to use tpruvot's kernel and device config. This builds a rom, but black screen, can't see anything or get into adb. If I flash Lejay's kernel over the top of my 10.2 build, it boots. Phone (dialer) keeps force closing in a loop, which is annoying, but asides from that it seems to boot.
Keep up the good work, can't wait to get some 10.2 love.
Click to expand...
Click to collapse
Comparing the 9295 and 9505 kernels, there's quite a lot of differences. Cyanogenmod tried to merge the two, but apparently gave up. The question is really if we should start with the 9505 and add the camera or start with the 9295 and make it compatible for CM. The stuff i uploaded here is a port of the 9505 kernel, but now I'm looking into starting out with the 9295 kernel instead.
The problem with 10.2 is of course there's no released 9295 kernel for android 4.3. I'm guessing there are not that many differences, so it might not be too hard.
I think I'm getting the same compile error you were with 10.2. Not sure what it means.
Are you going to try to make CM 10.2?
LeJay said:
Comparing the 9295 and 9505 kernels, there's quite a lot of differences. Cyanogenmod tried to merge the two, but apparently gave up. The question is really if we should start with the 9505 and add the camera or start with the 9295 and make it compatible for CM. The stuff i uploaded here is a port of the 9505 kernel, but now I'm looking into starting out with the 9295 kernel instead.
The problem with 10.2 is of course there's no released 9295 kernel for android 4.3. I'm guessing there are not that many differences, so it might not be too hard.
I think I'm getting the same compile error you were with 10.2. Not sure what it means.
Click to expand...
Click to collapse
I had a chat with noobnl about it, and he pointed out a patch on gerrit: http://review.cyanogenmod.org/#/c/44552/
I spent hours manually merging it with cm jf kernel, to finally end up with a kernel that gives me. You guessed it, a black screen. After investing about a days worth of effort into it, I ended up with a buggy unstable CM10.2 build, that will boot if I flash LeJay's kernel zip, but its unuseable. It's going to take some serious effort to come up with a functioning CM10.2 kernel for the International S4 Active. In the meantime, a CM10.1 build with a non functioning camera, is still way better than the stock TouchWiz rom, so I'm happy. :laugh:
Ok, I got bored and had another play around with 10.2 and the CM jf kernel. With the black screen problem, if you power the device down, then boot into recovery (power + vol up), you can adb pull /proc/last_kmsg and it tells an interesting story. It looks like the init scripts are totally borked. init.qcom.rc and init.carrier.rc are completely missing. I tried simply copying them into the root, but it looks like its a bit more complicated than that. The problem is clear that it is unable to mount /system for whatever reason, because it can't find /system/bin/sysinit, then pretty much gives up after that.
This looks like a pretty simple problem for a relatively experienced device maintainer, or rom kernel dev to be able to fix. It would be nice if we could get some more developer attention for this device.
snadge said:
Ok, I got bored and had another play around with 10.2 and the CM jf kernel. With the black screen problem, if you power the device down, then boot into recovery (power + vol up), you can adb pull /proc/last_kmsg and it tells an interesting story. It looks like the init scripts are totally borked. init.qcom.rc and init.carrier.rc are completely missing. I tried simply copying them into the root, but it looks like its a bit more complicated than that. The problem is clear that it is unable to mount /system for whatever reason, because it can't find /system/bin/sysinit, then pretty much gives up after that.
This looks like a pretty simple problem for a relatively experienced device maintainer, or rom kernel dev to be able to fix. It would be nice if we could get some more developer attention for this device.
Click to expand...
Click to collapse
You probably forgot to add jactivelte to the list at the bottom of device/jf-common/Android.mk. I didn't want to fork their repo just to add one word on a line, so you have to do this manually. It's probably also a good idea to extract rom files from a cm.10.2 rom for something like jfltexx.
LeJolly said:
Are you going to try to make CM 10.2?
Click to expand...
Click to collapse
I have cm10.2 running. The problem is really the camera.

Categories

Resources