Related
This thread's purpose is to off-load off-topic comments, comments about failing compilation, etc. from the main thread located:
http://forum.xda-developers.com/showthread.php?t=803103
please read the thread FROM POST #1 TO THE END before posting
most probably your question has already been asked
otherwise
* use the forum's search function
* use google:
Code:
site:forum.xda-developers.com gt-i9000 cyanogenmod 6.1
==> copy & paste and add your search term
e.g.:
- site:forum.xda-developers.com gt-i9000 cyanogenmod 6.1 ROM
- site:forum.xda-developers.com gt-i9000 cyanogenmod 6.1 ROM Doc Mod
------------------------------------------------------------------------
Which Phones are supported?
GT-I9000 + B/T/M
What about Vibrant, Captivate, Epic, Fascinate?
This version is only for GT-I9000 which means Samsung Galaxy S international.
Is there a list of all known bugs?
http://code.google.c...mod/issues/list
How to report bugs or problems?
- Updater Script failed? Get me the file "/mnt/emmc/cyanogenmod.log" and "/mnt/emmc/format_system.log".
- Was it a hard reboot? Get me the file "/proc/last_kmsg".
- Was it a soft reboot or a "boot loop"? Run "adb logcat" and get me the full output.
- Phone got stuck at white bootscreen? Run "adb shell" and then "mount" and get me the full output.
- http://pastebin.com links preferred
- Please use the issue tracker at http://code.google.c...mod/issues/list whenever possible!
Which Modem should i use?
JPP
How to revert back to a Samsung Rom?
Odin + Repartition. After this you can restore your nandroid backup.
What about sdcard's?
Stock Android doesn't support two sdcard's.
Internal sd: /mnt/emmc
External sd: /mnt/sdcard
I've no external sdcard. What can i do?
Buy one!
Or modify vold.fstab, remove all content and add following lines:
Code:
# internal sdcard
{
mount_deep = 0
ums_path = /sys/devices/platform/s3c-usbgadget/gadget/lun1/file
asec = disable
mbr_policy = skip
}
dev_mount sdcard /mnt/sdcard 1 /devices/platform/s3c-sdhci.0/mmc_host/mmc0
How to build from source?
http://forum.cyanoge...veloper-thread/
My phone is stuck at boot. What to do?
Boot into Recovery and choose: Data wipe / Factory reset
Does CM support rSAP protocol?
No.
Does CM support video calling?
No. Use a market App which can handle this.
Can we use Samsung Dialer or other Apps?
No. But you can install a App from Market that fits your needs.
There's no icon for HSDPA at statusbar?
Yes you're right. But HSDPA is supported but will be shown as 3G.
Is it possible to include Gapps in update.zip?
No, Google denied it.
--------------------------------------------------------------------
Awesome CyanogenMod for the SGS ! Those dudes are fulltime HaXXorZ - right ?
Nope, just normal users like you and me who taught themselves how to port and fix the CyanogenMod sources to make them run on our loved SGS - so give them a break with additional functionality questions
What do you mean by porting ?
use the all-knowing Google or Wikipedia (http://en.wikipedia.org/wiki/Porting)
this means, e.g. that you use the code from the Nexus One and add drivers and other needed stuff to make it work on the Samsung Galaxy S & after that compile it to the language of the SGS and make a ROM out of it (adding more stuff)
So who to ask if I need additional languages and features ?
Ask "upstream" (the developers/guys who develop CyanogenMod)
Where have the ROMs gone to ?
Disappeared - CyanogenMod 6.1 for the SGS currently is NOT for inexperienced "users" - so you need to build it on your own from source
(in fact they moved to cyanogenmod forums but that's NO reason to flood those forums, too, with "stupid", inexperienced/noobish questions)
Why are there less posts on forums.xda-developers.com from the developers than before ?
Inexperienced users scared & annoyed them away with noobish questions
---------------------------------------------------------------------------------------------------------
if you need information how to push stuff and other tasks:
read about android-sdk-windows or android-sdk-linux
there you'll find adb
with which you'll be able to do things like putting your phone into download-mode, push files to it and other nifty moves
People are still using the development thread...
Sent from my GT-I9000 using XDA App
Good idea, the main thread is getting cluttered.
Can someone who has got the cm build ruining do a series of benchmarks
Quadrant with ext2/4
Linpack
Benchmarkpi
Setcpu native bench
Glbench
A video would be great
Sent from my GT-I9000 using XDA App
I just compiled the kernel, but now dunno what to do :S
Yeah I got system.img and kernel... I know you use nandroid but the only nandroid I can find is for the G2. How do I do this bit?
Well idea is to push them to sd-card for ex. /sdcard/clockworkmod/backup/cyanogen
and
create MD5 hashes 'md5sum *img > nandroid.md5' (use adb)
boot to recovery, wipe, restore,boot, apply gapps, boot.
Someone correct me if wrong.
Don't you flash kernel with Odin? And is that before or after applying the nandroid?
jaju123 said:
Yeah I got system.img and kernel... I know you use nandroid but the only nandroid I can find is for the G2. How do I do this bit?
Click to expand...
Click to collapse
if you have a kernel with clockwork-recovery integrated like the ultimate lagfix kernel or the speedmod kernel by hardcore then you allready have nandroid! you just copy the system.img to your sdcard/clockwork/backup/somedir folder. then you freate a nandroid.md5 file with md5sum system.img > nandroid.md5 and your ready to restor. be sure to do a factory reset/wipe before or after and flash the cm-kernel.
edit, @Anteuz: hah, you were faster. and no, you are absolutely right
You can also unaffs the system.img, and make an update.zip, with modem and kernel, and put the gapps in the same zip. I did it this way and its running nicely. No sd ext acess yet tho.
I wonder if its only to add new symlinks in the update script to get the sd ext mounted properly... hmmm
something interesting: i pulled the newest initramfs from aery before and saw that they have changed the mounts from rfs to ext4. i am currently compiling a kernel with ext4 support ... now we only need a update.zip which converts data udn dbdata to ext4 and we are ready to go (or we use ul-kernel to convert...). this should give us another speed boost
Now if I only could be able to compile working system.img, currently it dies of some strange issue like:
PHP:
D/AndroidRuntime( 2587): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
I/AndroidRuntime( 2587): Heap size: -Xmx16m
D/AndroidRuntime( 2587): CheckJNI is OFF
D/dalvikvm( 2587): creating instr width table
E/dalvikvm( 2587): Can't open dex cache '/cache/dalvik-cache/[email protected]@co
[email][email protected][/email]': No such file or directory
I/dalvikvm( 2587): Unable to open or create cache for /system/framework/core.jar
(/cache/dalvik-cache/[email protected]@[email protected])
D/dalvikvm( 2587): Unable to process classpath element '/system/framework/core.j
ar'
E/dalvikvm( 2587): Can't open dex cache '/cache/dalvik-cache/[email protected]@ex
[email][email protected][/email]': No such file or directory
I/dalvikvm( 2587): Unable to open or create cache for /system/framework/ext.jar
(/cache/dalvik-cache/[email protected]@[email protected])
D/dalvikvm( 2587): Unable to process classpath element '/system/framework/ext.ja
r'
E/dalvikvm( 2587): Can't open dex cache '/cache/dalvik-cache/[email protected]@fr
[email][email protected][/email]': No such file or directory
I/dalvikvm( 2587): Unable to open or create cache for /system/framework/framewor
k.jar (/cache/dalvik-cache/[email protected]@[email protected])
D/dalvikvm( 2587): Unable to process classpath element '/system/framework/framew
ork.jar'
E/dalvikvm( 2587): Can't open dex cache '/cache/dalvik-cache/[email protected]@an
[email][email protected][/email]': No such file or directory
I/dalvikvm( 2587): Unable to open or create cache for /system/framework/android.
policy.jar (/cache/dalvik-cache/[email protected]@[email protected])
D/dalvikvm( 2587): Unable to process classpath element '/system/framework/androi
d.policy.jar'
E/dalvikvm( 2587): Can't open dex cache '/cache/dalvik-cache/[email protected]@se
[email][email protected][/email]': No such file or directory
I/dalvikvm( 2587): Unable to open or create cache for /system/framework/services
.jar (/cache/dalvik-cache/[email protected]@[email protected])
D/dalvikvm( 2587): Unable to process classpath element '/system/framework/servic
es.jar'
E/dalvikvm( 2587): ERROR: no valid entries found in bootclasspath '/system/frame
work/core.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/
framework/android.policy.jar:/system/framework/services.jar'
W/dalvikvm( 2587): JNI_CreateJavaVM failed
E/AndroidRuntime( 2587): JNI_CreateJavaVM failed
I/ServiceManager( 2370): service 'media.audio_flinger' died
I/ServiceManager( 2370): service 'media.player' died
I/ServiceManager( 2370): service 'media.camera' died
I/ServiceManager( 2370): service 'media.audio_policy' died
I/ ( 2588): ServiceManager: 0xafb8
E/ALSALib ( 2588): external/alsa-lib/src/control/control.c:902:(snd_ctl_open_nou
pdate) Invalid CTL AndroidOut
W/AudioHardwareALSA( 2588): Unable to attach mixer to device AndroidOut: No such
file or directory
E/ALSALib ( 2588): external/alsa-lib/src/control/control.c:902:(snd_ctl_open_nou
pdate) Invalid CTL AndroidIn
W/AudioHardwareALSA( 2588): Unable to attach mixer to device AndroidIn: No such
file or directory
I/CameraService( 2588): CameraService started: pid=2588
D/AudioHardwareALSA( 2588): openOutputStream called for devices: 0x00000002
D/ALSAModule( 2588): open called for devices 00000002 in mode 0...
I/ALSAModule( 2588): Initialized ALSA PLAYBACK device AndroidPlayback_Speaker_no
rmal
D/AudioFlinger( 2588): setParameters(): io 1, keyvalue routing=2, tid 2590, call
ing tid 2588
I/AudioFlinger( 2588): AudioFlinger's thread 0x263f8 ready to run
D/ALSAModule( 2588): route called for devices 00000002 in mode 0...
It's been a while since I've been compiling anything on *nix. I am mainly Java guy. Anybody have any glue what's going on with that ^^
I do get some drm\java errors when I start build and then it said something about changing api but that got solved with make api something..
Another whisky and another go around.
Right, doesn't the ext4 conversion require an update.zip? I remember Aery saying that over in the other thread I think idk.
Doc is your zip based on the newest source from git with ext4 and everything?
Any chance you could post your zip? I know it might encourage stupid people to flash but that's life I guess...
At least could you write some brief guide on how to do it?
Also I found this on Google, is this the current kernel? http://www.multiupload.com/R6KFORO36L
If Doc could share, I could mirror the zip from my dropbox public folder for a while, so there would be no need to mess with rapid upload or some other annoying file share services.
chambo622 said:
Right, doesn't the ext4 conversion require an update.zip? I remember Aery saying that over in the other thread I think idk.
Doc is your zip based on the newest source from git with ext4 and everything?
Any chance you could post your zip? I know it might encourage stupid people to flash but that's life I guess...
At least could you write some brief guide on how to do it?
Also I found this on Google, is this the current kernel? http://www.multiupload.com/R6KFORO36L
Click to expand...
Click to collapse
My update zip is heavily modded so maybe better to make a new one. i just compiling a new rom with the latest changes.
Yeah I want to be sure he has the latest zip with ext4 stuff and everything going on, if that could be shared that would be great.
Repo sync and building from source takes absolutely forever on slower computers, this would help a lot of people who are "mentally qualified" to run this but don't have the time/horsepower to get it going in a timely fashion.
DocRambone said:
My update zip is heavily modded so maybe better to make a new one. i just compiling a new rom with the latest changes.
Click to expand...
Click to collapse
Thanks Doc, this thing has been chugging for hours on my poor 1.2Ghz Core Solo
chambo622 said:
Thanks Doc, this thing has been chugging for hours on my poor 1.2Ghz Core Solo
Click to expand...
Click to collapse
I am not sure thats its a good idea to post an update.zip. Would be to easy for new users to break things.And the rom devs should have the honour to do this. Its still a beta and some important things is not functional yet.
I wish I could do this. If I manage to get going is a 3GHz core 2 quad enough horsepower? I don't want to start and find out it takes forever :-(
Sent from my GT-I9000 using XDA App
PaulForde said:
I wish I could do this. If I manage to get going is a 3GHz core 2 quad enough horsepower? I don't want to start and find out it takes forever :-(
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
it takes like 60 minutes on my core2Duo 1.6Ghz notebook
DocRambone said:
I am not sure thats its a good idea to post an update.zip. Would be to easy for new users to break things.And the rom devs should have the honour to do this. Its still a beta and some important things is not functional yet.
Click to expand...
Click to collapse
Okay I will keep working on it.
I'm currently building using the instructions on the OP in the main thread which I take it will produce a system.img. Then I can produce the nandroid.md5. If I flash the nandroid and then flash the kernel, reboot, flash gapps, etc. will I be ready to go? Or will this not work since it needs to convert to ext4??
Hi guys, me again,
i just fixed Navigon Select to work with Gingerbread. It needs the replacement of libmedia because some interfaces got incompatible. Now i can finally use onboard Navigation on my CM7
Download
Just replace the file in /system/lib
cheers
Nice job, i don't use navigon just copilote, but I must congratulated you because you are making hardcore coding for HD2 scene.
Thanks
Cooooooooool !!! THX !!!
Ok, doesn't work for me ... :-/
Sent from my HTC HD2 using XDA App
cheezusweezel said:
Ok, doesn't work for me ... :-/
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Tell me what you get on logcat when Navigon starts up.. Using aLogcat from Market for example. And of course.. Update your Navigon Select to the latest version..
pack21 said:
Nice job, i don't use navigon just copilote, but I must congratulated you because you are making hardcore coding for HD2 scene.
Thanks
Click to expand...
Click to collapse
+1 your out of control, dude. Your an 86, just one more than me and you are making some major breakthroughs.. It makes me think I am really doing nothing with my life, lol.. But yeah, keep up the god work, man
Edit: I meant to say "good" work but swype has no problem also praising you it seems
Sent from my HTC HD2 using XDA App
Cool man, you rock!
Going to try to get Navigon to work following your instructions, now that you already fixed GPS.
[OT]:
Do you by chance also know how to fix camcorder for [email protected]?
I'm playing with PPC_SHIFTPDA_V2 [RAM] which i really like. Camcorder is one of the last issues i would like to fix.
[/OT]
Thanks! But no luck for me either!
gauner1986 said:
Tell me what you get on logcat when Navigon starts up.. Using aLogcat from Market for example. And of course.. Update your Navigon Select to the latest version..
Click to expand...
Click to collapse
Sure, latest version installed and logcat is:
I/ActivityThread( 1773): Pub com.navigon.navigator_select.provider.naviprovider: com.navigon.navigator_select.provider.NaviProvider
D/NaviApp ( 1773): pn: com.navigon.navigator_select
D/NaviApp ( 1773): NaviKernel hasn't been started yet, ignore...
D/dalvikvm( 1773): Trying to load lib /data/data/com.navigon.navigator_select/lib/libNavinative.so 0x4051cc28
I/System.out( 1773): Cannot load library: reloc_library[1311]: 147 cannot locate '_ZN7android10AudioTrackC2EijiiijPFviPvS1_ES1_i'...
I/System.out( 1773): Trying NavinativeD...
I/System.out( 1773): Couldn't load NavinativeD: findLibrary returned null
D/NaviKernelConnector( 1773): NaviKernelConf.ini pkg_version = ANDROID_INI_VERSION = 1.5.8
D/NaviKernelConnector( 1773): NaviKernelConf.ini ins_version = ANDROID_INI_VERSION = 1.5.8
D/NaviKernelConnector( 1773): NaviKernelConf.ini is up-to-date
I/ActivityManager( 187): Displayed com.navigon.navigator_select/.hmi.CheckExistingRegistrationActivity: +384ms
W/dalvikvm( 1773): threadid=9: thread exiting with uncaught exception (group=0x4001d560)
Awesome, it worked for me even with the old Navigon version. Thanks!
EDIT: nope, sorry. wrong information. it's not working. I guess, my GPS is not working either. Is there a gps test app? The one in market Force Closes when open in gingerbread
Could you guys try again with the file i attached? Maybe i uploaded the wrong one.
gnash.s said:
Awesome, it worked for me even with the old Navigon version. Thanks!
EDIT: nope, sorry. wrong information. it's not working. I guess, my GPS is not working either. Is there a gps test app? The one in market Force Closes when open in gingerbread
Click to expand...
Click to collapse
Use GPS Status from Market.
Nope, also the new file won't work (for me) ...
cheezusweezel said:
Sure, latest version installed and logcat is:
I/ActivityThread( 1773): Pub com.navigon.navigator_select.provider.naviprovider: com.navigon.navigator_select.provider.NaviProvider
D/NaviApp ( 1773): pn: com.navigon.navigator_select
D/NaviApp ( 1773): NaviKernel hasn't been started yet, ignore...
D/dalvikvm( 1773): Trying to load lib /data/data/com.navigon.navigator_select/lib/libNavinative.so 0x4051cc28
I/System.out( 1773): Cannot load library: reloc_library[1311]: 147 cannot locate '_ZN7android10AudioTrackC2EijiiijPFviPvS1_ES1_i'...
I/System.out( 1773): Trying NavinativeD...
I/System.out( 1773): Couldn't load NavinativeD: findLibrary returned null
D/NaviKernelConnector( 1773): NaviKernelConf.ini pkg_version = ANDROID_INI_VERSION = 1.5.8
D/NaviKernelConnector( 1773): NaviKernelConf.ini ins_version = ANDROID_INI_VERSION = 1.5.8
D/NaviKernelConnector( 1773): NaviKernelConf.ini is up-to-date
I/ActivityManager( 187): Displayed com.navigon.navigator_select/.hmi.CheckExistingRegistrationActivity: +384ms
W/dalvikvm( 1773): threadid=9: thread exiting with uncaught exception (group=0x4001d560)
Click to expand...
Click to collapse
So it has to work now.. I checked the .so file, the symbol is definetly present:
Code:
gauners-MacBook-Pro:~ gauner$ strings libmedia.so | grep "_ZN7android10AudioTrackC2EijiiijPFviPvS1_ES1_i"
_ZN7android10AudioTrackC2EijiiijPFviPvS1_ES1_i
_ZN7android10AudioTrackC2EijiiijPFviPvS1_ES1_ii
Be sure to replace /system/lib/libmedia.so !
cheezusweezel said:
Nope, also the new file won't work (for me) ...
Click to expand...
Click to collapse
Could you check logcat again please?
Anyway.. I'll release a ROM based on CM7 soon.
Could you check logcat again please?
Anyway.. I'll release a ROM based on CM7 soon.
Click to expand...
Click to collapse
New logcat:
I/ActivityThread( 2812): Pub com.navigon.navigator_select.provider.naviprovider: com.navigon.navigator_select.provider.NaviProvider
D/NaviApp ( 2812): pn: com.navigon.navigator_select
D/NaviApp ( 2812): NaviKernel hasn't been started yet, ignore...
D/dalvikvm( 2812): Trying to load lib /data/data/com.navigon.navigator_select/lib/libNavinative.so 0x4051d788
I/System.out( 2812): Cannot load library: reloc_library[1311]: 147 cannot locate '_ZN7android10AudioTrackC2EijiiijPFviPvS1_ES1_i'...
I/System.out( 2812): Trying NavinativeD...
I/System.out( 2812): Couldn't load NavinativeD: findLibrary returned null
D/NaviKernelConnector( 2812): NaviKernelConf.ini pkg_version = ANDROID_INI_VERSION = 1.5.8
D/NaviKernelConnector( 2812): NaviKernelConf.ini ins_version = ANDROID_INI_VERSION = 1.5.8
D/NaviKernelConnector( 2812): NaviKernelConf.ini is up-to-date
W/dalvikvm( 2812): threadid=9: thread exiting with uncaught exception (group=0x4001d560)
I/Process ( 2812): Sending signal. PID: 2812 SIG: 9
And your ROM will be much appreciated !!!
gauner1986 said:
Anyway.. I'll release a ROM based on CM7 soon.
Click to expand...
Click to collapse
I read on mdj's thread that alot of ppl are complaining about lag in CM7, would you consider as AOSP release? Thanks soo much!!!
Had a FC when starting Navigon Select before applying the fixed library.
Replaced with your library now NS (&GPS) works without any problem!
Thx again!
Hopefully you guys did not forget to reboot? Otherwise i don't know!
another tip...
if you got a FC while starting Navigon Select, just remove the Navigon and reinstall it again
Should work afterwards.
Sounds like permission issues, check that the new files have the same permissions as others in the same folder.
Just tried this update with Navigon MobileNavigator on a Nexus S with Gingerbread(2.3.1) It's let me get past the spash screen without a FC. Just downloading the maps now. Hope the rest of the app doesn't have any other problems.
Many thanks for this fix.
(I did change the permissions and ownership of libmedia.so with these commands
chown root.root libmedia.so
chmod 644 libmedia.so
)
Rob
EDIT: Confirmed that this is working on my device. Thanks for a great fix.
hi there.
So i've asked a dev related questions here before but didnt get an answer... hoping to get one now!
--i didnt ask it in the DEV related forums because it doesnt seem like the place to ask a question--
and i've also searched for an answer, many times, but havent reached a solution
anyway, ...
I took the Dice_ml.apk from the sensation ROM and put it on my 2.3.3 deodexed (near to)stock-ROM, yet i get a 'Force Close'. i deodexed the dice_ml file and added the classes.dex file to the apk.
I 'logcat'ed and found that its missing a .so file, so i found it in the sensation ROM and copied it to the /system/lib folder, yet i still get the error, this is what it says:
I/ActivityManager( 1343): Start proc com.htc.dice.ml for activity com.htc.dice.m
l/.DiceActivity: pid=2762 uid=10130 gids={}
I/DiceActivity( 2762): onCreate()
I/DiceActivity( 2762): onResume()
D/DiceActivity( 2762): [onResume] mView is Null and postDelay
E/Dice ( 2762): Couldn't load libdice_ml.so!
W/dalvikvm( 1443): disableGcForExternalAlloc: false
D/DiceActivity( 2762): [DiceLib::getInstance] Null State
W/dalvikvm( 2762): No implementation found for native Lcom/htc/dice/ml/DiceLib;.
setResourcePath (Ljava/lang/String; )V
D/AndroidRuntime( 2762): Shutting down VM
W/dalvikvm( 2762): threadid=1: thread exiting with uncaught exception (group=0x4
001d5a0)
E/AndroidRuntime( 2762): FATAL EXCEPTION: main
E/AndroidRuntime( 2762): java.lang.UnsatisfiedLinkError: setResourcePath
E/AndroidRuntime( 2762): at com.htc.dice.ml.DiceLib.setResourcePath(Nativ
e Method)
Click to expand...
Click to collapse
The AndroidRuntime Error still goes on. What could be the problem (im kinda new to this moving from one ROM to the next)
And could i also ask how one changes the Resolution of an apk?
//----------------------------
Also, alot of people have this issue, which is that, after rooting, the headphone mic, and buttons dont work.
i also 'logcat'ed it, and sometimes the buttons send a signal to the OS, sometimes it takes a while for the OS to process the signal (or maybe get it?) and sometimes it doesnt receive it at all!(or maybe its taking to long to send the signal).
Anyway, when it does get a signal, it also says that a certain file is missing, heres the log:
W/KeyCharacterMap( 1443): Can't open keycharmap file
W/KeyCharacterMap( 1443): Error loading keycharmap file '/system/usr/keychars/h2
w_headset.kcm.bin'. hw.keyboards.65540.devname='h2w headset'
I/KeyCharacterMap( 1443): Using default keymap: /system/usr/keychars/qwerty.kcm.
bin
E/BroadcastReceiver( 1713): BroadcastReceiver trying to return result during a n
on-ordered broadcast
E/BroadcastReceiver( 1713): java.lang.RuntimeException: BroadcastReceiver trying
to return result during a non-ordered broadcast
E/BroadcastReceiver( 1713): at android.content.BroadcastReceiver.checkSynchr
onousHint(BroadcastReceiver.java:451)
E/BroadcastReceiver( 1713): at android.content.BroadcastReceiver.abortBroadc
ast(BroadcastReceiver.java:374)
Click to expand...
Click to collapse
and also the BroadcastReceiver Error continues in the log.
So i checked the 1.32 original stock rom(my buttons were working on that ROM before i rooted it), and i didnt find the 'h2w_headset.kcm.bin' file, so i thought maybe its from the 'qwerty.kcm.bin' file, thus i replaced it with the same file from 1.32, (and without restarting the phone) i tested the file and still, had the same problem.
My question for this part is ... Is that error normal? and can it be fixed?
and sorry for all this stuff!!!
Hoping for a reply!
UPDATE
Initial OmniROM release for Athene out now:
omni-7.1.1-20170219-athene-HOMEMADE.zip
--- Original OP below ---
Hi guys, I have started the bringup for OmniROM on Athene:
Device
Kernel
It starts to boot up, but gets stuck in the bootanimation and restarts soon after. According to dmesg / logcat, the modem does not come up (see attached files). I compared init.rc files and blobs being used with other roms (lineage / aex), but couldn't identify the root cause for that error at this early stage:
Code:
[ 7.022888,0] Fatal error on the modem.
[ 7.022913,0] modem subsystem failure reason: fs_device_efs_rmts.c:175:Invalid shared ram address from Apps.
@rahulsnair, @Silesh.Nair (or anybody else): Can you guys please help out here, is that something you have come across in any of your bringups? Really would like to bring Omni to life on Athene.
Thanks in advance :good:
Looks like rmt_storage can't load the needed modem firmware :
Code:
09-21 03:07:13.861 342 342 D rmt_storage: GZFSG open /fsg/athene_dsds_emea.img.gz
09-21 03:07:13.861 342 342 E rmt_storage: Couldn't open /fsg/athene_dsds_emea.img.gz, trying default for product-radio
09-21 03:07:13.862 342 342 E rmt_storage: Couldn't open /fsg/athene_emea.img.gz, trying default for radio
09-21 03:07:13.862 342 342 E rmt_storage: Couldn't open /fsg/emea.img.gz, trying default
09-21 03:07:13.862 342 342 E rmt_storage: Couldn't open /fsg/0.img.gz
09-21 03:07:13.862 342 342 I rmt_storage: rmt_storage_open_cb: Unable to open /boot/modem_fsg
Check that /fsg partition is mounted (can't check that in logs cause it's not full logs) and files are there.
You can also try to "strace" rmt-storage process :
Code:
strace -fF -s 1000 rmt_storage > /sdcard/rmt_storage_strace.txt
vache said:
Looks like rmt_storage can't load the needed modem firmware :
Check that /fsg partition is mounted (can't check that in logs cause it's not full logs) and files are there.
You can also try to "strace" rmt-storage process :
Click to expand...
Click to collapse
Good point, thanks. Haven't checked the mounts on boot yet. Eventually, fstab.qcom does not get parsed.
Making some progress: There is an issue with the ramdisk of the inline-built kernel: It is not picking up the correct .rc files. I don't get where these references to "recovery" are coming from:
Code:
<13>[ 3.022567,0] init: init second stage started!
<11>[ 3.207517,0] init: waitpid failed: No child processes
<11>[ 3.209434,0] init: property_set("ro.com.google.clientidbase", "android-motorola") failed
<11>[ 3.209584,0] init: property_set("ro.config.notification_sound", "Argon.ogg") failed
<11>[ 3.209599,0] init: property_set("ro.config.alarm_alert", "Helium.ogg") failed
<11>[ 3.209710,0] init: property_set("ro.config.ringtone", "Orion.ogg") failed
<13>[ 3.209803,0] init: (Loading properties from /default.prop took 0.00s.)
<11>[ 3.210260,0] init: /init.rc: 12: invalid command 'setcon'
<11>[ 3.210326,0] init: /init.rc: 62: invalid command 'load_all_props'
<11>[ 3.210406,0] init: could not import file '/init.recovery.logd.rc' from '/init.rc'
<13>[ 3.210688,0] init: (Parsing /init.recovery.usb.rc took 0.00s.)
<13>[ 3.210735,0] init: (Parsing /init.recovery.service.rc took 0.00s.)
<11>[ 3.210812,0] init: could not import file 'init.target.recovery.rc' from '/init.recovery.qcom.rc'
<13>[ 3.210827,0] init: (Parsing /init.recovery.qcom.rc took 0.00s.)
However, having flashed a Lineage kernel, it's booting up now.
@vache: /fsg indeed was not mounted. I think there is an issue with the mkdir, will amend that now.
Unhandled fsg_file security context on the fstab /fsg entry was the root cause for not mounting /fsg. Omni kernel booting up now.
golden-guy said:
Unhandled fsg_file security context on the fstab /fsg entry was the root cause for not mounting /fsg. Omni kernel booting up now.
Click to expand...
Click to collapse
Well done
To get RIL working, you need to add android_system_qcom from Lineage in your manifest and rebuilt.
Or you can push libqsap_sdk.so manually.
vache said:
Well done
To get RIL working, you need to add android_system_qcom from Lineage in your manifest and rebuilt.
Or you can push libqsap_sdk.so manually.
Click to expand...
Click to collapse
Thanks mate, I have done that yesterday to get RIL working (radio logcat showed that rild was complaining about that missing libqsap_sdk.so lib). All fine there already.
But I am still struggling with at least three things atm: Sensors, media playback and camcorder.
Sensors: I can see them initialized, but they don't return any values. According to logcat, e.g proximity gets disabled on screen on (sic!) Which sounds weird tbh
Media playback: Acodec cannot instantiate decoders upon ringtone playback and when music is to be played via bluetooth. mp3/mpeg playback does work when played via phone' speaker though. It could be a codec issue, but it could be audio policy / routing related. We are using a custom policy, aren't we?
Camcorder - didn't look into that yet. But is very likely related to media codec issue.
Will add some logs to further explain.
EDIT: Logs are added now.
PS: Device repo updated
Will cross-check with LineageOS, but the lack of sensor data might be permission related after all. All sensors seem to be up and configured, with their /dev and /sys entries being populated. Unfortunately, there is no error to be seen in the logs, giving no indication of the root cause...
Got the sensor issue sorted. It was selinux related again - what else. :silly:
Anyhow, one issue less.
Great news. How many issues are left now? :highfive:
Seriously, i would really appreaciate it if it´ll be released and maintained sometime... :fingers-crossed:
vinylmeister said:
Great news. How many issues are left now? :highfive:
Seriously, i would really appreaciate it if it´ll be released and maintained sometime... :fingers-crossed:
Click to expand...
Click to collapse
He is courteous enough to give us status updates on what is happening and what he is currently fixing.
I dont think he would appreciate the ETA-ish question.
It will be released when he is done. Im sure he is not on this full time. Have patience.
Sent from my Moto G4 Plus using Tapatalk
vinylmeister said:
Great news. How many issues are left now? :highfive:
Seriously, i would really appreaciate it if it´ll be released and maintained sometime... :fingers-crossed:
Click to expand...
Click to collapse
+1
1chrome said:
He is courteous enough to give us status updates on what is happening and what he is currently fixing.
I dont think he would appreciate the ETA-ish question.
It will be released when he is done. Im sure he is not on this full time. Have patience.
Click to expand...
Click to collapse
Didn't you realize that the issue related sentence was just ironic? The high-five smiley should indicate that, followed by seriously...
vinylmeister said:
Didn't you realize that the issue related sentence was just ironic? The high-five smiley should indicate that, followed by seriously...
Click to expand...
Click to collapse
Sorry man my bad... smileys didn't show up on my Tapatalk!
Sent from my Moto G4 Plus using Tapatalk
Vorbis decoder and camcorder are still open.
I'd love to have a fully working Omni build up by now, but time-wise this is a best-effort activity.
It is ready when it's done.
golden-guy said:
Vorbis decoder and camcorder are still open.
I'd love to have a fully working Omni build up by now, but time-wise this is a best-effort activity.
It is ready when it's done.
Click to expand...
Click to collapse
Could you grab fresh logs after trying to record a video ? Can't find traces in current logs.
Also, did you try with different camera apps ?
vache said:
Could you grab fresh logs after trying to record a video ? Can't find traces in current logs.
Also, did you try with different camera apps ?
Click to expand...
Click to collapse
I tried with Snap and SnapDragonCamera. I wanted to do that with a fresh build. After having synched sources, mm-camera daemon keeps crashing and causing bootloops. Omni has updated their manifest to r14, also, lineage seems to have merged in fresh caf sources causing issues with qcom blobs. If I had known that earlier, I wouldn't have synched anew.
I see u uploaded to afh is it ready for testing I'm excited
joeeboogz said:
I see u uploaded to afh is it ready for testing I'm excited
Click to expand...
Click to collapse
????!!
Good catch! ?
Yes, it's up for testing now: https://www.androidfilehost.com/?fid=457095661767137952
Please note that this is an early ALPHA build: Media playback (ogg/mp4) and camcorder are still broken. But apart from that it seems to work just fine.
Xperia finally updated their launcher!
Hey, so it has been a long long time since I have posted or even ported anything.
Finally, xperia updated the launcher and it was a must port for me.
The launcher should theoretically work on all xperia devices with android Pie (and sony software). I have currently tested it on Xperia XZP. You can also activate pill via an adb command.
Steps
Simply install the apk and then install the wallpaper apk and then reboot
If you want pill, you must use adb with your device.
I will not be explaining how to use adb, there are many guides out there.
But to activate pill simply use this adb command
Code:
adb shell settings put secure swipe_up_to_switch_apps_enabled 1
p.s the launcher will not override sony's built in launcher. But you cannot use Launcher3(Quickstep launcher) with it. The package name is com.android.launcher3.
FOR XPERIA XA2
Devices:
Working :-
Xperia XZ1
Xperia XZP
Xperia XZ2
Xperia XZ3
Not Working :- (Testing needs to be done to get the app working on these, logcats also need to be provided)
Click to expand...
Click to collapse
Known bugs :-
Split screen causes force closeFixed v1.1
Force Close on rotating Fixed v1.2
More than 1 page in folder FC on rearrange Fixed v1.5
App split shortcut not working
Click to expand...
Click to collapse
VERSIONS
v1.3 If you plan on using pill with this launcher, this one might be the most stable option for you. Navbar replacement/shortcut apps should work with this as long as this launcher is the default (App close animation had to be slightly altered).
v1.4.1 first of all, both have recents working without pill
v1.4.2 second version has recents working with other launchers, but to do this, i had to remove app opening animation(not the gesture) from the recent, so If this is something you cant live without, go with v1.4.1, but if you wanna use other launchers, then this is the version you want
Hope you all enjoy it as much as i am.
Don't forget thanks button and feel free to donate
Thanks @TakuyaZ for providing the apks from the system dumps (and motivating me )
Lastly, please do not use or repost my work without authorization, as this port was done for me and for a friend, took me at least 8 hours of constant work to get it to work properly and was not as easy and simple as copying from a system dump and uploading it and simply calling it a port.
Sahaab;
Don't forget thanks button and feel free to donate to help me buying new development device
Thanks [user=4499687 said:
@TakuyaZ[/user] for providing the apks from the system dumps (and motivating me )
[/CENTER]
Click to expand...
Click to collapse
Lol you used my port and even paste my thread text, ahahah
Envoyé de mon iPad en utilisant Tapatalk
nice port
@Sahaab
sorry all good and yes all good bro and with you ?
no thats true i am less on xda and busy life but i am still here and have now an XZ2
niaboc79 said:
Lol you used my port and even paste my thread text, ahahah
Envoyé de mon iPad en utilisant Tapatalk
Click to expand...
Click to collapse
Oh extremely sorry about that, just noticed your thread as well. If you like I can completely remove this thread. But we both do have completely different things. You have a version which is flashable. This is for non rooted devices and used as normal apps like all my previous ports.
Edit: also as a clarification, the apks were obtained from the xperia 10 system dump.
Pandemic said:
please close this thread -__-
Click to expand...
Click to collapse
I am sorry, but may i ask why? I have not seen any ports like these here? this apk also has my signatures, and also many of my various tactics i use inside smali, android manifest, and resources to make the port work without root.
p.s yooo pandemic how you doing man, hvnt seen you in ages
Sahaab said:
Oh extremely sorry about that, just noticed your thread as well. If you like I can completely remove this thread. But we both do have completely different things. You have a version which is flashable. This is for non rooted devices and used as normal apps like all my previous ports.
Edit: also as a clarification, the apks were obtained from the xperia 10 system dump.
Click to expand...
Click to collapse
You didn’t see my thread but you have paste my text...
Anyway, I am going to add non root version in my thread [emoji3]
Envoyé de mon iPhone en utilisant Tapatalk
niaboc79 said:
You didn’t see my thread but you have paste my text...
Anyway, I am going to add non root version in my thread [emoji3]
Envoyé de mon iPhone en utilisant Tapatalk
Click to expand...
Click to collapse
yes, once again completely sorry about that, hence i said sorry in the first place...(Sorry that the text seemed to have came out in the same way, as you can see from my various previous posts i usually write something like that in the end, and after seeing your thread, i have changed the text, if that would make you feel better)
Secondly, I would prefer that you do not steal my days work. Took me atleast 8 hours of constant work to port this, with fixing all the bugs and etc.
Sahaab said:
yes, once again completely sorry about that, hence i said sorry in the first place...(Sorry that the text seemed to have came out in the same way, as you can see from my various previous posts i usually write something like that in the end, and after seeing your thread, i have changed the text, if that would make you feel better)
Secondly, I would prefer that you do not steal my days work. Took me atleast 8 hours of constant work to port this, with fixing all the bugs and etc.
Click to expand...
Click to collapse
Don’t worry I am not like that and respect other devs [emoji2][emoji3]
Envoyé de mon iPhone en utilisant Tapatalk
niaboc79 said:
Don’t worry I am not like that and respect other devs [emoji2][emoji3]
Envoyé de mon iPhone en utilisant Tapatalk
Click to expand...
Click to collapse
Yes, i remember, back in the day, when i had my Arc S, those days you used to have amazing work.
App force close on XZ2 Premium android pie
raziel zarafan said:
App force close on XZ2 Premium android pie
Click to expand...
Click to collapse
Have you tried rebooting right after installing?
if so, could you provide me with a logcat?
Sahaab said:
Have you tried rebooting right after installing?
if so, could you provide me with a logcat?
Click to expand...
Click to collapse
Works now restarting the phone thanks bro
Works great on XZ3! Thanks!
EDIT:
Launcher crashes when attempting to use multi-window (splitscreen) mode.
Logcat:
Code:
02-28 13:24:56.879 834 937 W SurfaceFlinger: Attempting to set client state on removed layer: Splash Screen com.android.launcher3#0
02-28 13:24:56.879 834 937 W SurfaceFlinger: Attempting to destroy on removed layer: Splash Screen com.android.launcher3#0
02-28 13:24:57.406 16171 16171 W launcher-loader: type=1400 audit(0.0:546): avc: denied { read } for name="u:object_r:semc_version_cust_active_prop:s0" dev="tmpfs" ino=21902 scontext=u:r:untrusted_app:s0:c39,c257,c512,c768 tcontext=u:object_r:semc_version_cust_active_prop:s0 tclass=file permissive=0 ppid=722 pcomm="main" pgid=16171 pgcomm="droid.launcher3"
02-28 13:24:57.437 16171 16171 I chatty : uid=10295(com.android.launcher3) identical 1 line
02-28 13:25:01.701 16171 16171 E AndroidRuntime: Process: com.android.launcher3, PID: 16171
02-28 13:25:01.703 1381 7072 D ActivityManager: New dropbox entry: com.android.launcher3, data_app_crash, 734bd5c2-7e2f-43c9-8014-5708a52320a2
02-28 13:25:01.704 1381 7072 W ActivityManager: Force finishing activity com.android.launcher3/com.sonymobile.launcher.XperiaLauncher
02-28 13:25:01.707 1381 7072 I ActivityManager: Clearing package preferred activities from com.android.launcher3
02-28 13:25:01.708 1381 1452 I ActivityManager: Showing crash dialog for package com.android.launcher3 u0
02-28 13:25:01.712 997 997 I JavaDumper:JavaDumperThread: addEvent: [email protected] processName: com.android.launcher3
02-28 13:25:01.728 1381 1452 I InputDispatcher: Focus entered window: Window{46885fa u0 Application Error: com.android.launcher3}
02-28 13:25:03.359 1381 7072 W ActivityManager: Force finishing activity com.android.launcher3/com.sonymobile.launcher.XperiaLauncher
02-28 13:25:03.368 1381 7072 I ActivityManager: Killing 16171:com.android.launcher3/u0a295 (adj 100): crash
02-28 13:25:03.370 803 803 E ANDR-IOP: IOP HAL: Received pkg_name = com.android.launcher3 pid = 0
02-28 13:25:03.376 1381 1381 V NotificationListeners: notification listener connection lost: ComponentInfo{com.android.launcher3/com.android.launcher3.notification.NotificationListener}
02-28 13:25:03.376 1381 1381 W NotificationListeners: notification listener binding died: ComponentInfo{com.android.launcher3/com.android.launcher3.notification.NotificationListener}
02-28 13:25:03.380 834 2427 W SurfaceFlinger: Attempting to destroy on removed layer: 9f29ca0 com.android.launcher3/com.sonymobile.launcher.XperiaLauncher#0
02-28 13:25:03.388 1908 1908 W OverviewProxyService: Binding died of 'ComponentInfo{com.android.launcher3/com.android.quickstep.TouchInteractionService}', try reconnecting
02-28 13:25:03.420 1908 1908 W OverviewProxyService: Null binding of 'ComponentInfo{com.android.launcher3/com.android.quickstep.TouchInteractionService}', try reconnecting
02-28 13:25:03.431 1381 1453 I ActivityManager: Start proc 16247:com.android.launcher3/u0a295 for service com.android.launcher3/com.android.quickstep.TouchInteractionService
02-28 13:25:03.436 1381 6344 D NotificationListeners: Removing active service ComponentInfo{com.android.launcher3/com.android.launcher3.notification.NotificationListener}
02-28 13:25:03.559 803 803 E ANDR-IOP: IOP HAL: Received pkg_name = com.android.launcher3 pid = 0
02-28 13:25:03.583 834 937 W SurfaceFlinger: Attempting to destroy on removed layer: 46885fa Application Error: com.android.launcher3#0
02-28 13:25:08.886 1381 2203 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10010000 cmp=com.android.launcher3/com.sonymobile.launcher.XperiaLauncher} from uid 10295
02-28 13:25:08.888 803 803 E ANDR-IOP: IOP HAL: Received pkg_name = com.android.launcher3 pid = -1
02-28 13:25:08.896 16247 16247 W com.android.launcher3: type=1400 audit(0.0:547): avc: denied { read } for comm=45474C20496E6974 name="u:object_r:vendor_default_prop:s0" dev="tmpfs" ino=21945 scontext=u:r:untrusted_app:s0:c39,c257,c512,c768 tcontext=u:object_r:vendor_default_prop:s0 tclass=file permissive=0 ppid=722 pcomm="main" pgid=16247 pgcomm="droid.launcher3"
02-28 13:25:09.146 16247 16247 I chatty : uid=10295(com.android.launcher3) identical 1 line
02-28 13:25:09.756 16247 16247 W launcher-loader: type=1400 audit(0.0:548): avc: denied { read } for name="u:object_r:semc_version_cust_active_prop:s0" dev="tmpfs" ino=21902 scontext=u:r:untrusted_app:s0:c39,c257,c512,c768 tcontext=u:object_r:semc_version_cust_active_prop:s0 tclass=file permissive=0 ppid=722 pcomm="main" pgid=16247 pgcomm="droid.launcher3"
Work on xperia XZ1, but splitscreen crashed whole xperia home. Sometimes glitches when swipe up.. but good thanks [emoji4][emoji4][emoji4]
Odesláno z mého G8341 pomocí Tapatalk
I myself have noticed the split screen bug, i will fix it tomorrow
Sahaab said:
I myself have noticed the split screen bug, i will fix it tomorrow
Click to expand...
Click to collapse
There's also no option to "disable" gestures by toggling the swipe up to home button, which should be found in the display settings menu. Will report other crashing with logcats when they occur.
I am currently on XZ Premium. Is the recent button really visible on the navigation pane? Seems to have no function as of the moment.
Edit. Frgot to flash adb things.
Lol damn, if i'm faster in getting the FTF we might beaten @niaboc79 to the punch for the first new launcher related post XD
iArvee said:
There's also no option to "disable" gestures by toggling the swipe up to home button, which should be found in the display settings menu. Will report other crashing with logcats when they occur.
Click to expand...
Click to collapse
Ya thats not home related , maybe someone will port the new settings, but settings you cant port for non root that easily plus xperia 10 probably has a newer settings app than ours so again ours probably wont work
TakuyaZ said:
Lol damn, if i'm faster in getting the FTF we might beaten @niaboc79 to the punch for the first new launcher related post XD
Click to expand...
Click to collapse
Nah man porting takes time :-/
Sahaab said:
Have you tried rebooting right after installing?
if so, could you provide me with a logcat?
Click to expand...
Click to collapse
I have problems like him.
But after restarting it was fixed.
Xperia XZ1 (Pie)
Thank you friend