[ROM] [4.4.2] SlimKat (jordan) [STABLE 4.0] [Weekly 3.85] [Unofficial]

[deysmacro]

That would be great! :good:

By the way, are you planning to update the stable 4.0 build? IMHO, the only major issues with that build were the camera problems (no HD video recording) and the fact that the phone automatically rebooted into recovery after a telephony layer crash, instead of rebooting normally. Since both of those issues have been solved, it would be awesome to have an updated 4.0 build that I could recommend to some of my family members who also have DEFYs.

Since when phone rebooted into recovery? No such experience on latest build. Not even once phone is rebooted by itself since last few days. Stable as it is.

Red lense defy+

 

[Proverbs2]

Since when phone rebooted into recovery? No such experience on latest build. Not even once phone is rebooted by itself since last few days. Stable as it is.

See my earlier post here, and TJKV's reply here.

I've only had the issue a couple of times, but I can confirm that the latest slimkat 4.0 build (from April 7th) does indeed reboot into recovery if you let it reboot automatically after a "telephony layer" problem.

 

[TJKV]

Okay go to the d-h.st mirror and download to test build 4.6, along with gapps 4.6. CLEAN INSTALL REQUIRED! (Wipe data and system manually from TWRP before flashing)

That would be great! :good:

By the way, are you planning to update the stable 4.0 build? IMHO, the only major issues with that build were the camera problems (no HD video recording) and the fact that the phone automatically rebooted into recovery after a telephony layer crash, instead of rebooting normally. Since both of those issues have been solved, it would be awesome to have an updated 4.0 build that I could recommend to some of my family members who also have DEFYs.

Nope I already merged the newer updates. In any case the word stable, apart from not making much sense for the Defy, also doesn't make sense for the other official slim devices because no matter what slim features are always stable. So even the regular 'Weekly Builds' are pretty much as stable as 'Stable Builds'. The slim guys are generally careful about their code and test everything well.

 

[Proverbs2]

@TJKV, thanks for uploading the 4.6 build! I've downloaded it already, and I'm eager to test it. (Hopefully I'll have time later today.)

You mentioned that you had built 4.2 and 4.4, but were not happy with them. In those builds, did you encounter any new bugs or issues that we should be looking for when we test 4.6, besides the usual known bugs?

 

[DroidBot]

Please go ahead and upload with experimental tag.

That would be great! :good:

By the way, are you planning to update the stable 4.0 build? IMHO, the only major issues with that build were the camera problems (no HD video recording) and the fact that the phone automatically rebooted into recovery after a telephony layer crash, instead of rebooting normally. Since both of those issues have been solved, it would be awesome to have an updated 4.0 build that I could recommend to some of my family members who also have DEFYs.

I didn't face any telephony problem yet in any build. I had just one problem and that was, if we reboot phone, it wasn't getting on. And this problem was eliminated using GravityBox advance reboot option (for me atleast).

And @TJKV, please uplaod your latest build, we will try our best to give you usefull feedbacks. We can understand that you don't have that much time. So, just go ahead and upload with caution text i.e experimental build.

Always thankfull of yours for your great support and awesome work. :good:

 

[TJKV]

@TJKV, thanks for uploading the 4.6 build! I've downloaded it already, and I'm eager to test it. (Hopefully I'll have time later today.)

You mentioned that you had built 4.2 and 4.4, but were not happy with them. In those builds, did you encounter any new bugs or issues that we should be looking for when we test 4.6, besides the usual known bugs?

No nothing to look for particularly, I just wasn't happy with the state of the commits in the jordan-common branch. Seemed like there were many bug reports in the CM11 thread at the time, camera and all.

 

[DroidBot]

Installation failed

Okay go to the d-h.st mirror and download to test build 4.6, along with gapps 4.6. CLEAN INSTALL REQUIRED! (Wipe data and system manually from TWRP before flashing)

Oops...Latest build is not getting installed...I have rebooted the into recovery, wiped all /system, /Data, /Cache, /Dalvik...Flashed safe wipe and tried to install the build, but its getting failed. Its giving errors:

set_metadata: some changes failed
E: Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/Slim-mb526-4.4.2.build

Please help.....

 

[mielletseed]

Oops...Latest build is not getting installed...I have rebooted the into recovery, wiped all /system, /Data, /Cache, /Dalvik...Flashed safe wipe and tried to install the build, but its getting failed. Its giving errors:

set_metadata: some changes failed
E: Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/Slim-mb526-4.4.2.build

Please help.....

Got the same error - decided to ignore it since it was after installing the files. Installed gapps afterwards and rebooted - all is fine but the zip seems to be corrupted when u got this error too.

 

[DroidBot]

May be......

Got the same error - decided to ignore it since it was after installing the files. Installed gapps afterwards and rebooted - all is fine but the zip seems to be corrupted when u got this error too.

Oh yes...May be the zip is corrupted. I am installing 06-04 build now...
@TJKV: please look into this issue, if you have time.

 

[Stoku]

The 4.0 build looks very stable and I want to use it for some more days, so I have a question - will replacing DefyParts.apk from build 4.6 fix reboot to recovery issue?

No nothing to look for particularly, I just wasn't happy with the state of the commits in the jordan-common branch. Seemed like there were many bug reports in the CM11 thread at the time, camera and all.

Yay, that's why most of Slim builds are pretty ok for daily use

 

[Hasuris]

The 4.0 build looks very stable and I want to use it for some more days, so I have a question - will replacing DefyParts.apk from build 4.6 fix reboot to recovery issue?


Yay, that's why most of Slim builds are pretty ok for daily use

I think the messed up batteryreadings are more severe. A couple of pages back, TKJV posted a solution. I don't see the need anymore to update my phone every week like I used to. These builds are fairly stable and complete in a sense, that I don't miss any important features. I think an update once a month or so to get newest improvements by Quarx and Blechd0se is sufficient.

I don't see, how the defy could "grow" any more. It's as fast as one could hope with Kitkat 4.4. I don't know what kernel 3.0 would bring to the table, if it ever reaches stable/useable. And there is F2FS, that will help a lot but I guess it's a lot of work/maybe not possible, just like 3.0.

 

[TJKV]

Got the same error - decided to ignore it since it was after installing the files. Installed gapps afterwards and rebooted - all is fine but the zip seems to be corrupted when u got this error too.

You mean despite that error message the build wasinstalled file and the ROM booted?

The 4.0 build looks very stable and I want to use it for some more days, so I have a question - will replacing DefyParts.apk from build 4.6 fix reboot to recovery issue?

Yes you can use the defyparts app I guess.

 

[TJKV]

People who have downloaded the 4.6 build, try this fix:

Open the zip with 7zip or similar, go to /META-INF/com/google/android and open the updater-script with a text editor like Notepad++.

Line 179:

package_extract_file("system/etc/media_profiles_mb526.xml", "system/etc/media_profiles.xml");

change it to:

package_extract_file("system/etc/media_profiles_mb526.xml", "/system/etc/media_profiles.xml");

Basically add a forward slash before the SECOND occurrence of the word 'system'.

 

[Casper1982]

"failed"

delet

 

[DroidBot]

Have you tried the fix mentioned by TJKV??

delet

Have you tried the fix mentioned by TJKV??

 

[Sabre-F100]

Yesterday I remove gallery from hwa control. After that I make several tests in different day's times and every working well.
But yesterday I reinstall the ROM too, so I don't sure what action made the difference.
Today I will mark gallery in hwa again and try to confirm what happen

untick gallery from HWA

still no luck

W/MemoryBase( 1254): Using temporary compatibility workaround for usage of MemoryBase private API. Please fix your application! But...you can try... No! It's Moto lib... okay:(
E/LibSOCJordanCamera( 1254): MG: Returning focus to infinity!
D/LibSOCJordanCamera( 1254): -captureThread
V/CAM_PhotoModule( 3130): mShutterToPostViewCallbackTime = 750ms
V/CAM_PhotoModule( 3130): JpegPictureCallback: Received = 1Burst count = 1
V/CAM_PhotoModule( 3130): mPictureDisplayedToJpegCallbackTime = 17ms
V/CAM_PhotoModule( 3130): needRestartPreview=true
D/CameraHAL( 1254): get_camera_info: id:0 faceing:0 orientation: 90
V/CAM_PhotoModule( 3130): old picture_size = 2592 x 1936
V/CAM_PhotoModule( 3130): new picture_size = 2592 x 1936
V/CAM_PhotoModule( 3130): Preview size is 640x480
V/CAM_PhotoModule( 3130): Color effect value =none
V/CAM_PhotoModule( 3130): Face Recognition value = off
V/CAM_PhotoModule( 3130): AE Bracketing value =Off
V/CAM_PhotoModule( 3130): autoExposure value =frame-average
V/CAM_PhotoModule( 3130): antiBanding value =auto
D/LibSOCJordanCamera( 1254): +setParameters
I/LibSOCJordanCamera( 1254): Extract changes completed, 0 total changes
V/CAM_PhotoModule( 3130): startPreview
D/LibSOCJordanCamera( 1254): -setParameters
D/LibSOCJordanCamera( 1254): +setOverlay
D/LibSOCJordanCamera( 1254): +deinitPvOverlay
D/LibSOCJordanCamera( 1254): -deinitPvOverlay
D/CameraHAL( 1254): camera_set_preview_window: OK window is 0x2a01aa60
D/CameraHAL( 1254): camera_set_preview_window: OK on loading gralloc HAL
D/LibSOCJordanCamera( 1254): +getParameters
D/LibSOCJordanCamera( 1254): -getParameters
D/CameraHAL( 1254): camera_set_preview_window: preview format yuv420sp
I/CameraHAL( 1254): camera_set_preview_window: Using overlay for device 0x2a018c18
D/Overlay ( 1254): Overlay: Init overlay
D/Overlay ( 1254): Overlay: Init overlay complete
D/LibSOCJordanCamera( 1254): +setOverlay
D/LibSOCJordanCamera( 1254): +deinitPvOverlay
D/LibSOCJordanCamera( 1254): -deinitPvOverlay
D/LibSOCJordanCamera( 1254): -setOverlay
D/LibSOCJordanCamera( 1254): +startPreview
D/CameraStorage( 3130): External storage state=mounted
V/CAM_PhotoModule( 3130): mJpegCallbackFinishTime = 67ms
E/LibSOCJordanCamera( 1254): VIDIOC_STREAMOFF already issued
D/LibSOCJordanCamera( 1254): +initPvOverlay
D/Overlay ( 1254): getBufferAddress: 0
W/MemoryBase( 1254): Using temporary compatibility workaround for usage of MemoryBase private API. Please fix your application! But...you can try... No! It's Moto lib... okay:(
D/Overlay ( 1254): getBufferAddress: 1
W/MemoryBase( 1254): Using temporary compatibility workaround for usage of MemoryBase private API. Please fix your application! But...you can try... No! It's Moto lib... okay:(
D/Overlay ( 1254): getBufferAddress: 2
W/MemoryBase( 1254): Using temporary compatibility workaround for usage of MemoryBase private API. Please fix your application! But...you can try... No! It's Moto lib... okay:(
D/Overlay ( 1254): getBufferAddress: 3
W/MemoryBase( 1254): Using temporary compatibility workaround for usage of MemoryBase private API. Please fix your application! But...you can try... No! It's Moto lib... okay:(
D/Overlay ( 1254): getBufferAddress: 4
W/MemoryBase( 1254): Using temporary compatibility workaround for usage of MemoryBase private API. Please fix your application! But...you can try... No! It's Moto lib... okay:(
D/Overlay ( 1254): getBufferAddress: 5
W/MemoryBase( 1254): Using temporary compatibility workaround for usage of MemoryBase private API. Please fix your application! But...you can try... No! It's Moto lib... okay:(
D/Overlay ( 1254): getBufferAddress: 6
W/MemoryBase( 1254): Using temporary compatibility workaround for usage of MemoryBase private API. Please fix your application! But...you can try... No! It's Moto lib... okay:(
D/Overlay ( 1254): getBufferAddress: 7
W/MemoryBase( 1254): Using temporary compatibility workaround for usage of MemoryBase private API. Please fix your application! But...you can try... No! It's Moto lib... okay:(
D/LibSOCJordanCamera( 1254): -initPvOverlay
D/LibSOCJordanCamera( 1254): -startPreview
D/LibSOCJordanCamera( 1254): +setParameters
I/LibSOCJordanCamera( 1254): Extract changes completed, 0 total changes
D/LibSOCJordanCamera( 1254): -setParameters
I/LibSOCJordanCamera( 1254): Preview is running.
W/CursorWrapperInner( 3130): Cursor finalized without prior close()
D/skia    ( 3130): --- SkImageDecoder::Factory returned null
D/skia    ( 3130): --- SkImageDecoder::Factory returned null
I/Choreographer( 3130): Skipped 37 frames!  The application may be doing too much work on its main thread.
E/CAM_LocalData( 3130): Failed decoding bitmap for file:/storage/sdcard0/DCIM/Camera/IMG_20140422_101245.jpg
I/LibSOCJordanCamera( 1254): Preview is running.
D/skia    ( 3130): --- SkImageDecoder::Factory returned null
D/skia    ( 3130): --- SkImageDecoder::Factory returned null
E/CAM_LocalData( 3130): Failed decoding bitmap for file:/storage/sdcard0/DCIM/Camera/IMG_20140422_101236.jpg
I/LibSOCJordanCamera( 1254): Preview is running.

scrolling on gallery, and reboots:crying:

 

[rahul9871]

I have tried with this fix, but result is same,,, failed to install 4.6 in TWRP

Sent from my MB526 using XDA Premium 4 mobile app

 

[mielletseed]

You mean despite that error message the build wasinstalled file and the ROM booted?

Yes
But now I will correct the zip and install again, don't know what I'm missing with the media profiles ...

 

[mmbytes]

No WiFi drops.
No call drops.
Hardly any issues, except for the fact that screen takes a few seconds to wake up when u receive a call.

Interesting, I have flashed Slim-mb526-4.4.2.build.4 and I can't get WiFi to work.
It lists the WiFi networks, but I'm not able to connect to them. It always tries but can't finish the handshake.
Tried 2 different hotspots.

Any ideas?

Thanks

 

[qx876]

*solved*

google now is not available in your country?

did an update to 0407 coming from quarx 4.22
banks minimal gapps

really like it sofar, but I cant seem to get google now working again.

I deleted search, tried a few versions, no workie.

any tips, cheers and thx