Related
Hello I am trying to port the beloved OmniRom to my device which is a KLTE (Samsung Galaxy S5) I have successfully built the ROM from source using kernel and device configs from CM and of course some fixes and cherry picking. The issue I have now is that the ROM will not boot.
I stays at my carrier logo (Samsung) so it does not even let me cat-log. I tried to install the ROM and then restored a backup of Cyanogenmods system directory. It boots to android but all apps forceclose. I did this to see if it was an issue with the boot image and since it can boot to a different system partition I don't believe its a boot.img issue or kernel issue for that matter. Or is it?
Any help getting this to boot would be appreciated. I can provide build logs and my device repo if needed.
gigoo25 said:
Hello I am trying to port the beloved OmniRom to my device which is a KLTE (Samsung Galaxy S5) I have successfully built the ROM from source using kernel and device configs from CM and of course some fixes and cherry picking. The issue I have now is that the ROM will not boot.
I stays at my carrier logo (Samsung) so it does not even let me cat-log. I tried to install the ROM and then restored a backup of Cyanogenmods system directory. It boots to android but all apps forceclose. I did this to see if it was an issue with the boot image and since it can boot to a different system partition I don't believe its a boot.img issue or kernel issue for that matter. Or is it?
Any help getting this to boot would be appreciated. I can provide build logs and my device repo if needed.
Click to expand...
Click to collapse
MSM8974 is our first CAF chipset we're working on supporting.
I'd suggest looking at the Oppo find7/msm8974-common repos as nearly all initial CAF 8974 work is being done on the Find7.
you need android-5.1-caf branches for frameworks/av and frameworks/native for a CAF device until I finish the merge effort
Entropy512 said:
MSM8974 is our first CAF chipset we're working on supporting.
I'd suggest looking at the Oppo find7/msm8974-common repos as nearly all initial CAF 8974 work is being done on the Find7.
you need android-5.1-caf branches for frameworks/av and frameworks/native for a CAF device until I finish the merge effort
Click to expand...
Click to collapse
Thank you! That explains a lot. Maybe you can help me again? I keep coming across building with legacy opposed to CAF and to change it in the configs... What configs are they talking about?
Sent from my SM-G900T using XDA Free mobile app
gigoo25 said:
Thank you! That explains a lot. Maybe you can help me again? I keep coming across building with legacy opposed to CAF and to change it in the configs... What configs are they talking about?
Sent from my SM-G900T using XDA Free mobile app
Click to expand...
Click to collapse
You mean AOSP HALs? It's pretty rare for a CAF device to work with vanilla AOSP HALs.
It's the various QCOM_blah_VARIANT flags - 8974s are caf-bfam
Entropy512 said:
You mean AOSP HALs? It's pretty rare for a CAF device to work with vanilla AOSP HALs.
It's the various QCOM_blah_VARIANT flags - 8974s are caf-bfam
Click to expand...
Click to collapse
Updated my repo to 5.1 source but still getting errors. Here is the device configs that I am using. I am getting the same errors throughout.
First error was
Code:
frameworks/base/core/jni/android_view_Surface.cpp:206:14: error: 'class android::Surface' has no member named 'setDirtyRect'
surface->setDirtyRect(&rect);
Which I solved by cherry-picking THIS
Next I get an error that msmcal-hwdep.h is not found not sure how to fix this yet...
I recreated my devices config from scratch and uploaded it to git... Maybe you can take a look when you have some free time? It would mean alot! https://github.com/Gigoo25/android_device_samsung_klte
gigoo25 said:
Updated my repo to 5.1 source but still getting errors. Here is the device configs that I am using. I am getting the same errors throughout.
First error was
Code:
frameworks/base/core/jni/android_view_Surface.cpp:206:14: error: 'class android::Surface' has no member named 'setDirtyRect'
surface->setDirtyRect(&rect);
Which I solved by cherry-picking THIS
Next I get an error that msmcal-hwdep.h is not found not sure how to fix this yet...
I recreated my devices config from scratch and uploaded it to git... Maybe you can take a look when you have some free time? It would mean alot! https://github.com/Gigoo25/android_device_samsung_klte
Click to expand...
Click to collapse
msmcal_hwdep - look at the stiff in your kernel source under include/ - all of that header-y stuff in some of the Kconfigs
You shouldn't be cherrypicking that, I'm not sure why Max even put that up. Until I finish the CAF av/native merge, anyone declaring QCOM_HARDWARE should be using the android-5.1-caf branches of av and native
Entropy512 said:
msmcal_hwdep - look at the stiff in your kernel source under include/ - all of that header-y stuff in some of the Kconfigs
You shouldn't be cherrypicking that, I'm not sure why Max even put that up. Until I finish the CAF av/native merge, anyone declaring QCOM_HARDWARE should be using the android-5.1-caf branches of av and native
Click to expand...
Click to collapse
Awesome! alright will look into that
Sent from my SM-G900T using XDA Free mobile app
Entropy512 said:
msmcal_hwdep - look at the stiff in your kernel source under include/ - all of that header-y stuff in some of the Kconfigs
You shouldn't be cherrypicking that, I'm not sure why Max even put that up. Until I finish the CAF av/native merge, anyone declaring QCOM_HARDWARE should be using the android-5.1-caf branches of av and native
Click to expand...
Click to collapse
Having issues compiling the camera I get the error
Code:
device/samsung/klte/camera/CameraWrapper.cpp: In function 'char* camera_fixup_setparams(int, const char*)':
device/samsung/klte/camera/CameraWrapper.cpp:161:20: error: 'KEY_DIS' is not a member of 'android::CameraParameters'
params.set(android::CameraParameters::KEY_DIS, android::CameraParameters::DIS_DISABLE);
^
device/samsung/klte/camera/CameraWrapper.cpp:161:56: error: 'DIS_DISABLE' is not a member of 'android::CameraParameters'
params.set(android::CameraParameters::KEY_DIS, android::CameraParameters::DIS_DISABLE);
^
device/samsung/klte/camera/CameraWrapper.cpp:162:20: error: 'KEY_ZSL' is not a member of 'android::CameraParameters'
params.set(android::CameraParameters::KEY_ZSL, android::CameraParameters::ZSL_OFF);
^
device/samsung/klte/camera/CameraWrapper.cpp:162:56: error: 'ZSL_OFF' is not a member of 'android::CameraParameters'
params.set(android::CameraParameters::KEY_ZSL, android::CameraParameters::ZSL_OFF);
^
device/samsung/klte/camera/CameraWrapper.cpp:164:20: error: 'KEY_ZSL' is not a member of 'android::CameraParameters'
params.set(android::CameraParameters::KEY_ZSL, android::CameraParameters::ZSL_ON);
^
device/samsung/klte/camera/CameraWrapper.cpp:164:56: error: 'ZSL_ON' is not a member of 'android::CameraParameters'
params.set(android::CameraParameters::KEY_ZSL, android::CameraParameters::ZSL_ON);
^
make: *** [/home/rob/android/omni51/out/target/product/klte/obj/SHARED_LIBRARIES/camera.msm8974_intermediates/CameraWrapper.o] Error 1
make: *** Waiting for unfinished jobs...
Is this a framework issue?
gigoo25 said:
Having issues compiling the camera I get the error
Code:
device/samsung/klte/camera/CameraWrapper.cpp: In function 'char* camera_fixup_setparams(int, const char*)':
device/samsung/klte/camera/CameraWrapper.cpp:161:20: error: 'KEY_DIS' is not a member of 'android::CameraParameters'
params.set(android::CameraParameters::KEY_DIS, android::CameraParameters::DIS_DISABLE);
^
device/samsung/klte/camera/CameraWrapper.cpp:161:56: error: 'DIS_DISABLE' is not a member of 'android::CameraParameters'
params.set(android::CameraParameters::KEY_DIS, android::CameraParameters::DIS_DISABLE);
^
device/samsung/klte/camera/CameraWrapper.cpp:162:20: error: 'KEY_ZSL' is not a member of 'android::CameraParameters'
params.set(android::CameraParameters::KEY_ZSL, android::CameraParameters::ZSL_OFF);
^
device/samsung/klte/camera/CameraWrapper.cpp:162:56: error: 'ZSL_OFF' is not a member of 'android::CameraParameters'
params.set(android::CameraParameters::KEY_ZSL, android::CameraParameters::ZSL_OFF);
^
device/samsung/klte/camera/CameraWrapper.cpp:164:20: error: 'KEY_ZSL' is not a member of 'android::CameraParameters'
params.set(android::CameraParameters::KEY_ZSL, android::CameraParameters::ZSL_ON);
^
device/samsung/klte/camera/CameraWrapper.cpp:164:56: error: 'ZSL_ON' is not a member of 'android::CameraParameters'
params.set(android::CameraParameters::KEY_ZSL, android::CameraParameters::ZSL_ON);
^
make: *** [/home/rob/android/omni51/out/target/product/klte/obj/SHARED_LIBRARIES/camera.msm8974_intermediates/CameraWrapper.o] Error 1
make: *** Waiting for unfinished jobs...
Is this a framework issue?
Click to expand...
Click to collapse
Looks like maybe some missing Samsung patches
Entropy512 said:
Looks like maybe some missing Samsung patches
Click to expand...
Click to collapse
I appreciate all the help you have been giving me in trying to port Omni to the KLTE! I could not have done it without you!
I ended up having a booting and working build when I removed the camera and RIL
RIL gives me an error of
Code:
frameworks/opt/telephony/../../../device/samsung/klte/ril/telephony/java/com/android/internal/telephony/KlteRIL.java:282: error: no suitable constructor found for SignalStrength(int,int,int,int,int,int,int,int,int,int,int,int,int,boolean)
return new SignalStrength(gsmSignalStrength, gsmBitErrorRate, cdmaDbm, cdmaEcio, evdoDbm,
^
constructor SignalStrength.SignalStrength(Parcel) is not applicable
(actual and formal argument lists differ in length)
constructor SignalStrength.SignalStrength(SignalStrength) is not applicable
(actual and formal argument lists differ in length)
constructor SignalStrength.SignalStrength(int,int,int,int,int,int,int,boolean) is not applicable
(actual and formal argument lists differ in length)
constructor SignalStrength.SignalStrength(int,int,int,int,int,int,int,int,int,int,int,int,boolean) is not applicable
(actual and formal argument lists differ in length)
constructor SignalStrength.SignalStrength(boolean) is not applicable
(actual and formal argument lists differ in length)
constructor SignalStrength.SignalStrength() is not applicable
(actual and formal argument lists differ in length)
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
It should be a frameworks/opt/telephony issue correct? Except it doesn't display the full file path?
gigoo25 said:
I appreciate all the help you have been giving me in trying to port Omni to the KLTE! I could not have done it without you!
I ended up having a booting and working build when I removed the camera and RIL
RIL gives me an error of
Code:
frameworks/opt/telephony/../../../device/samsung/klte/ril/telephony/java/com/android/internal/telephony/KlteRIL.java:282: error: no suitable constructor found for SignalStrength(int,int,int,int,int,int,int,int,int,int,int,int,int,boolean)
return new SignalStrength(gsmSignalStrength, gsmBitErrorRate, cdmaDbm, cdmaEcio, evdoDbm,
^
constructor SignalStrength.SignalStrength(Parcel) is not applicable
(actual and formal argument lists differ in length)
constructor SignalStrength.SignalStrength(SignalStrength) is not applicable
(actual and formal argument lists differ in length)
constructor SignalStrength.SignalStrength(int,int,int,int,int,int,int,boolean) is not applicable
(actual and formal argument lists differ in length)
constructor SignalStrength.SignalStrength(int,int,int,int,int,int,int,int,int,int,int,int,boolean) is not applicable
(actual and formal argument lists differ in length)
constructor SignalStrength.SignalStrength(boolean) is not applicable
(actual and formal argument lists differ in length)
constructor SignalStrength.SignalStrength() is not applicable
(actual and formal argument lists differ in length)
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
It should be a frameworks/opt/telephony issue correct? Except it doesn't display the full file path?
Click to expand...
Click to collapse
It looks like the KLTE actually specifies its own RIL subclass (interesting trick, I've never seen that before) and that subclass is depending on something in frameworks/opt/tel that Omni doesn't have.
Either find the missing patch in f/opt/tel or figure out how to adapt KlteRIL.java
Entropy512 said:
It looks like the KLTE actually specifies its own RIL subclass (interesting trick, I've never seen that before) and that subclass is depending on something in frameworks/opt/tel that Omni doesn't have.
Either find the missing patch in f/opt/tel or figure out how to adapt KlteRIL.java
Click to expand...
Click to collapse
I seem to have gotten everything working fine besides the camera. The app and libraries compile fine but when the rom boots I cannot see it in the app drawer. When I try to launch it through the lockscreen it just force closes. Not sure what could be causing the problem? All the permissions seem to be checking out, and messing with the BoardConfiv and Device make files has not seemed to help. Any suggestions on how to fix this? Could it be a framework issue?
gigoo25 said:
I seem to have gotten everything working fine besides the camera. The app and libraries compile fine but when the rom boots I cannot see it in the app drawer. When I try to launch it through the lockscreen it just force closes. Not sure what could be causing the problem? All the permissions seem to be checking out, and messing with the BoardConfiv and Device make files has not seemed to help. Any suggestions on how to fix this? Could it be a framework issue?
Click to expand...
Click to collapse
Look through the logcat for camera errors, especially any errors about missing libraries.
Not appearing in app drawer indicates that Android doesn't think there is a camera present. There are 2349734297320 different things that could cause this - missing camera HAL dependency, kernel/HAL mismatch, many other things.
Entropy512 said:
Look through the logcat for camera errors, especially any errors about missing libraries.
Not appearing in app drawer indicates that Android doesn't think there is a camera present. There are 2349734297320 different things that could cause this - missing camera HAL dependency, kernel/HAL mismatch, many other things.
Click to expand...
Click to collapse
Here is what I found in the logcat
Code:
--------- beginning of crash
[ 06-01 20:08:07.366 3437: 3437 E/AndroidRuntime ]
FATAL EXCEPTION: main
Process: com.android.camera2, PID: 3437
java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.camera2/com.android.camera.CameraActivity}: java.lang.NullPointerException: Attempt to invoke virtual method 'void com.android.camera.util.PhotoSphereHelper$PanoramaViewHelper.onStart()' on a null object reference
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2325)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2387)
at android.app.ActivityThread.access$800(ActivityThread.java:151)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1303)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.java:5254)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)
Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'void com.android.camera.util.PhotoSphereHelper$PanoramaViewHelper.onStart()' on a null object reference
at com.android.camera.CameraActivity.onStartTasks(CameraActivity.java:1885)
at com.android.camera.util.QuickActivity.onStart(QuickActivity.java:111)
at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1236)
at android.app.Activity.performStart(Activity.java:6006)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2288)
... 10 more
gigoo25 said:
Here is what I found in the logcat
Code:
--------- beginning of crash
[ 06-01 20:08:07.366 3437: 3437 E/AndroidRuntime ]
FATAL EXCEPTION: main
Process: com.android.camera2, PID: 3437
java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.camera2/com.android.camera.CameraActivity}: java.lang.NullPointerException: Attempt to invoke virtual method 'void com.android.camera.util.PhotoSphereHelper$PanoramaViewHelper.onStart()' on a null object reference
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2325)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2387)
at android.app.ActivityThread.access$800(ActivityThread.java:151)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1303)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.java:5254)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)
Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'void com.android.camera.util.PhotoSphereHelper$PanoramaViewHelper.onStart()' on a null object reference
at com.android.camera.CameraActivity.onStartTasks(CameraActivity.java:1885)
at com.android.camera.util.QuickActivity.onStart(QuickActivity.java:111)
at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1236)
at android.app.Activity.performStart(Activity.java:6006)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2288)
... 10 more
Click to expand...
Click to collapse
Pretty much - if you can't figure out what is wrong from reading a logcat, most likely, you can't figure out what parts of the logcat are relevant and which are not.
That excerpt basically tells me nothing.
I assume that was from trying to forcefully start the camera with no camera actually present as far as Android was concerned. That's a symptom, not the root cause of the problem. Based on what you've described, the root cause of the problem will likely be visible even if no attempt is made to use the camera.
Entropy512 said:
Pretty much - if you can't figure out what is wrong from reading a logcat, most likely, you can't figure out what parts of the logcat are relevant and which are not.
That excerpt basically tells me nothing.
I assume that was from trying to forcefully start the camera with no camera actually present as far as Android was concerned. That's a symptom, not the root cause of the problem. Based on what you've described, the root cause of the problem will likely be visible even if no attempt is made to use the camera.
Click to expand...
Click to collapse
I've been messing around with the device configurations and logcats. I I think I have found the culprit for my camera not working. It shows that it loads the module but then fails to open it? Is this a CameraWrapper issue? Still trying to fix the camera so I can use this as a daily build but I have limited experience as a developer.
EDIT: Also the camera shows up on first boot but then disappears and says that the application is not installed. I'm trying to logcat it but not sure how to do that on the first boot without allowing my PC
EDIT2: From the looks of it searching the web it seems to be an issue with frameworks/av/camera/CameraParameters.cpp & frameworks/av/camera/include/CameraParameters.h
Code:
I/CameraService( 381): CameraService started (pid=381)
I/CameraService( 381): Loaded "MSM8974 Camera Wrapper" camera module
I/CameraWrapper( 381): camera_get_number_of_cameras
I/CameraWrapper( 381): check_vendor_module
I/PackageManager( 741): /system/priv-app/MmsService changed; collecting certs
I/PackageManager( 741): /system/priv-app/OmniSwitch changed; collecting certs
E/HAL ( 381): load: module=/system/lib/hw/camera.vendor.msm8974.so
E/HAL ( 381): dlopen failed: cannot locate symbol "_ZN7android16CameraParameters25KEY_DYNAMIC_RANGE_CONTROLE" referenced by "camera.vendor.msm8974.so"...
E/CameraWrapper( 381): failed to open vendor camera module
gigoo25 said:
I've been messing around with the device configurations and logcats. I I think I have found the culprit for my camera not working. It shows that it loads the module but then fails to open it? Is this a CameraWrapper issue? Still trying to fix the camera so I can use this as a daily build but I have limited experience as a developer.
EDIT: Also the camera shows up on first boot but then disappears and says that the application is not installed. I'm trying to logcat it but not sure how to do that on the first boot without allowing my PC
EDIT2: From the looks of it searching the web it seems to be an issue with frameworks/av/camera/CameraParameters.cpp & frameworks/av/camera/include/CameraParameters.h
Code:
I/CameraService( 381): CameraService started (pid=381)
I/CameraService( 381): Loaded "MSM8974 Camera Wrapper" camera module
I/CameraWrapper( 381): camera_get_number_of_cameras
I/CameraWrapper( 381): check_vendor_module
I/PackageManager( 741): /system/priv-app/MmsService changed; collecting certs
I/PackageManager( 741): /system/priv-app/OmniSwitch changed; collecting certs
E/HAL ( 381): load: module=/system/lib/hw/camera.vendor.msm8974.so
E/HAL ( 381): dlopen failed: cannot locate symbol "_ZN7android16CameraParameters25KEY_DYNAMIC_RANGE_CONTROLE" referenced by "camera.vendor.msm8974.so"...
E/CameraWrapper( 381): failed to open vendor camera module
Click to expand...
Click to collapse
Looks like a patch for CameraParameters needed by your device is missing since no one has tried to bring that device up before, or hasn't tried bringing it up with 5.x
Since it's a Qualcomm-based device and likely using CAF repos, you'll probably have to patch frameworks/av-caf and not frameworks/av - see https://lists.omnirom.org/pipermail/maintainers/2015-June/000101.html for details (we need to add this info to the wiki...)
Entropy512 said:
Looks like a patch for CameraParameters needed by your device is missing since no one has tried to bring that device up before, or hasn't tried bringing it up with 5.x
Since it's a Qualcomm-based device and likely using CAF repos, you'll probably have to patch frameworks/av-caf and not frameworks/av - see https://lists.omnirom.org/pipermail/maintainers/2015-June/000101.html for details (we need to add this info to the wiki...)
Click to expand...
Click to collapse
So I would have to split av into two folders then applying I believe THIS patch to av-caf in order to compile it properly?
Also does native-caf branch still have to be merged before compiling?
gigoo25 said:
So I would have to split av into two folders then applying I believe THIS patch to av-caf in order to compile it properly?
Also does native-caf branch still have to be merged before compiling?
Click to expand...
Click to collapse
Well, the splitting of av is already done. Native is already merged with ifdefs (it didn't require nearly as much ifdefing as av, so we have a "unified" CAF+AOSP native). The only thing that is needed for device maintainers is adding av-caf to omni.dependencies - see the maintainers list post I linked to, or look at the Oppo find7 history.
So once you're pulling in av-caf via omni.dependencies, you should be able to apply that patch to av-caf and then submit it to Gerrit for review.
You might want to start idling in IRC, #omni is where most device maintainers are (in fact, all maintainers for supported devices idle their routinely, it's now a requirement for maintainers to routinely idle in IRC so they can see what's going on/people can ping them with questions.)
Entropy512 said:
Well, the splitting of av is already done. Native is already merged with ifdefs (it didn't require nearly as much ifdefing as av, so we have a "unified" CAF+AOSP native). The only thing that is needed for device maintainers is adding av-caf to omni.dependencies - see the maintainers list post I linked to, or look at the Oppo find7 history.
So once you're pulling in av-caf via omni.dependencies, you should be able to apply that patch to av-caf and then submit it to Gerrit for review.
You might want to start idling in IRC, #omni is where most device maintainers are (in fact, all maintainers for supported devices idle their routinely, it's now a requirement for maintainers to routinely idle in IRC so they can see what's going on/people can ping them with questions.)
Click to expand...
Click to collapse
Turns out I might of fixed the problem. Instead of messing with frameworks/av I can just override it with a file inside include/camera? Looking back at the Cyanogenmod repo for my device THIS is present while in my source it is not.
Compiling now. Will post results after.
https://developers.google.com/android/images#shamu
Direct link: https://dl.google.com/dl/android/aosp/shamu-nbd91p-factory-987282ff.zip
anything different?
Not really, but it is nice to see the Nexus 6 get a second Nougat image and update. There is also a Marshmellow update for the Nexus 6 with the November security patch as well. Personally, I think N runs a little better on the Nexus 6, especially with the Pixel Launcher that can be found in the Themes and Apps area.
bootloader is different
Anyone want to pull radio and bootloader and post just that? Work blocks dl.google.com and drive. :'(
Sent from my iPhone 6+s using Tapatalk
SynisterWolf said:
Anyone want to pull radio and bootloader and post just that? Work blocks dl.google.com and drive. :'(
Sent from my iPhone 6+s using Tapatalk
Click to expand...
Click to collapse
Attached bootloader to this post, but here is a second link: https://www.dropbox.com/s/f4olqe54mab8dp6/bootloader-shamu-moto-apq8084-72.01.img?dl=0
Radio: https://www.dropbox.com/s/3ji28xwkebk2siq/radio-shamu-d4.01-9625-05.42+fsg-9625-02.113.img?dl=0
Radio is the same.
AOSP Changelog for NBD91P/7.0.0_r19 from NBD90Z/7.0.0_r14 for Shamu:
project build/
bec256f NBD91P
cbd12e9 NBF25
86f539b NBD91O
8d4b434 NBF24
ab07e94 Update security string to 2016-11-06 for nyc
b253a56 NBD91N
18d1ae4 NBD91M
0ffb924 NDB91M
99b9cfa NBD91L
9f47494 NBD91K
bc5db48 NBE92
2efe2e5 NBD91J
5c85641 NBD91I
91eaf6a NBD91H
2f25f53 NBD91G
79af65b NBD91F
52257ea NBD91E
2c0132f Updating security string to 2016-11-05 on nyc-dev
b65367b Updating Security String to 2016-11-01 on nyc-dev
10eaafa NBE89
e060660 NBD91D
5bbdbab NBD91C
4aaa5d8 NBD91B
8547561 Updating security string to 2016-11-05 on nyc-dev
c806aef Updating Security String to 2016-11-01 on nyc-dev
project device/moto/shamu/
7bb3812 shamu: remove discard in fstab
a84b0eb Revert "Path fix for backend connection to FE upon call disconnection"
29a0aaa Revert "Path fix for backend connection to FE upon call disconnection"
6427d7c allow empty
4b8d27e Revert "Path fix for backend connection to FE upon call disconnection"
project external/chromium-webview/
fe818f1 resolve merge conflicts of e9d901a to nyc-dev
a59bede resolve merge conflicts of e9d901a to nyc-dev
project external/conscrypt/
87d7551 Fix typo in name of des-ede mapping
9e2cb54 Fix typo in name of des-ede mapping
project external/expat/
a300f14 Security Vulnerability - CVE-2012-6702 and CVE-2016-5300
f193e66 Security Vulnerability - CVE-2012-6702 and CVE-2016-5300
project external/libavc/
1136e78 Decoder: Fixes for handling errors in multi-slice MB Aff streams
8b2f1c9 Fix in the case of invalid SPS PPS
8a9474c Decoder: Fixes for handling errors in multi-slice MB Aff streams
0f6a66d Fix in the case of invalid SPS PPS
project external/skia/
3272ed3 Fix rewinding bug in SkJpegCodec (cherry picked from Skia)
project frameworks/av/
5c15486 IOMX: do not clear buffer if it's allocated by component
c283e75 IOMX: allow configuration after going to loaded state
1f3fb66 IOMX: do not convert ANWB to gralloc source in emptyBuffer
9c55146 IOMX: do not clear buffer if it's allocated by component
eeedb2d IOMX: allow configuration after going to loaded state
d06c60b IOMX: do not convert ANWB to gralloc source in emptyBuffer
36f4e00 Limit mp4 atom size to something reasonable
604b74f SampleIterator: clear members on seekTo error
2d500e6 Check mprotect result
5e4602b OMXNodeInstance: sanity check portIndex.
5888c28 Fix free-after-use for MediaHTTP
8a38d3a Radio: get service by value.
a03e793 SoundTrigger: get service by value.
09f8f64 Fix stack content leak vulnerability in mediaserver
d25dee8 Fix potential overflow in Visualizer effect
6f3283e DO NOT MERGE: IOMX: work against metadata buffer spoofing
34b14ca Limit mp4 atom size to something reasonable
075c936 SampleIterator: clear members on seekTo error
380e846 Check mprotect result
cf4e570 OMXNodeInstance: sanity check portIndex.
acb30c5 Fix free-after-use for MediaHTTP
ec795b4 Radio: get service by value.
cb129c1 SoundTrigger: get service by value.
eaaf2c6 Fix stack content leak vulnerability in mediaserver
4b38366 Fix potential overflow in Visualizer effect
707f2a4 DO NOT MERGE: IOMX: work against metadata buffer spoofing
project frameworks/base/
cd2f75a LocationManager - Handle Shutdown for right User
435b97b DO NOT MERGE ANYWHERE: ImageReader: Add discardFreeBuffers method
7d96a1a Fix NPE for WifiConfiguration in AccessPoint.
be965e1 DO NOT MERGE - fix truncated boot sound
e612ba0 LocationManager - Handle Shutdown for right User
63d556a DO NOT MERGE ANYWHERE: ImageReader: Add discardFreeBuffers method
76d2d22 Avoid crashing when downloading MitM'd PAC that is too big am: 7d2198b586 am: 9c1cb7a273 am: 6634e90ad7 am: 66ee2296a9
03cc966 Use "all_downloads" instead of "my_downloads".
20384cc DO NOT MERGE Check caller for sending media key to global priority session
7beb6c2 Fix build break due to automerge of 7d2198b5
c46705b Catch all exceptions when parsing IME meta data
084a5b4 Fix deadlock in AcitivityManagerService.
072b4bd Only return password for account session flow if the caller is signed with system key and have get_password permission.
7e2d478 Ensure munmap matches mmap
1e70481 Fix setPairingConfirmation permissions issue (2/2)
41cdd05 DO NOT MERGE) ExifInterface: Make saveAttributes throw an exception before change
d20378f Backport changes to whitelist sockets opened by the zygote.
d3c1438 DO NOT MERGE Stop work challenge freeform bypass
b8c8f07 DO NOT MERGE - fix truncated boot sound
6db2c83 LocationManager - Handle Shutdown for right User
af7c2a7 Avoid crashing when downloading MitM'd PAC that is too big am: 7d2198b586 am: 9c1cb7a273 am: 6634e90ad7 am: 66ee2296a9
8dacd6f DO NOT MERGE Check caller for sending media key to global priority session
a87d513 Fix build break due to automerge of 7d2198b5
f30cfcb Catch all exceptions when parsing IME meta data
df4b2f6 Fix deadlock in AcitivityManagerService.
aa8226a Only return password for account session flow if the caller is signed with system key and have get_password permission.
7dc3969 Ensure munmap matches mmap
5dd5769 Fix setPairingConfirmation permissions issue (2/2)
6ff2f44 DO NOT MERGE) ExifInterface: Make saveAttributes throw an exception before change
388c9b2 Backport changes to whitelist sockets opened by the zygote.
63c82e4 DO NOT MERGE Stop work challenge freeform bypass
df0de20 Use "all_downloads" instead of "my_downloads".
project frameworks/native/
1a54d9d DO NOT MERGE ANYWHERE: BufferQueue consumers: Add discardFreeBuffer method
8b2de34 DO NOT MERGE ANYWHERE: BufferQueue consumers: Add discardFreeBuffer method
fe92e27 DO NOT MERGE ANYWHERE: BufferQueue consumers: Add discardFreeBuffer method
project frameworks/opt/telephony/
27af576 Remove flag from intent sent from Catservice to StkApp.
423614c Remove flag from intent sent from Catservice to StkApp.
8ac0b81 Remove flag from intent sent from Catservice to StkApp.
project hardware/qcom/audio/
cd259b2 Fix potential overflow in Visualizer effect
e239efc Fix potential overflow in Visualizer effect
project libcore/
2ff5d78 sun.security.util: check lengths in DER encoding are non-negative
8376309 sun.security.util: check lengths in DER encoding are non-negative
project packages/apps/Bluetooth/
3f9497e Fix setPairingConfirmation permissions issue (1/2)
46cfeaa Fix setPairingConfirmation permissions issue (1/2)
project packages/apps/Launcher3/
b4810a3 Preventing a shortcut which requires permissions from being added to homescreen
93a28fa Preventing a shortcut which requires permissions from being added to homescreen
project packages/apps/Settings/
f04e4b7 Remove help links when device is not provisioned. DO NOT MERGE
9058c8c Null check intent before starting "learn more".
0b493c0 Remove help links when device is not provisioned. DO NOT MERGE
31d9b19 Null check intent before starting "learn more".
project packages/apps/Stk/
81eb827 Make stk app FBE aware.
aadea71 Make stk app FBE aware.
26159e7 Make stk app FBE aware.
project packages/providers/DownloadProvider/
fad2923 Enforce calling identity before clearing.
1db23ff Enforce calling identity before clearing.
project system/core/
87d2f2d liblog: add __android_log_close()
a3afe4b liblog: add __android_log_close()
project system/media/
0a1cd07 Fix potential overflow in Visualizer effect
07fa6a0 Fix potential overflow in Visualizer effect
project system/sepolicy/
68e9f19 DO NOT MERGE - fix truncated boot sound.
d2f8104 Allow the zygote to stat all files it opens.
d2d935b DO NOT MERGE - fix truncated boot sound.
539f03c Allow the zygote to stat all files it opens.
Is the Bluetooth bug fixed in this one?
Sent from my Nexus 6 using XDA-Developers mobile app
sorry but after fresh factory install can we root NBD91P? which supersu we should be using?
sunandoghosh said:
sorry but after fresh factory install can we root NBD91P? which supersu we should be using?
Click to expand...
Click to collapse
I did fresh install and rooted with SuperSU 2.78 SR3
can be found here: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
TMG1961 said:
I did fresh install and rooted with SuperSU 2.78 SR3
can be found here: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Click to expand...
Click to collapse
I have not been able to get SuperSU 2.78 SR2 or SuperSU 2.78 SR3 to work on on the current (NBD91P) or initial (NBD90Z) releases of Nougat. SR1 works without issue. I can't figure out what I am doing wrong.
Thank you seniors for replying but based on last two replies i would request for reconfirmation...just scared at the thought of doing whole process again. Kindly confirm.
alryder said:
I have not been able to get SuperSU 2.78 SR2 or SuperSU 2.78 SR3 to work on on the current (NBD91P) or initial (NBD90Z) releases of Nougat. SR1 works without issue. I can't figure out what I am doing wrong.
Click to expand...
Click to collapse
I assume you finish the rom installation and then install twrp and flash supersu?
Never had any problems with installing supersu so have no experience with it not working
Curious. I currently have TWRP installed and am running the stock flashable NDB90Z build. Could I flash the OP zip and get back on with the OTA updates? I no longer care about superuser, root, and such. Thanks!
Wifi bug fix!!!
I am also interested to know if this fixes the wifi bug!
Thanks,
sandip_909 said:
Is the Bluetooth bug fixed in this one?
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
I'm hoping this fixes my one and only major issue on 7.0: after certain usage the phone gets extremely sluggish until reboot. Happens every day or two.
Never had this on Marshmallow. Running stock no modifications after a full wipe, clean flash of 7.0, then full wipe again. Redid all settings manually.
Anyone else?
TMG1961 said:
I assume you finish the rom installation and then install twrp and flash supersu?
Never had any problems with installing supersu so have no experience with it not working
Click to expand...
Click to collapse
Yep, that's exactly what I do. It installs fine and my phone boots without issue but none of my apps are able to get root access. It's really weird.
After upgrading to this build I can't apple substratum themes anymore. Doing so will result in a bootloop and I have to remove the overlay folder with TWRP. Is this a general issue with substratum?
TMG1961 said:
I assume you finish the rom installation and then install twrp and flash supersu?
Never had any problems with installing supersu so have no experience with it not working
Click to expand...
Click to collapse
alryder said:
Yep, that's exactly what I do. It installs fine and my phone boots without issue but none of my apps are able to get root access. It's really weird.
Click to expand...
Click to collapse
I installed SR3 again, the phone rebooted twice which is normal from past installs I have done, but still no root access after fully booted. Manually rebooted again and I now have root access with SR3. I don't know why the extra reboot was needed but I'm glad its working now.
https://developers.google.com/android/images
https://developers.google.com/android/ota
NOF26V everyone else
NOF26W Rogers Only
Same bootloader and Radio.
RRO looks like it works with installing the framework on this build...Used N/pixel dark theme, installed the framework (not framework-less) and didn't get a bootloop...Tread lightly but I know it works with that theme
I noticed that the factory images say that NOF26W is Rodgers only, but the OTA zip does not mention that. I would imagine that the OTA would follow the same guidelines, but I do find it odd that it's not specifically noted.
Google sure likes to use the letter "V" a lot.
I kind of wonder if it actually stands for something and if so, what.
Can someone please explain to me what is this 'Rodgers' only? Yet to get the update for 7.1.2 Beta (NPG05E).
Am on the January security version of 7.1.1 and have rooted my phone using the boot-to-root method. How do I update to the February version and then get back root?
Will flashing the factory image of Feb version (after deleting -w) and then using the same method of root, work?
c0des said:
Can someone please explain to me what is this 'Rodgers' only?
Click to expand...
Click to collapse
Rogers Telecom. Toronto, Ontario, Canada.
zaydenQ said:
Am on the January security version of 7.1.1 and have rooted my phone using the boot-to-root method. How do I update to the February version and then get back root?
Will flashing the factory image of Feb version (after deleting -w) and then using the same method of root, work?
Click to expand...
Click to collapse
flash the factory image of Feb version (after deleting -w)
temporary boot into twrp-3.0.2-0-RC1 in fastboot mode
from twrp flash SR3-SuperSU-v2.79-SR3
reboot the device
Note : the steps above assume you are on stock recovery and unlocked bootloader
touns_j said:
flash the factory image of Feb version (after deleting -w)
temporary boot into twrp-3.0.2-0-RC1 in fastboot mode
from twrp flash SR3-SuperSU-v2.79-SR3
reboot the device
Note : the steps above assume you are on stock recovery and unlocked bootloader
Click to expand...
Click to collapse
Thank you. I will follow this process. Hope this version doesn't reduce my battery SOT!
zaydenQ said:
Thank you. I will follow this process. Hope this version doesn't reduce my battery SOT!
Click to expand...
Click to collapse
it should work out just fine , by the way press the thanks button instead of writing thanks lol
touns_j said:
it should work out just fine , by the way press the thanks button instead of writing thanks lol
Click to expand...
Click to collapse
Done lol.
AOSP commits from 7.1.1_r8\NMF26U to 7.1.1_r20\NOF26V
project bionic/
0f6bfb7 Check for bad packets in getaddrinfo.c's getanswer.
project build/
e18db36 NOF26V
3c17cdf NOF26U
e0183ab Update Security String to 2017-02-05 on nyc-dev
e789b3b Update Security String to 2017-02-01 on nyc-dev
44f3bdf NOF26T
project device/google/marlin/
8ca6bce marlin: audio: Update volume level of volume listener (1007)
project device/htc/flounder/
cd647e3 Fix security issue in Visualizer effect
project external/libavc/
e08e31d Decoder: Fix in checking for valid profile flags
project external/libgdx/
49f2149 Fix security vulnerability
project external/libhevc/
f48c012 Fixed handling invalid chroma tu size for error clips
dd0f2d3 Fixed out of bound reads in stack variables
26b6626 Fix in Chroma SAO for non-multiple of 8 height
project frameworks/av/
edc723b Fix security vulnerability: potential OOB write in audioserver
c88e62a Effect: Use local cached data for Effect commit
project frameworks/base/
c639cb6 Do not write if apply() did not change the file.
0627670 Only persist last Shared Preferences state
70e13cc [DO NOT MERGE] Fix vulnerability in MemoryIntArray - fix build file
de5e345 Fix vulnerability in MemoryIntArray
36772fc DO NOT MERGE. Retain DownloadManager Uri grants when clearing.
db57376 DO NOT MERGE: Check provider access for content changes.
project frameworks/native/
bfd36c3 Fix security vulneratibly 31960359
922ab40 Fix SF security vulnerability: 32706020
7c1f953 Correct overflow check in Parcel resize code
project hardware/libhardware/
8a1906a Fix security vulnerability: potential OOB write in audioserver
project hardware/qcom/audio/
2692d9d Fix for audio distortion on speaker
project libcore/
9430b2e Fix URL parser may return wrong host name
project packages/apps/Bluetooth/
cbced75 Remove MANAGE_DOCUMENTS permission as it isn't needed
project packages/apps/Messaging/
b5ef563 resolve merge conflicts of eafd58a to nyc-dev
9879d17 32807795 Security Vulnerability - AOSP Messaging App: thirdparty can attach private files from "/data/data/com.android.messaging/" directory to the messaging app.
47971bc 32322450 Security Vulnerability - heap buffer overflow in libgiftranscode.so
project packages/apps/UnifiedEmail/
1de59f7 Don't allow file attachment from /data through GET_CONTENT.
project system/bt/
60bbbae Remove position dependent lookup tables in AT command parser
project system/core/
8d367d2 change /data/bugreports to /bugreports
project system/sepolicy/
ded2ca4 label /bugreports
touns_j said:
flash the factory image of Feb version (after deleting -w)
Click to expand...
Click to collapse
will this bring back the official recovery?
bush911 said:
will this bring back the official recovery?
Click to expand...
Click to collapse
Yes flashing a factory image will restore stock recovery. If you want to keep Twrp you can flash the ota update through Twrp using the sideload feature. The ota updates can be found at the link below.
https://developers.google.com/android/ota
xdatastic said:
AOSP commits from 7.1.1_r8\NMF26U to 7.1.1_r20\NOF26V
project bionic/
0f6bfb7 Check for bad packets in getaddrinfo.c's getanswer.
project build/
e18db36 NOF26V
3c17cdf NOF26U
e0183ab Update Security String to 2017-02-05 on nyc-dev
e789b3b Update Security String to 2017-02-01 on nyc-dev
44f3bdf NOF26T
project device/google/marlin/
8ca6bce marlin: audio: Update volume level of volume listener (1007)
project device/htc/flounder/
cd647e3 Fix security issue in Visualizer effect
project external/libavc/
e08e31d Decoder: Fix in checking for valid profile flags
project external/libgdx/
49f2149 Fix security vulnerability
project external/libhevc/
f48c012 Fixed handling invalid chroma tu size for error clips
dd0f2d3 Fixed out of bound reads in stack variables
26b6626 Fix in Chroma SAO for non-multiple of 8 height
project frameworks/av/
edc723b Fix security vulnerability: potential OOB write in audioserver
c88e62a Effect: Use local cached data for Effect commit
project frameworks/base/
c639cb6 Do not write if apply() did not change the file.
0627670 Only persist last Shared Preferences state
70e13cc [DO NOT MERGE] Fix vulnerability in MemoryIntArray - fix build file
de5e345 Fix vulnerability in MemoryIntArray
36772fc DO NOT MERGE. Retain DownloadManager Uri grants when clearing.
db57376 DO NOT MERGE: Check provider access for content changes.
project frameworks/native/
bfd36c3 Fix security vulneratibly 31960359
922ab40 Fix SF security vulnerability: 32706020
7c1f953 Correct overflow check in Parcel resize code
project hardware/libhardware/
8a1906a Fix security vulnerability: potential OOB write in audioserver
project hardware/qcom/audio/
2692d9d Fix for audio distortion on speaker
project libcore/
9430b2e Fix URL parser may return wrong host name
project packages/apps/Bluetooth/
cbced75 Remove MANAGE_DOCUMENTS permission as it isn't needed
project packages/apps/Messaging/
b5ef563 resolve merge conflicts of eafd58a to nyc-dev
9879d17 32807795 Security Vulnerability - AOSP Messaging App: thirdparty can attach private files from "/data/data/com.android.messaging/" directory to the messaging app.
47971bc 32322450 Security Vulnerability - heap buffer overflow in libgiftranscode.so
project packages/apps/UnifiedEmail/
1de59f7 Don't allow file attachment from /data through GET_CONTENT.
project system/bt/
60bbbae Remove position dependent lookup tables in AT command parser
project system/core/
8d367d2 change /data/bugreports to /bugreports
project system/sepolicy/
ded2ca4 label /bugreports
Click to expand...
Click to collapse
where did you get this "changelog" ?
thanks
Ariyax said:
where did you get this "changelog" ?
thanks
Click to expand...
Click to collapse
Did a diff of the AOSP source code.
http://source.android.com/source/build-numbers.html
M9guy said:
Yes flashing a factory image will restore stock recovery. If you want to keep Twrp you can flash the ota update through Twrp using the sideload feature. The ota updates can be found at the link below.
https://developers.google.com/android/ota
Click to expand...
Click to collapse
So, to be clear, I can follow Google's instructions copied below using TWRP instead of the factory recovery and the result will be an updated system with no data lost?
1) Download the appropriate update image for your device below.
2) Verify the checksum of the image: the OTA mechanism has a built-in validation feature, but verifying will save you some time if the file is incomplete. The last portion of the filename is the first 8 digits of its SHA-256 checksum; the full SHA-256 checksum is also shown next to the download link.
3) With the device powered on and USB debugging enabled, execute: adb reboot recovery The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
4) Hold the Power button and press Volume Up once, and a menu will appear. Select the option Apply update from ADB.
5) Run the following command:
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
6) Once the update finishes, reboot the phone by choosing Reboot the system now.
For security, you should disable USB debugging when the device is not being updated.
mlin said:
So, to be clear, I can follow Google's instructions copied below using TWRP instead of the factory recovery and the result will be an updated system with no data lost?
1) Download the appropriate update image for your device below.
2) Verify the checksum of the image: the OTA mechanism has a built-in validation feature, but verifying will save you some time if the file is incomplete. The last portion of the filename is the first 8 digits of its SHA-256 checksum; the full SHA-256 checksum is also shown next to the download link.
3) With the device powered on and USB debugging enabled, execute: adb reboot recovery The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
4) Hold the Power button and press Volume Up once, and a menu will appear. Select the option Apply update from ADB.
5) Run the following command:
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
6) Once the update finishes, reboot the phone by choosing Reboot the system now.
For security, you should disable USB debugging when the device is not being updated.
Click to expand...
Click to collapse
Googles instructions are for with a stock recovery and not for Twrp recovery. If you have stock recovery you can follow the listed google instructions and it should not wipe your data as only flashing a full factory image will wipe everything including your user data.
If you have Twrp recovery you can download the ota update at that link I provided then you can use the sideload feature in Twrp to flash the ota update and it will not wipe your data.
International Version, NJH47D
https://dl.google.com/dl/android/aosp/marlin-njh47d-factory-5ba1ef91.zip
Other versions:
NHG47O, Verizon: https://dl.google.com/dl/android/aosp/marlin-nhg47o-factory-a2b41619.zip
NKG47M, T-Mobile, Fi carriers: https://dl.google.com/dl/android/aosp/marlin-nkg47m-factory-f0fa887a.zip
NZH54B, Deutsche Telekom: https://dl.google.com/dl/android/aosp/marlin-nzh54b-factory-857c0179.zip
Only 70mb mustn't be anything too exciting.
Sent from my BTV-W09 using Tapatalk
Installed. Booted to TWRP, flashed SU 2.79 RC3. All is well, no bootloader signing needed. It did reboot twice after SU install. I did not install TWRP.
Here come the folks asking on the sly in every rom thread when the build will be updated.
ahent said:
Only 70mb mustn't be anything too exciting.
Sent from my BTV-W09 using Tapatalk
Click to expand...
Click to collapse
???
For Fi carriers, it's 842MB for the OTA/ 1.8GB for the factory.
Interesting, I have a Google play pixel xl on Verizon service, the NHG47O update is only 70mb.
Sent from my Pixel XL using Tapatalk
ahent said:
Interesting, I have a Google play pixel xl on Verizon service, the NHG47O update is only 70mb.
Click to expand...
Click to collapse
The ota image on the webpage is 800mb give or take
The factory image is 1.8gb give or take.
I switched from Sprint to Verizon on my Google store pixel. Should I start flashing verizon edition roms, or stick with generic?
Tb0n3 said:
I switched from Sprint to Verizon on my Google store pixel. Should I start flashing verizon edition roms, or stick with generic?
Click to expand...
Click to collapse
I mean the carrier specific builds have tweaks that could arguably be beneficial for connectivity. Example being an update or two ago there were changes for Verizon that were said to improve wifi calling. So I figure unless something is stopping you why not flash builds specific to your device
pcriz said:
Here come the folks asking on the sly in every rom thread when the build will be updated.
Click to expand...
Click to collapse
Could you help me out with something? kindly let me know why everyone is instructing to remove " the -w" ? it is "flash-all.bat" or another thing?
crazykas said:
Could you help me out with something? kindly let me know why everyone is instructing to remove " the -w" ? it is "flash-all.bat" or another thing?
Click to expand...
Click to collapse
It's the flash all.bat. You can edit bat files in a text editor.
One of the last commands is essentially a factory reset before the device reboots. If you want to keep your app data through a flash all then remove the -w switch.
You may ask why wouldnt you wipe, for me it was usually if I wanted to dirty update to a newer firmware since we get monthly builds.
I run the flash all with -w removed, fastboot recovery, reflash twrp, reflash my rom, root and wipe the caches. Then boot up to my rom with everything intact and my base advanced one month.
pcriz said:
It's the flash all.bat. You can edit bat files in a text editor.
One of the last commands is essentially a factory reset before the device reboots. If you want to keep your app data through a flash all then remove the -w switch.
You may ask why wouldnt you wipe, for me it was usually if I wanted to dirty update to a newer firmware since we get monthly builds.
I run the flash all with -w removed, fastboot recovery, reflash twrp, reflash my rom, root and wipe the caches. Then boot up to my rom with everything intact and my base advanced one month.
Click to expand...
Click to collapse
You mean -w at last "-w update image-marlin-njh47d.zip" right? so when flashing a rom no need to full wipe then? coz i've never done dirty flash in my life coz always though something issue will happen...:laugh: and removing -w will not erase userdata too then
crazykas said:
Could you help me out with something? kindly let me know why everyone is instructing to remove " the -w" ? it is "flash-all.bat" or another thing?
Click to expand...
Click to collapse
You remove that from inside the flash-all.bat file before you run it so you do not wipe your apps and data. So you open it with notepad, look for the -w near the end and delete it. Then save it.
AOSP commits for NJH47B/7.1.2_r17 to NJH47D/7.1.2_r24
For anyone interested, here are the AOSP commits for NJH47B/7.1.2_r17 to NJH47D/7.1.2_r24
project bionic/
b928447 linker: remove link from external library on unload
project build/
2dd5b56 Version bump to NJH47D
df00a9a [DO NOT MERGE]Updating security string to 2017-07-05 on nyc-dev bug:38342695 (cherry picked from commit 96d958c34509a65e5f7787945f9923fb44c42f05)
f1af383 [DO NOT MERGE]Updating security string to 2017-07-01 on nyc-dev bug:38342695 (cherry picked from commit 77dad3dfcd677136f6657e1b95dd84ed1be1d728)
project device/google/marlin-kernel/
fbab783 Merge cherrypicks of [2307556, 2307630, 2307631, 2307557, 2307632, 2307656, 2307743, 2307635, 2307799, 2307577, 2307800, 2307707, 2307803, 2307781, 2307773, 2307637, 2307804, 2307618, 2307734, 2307708, 2307805, 2307709, 2307806, 2307820, 2307746, 2307774, 2307839, 2307735, 2307782, 2307808, 2307840, 2307738, 2307783, 2307749, 2307775, 2307860, 2307899, 2307822, 2307823, 2307880, 2307778, 2307825, 2307882, 2307787, 2307919, 2307844, 2307905, 2307883, 2307829, 2307907, 2307832, 2307944, 2307945, 2307911] into nyc-mr2-pixel-monthly-release
project external/boringssl/
b1aad23 CVE 2016-2109 fix
project external/dng_sdk/
35aa468 Throw exception on integer overflow in dng_ifd.cpp.
project external/libavc/
9490be3 Decoder: Fix end of bitstream error.
77af827 Decoder: Fix allocation for Mbaff weight matrix
776ddbc Decoder: Initialize MB info buffer to zero.
4081cc4 Decoder: Fixed flag u1_top_bottom_decoded.
abb5cfb Decoder: Added an error check while parsing PPS.
c2d3ce5 Fix stack buffer overflow in ih264d_process_intra_mb
76f6a3e Decoder: Fix in reference list initialization.
d4b34e3 Decoder: Fixes in accessing mbaff flag in error cases
9759612 Fix in the case of MMCO 3 (long term reference idx).
project external/libgdx/
c97a2c1 Fix 36385715 heap overflow when loading HDR files
4702c50 Fix Pixmap overflow. Bug 36621442
e3b5da5 Fix series of JPEG vulnerabilities
e0ddaf0 Fix 36385715 heap overflow when loading HDR files
project external/libhevc/
6523680 Fix heap buffer overflow while searching for valid PPS
cf376a7 Check for buffer overflow in pps/slice header parsing
62e944d memset SPS to zero
d6fd3d7 Fix reallocation for new sps
011b658 DO NOT MERGE Handle streams with change in max_dec_buffering/num_reorder_frames without resolution change
4667b9e Check for cpb cnt in hrd parsing
project external/libmpeg2/
b427732 Check Number of Skip MBs
5da05c0 Error Resilience - Check on as_recent_fld[0][1]
45df45d Fix Bytes Consumed Issue
project external/skia/
e60ff4c Set a limit on the size for BMP images DO NOT MERGE
project external/sonivox/
63ff572 Fix infinite recursion
1f2842c Check chunk size
project external/tremolo/
7d1beba Always use unsigned char
project frameworks/av/
e0123f5 Modifying MetaData invalidates previous char*
309c4fb Fix memory leak in error case
77089b2 Limit ogg packet size
aaeca86 Prevent OOB write in soft_avc encoder
edc1286 Don't allow using or allocating a buffer after the first state transition
project frameworks/base/
0d099dd ZygoteInit: Remove CAP_SYS_RESOURCE
6b7bffb system_server: add CAP_SYS_PTRACE
de7cc6b Fix re-enabling alert window appop after leaving VR mode.
aa4edfe Make a11y node info parceling more robust
project frameworks/native/
2210c72 libgui: check for invalid slot in attachBuffer
d3fa90b libgui: Check slot received from IGBP in Surface
9ab1252 ui: Fix bad size check in Fence::unflatten
project libcore/
b85da16 Proper fix for rejecting ftp URL with /r/n.
d1b3b26 Test for rejection of ftp URL with /r/n in userinfo
project packages/apps/Settings/
bd1cc32 Fix phishing attack in ChooseLockGeneric
97fd637 resolve merge conflicts of 3964c51bf2 to nyc-dev
project packages/providers/DownloadProvider/
a66dd88 DO NOT MERGE Deleting downloads for removed uids on downloadprovider start
project packages/providers/MediaProvider/
67ef565 [DO NOT MERGE] Enforce user separation on external storage
project system/sepolicy/
4cfc1b9 system_server: replace sys_resource with sys_ptrace
probably answering my own question
but for previous build: NJH47B June i want to go for NJH47D for July?
y2grae said:
probably answering my own question
but for previous build: NJH47B June i want to go for NJH47D for July?
Click to expand...
Click to collapse
Unless you are on VZ, T Mobile, FI, Rogers or Deutsch Teleckom that is the one to get.
y2grae said:
probably answering my own question
but for previous build: NJH47B June i want to go for NJH47D for July?
Click to expand...
Click to collapse
Are you using any of the carriers listed in the op? If not then do D
pcriz said:
Are you using any of the carriers listed in the op? If not then do D
Click to expand...
Click to collapse
TonikJDK said:
Unless you are on VZ, T Mobile, FI, Rogers or Deutsch Teleckom that is the one to get.
Click to expand...
Click to collapse
thanks both
thought that was the way forward, but better to check and reassure
TonikJDK said:
Installed. Booted to TWRP, flashed SU 2.79 RC3. All is well, no bootloader signing needed. It did reboot twice after SU install. I did not install TWRP.
Click to expand...
Click to collapse
Hi tonikjdk,
Can you do me a favor and let me know how to install the latest update without losing root and data using TWRP? I can't find a way to accomplish this and can't find a documentation either
Your help is much appreciated.
niko26 said:
Hi tonikjdk,
Can you do me a favor and let me know how to install the latest update without losing root and data using TWRP? I can't find a way to accomplish this and can't find a documentation either
Your help is much appreciated.
Click to expand...
Click to collapse
Grab Chainfires app from the play store.....Flashfire. Grab the OTA zip from Googles website and flash it with FlashFire.
I know that will preserve root, and I'm pretty sure it will keep TWRP too.
Hello,
I am interested in trying to port sumire to Lineage 16.0, the problem is I couldn't find any guide that seemed to help me get started.
In IRC someone told me I had to:
1. Fork the cm-14.1 branch to lineage-16.0, change the required config files, and build in a 16.0 build env.
2. Wait for it to error out, fix error, repeat. Eventually once it builds, attempt booting, check logs to see why it isn't booting, fix error, repeat.
But as you can see, its not much.
I have been taking a look into the first commits for sumire on cm-14.1, https://github.com/LineageOS/androi...mmit/7be9d2e5edf6f7ea1f399febbeee9d9fbdc122e1
But I do not know if its the best way to learn.
Where could I find some guides?
Best regards
algui91 said:
Hello,
I am interested in trying to port sumire to Lineage 16.0, the problem is I couldn't find any guide that seemed to help me get started.
In IRC someone told me I had to:
1. Fork the cm-14.1 branch to lineage-16.0, change the required config files, and build in a 16.0 build env.
2. Wait for it to error out, fix error, repeat. Eventually once it builds, attempt booting, check logs to see why it isn't booting, fix error, repeat.
But as you can see, its not much.
I have been taking a look into the first commits for sumire on cm-14.1, https://github.com/LineageOS/androi...mmit/7be9d2e5edf6f7ea1f399febbeee9d9fbdc122e1
But I do not know if its the best way to learn.
Where could I find some guides?
Best regards
Click to expand...
Click to collapse
It's not really a guide, but the guy in this thread tried to port LOS 15 to the Z5, so it's probably the best place to start. He ran into issues with the camera so take a look at the last few pages too see what's going on. The people in that thread are willing to help.
https://forum.xda-developers.com/z5...erimental-lineageos-15-1-z5c-suzuran-t3894617
Devo7v said:
It's not really a guide, but the guy in this thread tried to port LOS 15 to the Z5, so it's probably the best place to start. He ran into issues with the camera so take a look at the last few pages too see what's going on. The people in that thread are willing to help.
https://forum.xda-developers.com/z5...erimental-lineageos-15-1-z5c-suzuran-t3894617
Click to expand...
Click to collapse
Thanks, although its not for the same device (Mine is sumire) it may be helpful.
I have also found this guide, it seems interesting:
https://fat-tire.github.io/porting-intro.html
algui91 said:
Thanks, although its not for the same device (Mine is sumire) it may be helpful.
I have also found this guide, it seems interesting:
https://fat-tire.github.io/porting-intro.html
Click to expand...
Click to collapse
Is there any progress at porting LOS 16?
BrazzerHead said:
Is there any progress at porting LOS 16?
Click to expand...
Click to collapse
I'm still on it. Advancing slowly as I am a newbie on this and only have a few hours/week to do it.
I will keep you updated
I have successfully come to execute brunch sumire, but I am having problems with open jdk-9:
Code:
/run/media/hkr/BackUp/out/soong/make_vars-lineage_sumire.mk:644: warning: JAVAC does not match between Make and Soong:
/run/media/hkr/BackUp/out/soong/make_vars-lineage_sumire.mk:644: warning: Make : /home/hkr/.gentoo/java-config-2/current-user-vm/bin/javac
/run/media/hkr/BackUp/out/soong/make_vars-lineage_sumire.mk:644: warning: Soong: prebuilts/jdk/jdk9/linux-x86/bin/javac
/run/media/hkr/BackUp/out/soong/make_vars-lineage_sumire.mk:1044: error: Soong variable check failed.
I have copied the prebuild version of java that comes with android into my own local version in gentoo, but still getting the same error.
Any ideas?
I have set up android_device_sony_sumire from sony-msm8994 in the included .repo/local_manifest. Setting ROOMSERVICE_BRANCHES=cm-14 as it functions as a fallback branch was suggested in the console output while i was getting familiar and this is a helpful feature worth noting.
There is an incompatibility in https://github.com/sony-msm8994/android_device_sony_sumire and kitakami-common, the lineage.dependencies file needs to be moved or it will try and download dependencies for the sumire files from the LineageOS Github (http://github.com/LineageOS). Next there are two easy defines, SND_AUDIOCODEC_ALAC and SND_AUDIOCODEC_APE to deal with before an untimely error because of a typo present in the Xperia kernel, content_interprtation_type instead of content_interpretation_type.
Code:
hardware/qcom/media-caf/msm8994/mm-video-v4l2/vidc/vdec/src/omx_vdec_msm8974.cpp:9377:60: error: no member named 'content_interprtation_type' in 'msm_vidc_s3d_frame_packing_payload'; did you mean 'content_interpretation_type'?
if (s3d_frame_packing_payload->content_interprtation_type == 1)
^~~~~~~~~~~~~~~~~~~~~~~~~~
content_interpretation_type
out/target/product/sumire/obj/KERNEL_OBJ/usr/include/media/msm_vidc.h:109:15: note: 'content_interpretation_type' declared here
unsigned int content_interpretation_type;
^
hardware/qcom/media-caf/msm8994/mm-video-v4l2/vidc/vdec/src/omx_vdec_msm8974.cpp:9379:65: error: no member named 'content_interprtation_type' in 'msm_vidc_s3d_frame_packing_payload'; did you mean 'content_interpretation_type'?
else if (s3d_frame_packing_payload->content_interprtation_type == 2)
^~~~~~~~~~~~~~~~~~~~~~~~~~
content_interpretation_type
out/target/product/sumire/obj/KERNEL_OBJ/usr/include/media/msm_vidc.h:109:15: note: 'content_interpretation_type' declared here
unsigned int content_interpretation_type;
^
hardware/qcom/media-caf/msm8994/mm-video-v4l2/vidc/vdec/src/omx_vdec_msm8974.cpp:9394:89: error: no member named 'content_interprtation_type' in 'msm_vidc_s3d_frame_packing_payload'; did you mean 'content_interpretation_type'?
s3d_frame_packing_payload->fpa_type, s3d_frame_packing_payload->content_interprtation_type, stereo_output_mode);
^~~~~~~~~~~~~~~~~~~~~~~~~~
content_interpretation_type
It compiled, but gives a black boot screen both from early boot, a kernel issue, adb seems to be communicating, I'm meddling with the boot image atm so i will know more later (Later: The updated mdss code broke for our case somewhere. I will also need to work on the local_manifest) (Later: New Manifest attached) . Last I tested the kernel a few moons ago it worked on the Z1, so issue this was a surprise... I will also import the changes from the sony-msm8994 project, who is doing a great job, i see quite a lot of work to the sdcardfs code.
threader said:
It compiled, but gives a black boot screen both from early boot, a kernel issue, adb seems to be communicating, I'm meddling with the boot image atm so i will know more later (Later: The updated mdss code broke for our case somewhere. I will also need to work on the local_manifest) (Later: New Manifest attached) . Last I tested the kernel a few moons ago it worked on the Z1, so issue this was a surprise... I will also import the changes from the sony-msm8994 project, who is doing a great job, i see quite a lot of work to the sdcardfs code.
Click to expand...
Click to collapse
How did you managed to compile it? I am finding a lot of problems, for example, in system/core/init/util.h
Code:
#include <android-base/chrono_utils.h>
#include <selinux/label.h>
were not found, so I had to comment them out, but I do not know if this its going to be the best approach...
@algui91
Im about to test what built tonight. I suspect i need to port the binder from sony-msm8994 though, it lookst tasty anyway. But does your build by any chance warn against building with a pre compiled kernel? I guess or simply some headers might have new names maybe or some feature needs to be introduced into the kernel.
The .repo/local_manifest/oss.xml contains some qcom opensource projects, to compile for 16.1 change opensource-location from revision=o-mr to p-mr. Also add https://github.com/sonyxperiadev/transpower/commits/android-8.1.0_r35, for 15.1 or probably master for 16.1, i missed that yesterday.
threader said:
@algui91
Im about to test what built tonight. I suspect i need to port the binder from sony-msm8994 though, it lookst tasty anyway. But does your build by any chance warn against building with a pre compiled kernel? I guess or simply some headers might have new names maybe or some feature needs to be introduced into the kernel.
The .repo/local_manifest/oss.xml contains some qcom opensource projects, to compile for 16.1 change opensource-location from revision=o-mr to p-mr. Also add https://github.com/sonyxperiadev/transpower/commits/android-8.1.0_r35, for 15.1 or probably master for 16.1, i missed that yesterday.
Click to expand...
Click to collapse
Hello,
Thanks for your quick reply, How did your test went? this are the only warnings I get when running brunch sumire:
Code:
build/make/core/combo/TARGET_linux-arm.mk:43: warning: cortex-a53.a57 is armv8-a.
build/make/core/combo/TARGET_linux-arm.mk:45: warning: TARGET_2ND_ARCH_VARIANT, armv7-a-neon, ignored! Use armv8-a instead.
Trying dependencies-only mode on a non-existing device tree?
I applied the required binder changes from sony-msm8994 for AOSP 8.1 and it turns out it results in a locked kernel that fails to even boot, so i'm looking that problem now. So for instant results instead of my Z1 to Z5 kernel, use https://github.com/sony-msm8994/android_kernel_sony_msm8994 in , .repo/local_manifests/LA.BR.1.3.3_rb2.14.xml , you need to comment out common-headers common-kernel, also i see i commented out my kernel, a good place to add sony-msm8994, i realize my project to update the unified kernel is riddled with mines., and we really need 15.1 and 16.1 yesterday.
I've come around to testing the whole Sony-msm8994 project that's up on Z5c, Lineage 15.1 is up with wifi, location, nfc available at least, so is the usb otg switch, not working is fingerprint and gsm services, camera.
Spotted this in logcat.
Code:
Abort message: 'CANNOT LINK EXECUTABLE "/system/bin/netmgrd": cannot locate symbol "_ZN6google8protobuf2io16CodedInputStream20ReadVarint32FallbackEPj" referenced by "/system/vendor/lib64/libcneapiclient.so"...'
TARGET_CPU_VARIANT in device/sony/kitakami-common/BoardConfigCommon.mk is set to generic, it's supposed to be TARGET_CPU_VARIANT := cortex-a53
threader said:
I've come around to testing the whole Sony-msm8994 project that's up on Z5c, Lineage 15.1 is up with wifi, location, nfc available at least, so is the usb otg switch, not working is fingerprint and gsm services, camera.
Spotted this in logcat.
Code:
Abort message: 'CANNOT LINK EXECUTABLE "/system/bin/netmgrd": cannot locate symbol "_ZN6google8protobuf2io16CodedInputStream20ReadVarint32FallbackEPj" referenced by "/system/vendor/lib64/libcneapiclient.so"...'
TARGET_CPU_VARIANT in device/sony/kitakami-common/BoardConfigCommon.mk is set to generic, it's supposed to be TARGET_CPU_VARIANT := cortex-a53
Click to expand...
Click to collapse
Have the same problem, spotted the same Fatal message, Did the change in TARGET_CPU_VARIANT solved the problem?
Best
I've got a problem with librmnetctl, vendor/qcom/opensource/dataservices, not building, netmgrd is complaining about that missing now, I'm trying the version on Xperiadev, but now I've messed up the build i built earlier and need to rebuild all of it...
threader said:
I've got a problem with librmnetctl, vendor/qcom/opensource/dataservices, not building, netmgrd is complaining about that missing now, I'm trying the version on Xperiadev, but now I've messed up the build i built earlier and need to rebuild all of it...
Click to expand...
Click to collapse
I am trying to detect where the error
Code:
Abort message: 'CANNOT LINK EXECUTABLE "/system/bin/netmgrd": cannot locate symbol "_ZN6google8protobuf2io16CodedInputStream20ReadVarint32FallbackEPj" referenced by "/system/vendor/lib64/libcneapiclient.so"...'
comes from.
I am guessing its some makefile which has a SHARED_LIBRARY link to _ZN6google8protobuf2io16CodedInputStream20ReadVarint32FallbackEPj missing, but do not know where to find it. I've searched on the LineageOS repos without luck.
algui91 said:
I am trying to detect where the error
Code:
Abort message: 'CANNOT LINK EXECUTABLE "/system/bin/netmgrd": cannot locate symbol "_ZN6google8protobuf2io16CodedInputStream20ReadVarint32FallbackEPj" referenced by "/system/vendor/lib64/libcneapiclient.so"...'
Click to expand...
Click to collapse
It seems to be called from protobuf, maybe a missing link to it somewhere?
threader said:
It seems to be called from protobuf, maybe a missing link to it somewhere?
Click to expand...
Click to collapse
It seems so, the question is where that 'Somewhere' is. . Will keep searching.
algui91 said:
It seems so, the question is where that 'Somewhere' is. . Will keep searching.
Click to expand...
Click to collapse
I see its in prebuilt compiler also.
But maybe?
Code:
external/protobuf/src/google/protobuf/io/coded_stream.cc :
Los 14.1
bool CodedInputStream::ReadVarint32Fallback(uint32* value) {
if (BufferSize() >= kMaxVarintBytes ||
// Optimization: We're also safe if the buffer is non-empty and it ends
// with a byte that would terminate a varint.
(buffer_end_ > buffer_ && !(buffer_end_[-1] & 0x80))) {
const uint8* end = ReadVarint32FromArray(buffer_, value);
if (end == NULL) return false;
buffer_ = end;
return true;
} else {
// Really slow case: we will incur the cost of an extra function call here,
// but moving this out of line reduces the size of this function, which
// improves the common case. In micro benchmarks, this is worth about 10-15%
return ReadVarint32Slow(value);
}
}
Los.15.1
int64 CodedInputStream::ReadVarint32Fallback(uint32 first_byte_or_zero) {
if (BufferSize() >= kMaxVarintBytes ||
// Optimization: We're also safe if the buffer is non-empty and it ends
// with a byte that would terminate a varint.
(buffer_end_ > buffer_ && !(buffer_end_[-1] & 0x80))) {
GOOGLE_DCHECK_NE(first_byte_or_zero, 0)
<< "Caller should provide us with *buffer_ when buffer is non-empty";
uint32 temp;
::std::pair<bool, const uint8*> p =
ReadVarint32FromArray(first_byte_or_zero, buffer_, &temp);
if (!p.first) return -1;
buffer_ = p.second;
return temp;
} else {
// Really slow case: we will incur the cost of an extra function call here,
// but moving this out of line reduces the size of this function, which
// improves the common case. In micro benchmarks, this is worth about 10-15%
uint32 temp;
return ReadVarint32Slow(&temp) ? static_cast<int64>(temp) : -1;
}
}
The function ReadVarint32Fallback is used in the following libraries :
vendor/sony/kitakami-common/proprietary/vendor/lib64/libsettings.so
vendor/sony/kitakami-common/proprietary/vendor/lib64/libcneapiclient.so
vendor/sony/kitakami-common/proprietary/vendor/lib/libsettings.so
vendor/sony/kitakami-common/proprietary/vendor/lib/libcneapiclient.so
vendor/sony/kitakami-common/proprietary/vendor/lib/mediadrm/libwvdrmengine.so
So i rolled back the functions required by the libraries in external/protobuf/src/google/protobuf/io/coded_stream.h, external/protobuf/src/google/protobuf/io/coded_stream.cc, attached a patch to get a bit farther .
I get the following error now.
Code:
520 F DEBUG : Abort message: 'CANNOT LINK EXECUTABLE "/system/bin/netmgrd": cannot locate symbol "_ZN6google8protobuf8internal14WireFormatLite10ReadStringEPNS0_2io16CodedInputStreamEPNSt3__112basic_stringIcNS6_11char_traitsIcEENS6_9allocatorIcEEEE" referenced by "/system/vendor/lib64/libcneapiclient.so"...'
I think the correct thing to do now is call ReadStringEPNS0_2io16CodedInputStreamEPNSt3__112basic_stringIcNS6_11char_traitsIcEENS6_9allocatorIcEEEE