[WIP]Make KitKat run on new 4.3 kernel source - Sony Xperia T, TL, TX, V

Since Sony has added new v45 Adreno graphics driver in .295,I think it will be good to compile a CM-like kernel and chances are that we can fix the blue flickers in this way.However,when I mananged to get the zImage booting CM properly(no reboot),I found the screen froze at Sony logo.In the logcat I can see the system is waiting for media.audio_policy,and BootAnim,or the whole display system, isn't working.though all the Adreno libs are loaded properly and the screen param is read correctly.
Related logcat:
Code:
E/Adreno-EGLSUB( 237): <CreateImage:1837>: Offset beyond buffer size.
W/Adreno-EGL( 237): <qeglDrvAPI_eglCreateImageKHR:4637>: EGL_BAD_PARAMETER
E/GLConsumer( 237): [BootAnimation] error creating EGLImage: 0x300c
W/GLConsumer( 237): [BootAnimation] updateAndRelease: unable to createImage on display=0x1 slot=0
E/qdhwcomposer( 237): Failed to call ioctl MSMFB_OVERLAY_SET err=Invalid argument
// And there are some "MDP: unknown ioctl (....)" errors in dmesg
Code:
I/ServiceManager( 670): Waiting for service media.audio_policy...
I/ServiceManager( 670): Waiting for service media.audio_policy...
I/ServiceManager( 670): Waiting for service media.audio_policy...
I/ServiceManager( 670): Waiting for service media.audio_policy...
I/ServiceManager( 670): Waiting for service media.audio_policy...
W/AudioSystem( 670): AudioPolicyService not published, waiting...
W/libc ( 236): WARNING: generic atexit() called from legacy shared library
I'm using Liquid Smooth 20140223(based on CM).And replaced the following files with stock 295.The other files are untouched.Now logcat shows nearly no error other than the ones mentioned above.
/system/etc/firmware/*
/system/etc/audio_policy.conf
/system/etc/sysmon.cfg
Click to expand...
Click to collapse
And here is how to update the Adreno libs in the system:
1.Delete these files
/system/lib/egl/* (except egl.cfg)
/system/lib/libC2D2.so
/system/lib/libc2d2_a3xx.so
/system/lib/libc2d2_z180.so
/system/lib/libgsl.so
/system/lib/libllvm-a3xx.so
/system/lib/libllvm-arm.so
/system/lib/libOpenCL.so
/system/lib/libOpenVG.so
/system/lib/libsc-a2xx.so
/system/lib/libsc-a3xx.so
Click to expand...
Click to collapse
2.Copy these files from stock 9.2.A.0.295 to the same directory(/system/vendor/lib, /system/lib will not work.)
/system/vendor/lib/egl/*
/system/vendor/lib/libadreno_utils.so
/system/vendor/lib/libC2D2.so
/system/vendor/lib/libc2d2_a3xx.so
/system/vendor/lib/libc2d2_z180.so
/system/vendor/lib/libCB.so
/system/vendor/lib/libgsl.so
/system/vendor/lib/libllvm-a3xx.so
/system/vendor/lib/libllvm-arm.so
/system/vendor/lib/libOpenCL.so
/system/vendor/lib/libOpenVG.so
/system/vendor/lib/libsc-a2xx.so
/system/vendor/lib/libsc-a3xx.so
/system/lib/egl/libGLES_android.so -> /system/lib/egl/
Click to expand...
Click to collapse
3.Boot.You can see all the libs are loaded without any error and driver info is read correctly.
Click to expand...
Click to collapse
And I will attach my kernel config and the full logcat.I didn't save dmesg...sorry...
I'm new to porting Android...Does that mean we need new HALs or something like that?Thanks!

I do not understand in porting Android. Can ask for help in the team FXP?

nnmka said:
I do not understand in porting Android. Can ask for help in the team FXP?
Click to expand...
Click to collapse
They should be already working on this...but any help is welcome

I've already got Kitkat running with 4.3 kernel sources - still no dice with the new Adreno blobs however. See the kernel source https://github.com/chirayudesai/laughing-octo-dangerzone/tree/omni/
As for the audio policy errors - they are what's causing the bootloops - you can fix that by either removing the camera HAL or fully updating it.

tilal6991 said:
I've already got Kitkat running with 4.3 kernel sources - still no dice with the new Adreno blobs however. See the kernel source https://github.com/chirayudesai/laughing-octo-dangerzone/tree/omni/
As for the audio policy errors - they are what's causing the bootloops - you can fix that by either removing the camera HAL or fully updating it.
Click to expand...
Click to collapse
THANKS A LOOOT MAN! :good::laugh:

tilal6991 said:
I've already got Kitkat running with 4.3 kernel sources - still no dice with the new Adreno blobs however. See the kernel source https://github.com/chirayudesai/laughing-octo-dangerzone/tree/omni/
As for the audio policy errors - they are what's causing the bootloops - you can fix that by either removing the camera HAL or fully updating it.
Click to expand...
Click to collapse
I used your source to compile the kernel.When I delete /system/lib/hw/vendor-camera*,booting process moves forward(the screen dims and Xperia logo gets lit,MediaScanner runs.I can even hear SMS notification sound)but there is "InputDispatcher" log spam,indicating that some window isn't responding so further input events are ignored.But after a reboot,there seems to be no problem in the logcat,except for the MSM_FB_OVERLAY/Invaild Argument error.Still nothing displayed on screen.
One weird problem:if I use Adreno libs from CM11,DDMS will grab screenshots correctly.But if stock updated ones are used,DDMS won't grab scrnshot properly.Just some lines on black ground:the attachment shows that.
If I add back the two files from stock 4.3,audio_policy error shows again.Let's see what else should be changed...

Well I've released a new omnirom test build which has everything working (except gps). The props repo is on my github and the patches for device configs are on omnirom gerrit.
Sent from my Xperia T using Tapatalk

tilal6991 said:
Well I've released a new omnirom test build which has everything working (except gps). The props repo is on my github and the patches for device configs are on omnirom gerrit.
Sent from my Xperia T using Tapatalk
Click to expand...
Click to collapse
Maybe replacing the whole arch/arm/mach-msm directory with old OmniROM one will do...I fixed GPS on CM by doing so,one and a half month ago.But I'm not sure which file causes this...

It occurred to me that if I leave CM11 unchanged and boot on 4.3 source,there will be "Bad OVInfo" log spam,which is the same as CM booting on previous Omni kernel...I should have tested the source with OmniROM.But why does CM change the ioctl/HALs? Related files in the kernel are the same...

Well I managed to get 4.3 source working on CM/LS/... roms...Just change "struct mdp_overlay_pp_params" definition in include/linux/msm_mdp.h to
struct mdp_overlay_pp_params {
uint32_t config_ops;
struct mdp_csc_cfg csc_cfg;
struct mdp_qseed_cfg qseed_cfg[2];
};
Click to expand...
Click to collapse
Things will be okay...

Now there is the long-lasting problem...ramdom reboots...I noticed there was some Watchdog:Modem Crashed logs in last_kmsg.I tried replacing /system/etc/firmware with stock one,which resulted in a not booting phone.It got stuck after the Recovery amber light with Sony logo still on screen.ADB is not running,or to say the kernel has died - removing battery with USB plugged in doesn't make the phone shut down.Any idea to upgrade the modem software?

Well I don't have enough time to test now...schoolwork is busy...sorry..

It's OK. I'll wait for it still... The CM11 is better than stock then the reboot issue would need kernel updated to help.
Sent from my Xperia V

@OP
New source have arrived:
http://developer.sonymobile.com/dow...es/open-source-archive-for-build-9-2-a-1-199/
Maybe these are somewhat easier to port :victory:

silasje1 said:
@OP
New source have arrived:
http://developer.sonymobile.com/dow...es/open-source-archive-for-build-9-2-a-1-199/
Maybe these are somewhat easier to port :victory:
Click to expand...
Click to collapse
Thanks~After the busy weeks I'll look into it.

Doesnt FXP usually incorporate the new kernels after Sony releases the source blobs?
Im not sure how long It usually takes them though...

Brewski606 said:
Doesnt FXP usually incorporate the new kernels after Sony releases the source blobs?
Im not sure how long It usually takes them though...
Click to expand...
Click to collapse
Yes.They are working on fusion3 and rhine devices now.Our devices are not active

Got a little free time...tried extract-files.sh,and new baseband is working now.Seems more stable than before...but camera & GPS & WiFi is broken.I have added new GPS blobs into proprieatry-files.txt but no use...logcat shows startFix() error...

You can look my omnirom commits - everything is now working.
Sent from my Xperia T using Tapatalk

tilal6991 said:
You can look my omnirom commits - everything is now working.
Sent from my Xperia T using Tapatalk
Click to expand...
Click to collapse
OK.I will be watching them.Thkx!
(Is light sensor working? Not until I removed /lib/hw/sensors.msm8960.so and pushed stock sensors.default.so did it start to work...no sure if it was my problem only.
And it seems that the stock lights.default.so can take the place of vendor/lib/hw/lights.qcom.so and lib/hw/vendor-lights.default.so. If that's common,we can remove the unnecessary files...)

Related

[Discussion]Building CM10 for p990

To keep my Threat "[GUIDE] Bulding CM9 from Sources for O2X (P990)" clean, I decided to open a new Threat in General Section,
lets use this Threat to discuss about compiling CM10 for the O2X.
thorstenhirsch said:
1. Changed "default revision" in manifest.xml to jellybean.
Code:
manifest.xml: <default revision="refs/heads/jellybean"
Click to expand...
Click to collapse
You have to download the jellybean sourcecode,
possibly it`s better to init the sources to a different folder e.g. /CM10/android/system
if you want to keep the CM9 sources, too.
Code:
cd ~/CM10/android/system/
Code:
repo init -u git://github.com/CyanogenMod/android.git -b jellybean
you have to create all files for yellybean which are added to local_manifest.xml, or find jellybean branches for those files on github, (I don`t know if there are jellybean branches for our O2X, I didn`t searched for it)
When removing all entries from local_manifest.xml "repo sync" works at least. But well... I think now I've got the same as I had after "repo init [...] -b jellybean". So I still need jellybean-ed repos for /system/device/lge/star-common and p990. Guess I start with the CM9 versions...
That`s exactly what I mean,
without the necessary working jellybean files, it makes no sense to try building CM10 for O2X,
except you are able to create the necessary working jellybean files by yourself,
Stuck with this:
Code:
device/lge/star-common/include/media/MediaPlayerInterface.h:165:25: note: virtual void android::MediaPlayerBase::sendEvent(int, int, int)
device/lge/star-common/include/media/MediaPlayerInterface.h:165:25: note: candidate expects 3 arguments, 4 provided
This is the code line:
Code:
158 virtual status_t getMetadata(const media::Metadata::Filter& ids,
159 Parcel *records) {
160 return INVALID_OPERATION;
161 };
162
163 virtual status_t setLGAudioEffect(int ) { return NO_ERROR; };
164
165 virtual void sendEvent(int msg, int ext1=0, int ext2=0) { if (mNotify) mNotify(mCookie, msg, ext1, ext2); }
Any ideas of how to avoid this?
Hey.
Without some serious modifications or to be more precisely hacks. Like the one introduced in cm9 and more. Like disabling and hacking around the project butter features. Like dealing with the vsync etc.
Anyway. Without these features a cm10 build doesn't make sense at all. Just more hacks and instabilities. It won't run better than the cm9 builds and the biggest improvement is the smoothness. The other stuff isn't worth the update. Without a OEM update to ICS a jb build isn't worth the amount of work. Not even the compile time. Sorry to say that. (And yeah I looked into it and had some progress. However it's not worth the time.)
Sent from my Nexus S using xda app-developers app
Benee said:
Hey.
Without some serious modifications or to be more precisely hacks. Like the one introduced in cm9 and more. Like disabling and hacking around the project butter features. Like dealing with the vsync etc.
Anyway. Without these features a cm10 build doesn't make sense at all. Just more hacks and instabilities. It won't run better than the cm9 builds and the biggest improvement is the smoothness. The other stuff isn't worth the update. Without a OEM update to ICS a jb build isn't worth the amount of work. Not even the compile time. Sorry to say that. (And yeah I looked into it and had some progress. However it's not worth the time.)
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
Yeah, i think all we know that. But i'm trying to make it with educational purpouses. I don't want to make a ROM with graphic acceleration and the other stuff that didn't work in cm9, cause it's impossible.
The only one thing i'mt trying is to bake some from sources and make it run on my phone. And maybe make a start point to make my roms for personal use.
If anyone want to help, i would be greatfull. If you don't want to help, it's ok. Probably you have better things to do xD.
Cya
ethansp said:
Stuck with this:
Code:
device/lge/star-common/include/media/MediaPlayerInterface.h:165:25: note: virtual void android::MediaPlayerBase::sendEvent(int, int, int)
device/lge/star-common/include/media/MediaPlayerInterface.h:165:25: note: candidate expects 3 arguments, 4 provided
This is the code line:
Code:
158 virtual status_t getMetadata(const media::Metadata::Filter& ids,
159 Parcel *records) {
160 return INVALID_OPERATION;
161 };
162
163 virtual status_t setLGAudioEffect(int ) { return NO_ERROR; };
164
165 virtual void sendEvent(int msg, int ext1=0, int ext2=0) { if (mNotify) mNotify(mCookie, msg, ext1, ext2); }
Any ideas of how to avoid this?
Click to expand...
Click to collapse
You need to update this file to JB. It's currently based on the ICS MediaPlayerInterface.h and then you need some audio hacks (the shim by arcee).
With the above I was talking about: Without these hacks the build will run worser than a sdk port. Unusable worse. Even with dev spirit it was just a temp flash.
Benee said:
You need to update this file to JB. It's currently based on the ICS MediaPlayerInterface.h and then you need some audio hacks (the shim by arcee).
With the above I was talking about: Without these hacks the build will run worser than a sdk port. Unusable worse. Even with dev spirit it was just a temp flash.
Click to expand...
Click to collapse
Yes, probably you have all the reason about this. But, if i can taking some advantages in the developing of a "experimental" build waiting for some sources from nvidia/LGE an then implement it. I think the work is not going all to trash. Maybe in the future, can we use it, probably not. Ok. But if people want, what is the inconvenience of "loosing" time trying to make it work?
Cya.
Ok, i've do some advances, now logcat is running but stuck on 2nd lg boot logo.
If want to know the changes i have make: https://github.com/ethansp
And the logcat: http://pastebin.com/SZGwM0Xm
The errors i've seen:
Code:
E/libEGL ( 1175): eglGetDisplay:121 error 300c (EGL_BAD_PARAMETER)
E/libEGL ( 1175): eglInitialize:137 error 3008 (EGL_BAD_DISPLAY)
E/libEGL ( 1175): validate_display:209 error 3008 (EGL_BAD_DISPLAY)
E/libEGL ( 1175): validate_display:209 error 3008 (EGL_BAD_DISPLAY)
F/libc ( 1175): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 1192 (SurfaceFlinger)
Code:
D/dalvikvm( 1176): DexOpt: incorrect opt magic number (0xff ff ff ff)
D/dalvikvm( 1176): ODEX file is stale or bad; removing and retrying (/data/dalvik-cache/[email protected]@[email protected])
Code:
I/ServiceManager( 1008): service 'media.audio_flinger' died
I/ServiceManager( 1008): service 'media.player' died
I/ServiceManager( 1008): service 'media.camera' died
I/ServiceManager( 1008): service 'media.audio_policy' died
Just a few ideas...
Regarding the EGL errors: probably some of the proprietary vendor files are missing (check /bin, /etc, /lib) or not included correctly.
The audio errors are most likely the result of the changes Google made to the audio system of JB. If these errors are critical to booting try compiling the rom without audio.
Good luck and keep on trying!
Have a nice day!
ethansp said:
Ok, i've do some advances, now logcat is running but stuck on 2nd lg boot logo.
If want to know the changes i have make: https://github.com/ethansp
And the logcat: http://pastebin.com/SZGwM0Xm
The errors i've seen:
Code:
E/libEGL ( 1175): eglGetDisplay:121 error 300c (EGL_BAD_PARAMETER)
E/libEGL ( 1175): eglInitialize:137 error 3008 (EGL_BAD_DISPLAY)
E/libEGL ( 1175): validate_display:209 error 3008 (EGL_BAD_DISPLAY)
E/libEGL ( 1175): validate_display:209 error 3008 (EGL_BAD_DISPLAY)
F/libc ( 1175): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 1192 (SurfaceFlinger)
Click to expand...
Click to collapse
EGL issues are related to the missing egl hacks from arcee (here for ics) (I think you need add even more hacks than in ics due to vsync etc.).
ethansp said:
Code:
D/dalvikvm( 1176): DexOpt: incorrect opt magic number (0xff ff ff ff)
D/dalvikvm( 1176): ODEX file is stale or bad; removing and retrying (/data/dalvik-cache/[email protected]@[email protected])
Click to expand...
Click to collapse
This error is related to above error.
ethansp said:
Code:
I/ServiceManager( 1008): service 'media.audio_flinger' died
I/ServiceManager( 1008): service 'media.player' died
I/ServiceManager( 1008): service 'media.camera' died
I/ServiceManager( 1008): service 'media.audio_policy' died
Click to expand...
Click to collapse
Same as above. Your complete egl driver etc is going down.
Raum1807 said:
Just a few ideas...
Regarding the EGL errors: probably some of the proprietary vendor files are missing (check /bin, /etc, /lib) or not included correctly.
The audio errors are most likely the result of the changes Google made to the audio system of JB. If these errors are critical to booting try compiling the rom without audio.
Good luck and keep on trying!
Have a nice day!
Click to expand...
Click to collapse
Getting audio running shouldn't be too difficult. You basically need to add the ics audio shim and make some adjustment to eventual JB changes. It will most likely bug around without working audio (mediaserver is crashing)
EDIT:
Ok. Had a closer look. In CM nearly everything is implemented. Like this for audio and this for egl etc. You just need to update the cam lib, the audio includes and it should boot and work partly.
Benee said:
EGL issues are related to the missing egl hacks from arcee (here for ics) (I think you need add even more hacks than in ics due to vsync etc.).
This error is related to above error.
Same as above. Your complete egl driver etc is going down.
Getting audio running shouldn't be too difficult. You basically need to add the ics audio shim and make some adjustment to eventual JB changes. It will most likely bug around without working audio (mediaserver is crashing)
EDIT:
Ok. Had a closer look. In CM nearly everything is implemented. Like this for audio and this for egl etc. You just need to update the cam lib, the audio includes and it should boot and work partly.
Click to expand...
Click to collapse
Lot of thanks benee for taking some time to watch it.
I have moded the expresions about the storages (changed /mnt/sdcard to /storage/scdcard0 ) and moded de libslights.c in the frameworks. a new logcat and seems very improved. Stays the screen black cause not working properly de egl driver. I'm going to take a look. I think there is a problem with kernel>drivers expresions.
Latest logcat if you want to take a look: http://pastebin.com/L3hjvTEi
ethansp said:
Lot of thanks benee for taking some time to watch it.
I have moded the expresions about the storages (changed /mnt/sdcard to /storage/scdcard0 ) and moded de libslights.c in the frameworks. a new logcat and seems very improved. Stays the screen black cause not working properly de egl driver. I'm going to take a look. I think there is a problem with kernel>drivers expresions.
Latest logcat if you want to take a look: http://pastebin.com/L3hjvTEi
Click to expand...
Click to collapse
I've send you some pull requests. Due to lag of time I havn't compiled them. Hope you can fire up a compile and send me a log and report if you noticed a improvement.
Benee said:
I've send you some pull requests. Due to lag of time I havn't compiled them. Hope you can fire up a compile and send me a log and report if you noticed a improvement.
Click to expand...
Click to collapse
A lot of thanks. i've see it. Doing the compile now. When finish i will post the results.
Hi, no solution. Stills blackscreen, same EGL errors, and i discovered, logcat only work on first boot. if i pull battery off and on, no more logcat until wipes.
I let here the logcat: http://pastebin.com/TH1wCsvV
Thanks for help.
ethansp said:
Hi, no solution. Stills blackscreen, same EGL errors, and i discovered, logcat only work on first boot. if i pull battery off and on, no more logcat until wipes.
I let here the logcat: http://pastebin.com/TH1wCsvV
Thanks for help.
Click to expand...
Click to collapse
Oh sure.. Yeah wait a moment . We need some more ported over changes.
EDIT:
use this this and that instead of the cm ones or cherry-pick the changes.
EDIT2:
Doing some blind RIL changes. Maybe they're working out - currently my girlfriend uses my o2x because her phone got stolen.
EDIT3:
and add frameworks_base. If the phone boots, please send me a adb logcat -b radio. I need the logcat from booting till 30 secs booted up rom. I suggest routing it to a txt file because the log is quite spammy.
EDIT4:
I created a repo for easier syncing: here
Benee said:
Oh sure.. Yeah wait a moment . We need some more ported over changes.
EDIT:
use this this and that instead of the cm ones or cherry-pick the changes.
EDIT2:
Doing some blind RIL changes. Maybe they're working out - currently my girlfriend uses my o2x because her phone got stolen.
EDIT3:
and add frameworks_base. If the phone boots, please send me a adb logcat -b radio. I need the logcat from booting till 30 secs booted up rom. I suggest routing it to a txt file because the log is quite spammy.
Click to expand...
Click to collapse
Ok. I'm at work right now, in 5 hours i go home. Expect results in ~7 hours or tomorrow in morning.
Thanks a lot for all your help.
you're the man benee
Benee said:
Oh sure.. Yeah wait a moment . We need some more ported over changes.
EDIT:
use this this and that instead of the cm ones or cherry-pick the changes.
EDIT2:
Doing some blind RIL changes. Maybe they're working out - currently my girlfriend uses my o2x because her phone got stolen.
EDIT3:
and add frameworks_base. If the phone boots, please send me a adb logcat -b radio. I need the logcat from booting till 30 secs booted up rom. I suggest routing it to a txt file because the log is quite spammy.
EDIT4:
I created a repo for easier syncing: here
Click to expand...
Click to collapse
Ok, phone boots, but the radio logcat only output this:
Code:
D/RILD ( 1011): radio disabled
D/RILB ( 1268): /proc/[email protected] [email protected] loglevel=0 muic_state=1 lpj=9994240 CRC=3010002a8e458d7 vmalloc=256M brdrev=1.0 video=tegrafb console=ttyS0,115200n8 usbcore.old_scheme_first=1 tegraboot=sdmmc tegrapart=recovery:35e00:2800:800,linux:34700:1000:800,mbr:400:200:800,system:600:2bc00:800,cache:2c200:8000:800,misc:34200:400:800,userdata:38700:c0000:800 androidboot.hardware=p990
D/RILB ( 1268): getLteOnCdmaMode=0 curVal=-1 product_type='' lteOnCdmaProductType=''
I have to say, i didn't understand the "edit 3" add frameworks base, where? I have synced it but have to take out from star.mk cause that files now exist only in frameworks/native.
Edit: forgot to say: FC's com.android.phone repeteavly. Tonyp, how did you that? xD
Edit2: Latest logcat without -b radio trigger: http://pastebin.com/ASUyM0vR
When load this service "884.I/SystemServer( 1270): AssetRedirectionManager Service" (you can find it at end of logcat) the logcat stops, is like usb get disabled. If i reboot, no more logcat output until full wipes.
Edit3: took off phone.apk and FC's media, and voice syntethizer.

Re: szezso's CyanVivo 10.2 / PA port problem

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:

[celoxhd][SGH-I757M][CWM Advanced Edition] PhilZ Touch

Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
celoxhd
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Original dev supporter:
http://www.androidfilehost.com/?w=files&flid=12461
Click to expand...
Click to collapse
Huge thanks and credits to @titanic_fanatic
He ported the sources and provided all needed stuff to build it
Excellent, many thanks for all the work you put into this for us. We very much appreciate it
On the topic of bugs, I only have two (but I really don't mind at all). The screenshot works except for the resulting image is wavy coloured lines and no vibration regardless of the setting.
We've never had either, so I'm not missing them at all, but wanted to let you know.
Take care Phil
Sent from my SGH-I757M using XDA Premium 4 mobile app
titanic_fanatic said:
Excellent, many thanks for all the work you put into this for us. We very much appreciate it
On the topic of bugs, I only have two (but I really don't mind at all). The screenshot works except for the resulting image is wavy coloured lines and no vibration regardless of the setting.
We've never had either, so I'm not missing them at all, but wanted to let you know.
Take care Phil
Sent from my SGH-I757M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Added you to credits on the device page in main thread and here in OP :good:
screen shots: forget it, I should disable it once for all on new devices. Sadly, we have no working thing for most new devices. Only some Sammy and the mako did work
vibration: can you provide the path for vibrator?, it should be in kernel drivers I guess. Currently I use:
Code:
/sys/class/timed_output/vibrator/enable
We echo some msec value there and it Bzzzzz for that msec
Phil3759 said:
Added you to credits on the device page in main thread and here in OP :good:
screen shots: forget it, I should disable it once for all on new devices. Sadly, we have no working thing for most new devices. Only some Sammy and the mako did work
vibration: can you provide the path for vibrator?, it should be in kernel drivers I guess. Currently I use:
Code:
/sys/class/timed_output/vibrator/enable
We echo some msec value there and it Bzzzzz for that msec
Click to expand...
Click to collapse
That's the correct path Maybe the driver isn't loading properly... I'll see if I can get a dmesg Log when booting recovery to see if the driver actually loads
Sent from my SGH-I757M using XDA Premium 4 mobile app
Vibrator Fixed
Hey @Phil3759, I did a whole lot of investigating tonight and have figured out and fixed the vibration issue. I discovered that it was trying to load the module from /system/lib/modules/vibrator.ko. This is my roms ko file and is currently for cm10.2. The kerenel I setup for this recovery is our cm11 kernel and uses a different module (compiled against that kernel). It was trying to load the cm10.2 module from my rom into the cm11 kernel which obviously doesn't work, so I split the recovery.img added the correct module at /tmp/system/lib/modules added the necessary lines to init.recovery.qcom.rc and repackaged the kernel and new ramdisk.
I have flashed this and tested it. it works like a charm now Can you replace the version in your repo with this new one?
titanic_fanatic said:
Hey @Phil3759, I did a whole lot of investigating tonight and have figured out and fixed the vibration issue. I discovered that it was trying to load the module from /system/lib/modules/vibrator.ko. This is my roms ko file and is currently for cm10.2. The kerenel I setup for this recovery is our cm11 kernel and uses a different module (compiled against that kernel). It was trying to load the cm10.2 module from my rom into the cm11 kernel which obviously doesn't work, so I split the recovery.img added the correct module at /tmp/system/lib/modules added the necessary lines to init.recovery.qcom.rc and repackaged the kernel and new ramdisk.
I have flashed this and tested it. it works like a charm now Can you replace the version in your repo with this new one?
Click to expand...
Click to collapse
If you update your device tree, it would be even better. That way, my next updates won't be affected again
Phil3759 said:
If you update your device tree, it would be even better. That way, my next updates won't be affected again
Click to expand...
Click to collapse
I just finished updating my device tree with the necessary fixes for the vibrator to work in recovery
https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/6f005f4045551e48adfa0ac228641bf8d6a12128
Also, not that I care, but Amarullz was able to get screenshots working in the latest AromaInstaller (Flamboyan I think). If your interested, maybe ask him what he did to get it to work. He could probably point you to the commits
Take Care
titanic_fanatic said:
I just finished updating my device tree with the necessary fixes for the vibrator to work in recovery
https://github.com/titanic-fanatic/...mmit/6f005f4045551e48adfa0ac228641bf8d6a12128
Also, not that I care, but Amarullz was able to get screenshots working in the latest AromaInstaller (Flamboyan I think). If your interested, maybe ask him what he did to get it to work. He could probably point you to the commits
Take Care
Click to expand...
Click to collapse
Looking at it quickly: why that first extra / at end of copy files?
Also, won't be cleaner to use standard path like /lib/modules?
/tmp can be wiped and modified by installers and recovery
Phil3759 said:
Looking at it quickly: why that first extra / at end of copy files?
Also, won't be cleaner to use standard path like /lib/modules?
/tmp can be wiped and modified by installers and recovery
Click to expand...
Click to collapse
The first / is because it's part of a set of chained product copy files directives:
# Ramdisk
PRODUCT_COPY_FILES += \
device/samsung/celoxhd/ramdisk/init.qcom.usb.rc:root/init.qcom.usb.rc \
# BT firmware
PRODUCT_COPY_FILES += \
device/samsung/celoxhd/firmware/bcm4330B1.hcd:system/etc/firmware/bcm4330B1.hcd \
# Needed for vibrator to work in recovery
PRODUCT_COPY_FILES += \
device/samsung/celoxhd/recovery/root/lib/modules/vibrator.ko:recovery/root/lib/modules/vibrator.ko \
device/samsung/celoxhd/recovery/root/init.recovery.qcom.rc:recovery/root/init.recovery.qcom.rc
Click to expand...
Click to collapse
I did this only to adhere to the existing pattern in my device.mk file, the one appended to the first PRODUCT_COPY_FILES was already there from when I forked the project and took that as being a set of chained commands. If this is wrong, I will change it
I definitely see your point on the /tmp dir. I here the commit that fixes that
https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/61da6be2d60a03797ddc31c0187cc5c62bb3a97a
titanic_fanatic said:
The first / is because it's part of a set of chained product copy files directives:
I did this only to adhere to the existing pattern in my device.mk file, the one appended to the first PRODUCT_COPY_FILES was already there from when I forked the project and took that as being a set of chained commands. If this is wrong, I will change it
I definitely see your point on the /tmp dir. I here the commit that fixes that
https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/61da6be2d60a03797ddc31c0187cc5c62bb3a97a
Click to expand...
Click to collapse
I uploaded 6.01.2 with your fixed vibrator :good:
PRODUCT_COPY_FILES:
Maybe I am wrong, but usually, in make files, only the last element has no trailing /
Code:
# Ramdisk
PRODUCT_COPY_FILES += \
device/samsung/celoxhd/ramdisk/init.qcom.usb.rc:root/init.qcom.usb.rc
xxx-yyy \
zzz-pppp\
last_one
# BT firmware
PRODUCT_COPY_FILES += \
device/samsung/celoxhd/firmware/bcm4330B1.hcd:system/etc/firmware/bcm4330B1.hcd
# Needed for vibrator to work in recovery
PRODUCT_COPY_FILES += \
device/samsung/celoxhd/recovery/root/tmp/system/lib/modules/vibrator.ko:recovery/root/tmp/system/lib/modules/vibrator.ko \
device/samsung/celoxhd/recovery/root/init.recovery.qcom.rc:recovery/root/init.recovery.qcom.rc
Also, just for info, my full gui builds need these, often in cm.mk:
Code:
TARGET_SCREEN_HEIGHT := 1280
TARGET_SCREEN_WIDTH := 720
Phil3759 said:
I uploaded 6.01.2 with your fixed vibrator :good:
PRODUCT_COPY_FILES:
Maybe I am wrong, but usually, in make files, only the last element has no trailing /
Code:
# Ramdisk
PRODUCT_COPY_FILES += \
device/samsung/celoxhd/ramdisk/init.qcom.usb.rc:root/init.qcom.usb.rc
xxx-yyy \
zzz-pppp\
last_one
# BT firmware
PRODUCT_COPY_FILES += \
device/samsung/celoxhd/firmware/bcm4330B1.hcd:system/etc/firmware/bcm4330B1.hcd
# Needed for vibrator to work in recovery
PRODUCT_COPY_FILES += \
device/samsung/celoxhd/recovery/root/tmp/system/lib/modules/vibrator.ko:recovery/root/tmp/system/lib/modules/vibrator.ko \
device/samsung/celoxhd/recovery/root/init.recovery.qcom.rc:recovery/root/init.recovery.qcom.rc
Also, just for info, my full gui builds need these, often in cm.mk:
Code:
TARGET_SCREEN_HEIGHT := 1280
TARGET_SCREEN_WIDTH := 720
Click to expand...
Click to collapse
It seems that the extra \ was introduced in our JB branch and has never been fixed. Various examples in googles repo confirm that you are correct. I have removed the extra \ and added the properties you mentioned above to the cm.mk file. Here is the relevant commit:
https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/6ce5f482d63cd70cf64a3d1428ad2428844e23cb
Hey @Phil3759, I just downloaded and flashed the latest version. Thanks kindly for the update
I see that I made a boo boo and forgot to update the path to the vibrator in the init.recovery.qcom.rc file and so the vibrator isn't loading. I've fixed that with the following commit:
https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/b87b3267d75a0de1bb94f68850ae6986ac4dde92
One other thing, for some reason the background is tiled 4 times as if my devices dimensions were not set correctly. I do have that set in my cm.mk file. Here was the commit for that:
https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/6ce5f482d63cd70cf64a3d1428ad2428844e23cb
Is there somewhere else I'm supposed to specify the device screen dimensions?
Thanks again for the new version and I apologize for missing that path in the init.recovery.qcom.rc.
titanic_fanatic said:
Hey @Phil3759, I just downloaded and flashed the latest version. Thanks kindly for the update
I see that I made a boo boo and forgot to update the path to the vibrator in the init.recovery.qcom.rc file and so the vibrator isn't loading. I've fixed that with the following commit:
https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/b87b3267d75a0de1bb94f68850ae6986ac4dde92
One other thing, for some reason the background is tiled 4 times as if my devices dimensions were not set correctly. I do have that set in my cm.mk file. Here was the commit for that:
https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/6ce5f482d63cd70cf64a3d1428ad2428844e23cb
Is there somewhere else I'm supposed to specify the device screen dimensions?
Thanks again for the new version and I apologize for missing that path in the init.recovery.qcom.rc.
Click to expand...
Click to collapse
About background image:
I think this is the cause:
https://github.com/CyanogenMod/android_device_samsung_celox-common/blob/cm-11.0/celox-common.mk#L45
called here:
https://github.com/titanic-fanatic/...xhd/blob/philz-recovery-cm-11.0/device.mk#L37
Your cm.mk settings are overridden
Maybe just move device resolution from cm.mk to device.mk after Line 37
About the vibrator: do you need exfat through kernel modules? If yes, let me know. It is much faster than fuse. For that, you'll need to compile the kernel with samsung exfat sources. I can guide you for that
Else, link me to what exactly is needed in your kernel for the vibrator to work. If it is just a change in defconfig, I can add it and compile along exfat
Phil3759 said:
About background image:
I think this is the cause:
https://github.com/CyanogenMod/android_device_samsung_celox-common/blob/cm-11.0/celox-common.mk#L45
called here:
https://github.com/titanic-fanatic/...xhd/blob/philz-recovery-cm-11.0/device.mk#L37
Your cm.mk settings are overridden
Maybe just move device resolution from cm.mk to device.mk after Line 37
About the vibrator: do you need exfat through kernel modules? If yes, let me know. It is much faster than fuse. For that, you'll need to compile the kernel with samsung exfat sources. I can guide you for that
Else, link me to what exactly is needed in your kernel for the vibrator to work. If it is just a change in defconfig, I can add it and compile along exfat
Click to expand...
Click to collapse
I see it, and now as you've recommended I reset the values after calling celox-common.mk. The commit is here:
https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/cd44b44b7cbb0ddb3b649ac5c4f8d5d1f51d7998
As for exfat, I will be adding this when I have some time to rebuild this kernel. We can worry about exfat for the next time you do device updates and hopefully I'll have it ready by that time. I have your main thread in my subscriptions, so I'll know when your ready to release a new version and will remind you to sync with my repo at that time
Thanks for catching that issue with screen size
titanic_fanatic said:
I see it, and now as you've recommended I reset the values after calling celox-common.mk. The commit is here:
https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/cd44b44b7cbb0ddb3b649ac5c4f8d5d1f51d7998
As for exfat, I will be adding this when I have some time to rebuild this kernel. We can worry about exfat for the next time you do device updates and hopefully I'll have it ready by that time. I have your main thread in my subscriptions, so I'll know when your ready to release a new version and will remind you to sync with my repo at that time
Thanks for catching that issue with screen size
Click to expand...
Click to collapse
np
Let me know if you need info to add exfat
I will update with the current fixes asap
Phil3759 said:
np
Let me know if you need info to add exfat
I will update with the current fixes asap
Click to expand...
Click to collapse
Can I get a link to these fixes please when you have it ready
titanic_fanatic said:
Can I get a link to these fixes please when you have it ready
Click to expand...
Click to collapse
https://github.com/PhilZ-cwm6/GE-Ed...mmit/a8963ca853cfd88466716f8a25434d5c469a2bb9
It is just adding the exfat folder in drivers and edit the makefile with -y to have it built as static. No need to separate modules
Phil3759 said:
https://github.com/PhilZ-cwm6/GE-Ed...mmit/a8963ca853cfd88466716f8a25434d5c469a2bb9
It is just adding the exfat folder in drivers and edit the makefile with -y to have it built as static. No need to separate modules
Click to expand...
Click to collapse
Excellent. I'll add it soon, it should be a pretty quick process.
Quick question though since we are currently having some issues with random reboots in all of my latest builds of cm-11.0. My kernel was updated at some point, and that's when my builds started having random reboots. They are actually not random, but seem rather consistent.
My question is this, do you think this will affect operation in recovery? I believe the reboots are due to kernel panic from a graphics related issue but am not sure if that will only affect the rom and not recovery.
If this might affect recovery, I think I'll build it as a module so I can just add it to my device tree instead of having to update the entire zImage. This will at least give us the old working kernel with the exfat module included.
What do you think?
Sent from my SGH-I757M using XDA Premium 4 mobile app
titanic_fanatic said:
Excellent. I'll add it soon, it should be a pretty quick process.
Quick question though since we are currently having some issues with random reboots in all of my latest builds of cm-11.0. My kernel was updated at some point, and that's when my builds started having random reboots. They are actually not random, but seem rather consistent.
My question is this, do you think this will affect operation in recovery? I believe the reboots are due to kernel panic from a graphics related issue but am not sure if that will only affect the rom and not recovery.
If this might affect recovery, I think I'll build it as a module so I can just add it to my device tree instead of having to update the entire zImage. This will at least give us the old working kernel with the exfat module included.
What do you think?
Sent from my SGH-I757M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
you'll end up with magic number mismatch errors
There are some hacks to force loading on mismatch, but, in my previous experience, they failed on many devices
the drivers must be compiled along the zImage
Now, why don't we drop to celox-common kernel which seems to work fine on skyrocket and other phones?
Phil3759 said:
you'll end up with magic number mismatch errors
There are some hacks to force loading on mismatch, but, in my previous experience, they failed on many devices
the drivers must be compiled along the zImage
Now, why don't we drop to celox-common kernel which seems to work fine on skyrocket and other phones?
Click to expand...
Click to collapse
It is for the most part the same kernel with the few quirks of my device. More notably is my devices display drivers are mipi s6e8aa0_720hd and had to fork the kernel to apply some fixes to that driver as it's not maintained by cm.
Hmmm. I'll be the guinea pig. I will build with the new kernel and I'll test the recovery before you upload. I just think that the issue might be a memory leak in android causing the kernel to panic (overlay issue) and might not have an effect in recovery since its graphics are very basic.
I'll let you know when it's ready
Sent from my SGH-I757M using XDA Premium 4 mobile app

{wip} slim jim rom

hello exhibit community,
i successfully compiled slim rom for the t599n. i need assisstance with the camera. when i run the camera from the terminal, the results are -->I/ActivityManager( 2129): START u0 {act=android.media.action.IMAGE_CAPTURE flg=0 - Pastebin.com. the camera app disables a few moments after initial boot. the logcat shows -->E/HAL ( 1672): load: module=/system/lib/hw/camera.montblanc.so E/HAL ( - Pastebin.com which is clearly the problem. the error is referencing this -->https://github.com/SlimRoms/frameworks_native/blob/kk4.4-caf/libs/binder/MemoryBase.cpp. i swapped the camera libs from various roms, showing the same result. my guess is, a build with non caf source for native. any advice is greatly appreciated.
brandonabandon said:
hello exhibit community,
i successfully compiled slim rom for the t599n. i need assisstance with the camera. when i run the camera from the terminal, the results are -->I/ActivityManager( 2129): START u0 {act=android.media.action.IMAGE_CAPTURE flg=0 - Pastebin.com. the camera app disables a few moments after initial boot. the logcat shows -->E/HAL ( 1672): load: module=/system/lib/hw/camera.montblanc.so E/HAL ( - Pastebin.com which is clearly the problem. the error is referencing this -->https://github.com/SlimRoms/frameworks_native/blob/kk4.4-caf/libs/binder/MemoryBase.cpp. i swapped the camera libs from various roms, showing the same result. my guess is, a build with non caf source for native. any advice is greatly appreciated.
Click to expand...
Click to collapse
Our device ( included in the STE Novathor family of devices ) requires several ROM level patches in order to function. Thats one of the main reasons why we have very little "official" support. My patches are located here:
https://github.com/Meticulus/android_device_samsung_codinalte/tree/carbon/patches
You may also find some on the slimroms gerrit by @Android-Andi such as this one here:
https://gerrit.slimroms.net/#/c/8269/
BTW, I believe that SlimRom's latest ROM is dubbed "SlimKat" and not "Slim Jim" LOL :laugh:
Meticulus said:
Our device ( included in the STE Novathor family of devices ) requires several ROM level patches in order to function. Thats one of the main reasons why we have very little "official" support. My patches are located here:
https://github.com/Meticulus/android_device_samsung_codinalte/tree/carbon/patches
You may also find some on the slimroms gerrit by @Android-Andi such as this one here:
https://gerrit.slimroms.net/#/c/8269/
BTW, I believe that SlimRom's latest ROM is dubbed "SlimKat" and not "Slim Jim" LOL :laugh:
Click to expand...
Click to collapse
cool. i built caf branch btw, i will cherry pick andi's diff, rebuild, and post results. my slow pc wont complete the build until tommorrow.
http://pastebin.com/cc48puVg <-patch 6 fails
i ported the libs from his slimrom and the camera works. everything works now. i dont have data atm, so testers after he allows me to host.
thanks for pemission to andi. i found a possible bug would like to squash before hosting. i found the sim i recieved with the phone and it is not detected. this is my first gsm device developing for cdma previously. when i tick network settings, screen turns blank and the proccess android.phone quit. if i tick 4g, settings quit. possibly the sim card is no good. i will host the rom tommorrow. got work.
im hosting the rom @ af if anyone is interested in testing http://androidforums.com/galaxy-exh...90-wip-rom-test-slim-jim-rom.html#post6745103. data has yet to be verified. i will update the op when it is. everything else is working.
data fixed^

Anyone else trying to build CyanogenMod 14 ?

I'm working on CM14, after a lot of go through I finally zipped it.
but its not booting up.
I used following Resources
Device Tree - It needs a lot of modifications.
Kernel
Vendor Files
MSM 8996 HALs from CM14 are giving Errors, so I used HALs from OMNI
EngMod: Logcat
Bump!
No one?
WhyOrean said:
Bump!
No one?
Click to expand...
Click to collapse
Unfortunately i cant help but i bump this thread
Thanks for your effortand hope someone helps.
Try port rom 7.0 from one plus 3 with file of miui n leak
Update: Got it booting :highfive:
But it seems like its display needs to be calibrated.
It shuts down after a giving a quick glance.
This time I used Precompiled Binaries from TheMuppets
Also Hardware/qcom/display-caf and Hardware/qcom/media-caf throw errors.
So I used ones from CM13 Branch.
-> Syncing CM14.1, seems like CM14 is abandoned.
WhyOrean said:
Update: Got it booting :highfive:
But it seems like its display needs to be calibrated.
It shuts down after a giving a quick glance.
This time I used Precompiled Binaries from TheMuppets
Also Hardware/qcom/display-caf and Hardware/qcom/media-caf throw errors.
So I used ones from CM13 Branch.
-> Syncing CM14.1, seems like CM14 is abandoned.
Click to expand...
Click to collapse
good job man! :good:
Whoa, that would be great, please keep us informed!

Categories

Resources