Develop Bugs

[Q] how to turn off vibration of menu/back/home/search buttons ?

Hi,
I don't know if this is possible because I have not found any setting to deactivate this. At least for me is a lil annoying... does anyone know how to do it?
Thanks!

siukeee said:
Hi,
I don't know if this is possible because I have not found any setting to deactivate this. At least for me is a lil annoying... does anyone know how to do it?
Thanks!
Click to expand...
Click to collapse
At the moment you cannot turn off Haptic Feeback for the keys at the bottom of the phone. Motorola says it's a bug. Maybe it'll get unbugged soon.

chmod 0444 /sys/class/timed_output/vibrator/enable
would totally disable the vibrator.

jakiej said:
chmod 0444 /sys/class/timed_output/vibrator/enable
would totally disable the vibrator.
Click to expand...
Click to collapse
What does that mean?

I think if you don't know what it me, you shouldn't try it ^^.

jakiej said:
chmod 0444 /sys/class/timed_output/vibrator/enable
would totally disable the vibrator.
Click to expand...
Click to collapse
It works, thank you, maybe someone can do an app to make this automaticaly.

autostart
fgendorf said:
It works, thank you, maybe someone can do an app to make this automaticaly.
Click to expand...
Click to collapse
one option is to use this with the autostart app.

jakiej said:
one option is to use this with the autostart app.
Click to expand...
Click to collapse
Can someone give more details how can i do that? As i can understand this is a command how can i execute it and how can i put it in startup.

*delete post*
Sent from my Defy

"How to"
In order to turn off keys vibration, you need to
- Have root on your defy (you can use z4root application, use google, download apk, install it)
- Have explorer that is able to view/edit system files (f.e. Super Manager from Android Market, remeber set "use Root" in this app settings)
- Go to the folder /sys/class/timed_output/vibrator/ with f.e. Super Manager
- Create file called "enable", and then change this file atributes (chmod 444 - read, read read) for this file with super managers, and thats all.
Regards.

headblow - your instructions work brilliantly until the phone's rebooted, and then the vibrations come back. Any way to make that stick so it's not reset every time?

Can u plz make an update zip file.
headblow said:
"How to"
In order to turn off keys vibration, you need to
- Have root on your defy (you can use z4root application, use google, download apk, install it)
- Have explorer that is able to view/edit system files (f.e. Super Manager from Android Market, remeber set "use Root" in this app settings)
- Go to the folder /sys/class/timed_output/vibrator/ with f.e. Super Manager
- Create file called "enable", and then change this file atributes (chmod 444 - read, read read) for this file with super managers, and thats all.
Regards.
Click to expand...
Click to collapse
Sent from my MB525 using XDA App

Found a couple of interesting things on another forum:
There's an app someone has cooked up that will make the permission changes to the file for you, so you don't have to hunt around in Super Manager or similar file explorer.
There's no way to make the change permanent, because you're not dealing with a physical file on disk. There's an app called Autostart than runs a script as root on startup though, so adding something like:
chmod 444 /sys/class/timed_output/vibrator/enable
into that script should always turn off vibration on startup. Haven't tried it yet, wife's phone is with her at work.

Worket for me
but how ever here is just temp when i get reboot the vibrate back , but i have a bug the call is to disable vibrations and for the call vibration is neccessary , i wish disable only for the butons

I''m disabling vibrations globally with application Streak Vibrations. Vibrating during unlocking device and button feedback drives me mad.

seukumeama said:
but how ever here is just temp when i get reboot the vibrate back , but i have a bug the call is to disable vibrations and for the call vibration is neccessary , i wish disable only for the butons
Click to expand...
Click to collapse
Hi,
I have a defy (stock 2.1) since some months now ... and I have got the same annoying issue...
Because I found nothing to answer this problem, I coded an app for myself some days ago ... but if it can help someone else ...
However, you must to be root for a full using of it.
This app stops the vibrate totaly (with a 0444 on /sys/class/timed_output/vibrator/enable) but switch it to enable (with a 777) when a call.
The app can be started at boot.
Fits perfectly for my usage ... but I'm aware if you have suggestions to improve it. Sources are shared on a SVN if someone wants them.
(I can post the url later when I have enough rights to post a link on this forum).
(sorry for my english and for the crap icon for the app : I'm not a designer )
EDIT : link for downloading is removed because a topic about VibraFix is created here.

is the problem still present on android 2.2 ?

yes on my defy with official update (Android2.2.2 / 34.164.3.MB525.Retail.en.FR).
I still using my app ^^

Cynyx said:
Hi,
I have a defy (stock 2.1) since some months now ... and I have got the same annoying issue...
Because I found nothing to answer this problem, I coded an app for myself some days ago ... but if it can help someone else ...
However, you must to be root for a full using of it.
This app stops the vibrate totaly (with a 0444 on /sys/class/timed_output/vibrator/enable) but switch it to enable (with a 777) when a call.
The app can be started at boot.
Fits perfectly for my usage ... but I'm aware if you have suggestions to improve it. Sources are shared on a SVN if someone wants them.
(I can post the url later when I have enough rights to post a link on this forum).
(sorry for my english and for the crap icon for the app : I'm not a designer )
Click to expand...
Click to collapse
Freakin' awesome! I've been trying to get the haptic to stop. This worked perfectly. Maybe you should post it in the apps thread, and/or Market? Or is it there? Either way thanks so much!

bobbyphoenix said:
Freakin' awesome! I've been trying to get the haptic to stop. This worked perfectly.
Click to expand...
Click to collapse
Nice this app can help you.. Thanks for your feedback.
bobbyphoenix said:
Maybe you should post it in the apps thread,
Click to expand...
Click to collapse
It's more a fix than a real app ... and why duplicate threads ? The fix answers the question imho.
bobbyphoenix said:
and/or Market?
Click to expand...
Click to collapse
Nope. I think I will not pay for publishing a fix for the Defy ...
The only thing I will do one day : change the icon because I don't like it and enable vibrate for SMS/MMS.

[HOWTO] Disable ALL camera sound AND possible fix for battery drain

HOWTO: Disable Camera Sound (completely silent)
Without deleting anything.
Edit: As pointed out by nickbarbs, after you have completed one of the below methods, the Camera sound is controlled via "System Sounds". If you turn up, down, or off the "System Sounds", the Camera sound would be changed respectively.
This means that you can now control the camera sound at will via volume control functions.
METHOD 1
1. Create a file called "local.prop" in /data/ if it doesn't exist. Example: "/data/local.prop"
2. Open the file "/data/local.prop"
3. add the line to the file:
Code:
ro.camera.sound.forced=0
4. Reboot and all sound in the camera app is completely silent.
5. To recover the sound, you can either delete the local.prop file or change the code to:
Code:
ro.camera.sound.forced=1
METHOD 2: ADB
1. unrar the attached file "local.prop.rar"
2. copy the "local.prop" file to your ADB folder
3. ADB push local.prop /data/local.prop
4. Reboot phone.
5. To restore sound, just delete local.prop and reboot
-----
POSSIBLE BATTERY DRAIN FIX
In addition, for those who are having huge battery drains from Android OS, I also had it. On original KDD firmware, no problem at all, but after updating to KE2 with KIES, I had it all afternoon. I did a hard reset, and the battery drain seemed to go away, but I can neither guarantee or give a 100% confirmation (considering the fact that the Android OS battery usage is based on %, so if I constantly use the phone, Display goes up to 54% and Android OS drops to 10%)
Did a hard reboot by the following method:
WARNING: Will delete apps and all data; phone will boot like new phone.
1. Make sure phone is root first if you want root, and both SU and BUSYBOX installed
2. Shut down phone
3. Hold on the "UP" and "HOME" key, and press the "POWER" button for 2-3 seconds to turn on the phone (make sure to release the "POWER" key after the phone turns on, but continue holding "UP" and "HOME")
4. Select "wipe data/factory reset" and then "wipe cache partition" to remove both.
5. "Reboot system"
6. Once phone has rebooted, Root stays if properly installed, and phone starts off like new.
7. I have been using the phone since for 7 hours now, and seems better.

still have sound when focusing when taking pictures.

[email protected] said:
still have sound when focusing when taking pictures.
Click to expand...
Click to collapse
It needs to be disabled within Camera.apk
I'll look at that just now then.

Sorry; I live in Hong Kong and posted it at 2am in the morning and made a typo. It should be:
ro.camera.sound.forced=0
Will correct original post now.

kohiiou said:
Sorry; I live in Hong Kong and posted it at 2am in the morning and made a typo. It should be:
ro.camera.sound.forced=0
Will correct original post now.
Click to expand...
Click to collapse
Still not working...

mrfreddan said:
Still not working...
Click to expand...
Click to collapse
Did you reboot your phone? The changes doesn't persist till after a hard reboot.
Make sure it's also in:
/data/local.prop
And not
/data/data/local.prop
Double check to make sure you have it in the right place too and for example NOT in /sdcard/data/local.prop.

YES!! works great for me! not only that - but it follows the setting of you phone therefore
- Phone silenced = NO Camera sound at all (focus OR snap)
-Phone sound on = Camera sound with Focus AND snap
Thanks a lot dude. finally.
cheers
nick

by the way i extracted your .Rar file to my phone's SD card from my windows machine. Then i copied the file with Root Explorer to /data
= Profit

nickbarbs said:
YES!! works great for me! not only that - but it follows the setting of you phone therefore
- Phone silenced = NO Camera sound at all (focus OR snap)
-Phone sound on = Camera sound with Focus AND snap
Thanks a lot dude. finally.
cheers
nick
Click to expand...
Click to collapse
Confirmed - it's now related to the system volume.

Is possible to create tweak which enable digital zoom while recording 1080p video? Yeah, I know it is digital zoom but sometimes it would be usefull. Now zoom is possible only with 720p or less.

You need to have root for this, no?
Because I haven't rooted it yet and it doesn't work.

El Salvador said:
You need to have root for this, no?
Because I haven't rooted it yet and it doesn't work.
Click to expand...
Click to collapse
Unfortunately, yes you do.

kohiiou said:
POSSIBLE BATTERY DRAIN FIX
In addition, for those who are having huge battery drains from Android OS, I also had it. On original KDD firmware, no problem at all, but after updating to KE2 with KIES, I had it all afternoon. I did a hard reset, and the battery drain seemed to go away, but I can neither guarantee or give a 100% confirmation (considering the fact that the Android OS battery usage is based on %, so if I constantly use the phone, Display goes up to 54% and Android OS drops to 10%)
Click to expand...
Click to collapse
it works for me too! on KE1 rom, after 8 hours, battery is at 5%!
after hard reset, after 8 hours, i still have 50% battery left!

So far it looks like hard reset fixed my battery life problem too

yep same here hard reset, root still remains, all apps gone, but hey after 9hr used only 25% battery....thanks for the tip....may try the camera trick aswell later...

kohiiou said:
Did you reboot your phone? The changes doesn't persist till after a hard reboot.
Make sure it's also in:
/data/local.prop
And not
/data/data/local.prop
Double check to make sure you have it in the right place too and for example NOT in /sdcard/data/local.prop.
Click to expand...
Click to collapse
When you say hard reboot, do you mean reset back to factory settings or turn phone off completely then turn on again??

sheridan2000 said:
When you say hard reboot, do you mean reset back to factory settings or turn phone off completely then turn on again??
Click to expand...
Click to collapse
The latter - don't confuse hard reboot with hard reset

Summered said:
The latter - don't confuse hard reboot with hard reset
Click to expand...
Click to collapse
Thanks....just pushed the file...thought that it did not work but noticed that you have to turn off all sounds inorder for camera sounds to turn off as well. When sound is on then camera sounds are back.
Great.

works like a charm! both focus and snap sound are now disabled on silent mode. thanks=)

How do you detect if you have the Battery Drain Issue?
Battery Usage stats?

[ROM][CM7] Defy Pro XT560 Support Thread

This is a support thread for the ROM posted here.
http://forum.xda-developers.com/showthread.php?p=49394355
* It is very important to clear factory data/cache after installing the CM7 rom.
* If your stuck on the android boot screen, connect usb and do a logcat to see what it is crashing on.
* The battery_charger has been replaced in this build as a safety backup to get into bootmenu. Anytime the phone is powered off and then plugged in it will boot to bootmenu instead of the charging screen.

* It is very important to clear factory data/cache after installing the CM7 rom.
Click to expand...
Click to collapse
I make all wipe data/cache and even Dalvik cache before and after install CM7 - but I stuck on the android boot screen.
But note: I made all wipes from CWM, because stock recovery is not works on my phone (only green robot and yellow triangle and that's all - nothing key works, only pull battery helps).
* If your stuck on the android boot screen, connect usb and do a logcat to see what it is crashing on.
Click to expand...
Click to collapse
How can I make this (run logcat)?
Thanks for the advices.

Im not sure the clear data/cache works right in CWM. I have not tested it. To access the menu in the stock recovery hit the Home key.
To output a logcat open a command prompt and run "adb logcat"
If you want to output it to a file use "adb logcat > filename.txt"

so there is some querrys:
- torch app does not work as a flashlight, while it stay in status bar and even task killer wont help
- led notification light does not work at all, i guess there is no app for that and original is missing
- it wont unlock sim card, or lock it while it's unlocked. message is "incorrect pin". previously unlocked on other phone sim works fine. pin correct.
- the reboot menu list wont operate with joystick, only touch.
- both cameras wont work in skype, when forced induce crash.
- dev tools options become a force close
- voice dialer started by long press call button opens in wrong screen orientation and does not work. it work if started from all apps.
- superuser does not ask about allowing su permissions, there is no app listed as allowed su perm. while all super su apps works fine as usual.
- yandex maps app issue. rendering map result is quite not what it should be

I did it! Thanks for stock recovery main key (Home) .
And now some my notes (first, I use Russian language and CM7 has it).
- torch app doesn't work - this right for me too;
- about led - not work too;
- about sim - not check this yet;
- the reboot menu OPERATE for me with D-Pad;
- I don't use Skype;
- dev tools work in full for me;
- all correct about voice dialer;
- it's right too;
- don't install yandex maps yet.

wifi is not work

clxer said:
wifi is not work
Click to expand...
Click to collapse
was't been working for me too, but first reboot solved it
a lot of apps that uses the hardware gpu does not work properly, i guess this is same as camera driver problem and it can't be resolved till motorola releases it freely(only if)
also i am having issue with call ringtone - it rings for fraction of a second and then goes silent

I missed some egl librarires in the build, copying the attached files to /system/lib/egl should correct some of the graphic issues.
retr13 said:
was't been working for me too, but first reboot solved it
a lot of apps that uses the hardware gpu does not work properly, i guess this is same as camera driver problem and it can't be resolved till motorola releases it freely(only if)
also i am having issue with call ringtone - it rings for fraction of a second and then goes silent
Click to expand...
Click to collapse

superdave said:
I missed some egl librarires in the build, copying the attached files to /system/lib/egl should correct some of the graphic issues.
Click to expand...
Click to collapse
antutu now running, mx harddecoding on the other hand dont
yandex. maps still weird

Good Job, and thank you
By the way, Pls tell me how to root defy pro.
I had tried many tools but both fail.

jimway said:
By the way, Pls tell me how to root defy pro.
I had tried many tools but both fail.
Click to expand...
Click to collapse
With poot.apk
http: / / ofimatica-programacion[dot]blogspot[dot]com/2014/02/rootear-telefonos-android-sin-necesidad[dot]html

Any updates?
edit- specifically, does CM7 fix the poor bluetooth A2DP quality of the stock ROM?
Sent from my XT560 using xda app-developers app

Viper4Android not working right on stock ROM.

Having a problem with V4A on build .139. I am rooted, have Busybox free installed, and bought SELinux.
I use the stock music app, because I don't know how to sideload the info for other programs. Total newb here, first time rooting. Anyways, as I start the music app, V4A is not active, and I have to go to the EQ settings, then it starts. Then after about 5 min., playing with screen off, it shuts off. I have tried both Normal and Compatible FX settings, Compatible renders the driver useless. I have V4A set to force start, but that does nothing, and I've installed the latest version 3 times now, doing a driver removal, reboot, app removal reboot, redownload, re-install, setup etc. It still happens. Is there something I'm doing wrong. I've disabled the "Music FX" app that comes with the phone that is the basic EQ on the phone, so that's not interfering. I don't know what it could be. Does anyone else have this problem, and how did you solve it?
Much appreciated for the responses.

Check if you are using the Asus auto start manager, allow viper and uncheck cleanup in suspend option.

harpreet.s said:
Check if you are using the Asus auto start manager, allow viper and uncheck cleanup in suspend option.
Click to expand...
Click to collapse
I am using Asus auto start. I did what you said, and I'm running a test now. It would usually run for about 15 min, then shut off. So, I'm doing the 15 min. test, then I'll try the music app shutdown and restart, and see if your suggestion worked. I hope so, it's been driving me nuts all day.:good:

I know, it drove me crazy too. What i did was change something in the "audio.conf" file. You have to erase some lines.
With this, android uses viper audio for everything.
for the audio conf thing look in the sticky posts, thats where i found it

lkzshg said:
I know, it drove me crazy too. What i did was change something in the "audio.conf" file. You have to erase some lines.
With this, android uses viper audio for everything.
for the audio conf thing look in the sticky posts, thats where i found it
Click to expand...
Click to collapse
Well, the 15 min. thing worked out. It seems to run no problem now. But when I shut the music player off, and restart it, I have to Force Stop V4A, then go into the EQ of the music player, then it kicks in.
I'll look for the "audio.conf" file, but how do I implement it, or write it on the phone. I'm not a user of ADB, and frankly, using developer tools scares me, as this is my first time rooting a phone. So, something straightforward would be great.

ZMan2k2 said:
Well, the 15 min. thing worked out. It seems to run no problem now. But when I shut the music player off, and restart it, I have to Force Stop V4A, then go into the EQ of the music player, then it kicks in.
I'll look for the "audio.conf" file, but how do I implement it, or write it on the phone. I'm not a user of ADB, and frankly, using developer tools scares me, as this is my first time rooting a phone. So, something straightforward would be great.
Click to expand...
Click to collapse
Just checked it: the file name is audio_policy.conf on /system/etc/.
Its the 7.2 on this post:
http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
I used a file explorer like "ES File explorer". Just edited the audio_policy.conf to erase the lines of it using the text editor. I dont remember which text editor i used though, i think it was the one built into the es file explorer.
By doing this i dont have to restart V4A anymore. I use spotify app, but i think its the same thing.
just remember to do a backup if anything.

lkzshg said:
Just checked it: the file name is audio_policy.conf on /system/etc/.
Its the 7.2 on this post:
http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
I used a file explorer like "ES File explorer". Just edited the audio_policy.conf to erase the lines of it using the text editor. I dont remember which text editor i used though, i think it was the one built into the es file explorer.
By doing this i dont have to restart V4A anymore. I use spotify app, but i think its the same thing.
just remember to do a backup if anything.
Click to expand...
Click to collapse
Grrrrrr. I downloaded ES File Explorer, but it won't let me erase the lines of code you showed me. It just keeps telling me there's an error. Even though I gave it root access and all, it still won't do anything.

Download Root Browser and set audio_policy.conf rw-rw---
Enviado desde mi ASUS_Z00AD mediante Tapatalk

carloshq said:
Download Root Browser and set audio_policy.conf rw-rw---
Enviado desde mi ASUS_Z00AD mediante Tapatalk
Click to expand...
Click to collapse
Root Browser won't let me edit permissions.
nvm. Didn't give it root access.

Okay, I screwed up. I changed the audio_effects.conf file permissions to rw-rw---, and now I have no sound. What's the correct sequence for that file?

ZMan2k2 said:
Okay, I screwed up. I changed the audio_effects.conf file permissions to rw-rw---, and now I have no sound. What's the correct sequence for that file?
Click to expand...
Click to collapse
I have it on rw- r-- r--

Thanks!

Just checked it: the file name is audio_policy.conf on /system/etc/.
Its the 7.2 on this post:
http://forum.xda-developers.com/zenf...-mode-t3096596
I used a file explorer like "ES File explorer". Just edited the audio_policy.conf to erase the lines of it using the text editor. I dont remember which text editor i used though, i think it was the one built into the es file explorer.
By doing this i dont have to restart V4A anymore. I use spotify app, but i think its the same thing.
just remember to do a backup if anything./QUOTE]
Okay, now im trying to get PowerAmp working, and I've done everything suggested, and V4A refuses to start in it. It would be nice to get it going, as I can use the bluetooth connection in my truck, and I'm sick of the gaps in playback and other failings of the stock player. I've shut down the EQ and tone controls and limiter in PowerAmp, and activated the Music tweaks part of the app. If I long press on it, V4A comes up, but it's not working. Any help would be appreciated.
Click to expand...
Click to collapse

[ROM][AOSP][CM][SafeStrap]Cyanogenmod 11 for SafeStrap with locked bootloaders

[ NO LONGER ACTIVELY BEING DEVELOPED - SORRY, READ THE POSTS FOR INFORMATION ]
Yes, you read that right. What we have here is a semi-functional CM11 (Kit Kat 4.4.4) for those with the locked boot loader using Safe Strap. I have been working on this for about a month, and this is what has come of that work. However, I need some help. I am not Android savvy enough to fix all of these problems to make this a fully functioning phone.
That being said, the phone does boot up and appears to mostly work. At this time, it is not a stable daily driver.
I did search all the threads, and I believe that this is not covered in another thread, so please forgive me if there is another CM11 thread that is for SS users on AT&T's locked boot loader phones. I don't see any.
How I got here:
Well, I wanted Cyanogenmod on my AT&T locked boot loader Safe Strapped phone. Every thread says we can't do that, and I just don't like hearing people tell me we can't do something and not provide any reasons. So I decided to try for myself. For the most part, they are right, but with enough perseverance, anything could happen.
I wanted to still use my phone as my daily driver, so I needed SafeStrap to work without having to bounce between kernels.
I was currently using Safe Strap with the NB1/NC1 kernels, and running Joe-Tech's GPE 4.4.4, so I decided that I should start with a 4.4.4 variant of CM, which lead me to CM11. I tried all of them, the nightlies, the home builds, the official builds, and I stumbled across one particular CM11 nightly (20151115) that would boot and then crash as soon as it booted. So I decided to use that as a base.
Reviewing the situation/logs/errors after each crash, I slowly removed, edited, or replaced something until it would not receive that error and would move on to the next error. By the grace of God it was slowly coming together! Hence why the built in camera app is gone and replaced with open camera, etc.
If we get this working, we may be able to use these hacks or tricks to get higher versions such as CM12 or perhaps (fingers crossed) CM13. I know this is kind of lofty, but perhaps we could get something going here. Once we identify the key problems, perhaps we can also apply these tricks to other AOSP variants, such as Slim Roms.
However, let's stick to putting one foot in front of the other right now and focus on CM11.
The Setup:
AT&T boot loader locked phone with NB1/NC1 kernel and modules flashed.
Safe Strap 3.75, currently using Rom Slot 1 for this, as my daily driver is on the stock slot, however I have done it both ways, and it works either way.
Download the below CM11 zip and put it on your phone.
In Safe Strap, choose stock or rom slot, then wipe and flash the CM11 zip.
After flashing the zip, flash the wifi modules for your kernel.
Once it boots:
Go to the settings->about phone->tap on build to enable developer mode.
Then, in developer menu, choose "Disable HW overlays" to always use GPU for screen compositing. (To improve graphics performance, you may find playing with the other graphics options help also.)
Then disable the lock screen by changing "slide" to "none" (To prevent sleep of death until we fix it.) Thanks @Sterben Pistole
Temporary Root:
Simply open the KingoRoot app and click on the padlock. This will take roughly 3-5 minutes, but it will successfully give you root permissions. After reboot, root permission will be lost, but you can simply open KingoRoot and give yourself root permissions again.
Download link:
http://www.mediafire.com/download/at7iw100uawi74k/CM11-20160322-SS.zip
OR This version, which includes the qcom scripts (testing):
http://www.mediafire.com/download/nb98rtkk2j0vjpa/CM11-20160326-SS.zip
Screenshots:
Boot animationhttp://www.mediafire.com/view/wgn5m57mjk5irvm/IMG_20160310_165320.jpg
Boot animationhttp://www.mediafire.com/view/7k8y591adrwsscw/IMG_20160310_162451.jpg
Settings http://www.mediafire.com/view/lrni6kpw04oi43d/IMG_20160310_165713.jpg
About phone1http://www.mediafire.com/view/8hb8slcwxgqxycl/IMG_20160310_165603.jpg
About phone2http://www.mediafire.com/view/ugra6jdeiz6wro5/IMG_20160310_165610.jpg
Dev. optionshttp://www.mediafire.com/view/qvd2q9uwd2vv8pn/IMG_20160310_165652.jpg
Home screen2http://www.mediafire.com/view/5h9vg4wxaacfpio/IMG_20160310_165742.jpg
Menu screenhttp://www.mediafire.com/view/55bvds7k08b2nkk/IMG_20160310_165548.jpg
Home screen1http://www.mediafire.com/view/qkod20qyyv3fska/IMG_20160310_165449.jpg
Check the following posts for issues and known working items. If you have an idea of how to solve the item, the best thing to do would be to download this CM11 and try it out. If you can't do that, or if you did and found a solution, just post your thoughts/trials/2 cents here in the forum and we can hopefully integrate it into the final product!
Team Members and Contributors: (People who have contributed to the project.)
@Sterben Pistole
@Evant28
Beta testers: @DeadlySin9
Huge special thanks to @jmsq and @Joe-Tech for permission to use things we need from their GPE roms!

Known problems
Here is a list of the Known issues:
SYSTEM:
-USB - MTP, UMS, and PTP are not currently working properly. The PTP may be working, but my Linux computer cannot connect to it. The UMS will not mount. The MTP says the connection is taking too long and resets (on my computer).
-Sleep of Death - Lock screen causes sleep of death and reboot errors. Must disable the lock screen to prevent this. Thanks @Sterben Pistole !
-Mounting external SD card - Currently the extSdCard is mounted, however it requires root privileges to use it.
-SU - Currently, @Sterben Pistole has found a SU temporary work around, however, it is lost on reboot.
-GPS - Not currently functioning.
-APN settings - Since that portion of the settings crashes, I thought we could edit the xml file directly and set a default option for the carrier of choice. Not ideal, but perhaps a good work around?
-TeleService.apk has been removed, it causes too many crashes, this apk is really important for phone calls/radio control, so this would really need to be replaced.
APPS:
-GPS Status - The app works, but GPS does not appear to be functioning.
-Messaging - Crashes when you open it. I think due to settings issue with connectivity to network.
-Settings - Mostly works, a few settings options cause it to crash, most importantly, the mobile network settings for APN's etc. crashes.
-Torch - Torch apk does not function at this time. Found that during CM kernel init, changes are made to facilitate the torch.apk, which are not done by the stock kernel init. However, it is possible that these could be written in as a init.d script.

Known Working
Here is a list of the known working:
SYSTEM:
-ADB - Fully functional.
-Audio - Makes sounds when you tap on buttons, appears to work fine.
-Bluetooth - Fully functional, used it to tether internet to use the browser, worked great.
-Bootlogo - Fully functional.
-Bootup - Boots all the way up the first time.
-Camera - Fully functional.
-External SD Card - Currently mounts, but requires super user privileges to use it.
-Internal Storage - Fully functional.
-Themes - @Sterben Pistole has verrified that different themes work.
-Wifi - Remember to flash your modules in SS! Thanks @Sterben Pistole
APPS:
-Apollo - Works great.
-Browser - Works great when you have an active network connection.
-Calculator - Works great.
-Calendar - Works great.
-Camera - Works great. Thanks @Sterben Pistole
-Clock - Works great.
-CM File Manager - Now working!
-DSP Manager - Appears to work.
-Email - Appears to work.
-Gallery - Works great!
-Movie Studio - Appears to work.
-People - Appears to work.
-Phone - Appears to work, but due to a settings issue with setting the carrier, I could not connect to make a phone call.
-Terminal Emulator - Works great.
-Voice Dialer - App opens, don't know if it works as I did not add my contacts.

Change log
Code:
3/26/16
-New QCOM script testing download link CM11-20160326-SS.zip
-Removed two of the scripts, the BT, and the BTDUN scripts. Those two scripts cause the Bluetooth to fail. Now the bluetooth works just as it did before the scripts were added.
3/24/16
-Alternate CM11-20160324-QCOMSCRIPTS-SS.zip download link
-Our NB1/NC1 kernel will need certain settings, services, and scripts run to be fully functional in regards to the hardware. Our kernel, through init, was calling for several qcom shells that did not exist. They have been added into this zip. Although it does not immediately solve any issues, it may be worth trying some of the things in these scripts, thus the original 20160322 zip is still available for download.
3/22/16
-New CM11-20160322-SS.zip download link
-Removed /recovery, boot.img, and file_context from zip as well as from updater-script. This makes it smaller and quicker to flash to your phone.
-Removed Loki script from installation script, as we do not need it on SS.
3/16/16
-New CM11-20160316-SS.zip download link
-External SD card now is auto mounted to /storage/extSdCard, however, it requires super user permission to use it.
-Dropped UltraExplorer and added ES File Manager for maintenance tools. Not intended for final product.
3/15/16
-New CM11-20160315-SS.zip download link
-Added Kingoroot for simpler one click rooting, root is still temporary.
(We had already achieved temporary root, but it was more complicated to activate than this. Kingoroot can re-root after restarting your phone.)
3/14/16
-New CM11-20160314-SS.zip download link
-Subtle changes in build.prop, fixed model # in about phone.
-Added TowelRoot, UltraExplorer, and Pushbullet for maintenance tools. Not intended for final product.
3/13/16
-New CM11-20160313-SS.zip download link.
-Camera2.apk fixed, open camera removed. Thanks [user=6053184]@Sterben Pistole[/user]
-CM File Manager fixed, removed ES File explorer.
3/12/16
-New CM11-20160312-SS.zip download link.
-WiFi Fixed, be sure to flash the appropriate modules in SS! Thanks [user=6053184]@Sterben Pistole[/user] !
3/11/16
-New CM11-20160311-AKLU-SS.zip download link with fix for internal phone memory "sdcard" mounting with SS.
-Sleep of death and reboot error workaround - Thanks [user=6053184]@Sterben Pistole[/user]
- Disable the lock screen to prevent sleep of death and to allow future reboots. We will want to disable or fix the lock screen function, but the workaround allows us to continue working at this time!
3/10/16
-Uploaded to XDA for assistance from other members and to share what has been done so far.
2/26/16
-Created new boot animation reflecting SS and CM.
2/24/16
-Removed Torch.apk, camera.apk, camera2.apk due to issues.
-Added OpenCamera - works great, and you can choose where to save pics.
-Added /system/lib/modules, but still cannot insmod them, due to no root permission.
-Tried Kingroot, will not root without internet connection, used bluetooth tether, but it did not recognize internet connection, even though browser worked online.
-Tried SuperSU, but it cannot update the binary.
2/23/16
-Removed teleservices.apk from /system/priv-app due to issues.
-Edited build.prop
-Now the crrashing has stopped, however we cannot use data or make phone calls without teleservices.apk. Perhaps we can steal it from another rom?
-Camera app crashes when accessing the camera.
-Settings sometimes crash.
-File manager could not find any storage devices, internal or external. Replacd with ES File Manager and now can see all files in mounted partitions.
-sdcard and extSdCard are not mounted at boot. Write script to do that?
-GPU needed set to no HW overlays in dev. options to prevent graphics errors/tearing.
-Bluetooth tests sat! :)
2/22/16
-Installed CM11 nightly through SS, but it constantly crashes.

I'm going to be experimenting with your build as I've started working on the same type of project as of last week. I'm going to see what I can do to fix a couple of the crashes and report back to you.
EDIT: TO ALL, IF YOU DON'T KNOW WHAT YOU'RE DOING DO NOT INSTALL THIS. IT IS NOT A DAILY DRIVER AT ALL.
EDIT 2: As I suspected, if you go into the settings and disable the lockscreen it won't go into the sleep of death.

Wow, this looks great! I'd love to help with this if I can.

Rebooting works flawlessly if you turn off the lock screen. As for the internal and external storage not mounting properly, you need a wrapper script for that. I think @jmsq made one a while ago, but he's not active anymore.

Sterben Pistole said:
I'm going to be experimenting with your build as I've started working on the same type of project as of last week. I'm going to see what I can do to fix a couple of the crashes and report back to you.
EDIT: TO ALL, IF YOU DON'T KNOW WHAT YOU'RE DOING DO NOT INSTALL THIS. IT IS NOT A DAILY DRIVER AT ALL.
EDIT 2: As I suspected, if you go into the settings and disable the lockscreen it won't go into the sleep of death.
Click to expand...
Click to collapse
Tested, works great! Updated thread! Great work!
Now we should replace or fix the lock screen. At least now we know what the problem was. Great insight!

Evant28 said:
Wow, this looks great! I'd love to help with this if I can.
Click to expand...
Click to collapse
Evant28,
You bet, if you can, download the files and play around with it. Let us know if you find any way to fix anything and we'll put it to work.

Sterben Pistole said:
Rebooting works flawlessly if you turn off the lock screen. As for the internal and external storage not mounting properly, you need a wrapper script for that. I think @jmsq made one a while ago, but he's not active anymore.
Click to expand...
Click to collapse
Great find on the disabled lock screen allowing reboots! I've added it to the instructions after booting up the first time. I am breaking down @jmsq GPE 4.4.3 rom to look at the script. I've also pm'd to ask their permission.

To be fair, some of those people saying it wasn't possible did specify that it would require plenty of work that most people don't want to/can't do. Kitkat probably is the best option since we did get those GPE's working though, and I certainly applaud your efforts. I'm no developer myself or I'd help out, but I think a good way to get some things working since we can't change the kernel is to try and build and load modules for it using bypasslkm. I don't know the viability of that, but I know at least for the storage issue I've seen a case where a module was loaded in order to allow mounting.

*deleted*

DeadlySin9 said:
To be fair, some of those people saying it wasn't possible did specify that it would require plenty of work that most people don't want to/can't do. Kitkat probably is the best option since we did get those GPE's working though, and I certainly applaud your efforts. I'm no developer myself or I'd help out, but I think a good way to get some things working since we can't change the kernel is to try and build and load modules for it using bypasslkm. I don't know the viability of that, but I know at least for the storage issue I've seen a case where a module was loaded in order to allow mounting.
Click to expand...
Click to collapse
Does BypassLKM work on 4.4.2? I know it works on 4.3, because that's what it was built for, but if it does it would definitely help a good bit.

Mounting of sdcard fixed.
DeadlySin9 said:
To be fair, some of those people saying it wasn't possible did specify that it would require plenty of work that most people don't want to/can't do. Kitkat probably is the best option since we did get those GPE's working though, and I certainly applaud your efforts. I'm no developer myself or I'd help out, but I think a good way to get some things working since we can't change the kernel is to try and build and load modules for it using bypasslkm. I don't know the viability of that, but I know at least for the storage issue I've seen a case where a module was loaded in order to allow mounting.
Click to expand...
Click to collapse
Internal phone storage "sdcard" mounting is fixed, new download link in OP. Turns out SS roms use a special sdcard mounting script. Thanks for the suggestions though, we need all the help we can get!

Wow great progress! I'll be installing as soon as I get home. Now that internal storage is fixed does WiFi work?

Evant28 said:
Wow great progress! I'll be installing as soon as I get home. Now that internal storage is fixed does WiFi work?
Click to expand...
Click to collapse
Not at the moment. Even if Wi-Fi was working this would still be far off from being a stable daily driver. I'll post an update if I figure something out.
EDIT: WIFI IS NOW UP AND RUNNING! Modules are needed as always.
EDIT 2: Uploading build with working Wi-Fi as I am typing this. I have slow Wi-Fi so it'll be a while ;-;
EDIT 3: Got root working, but it's not out of the box. You need to flash SU in Safestrap right after modules, download towelroot, make it rain, and then install SU binary's from SU app.
EDIT 4: Root is only temporary. After a reboot it disappears. Also, theme's work great

Sterben Pistole said:
Not at the moment. Even if Wi-Fi was working this would still be far off from being a stable daily driver. I'll post an update if I figure something out.
EDIT: WIFI IS NOW UP AND RUNNING! Modules are needed as always.
EDIT 2: Uploading build with working Wi-Fi as I am typing this. I have slow Wi-Fi so it'll be a while ;-;
EDIT 3: Got root working, but it's not out of the box. You need to flash SU in Safestrap right after modules, download towelroot, make it rain, and then install SU binary's from SU app.
EDIT 4: Root is only temporary. After a reboot it disappears. Also, theme's work great
Click to expand...
Click to collapse
Just about to flash, did you by chance get the build uploaded? Awesome work!

Evant28 said:
Just about to flash, did you by chance get the build uploaded? Awesome work!
Click to expand...
Click to collapse
uploaded wrong file lol There you go btw, there's still no service.
EDIT: Reuploading... Uploaded the original one by accident :/

Sterben Pistole said:
Does BypassLKM work on 4.4.2? I know it works on 4.3, because that's what it was built for, but if it does it would definitely help a good bit.
Click to expand...
Click to collapse
I'm pretty sure someone got it working while everyone was looking into getting a working kexec module. I'll see if I can't find a link somewhere.
EDIT: Still searching, but there are also directions on how to point it to the right address and compile it in the bypasslkm thread. Surge1223 built one for 4.4.2, but it's for verizon NC5 and I haven't found the link yet just found it here.

DeadlySin9 said:
I'm pretty sure someone got it working while everyone was looking into getting a working kexec module. I'll see if I can't find a link somewhere.
EDIT: Still searching, but there are also directions on how to point it to the right address and compile it in the bypasslkm thread. Surge1223 built one for 4.4.2, but it's for verizon NC5 and I haven't found the link yet just found it here.
Click to expand...
Click to collapse
http://ubunmobile.blogspot.com/2015/03/moddev-enable-unsigned-kernel-modules.html Here's a link to what seems like it's what we're looking for.