Database Users

[APP] Milestone - Overclock (requires root)

Hi all,
I realize this is a post about a Motorola phone but please bear with me.
As you might know, the Milestone firmware is firmly locked, unlike its cousin Droid. Among many things, this forbids overclocking because we can't change the kernel and unlock new frequencies.
However I developed a solution that allows overclocking by changing key structures directly in the kernel memory in runtime. All you need is a rooted phone; no flashing involved. For this to work, the module must know two memory addresses that are specific to each kernel. Fortunately, Motorola appears to have reused its kernel on most 2.1 firmwares, and I've yet to come across a firmware where it doesn't work by default. Confirmed working are Central Europe, Telus and Brazilian firmwares. Testers are welcome to give it a try.
Now for the relevant part for XDA: in theory this can be applied to any kernel on any other phone. You may say it's unneeded because you can already overclock; but you must flash a specific kernel to get a particular speed. It would be much better to be able to set any maximum frequency/voltage on the fly without flashing or rebooting. For instance, you could overclock to 1.0 GHz before a browsing or gaming session and then return to a lower frequency like 600 MHz, though still overcloked, for battery savings and safety. It's up to you.
Milestone users can try it out now:
http://code.google.com/p/milestone-overclock/
For the rest of you, what do you think?

sounds fantastic, I'd love to check it out but for the life of me I can't find the page.
If you want to pm it to me, I'll post it.

Nice. Telus Milestone User here. Would love to learn how to do this for mine.
Here is the project link:
http://code.google.com/p/milestone-overclock/

found it. looks like a fantastic idea.
How can we help get the addresses?

awesome .....wht there is no milestone/droid section here is beyond me ....wtf

Because it was decreed months ago by someone and no one seems to like changing their mind once they make a decision in this day and age.....

but it's need to root, could you fix it？

stevecai said:
but it's need to root, could you fix it？
Click to expand...
Click to collapse
what's the problem with rooting the milestone? There's plenty of solutions for that. Just no custom kernel/ramdisk, which this works around by using a kernel module.

hi,
i use the 2.1-reu version on my milestone,
but in order to prevent the 2.1 introduced alarm bug,
i have updated the kernel (only) to the 2.1-telus
(via a sbf).
is possible to use this mod to overlock my phone?
how?
if not, how help you to obtain the addresses?
thank's and continue your great work!
robert

gemini002 said:
awesome .....wht there is no milestone/droid section here is beyond me ....wtf
Click to expand...
Click to collapse
XDA is a HTC developer forum, not an Android forum. Google some moto modding sites, i know modmymoto.com is pretty good, found out how to root the Cliq (garbage) there.

staticshadow said:
XDA is a HTC developer forum, not an Android forum. Google some moto modding sites, i know modmymoto.com is pretty good, found out how to root the Cliq (garbage) there.
Click to expand...
Click to collapse
I have read this explanation several times.
I do not mind, but then because there are subforums dedicated to sonyericsson, hp, etc in xda.
modmymoto is good but the best developers site is, withous any doubt, xda-developers!

Re: milestone-overclock
Xda-developers is for htc and android is for porn.
Welcome to xda btw and great job. Now prepared to be flamed for uttering the M word.
-------------------------------------
sent via xda app from my milestone

ady said:
android is for porn.
Click to expand...
Click to collapse
are you Steve Jobs ?

miragu said:
Hi all,
Now for the relevant part for XDA: in theory this can be applied to any kernel on any other phone.
Click to expand...
Click to collapse
Will the method to find the right address that will be posted at /wiki/Disassembly work with every phone and kernel,too?
Has the app something like a setting where you can just change the address to the one you found with the method above?
Would really love an overclocked 2.1 on the HTC HERO. There is no oc-2.1-kernel for the Hero, yet.
Thanks for the great work, til now!

this is a good via to mod any application.
please, publish the source code of your applicacion ASAP.
thx

Source code for the kernel module released
Hi all,
Thank you for your support. I've just uploaded the source code for the kernel module and also the standalone module itself (it's included in the apk but still). Will write the Disassembly section soon, stay tuned.

miragu said:
Hi all,
Thank you for your support. I've just uploaded the source code for the kernel module and also the standalone module itself (it's included in the apk but still). Will write the Disassembly section soon, stay tuned.
Click to expand...
Click to collapse
hi,
i'm interested on include this in my system applications directory,
in order to prevent your deletion on hardreset, and in order to make it available FOREVER
the instructions are that:
cp OverClock.apk /system/app
cp OverClock.ko /system/lib
????
thx

The overclock.ko is created automatically when you press the "Load module" button in /data/data/pt.com.darksun.milestoneoverclock/files/overclock.ko. You don't need to copy it. I'm providing it separately so that people can load/bundle it without ever running the apk.
bartito said:
hi,
i'm interested on include this in my system applications directory,
in order to prevent your deletion on hardreset, and in order to make it available FOREVER
the instructions are that:
cp OverClock.apk /system/app
cp OverClock.ko /system/lib
????
thx
Click to expand...
Click to collapse

ok,
if i'm interested on have overclocking on my milestone after boot the system, and don't interested on manually execute the apk on each reboot, i need only to copy the OverClock.ko to /data/data/pt.com.darksun.milestoneoverclock/files/overclock.ko on boot time ?
but in your wiki page says to execute "insmod overclock.ko max_rate=800000 max_vsel=62"
please, provide me instructions to set overclock in boot time

The module created by the apk is preserved across reboots. However, if you want to run the module completely standalone I recommend you put it in /data/local/overclock.ko and run insmod /data/local/overclock.ko max_rate=800000 max_vsel=62

[MOD]Hey Snapdragon! Mod - 4/14/15

Disclaimer
I'm not responsible for anything that may happen to your device. I've tested this mod to the best of my abilities, but I can't guarantee anything. Make a complete backup before applying any of these changes. If you brick your device, boot loop, lose data, or etc...again, I'm not responsible.
CM12 - Working
- CM12S YNG1TAS0YL with stock kernel
- CM12 nightly with stock kernel
CM11 - Working
- CM11S XNPH30O, XNPH33R, XNPH38R, XNPH44S, and XNPH05Q with stock kernel
- CM11, PAC-man, crDroid with most recent kernels
- franco r35 kernel
CM12.1 - Not Working
- CM12.1 nightly (bootloop)
CM11 - Not Working
- LiquidSmooth ROM (mediaserver seg faults immediately)
- OmniROM
Also, I found a commit in the CM source that adds Voice Wakeup options to the Settings app. If the ROM doesn't have this code compiled into their Settings, the mod will probably not work. You'll still be able to go through the training process, however, I don't believe Google Now will launch because the intent action is never being set.
Instructions
1.) Backup any important data on your phone (files, pictures, etc.)
2.) Boot into recovery. I use and have only tested with TWRP
3.) Make a nandroid backup
4.) Flash the mod
5.) Reboot
Recovery
If you encounter any issues (e.g. bootloop) or just want to remove the mod, go into recovery and restore just the System partition from the backup you made earlier (this will preserve your Data partition).
After Installation
After installing, you'll get a notification to enable Voice Wakeup and to train your voice. You can do this now or skip it. It can always be setup later by going to:
CM11: Settings --> Voice Wakeup --> Retrain your voice
CM12: Settings --> Language & Input --> Voice Wakeup --> Retrain your voice
Also...
1.) Go into the Google Now settings and disable "OK Google" detection settings.
2.) Disable your lockscreen if on CM11S or CM12S...other CM11/CM12 based ROMs should work fine since the apk is signed correctly. Some users have reported being able to use a 3rd party lockscreen (e.g AcDisplay) as a work around for CM11S.
If something is not working for you, I need the following or I can't help...
- The ROM you're using (date/version too)
- The kernel you're using (date/version too)
- A description of the problem
- A logcat of the problem in action
Changelog
Code:
[I]4-14-2015[/I]
- New test version for CM12 based ROMs. I believe this should work with most kernels.
[I]Version 2.0[/I]
- CM11 based ROMs only
- Updated mixer_paths.xml with more recent version from CM11
- Deodexed, signed, and zip aligned VoiceWakeup.apk. The app can now bypass the lockscreen on CM11 based ROMs
Disabling the lockscreen is still necessary for CM11S ROMs because those keys aren't public
- Added a "loud" version. It increases the microphone volume levels to make it more sensitive
[I]Version 1.0[/I]
- Initial Release

Woow. It seems working flawlessly

me wanty. Hopefully you can post a how to in the near future

Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
Transmitted via Bacon

jojo_whit3 said:
I bought the OnePlus One in August because I was interested in the always on listening feature that they showed off back in the Spring. So when I actually received the phone, I was pretty disappointed to learn that they took the feature out before shipping. Over the past couple weeks, I've been working on a way to get this feature back in the phone and I think I finally got it working pretty well. I've only tested it on the 25R and 33R builds, but it should work on most ROMs for this phone. The mod uses the always on low power core, so there's no significant drop in battery life. I know Qualcomm has some licenses for this IP, so I'm still trying to figure out if I can legally post the mod here. But in the meantime, here's a demo of it working...
Click to expand...
Click to collapse
Just curious, would this mod stop ota updates and if so is it easily reversible? Looks really nice.
Sent from my A0001 using Tapatalk

share it pls!

Overdose1986 said:
share it pls!
Click to expand...
Click to collapse
Did you read the OP?
I know Qualcomm has some licenses for this IP, so I'm still trying to figure out if I can legally post the mod here.
Click to expand...
Click to collapse
Transmitted via Bacon

looks cool, do keep us updated if you are able to share this "legally" or can you pm me the "not so legal" way? LOL

I didn't know I wanted this until now

That looks awesome

I've been trying to contact someone from the Cyanogen team to get some more information about posting this. If anyone has any contact info, either send me a PM or send them over to this thread.
To give a little more information about this mod, its essentially a port of the VoiceWakeup.apk I found here. If you use apktool to disassemble this file, it's easy to tell it came directly from Qualcomm. However, if the Cyanogen team intended to release this apk with the phone initially, then I'm assuming they already have some agreement in place with Qualcomm. So hopefully that also means it'll be ok for me to post this mod in the near future.

26.2man said:
Just curious, would this mod stop ota updates and if so is it easily reversible? Looks really nice.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
You would still be able to download the OTA updates, but you wouldn't be able to apply them since there would be changes to your file system. If you make a nandroid backup in recovery, then anything is easily reversible.

Thanks. Hope you can release this soon.
Sent from my A0001 using Tapatalk

Looks great, wonder if the cm team is working to make it work by choosing you own wake up command. Had it on my find 7a and saying snapdragon was strange

If it's already freely available then it's unlikely to cause any more issues, depends on what did you do to"port" it I guess.
All the cm11s apps have been made available, so if it came from an existing rom I can't really see much of an issue. But I'm not a lawyer
Alternative is to post a walkthrough of your changes to the original.
Sent from my A0001 using Tapatalk

Awesome work, hopefully you're and to post it up for us eventually.

Hi Everyone...I did a little thread cleaning. Please, lets not harass the OP about when this will be released. Like everything else on xda, it will be released when the developer is ready. Just as a reminder to everyone,
yes this is a hackers site, but certain things are not allowed. If the OP wants to make sure that he isn't violating CMs or Qualcomm's Intellectual Property then we should let him do this to his own satisfaction. Nobody
wants to see a modification removed because CM or Qualcomm complained.
Thanks!

This looks really good! Would love to have this feature, keep it up man

If you're worried about posting the modded APK and the IP issues, can you at least let us know what you modded so we can do it on our own?

had a quick play with it earlier,
Cm 11 nightly contains the background libs (except liblisten.so) but there's some java calls missing. Curious that cm have left most of the libs in place.

lollipop/kitkat versions of Low Lying Fruit Kernel (LLFK) for N915T

(6/30/15) Newest LLFK for T-Mobile Note EDGE N915T Lollipop.
Now has TCP congestion control options with default TCP Westwood
This version is flashable using TWRP.
Features:
SELinux=Permissive option
init.d support
adbd insecure
TCP congestion controls: TCP options include Westwood, cubic, reno among others: default is Westwood
Modifications that need to be made when using LLFK kernel
1)In build.prop set
ro.securestorage.support=false
2)For those that use AllShare Cast you will need to do two things.
First, add the following line at the end of build.prop
wlan.wfd.hdcp=disable
second, you need to have the Xposed module Wanum Xposed installed. In Wanum select "security hacks" then check box of Fake system status
Download link:
https://www.dropbox.com/s/6bg9l8qqcmmh83x/llfk_permissive_initd_adbd_tcp_lpop.zip?dl=0
Check below for other information that might come in handy and good luck!
(06/11/15)New Low Lying Fruit Kernel (LLFK) for Tmobile Note Edge (lollipop)
I've added adb insecure to kernel. This gives you root access to modify /system on phone from a pc
Features:
SELinux = Permissive option
init.d support
adb insecure
download link
https://www.dropbox.com/s/kr7xb22449p497w/llfk_permissive_initd_adbd_lpop.zip?dl=0
(06/10/15) Low Lying Fruit Kernel (LLFK) for Tmobile Note Edge (N915T)
Two new flashable kernels. One for Lollipop the other for Kitkat.
Lollipop: This new version has init.d support so, for example, you can write scripts that run on boot up. (more below).
Features:
SELinux = Permissive option
init.d support
https://www.dropbox.com/s/k8w423ecoj1covs/llfk_permissive_initd_lpop.zip?dl=0
Kitkat:This version now has TCP congestion control options available (e.g. Westwood)
Features:
SELinux = Permissive option
init.d support
adb insecure (allows you to have r/w access to phone's /system from you pc)
TCP congestion control options
Thanks to JT man for testing
https://www.dropbox.com/s/jbifzsuztb73wpg/llfk_permissive_initd_adbd_tcp_kkat.zip?dl=0
Example of init.d script to automatically set SELinux=permissive given here
https://forums.oneplus.net/threads/how-to-selinux-permissive.314120/
couple notes on how-to-selinux-permissive
1)You only need have permissions of /sys/fs/selinux/enforce set to 644
2)Make sure permission of init.d script is 775
One more thing, knox based warnings can be silenced using wanum.
(05/27/15) Low Lying Fruit Kernel (LLFK) for Tmobile Note Edge (N915T) running Lollipop.
For those that miss having SELinux=Permissive on their T-mobile Note Edge running lollipop, here is a kernel
that supports this setting. The kernel is based on the Tmobile Note Edge Lollipop source code. The only thing that was
changed was a setting in the kernel's Makefile to allow the user to choose whether they want to have SELinux=Permissive
as described for the previous Kitkat version of LLFK below.
NOTE: This time around, the kernel is packaged as a zip file than can be directly flashed in recovery.
But before I go any further I need to give credit to @TEKHD for providing a zipped
version of the T-Mobile kernel I could modify and, in addition, for testing it.
Please buy him a well deserved cup of coffee!
Once you have flashed the kernel and rebooted you are ready to set SELinux=permissive by opening a terminal and typing
su
and
setenforce 0
To check it worked, go to settings > About device and you should see, under SE for Android status, that it is now set to Permissive.
An alternative way to change the setting with this kernel is to use the apk SeLinuxModeChanger. Unfortunately this apk is no longer
available at the play store but you can still download it from the F-Droid site.
https://f-droid.org/repository/browse/?fdfilter=selinuxmodechanger&fdid=com.mrbimc.selinux
A third option would be to set up an init.d script if your rom permits it.
I must admit, at the time of this writing, I'm still on KitKat and have yet to try this on my phone. I'll be checking out lollipop soon
but till then, let me know if/how it works. If successful I'll start adding a few more low lying fruit I've picked!
Remember to do a full nandroid back-up before trying this so your phone can return to its original state before trying llfk if needed.
The usual disclaimer applies!
Good Luck!
lollipop LLFK download link:
WAIT! Only one person has tried this version and although it worked for him, I still consider it beta at best. You have been warned!
WAIT! WAIT! One more thing: You need to do the following otherwise you may experience problems with WIFI:
Download the apk BuildProp Editor and use it to set
ro.securestorage.support=false (thanks @TEKHD for checking this)
WAIT! WAIT! WAIT! May be an issue with private mode not working (see http://forum.xda-developers.com/showpost.php?p=61033627&postcount=109 ). I did not have this problem on kitkit. I am unable to test till next week so if someone can check it out that would be great.
http://www.4shared.com/zip/Z8g1u3FHba/llfk_permissive_lpop.html
dropbox link
https://www.dropbox.com/s/ud84t2fc3n9sqdg/llfk_permissive_lpop.zip?dl=0
Below only applies to the KitKat version.
(04/07/15) Update:
Well, I had a little time and decided to add a feature to LLFK. So for now it has the following three capabilities.
1)Allows you to set SELinux = Permissive
2)adb insecure
3)init.d support
Here is the link for the tar file. (follow same instructions given below to install via ODIN):
http://www.4shared.com/archive/2PepSJcPce/llfk_permissive_initd_adbtar.html
Let me know if/how it works...
New features:
The kernel is now adb insecure. This was accomplished by replacing the adbd file in ramdisk with one due to @freeza. Big thanks to him (as in buy him a cup of coffee!) for giving me permission to use it. With adb insecure you can now remount system as r/w from your pc which can come in handy at times.
The kernel has init.d support (Allows you to run scripts from boot) by modifying the ramdisk using the instructions in STEP 1 (Making kernel ready) of the following post
http://forum.xda-developers.com/showthread.php?t=2287540
So this part is done for LLFK
For it to work, the user still needs to make some minor modifications (add a file and create a directory) in their rom. To do this, please follow all 4 parts of STEP 2 (Making Rom Ready) in the same post.
Once you have completed STEP 2 you are ready to try some scripts.
You can search the Internet for init.d scripts to try.
For example there are some init.d scripts in the later half of the following post to give you an idea.
http://en.miui.com/thread-5685-1-1.html
If folks can experiment to see what scripts work I will make a list and post it here.
Seems to work OK on Hyperdrive and Lab Rats (let me know otherwise).
CAVEAT: When testing whether init.d support was successfully implemented I had tried some scripts (like echo "2048" > /sys/devices/virtual/bdi/179:0/read_ahead_kb; ) that should have modified some kernel settings at boot up. But as it turns out there are a set of scripts that run after boot up that supersede these settings. These scripts are in the file /etc/init.qcom.post_boot.sh. (some other neat stuff to play around with in there!) If you want those scripts to not take effect you can simply comment them out and then your init.d scripts will work.
The usual disclaimer and Good Luck
Original post 1/30/15
**********************************************************************************************************************************************************************
Hi. I thought I'd give out this kernel which allows one to set SELinux=permissive for a rooted T-Mobile Note Edge with base NK3. This setting is needed if you would like to run Linux on Android and, I believe Viper4Android if you are so inclined, as well as some other specialized apps (for future reference, let me know what apps you use that need this setting). Once you have loaded this kernel you can use the app SELinuxModeChanger, found in the play store, to set SELinux=Permissive and back to Enforcing. Note, this setting is maintained until you change it back in the app (rebooting will not change the setting). Anyways, what I am providing is a gzipped tar file that you can download, gunzip and then load on your phone using ODIN (version 3.07 worked fine for me, goes in PDA). Remember, this kernel is ONLY for the T-Mobile N915T NK3 rom. Actually, I have only tested it on the Lab Rats rom so hopefully it will work on other roms for T-Moble N915T with NK3 base.
As most folks like to have a name for their kernel I've decided to call this the "Low Lying Fruit Kernel" (LLFK) because it only has a minor change made to it. Indeed this kernel is about as low as it goes (lol) as not a single line of code is changed. I only changed an option in the Makefile from true to false. Details are given at the following github site.
https://github.com/mscion/Permissive-Kernel-N915T-EDGE/
Anyways, I've been using this kernel for over 10 days with no problems, but, of course , for those that try LLFK, the usual warnings apply! I am not responisble for anything that happens to your device as a conseqence of
using this kernel. Indeed you have to be crazy to try it as I have zero experience at this! You also might want to read this before you try setting SELinux=permissive:
http://en.wikipedia.org/wiki/Security-Enhanced_Linux
One more thing, while my preference is that an experienced dev make a kernel worthy of the N915T EDGE, I am open to suggestions to make some more modifications assuming the request are somewhat consistent with the philosophy of LLFK.
Thanks to @jimmydene84 for boot.img and @deeznutz1977 for testing!
Don't forget to do a full back up! Good luck!
Kernel Download link: For SELinux=Permissve option only
http://www.4shared.com/archive/oH5fE053ba/llfk_permissivetar.html

Hey that you that working. I was wondering if there was anyway you would make/try to make the same type of mod/kernel for the sprint version. N915P I believe it is. I will be more than willing to help anyway I can.
The reason I need SELinux to permissive is because to use certain bluetooth controller mapping apps u need it on permissive. Specifically the OG Moga Pocket, that controller only works with the pivot app. In order to have android pick it up as a hid controller, I need the app I use to access linux. I really hate to ask but it looks like there's very limited dev for sprint ?

VenpaCasa said:
Hey that you that working. I was wondering if there was anyway you would make/try to make the same type of mod/kernel for the sprint version. N915P I believe it is. I will be more than willing to help anyway I can.
The reason I need SELinux to permissive is because to use certain bluetooth controller mapping apps u need it on permissive. Specifically the OG Moga Pocket, that controller only works with the pivot app. In order to have android pick it up as a hid controller, I need the app I use to access linux. I really hate to ask but it looks like there's very limited dev for sprint ?
Click to expand...
Click to collapse
Ok, As long as you are willing to test it! Presumably no harm will be done as long as you do a full nandroid back up. Give me a few days to gather files and such...

Awesome @mscion

deeznutz1977 said:
Awesome @mscion
Click to expand...
Click to collapse
Thanks! What would be even more awesome is if someone tries it and it works! lol.

I'll flash it now kind sir

mscion said:
Ok, As long as you are willing to test it! Presumably no harm will be done as long as you do a full nandroid back up. Give me a few days to gather files and such...
Click to expand...
Click to collapse
Omg dude if ur really serious, hell yeah I'm willing to test. I'm extremely greatful n lost for words right now. Thanks so much for just attempting ?? at least. Made my day lol

deeznutz1977 said:
I'll flash it now kind sir
Click to expand...
Click to collapse
I hope you mean Odin it! Drum roll please....

mscion said:
I hope you mean Odin it! Drum roll please....
Click to expand...
Click to collapse
kernel is not se android enforcing

@mscion you still had to use the selinux changer app correct?

deeznutz1977 said:
kernel is not se android enforcing
Click to expand...
Click to collapse
Hi @deeznutz1977. Depending on rom, I think when you boot up you will get that message. Please check in settings > about device and see what SE for android is showing. For now I have pulled the kernel because I unwittingly used the boot.img from lab rats rom to pack in my zImage file that allows permissive setting, cause I thought it was not modded. I am currently waiting to hear from @jimmydene84...

deeznutz1977 said:
@mscion you still had to use the selinux changer app correct?
Click to expand...
Click to collapse
Yes. Check the OP for more details. Once you have installed this kernel, you have the option to turn permissive on or off with this app. You should also be able to set it from command line as well. May I ask which rom are you using? Also, as I just mentioned I need to check with jimmydene84 about his boot.img...

mscion said:
Yes. Check the OP for more details. Once you have installed this kernel, you have the option to turn permissive on or off with this app. You should also be able to set it from command line as well. May I ask which rom are you using? Also, as I just mentioned I need to check with jimmydene84 about his boot.img...
Click to expand...
Click to collapse
Stock deodexed. And sorry about not reading the op. Don't you know that all of the cool people don't read ops
Sent from my SM-N915T using Tapatalk

@mscion I asked jimmydene to pm you ...

deeznutz1977 said:
@mscion I asked jimmydene to pm you ...
Click to expand...
Click to collapse
Thanks very much! We're all good. I'm putting the link back up shortly.

Got excited for a minute I thought deeznutz1977 said he flashed on a Sprint Note Edge. Had to read it over a couple times.

VenpaCasa said:
Got excited for a minute I thought deeznutz1977 said he flashed on a Sprint Note Edge. Had to read it over a couple times.
Click to expand...
Click to collapse
Almost there. It appears to have compiled fine. I need to download the sprint rom and extract its boot.img file so I can pack the file for you to odin. Maybe this afternoon...
I will use the sprint deodexed version NK1, to extract boot.img from, that @snovvman has posted in the sprint developers thread. (hope that is ok! EDIT: We're good!)

mscion said:
Almost there. It appears to have compiled fine. I need to download the sprint rom and extract its boot.img file so I can pack the file for you to odin. Maybe this afternoon...
I will use the sprint deodexed version NK1, to extract boot.img from, that @snovvman has posted in the sprint developers thread. (hope that is ok! EDIT: We're good!)
Click to expand...
Click to collapse
Honestly your awesome. I was starting to regret my purchase too. I'll assume you weren't asking me if it's ok but if you were, yeah that's fine. I'm actually any using that ROM
EDIT: Just saw your edit n thanks (to both) that's so awesome! I owe you guys!

When ubr done are you going to post here or a new thread?

VenpaCasa said:
When ubr done are you going to post here or a new thread?
Click to expand...
Click to collapse
Just pm'd you with link. If it works I'll post it in this thread.

[ROM][7.1][NOUGAT][TESTING] CyanogenMod14.1-cohaolain [UNOFFICIAL]

Hey guys!
To prevent the other CM14.1 thread from getting too crowded I'll be putting my own builds up here
These builds will be based on the official source except I'll keep adding in new features and fixes before they're officially merged, and I'll be putting in some other small changes along the way if I feel they improve the experience without compromising on anything else
Currently working:
//All battery status indicators are fixed
//Pocket mode
Modifications:
//'Unofficial' tag removed from CyanogenMod version. It just made me squirm with the lack of aesthetic. Of course this is still an unofficial version!
Updated (//): 16.11.03
Download link: https://drive.google.com/open?id=0B88aOagl9VcCV3YtNFpwRzR1akk
Credit of course goes to CyanogenMod and all of its contributors for all of their work!
Disclaimer:
This software is provided by me "as is" and "with all faults." I make no representations or warranties of any kind concerning the safety, suitability, lack of viruses, inaccuracies, typographical errors, or other harmful components of this software. There are inherent dangers in the use of any software, and you are solely responsible for determining whether this software is compatible with your equipment and other software installed on your equipment. You are also solely responsible for the protection of your equipment and backup of your data, and I will not be liable for any damages you may suffer in connection with using, modifying, or distributing this software.
XDA:DevDB Information
CyanogenMod14.1-cohaolain, ROM for the OnePlus 3
Contributors
cohaolain
Source Code: https://github.com/cohaolain
ROM OS Version: 7.x Nougat
Version Information
Status: No Longer Updated
Current Beta Version: 7.1 (CM14.1)
Beta Release Date: 2016-11-04
Created 2016-10-31
Last Updated 2016-11-12

First...!!
Will definitely try it out.
Peace

Call Echo and no audio in video chat apps fixed ?
Two things that not allowing me to return to 7.1
Thanks for building and sharing your builds.
Btw are you open to suggestions or requests?

Nice work!
Can you remove cm setup wizard? Cos I'm a Chinese, and if I flash gapps, I can't pass it. And set selinux to permissive?
Thinks a lot!

silentvisitor said:
Call Echo and no audio in video chat apps fixed ?
Two things that not allowing me to return to 7.1
Thanks for building and sharing your builds.
Btw are you open to suggestions or requests?
Click to expand...
Click to collapse
In my testing I haven't experienced any call echo. And I can't test video chat apps right now, so you'd have to check for that yourself mate, or wait for someone else to let you know here, sorry about that
No problem anyway mate, I'm only doing this on a learning curve. That said, I'm open to suggestions and requests, but they should be submitted without much expectation. This is my first ROM, and I'm pretty new to Android development. I can try my best, but I'm no expert. Although I do love a challenge, I can't make any guarantees
But for now I'm going to try and get Google Assistant working by default. We'll see after that

Great! When I have time I'll definitely give it a try.
Sent from my iPod touch using Tapatalk

revive111 said:
Nice work!
Can you remove cm setup wizard? Cos I'm a Chinese, and if I flash gapps, I can't pass it. And set selinux to permissive?
Thinks a lot!
Click to expand...
Click to collapse
Sorry mate, but I don't want to make such drastic changes, particularly ones that most people don't need
I think the setup wizard should stay, and that selinux is fine just the way it is.
Also, I'm not completely sure how to do either of these things anyway....

Can you include your personal Github sources such as device and kernel tree in the 1st post to actually see what changes you've done so far at the moment?

cohaolain said:
Sorry mate, but I don't want to make such drastic changes, particularly ones that most people don't need
I think the setup wizard should stay, and that selinux is fine just the way it is.
Also, I'm not completely sure how to do either of these things anyway....
Click to expand...
Click to collapse
OK,fine.
In cm13, I can pass it without anything, just wait cm to fix this bug.

Thanks for this! :good:

saayuj98 said:
Can you include your personal Github sources such as device and kernel tree in the 1st post to actually see what changes you've done so far at the moment?
Click to expand...
Click to collapse
As soon as I've learned how to do that, I will do that.

If somebody could help me with this it'd be appreciated:
When ro.product.model=Pixel XL is added, 'Device model' in settings>about phone changes to Pixel XL, but when it's removed completely, it reverts back to ONEPLUS A300*.
Question is, when building, how can I make it skip checking the build.prop for the device name and just make it select the device name it defaults to when it's not specified in the build.prop, and where is this check located in source?
Thanks,
Ciarán

cohaolain said:
If somebody could help me with this it'd be appreciated:
When ro.product.model=Pixel XL is added, 'Device model' in settings>about phone changes to Pixel XL, but when it's removed completely, it reverts back to ONEPLUS A300*.
Question is, when building, how can I make it skip checking the build.prop for the device name and just make it select the device name it defaults to when it's not specified in the build.prop, and where is this check located in source?
Thanks,
Ciarán
Click to expand...
Click to collapse
I think its not possible( maybe I'm wrong in here) to change device model when you're building as it might create errors during build process. You might need to create a separate bash script I believe, for users to change that afterwards while flashing the ROM. Or create an Aroma Installer to give user an option to do that if he/she wants to.

which gapps should i flash opengapps 7.1 nano or opengapps 7.1 pico ?

Ashish Bhalla said:
which gapps should i flash opengapps 7.1 nano or opengapps 7.1 pico ?
Click to expand...
Click to collapse
I use pico gapps everytime(I like my system being less bloated). Nano is a good option too.
I suggest you to go with Nano.

Ashish Bhalla said:
which gapps should i flash opengapps 7.1 nano or opengapps 7.1 pico ?
Click to expand...
Click to collapse
I recommend pico, but nano is fine if you don't want Google Now, or Now on Tap, or Assistant and stuff.

saayuj98 said:
I think its not possible( maybe I'm wrong in here) to change device model when you're building as it might create errors during build process. You might need to create a separate bash script I believe, for users to change that afterwards while flashing the ROM. Or create an Aroma Installer to give user an option to do that if he/she wants to.
Click to expand...
Click to collapse
Possibly yeah.
I ran a build that included the two lines to enable Google Assistant, it just ended up discarding the Pixel XL line like it had never been put in there at all.
Google Assistant ran fine for a while, until I cleared Google''s data. Assistant comes up straight after the wipe, but goes back to Now on Tap again afterwards.

Can i install aroma installer open gapps 7.1 on this? If yes how.. I flashed it on this rom but then on booting google services are crashing continuously play store is also not opening.. So some can help plz on this?

cohaolain said:
Possibly yeah.
I ran a build that included the two lines to enable Google Assistant, it just ended up discarding the Pixel XL line like it had never been put in there at all.
Google Assistant ran fine for a while, until I cleared Google''s data. Assistant comes up straight after the wipe, but goes back to Now on Tap again afterwards.
Click to expand...
Click to collapse
Maybe init.d
---------- Post added at 04:42 PM ---------- Previous post was at 04:40 PM ----------
cohaolain said:
In my testing I haven't experienced any call echo. And I can't test video chat apps right now, so you'd have to check for that yourself mate, or wait for someone else to let you know here, sorry about that
No problem anyway mate, I'm only doing this on a learning curve. That said, I'm open to suggestions and requests, but they should be submitted without much expectation. This is my first ROM, and I'm pretty new to Android development. I can try my best, but I'm no expert. Although I do love a challenge, I can't make any guarantees
But for now I'm going to try and get Google Assistant working by default. We'll see after that
Click to expand...
Click to collapse
Really impressed by your overall response.
You can be a great developer one day. Humility, curiosity and simplicity are hallmarks.
Good luck :good:

ankushgautam said:
Can i install aroma installer open gapps 7.1 on this? If yes how.. I flashed it on this rom but then on booting google services are crashing continuously play store is also not opening.. So some can help plz on this?
Click to expand...
Click to collapse
I've read abouyt some bugs with the Aroma installer in 14.1. I'm not even sure if this is a CM problem or a Gapps problem, but for now, stick with pico or something pre-packaged if you can
silentvisitor said:
Really impressed by your overall response.
You can be a great developer one day. Humility, curiosity and simplicity are hallmarks.
Good luck :good:
Click to expand...
Click to collapse
Thanks mate Maybe, maybe . Gotta finish school first!
init.d, hm. Mysterious to me. I've heard tell of it many times but never learned too much about it. Better start reading up

Internal Mic on Joying nonresponsive after noob meddling

While attempting to log in to my unit using ADB over wifi, I grew frustrated as I would get an "error:device offline" after 30s to a minute of being connected. this didn't give me enough time to put in many commands. i would use adb-killserver and disconnect and turn back on wifi on the device, which would let it work for another 30 seconds.
I was able to use a root zip on xda that had these instructions (because it was just one command so I was able to run it in Adb in time)
How-To install:
1. You need a Windows PC that is connected to the same WiFi network as your HU.
2. Unzip the attached file somewhere to your disk.
3. Run CMD.exe as Administrator
4. Change directory to the folder that you unzipped.
5. Run the install.bat script with an IP address of your HU as a parameter:
C:\Users\<username>\Downloads\Joying_JY-UL135N2_SuperSU> install.bat 192.168.123.137
6. Wait until script finishes and reboot your Head Unit.
7. DONE!
I next wanted to install the steeringwheelcontrol/nokill mod on xda, and since i saw an install.bat in the zip, attempted to use adb in the same way
It ran and I believe sucessfully installed portions including nokill. But now my microphone doesnt work at all (this may do with the surfer63 TTS mod included in the no kill? Any clue how to get my microphone working again (internal mic) without doing a hard reset on the whole device?
Anyone with any advice on A) how to cure my ADB issues and be

juandhi said:
I next wanted to install the steeringwheelcontrol/nokill mod on xda, and since i saw an install.bat in the zip, attempted to use adb in the same way
It ran and I believe sucessfully installed portions including nokill. But now my microphone doesnt work at all (this may do with the surfer63 TTS mod included in the no kill? Any clue how to get my microphone working again (internal mic) without doing a hard reset on the whole device?
Anyone with any advice on A) how to cure my ADB issues and be
Click to expand...
Click to collapse
Your device being offline: The WiFi can be unstable after sleep mode. Simply reboot your head unit before adb connections//actions and the connection will be fine again.
The fact that the microphone doesn't work has in principal nothing to do with the modded apk as it works correctly for "the rest of us".
However, you nowhere mention which ROM version you are using and which apk version you used and from where. By now there are 3 "latest" versions.
Please be specific when reporting errors, even better: mention it in your signature.
Finally: the root script version, incl. the binaries/libs, you are using is outdated. Better use the one from my signature.

You're absolutely right the root zip I was using was this one :https://mega.nz/#!MdVlEJLI!KQxP31F2dvXAJ-RNUsiSx9T5Xn5r6bn6hjevR_5bTB0
and I was attempting to install version 4 of the steering wheel control mod found here https://forum.xda-developers.com/an...-units/joying-2gb-steering-wheel-key-t3543390
thanks for any help you can provide in getting my mix working again

juandhi said:
You're absolutely right the root zip I was using was this one :https://mega.nz/#!MdVlEJLI!KQxP31F2dvXAJ-RNUsiSx9T5Xn5r6bn6hjevR_5bTB0
and I was attempting to install version 4 of the steering wheel control mod found here https://forum.xda-developers.com/an...-units/joying-2gb-steering-wheel-key-t3543390
thanks for any help you can provide in getting my mix working again
Click to expand...
Click to collapse
you still don't mention which ROM version you are on. The version of the modded sofia server is also dependent on the ROM version.

surfer63 said:
you still don't mention which ROM version you are on. The version of the modded sofia server is also dependent on the ROM version.
Click to expand...
Click to collapse
my apologies, latest stock rom for mtcd (March 28)

bumperoo

is V3.0 compatible with 20170328?
surfer63 said:
Your device being offline: The WiFi can be unstable after sleep mode. Simply reboot your head unit before adb connections//actions and the connection will be fine again.
The fact that the microphone doesn't work has in principal nothing to do with the modded apk as it works correctly for "the rest of us".
However, you nowhere mention which ROM version you are using and which apk version you used and from where. By now there are 3 "latest" versions.
Please be specific when reporting errors, even better: mention it in your signature.
Finally: the root script version, incl. the binaries/libs, you are using is outdated. Better use the one from my signature.
Click to expand...
Click to collapse
I have not updated from 20170222. I used V2.0. I am considering updating to 20170328 and wanted to make sure that V3.0 was compatible (says build from 20170314).
I appreciate all your hard work, but could not find a donate button to buy you a beverage.

juandhi said:
my apologies, latest stock rom for mtcd (March 28)
Click to expand...
Click to collapse
What? mtcd?
mtcd is NOT intel. I assume you are making a mistake.
You can use the 4.0, the 4.1 and AssassinsLament 4.1 version on that ROM version.
---------- Post added at 06:53 PM ---------- Previous post was at 06:52 PM ----------
Hankafyin said:
I have not updated from 20170222. I used V2.0. I am considering updating to 20170328 and wanted to make sure that V3.0 was compatible (says build from 20170314).
Click to expand...
Click to collapse
Yes, 3.0, 4.0, 4.1 and AssassinsLament 4.1 are all compatible.

surfer63 said:
What? mtcd?
mtcd is NOT intel. I assume you are making a mistake.
You can use the 4.0, the 4.1 and AssassinsLament 4.1 version on that ROM version.
---------- Post added at 06:53 PM ---------- Previous post was at 06:52 PM ----------
Yes, 3.0, 4.0, 4.1 and AssassinsLament 4.1 are all compatible.
Click to expand...
Click to collapse
Thanks, learning as I go. Yes the intel sofia version with the March 28th Rom. Any ideas on if it could be responsible for Mic issues? Thanks in advance.

juandhi said:
Thanks, learning as I go. Yes the intel sofia version with the March 28th Rom. Any ideas on if it could be responsible for Mic issues? Thanks in advance.
Click to expand...
Click to collapse
You have been the only one to have this mic issue, so these mods are not the issue. Hopefully it's not a hardware issue. The only way to make sure it isn't a hardware issue, is to reflash the original joying firmware and see if the mic works. Do not install any mods until you test the mic.