yashsingh1/xdaforums huggingface dataset:
[G3 Developer Discussion [Developers Only]] manups4e:
so.. going further into the bootloop... i got this in Dmesg

[ 68.987725 / 01-17 08:17:43.029] init: Starting service 'netmgrd'...
[ 68.988092 / 01-17 08:17:43.029] init: Starting service 'qmuxd'...
[ 68.988406 / 01-17 08:17:43.029] init: Starting service 'qseecomd'...
[ 68.988730 / 01-17 08:17:43.029] init: Starting service 'rmt_storage'...
[ 68.989190 / 01-17 08:17:43.029] init: Service 'netmgrd' (pid 328) exited with status 1
[ 68.989211 / 01-17 08:17:43.029] init: Service 'netmgrd' (pid 328) killing any children in process group
[ 68.989362 / 01-17 08:17:43.029] init: Service 'qmuxd' (pid 329) exited with status 1
[ 68.989381 / 01-17 08:17:43.029] init: Service 'qmuxd' (pid 329) killing any children in process group
[ 68.990768 / 01-17 08:17:43.029] init: Service 'rmt_storage' (pid 331) exited with status 1
[ 68.990787 / 01-17 08:17:43.029] init: Service 'rmt_storage' (pid 331) killing any children in process group
[ 68.991276 / 01-17 08:17:43.029] init: Service 'qseecomd' (pid 330) exited with status 1
[ 68.991294 / 01-17 08:17:43.029] init: Service 'qseecomd' (pid 330) killing any children in process group
[ 73.996545 / 01-17 08:17:48.039] init: Starting service 'netmgrd'...
[ 73.996904 / 01-17 08:17:48.039] init: Starting service 'qmuxd'...
[ 73.997220 / 01-17 08:17:48.039] init: Starting service 'qseecomd'...
[ 73.997542 / 01-17 08:17:48.039] init: Starting service 'rmt_storage'...
[G3 Developer Discussion [Developers Only]] t-shock:
For me it seems as a kernel problem but I'm not a big developers to know
[G3 Developer Discussion [Developers Only]] manups4e:
It could be kernel, libs, framework.. Logcat doesn't help that's the problem
[G3 Developer Discussion [Developers Only]] Snoob25:
did you use g3's netmgrd, qmuxd, qseecomd, rmt_storage bins??
[G3 Developer Discussion [Developers Only]] manups4e:
The same thing with both g3's and latest qcom bins
[G3 Developer Discussion [Developers Only]] manups4e:
almost booting :D :D just few more errors remaining :D :D (it almost boot "updating apps 23 of 57" then shutdown because of too much errors in logcat)

edit: logcat and dmesg in OP
[G3 Developer Discussion [Developers Only]] Aaahh:
You can get it to boot without them, just remove the two services from the init

That's radio and WiFi

I'm not on my laptop

I'll take a look at the full logs soon...
[G3 Developer Discussion [Developers Only]] manups4e:
ok i will try it tomorrow ^^ 11.24 pm :D i'll let you know :D
[G3 Developer Discussion [Developers Only]] manups4e:
if you'll check the dmseg while booting there are errors on the init: write file like this

init: write_file: Unable to open '/proc/sys/kernel/hung_task_timeout_secs': No such file or directory
[ 1.933360 / 01-18 22:10:01.980] init: write_file: Unable to open '/proc/sys/kernel/sched_compat_yield': No such file or directory
[ 1.933792 / 01-18 22:10:01.980] init: write_file: Unable to open '/proc/sys/net/ipv4/fwmark_reflect': No such file or directory
[ 1.933844 / 01-18 22:10:01.980] init: write_file: Unable to open '/proc/sys/net/ipv6/fwmark_reflect': No such file or directory
[ 1.933887 / 01-18 22:10:01.980] init: write_file: Unable to open '/proc/sys/net/ipv4/tcp_fwmark_accept': No such file or directory
[ 1.934224 / 01-18 22:10:01.980] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts
[ 1.934349 / 01-18 22:10:01.980] init: write_file: Unable to write to '/dev/cpuctl/cpu.shares': Invalid argument
[ 1.935157 / 01-18 22:10:01.980] init: write_file: Unable to open '/proc/sys/abi/swp': No such file or directory

and

init: write_file: Unable to write to '/sys/devices/system/cpu/cpu1/online': Invalid argument
[ 2.844359 / 01-18 22:10:02.890] init: write_file: Unable to write to '/sys/devices/system/cpu/cpu2/online': Invalid argument
[ 2.844417 / 01-18 22:10:02.890] init: write_file: Unable to write to '/sys/devices/system/cpu/cpu3/online': Invalid argument
[G3 Developer Discussion [Developers Only]] Aaahh:
They look cosmetic, but there's something in the init that needs updating

Grep -rn /sys/devices/system/cpu/cpu1/

Then post the result
[G3 Developer Discussion [Developers Only]] Aaahh:
Also, I see your using vold 2.1 (revenge) instead of 3.0 (awakening)
[G3 Developer Discussion [Developers Only]] manups4e:
I don't know why ^^

edit: rebuilded with correct vold.. i'll keep the project going when i'll come back from work ^^
[G3 Developer Discussion [Developers Only]] t-shock:
If you need any help after booting the build (fixing wifi, bluetooth, gps, nfc etc), I would be very happy to help :)
[G3 Developer Discussion [Developers Only]] manups4e:
First let me boot this beast :P
[G3 Developer Discussion [Developers Only]] :
are you missing some vendor files?

01-18 22:10:03.105 316 371 E adsprpc : vendor/qcom/proprietary/adsprpc/src/listener_android.c:107:listener using ion heap: -1
01-18 22:10:03.107 316 371 E adsprpc : vendor/qcom/proprietary/adsprpc/src/apps_std_imp.c:33:apps_std fopen failed: ./oemconfig.so No such file or directory
01-18 22:10:03.107 316 371 E adsprpc : vendor/qcom/proprietary/adsprpc/src/apps_std_imp.c:33:apps_std fopen failed: /system/lib/rfsa/adsp/./oemconfig.so No such file or directory
01-18 22:10:03.107 316 371 E adsprpc : vendor/qcom/proprietary/adsprpc/src/apps_std_imp.c:33:apps_std fopen failed: /system/vendor/lib/rfsa/adsp/./oemconfig.so No such file or directory
01-18 22:10:03.107 316 371 E adsprpc : vendor/qcom/proprietary/adsprpc/src/../inc/mod_table_imp.h:346::error: 2: 0 == (nErr = invoke_func_ptr(sc, pra))
01-18 22:10:03.107 306 306 I Netd : Netd 1.0 starting
01-18 22:10:03.108 316 371 E adsprpc : vendor/qcom/proprietary/adsprpc/src/apps_std_imp.c:33:apps_std fopen failed: ./voiceproc_tx.so No such file or directory
01-18 22:10:03.108 316 371 E adsprpc : vendor/qcom/proprietary/adsprpc/src/apps_std_imp.c:33:apps_std fopen failed: /system/lib/rfsa/adsp/./voiceproc_tx.so No such file or directory
01-18 22:10:03.108 316 371 E adsprpc : vendor/qcom/proprietary/adsprpc/src/apps_std_imp.c:33:apps_std fopen failed: /system/vendor/lib/rfsa/adsp/./voiceproc_tx.so No such file or directory
01-18 22:10:03.108 316 371 E adsprpc : vendor/qcom/proprietary/adsprpc/src/../inc/mod_table_imp.h:346::error: 2: 0 == (nErr = invoke_func_ptr(sc, pra))
01-18 22:10:03.108 316 371 E adsprpc : vendor/qcom/proprietary/adsprpc/src/apps_std_imp.c:33:apps_std fopen failed: ./voiceproc_rx.so No such file or directory
01-18 22:10:03.108 316 371 E adsprpc : vendor/qcom/proprietary/adsprpc/src/apps_std_imp.c:33:apps_std fopen failed: /system/lib/rfsa/adsp/./voiceproc_rx.so No such file or directory
01-18 22:10:03.108 316 371 E adsprpc : vendor/qcom/proprietary/adsprpc/src/apps_std_imp.c:33:apps_std fopen failed: /system/vendor/lib/rfsa/adsp/./voiceproc_rx.so No such file or directory

also are you using G3 stock as base?

01-18 22:10:05.593 719 719 D idmap : error: no read access to /vendor/overlay: No such file or directory

afaik AOSP doesn't use overlay or does they?

also

01-18 22:10:04.225 322 322 W JniInvocation: Falling back from libart to libart.so after dlopen error: dlopen failed: library "libart" not found
01-18 22:10:04.238 329 329 I libmdmdetect: ESOC framework not supported

and

4 793 793 W SystemConfig: No directory /system/etc/sysconfig, skipping
[G3 Developer Discussion [Developers Only]] manups4e:
no bases.. i'm building from sources
[G3 Developer Discussion [Developers Only]] :
Er wouldn't that be hard since it isn't fully pushed source code? Or am I wrong?
[G3 Developer Discussion [Developers Only]] manups4e:
The pushed source is fully buildable and bootable I just need to fix a few things
[G3 Developer Discussion [Developers Only]] :
Well yes it is buildable but would most likely cause issues like this I assume.

And is the kernel modified To load all the missing related errors? It seems like some files isn't created Which might or not be dependent.
[G3 Developer Discussion [Developers Only]] manups4e:
in fact android m wants a 3.10 kernel to work ^^ but we don't have one ^^ the problem is that most of the normal commands in init.rc are not working and i don't understand why
[G3 Developer Discussion [Developers Only]] :
well i might be wrong but latest KK kernel (from CM) would make the LP bootable so if you use latest kernel sources it *might* get it to boot, however it might not be that way, well at least someone is trying to build it, i don't use Linux and my workstation won't build that fast so i'd rather not try to build since it just waste of time i assume
[G3 Developer Discussion [Developers Only]] manups4e:
my laptop builds from scratch in 2 hours ^^ and i'm using latest 5.1 sources but i had to make some changes to make it bootloop at least :)
[G3 Developer Discussion [Developers Only]] :
if there is no kernel for android M yet, look at the current M prev kernels to set the correct loadpath of framework files (if missed)

also there might be some cherry pics that needs to be done from an "updated" kernel source that might fix a bootloop (if out there)

i'll look around
[G3 Developer Discussion [Developers Only]] manups4e:
sounds great :) no frameworks files problem atm.. the real problem that i can't figure out is why the phone shuts down while booting in the final stage with nothing on logcat or dmesg that seems to be an error..
[G3 Developer Discussion [Developers Only]] shery butt:
will i be able to flash this on android M when it arrives ? (working link)

https://www.youtube.com/watch?v=6UDxyI8zS_0
[G3 Developer Discussion [Developers Only]] thatkindaguy:
This is not the place to post that kind of question-this is developers ONLY.

However, I'm a nice guy. I can not speak for the dev, however, I think you should be able too. CloudyG3 also has this feature, at least I know 2.2 did.
[G3 Developer Discussion [Developers Only]] astonmartin214:
Yes it works on ALL ROMS + stock just flashed it to Stock 4.4.2 just ran it works you can tell the differ
[G3 Developer Discussion [Developers Only]] manups4e:
i don't know if it will work ^^
[G3 Developer Discussion [Developers Only]] :
The mod will work if the needed drivers and if it. Doesn't crash due to incompatibility. but most likely should. Don't think M comes with huge sound changes like from ics to jb.
[G3 Developer Discussion [Developers Only]] Aaahh:
Init packed in boot.img is trash

---------- Post added at 07:42 AM ---------- Previous post was at 07:41 AM ----------

There's a build guide for M on Sonys website

---------- Post added at 07:43 AM ---------- Previous post was at 07:42 AM ----------

It kind of does

With stlport going
[G3 Developer Discussion [Developers Only]] :
Mm interesting. Well I hope its battery friendly (not that I don't blame it for having bad battery life now) its most likely due to some tools made by LG is like Google always be running even if you don't want to. Hope they create a more advanced battery saver support by default. because the one now is terrible
[G3 Developer Discussion [Developers Only]] manups4e:
In fact i will try using 5.1 init file anfld yup I used Sony guide to build m
[G3 Developer Discussion [Developers Only]] Aaahh:
I've been battling errors like

external/libcxx/include/atomic:1300:5: error: no template named 'is_integral'; did you mean 'tr1::is_integral'?
is_integral<_Tp>::value && !is_same<_Tp, bool>::value,
^
external/stlport/stlport/type_traits:214:8: note: 'tr1::is_integral' declared here
struct is_integral :
^
In file included from system/vold/main.cpp:34:
In file included from system/vold/VolumeManager.h:24:
In file included from system/core/include/sysutils/SocketListener.h:21:
In file included from system/core/include/sysutils/SocketClient.h:7:
In file included from system/core/include/cutils/atomic.h:22:
In file included from bionic/libc/include/stdatomic.h:58:
external/libcxx/include/atomic:1300:33: error: no template named 'is_same'; did you mean 'tr1::is_same'?
is_integral<_Tp>::value && !is_same<_Tp, bool>::value,
^
external/stlport/stlport/type_traits:583:8: note: 'tr1::is_same' declared here
struct is_same :
^

Any ideas? I built it before but now it won't build.
[G3 Developer Discussion [Developers Only]] manups4e:
did you change something before building this time?
[G3 Developer Discussion [Developers Only]] Aaahh:
Yeah, and I couldn't find the change

I'm doing a diff compare, I remember something to do with stlport
[G3 Developer Discussion [Developers Only]] manups4e:
Try replacing stock stlport
[G3 Developer Discussion [Developers Only]] Aaahh:
Enough about me, what's on with you?

I'm thinking themral in bin is shutting you down.

---------- Post added at 08:11 AM ---------- Previous post was at 08:10 AM ----------

Unless of course it reboots, then it's just a matter of removing those 2 services from the init.rc
[G3 Developer Discussion [Developers Only]] manups4e:
The phone shutdowns while booting it doesn't reboot I think its sensors related
[G3 Developer Discussion [Developers Only]] manups4e:
The init is then destroying all Tue symlinks and things like that I'll try replacing it today and I'll let you know
[G3 Developer Discussion [Developers Only]] manups4e:
damn cyanogenmod init starts automatically in enforcing mode and there is no way to set it in permissive in on boot neither setting it in init.rc :( i need to dig more into this
[G3 Developer Discussion [Developers Only]] Aaahh:
I'm having this now, the libart thing.

How did you solve it?

Also...

http://developer.android.com/preview/support.html#preview2-notes

Right as I get mine to show anything... :P
[G3 Developer Discussion [Developers Only]] manups4e:
i didn't solve since it's only a warning

Falling back from libart to libart.so after dlopen error: dlopen failed: library "libart" not found

i don't know about this... it shows and seems to not do anything strange since libart is still working good during boot
[G3 Developer Discussion [Developers Only]] manups4e:
i will not update to m preview 2 because i want first make boot this rom.. when i will have a booting rom i will update it
[G3 Developer Discussion [Developers Only]] Aaahh:
I'm doing the same, but I am pretty amazed at timing.
[G3 Developer Discussion [Developers Only]] manups4e:
google wanted to release 2 updates for m preview before the official release :)
[G3 Developer Discussion [Developers Only]] astonmartin214:
Fine just waiting for a flashable zip
[G3 Developer Discussion [Developers Only]] Aaahh:
Binder?

It looks like everything dies
[G3 Developer Discussion [Developers Only]] manups4e:
every app and ^^ even displaymanager
[G3 Developer Discussion [Developers Only]] Aaahh:
Yeah, your looking to deep, find what's killing everything
[G3 Developer Discussion [Developers Only]] manups4e:
that's the thing... can't find anything in dmesg and logcat is not helping :(
[G3 Developer Discussion [Developers Only]] kirmaniarslan:
yep its display problem , have u used kernel headers from sony ?

01-24 06:20:21.664 1088 1088 E DisplayManager: Could not get display information from display manager.
01-24 06:20:21.664 1088 1088 E DisplayManager: android.os.DeadObjectException
01-24 06:20:21.664 1088 1088 E DisplayManager:	at android.os.BinderProxy.transactNative(Native Method)
01-24 06:20:21.664 1088 1088 E DisplayManager:	at android.os.BinderProxy.transact(Binder.java:496)
01-24 06:20:21.664 1088 1088 E DisplayManager:	at android.hardware.display.IDisplayManager$Stub$Proxy.getDisplayInfo(IDisplayManager.java:254)
01-24 06:20:21.664 1088 1088 E DisplayManager:	at android.hardware.display.DisplayManagerGlobal.getDisplayInfo(DisplayManagerGlobal.java:119)
01-24 06:20:21.664 1088 1088 E DisplayManager:	at android.view.Display.updateDisplayInfoLocked(Display.java:763)
01-24 06:20:21.664 1088 1088 E DisplayManager:	at android.view.Display.getRotation(Display.java:580)
01-24 06:20:21.664 1088 1088 E DisplayManager:	at com.android.systemui.ImageWallpaper$DrawableEngine.drawFrame(ImageWallpaper.java:315)
01-24 06:20:21.664 1088 1088 E DisplayManager:	at com.android.systemui.ImageWallpaper$DrawableEngine.onSurfaceRedrawNeeded(ImageWallpaper.java:301)
01-24 06:20:21.664 1088 1088 E DisplayManager:	at android.service.wallpaper.WallpaperService$Engine.updateSurface(WallpaperService.java:804)
01-24 06:20:21.664 1088 1088 E DisplayManager:	at android.service.wallpaper.WallpaperService$Engine.attach(WallpaperService.java:877)
01-24 06:20:21.664 1088 1088 E DisplayManager:	at android.service.wallpaper.WallpaperService$IWallpaperEngineWrapper.executeMessage(WallpaperService.java:1164)
01-24 06:20:21.664 1088 1088 E DisplayManager:	at com.android.internal.os.HandlerCaller$MyHandler.handleMessage(HandlerCaller.java:37)
01-24 06:20:21.664 1088 1088 E DisplayManager:	at android.os.Handler.dispatchMessage(Handler.java:102)
01-24 06:20:21.664 1088 1088 E DisplayManager:	at android.os.Looper.loop(Looper.java:135)
01-24 06:20:21.664 1088 1088 E DisplayManager:	at android.app.ActivityThread.main(ActivityThread.java:5294)
01-24 06:20:21.664 1088 1088 E DisplayManager:	at java.lang.reflect.Method.invoke(Native Method)
01-24 06:20:21.664 1088 1088 E DisplayManager:	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:723)
01-24 06:20:21.664 1088 1088 E DisplayManager:	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:613)
[G3 Developer Discussion [Developers Only]] manups4e:
no everything is from cm kernel

edit: new log in op ^^
[G3 Developer Discussion [Developers Only]] thatkindaguy:
[MENTION=5158920]kirmaniarslan[/MENTION] what do you think now?
[G3 Developer Discussion [Developers Only]] kirmaniarslan:
Sources are closed , I can't say anything until I'll test personally.

Sent from my LG-D855
[G3 Developer Discussion [Developers Only]] Aaahh:
How did you fix libart?

Still going through logs.
[G3 Developer Discussion [Developers Only]] manups4e:
didn't fix it, it goes well like this
[G3 Developer Discussion [Developers Only]] Aaahh:
It's not in your logs, so you did
[G3 Developer Discussion [Developers Only]] manups4e:
i made lots of things while trying but i can say that the libart error is only that since it can't found the libart bin file it will load the libart.so lib that's all.. it's not even an error itself ^^
[G3 Developer Discussion [Developers Only]] Aaahh:
I know but you made changes, to what?
[G3 Developer Discussion [Developers Only]] manups4e:
i deleted bins files to remove errors and strangely libart warning was removed..
[G3 Developer Discussion [Developers Only]] manups4e:
so the rom now boots... but i have this annoying randoom poweroff right after boot that i can't get rid off ^^ i will upload to everyone the rom as soon as i will get rid of it ^^

my vid http://youtu.be/mF6G9uByWR4
[G3 Developer Discussion [Developers Only]] thatkindaguy:
How did you fix the power off at the app optimisation?
[G3 Developer Discussion [Developers Only]] manups4e:
i found the error that prevented the rom from booting but the poweroff right after boot is still there.. is the only thing i can't get rid off
[G3 Developer Discussion [Developers Only]] astonmartin214:
Okay since you ran it on D855 will this be able to run on VS985??
[G3 Developer Discussion [Developers Only]] thatkindaguy:
Can you post logcat and dmessage?
[G3 Developer Discussion [Developers Only]] manups4e:
I did in past days.. I will post a new one asap
[G3 Developer Discussion [Developers Only]] Aaahh:
What was it?
[G3 Developer Discussion [Developers Only]] manups4e:
to me it was gps.. i was missing libs and that was killing all the processes.. it boots now because i've added those libs
[G3 Developer Discussion [Developers Only]] Aaahh:
How did you figure that out?
[G3 Developer Discussion [Developers Only]] manups4e:
in logcat i was having lots of "fatal system exception libloc_eng.so not found" or libloc_eng.so and i added them from cyanogenmod... bluetooth gived me problems i replaced it from cyanogenmod and now it works.. the only problem left is the automatic shutdown
[G3 Developer Discussion [Developers Only]] thatkindaguy:
I saw in the video an error pop up, what so/process was it?
[G3 Developer Discussion [Developers Only]] :
I asked if you was missing files ?

And now you have some crashing apps though it isn't important if it crashes (depends on what apps though)

But a boot is a boot congrats
[G3 Developer Discussion [Developers Only]] Aaahh:
I similarly have the same problem now, although it was a framework, I removed references to it and now I wait for the build.
[G3 Developer Discussion [Developers Only]] skiman10:
Are you sure that's M? That looks like lollipop on the lock screen. M has a microphone in the bottom left, while lollipop has a phone icon like that.
[G3 Developer Discussion [Developers Only]] Aaahh:
Its the M we got

Add the frameworks from hammmer head
[G3 Developer Discussion [Developers Only]] skiman10:
Can we get a pic of the about phone screen? I see everything is crashing but if you are fast enough you might be able to get to it. I'm not sure you have M at all... It looks like lollipop still.
[G3 Developer Discussion [Developers Only]] TekGadgt:
Or a zip? Or at least the build.prop?
[G3 Developer Discussion [Developers Only]] TacoTuco:
Maybe a video of the ROM running?
[G3 Developer Discussion [Developers Only]] skiman10:
There is one but apps start crashing right after the lock screen is swiped up
[G3 Developer Discussion [Developers Only]] Aaahh:
It's 5.1.51 to be Honest.

---------- Post added at 04:08 AM ---------- Previous post was at 04:04 AM ----------

It's 5.1.51

The M stufff come later

There simple apks and frameworks that we can just copy
[G3 Developer Discussion [Developers Only]] skiman10:
Ahhh so it's the master branch, not M. So basically what Sony released. It only has the GPL pieces of M, not the features announced for M.

Sorry let's get back on topic of actually porting the m preview now
[G3 Developer Discussion [Developers Only]] :
Guys and girls stay calm bugs are need to be squeezed out ;)

No video or screen about my phone can't be displayed since it dies to fast. [MENTION=2849215]manups4e[/MENTION] when a New log is up I can try to help :)
[G3 Developer Discussion [Developers Only]] Aaahh:
Precisely, but only for now

We can add all the features easily.
[G3 Developer Discussion [Developers Only]] Aaahh:
https://forums.oneplus.net/threads/android-m-booting.321766/

It'd look like that

currently
[G3 Developer Discussion [Developers Only]] manups4e:
so let me explain.. nothing is crashing the crash in the video is the bluetooth share that crashes.. i fixed it using bluetooth.common.so lib from cm12.1 so.. everything work except radio and sensors.. i still have the problem of the randoom shutdown when the phone boots so i will upload the rom when that problem will be fixed ^^ still working on it
[G3 Developer Discussion [Developers Only]] manups4e:
for those who want logcat and dmesg :) here i just need to figure out who to not make it poweroff automatically

logcat:http://www.chopapp.com/#49q25ckr
[G3 Developer Discussion [Developers Only]] manups4e:
edit: problem solved... still shutting down while booting...
[G3 Developer Discussion [Developers Only]] manups4e:
Fixeeeeeeeeeeeeed
[G3 Developer Discussion [Developers Only]] manups4e:
i'm rebuilding from scratch to be sure that it works
[G3 Developer Discussion [Developers Only]] MidnightDevil:
Do you guys wanna create a IRC channel on Freenode to have these interactions in real time? :)
[G3 Developer Discussion [Developers Only]] :
Great work manups4e a little more work and understanding and you'll for sure become a dev ;)
[G3 Developer Discussion [Developers Only]] manups4e:
thank you :) it means a lot for me :)