|
|
Post by No1VIPER on Nov 26, 2016 16:29:25 GMT
Latest Build: 11Dec16CYou have to flash with sptool, if you want to use it to dirty flash over stock then **UNTICK** the userdata in sptool. Don't flash recovery. Go straight into twrp recovery if you have it installed already. If not flash it before rebooting. Install open gapps Install supersu (if using it before) The other instructions are there if you let it boot without flashing gapps. Lots of apps will crash then after you install opengapps. Then login to play store. Don't factory reset It isn't a huge amount you'll need to remove and reinstall afterwards EIS is available in stock camera app for video, video hdr and EIS is available in freedcam dng using imx230_QC profile gives correct colours in freedcam too. |
|
|
|
Post by ricey155 on Nov 28, 2016 9:06:01 GMT
This ROM sounds interesting, hope to try this a little further down the development :-)
|
|
|
|
Post by bl3nto on Dec 2, 2016 6:56:12 GMT
Is there any link where we can monitor the progress? I would like to try this, but since Apollo is now my daily driver, I would like it to see how the progress is going...
|
|
|
|
Post by chucker on Dec 2, 2016 7:34:40 GMT
Just attempted using SPtool to flash FARDS Custom Stock ROM. Message issued 'The load scatter file is invalid' error#8417.
|
|
|
|
Post by No1VIPER on Dec 2, 2016 9:28:39 GMT
|
|
|
|
Post by fards on Dec 4, 2016 13:22:32 GMT
Just attempted using SPtool to flash FARDS Custom Stock ROM. Message issued 'The load scatter file is invalid' error#8417. Check if there's a newer version of SP flashtool available? I had the same issue with the linux version, then realised there was a much newer one available. |
|
|
|
Post by No1VIPER on Dec 4, 2016 20:55:51 GMT
Download: Build 11 You have to flash with sptool, if you want to use it to dirty flash over stock then **UNTICK** the userdata in sptool. Changelog: reduced google play stuff. the core is still there, but there's no autosetup. Install arm64 opengapps (ignore the warning about the files already there and go for it if you want it to autostart after a factory reset) some other tweaks, can't remember them all as I've spent today swearing at things that won't build but should be. |
|
|
|
Post by ricey155 on Dec 4, 2016 22:04:08 GMT
Not for me cwm and twrp so easy and hassle free, had enough of USB burning tool and TV boxes with windows10 #MakeItEasy
|
|
|
|
Post by fards on Dec 5, 2016 0:43:49 GMT
Not for me cwm and twrp so easy and hassle free, had enough of USB burning tool and TV boxes with windows10 #MakeItEasy No |
|
|
|
Post by fards on Dec 5, 2016 0:48:34 GMT
I'm currently trying to force camera 3.
That crap mtkcam middleware is getting in the way
There's not even a cameraprofile_v3
On the other hand the kernel source on github looks promising.
Playing with camera sensor and lens drivers as the code is simpler and less debugged.
Fingers crossed
|
|
|
|
Post by maddes 1402 on Dec 5, 2016 6:35:54 GMT
Not for me cwm and twrp so easy and hassle free, had enough of USB burning tool and TV boxes with windows10 #MakeItEasy This is a community, mate. And in a community everybody should try to contribute. Google "Android kitchen" and try to do this by your own. Believe me;it is much fun and satisfying when you after some drawbacks manage it to build your "own" ROM. Usually a nandroid backup of fards ROM is enough. Regards, Matt |
|
|
|
Post by chucker on Dec 5, 2016 11:39:06 GMT
Succcess with flash of Mr. Fards BUILD11! I used SPTOOL V5.1632.00.000. All user data is still there....and camera working well like before OTA3. Thanks Fards and Viper1 for the great advice.
|
|
|
|
Post by fards on Dec 5, 2016 18:26:53 GMT
Build#12 has succeeded.
Using loads of new pulls from kernel on github. Might be placebo but it's a load another and friendlier on battery than before.
Needs bit more testing.
My attempts at forcing camera Hal 3 appear to have failed.
Camera takes photo then crashed. Requiring reboot.
Damn
Will revert that hack and rebuild
|
|
alxz
Junior Member
Posts: 65
|
Post by alxz on Dec 6, 2016 10:49:03 GMT
Whats broken on build 14?
|
|
|
|
Post by chucker on Dec 6, 2016 12:38:42 GMT
FYI... After the FARDS build 11...The camera app is using 9.39MB and cam is working good as stock, battery use is better than OTA3, but not as good at OTA1. With OTA1 Camera took up 8.00MB *worked well. With OTA3 update camera took up 9.20MB and would hang upon second use - message CANNOT CONNECT TO CAMERA issued, but battery drained 2x compared to OTA1. Attachments:
|
|
