[ROM][7.1.x][NOUGAT][BETA][CyanogenMod 14.1][WIP][UNOFFICIAL]

Search This thread

pesci2k

Senior Member
Feb 15, 2011
141
1,354
Trieste
Same problem here… Looks like there is an error in the code. You could try to revert the last commit: "git revert 3592748d4d08a382bfed51d9ab009060d89c2fb9"

Yes you are right. After repo sync use these code

Code:
cd device/samsung/i9300
git revert 3592748d4d08a382bfed51d9ab009060d89c2fb9
croot

You have also to cherry pick these two patches (one fix 100% CPU bug and the other fix current cm build that is broken)

Code:
repopick 165367 164162


---------- Post added at 04:22 PM ---------- Previous post was at 04:20 PM ----------


Code:
repopick 164162
 

poulette73

Member
Feb 12, 2012
29
31
Thanks for the suggestion. ;)

  • I have replaced this file camera.smdk4x12.so in /system/lib/hw, but this fix for launch the stock camera still doesn't work.
  • Same error with Footej Camera and Open Camera (downloaded & installed too). No problem with original Android 7.0 Video Player which works well.
  • I tried Mediaserver Killer without success.
  • I've flashed in recovery this file JustArchi_Camera_Fix_Everything.zip but no luck.
I'll keep looking for a solution, and I will post it when I have found. :)
 

pesci2k

Senior Member
Feb 15, 2011
141
1,354
Trieste
Thanks for the suggestion. ;)

  • I have replaced this file camera.smdk4x12.so in /system/lib/hw, but this fix for launch the stock camera still doesn't work.
  • Same error with Footej Camera and Open Camera (downloaded & installed too). No problem with original Android 7.0 Video Player which works well.
  • I tried Mediaserver Killer without success.
  • I've flashed in recovery this file JustArchi_Camera_Fix_Everything.zip but no luck.
I'll keep looking for a solution, and I will post it when I have found. :)

The camera isn't working because of recent Nougat changes. The problem is known and affects many devices.
Many developers are currently working on it. We have just to wait until it is fixed.
 

leleobhz

Senior Member
Mar 8, 2009
289
71
Campinas
BUG: AdoptedStorage does not work, with the following error (After a long wait and a lot of CPU):

10-16 18:17:08.258 2932 2945 I ActivityManager: START u0 {cmp=com.android.settings/.deviceinfo.StorageWizardFormatProgress (has extras)} from uid 1000 on display 0
10-16 18:17:08.721 2932 4850 D VoldConnector: SND -> {8 volume partition disk:179_48 private}
10-16 18:17:08.746 2932 3062 D VoldConnector: RCV <- {651 private:179_50 7}
10-16 18:17:08.749 2932 3062 D VoldConnector: RCV <- {659 private:179_50}
10-16 18:17:08.770 3128 3128 D StorageNotification: Notifying about private volume: VolumeInfo{private:179_50}:
10-16 18:17:08.770 3128 3128 D StorageNotification: type=PRIVATE diskId=disk:179_48
10-16 18:17:08.770 3128 3128 D StorageNotification: partGuid=DBD22285-ED38-9F4C-6CD2-85D5930F0189 mountFlags=0 mountUserId=-1
10-16 18:17:08.770 3128 3128 D StorageNotification: state=REMOVED
10-16 18:17:08.770 3128 3128 D StorageNotification: fsType=null fsUuid=null fsLabel=
10-16 18:17:08.770 3128 3128 D StorageNotification: path=null internalPath=null
10-16 18:17:08.792 2033 2091 V vold : /system/bin/sgdisk
10-16 18:17:08.792 2033 2091 V vold : --zap-all
10-16 18:17:08.792 2033 2091 V vold : /dev/block/vold/disk:179_48
10-16 18:17:08.896 3420 3420 I Choreographer: Skipped 31 frames! The application may be doing too much work on its main thread.
10-16 18:17:09.133 2932 2974 I ActivityManager: Displayed com.android.settings/.deviceinfo.StorageWizardFormatProgress: +818ms
10-16 18:17:09.516 2932 4910 I WindowManager: Destroying surface Surface(name=com.android.settings/com.android.settings.deviceinfo.StorageWizardFormatConfirm) called by com.android.server.wm.WindowStateAnimator.destroySurface:2014 com.android.server.wm.WindowStateAnimator.destroySurfaceLocked:881 com.android.server.wm.WindowState.removeLocked:1449 com.android.server.wm.WindowManagerService.removeWindowInnerLocked:2485 com.android.server.wm.WindowManagerService.removeWindowLocked:2443 com.android.server.wm.WindowManagerService.removeWindowLocked:2312 com.android.server.wm.WindowManagerService.removeWindow:2307 com.android.server.wm.Session.remove:193
10-16 18:17:09.981 2033 2091 I sgdisk : GPT data structures destroyed! You may now partition the disk using fdisk or
10-16 18:17:09.982 2033 2091 I sgdisk : other utilities.
10-16 18:17:10.017 2033 2091 D vold : Persisted key for GUID 454e3aa96f606a891aa5c093ee6576a0
10-16 18:17:10.017 2033 2091 V vold : /system/bin/sgdisk
10-16 18:17:10.017 2033 2091 V vold : --new=0:0:+16M
10-16 18:17:10.017 2033 2091 V vold : --typecode=0:19A710A2-B3CA-11E4-B026-10604B889DCF
10-16 18:17:10.017 2033 2091 V vold : --change-name=0:android_meta
10-16 18:17:10.017 2033 2091 V vold : --new=0:0:-0
10-16 18:17:10.017 2033 2091 V vold : --typecode=0:193D1EA4-B3CA-11E4-B075-10604B889DCF
10-16 18:17:10.018 2033 2091 V vold : --partition-guid=0:454e3aa96f606a891aa5c093ee6576a0
10-16 18:17:10.018 2033 2091 V vold : --change-name=0:android_expand
10-16 18:17:10.018 2033 2091 V vold : /dev/block/vold/disk:179_48
10-16 18:17:10.061 2033 2091 I sgdisk : Creating new GPT entries.
10-16 18:17:10.073 2033 2091 I sgdisk : Setting name!
10-16 18:17:10.074 2033 2091 I sgdisk : partNum is 0
10-16 18:17:10.074 2033 2091 I sgdisk : REALLY setting name!
10-16 18:17:10.076 2033 2091 I sgdisk : Setting name!
10-16 18:17:10.076 2033 2091 I sgdisk : partNum is 1
10-16 18:17:10.076 2033 2091 I sgdisk : REALLY setting name!
10-16 18:17:11.196 2033 2091 I sgdisk : The operation has completed successfully.
10-16 18:17:11.197 2932 3062 D VoldConnector: RCV <- {200 8 Command succeeded}
10-16 18:17:11.200 2033 2042 D vold : Disk at 179:48 changed
10-16 18:17:11.202 2033 2042 V vold : /system/bin/sgdisk
10-16 18:17:11.203 2033 2042 V vold : --android-dump
10-16 18:17:11.203 2033 2042 V vold : /dev/block/vold/disk:179_48
10-16 18:17:11.203 2932 3062 D VoldConnector: RCV <- {641 disk:179_48 16089350144}
10-16 18:17:11.207 2932 3062 D VoldConnector: RCV <- {642 disk:179_48 Transcend}
10-16 18:17:11.209 2932 3062 D VoldConnector: RCV <- {644 disk:179_48 /sys//devices/platform/s3c-sdhci.2/mmc_host/mmc1/mmc1:59b4/block/mmcblk1}
10-16 18:17:11.209 2932 4850 E VoldConnector: NDC Command {8 volume partition disk:179_48 private} took too long (2479ms)
10-16 18:17:11.281 2033 2042 V vold : DISK gpt B16E2131-30D1-4E16-86F2-DCDDF5A4B9EC
10-16 18:17:11.281 2033 2042 V vold :
10-16 18:17:11.282 2033 2042 V vold : PART 1 19A710A2-B3CA-11E4-B026-10604B889DCF 4A3273AA-B187-4B41-B578-1DC401EEBF46 android_meta
10-16 18:17:11.282 2033 2042 V vold :
10-16 18:17:11.282 2033 2042 V vold : PART 2 193D1EA4-B3CA-11E4-B075-10604B889DCF 454E3AA9-6F60-6A89-1AA5-C093EE6576A0 android_expand
10-16 18:17:11.282 2033 2042 V vold :
10-16 18:17:11.284 2033 2042 D vold : Found key for GUID 454e3aa96f606a891aa5c093ee6576a0
10-16 18:17:11.284 2033 2042 D vold : Device just partitioned; silently formatting
10-16 18:17:11.288 2033 2042 E Cryptfs : Cannot remove dm-crypt device
10-16 18:17:11.294 2033 2042 I Cryptfs : Enabling support for allow_discards in dmcrypt.
10-16 18:17:11.294 2033 2042 I Cryptfs : target_type = crypt
10-16 18:17:11.294 2033 2042 I Cryptfs : real_blk_name = /dev/block/vold/private:179_50, extra_params = 1 allow_discards
10-16 18:17:11.297 2033 2042 D vold : Resolved auto to f2fs
10-16 18:17:11.297 2033 2042 V vold : /system/bin/mkfs.f2fs
10-16 18:17:11.297 2033 2042 V vold : /dev/block/dm-0
10-16 18:17:11.329 2033 2042 I mkfs.f2fs:
10-16 18:17:11.329 2033 2042 I mkfs.f2fs: F2FS-tools: mkfs.f2fs Ver: 1.6.1 (2016-03-22) [modified by Motorola to reserve space]
10-16 18:17:11.329 2033 2042 I mkfs.f2fs:
10-16 18:17:11.329 2033 2042 I mkfs.f2fs: Info: Debug level = 0
10-16 18:17:11.329 2033 2042 I mkfs.f2fs: Info: Label =
10-16 18:17:11.330 2033 2042 I mkfs.f2fs: Info: Segments per section = 1
10-16 18:17:11.330 2033 2042 I mkfs.f2fs: Info: Sections per zone = 1
10-16 18:17:11.330 2033 2042 I mkfs.f2fs: Info: Trim is enabled
10-16 18:17:11.331 2033 2042 I mkfs.f2fs: Info: sector size = 512
10-16 18:17:11.331 2033 2042 I mkfs.f2fs: Info: total sectors = 31389663 (15326 MB)
10-16 18:17:11.331 2033 2042 I mkfs.f2fs: Info: zone aligned segment0 blkaddr: 512
10-16 18:17:11.332 2033 2042 I mkfs.f2fs: Info: format version with
10-16 18:17:11.332 2033 2042 I mkfs.f2fs: "Linux version 3.0.101-CM (Boeffla-Kernel-6.0-alpha2-CM14.0-i9300-UNOFFICIAL-20161004@mm20) (gcc version 4.9.3 20150311 (prerelease) (crosstool-NG 1.20.0) ) #1 SMP PREEMPT Tue Oct 4 17:47:14 CEST 2016"
10-16 18:17:11.332 2033 2042 I mkfs.f2fs: Info: Discarding device: 3196201224 sectors

(A lot of time after this):

10-16 18:20:11.251 3420 3420 E StorageSettings: Failed to partition
10-16 18:20:11.251 3420 3420 E StorageSettings: java.lang.IllegalStateException: java.util.concurrent.TimeoutException: Thread Binder:2932_D gave up waiting for partitionPrivate after 180000ms
10-16 18:20:11.251 3420 3420 E StorageSettings: at android.os.Parcel.readException(Parcel.java:1691)
10-16 18:20:11.251 3420 3420 E StorageSettings: at android.os.Parcel.readException(Parcel.java:1636)
10-16 18:20:11.251 3420 3420 E StorageSettings: at android.os.storage.IMountService$Stub$Proxy.partitionPrivate(IMountService.java:1085)
10-16 18:20:11.251 3420 3420 E StorageSettings: at android.os.storage.StorageManager.partitionPrivate(StorageManager.java:725)
10-16 18:20:11.251 3420 3420 E StorageSettings: at com.android.settings.deviceinfo.StorageWizardFormatProgress$PartitionTask.doInBackground(StorageWizardFormatProgress.java:98)
10-16 18:20:11.251 3420 3420 E StorageSettings: at com.android.settings.deviceinfo.StorageWizardFormatProgress$PartitionTask.doInBackground(StorageWizardFormatProgress.java:93)
10-16 18:20:11.251 3420 3420 E StorageSettings: at android.os.AsyncTask$2.call(AsyncTask.java:304)
10-16 18:20:11.251 3420 3420 E StorageSettings: at java.util.concurrent.FutureTask.run(FutureTask.java:237)
10-16 18:20:11.251 3420 3420 E StorageSettings: at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:243)
10-16 18:20:11.251 3420 3420 E StorageSettings: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
10-16 18:20:11.251 3420 3420 E StorageSettings: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
10-16 18:20:11.251 3420 3420 E StorageSettings: at java.lang.Thread.run(Thread.java:761)
 

gameskill123

New member
Dec 11, 2015
3
1
The newest pesci2k ROM is working pretty good, i like the performance and the battery runtime, but there is one annoying bug,
if i disable my wifi, and turn it back on, i am not able to connect to a network anymore until i restart my phone.


After all the ROM boots very fast, and im using it as my daily driver for two days now and im pretty happy that it is working just so good until now. Keep going :good:
 
  • Like
Reactions: Scorpionea

Tech-Ina

Member
Apr 29, 2015
45
14
Just leaving this here: I downloaded the leaked Pixel Launcher and it is a joy to use. Trebuchet on this ROM, as you probably know, has a mind of its own regarding the number columns in the app drawer plus the icons are not properly arranged. So if you haven't installed a third party launcher yet, be sure to try it.

Also, just an FYI, do not turn on SELinux strict in the boeffla config app. If you do so, the app will say that the kernel is not supported, until you reboot.

Good luck and thank you to all the devs working on the ROM, and great evening to you all!
 

JohnSmit268

Senior Member
Can somebody put this into their build.prop and see if camera works + video recording?

media.stagefright.legacyencoder=true

and if that doesn't work try using the camera.smdk4x12.so and this also.
I had a working camera (just tried picturing). And now after adding this line I took a video in footej camera and it worked as it should. Dunno if it was ok or this line fixed it cause I never use camcorder on my phone.
 

poulette73

Member
Feb 12, 2012
29
31
Can somebody put this into their build.prop and see if camera works + video recording?

media.stagefright.legacyencoder=true

and if that doesn't work try using the camera.smdk4x12.so and this also.
I've tried adding this line into my build.prop and no effect :
- camera doesn't work.
- trying with camera.smdk4x12.so too without success.
- same issue with Footej.
I'm still ready to beta test and try different solutions. :good:
 

SILELICA

Member
Jun 28, 2013
33
10
I've tried adding this line into my build.prop and no effect :
- camera doesn't work.
- trying with camera.smdk4x12.so too without success.
- same issue with Footej.
I'm still ready to beta test and try different solutions. :good:

JustArchi camera zip. anysing its working in thish room, buy to zip.

Sent from my GT-I9300 using XDA Free mobile app
 

achkap

Senior Member
Oct 26, 2009
620
80
Last edited:

FaserF

Senior Member
Oct 23, 2014
1,311
2,156
Munich
www.youtube.com
[Flashable] Fix Camera+WIFI

I have made a flashable zip to fix the Camera issue on CM14 for i9300 made by @Hellsingoff and it will install the new Google camera with working video recording and it will patch the WIFI fix for Murata made by @MaxMustermann2.0

Download removed due to incompatibility

Credits:
- @Hellsingoff for his Camera Fix
- @MaxMustermann2.0 for his WIFI Fix

More Details about the ZIP Files and what they do:
I have made this as I dont want to do it again with every new clean flash.
So now you can flash the Rom+Gapps+This fix in one row.
This zip file contains the WIFI Fix for MURATA ONLY
It will replace the camera.smdk4x12.so file on your system and it will install the newest working google camera and remove the stock camera.

++Waiting for feedback :) ++
 
Last edited:

JohnSmit268

Senior Member
Can somebody put this into their build.prop and see if camera works + video recording?

media.stagefright.legacyencoder=true

and if that doesn't work try using the camera.smdk4x12.so and this also.
Confirmed. I clean flashed once and the footej camera couldn't record any video. After adding this line to build.prop I can record videos on high resolutions with no problem. I didn't replace the camera.smdk4x12.so and it is the one included in the rom. Thanks for this fix!!
Edit: Back camera 1080p video recording have lags.
 
Last edited:
  • Like
Reactions: SteStanich

sunny1234590

Senior Member
Feb 15, 2014
1,326
707
Greater Noida
Good to know that we are getting closed to getting most of the things working. The way it is right now, I believe, camera issues will also get solved pretty quickly too.

Also, tell me guys which build has the CPU fix included ?

Sent from my GT-I9300 using XDA-Developers mobile app
 

JohnSmit268

Senior Member

poulette73

Member
Feb 12, 2012
29
31
I have made a flashable zip to fix the Camera issue on CM14 for i9300 made by @Hellsingoff and it will install the new Google camera with working video recording and it will patch the WIFI fix for Murata made by @MaxMustermann2.0

**Download**

Credits:
- @Hellsingoff for his Camera Fix
- @MaxMustermann2.0 for his WIFI Fix

More Details about the ZIP Files and what they do:
I have made this as I dont want to do it again with every new clean flash.
So now you can flash the Rom+Gapps+This fix in one row.
This zip file contains the WIFI Fix for MURATA ONLY
It will replace the camera.smdk4x12.so file on your system and it will install the newest working google camera and remove the stock camera.

++Waiting for feedback :) ++
I'm sorry... in my case this fix does not work either:(
But thank you a lot for the job and time spent ! :good:

This the error in TWRP :

Checking for MD5 file...
Skipping MD5 check: no MD5 file found
E:Error executing updater binary in zip '/external_sd/CM14/FixCamera+WIFI-CM14-i9300.zip'
Error flashing zip '/external_sd/CM14/FixCamera+WIFI-CM14-i9300.zip'
Updating partition details...
...done

I've tried 2 times, with 2 archives zip from different download locations (mirror) and same error.

BTW in my case, my wifi works with SEMCOSH.

I continue to believe we will get to operate this camera, one day. :D ;)
 

schwarzerfleck

Senior Member
Aug 20, 2015
287
141
Berlin
OnePlus 8T
OnePlus 9 Pro
I have made a flashable zip to fix the Camera issue on CM14 for i9300
[...]
++Waiting for feedback :) ++

Can't even get past flashing. I have manually flashed the WiFi fix (murata) before, replaced the smdx...something manually etc. Just had not installed Google camera. Is it related to that?
I am on 10092016, using Boeffla kernel


Sent from my GT-I9300 using XDA Labs
 

Attachments

  • Screenshot_2016-10-17-08-03-07.png
    Screenshot_2016-10-17-08-03-07.png
    70.2 KB · Views: 968

Pianetino75

New member
May 30, 2015
2
0
Can't even get past flashing. I have manually flashed the WiFi fix (murata) before, replaced the smdx...something manually etc. Just had not installed Google camera. Is it related to that?
I am on 10092016, using Boeffla kernel


Sent from my GT-I9300 using XDA Labs

I've had that error some day ago with another zip. Downgrading twrp to 2.8.6.1 solved for me.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 110
    gXAqCye.png

    CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.​

    Be careful, this is still a WIP, dont think that all is working FINE!
    There is, and will be still alot to do, and pls report back here!
    Also pls make a Backup befor you flash this!

    Whats working:


    Whats not working:




    Sources:
    Kernel Tree

    Credits:
    Whole CM Team
    and of course: to all those who have contributed to cm and for there help!​

    XDA:DevDB Information
    CyanogenMod 141., ROM for the Samsung Galaxy S III I9300

    Contributors
    Taker18, flo071
    Source Code: https://github.com/CyanogenMod

    ROM OS Version: 7.x Nougat
    ROM Kernel: Linux 3.0.x
    Based On: CyanogenMod 14

    Version Information
    Status: Testing

    Created 2016-09-13
    Last Updated 2016-11-24
    39
    Any changes on ril? If ril works I'm gonna install CM14 build as my daily driver.

    RIL "works". There's a pretty big bug though: when the screen goes off rild starts eating CPU and the phone becomes unresponsive. (actual RIL functionality should be working ok though). Wifi tethering is also broken (for now, hopefully won't be too hard to fix), along with camcorder (CM problem).

    So... don't expect anything from me until that's fixed. I'm going to be pretty busy over the next ~month, but I'll get to it eventually.

    In the meantime, if anyone wants to roll their own, here's a quick'n'dirty guide, including all the additional patches you need on top of CM (you should already have all the tools to build android installed):
    Code:
    mkdir ~/android/system
    cd ~/android/system
    repo init -u git://github.com/CyanogenMod/android.git -b staging/cm-14.0
    mkdir -p .repo/local_manifests
    curl https://gist.githubusercontent.com/fourkbomb/2cde209bb69c29853085e8af5d68bfa5/raw/cdd078618ef96cf0586fc84f02e4ec8d663b2369/i9300.xml > .repo/local_manifests/roomservice.xml
    reposync
    source build/envsetup.sh
    repopick $(cat device/samsung/i9300/PICKS | grep -v '#')
    lunch cm_i9300-userdebug
    mka bacon
    38
    I have uploaded Build 20161018 on AndroidFileHost.

    Changelog:
    - RIL works again
    - Updated CM14 sources
    36
    Build 20161022 Download: AndroidFileHost

    Changelog:
    - Fixed GPS issue
    - Fixed Google Play Services FC during setup wizard
    - Kernel is more stable and the device doesn't reboot when the screen goes off
    - Long press app switch button to open menu
    - Updated CM14 sources

    The last main issue that needs to be fixed is the camera.
    The app permission dialog bug seems related to OpenGApps. I have read that other gapps don't have this problem.

    All device fixes are from forkbomb444.
    31
    Good new everyone!

    CyanogenMod 14.1 (based on Android 7.1) compiles and the build seems stable and has the same working features as in cm14.0.
    I will clean up the build and post it later, maybe in a new thread.