Related
Hello I'm trying to compile cyanogenmod 7 with subskyper tass device to try to mantain this project update in line with the original philosophy: keep it 100% cyanogenmod without any tweaks
When I compile I face two errors that broke my compilation:
1-
device/samsung/tass/overlay/frameworks/base/core/res/res/values/config.xml:95: error: Resource at swap_volume_keys_orientation appears in overlay but not in the base package; use <add-resource> to add.
make: *** [out/target/common/obj/APPS/framework-res_intermediates/package-export.apk] Errore 1
make: *** Eliminazione del file "out/target/common/obj/APPS/framework-res_intermediates/package-export.apk"
make: *** Attesa per i processi non terminati....
This one I commented out the line reguarding swap_volume_keys_orientation in file
device/samsung/tass/overlay/frameworks/base/core/res/res/values/config.xml
but when i continue...
2-
prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld: out/target/product/tass/obj/SHARED_LIBRARIES/libandroid_runtime_intermediates/AndroidRuntime.o: in function android::gRegJNI:AndroidRuntime.cpp(.data.rel.ro+0x148): error: undefined reference to 'register_android_hardware_fm_fmradio(_JNIEnv*)'
collect2: ld returned 1 exit status
make: *** [out/target/product/tass/obj/SHARED_LIBRARIES/libandroid_runtime_intermediates/LINKED/libandroid_runtime.so] Errore 1
make: *** Attesa per i processi non terminati..
Someone faced same problems?
Any ideas?
thanks a lot
Send PM With The Error To Subpsyke
t-r-e said:
Send PM With The Error To Subpsyke
Click to expand...
Click to collapse
done. I hope he will answer me cause I'm able to sync repos in a couple of hours, so it will be easy to mantain pure cyanogenmod 7 for our sgm.
mebitek said:
done. I hope he will answer me cause I'm able to sync repos in a couple of hours, so it will be easy to mantain pure cyanogenmod 7 for our sgm.
Click to expand...
Click to collapse
Best Luck Buddy Don't Give Up Early , We Look Forward To See Your Work As We Need To Keep Subpsyke Project Alive
prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld:
Click to expand...
Click to collapse
Are you using 32-bit linux system ?
If yes, then I guess 64-bit is necessary to get things compiled properly without errors.
NB: Just sharing info.
coolsandie said:
Are you using 32-bit linux system ?
If yes, then I guess 64-bit is necessary to get things compiled properly without errors.
NB: Just sharing info.
Click to expand...
Click to collapse
Thanks for the reply but I think that this kind of error is a missing reference for the function register_android_hardware_fm_fmradio that is called from AndroidRuntime.cpp
32 or 64 bit it is no differnce in compile result. just speed....
However I've checked tass configuration and I see that fm radio is set to BCM2049 chip.
I checkd into frameworks/base/core/jni/ cm source tree directory and I found only fm hardware reference for :
bcm4325
si4708
si4709
wl1271
now I'm trying to compile again setting radio to bcm4325 just to see if something appens...
P.S. should be nice to have some tecnical ideas about the code error not only if the host system is well configured
P.P.S. changed values to bcm4325 let me not face errors no more. Now I'm compiling!!!!
I have checked some github projects and I see that a lot of device as sgm with bcm2049 fm chipset set it to bcm4325. I see that just subskype change that value to bcm2049. Should be nice to have some tip and tricks from him to understand well the point of the situation
Now I have a signed zip to flash into my sgm.
It contains subskype cm7.2 tass device configuration and latest cm 7.2 sources update at 31-01-2012.
to check changes:
http://review.cyanogenmod.com/#q,status:open,n,z
It works!!! finally compiled and booting successfully.
Now I'm trying to study the best way to mantain this kind of project (it's first time for me in android dev and I just have an android device by november).
first at all I was thinking to add V6 supercharge by default. what do you think?
mebitek said:
It works!!! finally compiled and booting successfully.
Now I'm trying to study the best way to mantain this kind of project (it's first time for me in android dev and I just have an android device by november).
first at all I was thinking to add V6 supercharge by default. what do you think?
Click to expand...
Click to collapse
Great news. Glückwunsch (don't know the english word at the moment).
Supercharger would be possibly good. Subpsyke said something to it but i don't rember clearly.
Keep up your work.
Sent from my GT-S5570 using xda premium
mebitek said:
It works!!! finally compiled and booting successfully.
Now I'm trying to study the best way to mantain this kind of project (it's first time for me in android dev and I just have an android device by november).
first at all I was thinking to add V6 supercharge by default. what do you think?
Click to expand...
Click to collapse
No not add anything. It s better. Completely clean
Inviato dal mio GT-S5570 usando Tapatalk
mebitek said:
Thanks for the reply but I think that this kind of error is a missing reference for the function register_android_hardware_fm_fmradio that is called from AndroidRuntime.cpp
32 or 64 bit it is no differnce in compile result. just speed....
However I've checked tass configuration and I see that fm radio is set to BCM2049 chip.
I checkd into frameworks/base/core/jni/ cm source tree directory and I found only fm hardware reference for :
bcm4325
si4708
si4709
wl1271
now I'm trying to compile again setting radio to bcm4325 just to see if something appens...
P.S. should be nice to have some tecnical ideas about the code error not only if the host system is well configured
P.P.S. changed values to bcm4325 let me not face errors no more. Now I'm compiling!!!!
I have checked some github projects and I see that a lot of device as sgm with bcm2049 fm chipset set it to bcm4325. I see that just subskype change that value to bcm2049. Should be nice to have some tip and tricks from him to understand well the point of the situation
Click to expand...
Click to collapse
For the radio, I used my patch to add support for the bcm2xxx devices with proper seeking. It's on gerrit here: http://review.cyanogenmod.com/#change,10358
mebitek said:
It works!!! finally compiled and booting successfully.
Now I'm trying to study the best way to mantain this kind of project (it's first time for me in android dev and I just have an android device by november).
first at all I was thinking to add V6 supercharge by default. what do you think?
Click to expand...
Click to collapse
no no...no v6.
Just vanilla cm7...and thanks for the initiative and ABT!
dont add scripts..but maybe something from cm gerrit if u wish..but then it'll not be vanilla.
Hi guys,
i'm a new member and i've read forum rules, this is my first post, i hope i'm posting to the right section. I'm trying to build ChameleonOS from source for our device, after 7 hours everytime i get two errors saying "vibrator.c:76: error: undefined reference to "sendit"" and "vibrator.c:81: error: undefined reference to "sendit"", then the build stops with Error 1. I'm using Lubuntu 13.04 with ChaOS repo and Team Canjica's repos: device, vendor, kernel, libhardware and libhardware_legacy, i followed this guide: http://forum.xda-developers.com/showthread.php?t=2351504. Seems that these errors are related to libhardware_legacy's vibrator.c, i attach the image of the error in this post. Thanks
P.S. Sorry for my bad english, i'm Italian
EDIT: For error I made post #5 instead of edit this, sorry! :angel:
No one can help me? Also only to ignore the errors and continue the build, if there's a way, instead of automatically stop it. In this case I can extract libhardware_legacy.so from CM10.1's flashable zip and put it in builded ChaOS's flashable zip.
Add ifdef to the original vibrator c file
Sent from my GT-I9070 using Tapatalk 4
Shaaan said:
Add ifdef to the original vibrator c file
Sent from my GT-I9070 using Tapatalk 4
Click to expand...
Click to collapse
In which part of file I have to add it?
[HELP] ChameleonOS-janice compiled, but wifi issue!
Now I have compiled ChameleonOS for janice, everything works fine but low incall volume bug, same as CM, and wifi doesn't turn on with compiled boot.img... I've tested it with CM10.1 build 20130923's boot.img and wifi works, but in this way loses the customizations and possibility to use integrated theme manager, which are the strong point of this rom. When this problem will be resolved I share the rom in devs section. Any help will be appreciated
Tesla-MADAL93 said:
Now I have compiled ChameleonOS for janice, everything works fine but low incall volume bug, same as CM, and wifi doesn't turn on with compiled boot.img... I've tested it with CM10.1 build 20130923's boot.img and wifi works, but in this way loses the customizations and possibility to use integrated theme manager, which are the strong point of this rom. When this problem will be resolved I share the rom in devs section. Any help will be appreciated
Click to expand...
Click to collapse
compile again with our updated sources
Sent from my GT-S5367 using xda app-developers app
frapeti said:
compile again with our updated sources
Sent from my GT-S5367 using xda app-developers app
Click to expand...
Click to collapse
Okay, sources updated, now I'm rebuilding
EDIT: Recompiled, now wifi works
Re: szezso's CyanVivo 10.2 / PA port problem
Hi guys!
As I am more or less new here on xda and pretty passive I can't post a reply to szezso's CyanVivo 10.2 and have instead post a new thread here :crying:
First of all, I really want to thank szezso for the extremly awesome work he's done on this!
I tried to port PA 3.99-RC2 to the vivo using your sources.
I synced and built (pa_vivo-eng) the sources from 2013/10/14 using the attached local_manifest.xml and a few patches (also attached).
The ROM built successfully and was flashable.
But when I boot now, nothing on the screen happens and the red LED (while charging the battery) gets turned off.
However ADB still recognizes the phone (adb shell is possible too).
adb logcat prints out following all the time:
Code:
W/dalvikvm( 8828): PR_SET_NO_NEW_PRIVS failed. Is your kernel compiled correctly?: Invalid argument
I/SystemServer( 8832): Entered the Android system server!
I/SystemServer( 8832): Waiting for installd to be ready.
I/Installer( 8832): connecting...
I/SystemServer( 8832): Power Manager
I/SystemServer( 8832): Activity Manager
I/ActivityManager( 8832): Memory class: 48
W/UsageStats( 8832): Usage stats version changed; dropping
I/AppOps ( 8832): No existing app ops /data/system/appops.xml; starting empty
I/SystemServer( 8832): Display Manager
I/SystemServer( 8832): Telephony Registry
I/SystemServer( 8832): Scheduling Policy
Does anyone know how to fix this or what the actual problem is there?
Oh.. and sorry for my (pretty sure) not perfect english...
Edit 1:
I used this guide to checkout/build paranoid android (using branch jb43-legacy) too.
In the rom-build.sh I changed the line
Code:
lunch "pa_$DEVICE-userdebug";
to
Code:
lunch "pa_$DEVICE-eng";
.
As I am building on ArchLinux which is using OpenJDK 7u40 I installed jre and jdk 6u45 to /opt/java6 and set JAVA_HOME to /opt/java6/bin before lunching and building.
gcc version (don't know if needed):
Code:
gcc (GCC) 4.8.1 20130725 (prerelease)
Copyright (C) 2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOS
make version:
Code:
GNU Make 3.82
Built for x86_64-unknown-linux-gnu
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Uroc327 said:
Hi guys!
As I am more or less new here on xda and pretty passive I can't post a reply to szezso's CyanVivo 10.2 and have instead post a new thread here :crying:
First of all, I really want to thank szezso for the extremly awesome work he's done on this!
I tried to port PA 3.99-RC2 to the vivo using your sources.
I synced and built (pa_vivo-eng) the sources from 2013/10/14 using the attached local_manifest.xml and a few patches (also attached).
The ROM built successfully and was flashable.
But when I boot now, nothing on the screen happens and the red LED (while charging the battery) gets turned off.
However ADB still recognizes the phone (adb shell is possible too).
adb logcat prints out following all the time:
W/dalvikvm( 8828): PR_SET_NO_NEW_PRIVS failed. Is your kernel compiled correctly?: Invalid argument
I/SystemServer( 8832): Entered the Android system server!
I/SystemServer( 8832): Waiting for installd to be ready.
I/Installer( 8832): connecting...
I/SystemServer( 8832): Power Manager
I/SystemServer( 8832): Activity Manager
I/ActivityManager( 8832): Memory class: 48
W/UsageStats( 8832): Usage stats version changed; dropping
I/AppOps ( 8832): No existing app ops /data/system/appops.xml; starting empty
I/SystemServer( 8832): Display Manager
I/SystemServer( 8832): Telephony Registry
I/SystemServer( 8832): Scheduling Policy
Does anyone know how to fix this or what the actual problem is there?
Oh.. and sorry for my (pretty sure) not perfect english...
Click to expand...
Click to collapse
Hi, did you make sure to use legacy sources/pmem?
And did you try flash the Kernel from szezsos build, or libs too if you're not building again
Sent from my HTC One using XDA Premium 4 mobile app
poondog said:
Hi, did you make sure to use legacy sources/pmem?
And did you try flash the Kernel from szezsos build, or libs too if you're not building again
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for your reply!
I used szezso's local manifest as base for the local_manifest (see attachement of the first post) and the jb43-legacy branch for the PA manifest (see Edit #1 of the first post).
But I do not know if the PA tree uses pmem or ion..
And what exactly do you mean with the second line?
I built the ROM like the guide told me to do (except for the fact that i built the eng version and not the userdebug version) and flashed out/target/product/vivo/pa_vivo-3.99-RC2-20131014.zip which contains the boot.img AFAIK.
Uroc327 said:
Thanks for your reply!
I used szezso's local manifest as base for the local_manifest (see attachement of the first post) and the jb43-legacy branch for the PA manifest (see Edit #1 of the first post).
But I do not know if the PA tree uses pmem or ion..
And what exactly do you mean with the second line?
I built the ROM like the guide told me to do (except for the fact that i built the eng version and not the userdebug version) and flashed out/target/product/vivo/pa_vivo-3.99-RC2-20131014.zip which contains the boot.img AFAIK.
Click to expand...
Click to collapse
Yeah I'm saying that maybe if your Kernel is the problem, flashing the working kernel from his cm builds may work
Sent from my HTC One using XDA Premium 4 mobile app
poondog said:
Yeah I'm saying that maybe if your Kernel is the problem, flashing the working kernel from his cm builds may work
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hmm... shouldn't the rom be built with szezsos kerneI (the kernel is in the manifest and I saw a kernel building from source when watching make output :laugh?
I flashed the TESCO 2.9++ for JB 4.2 now (the latest available on the xda thread) and after the green 'htc' on the white background the screen gets black again...
Only thing that changed is: adb now says the device is unauthorize (=> shell does not work anymore).
Uroc327 said:
Hmm... shouldn't the rom be built with szezsos kerneI (the kernel is in the manifest and I saw a kernel building from source when watching make output :laugh?
I flashed the TESCO 2.9++ for JB 4.2 now (the latest available on the xda thread) and after the green 'htc' on the white background the screen gets black again...
Only thing that changed is: adb now says the device is unauthorize (=> shell does not work anymore).
Click to expand...
Click to collapse
Yes but log said something may be wrong with kernel, no harm in trying
Okay maybe its not the problem
@szezso
Uroc327 said:
Hmm... shouldn't the rom be built with szezsos kerneI (the kernel is in the manifest and I saw a kernel building from source when watching make output :laugh?
I flashed the TESCO 2.9++ for JB 4.2 now (the latest available on the xda thread) and after the green 'htc' on the white background the screen gets black again...
Only thing that changed is: adb now says the device is unauthorize (=> shell does not work anymore).
Click to expand...
Click to collapse
Since you're building 4.3 PAC, maybe you should download the latest CyanVivo 10.2 and strip the boot.img outta it instead.
Sent from Google Nexus 4 @ CM10.2
Uroc327 said:
Hmm... shouldn't the rom be built with szezsos kerneI (the kernel is in the manifest and I saw a kernel building from source when watching make output :laugh?
I flashed the TESCO 2.9++ for JB 4.2 now (the latest available on the xda thread) and after the green 'htc' on the white background the screen gets black again...
Only thing that changed is: adb now says the device is unauthorize (=> shell does not work anymore).
Click to expand...
Click to collapse
That was a mistake! Download the latest CV10.2, pull the boot.img from there, and try it with that!
AndyYan said:
Since you're building 4.3 PAC, maybe you should download the latest CyanVivo 10.2 and strip the boot.img outta it instead.
Sent from Google Nexus 4 @ CM10.2
Click to expand...
Click to collapse
Oh yeah.. thanks!
Gonna try that too after the latest zip is completely downloaded. But.. again... shouldn't be the kernel included in the final zip (as szezos TESCO and CyanVivo 10.2 repos are in the manifest)?
I flashed my built zip again (including the kernel as far as I think) and also flashed a Fix_display_bug.zip (which I downloaded for the vivo PAC port from blindndumb) and now the screen does not get black anymore but the green htc logo stays...
I also found a post from szezso in this thread, talking about missing vsync (here)... I'm gonna try his propsed fix and build again.
Uroc327 said:
Oh yeah.. thanks!
Gonna try that too after the latest zip is completely downloaded. But.. again... shouldn't be the kernel included in the final zip (as szezos TESCO and CyanVivo 10.2 repos are in the manifest)?
I flashed my built zip again (including the kernel as far as I think) and also flashed a Fix_display_bug.zip (which I downloaded for the vivo PAC port from blindndumb) and now the screen does not get black anymore but the green htc logo stays...
I also found a post from szezso in this thread, talking about missing vsync (here)... I'm gonna try his propsed fix and build again.
Click to expand...
Click to collapse
If you used my msm7x30-common, then you should have disabled vsync. In fact, I think, that the problem should be with the ramdisk. And don't flash the screen fix, cause it's for 4.2.2, not for 4.3.1!
ssotanc there
poondog said:
Yes but log said something may be wrong with kernel, no harm in trying
Okay maybe its not the problem
@szezso
Click to expand...
Click to collapse
Well, thanks anyway.. It was a reasonable idea and I'm thankful for your help
szezso said:
That was a mistake! Download the latest CV10.2, pull the boot.img from there, and try it with that!
Click to expand...
Click to collapse
Oh, ok... thank you.
So I'm gonna flash the kernel from the CV 10.2 zip after downloaded (50% already).
Is this a bug in the latest kernel on github or did I built the kernel wrong (I patched a line for the kernel toolchain as visible in the patch files from first post)?
szezso said:
If you used my msm7x30-common, then you should have disabled vsync. In fact, I think, that the problem should be with the ramdisk. And don't flash the screen fix, cause it's for 4.2.2, not for 4.3.1!
Click to expand...
Click to collapse
Yup! I'm using your msm7x30-common repo (revision cm-10.2).
The screen fix was just a try
Did not really expect it to work... but it can't harm :laugh:.
Uroc327 said:
Yup! I'm using your msm7x30-common repo (revision cm-10.2).
The screen fix was just a try
Did not really expect it to work... but it can't harm :laugh:.
Click to expand...
Click to collapse
Okay, we'll see. But at first, let's check the boot.img.
szezso said:
Okay, we'll see. But at first, let's check the boot.img.
Click to expand...
Click to collapse
Ok now... I flashed the boot.img from the CyanVivo 10.2 zip.
Results are same as with the TESCO kernel for jb 4.2:
I get a black screen after htc logo and adb says the device is unauthorized (btw charging led does not work to after booting the rom).
Apparently same issues on CyanVivo 10.2 'shipped' kernel and separate 4.2 kernel :crying:
Uroc327 said:
Ok now... I flashed the boot.img from the CyanVivo 10.2 zip.
Results are same as with the TESCO kernel for jb 4.2:
I get a black screen after htc logo and adb says the device is unauthorized (btw charging led does not work to after booting the rom).
Apparently same issues on CyanVivo 10.2 'shipped' kernel and separate 4.2 kernel :crying:
Click to expand...
Click to collapse
Could you upload the ROM for me?
szezso said:
Could you upload the ROM for me?
Click to expand...
Click to collapse
Yeah sure!
But it will need some time to upload the rom...
I'm gonna post the link when its done.
Uroc327 said:
Yeah sure!
But it will need some time to upload the rom...
I'm gonna post the link when its done.
Click to expand...
Click to collapse
Okay, I'm waiting for that.
szezso said:
Okay, I'm waiting for that.
Click to expand...
Click to collapse
Finally.... (actually the upload was pretty fast )!
Here's the link: pa_vivo-3.99-RC2-20131014.zip
Uroc327 said:
Finally.... (actual upload was pretty fast)!
Here's the link: pa_vivo-3.99-RC2-20131014.zip
Click to expand...
Click to collapse
I'll be able to look into it tomorrow. Please be patient!
szezso said:
I'll be able to look into it tomorrow. Please be patient!
Click to expand...
Click to collapse
No problem!
Thanks for your help :good:
Hi There we have found complete sources of our phone Micromax A110 MTK 6577
We were hoping if any one Awsum Dev could compile an omni rom for our Beloved Phone here is the link to the sources http://pan.baidu.com/s/1ACPRk#dir/path=%2F8377%E8%BD%AF%E4%BB%B6%E5%8C%85
If u want u can contact our devs u can contact @[email protected] and @khan_frd2002 and also our kernel dev @varun.chitre15
And for compiling there is this guide http://wenku.baidu.com/link?url=GlZC...3XdjfuZXcip5zm
I hope i will receive Positive results and replies
Thnx
Andromodgod:cyclops:
if possible please upload to a better file hosting site. this is so slow it's causing the download to fail
cybojenix said:
if possible please upload to a better file hosting site. this is so slow it's causing the download to fail
Click to expand...
Click to collapse
Thnx for the reply 2 Questions
Are you from the omni team I.E help us in making rom
How long would the compilation take
U can contact all of us we are at http://forum.xda-developers.com/micromax-a110/development
Or Here
http://forum.xda-developers.com/micromax-a110/
Link will be provided as soon as possible :angel:
I'm a contributor there. I'm just curious as to what parts they change. seeing as mtk devices are dirt cheap here, I might consider getting some to work on if their sources aren't desperately bad
edit:
compilation doesn't take long. getting to the stage of getting a working compilation may take a while though
ps can the file labelled "alps patch" be uploaded first please. thanks
Thnx
@cybojenix Thnx for ur interest in our Phone one developer @[email protected] is already working on cm 10.2
And Varun Chitre is also a great dev u can ask anyone and all of them will help u
About the mirror i dont think it is possible cuz most of the people(Dev) Live in india or other places where the Internet connection is slow u can use an extension for firefox i will link it to you https://addons.mozilla.org/en-US/firefox/addon/downthemall/
ANd please try not to post cuz if u see ur post it say """"555 Posts"""" Lucky number
U can PM Me Thnx
I will ask devs to mirror it
yes buddy mirroring is needed....the downloading speed is so less that my downld has failed more than 4 tiimes..
Alps Patch file
Here is the link to patch file @cybojenix http://d-h.st/BAg
Leeching that to take a look.
Since none of us have a 6577 device, someone else will have to do the bringup work, but it would be interesting to see how much commonality there is between 6577 and 6589.
Unfortunately the problem is MTK's sources are a disorganized mess, and in many cases, their HALs are just wrappers around a blob. The source we have for R819 is for 4.2 - while xplodwild got 4.3 partially booting on R819, so far, the display drivers just crash on boot on 4.4.
Entropy512 said:
Leeching that to take a look.
Since none of us have a 6577 device, someone else will have to do the bringup work, but it would be interesting to see how much commonality there is between 6577 and 6589.
Unfortunately the problem is MTK's sources are a disorganized mess, and in many cases, their HALs are just wrappers around a blob. The source we have for R819 is for 4.2 - while xplodwild got 4.3 partially booting on R819, so far, the display drivers just crash on boot on 4.4.
Click to expand...
Click to collapse
From what I've looked at so far in the uploaded patch file, it doesn't seem to be too good. I was expecting to see diff patches.. from what is included in it, it seems to be partial, and out of the camera, there are only headers.
Waiting for the full source to be uploadec
Sent from my Nexus 7 using Tapatalk
cybojenix said:
From what I've looked at so far in the uploaded patch file, it doesn't seem to be too good. I was expecting to see diff patches.. from what is included in it, it seems to be partial, and out of the camera, there are only headers.
Waiting for the full source to be uploadec
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Source are uploaded here you go http://forum.xda-developers.com/showthread.php?p=48303269
Sent from my Nexus 4 using XDA Premium 4 mobile app
[SOURCE]Full MTK6577 AOSP tree + proprietary source: http://forum.xda-developers.com/showthread.php?t=2172440
*edit: These are sources for ICS. Reason: http://forum.xda-developers.com/showpost.php?p=48307124&postcount=134
Progress
Any report on the progress @cybojenix
andromodgod said:
Any report on the progress @cybojenix
Click to expand...
Click to collapse
Sources seem somewhat unhelpful at a first glance, however going deeper into them may reveal key parts that have Been overlooked
Sent from my Nexus 7 using Tapatalk
Any Good News
DO we have any good news from u @cybojenix
We are eagerly waiting for u
andromodgod said:
DO we have any good news from u @cybojenix
We are eagerly waiting for u
Click to expand...
Click to collapse
Please, check this comments:
http://forum.xda-developers.com/showpost.php?p=48628112&postcount=43
http://forum.xda-developers.com/showpost.php?p=48642380&postcount=44
mtk你还是放弃吧，很多都没有开源的，mtk提供整套方案给生产商，连生产商都没有源代码的。
Sent from my One X using xda app-developers app
I thought it is complete
Sent from my Nexus 4 using Tapatalk
Any news?
Related:
MediaTek driver sourcecode (want custom ROMs? read this!): http://forum.xda-developers.com/showthread.php?p=50146816
No complete source, nothing to accomplish.
I am not responsible for any possible bad effects which may result from using included software! You flash it on your own risk!
Probably it will work in the P905 version, because I flashed the a P905 kernel in my P905M without problems. But, as usual, it is your risk.
User esgie confirmed that it works on SM-P905 too!
STOCK compiled with SELinux setenforce enabled
Kernel base: compiled from Samsung sources without modifications (opensource.samsung.com)
Kernel ramdisk: extracted from stock image
Features: setenforce command working
WARNING!
FLASHING THIS WILL TRIP KNOX AVOIDING YOUR WARRANTY!
Known issues
WiFi gets a little screwy. To fix it edit /system/build.prop, change the parameter ro.securestore.support from true to false and reboot.
Installation
flash using ODIN (AP/PDA)
Image sha1sum
b85360a80f6205269b75d9dfabccac211a224d46
CREDITS
- Graeme Hill`s Dev Blog (http://graemehill.ca/compiling-permissive-android-kernel)
- osm0sis user Android Image Kitchen tool (http://forum.xda-developers.com/showthread.php?t=2073775)
- Samsung (opensource.samsung.com)
- esgie Kernel STOCK RELOADED (http://forum.xda-developers.com/showthread.php?t=2771469)
No one interested?
Thanks a lot. Will try it.
Sent from my GT-N7100 using XDA Premium 4 mobile app
rodpp said:
I am not responsible for any possible bad effects which may result from using included software! You flash it on your own risk!
Probably it will work in the P905 version, because I flashed the a P905 kernel in my P905M without problems. But, as usual, it is your risk.
STOCK compiled with SELinux setenforce enabled
Kernel base: compiled from Samsung sources without modifications (opensource.samsung.com)
Kernel ramdisk: extracted from stock image
Features: setenforce command working
WARNING!
FLASHING THIS WILL TRIP KNOX AVOIDING YOUR WARRANTY!
Known issues
WiFi gets a little screwy. To fix it edit /system/build.prop, change the parameter ro.securestore.support from true to false and reboot.
Installation
flash using ODIN (AP/PDA)
CREDITS
- Graeme Hill`s Dev Blog (http://graemehill.ca/compiling-permissive-android-kernel)
- osm0sis user Android Image Kitchen tool (http://forum.xda-developers.com/showthread.php?t=2073775)
- Samsung (opensource.samsung.com)
- esgie Kernel STOCK RELOADED (http://forum.xda-developers.com/showthread.php?t=2771469)
Click to expand...
Click to collapse
Hangs on boot before the Samsung logo.
Sent from my SM-P905M using XDA Premium HD app
gorcutt said:
Hangs on boot before the Samsung logo.
Sent from my SM-P905M using XDA Premium HD app
Click to expand...
Click to collapse
Hi,
I just downloaded the file from this post and checked the sha1sum against the original file that I uploaded and it´s ok. The sha1sum value is b85360a80f6205269b75d9dfabccac211a224d46. So there is no file corruption problem.
Please check if your file has the same sha1sum.
Tonight I´ll flash this file again in my tablet and verify if it works. It´s highly improbable that I uploaded the wrong file, but I´ll check flashing it.
As soon as possible I´ll update here the result of this test.
Regards,
Rodrigo.
Awesome!
Flashed, seems to boot ok on SM-P905
Great job.
Seems to be working fine! Boots as permissive and setenforce 0/1 working fine.
Great job. Now we are waiting for at least some basic overclocking and governors implementation
esgie said:
Awesome!
Flashed, seems to boot ok on SM-P905
Great job.
Seems to be working fine! Boots as permissive and setenforce 0/1 working fine.
Great job. Now we are waiting for at least some basic overclocking and governors implementation
Click to expand...
Click to collapse
Thank you very much for confirm that it works on SM-P905, I'll include this information on the first post.
If you find some WiFi issues don't forget to edit /system/build.prop, change the parameter ro.securestore.support from true to false and reboot.
Regards,
Rodrigo.
Already had the property changed in my build.prop, so i'm not exactly sure if the wifi works out of the box or not. Although I confirm that it DOES work with the build.prop modification
And by "does work" I meant both wifi and mobile radio working flawlessly.
gorcutt said:
Hangs on boot before the Samsung logo.
Sent from my SM-P905M using XDA Premium HD app
Click to expand...
Click to collapse
rodpp said:
Hi,
I just downloaded the file from this post and checked the sha1sum against the original file that I uploaded and it´s ok. The sha1sum value is b85360a80f6205269b75d9dfabccac211a224d46. So there is no file corruption problem.
Please check if your file has the same sha1sum.
Tonight I´ll flash this file again in my tablet and verify if it works. It´s highly improbable that I uploaded the wrong file, but I´ll check flashing it.
As soon as possible I´ll update here the result of this test.
Regards,
Rodrigo.
Click to expand...
Click to collapse
Hi there, I tested here and the image is working fine here. The user esgie just confirmed that too, in a P905. Please check the sha1sum of your downloaded image file.
Regards,
Rodrigo.
rodpp said:
Hi,
I just downloaded the file from this post and checked the sha1sum against the original file that I uploaded and it´s ok. The sha1sum value is b85360a80f6205269b75d9dfabccac211a224d46. So there is no file corruption problem.
Please check if your file has the same sha1sum.
Tonight I´ll flash this file again in my tablet and verify if it works. It´s highly improbable that I uploaded the wrong file, but I´ll check flashing it.
As soon as possible I´ll update here the result of this test.
Regards,
Rodrigo.
Click to expand...
Click to collapse
I probably did something wrong.
I've downloaded again and wiill try once more.
MD5 f39207bd4c45b1854372cd519942a6c2
SHA1 b85360a80f6205269b75d9dfabccac211a224d46
Thanks.
Sent from my GT-N7100 using XDA Premium 4 mobile app
As we all can see, our devices lacks of community support.
I wonder if you are the first person on the planet who managed to prepare an environment and compile P905(x) kernel succesfuly
May I ask you if have any plans to proceed with the kernel developement?
Please integrate fauxsound
esgie said:
As we all can see, our devices lacks of community support.
I wonder if you are the first person on the planet who managed to prepare an environment and compile P905(x) kernel succesfuly
May I ask you if have any plans to proceed with the kernel developement?
Click to expand...
Click to collapse
Unfortunately I don't have enough free time, so I don't have plans to work in kernel development. I did this because I was needing it to install some stuffs in my tablet and decided to share it here o XDA where I always found useful things.
If someone wants simple modifications and points some links explaining that I can try without problems.
And if someone have problems preparing an environment to compile the kernel, let me know, I'll be very happy to help.
Regards,
Rodrigo.
koko115 said:
Please integrate fauxsound
Click to expand...
Click to collapse
Do you have a link?
Honestly, I don't know what fauxsound is!
rodpp said:
Do you have a link?
Honestly, I don't know what fauxsound is!
Click to expand...
Click to collapse
Well, i'm not the one who asked this nor I have ever heard about it, but by curiousity I googled this. Got link for this app at Google Play. There are github links in app description to patches that needs to be added to kernel to make this work.
Just can't see Note Pro in officially supported devices -list and don't know can this device even be supported. There reads "Unofficially Supporting: Any Phones using Qualcomm Audio Chip WCD93xx chipsets." But I don't know which chipset NP12.2 got.
Spere said:
Well, i'm not the one who asked this nor I have ever heard about it, but by curiousity I googled this. Got link for this app at Google Play. There are github links in app description to patches that needs to be added to kernel to make this work.
Just can't see Note Pro in officially supported devices -list and don't know can this device even be supported. There reads "Unofficially Supporting: Any Phones using Qualcomm Audio Chip WCD93xx chipsets." But I don't know which chipset NP12.2 got.
Click to expand...
Click to collapse
Thanks, it seems simple if the audio chip is compatible. I'll try to include this in the kernel.
Thanks, Rodrigo for the great work!
Finally i was able to get Ubuntu running using linux complete installer.
Its a shame there's so little development for this great device.
I wish i had skills to do some.
Thanks, from Piracicaba-SP
js345 said:
Thanks, Rodrigo for the great work!
Finally i was able to get Ubuntu running using linux complete installer.
Its a shame there's so little development for this great device.
I wish i had skills to do some.
Thanks, from Piracicaba-SP
Click to expand...
Click to collapse
Yes, one of my motivations to compile this kernel was to boot Linux images too.
Regards,
Rodrigo.
Enviado de meu SM-P905M usando Tapatalk
rodpp said:
Thanks, it seems simple if the audio chip is compatible. I'll try to include this in the kernel.
Click to expand...
Click to collapse
I tried to compile the kernel with the patches sugested by the Fauxsound developer but, unfortunately, I have no success.
Probably it will be necessary more kernel modifications to compile it with the Fauxsound patches.
Enviado de meu SM-P905M usando Tapatalk
Hi,
I have a question about your kernel.
does it contains a root feature ?
I am running XXUANI1 firmware on P900 (wifi version), and have tried the auto root from Chainfire.
it does not work well (I think it was release for a previous firmware), and give a lot of random reboot.
I was thinking that may be I could flash a kernel accepting to work with su.bin
thanks for any information.
Olivier
orobin said:
Hi,
I have a question about your kernel.
does it contains a root feature ?
I am running XXUANI1 firmware on P900 (wifi version), and have tried the auto root from Chainfire.
it does not work well (I think it was release for a previous firmware), and give a lot of random reboot.
I was thinking that may be I could flash a kernel accepting to work with su.bin
thanks for any information.
Olivier
Click to expand...
Click to collapse
The kernel is for P905M/P905...