Develop Bugs

[10 JAN 2011] [DISCONTINUED] CMN 6.2.0 v2.0 [RMNET/PPP] [OPTIMIZED] [Kernel: ocm_r1]

CMN [CyanogenMod_Nand] 1.02
CyanogenMod 6.1 Desire based.
Nand through magldr 1.09 or higher ONLY. DAF is included in the package (win7 version)
Features:
RMNET as default connection mode
Smartass governer as default
0.7 custom ril wrapper from LeTama in case anyone wants PPP instead
Click to expand...
Click to collapse
Kernel:
ocm_r1.
Click to expand...
Click to collapse
What works:
Everything works for me except of course 720p record/decode.
Click to expand...
Click to collapse
Included:
CM 6.2.0RC Nand Rom
DAF (DFT Android Flasher)
Click to expand...
Click to collapse
Instructions:
Boot phone into magldr and go into Flasher menu. Connect it to the PC and wait for it to recognize it.
Run ANDR_INSTALL.exe in extracted folder from .rar, follow the instructions. If you are updating magldr will prompt you if you want to delete or keep userdata. It is SAFE to keep userdata when updating from 1.0 -> 1.01 -> 1.02
For 2.0 you MUST wipe for best performance.
Click to expand...
Click to collapse
FAQ
[Q] My [insert something here] doesnt work!
[A] Search the thread, its most likely has been fixed
[Q] I get robovoice!
[A] delete or rename /system/etc/firmware/default.acdb
[Q] My apps arent showing fullscreen!
[A] Menu-> Spare Parts -> Uncheck Compatability Mode -> Reboot
[Q] Everything is too small, i want it ginormous again!
[A] Edit /system/build.prop the line ro.sf.lcd_density=200 to ro.sf.lcd_density=240 or some larger value (240 = AOSP default)
[Q] I have this weird problem and it works for everyone else but not for me, whats wrong?!
[A] Every problem is harder to diagnose if its just one person with the problem. If its just you then chances are you messed something up.
Click to expand...
Click to collapse
Additional Information:
This will wipe winmo off your phone. To get it back just flash a stock winmo rom. Also, magldr takes the place of the SECOND bootscreen (there are three stages). So you can flash a first stage bootscreen no problem (I have done this), but do NOT flash a second stage one.
Click to expand...
Click to collapse
Credits:
Rajko
Cotulla
LeTama
Cyanogen
etc.
Click to expand...
Click to collapse
Changelog:
v1.0:
Original Release
v1.01:
Added RMNET support and as default net connection.
Update to Hastarin 8.6. LeTama RIL Wrapper .7.
Smartass default governer
v1.01a:
Hotfix, Fixed wifi for 1.01 and 1.02
v1.02:
Removes quadrant advanced and fixes wifi issues.
v2.0:
Custom built CM6.2.0RC optimized for the HD2.
Added LED Notification settings.
Button backlight settings and RMNET/PPP configurations in CM Settings.
Added Wifi MAC address fix in kernel.
new LED driver.
Revert to 240dpi
Click to expand...
Click to collapse
No need for screenshots, its a stock CM rom built for nand. Quadrant advanced score is around ~1540. You wont be getting any better due to IO, which i doubt can be improved much, if at all. Its fast enough as it is.
Download v1.02: http://www.mediafire.com/?pkb4bht9gtk3axu
Download v2.0: http://www.multiupload.com/CL7MVNPUT0
How to fix wifi (1.02 only): http://www.youtube.com/watch?v=LsghZNqyT70 (Credit to TechBurrow)
Custom HD2 CM Settings are in:
CyanogenMod Settings -> User Interface -> LED Notifications
CyanogenMod Settings -> Input Settings -> Button Backlight
CyanogenMod Settings -> Performance Settings -> Data Connection Mode (requires reboot)
-ocm

10char..

Waiting for this for supeer long!!! Great

SuperWOW!!!!

are instructions included within the download? Or do we just flash this ROM like any other WinMO ROM??

you guys are the greatest! happy new year to all..

InitialG said:
are instructions included within the download? Or do we just flash this ROM like any other WinMO ROM??
Click to expand...
Click to collapse
+1 as I'm a little unsure, but I think it's just like flashing as you say. I'll find out in about two mins lol

Reno_79 said:
+1 as I'm a little unsure, but I think it's just like flashing as you say. I'll find out in about two mins lol
Click to expand...
Click to collapse
Actually, I found instructions. lol
There's another thread started by Cotulla and he put instructions how to do it.

Instructions added in first post

sorry for my question.... maybe I'm dumby.... it means we will have just the android operative system installed??? no winmo anymore???
and is it multilanguage and feat every leo device (i.e. european no Tmouse)???
thanx in advantage and congrats 4 your work!

Thanks alot for the ROM . I will begin testing this and cotulla's stock rom .
Happy new year

I'm extremely new to all of this, do I have to put my phone in a special mode or anything, or do I just run the exe file, and my phone will automatically start.
Sorry for the noob question.

wwwooowwww.........what good way to start the new year!

You must be joking !!! unbelievable
that's a great work , and a big step in the androworld. Thanks.
Did that change anything concerning the battery life ?
Will this procedure totally wipe W6.5.5 ?

solid.snake said:
You must be joking !!! unbelievable
that's a great work , and a big step in the androworld. Thanks.
Did that change anything concerning the battery life ?
Will this procedure totally wipe W6.5.5 ?
Click to expand...
Click to collapse
Yes, it will wipe winmo completely. To go back just flash a stock winmo rom.

Thanks for answer. Did you notice something concerning battery consumption ? How many mah ?

Possible to get a mirror ?

will this actually BRICK the phone? confirm works?

Great news on xda again.
Hats off for this Team

Now with possibility of installing android into nand could we have an opportunity to record 720p videos? or it's limited somehow?
another great milestone for xda-developers, you're the best

[ROM] Clean AOSP 4.1.1 build 5 (JRO03R)

Clean AOSP 4.1.1
build 5 (JRO03R)
for the Verizon LTE Galaxy Nexus (toro)
Twitter: http://twitter.com/javroch_dev
Based off of the AOSP "android-4.1.1_rX" branch. it's a mostly bare ROM, basically just rooted. I'll slowly add the previous features back in subsequent builds. I redid everything clean, from the ground up, for 4.1.1.
NOTE: I don't know if this 4.1.1 release will bring a new kernel with it, when Verizon releases it. As well, I don't know if there will be a new radio/etc, but this ROM does not include those if so. radio.img's aren't released via AOSP as far as I know. Feel free to correct me, if I'm wrong.
Modifications:
The only modifications that I have made are listed below, mostly they include enabling features that are already included in AOSP's source code, but weren't enabled by default:
Here's what's made it so far for 4.1.1:
Root/Superuser (ChainsDD)
Wi-Fi Tethering Subscription Check Removal
Enabled Backup/Restore
Google Movies access fix (peteralfonso)
Root Settings/Selective Root (cyanogenmod)
Custom "Clean extras" settings panel
Settings shortcut to Clean extras for easy access
SIP+VoIP
Battery Percentage in Status bar (Icon, Text, or Both)
Fixed Facebook Contact Sync (romanbb)
Reboot/Safe mode Options in Power menu
Here's what's to come in the near future:
Screenshot Options in Power menu (DvTonder)
Airplane/Silent Mode toggles via Custom extras
Number of home screens Option in Clean Extras
Aside from the explicit credit given above, I also spent tons of time looking through the git repo's of cvcps, peteralfonso, cyanogen, and many others. As well, I often used howto.ccroms.net and source.android.com/source as references. I'm sure there are others I'm not giving credit to that should be getting it.
Let me know what you think or if anything is broken! This is still a learning experience for me. Nobody's perfect.
Current Version: http://bit.ly/R71Yu8
MD5: 023271a54f428bb2197e667b9033ffe4
GApps: http://goo-inside.me/gapps/gapps-jb-20120726-signed.zip
Previous Versions:
4.1.1 for us with gapps: http://goo-inside.me/gapps/gapps-jb-20120726-signed.zip
build 4: http://bit.ly/QeH61x, md5: 3cc96cc0d703300a52ca885e49f73139
build 3: http://bit.ly/Tq0g88, md5: f3dea30b0922e2d67926510a6afd2a31
build 2: http://bit.ly/R69UYK, md5: cbbcadf2ed7a4ca7a516389abe6338af
build 1: http://bit.ly/PRByu2, md5: 69d101d025037c554ea2d0b25b55ad25
build 0: http://bit.ly/NqmH9M, md5: 3ad6f6134656b7adf65c6b48c8f5805f
4.0.4 for use with gapps: http://goo-inside.me/gapps/gapps-ics-20120317-signed.zip
build 5: http://bit.ly/HPGMq8, md5: eb0daa742d56189b770ff0662a984b12
build 4: http://bit.ly/IP7omo, md5: 1ec18075db77936b4972a7593a5878ec
build 3: http://bit.ly/HlA1ah, md5: fbcde7d07617ead21a369756df306304
build 2: http://bit.ly/HHYVQF, md5: e989c25388feaabee5da92c6c0965b7c
build 1: http://bit.ly/H3oM5P, md5: 590c36c905cd50a072027bbf9da8b1d1
4.0.3
build 4: http://bit.ly/GGEK7W, md5: fc1b733d37c8d61c21a3f248b8b6a2b7
build 3: http://bit.ly/FPBsSK, md5: 53dc910d5e1c23c32c7e4a696d679790
build 2: http://bit.ly/xbzUKR, md5: 56ccfc3856e0f6ea8e7aaecbbdc7b799
build 1: http://bit.ly/xNzKZQ, md5: a373793a69fb193ca162f24a719636b3

I just flashed to AOKP, so I will run that for a while. But, I will try this next.
Thanks!!

Updated / cleaned up the description to provide more information

Added the md5 - a373793a69fb193ca162f24a719636b3

Just a heads up, I'm in the process of migrating everything over to github. As well, I'll be adding facebook sync and possibly one or two more tweaks hopefully tonight. Also, starting with the next release, I'll be naming them "Clean AOSP x.y.z build #". So, the update hopefully coming tonight will be "Clean AOSP 4.0.3 build 2". Any further tweaks / modifications will probably be added to a separate ROM, possibly Clean AOSP+, because I really want to keep Clean AOSP tweak free.

Build 2 posted, includes fixed Facebook Contact Sync. That's about it for now. Next thing I want to do is validate whether or not Google Wallet is working. I've been able to use NFC to beam, etc and everything else seems to be working fairly well so far. Let me know if anybody has any feedback for me
I tried to see if I could get Twitter's Contact Sync working in a similar fashion, but it seems it's an issue on their end: http://support.twitter.com/groups/3...cles/213727-known-issues-with-the-android-app

so to clarify...the apps like rom manager and terminal emulator will be removed?
I hate having to delete all the apps from CM9
thinking about making a rom that is as close to stock as possible (all google apps and stuff but its still going to be based on CM)
if your rom removes all this stuff....niiiceeeeeee.

ezcats said:
so to clarify...the apps like rom manager and terminal emulator will be removed?
I hate having to delete all the apps from CM9
thinking about making a rom that is as close to stock as possible (all google apps and stuff but its still going to be based on CM)
if your rom removes all this stuff....niiiceeeeeee.
Click to expand...
Click to collapse
My ROM isn't based on CM at all in any way whatsoever. It's based on AOSP source directly. So no, there won't be any ROM Manager or Terminal Emulator included by default. My goal for this ROM was actually exactly what you said, "[to make] a rom that is as close to stock as possible".

I'm not gonna add this as a "Modification" or anything... because I didn't really do anything to fix anything, but I just wanted to confirm that I was successfully able to use Google Wallet on Clean AOSP last night. Apparently, I just needed to "Reset Google Wallet" from when I flashed from stock

today, i will begin working on implementing the new root settings menu from cyanogenmod into clean aosp. i feel that this is really an essential feature for any ROM and so i think this is a necessary modification for clean aosp

I'm currently uploading build 3. should be up tonight / tomorrow. it includes the root settings menu under developer options. the menu provides four options "Disabled", "Apps Only", "ADB Only", and "Apps and ADB". currently the default in build 3 is "Apps Only", however i will probably be putting out a build 4 which defaults it to "Disabled". my code is mainly based off of cyanogenmod's commits mentioned in the blog post here, and functions much in the same way. cm doesn't build Superuser from source, but i do, so I also added some of my own code related to this in Superuser. basically in CM it would say that superuser had granted apps permissions if they were on the whitelist, even when root was disabled via the settings and they didn't actually have root. i plan on launching the developer's settings intent as well, if you get denied superuser permissions because the setting is disabled. this way you can easily re-enable it. but that isn't in build 3.
i should note that this way doesn't seem to give you access to google play movies. i like to think of it as a selective root, rather than completely removing root altogether. but, the main purpose of this is security, not to enable google play movies. i've been leaving mine on "Disabled", and i really don't find that i have to re-enable root very often.

posted build 3..

This sounds really awesome! Does the voip work and could you include an option to allow led with screen on?

I haven't used it as I don't have a VoIP account, but the options are there and should be enabled/working fine. I'm not sure what you mean by "allow led with screen on" to be honest.

Normally the led will only blink if the screen is off.

foxdog66 said:
Normally the led will only blink if the screen is off.
Click to expand...
Click to collapse
Got it, to be honest I'm sort of reluctant at this point to implement too many tweaks into Clean AOSP. I kind of want it to be as barebones as possible. But, as I am considering a few others, I might look into this one as well, either as part of Clean AOSP or as part of some Clean AOSP+ version with extra modifications that I might put out separately.
Either way, if you do give it a shot, let me know your findings related to VoIP. I have no reason to think it shouldn't work, but I haven't tried it yet.

Thanks for this!
What kernel are you using for this build? I assume the stock google one.
Including status bar toggles and soft key options would be the only mods I would look from the clean build.

BarberAE said:
Thanks for this!
What kernel are you using for this build? I assume the stock google one.
Including status bar toggles and soft key options would be the only mods I would look from the clean build.
Click to expand...
Click to collapse
I'm just using the stock Google one. Haven't changed anything there. Haven't really played around with kernel development.
Those are likely mods I'd include in some sort of Clean AOSP+ version as well. Along with reboot options, though those I might actually shoehorn into regular Clean AOSP as well. Either way, I will be looking to getting in some of these mods in either Clean AOSP or some other AOSP+ version when time permits.

I wanted to wait and get more features in, but I might be busy for the next week or so. So, here's build 4. The only change is that root is "Disabled" by default

I just saw that the AOSP 4.0.4 Source Code is being pushed out today. I'm gonna see if I can't get a build out in the next couple of days, probably just with the features I've implemented for 4.0.3

[ROM][Unofficial/Experimental][Android 4.3] CyanogenMod 10.2 for SGS4A (int'l)

-------------------------Warning!-------------------------------------
This ROM is for SGS4A (int'l) ONLY. Does not work on SGS4 from AT&T as it has a locked bootloader.
Please refer to this thread for a bounty on the bootloader.
-------------------------Please note---------------------------------
This is an experimental build of CyanogenMod 10.2 running Android 4.3.
Meaning there's a couple of known issues with the camera. It is my hope these will be sorted out over time.
If anyone has any interest in helping out, please PM me. Or simply fork the code if you want.
-------------------------Instructions---------------------------------
Install CWM recovery from here.
Download most recent ROM from here.
Download most recent Google Applications for Android 4.3 from here.
Boot into recovery by holding the Volume Up button as the phone is booting.
Back up your current ROM inside CWM recovery.
Flash CyanogenMod ROM to your device using CWM recovery.
Flash Google Applications to your device using CWM recovery.
Do a wipe data/factory reset from within CWM recovery.
Reboot system
---------------------------Known issues-----------------------------
Several camera functions such as HDR don't work.
---------------------------Build from source------------------------
Please consult this guide for setting up CyanogenMod for compile.
Please use
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.2
when you initialize the CyanogenMod repository so you get the source for CM-10.2.
Download roomservice.xml (see below) and put in ~/android/system/.repo/local_manifests/.
Run 'repo sync' and compile with 'brunch jactiveltexx'. You can get the proprietary files from the ROM.
As always, I take no responsibility in case your phone blows up.
And thanks to the CM team for all their hard work.

Downloads
---------------------------CM-10.2 ROM (Android 4.3) -------------------
---------------------------cm-10.2-20130917-----------------------------------
CyanogenMod 10.2 - 20130917
CyanogenMod 10.2 - 20130917 (mirror - thanks to mrvovven)
---------------------------cm-10.2-20130910-----------------------------------
CyanogenMod 10.2 - 20130910
CyanogenMod 10.2 - 20130910 (mirror - thanks to mrvovven)
---------------------------CM-10.1 ROM (Android 4.2.2) ----------------
CyanogenMod 10.1 - 20130810
----------------------------Google apps -------------------------------
Download the official Google apps. Need to download this in order to have apps like Google Play.
For CM-10.1 choose Android 4.2 apps.
For CM-10.2 choose Android 4.3 apps.
http://goo.im/gapps
------------------------------------- KERNELS ---------------------------------
- SGS4A android 4.2.2 kernel for CM10.1
https://www.dropbox.com/s/oo1hr2n6evp3zu9/sgs4a-cm10-1kernel.zip

----------------------- Changelog--------------------
-------CyanogenMod 10.2 - 20130917----------
- Fixed video preview resolution
- Disabled zsl for slightly more stable camera app.
-------CyanogenMod 10.2 - 20130910----------
- Updated kernel to most recent version of cm-10.2 for SGS4.
- Replaced all sensor drivers with SGS4A kernel sources.
- Replaced several camera blobs in /system/lib/* with SGS4A versions enabling basic camera functionality.
-------CyanogenMod 10.1 - 20130810----------
Initial build.

Good job.
Sent from my Nexus 7 using Tapatalk 4

hello
anyone tried this out ?
feedbacks ?
thanks in advance

pdf5 said:
hello
anyone tried this out ?
feedbacks ?
thanks in advance
Click to expand...
Click to collapse
This is not something you should install unless you want to be compiling and debugging yourself. It's far from usable as day to day rom. I hope I'm clear on that.

Fixed wifi and a number of small issues. Should be a lot more stable. Seems the main remaining issue is, not surprisingly, the camera. If anyone knows how the entire camera driver setup is supposed to work in android, I'd love some help

LeJay said:
Fixed wifi and a number of small issues. Should be a lot more stable. Seems the main remaining issue is, not surprisingly, the camera. If anyone knows how the entire camera driver setup is supposed to work in android, I'd love some help
Click to expand...
Click to collapse
Call it just a hunch. But have you tried the camera drivers from the s3 ? I would say that it's basically the same camera and has been added in s4 active because after 1 year it became very cheap to continue manufacturing and this way compensate for the more expensive case and water proofing.

aurelm said:
Call it just a hunch. But have you tried the camera drivers from the s3 ? I would say that it's basically the same camera and has been added in s4 active because after 1 year it became very cheap to continue manufacturing and this way compensate for the more expensive case and water proofing.
Click to expand...
Click to collapse
Honestly, not exactly sure how the setup is. I assume it's mostly in some proprietary libs separate from the kernel, but it's hard to find good information on it.
Sent from my GT-I9295 using xda premium

Thank you for you work!!
But search another File hoster!! DropBox close your account if the trafic is to big!!

So S4 Active Original is the intl i9295 ?
EDIT: oh ok the real dev thread
Sent from my GT-I9295 using xda app-developers app

I've a MicroSD in my SGS4A and i can't choose the external_sd in the CM File Explorer.
Is there any solution?
For example creating symlink or mounting in /sdcard
I've never tried anything of that!

It's working really well Wifi works yay, well done! Hopefully you can get the camera working too.

Building from source
Hi,
I'm happy to see such great progress already, and am only diving in to this because I'd like to be able to lend a hand in any way I can.
Is it too soon to be asking questions about how to build for 10.2? I'm having a go at it right now, and if I use Lejay's kernel and device configuration (jactivelte), the kernel fails to compile, something about BUG_ON rcu error, I can come back to that if its relevant. So I tried Epsylon3's suggestion to use tpruvot's kernel and device config. This builds a rom, but black screen, can't see anything or get into adb. If I flash Lejay's kernel over the top of my 10.2 build, it boots. Phone (dialer) keeps force closing in a loop, which is annoying, but asides from that it seems to boot.
Keep up the good work, can't wait to get some 10.2 love.

snadge said:
Hi,
I'm happy to see such great progress already, and am only diving in to this because I'd like to be able to lend a hand in any way I can.
Is it too soon to be asking questions about how to build for 10.2? I'm having a go at it right now, and if I use Lejay's kernel and device configuration (jactivelte), the kernel fails to compile, something about BUG_ON rcu error, I can come back to that if its relevant. So I tried Epsylon3's suggestion to use tpruvot's kernel and device config. This builds a rom, but black screen, can't see anything or get into adb. If I flash Lejay's kernel over the top of my 10.2 build, it boots. Phone (dialer) keeps force closing in a loop, which is annoying, but asides from that it seems to boot.
Keep up the good work, can't wait to get some 10.2 love.
Click to expand...
Click to collapse
Comparing the 9295 and 9505 kernels, there's quite a lot of differences. Cyanogenmod tried to merge the two, but apparently gave up. The question is really if we should start with the 9505 and add the camera or start with the 9295 and make it compatible for CM. The stuff i uploaded here is a port of the 9505 kernel, but now I'm looking into starting out with the 9295 kernel instead.
The problem with 10.2 is of course there's no released 9295 kernel for android 4.3. I'm guessing there are not that many differences, so it might not be too hard.
I think I'm getting the same compile error you were with 10.2. Not sure what it means.

Are you going to try to make CM 10.2?

LeJay said:
Comparing the 9295 and 9505 kernels, there's quite a lot of differences. Cyanogenmod tried to merge the two, but apparently gave up. The question is really if we should start with the 9505 and add the camera or start with the 9295 and make it compatible for CM. The stuff i uploaded here is a port of the 9505 kernel, but now I'm looking into starting out with the 9295 kernel instead.
The problem with 10.2 is of course there's no released 9295 kernel for android 4.3. I'm guessing there are not that many differences, so it might not be too hard.
I think I'm getting the same compile error you were with 10.2. Not sure what it means.
Click to expand...
Click to collapse
I had a chat with noobnl about it, and he pointed out a patch on gerrit: http://review.cyanogenmod.org/#/c/44552/
I spent hours manually merging it with cm jf kernel, to finally end up with a kernel that gives me. You guessed it, a black screen. After investing about a days worth of effort into it, I ended up with a buggy unstable CM10.2 build, that will boot if I flash LeJay's kernel zip, but its unuseable. It's going to take some serious effort to come up with a functioning CM10.2 kernel for the International S4 Active. In the meantime, a CM10.1 build with a non functioning camera, is still way better than the stock TouchWiz rom, so I'm happy. :laugh:

Ok, I got bored and had another play around with 10.2 and the CM jf kernel. With the black screen problem, if you power the device down, then boot into recovery (power + vol up), you can adb pull /proc/last_kmsg and it tells an interesting story. It looks like the init scripts are totally borked. init.qcom.rc and init.carrier.rc are completely missing. I tried simply copying them into the root, but it looks like its a bit more complicated than that. The problem is clear that it is unable to mount /system for whatever reason, because it can't find /system/bin/sysinit, then pretty much gives up after that.
This looks like a pretty simple problem for a relatively experienced device maintainer, or rom kernel dev to be able to fix. It would be nice if we could get some more developer attention for this device.

snadge said:
Ok, I got bored and had another play around with 10.2 and the CM jf kernel. With the black screen problem, if you power the device down, then boot into recovery (power + vol up), you can adb pull /proc/last_kmsg and it tells an interesting story. It looks like the init scripts are totally borked. init.qcom.rc and init.carrier.rc are completely missing. I tried simply copying them into the root, but it looks like its a bit more complicated than that. The problem is clear that it is unable to mount /system for whatever reason, because it can't find /system/bin/sysinit, then pretty much gives up after that.
This looks like a pretty simple problem for a relatively experienced device maintainer, or rom kernel dev to be able to fix. It would be nice if we could get some more developer attention for this device.
Click to expand...
Click to collapse
You probably forgot to add jactivelte to the list at the bottom of device/jf-common/Android.mk. I didn't want to fork their repo just to add one word on a line, so you have to do this manually. It's probably also a good idea to extract rom files from a cm.10.2 rom for something like jfltexx.

LeJolly said:
Are you going to try to make CM 10.2?
Click to expand...
Click to collapse
I have cm10.2 running. The problem is really the camera.

[Oneplus 3T][20161214] Unofficial CyanogenMod 14.1 by PeterCxy

Code:
/*
* Your warranty is now VOID!
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
This is my custom ROM built only for Oneplus 3T. DO NOT try to flash it on Oneplus 3.
This ROM is NOT compatible with sultan's custom kernel (actually not compatible with any kernel that is not built for CM14.1)
I built this for my own daily use, and shared because I did not see another public release of CM14.1 yet. This is based on the work of morckx at GitHub.
Sorry for you all, but the final exam for me is coming I might not have time to update this ROM regularly, so let's just wait for CM's official support or you may turn to the unified unofficial nightlies lol.. (actually I could have updated this last weekend but I went for dating, haha.)
ROM features
- Vanilla CyanogenMod 14.1 (last synced: 2016-12-14 GMT+8)
- Ported to Oneplus 3T (Thanks to morckx for merging 3T changes into the CM kernel)
- No OTA supported for this ROM, if you receive any, please ignore it and DO NOT install. (Though you will not be able to install that at all)
About the embedded "Brevent" App:
This is a refactored version of the Xposed module "Prevent Running" (http://repo.xposed.info/module/me.piebridge.forcestopgb) that do not depend on the Xposed framework but depend on framework patches, which I need for daily use because I have to stop some Chinese apps from keeping the whole device awake all the time. Sorry if adding this brought you any inconvenience, and you can turn the 'Auto Prevent' off in Brevent -> User Guide -> Advanced Settings, thus it will not affect apps any more. Read the instructions at https://github.com/liudongmiao/Brevent to learn more about it.
Installation
Flash the zips with a custom recovery, for example, TWRP.
Known bugs
- All BUGs that the CM14.1 ROM for Oneplus 3 has
- Front camera goes only up to 4MP instead of 16MP
- New photos may become green sometimes (use a third-party camera app instead if you experience this issue)
- (Confirmation needed) LTE may not work as expected for some carriers. However I did not encounter any problem for my China Telecom LTE(+) network for now.
- You tell me
Source code
https://github.com/LOSP/local_manifests
Downloads
2016.12.14
AndroidFileHost: https://www.androidfilehost.com/?fid=457095661767122729
- Updated camera drivers and configurations from OxygenOS 3.5.3 for OnePlus 3T (front camera 16MP still missing, maybe it needs a CameraWrapper)
- Synced lastest CM sources
- Applied framework patches for Brevent and pre-installed Brevent.apk (An app that tries to prevent selected apps from keeping themselves alive and keeping the CPU awake, see https://github.com/liudongmiao/Brevent for details)
DISCLAIMER: I, PeterCxy, am not affiliated with the author of Brevent, and do not get any income for embedding this app, and this app do not include any form of ADs.
2016.12.13
AndroidFileHost: https://www.androidfilehost.com/?fid=673368273298916355
Screenshots
See attachments
Donation
Bitcoin: 33yHkcWmTbKegCVVeTkqKcAdibG814f9To
Credits to:
- All CyanogenMod contributors
- morckx for merging the kernel sources (actually I am just a packager of his work)

Thanks a lot

Wow! Awesome man! Thanks!

awsome great job OP

Seriously... lol right after I load cm13 on my device you go an do this
Thanks for nothing lol
Jk
Thanks OP

c_86 said:
Seriously... lol right after I load cm13 on my device you go an do this
Thanks for nothing lol
Jk
Thanks OP
Click to expand...
Click to collapse
Use multirom [emoji41]
Sent from my Darkside of Oneplus 3T

OMG! Going to flash it today! Thanks a lot!!!!
Gesendet von meinem ONEPLUS A3003 mit Tapatalk

c_86 said:
Seriously... lol right after I load cm13 on my device you go an do this
Thanks for nothing lol
Jk
Thanks OP
Click to expand...
Click to collapse
No worries, you can just dirty flash this over Sultan's rom, did the same for the OPO, OPX and now for the 3T :
- Backup in TWRP (Just in case)
- Do not wipe anything!
- Flash CM14.1
- Flash Gapps 7.1 ARM64
- Wipe cache/dalvik
- Reboot
Clean flash is always better ofcourse but for now everything is working perfectly for me.

michie said:
No worries, you can just dirty flash this over Sultan's rom, did the same for the OPO, OPX and now for the 3T :
- Backup in TWRP (Just in case)
- Do not wipe anything!
- Flash CM14.1
- Flash Gapps 7.1 ARM64
- Wipe cache/dalvik
- Reboot
Clean flash is always better ofcourse but for now everything is working perfectly for me.
Click to expand...
Click to collapse
Thanks! I may try this.. BTW what are some of the bugs he mentions that are on the op3?

Thanks for this @PeterCxy
I think it would be better to rename the file to: cm-14.1-20161213-UNOFFICIAL-oneplus3T.zip
To avoid confusions , just saying ...

c_86 said:
Thanks! I may try this.. BTW what are some of the bugs he mentions that are on the op3?
Click to expand...
Click to collapse
They don't mention device specific bugs, only "many minor bugs" so I guess it will be in CM framework. Each nightly will bring new fixes but.new bugs too till they bring out a stable branch. I would advise staying on a nightly that seems stable for your use and only update when the monthly security patch is released by google and merged by CM.

michie said:
They don't mention device specific bugs, only "many minor bugs" so I guess it will be in CM framework. Each nightly will bring new fixes but.new bugs too till they bring out a stable branch. I would advise staying on a nightly that seems stable for your use and only update when a security patch is released and merged.
Click to expand...
Click to collapse
Cool thanks. Just read over the op3 cm14.1 thread and it seems like everything major is working.

pvillasuso said:
Thanks for this @PeterCxy
I think it would be better to rename the file to: cm-14.1-20161213-UNOFFICIAL-oneplus3T.zip
To avoid confusions , just saying ...
Click to expand...
Click to collapse
Yes I agree. The naming was directly taken from CM14.1 building system, and I was too excited to rename the device.... But no worry, oneplus3 users will not be able to flash it into their devices.

Anyone having issues with the screen turning yellowish after rebooting?

c_86 said:
Anyone having issues with the screen turning yellowish after rebooting?
Click to expand...
Click to collapse
That's LiveDisplay, just turn it off in Settings -> Display -> LiveDisplay

PeterCxy said:
That's LiveDisplay, just turn it off in Settings -> Display -> LiveDisplay
Click to expand...
Click to collapse
I just realized that when I was playing with the settings. Derp
Thank
Edit... I know i shouldn't care but I do... but does it seem like the ram usage is high on this? Averaging around 1.9gb after a fresh reboot...

c_86 said:
I just realized that when I was playing with the settings. Derp
Thank
Edit... I know i shouldn't care but I do... but does it seem like the ram usage is high on this? Averaging around 1.9gb after a fresh reboot...
Click to expand...
Click to collapse
Well I did not really think so because I just went from OxygenOS and the free ram was usually 1.8GB while now it is around 2.8GB.

PeterCxy said:
Well I did not really think so because I just went from OxygenOS and the free ram was usually 1.8GB while now it is around 2.8GB.
Click to expand...
Click to collapse
Sorry should have specified better that's 1.9 go usage not free. 1.9 go used. In cm13 for example it was around 1.3gb used

Here we go... Any bug? Echo in call?
Fingerprint is fast?
Enviado desde mi ONEPLUS A3003 mediante Tapatalk

For the people who are interested and maybe feed for the OP, working perfectly and tested by me on this rom :
Nougat System app Debloater Script:
(Maximum Debloater version)
- Flash in recovery
- Removes AOSP apps so you can replace them with the new google PlayStore apps :
AOSP Browser2 -> Google Chrome
AOSP Calculator -> - Google Calculator
AOSP Calendar -> Google Calendar
AOSP Camera2 -> Open Camera - F-Droid
AOSP Contacts -> Google Contacts
AOSP DesktopClock -> Google Clock
AOSP Dialer -> Google Phone
AOSP Email -> Google Gmail
AOSP Gallery -> Google Photos
AOSP Keyboard -> Google Keyboard
AOSP Messaging -> Google Messenger
AOSP Music -> Google Play Music
AOSP QuickSearchBox -> Google
BE SURE TO HAVE GOOGLE KEYBOARD INSTALLED BEFORE FLASHING. OTHERWISE YOU WILL HAVE NO KEYBOARD AND WILL HAVE TO SIDELOAD THE APK.
Download : [url]http://forum.xda-developers.com/google-nexus-5/themes-apps/gapps-debloating-scripts-aosp-t3457204[/URL]

| ROM | LineageOS 14.1 | unofficial | 27/02/2017 | Signature Spoofing integrated |

Hello
I am going to release unofficial builds of LineageOS 14.1 for Wileyfox Crackling. The builds will be updated every month after a new security patch level is reached.
The build I made can be flashed on top of Cyanogenmod 13 build (with wiping dalvik and cache). It should work without any problems; I do not experience any.
But I do not take any responsibility if your favorite app/setting/etc. is not working anymore.
If it makes problems, wipe data/dalvik/cache and install again.
Besides that the ROM has two extra features:
I patched signature spoofing support into the ROM. Now it is possible to install microG. This is a re-implementation of Google’s proprietary Android user space apps and libraries. So for many cases you do not have to install the proprietary GAPPS anymore.
Note: This feature is disabled by default and will not affect the ROM in any way. It has to be enabled in the according settings.
Also, there's an option available to record calls now. Please respect the privacy of others.
Android security patch level:
Code:
[URL="https://source.android.com/security/bulletin/2017-02-01.html"]February[/URL] | 2017-02-05 security patch level
Version/Filename:
Code:
lineage-14.1-20170227-UNOFFICIAL-crackling.zip
Download:
Code:
[B][SIZE="2"]Openload.co:[/SIZE][/B]
https://openload.co/f/DBKYItUGllA/lineage-14.1-20170227-UNOFFICIAL-crackling.zip
https://openload.co/f/grRwId0HJJE/lineage-14.1-20170227-UNOFFICIAL-crackling.zip.md5sum
Alternativ:
[B][SIZE="2"]Free.fr:[/SIZE][/B]
http://dl.free.fr/uqIBAf8dM
The kernel and device sources I used to build the ROM can be found here:
Code:
https://github.com/lineageos

thomson.aa said:
Hello
This is my first build of LineageOS for Wileyfox Crackling.
I flashed it on top of my Cyanogenmod 13 build (with only wiping dalvik and cache) and it so far works without any problems.
But I do not take any responsibility if your favorite app/setting/etc. is not working anymore.
This release has the root access option disabled because LineageOS disables root for apps by default. It has to be enabled before building the rom - I didn't know that so I will provide an updated rom with root access for apps available.
Besides that the rom has one extra feature:
I patched signature spoofing support into the rom. Now it is possbible to install microG. This is a re-implementation of Google’s proprietary Android user space apps and libraries. So for many cases you do not have to install the proprietary GAPPS anymore.
Note: This feature is disabled by default and has to be enabled in the according settings.
Android security patch level:
Code:
[URL="https://source.android.com/security/bulletin/2017-01-01.html"]January[/URL] | 2017-01-05 security patch level
Version/Filename:
Code:
lineage-14.1-20170117-UNOFFICIAL-crackling.zip
Download:
Code:
https://openload.co/f/WCt_JxGZ-UE/lineage-14.1-20170117-UNOFFICIAL-crackling.zip
Click to expand...
Click to collapse
Sorry thomson.aa sorry i do not have english my google translation. Work is very nice thanks one has a mistake sim card people do not see a way to solve it? I wish you continued success.

Where is the source ? You can't post this without kernel source

I dirty flashed this over crDroid and it seems to be working pretty well. Thanks.
All my app's (not many at the moment) were working fine.
Playstore thinks it's 'no carrier Wileyfox Wileyfox Swift'... but I guess that's better than 'Wileyfox Pixel XL' (crDroid).
On initial booting the status bar wouldn't pull down but works ok after a reboot.
Buttons were a bit messed up which only gave me a back button even though the usual defaults were all set. After deleting them and re-adding them they worked fine. I'm guessing this may be due to dirty flashing. Shame the button customisation is just as basic as cm13 especially after using crDroid.
Using Kernal Auditor Mod I see that the cpu only scales down to 800mhz and the gpu scales up to 400mhz. I don't know much about this but won't this make it a little power hungry?
Going through the settings, I'm thinking that LOS14 isn't quite as complete as the cm13 I was using a few weeks ago. Although I guess this is to be expected at this stage. And I'm used to the more versatile crDroid now so I'll be restoring that in a mo.
This MicroG project sounds great. It seems a bit complex to get it working as I'd like but I definitely be having a go when I get my head around it.
All in all, Great job. Keep up the good work... please. I'm already waiting for the next release.
Oh, and er... Surely you could find a better file host???

I tried to build the Image myself by using your other Thread's How-To and after flashing i had no WIFI.
Now i flashed this build and WIFI is also not working.
[Edit]
I've collected some Logs - perhaps they'll help.
[Edit2]
Now i tried another '14.1-ROM' and i've the same problem....
During all my Tests the shown MAC-Address during the 'inital install' was weird: 02:00:00:00:00:00.
Before the 14.1 Lineage i had the latest CMmod 13 running without any Problems :/

Ok - solved it....
I encrypted my Device during CM13 and always entered my Key during Boot/TWRP and Formatting/Installation of 14.1.
Now i *really* formated all the Data (and the former encryption), rebooted to Recovery and sideloaded the Image+Gapps.
Now WIFI is working.

How do I enable signature spoofing ? I can't find any relevant setting.

M.A.K said:
How do I enable signature spoofing ? I can't find any relevant setting.
Click to expand...
Click to collapse
Settings -> Apps -> Gear symbol -> App permissions -> Spoof package signature

No... it's not there for me.

M.A.K said:
No... it's not there for me.
Click to expand...
Click to collapse
Works like it is supposed to be. The setting/app permission is only available if you install an app that requires that permission.
So, if you install microG the setting for signature spoofing will become available.

fred0r said:
Now i *really* formated all the Data (and the former encryption)
Click to expand...
Click to collapse
Could you tell me how to do that? I remember trying to find a way to remove encryption back in the day on my Nexus 5 and wasn't able to do it. Thanks!

thomson.aa said:
Works like it is supposed to be. The setting/app permission is only available if you install an app that requires that permission.
So, if you install microG the setting for signature spoofing will become available.
Click to expand...
Click to collapse
Ah, yes... got it now, thanks.

jobedius said:
Could you tell me how to do that? I remember trying to find a way to remove encryption back in the day on my Nexus 5 and wasn't able to do it. Thanks!
Click to expand...
Click to collapse
I booted into the TWRP 3.0.3 and did not enter my Encryption-PW (cancel) and then clicked 'Wipe' and then 'Format Data'.

update to official build?
Is it possible to update (aka dirty flash) to the now released official build? I had some problems doing that, see https://forum.xda-developers.com/showpost.php?p=70829582&postcount=8
Cheers

Nope, its not
Mithodin said:
Is it possible to update (aka dirty flash) to the now released official build? I had some problems doing that, see https://forum.xda-developers.com/showpost.php?p=70829582&postcount=8
Cheers
Click to expand...
Click to collapse
Twrp shows error 7(the data is incompatible). You need to wipe data, cache partitions and the system partition. Then install the zip with arm64 android 7.1 g-apps.
Cheers:good:

fred0r said:
I booted into the TWRP 3.0.3 and did not enter my Encryption-PW (cancel) and then clicked 'Wipe' and then 'Format Data'.
Click to expand...
Click to collapse
Aahhh, that makes sense if you know it! Thanks!