Develop Bugs

[WIP] [ROM] SSROM "Simon'sStock"

SS ROM:
SS stands for SimonsStock, for the HTC Wildfire S (Virgin Mobile USA ONLY)
I spent a long time compiling and testing this ROM, and am still working on modifying it, as I have school on weekdays and a big test in math coming up, so my developing time is limited. Ive de-odexed the entire ROM, made sure the carrier key logger was NOT present, added WiFi tethering (native htc, check the quick settings tab in status bar), added root, removed most of the crapware, however you can still activate your phone on my ROM, zip-aligned, ADHOC Networks are supported, and buisybox. NOTE: UOT's theme kitchen will work for this device anything you'll need to upload to them is in this zip as well. Eventually, I will get around to making a new boot.img but as of now, this one is stock. If you'd like to make one with apps2sd support and receive credit, PM me. Also, to anyone brought here looking for CM7, I am currently porting it, but have run into problems with the boot.img and kernel, its getting there, slowly. When I have a release of it I'll post, so dont ask for updates.
WARNING:
Any bricks are not mine, XDA's or anyone besides yourself's fault. The procedures used to flash my ROM may cause semi-bricking, However, it is always reversible.
So heres the flash-able zip:
you know the drill on flashing.. Dont forget to wipe everything
https://docs.google.com/open?id=0BwZZjRHl9NIJMGI1MTI3ZTEtYTk4YS00NzAwLWE3YjktMWRhZmRkODIzNTA1
ADDED:
WiFi tethering (check the quick settings tab on notification bar)
DeOdexed the Rom, so it is now themeable.
zipaligned for speed
fixed some small problems with memory (got you guys a little more)
fixed the link2sd problem
Added adhoc network support
MADE THE FIRST ROM (with these modifications)

Nice another ROM for the vm wildfire s
Sent from my HTC_A510c using xda premium

Will the CM7 be universal or just for the VM 510c?

d33ps1x said:
Will the CM7 be universal or just for the VM 510c?
Click to expand...
Click to collapse
CM7 should be universal, CDMA phones share the same hardware, so i plan on having a separate zip for the VM files that i want to include. This is stock VM firmware, the only reason that this is only for VM. Also, when CM9 Comes out, im only updating to make cm7 stable and as bugless as i can then permenately moving over to the CM9 source.
Update: sorry for the long wait, dialup is a killer on uploads
EDIT:
Also be looking for my next build, im going to include DSP and look through and see if i can unlock any more goodies. Ill also be posting some tutorials that allow for development on the phone, here. Not this thread, but a new one.

Great news m8,keep it up

I was wondering if you are going to add sense 3.0 lockscreen ?
Sent from my HTC_A510c using xda premium

New build is up
https://docs.google.com/open?id=0BwZZjRHl9NIJMGI1MTI3ZTEtYTk4YS00NzAwLWE3YjktMWRhZmRkODIzNTA1

cpie20 said:
I was wondering if you are going to add sense 3.0 lockscreen ?
Sent from my HTC_A510c using xda premium
Click to expand...
Click to collapse
Thanks for the reccomendation I think i will try to add it in there, but i am working on another rom at present, this is only a holdover until then to make our phones useable

No problem is that rom for the wildfire s??
Sent from my HTC_A510c using xda premium

Yes that is the Rom for the VMUS wildfire s. Next im going to try to add and remove some things. Im also working on the kernel, so if anyone knows how, and would like to teach me how to develop kenels, PM or email me

Oh I know someone that knows how to compile kernels but he is in another forum
Sent from my HTC_A510c using xda premium

What forum, send me to him lol. I have the thing booting, but i need the kernel for stability im a member of all forums, i can sent him a PM

His name is tiny from the htc incredible forums
Sent from my HTC_A510c using xda premium

Im going to look him up. I took a crash (google) course on kernels today. So i keep getting this error i dont know how to fix lol.. Fun fun.. Anyways, if anyone knows how to fix it it is
[email protected]:~/kernelsense$ make ARCH=arm CROSS_COMPILE=$CCOMPILER -j`grep 'processor' /proc/cpuinfo | wc -l`
scripts/kconfig/conf -s arch/arm/Kconfig
CHK include/linux/version.h
CHK include/generated/utsrelease.h
make[1]: `include/generated/mach-types.h' is up to date.
CC kernel/bounds.s
cc1: error: unrecognized command line option ‘-mlittle-endian’
cc1: error: unrecognized command line option ‘-mapcs’
cc1: error: unrecognized command line option ‘-mno-sched-prolog’
cc1: error: unrecognized command line option ‘-mno-thumb-interwork’
kernel/bounds.c:1:0: error: unknown ABI (aapcs-linux) for -mabi= switch
kernel/bounds.c:1:0: error: bad value (armv5t) for -march= switch
kernel/bounds.c:1:0: error: bad value (strongarm) for -mtune= switch
make[1]: *** [kernel/bounds.s] Error 1
make: *** [prepare0] Error 2
EDIT: I couldnt find him on there
its me ttying to make a stock kernel, with added supports.

I know nothing of kernels well the full avatar name is tiny4579 or something like that
Sent from my HTC_A510c using xda premium

lol still couldnt find him. Im going to look around XDA some

Got Cm7 to build, and a dev built me a kernel. Touchscreen and network dont work and some graphics issues but its getting there everyone

Nice to see progress going along

Ok, this is the real deal. An alpha release. There are lots of problems, but i need testers while im at school. This should work on any carrier. Please check the listing for my rom post

ssrom
This Rom is sick. Use this as my stock. Works well with Jikantaru oc kernel. WiFi is working. Thanks

[RECOVERY] TWRP 2.2 - latest version [MARVEL/MARVELC]

TWRP 2.2
team win recovery project
Hey guys, I give you the latest TWRP build. This is (as of edit date) the only TWRP build that is up to date with 2.2. This build is available to flash via fastboot or via a normal zip to use in your recovery.
Me and Dees_Troy have also been discussing official TWRP support for the future.​
-
TWRP 2.2 has the following that 2.1 or 2.0 doesn't have:
On-screen keyboard in recovery! -- supports long press, backspace repeat, and swipe left deletes everything left of the cursor
Name new backups and rename existing backups
Rename files and folders in the file manager
Pseudo-terminal emulator
Support decrypting an encrypted data partition on Galaxy Nexus (enter password using keyboard)
Backup archive splitting -- allows backup and restore of data partitions larger than 2GB
Simplified XML layout support between resolutions
Added dual storage selection radio buttons to zip install, backup, and restore pages
Improved zip install compatibility
Updated update-binary source code
Numerous small bug fixes and improvements
Known bugs:
There are no known bugs at the moment, if you see any please inform me

Download links
DOWNLOAD FOR THE MARVEL | DOWNLOAD FOR THE MARVELC
Flashable ZIPs soon Only recovery.img's currently available (sorry)
​

Please upload fast I'm gonna love it....
Sent from my HTC Wildfire S A510e

Thanks ben for getting this working how did you fix the compile problems or is my cm repo gone bad again lol waiting for link if you can pm me it ill upload it to my vps.
Sent from my Wildfire S A510e using Tapatalk 2

eoghan2t7 said:
Thanks ben for getting this working how did you fix the compile problems or is my cm repo gone bad again lol waiting for link if you can pm me it ill upload it to my vps.
Sent from my Wildfire S A510e using Tapatalk 2
Click to expand...
Click to collapse
I didn't get many compile problems. Any that I did get I fixed.
The colour is a bit messed up atm. Eoghan, what colour setting did you use?
Sent from my HTC Wildfire S A510e using xda premium

benjamingwynn said:
I didn't get many compile problems. Any that I did get I fixed.
The colour is a bit messed up atm. Eoghan, what colour setting did you use?
Sent from my HTC Wildfire S A510e using xda premium
Click to expand...
Click to collapse
I had to change the colour space in the boardconfig.mk
I added one of these cant find out atm
TARGET_RECOVERY_PIXEL_FORMAT := "BGRA_8888"
TARGET_RECOVERY_PIXEL_FORMAT := "RGBX_8888"
TARGET_RECOVERY_PIXEL_FORMAT := "RGB_565"
I'm almost sure its the second one but try all three to be sure
P.s. look over at the rc fora
Sent from my Wildfire S A510e using Tapatalk 2

eoghan2t7 said:
I had to change the colour space in the boardconfig.mk
I added one of these cant find out atm
TARGET_RECOVERY_PIXEL_FORMAT := "BGRA_8888"
TARGET_RECOVERY_PIXEL_FORMAT := "RGBX_8888"
TARGET_RECOVERY_PIXEL_FORMAT := "RGB_565"
I'm almost sure its the second one but try all three to be sure
P.s. look over at the rc fora
Sent from my Wildfire S A510e using Tapatalk 2
Click to expand...
Click to collapse
Yeah its one of em. Can't remember what one worked best either
I'll head over there now
Sent from my HTC Wildfire S A510e using xda premium

Let's hope it doesnt have the SD-ext formatting bug

Read your build.prop
benjamingwynn said:
Yeah its one of em. Can't remember what one worked best either
I'll head over there now
Sent from my HTC Wildfire S A510e using xda premium
Click to expand...
Click to collapse
The Wildfire S is an RGBX device. Use that setting. Just completed a build myself and am testing presently, searching for errors. Colours are fine tho.
---------- Post added at 11:19 PM ---------- Previous post was at 11:13 PM ----------
eoghan2t7 said:
Thanks ben for getting this working how did you fix the compile problems or is my cm repo gone bad again lol waiting for link if you can pm me it ill upload it to my vps.
Sent from my Wildfire S A510e using Tapatalk 2
Click to expand...
Click to collapse
The latest blob of compile errors were due to changes is all three codebases around the same time. After a great deal of work by the CM Team, Modpunk and TWRP the code has reached a point where it is stable enough to compile TWRP. Update from the respective repositories and enjoy.

We'll see... wouldn't get your hopes up tho.
csoulr666 said:
Let's hope it doesnt have the SD-ext formatting bug
Click to expand...
Click to collapse
As this developer has yet to post his build I can't say for sure but, in my own build of 2.2.1 using CM9 and the modpunk kernel the bug still exists.

Sounds good though
But pretty risky for babies like me LOL Will give it a try when I get educated a little.

I will upload today, having a bit more trouble with Ubuntu not booting after updating - bootloader went kapoosh.
I compiled this in my AOKP tree, I'm not exactly sure what bugs it will have and what bugs it won't.
Anyways, once I upload, enjoy

Wait...
benjamingwynn said:
I will upload today, having a bit more trouble with Ubuntu not booting after updating - bootloader went kapoosh.
I compiled this in my AOKP tree, I'm not exactly sure what bugs it will have and what bugs it won't.
Anyways, once I upload, enjoy
Click to expand...
Click to collapse
You haven't even bothered running standard feature tests yourself?

My posts can have titles too.
WoefulDerelict said:
You haven't even bothered running standard feature tests yourself?
Click to expand...
Click to collapse
I flashed a ROM and backed up a ROM and restored it.

That's nice but...
benjamingwynn said:
I flashed a ROM and backed up a ROM and restored it.
Click to expand...
Click to collapse
Didn't have a spare SD card to test the major known issues from previous builds? This seems to be lacking win. Did you get to test the keyboard or backup naming features?

WoefulDerelict said:
Didn't have a spare SD card to test the major known issues from previous builds? This seems to be lacking win. Did you get to test the keyboard or backup naming features?
Click to expand...
Click to collapse
If it means so much to you then you can go test it when I upload it in a min.
Sent from my HTC Wildfire S A510e using Tapatalk 2

Uploaded, flashable ZIP soon

benjamingwynn said:
Uploaded, flashable ZIP soon
Click to expand...
Click to collapse
Thanks but it has the colour issue
Sent from my Wildfire S A510e using Tapatalk 2

eoghan2t7 said:
Thanks but it has the colour issue
Sent from my Wildfire S A510e using Tapatalk 2
Click to expand...
Click to collapse
Yep somebody just told me over IRC about that. It was me not making cleanly I guess. Uploading a new version in about an hour. Want to get some git stuff out of the way.

benjamingwynn said:
Yep somebody just told me over IRC about that. It was me not making cleanly I guess. Uploading a new version in about an hour. Want to get some git stuff out of the way.
Click to expand...
Click to collapse
No problem I'm going to wipe my laptop and do fresh installs or win 7 and Ubuntu with fresh repos so I can mate a theme for trwp and for my site
Sent from my Wildfire S A510e using Tapatalk 2

aospa 3+ porting

i have tried to port aospa 3+ rom on the base of shpongle rom by 1cebox and i did it https://www.dropbox.com/s/q3lk2d89dp5uvuk/rom_unsigned.zip
but the thing is it stuck at paranoid boot animation logo, hope some can help to port this rom successfully

is it gsm or cdma?

vic126 said:
is it gsm or cdma?
Click to expand...
Click to collapse
gsm

that leaves me out im cdma

the awkward moment is when htc wildfire has aospa 3+ working on it and we are still lagging behind

Are you using the 42 hellboy kernel?

MameTozhio said:
Are you using the 42 hellboy kernel?
Click to expand...
Click to collapse
yea m using 4.2 hellboy even the rom got boot but stuck at boot animation

@1ceb0x help

Take a boot logcat so someone can help :thumbup:
Sent from my One V using xda app-developers app

mr_nooby said:
Take a boot logcat so someone can help :thumbup:
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
logcat

Now let's wait, as i don't know anything about it
Sent from my One V using xda app-developers app

anyone ??

I'm very new to all of this but it would seem (from looking through all the failed module loads) that this section is recurring throughout the load attempt.
[ 06-13 16:01:24.283 3172: 3172 W/InterfaceController ]
Warning (Cannot load library: load_library(linker.cpp:747): library "/system/lib/libnetcmdiface.so" not found) while opening the net interface command library
[ 06-13 16:01:24.594 3171: 3171 I/mediaserver ]
ServiceManager: 0x1e7aed8
[ 06-13 16:01:24.594 3171: 3171 I/AudioFlinger ]
Using default 3000 mSec as standby time.
[ 06-13 16:01:24.594 3171: 3171 E/MediaPlayerFactory ]
Failed to open FACTORY_LIB Error : Cannot load library: load_library(linker.cpp:747): library "libdashplayer.so" not found
Click to expand...
Click to collapse
Now knowing little about Java and less about AOSP itself it would seem that the command interface and dashboard player aren't loading. I would start by looking into these modules and the ones that call it.
Just trying to help

mcgi5sr2 said:
I'm very new to all of this but it would seem (from looking through all the failed module loads) that this section is recurring throughout the load attempt.
Now knowing little about Java and less about AOSP itself it would seem that the command interface and dashboard player aren't loading. I would start by looking into these modules and the ones that call it.
Just trying to help
Click to expand...
Click to collapse
so what should i do now?? actually i tried to port it from samsung galaxy nexus because we people still don't have aospa

gulsher said:
so what should i do now?? actually i tried to port it from samsung galaxy nexus because we people still don't have aospa
Click to expand...
Click to collapse
Sorry well out of my league

Find all the .so files mentioned and add them. You probably messed up somewhere
Sent from my Samsung Galaxy S 3 using Tapatalk 4 Beta

cpu999 said:
Find all the .so files mentioned and add them. You probably messed up somewhere
Sent from my Samsung Galaxy S 3 using Tapatalk 4 Beta
Click to expand...
Click to collapse
sorry but i couldn't find these mentioned files anywhere, not even the base rom or port rom

Your trying to Port a ROM from a device that doesn't even resemble ours. Try finding an AOSPA ROM for a device with a similar CPU and screen size. For example the Incredible S.
Sent from my One V using xda premium

reV17 said:
Your trying to Port a ROM from a device that doesn't even resemble ours. Try finding an AOSPA ROM for a device with a similar CPU and screen size. For example the Incredible S.
Sent from my One V using xda premium
Click to expand...
Click to collapse
desire s don't have aospa 3+ not even in htc desire s nd desire x but htc wildfires has aospa3+ working on it

Porting from other phones won't work except HTC ones
The porting is easy via a simple guide
Building a fully working rom is a whole different story
PS. Dont worry 1ce hasnt forgotten abt u guys :good:

Compile of CM12.1 error

Hi devs,
I would like to ask you about this problem:
Many times I have compiled succesfully CM ROM (12.1) without any problems. Compiles still the same (same machine, same OS, ...) and since yesterday I get this error. I can not solve it. Please, does anyone know what to do?
Thanks in advance.
Code:
target Strip: recovery (/root/android/system/out/target/product/endeavoru/obj/EXECUTABLES/recovery_intermediates/recovery)
----- Making recovery image ------
Copying baseline ramdisk...
Modifying ramdisk contents...
cp: nelze získat informace o*„/root/android/system/out/target/product/endeavoru/root/init.recovery.*.rc“: Adresář nebo soubor neexistuje
make: [/root/android/system/out/target/product/endeavoru/ramdisk-recovery.img] Error 1 (ignored)
/root/android/system/out/target/product/endeavoru/recovery.img maxsize=8562048 blocksize=4224 total=7170048 reserve=88704
Made recovery image: /root/android/system/out/target/product/endeavoru/recovery.img
target Java: org.cyanogenmod.platform.sdk (/root/android/system/out/target/common/obj/JAVA_LIBRARIES/org.cyanogenmod.platform.sdk_intermediates/classes)
javac: file not found: /root/android/system/out/target/common/obj/APPS/org.cyanogenmod.platform-res_intermediates/src/cyanogenmod/platform/Manifest.java
Usage: javac <options> <source files>
use -help for a list of possible options
make: *** [/root/android/system/out/target/common/obj/JAVA_LIBRARIES/org.cyanogenmod.platform.sdk_intermediates/classes-full-debug.jar] Error 41
#### make failed to build some targets (03:30 (mm:ss)) ####

Same error here. Ask if they solved it.
http://forum.xda-developers.com/galaxy-s5/help/kltechnduos-compile-error-t3134865

Unfortunatelly, still no reply on linked thread
Sent from my HTC One X using XDA Free mobile app

I have the same error, see if someone can help us

Which Java do you build with?
Kitkat: Java 6
Lollipop: Java1.7
Did you try to make clean or clobber or simply "rm -rf out" ?

teemo said:
Which Java do you build with?
Kitkat: Java 6
Lollipop: Java1.7
Did you try to make clean or clobber or simply "rm -rf out" ?
Click to expand...
Click to collapse
Using Java 1.7 from time of first build CM 12.1. No problem with it till now. Yes, tried rm -rf out, I got same error after almost 4 hours of building. Sorry, I'm noob, so I don't know, what "make clean" or "clobber" is.
Sent from my HTC One X using XDA Free mobile app

milda25 said:
Using Java 1.7 from time of first build CM 12.1. No problem with it till now. Yes, tried rm -rf out, I got same error after almost 4 hours of building. Sorry, I'm noob, so I don't know, what "make clean" or "clobber" is.
Sent from my HTC One X using XDA Free mobile app
Click to expand...
Click to collapse
I don't remember the difference of clean and clobber, they delete old files before compiling. But rm rf out does the same, just faster.
Is there other errors above or is it only this error 41?

teemo said:
I don't remember the difference of clean and clobber, they delete old files before compiling. But rm rf out does the same, just faster.
Is there other errors above or is it only this error 41?
Click to expand...
Click to collapse
All errors is in my initial post. First error is error 1. Don't know if this errors depends one on second ...
Sent from my HTC One X using XDA Free mobile app

milda25 said:
Hi devs,
I would like to ask you about this problem:
Many times I have compiled succesfully CM ROM (12.1) without any problems. Compiles still the same (same machine, same OS, ...) and since yesterday I get this error. I can not solve it. Please, does anyone know what to do?
Thanks in advance.
Code:
target Strip: recovery (/root/android/system/out/target/product/endeavoru/obj/EXECUTABLES/recovery_intermediates/recovery)
----- Making recovery image ------
Copying baseline ramdisk...
Modifying ramdisk contents...
cp: nelze získat informace o*„/root/android/system/out/target/product/endeavoru/root/init.recovery.*.rc“: Adresář nebo soubor neexistuje
make: [/root/android/system/out/target/product/endeavoru/ramdisk-recovery.img] Error 1 (ignored)
/root/android/system/out/target/product/endeavoru/recovery.img maxsize=8562048 blocksize=4224 total=7170048 reserve=88704
Made recovery image: /root/android/system/out/target/product/endeavoru/recovery.img
target Java: org.cyanogenmod.platform.sdk (/root/android/system/out/target/common/obj/JAVA_LIBRARIES/org.cyanogenmod.platform.sdk_intermediates/classes)
javac: file not found: /root/android/system/out/target/common/obj/APPS/org.cyanogenmod.platform-res_intermediates/src/cyanogenmod/platform/Manifest.java
Usage: javac <options> <source files>
use -help for a list of possible options
make: *** [/root/android/system/out/target/common/obj/JAVA_LIBRARIES/org.cyanogenmod.platform.sdk_intermediates/classes-full-debug.jar] Error 41
#### make failed to build some targets (03:30 (mm:ss)) ####
Click to expand...
Click to collapse
At your sorce dir, go to vedor/cmsdk, then run:
git reset --hard
After it finishes, go back to your source folder and run:
repo sync
That fixed that exact same error for me. It feels like there's some commit not going through when you simply do a repo sync or something..
Credits where they're due: http://forum.datadevelopement.com/o...building-lollipop-oneplus-one-t2947949/page37
Good luck!

Are you doing forced sync?
These days we sometimes need to
repo sync --forced-sync

@bigtor_gj, @teemo Thanks for the tips, will try ASAP and send a feedback.
Sent from my HTC One X using XDA Free mobile app

biktor_gj said:
At your sorce dir, go to vedor/cmsdk, then run:
git reset --hard
After it finishes, go back to your source folder and run:
repo sync
That fixed that exact same error for me. It feels like there's some commit not going through when you simply do a repo sync or something..
Credits where they're due: http://forum.datadevelopement.com/o...building-lollipop-oneplus-one-t2947949/page37
Good luck!
Click to expand...
Click to collapse
Code:
target Java: org.cyanogenmod.platform.sdk (/home/rafitcu/Android/Cm12.1/out/target/common/obj/JAVA_LIBRARIES/org.cyanogenmod.platform.sdk_intermediates/classes)
javac: file not found: /home/rafitcu/Android/Cm12.1/out/target/common/obj/APPS/org.cyanogenmod.platform-res_intermediates/src/cyanogenmod/platform/Manifest.java
Usage: javac <options> <source files>
use -help for a list of possible options
make: *** [/home/rafitcu/Android/Cm12.1/out/target/common/obj/JAVA_LIBRARIES/org.cyanogenmod.platform.sdk_intermediates/classes-full-debug.jar] Error 41
#### make failed to build some targets (02:02:04 (hh:mm:ss)) ####
No solved for me

Jumping in here - I'm having the same issue building pac for the lg g2. The last successful build I had was on 8/30. Since then, I've gone as far as formatting my build box and reloading ubuntu, then getting a fresh sync - still no success. (I thought it might have been an update to Ubuntu that messed it up)
I'm still looking for a solution as well.

Same last sucessful date here
Sent from my HTC One X using XDA Free mobile app

da_reeseboy said:
Jumping in here - I'm having the same issue building pac for the lg g2. The last successful build I had was on 8/30. Since then, I've gone as far as formatting my build box and reloading ubuntu, then getting a fresh sync - still no success. (I thought it might have been an update to Ubuntu that messed it up)
I'm still looking for a solution as well.
Click to expand...
Click to collapse
milda25 said:
Same last sucessful date here
Sent from my HTC One X using XDA Free mobile app
Click to expand...
Click to collapse
You have given me an idea, I am testing a solution and so far it seems to work, if the compilation ends successfully, the share here.

Unfortunately, git reset --hard and repo sync --force-sync doesn't solved the problem. Still same error on same position of building

What java version is everyone using? Run java -version and put the results here.
Code:
[email protected]:~$ java -version
Picked up JAVA_TOOL_OPTIONS: -javaagent:/usr/share/java/jayatanaag.jar
java version "1.7.0_79"
OpenJDK Runtime Environment (IcedTea 2.5.6) (7u79-2.5.6-0ubuntu1.15.04.1)
OpenJDK 64-Bit Server VM (build 24.79-b02, mixed mode)

I switched from OpenJDK to Oracle's JDK... no difference. I just found the vm I started building on in July, untouched with no updates done. I will resync and try a build on it to see if its an update to one of the packages installed for building that is causing the issue.
...This will take some time...

http://forum.cyanogenmod.org/topic/115010-build-fails-javac/
Edit: Is THIS your issue ?

teemo said:
http://forum.cyanogenmod.org/topic/115010-build-fails-javac/
Edit: Is THIS your issue ?
Click to expand...
Click to collapse
Thank you for the responses - those are both along the lines of the issue. The first post never mentioned what he deleted tho. The second one is definitely related as I can make it further in my build before failing when I revert that commit, but it still fails.
As few posts as there are online about having this issue, I don't think a commit is directly causing it, otherwise there wouldn't be any successful builds from anyone for the last couple weeks. I think its related to a security update that a few of us did, and most of the devs don't update if its not broken lol. I should know this afternoon...
Edit: I mean its an incompatibility between the changes to cmsdk and some security update I did.

[KERNEL] Kerneldevelopment

Hello.
This is a try to keep other thread clean. Please post everything regarding kerneldevelopment in this thread.
Github: Original Elephone P9000 Kernel
Github: Forked Kernel by vsrookie
Github: Forked Kernel by @BlueFlame4
In BlueFlames kernelsources are already commits. These commits, correct wrong includes. Without you can't compile the kernel.
Thank you!
greeting
vsrookie

@BlueFlame4
I compiled the kernel with another cmdline:
Code:
console=tty0 console=ttyMT0,921600n1 root=/dev/ram vmalloc=496M slub_max_order=0 slub_debug=O androidboot.hardware=mt6755 androidboot.verifiedbootstate=green bootopt=64S3,32N2,64N2 lcm=1-R63315_GWMD13752A_drv fps=5540 vram=29229056 printk.disable_uart=1 bootprof.pl_t=658 bootprof.lk_t=2992 boot_reason=4 androidboot.serialno=K7CUOZJRJBAERG5D androidboot.bootreason=wdt_by_pass_pwk gpt=1 usb2jtag_mode=0
This is taken from /proc/cmdline.
The resulting kmsg is something weired. http://grork.lohnadmin.de/kernel/lstkms.txt
greetings
vsrookie
Ps: @BlueFlame4
I've testes your kernel also. This one:
BlueFlame4 said:
Here's a testkernel. I am pretty sure it will not boot. If it crashes, please reboot into recovery and post /proc/last_kmsg here. I just repacked stock boot.img with p9000_defconfig kernel.
http://d-h.st/clHI
Click to expand...
Click to collapse
As expected it didnt boot. Here is the last_kmsg from this.
http://grork.lohnadmin.de/kernel/test.txt
It looks like there is any encoding problem, or?
greetings
vsrookie

It looks like the video driver is crashing:
Code:
BUG: failure at /homeproject3/25%/2000706_c238_dx-andrOid+alps/kdrnel-3.18/drivers.misc/mediat%k/video/mt6755/dirp3ys/ddp[manafer.c:1616/dpmgr_ah%ck_stAtus

BlueFlame4 said:
It looks like the video driver is crashing:
Code:
BUG: failure at /homeproject3/25%/2000706_c238_dx-andrOid+alps/kdrnel-3.18/drivers.misc/mediat%k/video/mt6755/dirp3ys/ddp[manafer.c:1616/dpmgr_ah%ck_stAtus
Click to expand...
Click to collapse
I compile it with another cmdline to see what happens. I will leave the "lcm"-Parameter.
Two lines above in the kmsg there is:
Code:
[0.617501] (7)Y12swapper/0][DISP][disp^lcm_prbe #219]EBROR:[email protected] EROR: aan't found lcm drIver*R63315_GWMD3752A_drv�in linux kerNel driver [ 0.607528] (7)[0:swapp%r/ ][DISP][disp_lcm_probe #029]ERROP:[email protected]@L ERROR!!!Fo LCM Driver defined
greetings
vsrookie
Sent from my P9000 using XDA-Developers mobile app

Oddly enough the mt65xx_lcm_list.c is prebuilt as well as many other .c files which normally are not. Even every single LCM driver is prebuilt... I would say that Elephone wants to screw us but from my past experience with them it is more likely that they just have no clue what they are doing
Luckily we have other 6.0 sources (for example from Vernee) so we could reverse engineer them but I want to avoid that for now. I attached a new version of the kernel with a possible fix for the crash implemented. Let me know if it boots please
http://d-h.st/6hwF

BlueFlame4 said:
Oddly enough the mt65xx_lcm_list.c is prebuilt as well as many other .c files which normally are not. Even every single LCM driver is prebuilt... I would say that Elephone wants to screw us but from my past experience with them it is more likely that they just have no clue what they are doing
Luckily we have other 6.0 sources (for example from Vernee) so we could reverse engineer them but I want to avoid that for now. I attached a new version of the kernel with a possible fix for the crash implemented. Let me know if it boots please
http://d-h.st/6hwF
Click to expand...
Click to collapse
Yepp, just grep for project3. You will see all shipped drivers.
Your kernel dont boot. There is also a one line last_kmsg. Strange. Only ram console header, hw_status: 0, fiq step 0.
Did you compile with the original cmdline?
greetings
vsrookie
EDIT:
Compiled without lcm Parameter, also same problem. last_kmsg

I used the default cmdline, yeah. Essentially I just repacked the stock boot.img without changing anything else than the kernel.

BlueFlame4 said:
I used the default cmdline, yeah. Essentially I just repacked the stock boot.img without changing anything else than the kernel.
Click to expand...
Click to collapse
Hi.
I've a last_kmsg that is readable! It took even longer till crash.
What I've done:
I've setted up a user project3 and put the sources into a directory you have to create:
Code:
/home/project3/6755/20160706_c239_dx/android/alps/kernel-3.18/
Also you have to put the correct config_cmdline in your config. (look in second post).
Hope that will help other so that we have a running kernel.
greetings
vsrookie
Sent from my P9000 using XDA-Developers mobile app

Good job! Still weird that you have to use a static path but it is MediaTek code so everything is possible I tried to build lcm_list myself like so but then I get linker errors complaining for some "agold_lcm_power_down" symbol. When I grep for it, it is only found in the .shipped files so I think we have a dead end here and we somehow have to use the .shipped files.
What I am seeing from you log is that
Code:
[ 158.303970] (4)[1:init]init: Starting service 'md_monitor'...
[ 158.334455] (4)[264:logd.auditd]type=1400 audit(1469711965.478:374): avc: denied { open } for pid=5690 comm="md_monitor" path="/data/md_mon/mdlog_mon1_config" dev="mmcblk0p28" ino=1589251 scontext=u:r:md_monitor:s0 tcontext=u:object_r:system_data_file:s0 tclass=file permissive=0
[ 158.336867] (4)[1:init]init: Service 'md_monitor' (pid 5690) exited with status 1
[ 158.336890] (4)[1:init]init: Service 'md_monitor' (pid 5690) killing any children in process group
md_monitor crashes which is probably leading to the reboot. Could you boot it permissively (androidboot.selinux=permissive in cmdline) and see if that helps?

BlueFlame4 said:
Good job! Still weird that you have to use a static path but it is MediaTek code so everything is possible I tried to build lcm_list myself like so but then I get linker errors complaining for some "agold_lcm_power_down" symbol. When I grep for it, it is only found in the .shipped files so I think we have a dead end here and we somehow have to use the .shipped files.
What I am seeing from you log is that
Code:
[ 158.303970] (4)[1:init]init: Starting service 'md_monitor'...
[ 158.334455] (4)[264:logd.auditd]type=1400 audit(1469711965.478:374): avc: denied { open } for pid=5690 comm="md_monitor" path="/data/md_mon/mdlog_mon1_config" dev="mmcblk0p28" ino=1589251 scontext=u:r:md_monitor:s0 tcontext=u:object_r:system_data_file:s0 tclass=file permissive=0
[ 158.336867] (4)[1:init]init: Service 'md_monitor' (pid 5690) exited with status 1
[ 158.336890] (4)[1:init]init: Service 'md_monitor' (pid 5690) killing any children in process group
md_monitor crashes which is probably leading to the reboot. Could you boot it permissively (androidboot.selinux=permissive in cmdline) and see if that helps?
Click to expand...
Click to collapse
I am tested my kernel on cm with permissive selinux, same

Deepflex said:
I am tested my kernel on cm with permissive selinux, same
Click to expand...
Click to collapse
Hi.
Have you compiled your own, or is it stock? How did you compiled it. (Toolchain, cmdline, config?)
Thank you for reply.
greetings
vsrookie
Sent from my P9000 using XDA-Developers mobile app

vsrookie said:
Hi.
Have you compiled your own, or is it stock? How did you compiled it. (Toolchain, cmdline, config?)
Thank you for reply.
greetings
vsrookie
Sent from my P9000 using XDA-Developers mobile app
Click to expand...
Click to collapse
Hi.
In sources of CM

Hi!
Hi!
The last last_kmsg wasnt correct i think, but this is a really nice one.
Its readable and from boot.
last_kmsg
There are at least three really big problems with the kernel sources:
1. incorrect sources; you have to do too much to compile a kernel.
2. incomplete; at least three drivers are missing:
Code:
/home/project3/6755/20160706_c239_dx/android/alps/kernel-3.18/drivers/misc/mediatek/base/power/ppm_v1/src/mt_ppm_main.c
/home/project3/6755/20160706_c239_dx/android/alps/kernel-3.18/drivers/misc/mediatek/agold_pm_info/agold_pm_info.c
/home/project3/6755/20160706_c239_dx/android/alps/kernel-3.18/drivers/misc/mediatek/agold_hw_compatible/agold_hw_compatible.c
3. most drivers are compiled binaries
Cause this is fun to me, i ill go on!
greetings
vsrookie

vsrookie said:
Hi!
Hi!
The last last_kmsg wasnt correct i think, but this is a really nice one.
Its readable and from boot.
last_kmsg
There are at least three really big problems with the kernel sources:
1. incorrect sources; you have to do too much to compile a kernel.
2. incomplete; at least one driver is missing:
[CODEt/home/project3/6755/20160706_c239_dx/android/alps/kernel-3.18/drivers/misc/mediatek/base/power/ppm_v1/src/mt_ppm_main.c
[/CODE]
3. most drivers are compiled binaries
Cause this is fun to me, i ill go on!
greetings
vsrookie
Click to expand...
Click to collapse
Welcome to the world of MediaTek! I had the same problems with a Kazam device I got at XDA DevCon a couple of years ago - the company sent me the source code to play with and it was horrendous, gave up on it in the end :laugh:
Sent from my Elephone P9000 using XDA Labs

Jonny said:
Welcome to the world of MediaTek! I had the same problems with a Kazam device I got at XDA DevCon a couple of years ago - the company sent me the source code to play with and it was horrendous, gave up on it in the end :laugh:
Sent from my Elephone P9000 using XDA Labs
Click to expand...
Click to collapse
Thats not very encouraging. Maybe they will release some more infos or sources.... I dont give up... at least the hope!
greetings
vsrookie
PS: Why isnt this a Sony Phone!?

Unlock bootloader and try your kernel

Deepflex said:
Unlock bootloader and try your kernel
Click to expand...
Click to collapse
Hi.
At present i'm struggeling with lcmdriver. I have to find the correct initialization for it. I think if I find it, then its a little milestone.
Kernel want to boot, but screen fades out slowly with no kernelpanic.
So far, I've replaced many shipped drivers with sourcecode from other devices. Looks good till now.
kmsg will print proper messages without any other weird codecs.
Do you have sources for uboot?
greetings
vsrookie
Sent from my P9000 using XDA-Developers mobile app

vsrookie said:
Hi.
At present i'm struggeling with lcmdriver. I have to find the correct initialization for it. I think if I find it, then its a little milestone.
Kernel want to boot, but screen fades out slowly with no kernelpanic.
So far, I've replaced many shipped drivers with sourcecode from other devices. Looks good till now.
kmsg will print proper messages without any other weird codecs.
Do you have sources for uboot?
greetings
vsrookie
Sent from my P9000 using XDA-Developers mobile app
Click to expand...
Click to collapse
Hi!
Go to settings/about phone/and enable developer settings, after, go to developers settings and choose "Factory Unlock (unlocking the bootloader)"

Deepflex said:
Hi!
Go to settings/about phone/and enable developer settings, after, go to developers settings and choose "Factory Unlock (unlocking the bootloader)"
Click to expand...
Click to collapse
Hi. There is no option for that. Only "OEM UNLOCKING" (allow the bootloader to be unlocked).
Also if I use fastboot OEM unlock, I can't use volume up? Anyone tried to unlock bootloader?
greetings
vsrookie
Sent from my P9000 using XDA-Developers mobile app