Database Develop

[ROM]Cyanogen Mod 9.0 Mod (For stock rom users)

Introduction
This is a port of Android 4.0.X for Streak7 [WIP]
The "official" CM9 port requires you to repartition your device to use it. This is a mod that allows it to run on standard partition devices.
Any bugs in the "official" CM9 port will likely carry over, and there is a possibility of the mod creating more bugs.
Do not bug DJ_Steve or Giveen about any bugs in this version.
I will be providing support/changes for using CM9 on devices with stock partition layouts (ie Stock 5xx, HS r7 and newer users)
This version is a mod of the CM9 build by DJ_Steve/Giveen for stock rom partition users.
IF YOU ARE CURRENTLY USING HONEYSTREAK R2-R6, "NORMAL" CM9 (ICS-B4), OR HAVE USED NVFLASH: THIS BUILD IS NOT FOR YOU
If you have installed the prerelease, you are STRONGLY RECOMMENDED to do a fac reset after installing.
Click to expand...
Click to collapse
How to flash a zip:
Entering recovery mode on device -XDA wiki
Flashing an update.zip with custom recovery - XDA wiki
Click to expand...
Click to collapse
Requirements:
A custom recovery:
Clockwork Mod 6.0.1.1 (or newer)
Team Win Recovery Project 2.2.1.4 (or newer)
A compatable device (see above)
Click to expand...
Click to collapse
Install instructions:
Download: update-S7-CM9-b4-mod-2.zip
Copy update zip to SD card
Reboot into custom recovery mod
Select "update from update.zip"
Navigate to update zip
Flash
REQUIRED: Flash Gapps
Finished
Click to expand...
Click to collapse
Changes:
Removal of gapps (which will be provided in a seperate zip)
(Semi) Working /sdcard and /sdcard2 (has some bugs still, but mostly works)
Minor polish
Credits:
DJ_Steve for porting CM9
Giveen for every random thing
Click to expand...
Click to collapse
Changelog:
Aug 23 2012: Updated install script
Jul 22 2012: Released full version
Jul 21 2012: Updated instructions
Jul 20 2012: Released prerelease 1
Click to expand...
Click to collapse
2char

Introduction
I'm gonna organize everything I'm currently aware of, I'm gonna update this post as people comment.
Wifi
[-] Overall: Works fine
[-] Speed: Same as on previous roms
[?] Untested: Wi-fi tethering
Bluetooth
[?] Overall: Untested
[?] Untested: File transfer
[?] Untested: BT Headset
[?] Untested: Keyboard
[?] Untested: Mouse
[?] Untested: BT Tethering
[?] Untested: Handsfree device
Cellular data
[!] Overall: Nothing works
GPS/Sensors
[-] Overall: Works fine
[?] Unknown: AGPS support (Needs confirmation)
[-] Works: Accelerometer
[-] Works: E-Compass
[!] Bug: FM Radio does not work
[!] Bug: GPS very inaccurate/does not work
[-] Works: Light Sensor
[?] Untested: Microphone
[-] Works: Vibrator
Dock and outputs
[-] Works: Mostly works
[-] Works: Dock detection
[-] Works: HDMI out
[?] Untested: USB tethering
Mass Storage and Inputs
[-] Overall: Mostly works
[?] BUG: Internal sdcard not presented does not work
[!] Bug: USB-Hosting does not work
Battery
[-] Overall: Airplane mode: Seems Fine
[?] Overall: Cellular on: Unknown
[-] Works: Charging
[!] Bug: Usage info not available
Graphics
[-] Overall: Works fine
Sound
[-] Overall: Works fine
[?] Untested: Headphone out
Buttons and leds
[-] Overall: Works fine
Camera
[!] Overall: Nothing works
[!] BUG: Rear cam doesnt work
[!] BUG: Front cam doesnt work
[!] BUG: Rear Flash doesnt work
Screen and UI
[-] Overall: Works fine
Apps
[-] Overall: Mostly works
[-] Not a bug: GAPPs isnt included (General consensus: stock based roms: including gapps is ok, source based roms: do not include gapps)
[!] BUG: Chrome settings button causes app to crash
Feature requests:
Phone mode UI
Virtual keys (in phone mode)
Overall summary:
[-] Wifi: Works fine
[?] Bluetooth: Untested
[?] Tethering: Untested
[!] Cellular: Nothing works
[?] GPS/Sensors: Untested
[-] Dock/Output: Mostly works
[-] Mass Storage/Input: Mostly works
[-] Battery: Good
[-] Graphics: Mostly works
[-] Sound: Works fine
[-] Buttons: Works fine
[!] Cameras: Nothing works
[-] Screen and UI: Mostly works
[-] Apps: Mostly works
Conclusion:
(placeholder)

Released a prerelease version, this version uses the B3 apks as I cannot extract the B4 ones.
Once someone is able to give me a copy of the B4 apks I'll release the full version of B4-mod

I installed but it's a bit empty.(I know there is no gApps in it) Also I noticed rotation not works by default until you switch it on from Trebuchet - General Settings. While I am switching between menus on wireless part, device becomes unresponsive sometimes.(T-Mobile 4G Model)
Camera and 3G/4G Radios are still same, not working.
On the other hand it boots up and works very fast. Good Job!
I'm new to Android system but I know a bit about Linux. Also I'm a software developer. Are there any guideline for development/environment? (I'm using Windows 7 and Ubuntu both) I wanna try to contribute.
Edit: This works for me very well: http://wiki.cyanogenmod.com/index.php?title=Latest_Version/Google_Apps
Second Edit: Switching airplane mode on, locks device completely.

Cell data was never supported, and airplane mode freezing is likely related to that.
Treb locking to landscape by default isnt really a bug, as there is a checkbox and it does remember which one you pick.
Camera is known to not work. All these are carry over from ICS B4
Gapps isnt ready yet, it will be soon.

Snarg is trying to get camera to work
Sent from my Nexus 7 using Tapatalk 2

VPN is not working too. It says "Unsucessful". I'm sure credentials and other setting are correct.
Bluetooth:
General Functions and pairing with bluetooth mouse is working.

I havnt changed anything at all regarding VPN,
it's either due to:
Using the B3 apks (since I dont have the B4 apks)
A bug in B4 (which I cant fix)
Keep in mind I'm only making minimal changes, I'm not actively updating the code.
But I'll take a look tomorrow and see if it's anything fixable

iboware said:
VPN is not working too. It says "Unsucessful". I'm sure credentials and other setting are correct.
Bluetooth:
General Functions and pairing with bluetooth mouse is working.
Click to expand...
Click to collapse
I cant reproduce as I dont have a vpn I can attempt to connect to.
I'm going to need a logcat of you attempting to connect to it to look at, otherwise I cant even look at what could be the issue.

It turns out that the B4's system.img is in fact 'damaged'
It's damaged to the point that ext2explore cant read it, but linux kernals can mount it.
I will be releasing the full version of CM9-mod soon
Edit: There's a really strange bug with the B4 apks.
You must also install Gapps or the home button will not respond.
It actually responds when you're in the clock app, but not anywhere else.
I dont know why installing gapps fixes it, as I've cleanly pulled gapps out of the rom.

TheManii said:
I cant reproduce as I dont have a vpn I can attempt to connect to.
I'm going to need a logcat of you attempting to connect to it to look at, otherwise I cant even look at what could be the issue.
Click to expand...
Click to collapse
Code:
W/PrintK ( 68): dog, +tegra_wdt_set_timeout, wdt->timeout=130
V/PrintK ( 1323): <7>[ASOC-DBG]tegra_dapm_event_int_spk SND_SOC_DAPM_EVENT_ON ?
2
V/PrintK ( 1323):
I/keystore( 103): uid: 1000 action: s -> 1 state: 1 -> 1 retry: 4
I/keystore( 103): uid: 1000 action: s -> 1 state: 1 -> 1 retry: 4
I/keystore( 103): uid: 1000 action: s -> 1 state: 1 -> 1 retry: 4
D/dalvikvm( 2967): GC_CONCURRENT freed 318K, 23% free 6465K/8391K, paused 2ms+4m
s
E/BinaryDictionaryGetter( 1527): Could not find a dictionary pack
E/ActivityThread( 1527): Failed to find provider info for com.android.inputmetho
d.latin.dictionarypack
D/PrintK ( 1323): <6>wm8903_set_dai_trigger 1
D/dalvikvm( 1359): GC_EXPLICIT freed 745K, 22% free 9279K/11783K, paused 4ms+7ms
E/ActivityThread( 1527): Failed to find provider info for com.android.inputmetho
d.latin.dictionarypack
E/BinaryDictionaryGetter( 1527): Could not find a dictionary pack
D/dalvikvm( 1527): GC_CONCURRENT freed 474K, 21% free 7396K/9287K, paused 3ms+4m
s
I/keystore( 103): uid: 1000 action: i -> 1 state: 1 -> 1 retry: 4
I/Vpn ( 1359): Switched from [Legacy VPN] to [Legacy VPN]
I/Vpn ( 1359): Switched from [Legacy VPN] to [Legacy VPN]
V/LegacyVpnRunner( 1359): Waiting
V/LegacyVpnRunner( 1359): Executing
D/mtpd ( 3001): Waiting for control socket
I/LatinIME( 1527): InputType.TYPE_NULL is specified
W/LatinIME( 1527): Unexpected input class: inputType=0x00000000 imeOptions=0x000
00000
D/PrintK ( 1359): <6>wm8903_set_dai_trigger 0
D/PrintK ( 1323): <6>wm8903_set_dai_trigger 1
D/mtpd ( 3001): Received 20 arguments
I/mtpd ( 3001): Using protocol pptp
I/mtpd ( 3001): Connecting to ribbsede.getfoxyproxy.org port 1723 via wlan0
I/mtpd ( 3001): Connection established (socket = 11)
D/mtpd ( 3001): Sending SCCRQ
D/mtpd ( 3001): Received SCCRP -> Sending OCRQ (local = 39064)
I/mtpd ( 3001): Tunnel established
D/mtpd ( 3001): Received OCRQ (remote = 32984)
I/mtpd ( 3001): Session established
I/mtpd ( 3001): Creating PPPoX socket
F/mtpd ( 3001): Socket() Protocol not supported
D/dalvikvm( 2967): GC_CONCURRENT freed 336K, 23% free 6527K/8391K, paused 2ms+6m
s
I/LegacyVpnRunner( 1359): Aborting
I/LegacyVpnRunner( 1359): java.lang.IllegalStateException: mtpd is dead
I/LegacyVpnRunner( 1359): at com.android.server.connectivity.Vpn$LegacyVpn
Runner.execute(Vpn.java:569)
I/LegacyVpnRunner( 1359): at com.android.server.connectivity.Vpn$LegacyVpn
Runner.run(Vpn.java:447)
D/PrintK ( 0): <6>wm8903_set_dai_trigger 0
well, it looks like a common cm9 bug but I'm not sure : http://code.google.com/p/minicm/issues/detail?id=495
Another thread about this issue: http://code.google.com/p/android/issues/detail?id=23124
According to the posts I read, adding a kernel compatible tun.ko file will solve this problem.

It does seem to be the case, what rom were you on previously and did VPN work then?
None of our stock roms (by stock roms I mean for every dell device) have tun.ko (by default) and I havnt changed the kernel at all from ICS-B4.
If it worked in B4 then it might have been something from my end, if it didnt then there's nothing that can currently done.
Edit: I will be uploading the full version of CM9-mod soon, flash and fac reset and test against that.
As the prerelease is just that, it doesnt sound like something that would be fixed in the full version, but lets just check and confirm.

TheManii said:
It does seem to be the case, what rom were you on previously and did VPN work then?
None of our stock roms (by stock roms I mean for every dell device) have tun.ko (by default) and I havnt changed the kernel at all from ICS-B4.
If it worked in B4 then it might have been something from my end, if it didnt then there's nothing that can currently done.
Click to expand...
Click to collapse
I was on the latest stock HC and I have never installed any other rom.

If you need VPN support for anything critical (or do anything mission critical period), I would recommend staying on a stock rom.
Regardless of which version of CM9 you choose to install, they're all closer to beta then they are to release.
That said, the full version of CM9-mod is now live.
You are STRONGLY recommended to do a fac reset after installing it if you installed the prerelease.
You also MUST install Gapps as there's a strange bug that causes the home button to not work without it.

TheManii said:
If you need VPN support for anything critical (or do anything mission critical period), I would recommend staying on a stock rom.
Regardless of which version of CM9 you choose to install, they're all closer to beta then they are to release.
That said, the full version of CM9-mod is now live.
You are STRONGLY recommended to do a fac reset after installing it if you installed the prerelease.
You also MUST install Gapps as there's a strange bug that causes the home button to not work without it.
Click to expand...
Click to collapse
I have a timeout problem with marketplace on the full version. It says "loading" for ages and then "Connection timed out. [Retry]" (I did factory reset)

Are you able to connect to websites with the browser?

TheManii said:
Are you able to connect to websites with the browser?
Click to expand...
Click to collapse
Yes. I was able to connect. Today, I tried again and it's successful. I don't know why it could not connected yesterday maybe a DNS issue.
Edit: Shortcuts are displaying in wrong position(under the search icon) it needs alignment. Kindle is not working. I think pre-release version was more stable. Now, I'm back to the stock hc. I would like to try it if there is a new version.

Ive never seen a rom that you shouldnt use if you have Nvflashed before.. whats the cause, or what would happen if one did flash?

ssmr2t said:
Ive never seen a rom that you shouldnt use if you have Nvflashed before.. whats the cause, or what would happen if one did flash?
Click to expand...
Click to collapse
I was wondering the same thing.
sent from device using an app

joeclark said:
I was wondering the same thing.
sent from device using an app
Click to expand...
Click to collapse
Because nvflashed ones are changing the original partition table. if you can restore the partition table, than you can use this one as well, i think.

Cell signal lost

Some people (like me) loosing the signal to the provider. WiFi is ok, but to get back the mobile connection I had to reboot the phone (1-2 times a working day. I never had this problem over the weekend).
I could pin down this behavior to a fast switching between mobile connection and no mobile connection. If the connection is just reestablished and in the next moment it is lost again the phone hangs. I take the underground to reach the office. That is the reason why I only have this issue on working days
So the solution is clear: Stop working. Enjoy the free time
I used "How to get useful logs" from tonyp with the App: SysLog and found in the modem.log the following error: (full log attached)
( 98): dlc[12] atchannel: at_send_command_full() at handshake fails, err - 12. Restarting rild
( 98): lge-ril: handle Cp Reset (CP Reset Cause - 1, RIL recovery activated flag - 0, dlc - 12)
( 98): [0485]< DEACTIVATE_DATA_CALL fails by E_RAIDO_NOT_AVAILABLE
( 98): dlc[12]: lge-ril - requestInterface: Exiting DLC handler, thread - 22231000. s_dlc_handler_create_tracker - 0x6013f
( 759): Exception processing unsol response: 1054Exception:java.lang.RuntimeException: Unrecognized unsol response: 1054
( 759): Unrecognized RIL errno 16
Click to expand...
Click to collapse
I tried a lot of different basebands but could not fix the problem. The only difference was the RIL errno changed from 16 to 14 ???
The basebands I tried are: V30b, V30a, V30c (SU660 - because the sticker under the battery says: Made in Korea), V20m, V20s. In the end I tried different RILs but that only made the problem worse. Now I am back on the original cm10.1 RIL.
Losing the IMEI in the phone is not the problem. I already checked this.
I am pretty sure it is not ROM related because I experienced the same thing on cm7.2 and now on cm10.1 from tonyp on the old and new Boot loader
Regards
Fidi

Possible solution
Hi,
it looks like I found a solution for the loosing signal problem.
After trying all kinds of differnt basebands I switched to an old not recommended baseband. No signal lost for 4 working days in a row :fingers-crossed:
I am now on Baseband 0823-V21b and using ROM tonyp cm10.1 (04)
For the baseband have a look at the P990 Complete Baseband Overview Thread from tonyp: http://forum.xda-developers.com/showthread.php?t=1658047
Cheers
Fidi

Thanks for your informations, i think i have the same problem. Please respond if you have further informations!

I keep you updated:
Over the weekend: Everything worked fine and stable. I used the phone "normal" over the last three days. Including running with Endomondo Sports Tracker and some other parts. The phone is still stable. No reboot since the downgrade to Baseband 0823-V21b.
If I don't get any issues over the week I think that's the solution.
trampi did you downgrade your baseband too? I hope it's a working solution for you too.
Cheers
Fidi

Thank you Fidi!
I have the same logs when my data connection drops, currently with tonyp's T-Build 4 and Kowalski 125 and baseband 0725-V10d.
I will try this out, and report back.

Well I had this data drop issue but when using tonyp's T-Build I started having drops in the whole mobile connection (no voice as well). So I followed his recommendation and flashed BB V30a but that did nothing. Then I tried his Paranoid Android and it's working great!

Bad news here:
7 hours after flashing the baseband 0823-V21b (tonyp T-Build 4, kowalski kernel 125 exp), I got the same error again, and no data, no voice. And only reboot will fix it.
As soon as I see
## AT COMMAND TIMEOUT ##
in the radio log, I'm in the same situation again.
then at the moment of the connection blackout, always followed by:
E/RILJ ( 584): Exception processing unsol response: 1054Exception:java.lang.RuntimeException: Unrecognized unsol response: 1054
and
D/RIL ( 98): dlc[5]: lge-ril - requestInterface: Exiting DLC handler, thread - 7126560. s_dlc_handler_create_tracker - 0x611df
Only with this baseband I don't see this anymore:
E/GSM ( 593): Unrecognized RIL errno 16

I've found a workaround to restore the connection without rebooting:
first kill the /system/bin/rild process
then kill the com.android.phone process
They will both restart automatically.
So this looks like a problem with the ril. Is the ril not compatible with the baseband?
This is also suggested by the "Exception processing unsol response" messages: ril is not able to handle certain baseband commands, although this could also be a corruption on the baseband side...
Now creating a script to automate this workaround will at least give back the connection immediately.

Hi gios_
I am running on the same configuration: 0823-V21b (tonyp T-Build 4, kowalski kernel 125 exp)
If you could provide the script that will check for the error and kill the two services that would be gorgeous. That will solve the problem even if we don't find a "real" solution :fingers-crossed:

Here's the script to fix the connection:
Code:
#!/system/xbin/sh
ps|grep phone|cut -c10-14|xargs kill
ps|grep rild|cut -c10-14|xargs kill
To quickly execute it, you can use gscript (then leave out that first line).

do you guys already check with this solution?
Code:
http://forum.xda-developers.com/showthread.php?t=2075564

antec123 said:
do you guys already check with this solution?
Code:
http://forum.xda-developers.com/showthread.php?t=2075564
Click to expand...
Click to collapse
I did not try that solution because their problem seems to be something else: transition from wifi to data not working; whereas our problem is connection dropping (not only data) at a random moment.
Also my IMEI number is transmitted correctly, so I doubt changing it will do any good.

gios_ said:
I did not try that solution because their problem seems to be something else: transition from wifi to data not working; whereas our problem is connection dropping (not only data) at a random moment.
Also my IMEI number is transmitted correctly, so I doubt changing it will do any good.
Click to expand...
Click to collapse
i used that solution, and with kowalski kernel exp 125 i haven't gotten any data loss. up time already 4 days. using kowalski kernel exp 124, i always get data loss and need reboot.
i use bb v30b ics, and ril (default). rom is using tony bulid 4 cm10.1 newBL. and using 2G always.

Yes, I tried this. But I never lost my IMEI and the solution did not help me
At the moment I am happy with my old baseband (no drops over two weeks). But It looks like that's only a solution for my phone. Maybe we should create a script, that scans the logs for the error and if the connection drops we could restart it with the solution from gios_

FidiS said:
Yes, I tried this. But I never lost my IMEI and the solution did not help me
At the moment I am happy with my old baseband (no drops over two weeks). But It looks like that's only a solution for my phone. Maybe we should create a script, that scans the logs for the error and if the connection drops we could restart it with the solution from gios_
Click to expand...
Click to collapse
yeah i think that true. I'm also confused why some people still have data loss with kowalski exp 125 and some people don't, so wierd

I will stick with baseband 0823-V21b. Still there is no real issue.
There is only remaining thing. In the situations when I formerly lost my connection now the phone rarely heats up for a short time with can drain the battery about 3%. After that the connection is reestablished and everything works as it should
Cheers Fidi

[P905 LTE ONLY!][KERNEL][ODIN] STOCK RELOADED | su | busybox | init.d | permissive !

I am not responsible for any possible bad effects which may result from using included software! You flash it on your own risk!!!
STOCK RELOADED v1 fix 1
Kernel base: stock XXUANC3 (kernel 3.4.0-1131235)
Kernel ramdisk: modded
Features: a few...
Security level: low!
Purpose: giving everyone who loves free exploring of Android secrets and who doesn't consider security as an absolute priority and who wants to put some life in this, indeed, awesome device, a possibility of playing with his device without disturbing restrictions, forced by Samsung, at least until fully-custom kernels, compiled from sources, appear (and that may take some time, as source code available atm seems to be broken, causing all the compiled kernels to stuck at boot screen).
Features working out-of-the-box:
- su binary from SuperSU by Chainfire @ /sbin/su (binary only for scripting purposes! Flash cf-root to use SuperSU app!)
- busybox 1.22.1 binary compiled by Stericson @ /sbin/busybox
- init.d support - just put your favorite scripts into /system/etc/init.d using any file manager and chmod 755 (not 777! it's NOT smart to permit write access for "world" to any system file), chown root:root, they will run on every boot. Well, to be honest, above permissions are given to all the scripts automatically during boot, but it has not yet been tested
- SELinux: Permissive - Samsung's most recent policy of forcing SELinux Enforcing mode by pre-compiling it into a kernel binary part, found in latest KitKat builds since at least a few months, HACKED FOR THE FIRST TIME EVER using innovative method of injecting an information directly into kernel memory space and forcing overwriting potentially-persistent kernel symbol value on-line during boot!)
- unsecure adb access (not tested yet)
- ext4 tweak: 20 sec (instead of stock 5 sec) write commit delay for /data partition (significantly increases IO performance!)
- some further, minor modifications
WARNING!!!
- flashing this WILL undoubtly trip KNOX, avoiding your warranty (which atm cannot be reverted! in any way)
- flashing this WILL cause a warning message of avoided warranty to be displayed on every boot (ofc it disappears right after reverting to stock boot.img)
- flashing this WILL disable some of the very important security features provided with stock firmware!!!! For advanced and experienced users only!!! Use at your own risk!
Known issues:
- AllCast Share mirroring not working (typical for all Samsung devices running not-exactly-stock kernels since S3). WORKING FIX AT POST #16!!!
http://forum.xda-developers.com/showpost.php?p=54516532&postcount=16
Please consider solution from post #3 as not-always-working and depreciated!
Installation:
- compatibile with XXUANC3 firmwares but probably also with other (past and hope future too...) KitKat 4.4.2 Samsung branded firmwares;
- rooting by Chainfire's CF-Root first recommended as it will install SuperSU app in Android (this kernel contains su binary only giving su access without any policy settings!);
- enter download mode and plug the tablet via USB...
- ...select provided file in PDA section (and NOT touch anything except that)...
- ...and flash with Odin in a same way as CF-Root or like anything else...
- enjoy.
DOWNLOAD HERE:
Current version - STOCK RELOADED v1 fix 1
http://www63.zippyshare.com/v/87557346/file.html
FIXED: file name changed so it can be flashed directly by Odin without renaming! Sorry for this silly mistake!
=======
Changelog:
v1 fix1:
- fixed permissive mode due to trivial error;
- delayed init.d execution to a moment AFTER init process set cfq scheduler so it is not overriding mmcblk0 tweaks (if put in init.d) anymore;
- minor code cleanups
v1:
- initial release
- init.d support
- SELinux permissive
- unsecure ADB
- ext4 delayed commit for /data
=======
Stock XXUANC3 kernel (to revert changes)
http://www65.zippyshare.com/v/32441894/file.html
Revert using Odin, in the same way you've installed a Reloaded Version....

Awww man,...I wish i could flash this, but I'm on the exynos =(
Sent from my SM-P900 using Tapatalk

rgolnazarian said:
Awww man,...I wish i could flash this, but I'm on the exynos =(
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
Sorry pal, Qualcomm only, not even a chance to run this same way as the devices (and mostly important: provided software, ie. system structure) DIFFER A LOT between themselves.
Update 1: uploaded fix #1 which is resolving some trivial issues found in initial version; sorry for that, now we can say that every described feature has been included hope for some feedback... thank you...
Update 2: FIX FOR NOT WORKING SCREEN MIRRORING CAN BE DOWNLOADED HERE:
http://www67.zippyshare.com/v/25492738/file.html
I have personally modified a library that is being used by screen mirroring feature, which forces video encryption using keys from stock kernel, and which prevents to run mirroring at all . This is an issue of any modified kernel, on any Samsung device. Attached library fixes this, by disabling HDCP at all. It has been reported that the library resolves the issue for any Qualcomm based Samsung device running 4.4.2 KitKat and for any custom kernel. It will NOT work for Exynos devices...
Installation:
- download attached libwfdsm.so file
- overwrite genuine one in/system/vendor/lib (important! NOT /system/lib!!!!)
- chmod 644 libwfdsm.so ||| chown 0.0 libwfdsm.so ||| restorecon -R /system/vendor/lib
- mirroring will work again after reboot!!

YAY!
Beautiful, absolutely beautiful. You made ma a very happy man with this. I'll flash this as soon as I get home from work. Can't wait to try it out, the stock kernel is giving me SOD and frozen wifi issues sometimes.

esgie said:
Sorry pal, Qualcomm only, not even a chance to run this same way as the devices (and mostly important: provided software, ie. system structure) DIFFER A LOT between themselves.
Update 1: uploaded fix #1 which is resolving some trivial issues found in initial version; sorry for that, now we can say that every described feature has been included hope for some feedback... thank you...
Update 2: FIX FOR NOT WORKING SCREEN MIRRORING CAN BE DOWNLOADED HERE:
http://www67.zippyshare.com/v/25492738/file.html
I have personally modified a library that is being used by screen mirroring feature, which forces video encryption using keys from stock kernel, and which prevents to run mirroring at all . This is an issue of any modified kernel, on any Samsung device. Attached library fixes this, by disabling HDCP at all. It has been reported that the library resolves the issue for any Qualcomm based Samsung device running 4.4.2 KitKat and for any custom kernel. It will NOT work for Exynos devices...
Installation:
- download attached libwfdsm.so file
- overwrite genuine one in/system/vendor/lib (important! NOT /system/lib!!!!)
- chmod 644 libwfdsm.so ||| chown 0.0 libwfdsm.so ||| restorecon -R /system/vendor/lib
- mirroring will work again after reboot!!
Click to expand...
Click to collapse
I was literally just about to post in the old thread with bad news about the modified "libwfdsm.so" file & screen mirroring with a custom kernel...if u remember i confirmed that the file u altered would work with a custom recovery on the 8.4 lte & i just assumed that it would work with an altered boot.img as well but unfortunately thats not the case after testing the other night (unless something else is wrong with my setup). So...my question is have u changed something else since then to allow it to work again & have u personally tested this yourself?
sorry to hijack the thread...didnt know if i should pm or post in the older thread

THEDEVIOUS1 said:
I was literally just about to post in the old thread with bad news about the modified "libwfdsm.so" file & screen mirroring with a custom kernel...if u remember i confirmed that the file u altered would work with a custom recovery on the 8.4 lte & i just assumed that it would work with an altered boot.img as well but unfortunately thats not the case after testing the other night (unless something else is wrong with my setup). So...my question is have u changed something else since then to allow it to work again & have u personally tested this yourself?
sorry to hijack the thread...didnt know if i should pm or post in the older thread
Click to expand...
Click to collapse
No problem, anyway, thanks for pointing the issue out! This may be an important information for mirroring users!
Since then I didn't change anything, yet. Really, I am also not sure if I have tested it with modified kernel, as the one posted here is the first kernel for P905 at all, and it's not even "fully" customized, as the kernel binary base was left unchanged.
So, I'd like to be sure: you are saying that modded lib:
- fixed the problem for custom recovery, but...
- ...didn't fix it for custom kernel
right?
I was looking for a solution to persistent enforcing mode since some time, so I was flashing test boot.imgs from time to time, then reverting to stock again, meanwhile I created above lib, I can't really be sure about if it is working when both bootimg and kernel are customized (this would also be an opposite to previous Sammy's Android releases, where a single fix was solving all the issues related to customizations of both kernel and recovery!).
We also have to be aware that the issues may not be a result of flashing different kernel at all, but a result of the changes themselves, ie. disabled knox, disabled encryption of i-dont-really-know-what, etc, etc.
And the most important thing! Since I have heard of AllShareCast/Screen Mirroring for the first time (it probably appeared for the first time in S3/Note2/Note10.1), it always required resetting the flash counter - which could be viewed in download mode and which is NOT the same as Knox flag - to ZERO and that requirement AFAIR remained totally independent from the requirement of having stock boot/kernel (or lib patch). Have you checked the counter state? Did you reset it to zero again using Chainfire's Triangle Away after flashing non-stock kernel (which, obviously, TRIPPED the counter)? Can you check if it is working? Note that at least on my P905, Triangle Away still works flawlessly and resets the counter without any problems and even without a need of reboot!
Please check above info and try if the issue is fixed after running Triangle Away. I am leaving for a short business trip soon, so I'll perform my own tests with AllShare cast until next of the week, however, neither today nor tomorrow...

I get an "md5 error! binary is invalid" when I choosse the file in Odin. I downloaded the file 6 times, and every time I get the md5 error.
What do I do?
EDIT: Renaming the file to "boot.tar.md5" seemed to solve the problem.

cavkic said:
I get an "md5 error! binary is invalid" when I choosse the file in Odin. I downloaded the file 6 times, and every time I get the md5 error.
What do I do?
EDIT: Renaming the file to "boot.tar.md5" seemed to solve the problem.
Click to expand...
Click to collapse
Argh possibly too many dots in filename... will correct it tomorrow.

cavkic said:
I get an "md5 error! binary is invalid" when I choosse the file in Odin. I downloaded the file 6 times, and every time I get the md5 error.
What do I do?
EDIT: Renaming the file to "boot.tar.md5" seemed to solve the problem.
Click to expand...
Click to collapse
same here...

Hi,
I have a problem with screen mirroring.
Installed the patch and mirroring connects to the dongle, but the TV screen turns just black.
The dongle works perfect with HTC One M8, it must be a softwareproblem?
Thanks for help!!!

Will this work on the P905V (Verizon Variant)? I need to downgrade the permissions in my Security in order to use Towelroot, because they're set to Medium and I believe that prevents Towelroot to work properly. Most of the other Note 12.2 variants have been rooted....except the Verizon version.

Can anyone give me some advice please. When I enter the command in terminal emulator I get an error saying "Unable to open chown. No such file or directory". Am I missing something obvious lol.

Will this work on p907a AT&T version of note pro 12.2?
Sent from my SAMSUNG-SM-P907A using XDA Premium 4 mobile app

cnote74 said:
Will this work on p907a AT&T version of note pro 12.2?
Sent from my SAMSUNG-SM-P907A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
On the topic name it says [P905 LTE ONLY], and your device is some different..

tdetroit said:
Will this work on the P905V (Verizon Variant)? I need to downgrade the permissions in my Security in order to use Towelroot, because they're set to Medium and I believe that prevents Towelroot to work properly. Most of the other Note 12.2 variants have been rooted....except the Verizon version.
Click to expand...
Click to collapse
I would like this answered as well. I also have the "v" variant. Maybe saying LTE includes many? See my link I attached, found while investigating this specific question.
http://www.usatoday.com/story/tech/2013/07/07/sprint-att-verizon-phones-network-carriers/2486813/
Ever since I rooted my tablet it goes on random reboot kicks. I want to start over. Also TWRP will not stick when I try to flash it.
I have many issues which I'm currently posing in their appropriate forums. It would be nice to wipe to a rooted stock.

Guys!
I have probably found another solution for non-working Screen Mirroring / AllShare Cast when custom kernel is flashed (again, LTE devices only).
No need of modded lib
Seems that the only thing we need is to
1) run Terminal Emulator and type:
Code:
su -c setprop wlan.wfd.hdcp disable
(will work immediately; won't stick between reboots!), OR...
2) edit /system/build.prop file with any root file manager/text editor and add a line (no matter where):
Code:
wlan.wfd.hdcp=disable
(will work only after reboot; will stick between reboots).
Try this using kernel from op waiting for feedback!

Thanks. The Galaxy is connecting to theTV, but the screen is only turning black - no Display...
Any idea?
Thank you.
esgie said:
Guys!
I have probably found another solution for non-working Screen Mirroring / AllShare Cast when custom kernel is flashed (again, LTE devices only).
No need of modded lib
Seems that the only thing we need is to
1) run Terminal Emulator and type:
Code:
su -c setprop wlan.wfd.hdcp disable
(will work immediately; won't stick between reboots!), OR...
2) edit /system/build.prop file with any root file manager/text editor and add a line (no matter where):
Code:
wlan.wfd.hdcp=disable
(will work only after reboot; will stick between reboots).
Try this using kernel from op waiting for feedback!
Click to expand...
Click to collapse

esgie said:
Guys!
I have probably found another solution for non-working Screen Mirroring / AllShare Cast when custom kernel is flashed (again, LTE devices only).
No need of modded lib
Seems that the only thing we need is to
1) run Terminal Emulator and type:
Code:
su -c setprop wlan.wfd.hdcp disable
(will work immediately; won't stick between reboots!), OR...
2) edit /system/build.prop file with any root file manager/text editor and add a line (no matter where):
Code:
wlan.wfd.hdcp=disable
(will work only after reboot; will stick between reboots).
Try this using kernel from op waiting for feedback!
Click to expand...
Click to collapse
I tried both methods and still get no devices found when I turn on screen mirroring.

ColBill said:
I tried both methods and still get no devices found when I turn on screen mirroring.
Click to expand...
Click to collapse
Hm.
This is weird, as the problems with allshare cast + custom kernels is not that "no devices are found" but that devices ARE found without any problem but the connection process fails after a few secs. This solution may help with the issue i described, but it will surely not solve the problem with no peers detected at all.
No peers detected = problems with wifi direct (are you able to send files between wifi direct between devices?)
Can you tell me what is your exact device config? And are you using allsharecast dongle or other third party hardware?
@fokus
Only one: also reset flash counter with Triangle Away and then try again. And make sure you spell the value in the command as "disable" not "disabled" - it's tricky and one can miss it...
Well, there are two additional things to add.
Guys, make sure you have updated Samsung's ScreenMirroring firmware update app to the latest version. And check out the samsung mirroring fix app in google play, which solves some issues for various devices (dunno which ones exactly as i have never been in need of using it).

The fix half worked for me lol. The tablet now connects fine to the Netgear PTV3000 but all I get is black screen. Step in the right direction though as at least it connects now. Just need to get a picture to show lol.

WIFI Suddently disabled after reboot

Hi all,
I hope I can get some help here.
Yesterday I rebooted my S4 Active after I installed some app updates, and suddenly WIFI can't be enabled anymore.
First I thought the phone might be broken, but I tested a factory reset and WIFI works again.
But I don't want to reinstall all apps and lose app settings and so on. I also want to know what is causing this issue, it might happen again.
I am on official Stock Rom (Android 4.4.2) I9295XXUCNE5 I9295PHNCNE1. I am using this rom without any problems since a half year.
So I did some testing with adb and usb debugging, and for some reason the wifi kernel driver cannot be loaded. I tried loading it manually with:
Code:
insmod /system/lib/modules/dhd.ko
But this fails with:
Code:
insmod /system/lib/modules/dhd.ko
insmod: init_module '/system/lib/modules/dhd.ko' failed (Exec format error)
I looked into output of kmesg, and it shows this when trying to load the wifi module:
Code:
<3>[ 614.365997] QSEECOM: qsee_disable_clock_vote: Client error.Extra call to disable SFPB clk
<3>[ 614.362304] QSEECOM: qseecom_ioctl: Failed to vote for SFPB clock-6
<3>[ 614.362060] QSEECOM: qsee_vote_for_clock: SFPB Bandwidth req failed (-6)
<3>[ 614.361816] AXI: msm_bus_scale_client_update_request(): Client 3720895680 passed invalid index: 3
Again when I do a factory reset, WIFI works fine again, so it has to be a software bug somewhere.

After factory reset and working WiFi disable Play Store auto update.
Do one app update, test wifi, next app update, test WiFi,...
Easier to identify if an app is source of issue than do all in one update.
Not sure if insmod or other module related commands might need su credentials provided by rooting.

O-T said:
After factory reset and working WiFi disable Play Store auto update.
Do one app update, test wifi, next app update, test WiFi,...
Easier to identify if an app is source of issue than do all in one update.
Not sure if insmod or other module related commands might need su credentials provided by rooting.
Click to expand...
Click to collapse
That's kind of pain in the ass when you have like 100 apps installed
Well I know the last apps that got updated. But how can this damage wifi system driver? And yes insmod needs root , and my phone was NOT rooted prior this issue. I rooted it know in order to properly debug the problem.
best regards,
Andre

delta_ray said:
That's kind of pain in the ass when you have like 100 apps installed
Well I know the last apps that got updated. But how can this damage wifi system driver? And yes insmod needs root , and my phone was NOT rooted prior this issue. I rooted it know in order to properly debug the problem.
best regards,
Andre
Click to expand...
Click to collapse
Try flashing the NE5_PHN_wifi_150107.zip in CWM from the NE5 folder on my GDrive.

JASONRR said:
Try flashing the NE5_PHN_wifi_150107.zip in CWM from the NE5 folder on my GDrive.
Click to expand...
Click to collapse
Thanks I tried this. Unfortunately, the problem persists.
Do you know which files are used by the WIFI kernel module?
My guess is that some config file causes this problem.

delta_ray said:
Thanks I tried this. Unfortunately, the problem persists.
Do you know which files are used by the WIFI kernel module?
My guess is that some config file causes this problem.
Click to expand...
Click to collapse
Those are the files in the zip file. You can also try deleting data/misc/wifi/wpa_supplicant.conf and rebooting or even try deleting the entire folder.
You can also try my ROM, super WizCyan that is based on the PHN firmware with mostly S5 apps.

Can your rom installed without factory reset over stock rom?
A side note, Play Store also does not work anymore. I am online over LTE and can use Internet, but Play Store gets timeout while loading.
Some more debugoutput from logcat, but not helping much:
Code:
E/WifiHW ( 848): ##################### set firmware type 0 #####################
I/WifiHW ( 848): module is semco
E/WifiHW ( 848): ==========[WIFI] Station firmware load ===========
E/WifiHW ( 848): ==========[WIFI] SEMCO MODULE ===========
E/WifiHW ( 848): return of insmod : ret = -1, Exec format error
If I just knew what is causing the driver fail.

delta_ray said:
Can your rom installed without factory reset over stock rom?
A side note, Play Store also does not work anymore. I am online over LTE and can use Internet, but Play Store gets timeout while loading.
Some more debugoutput from logcat, but not helping much:
Code:
E/WifiHW ( 848): ##################### set firmware type 0 #####################
I/WifiHW ( 848): module is semco
E/WifiHW ( 848): ==========[WIFI] Station firmware load ===========
E/WifiHW ( 848): ==========[WIFI] SEMCO MODULE ===========
E/WifiHW ( 848): return of insmod : ret = -1, Exec format error
If I just knew what is causing the driver fail.
Click to expand...
Click to collapse
Unfortunately not, as most of the stock apps have been replaced by S5 apps. You can try but will get a lot of fc's. If you want to try without factory reset use super backup to backup calls, call logs, contacts and calendar and clear cache and data for these before flashing ROM as well as clear cache and dalvic and restore these after flashing the ROM.
Any specific reason why you do not want to wipe data. I always do it once in a couple of months and reconfigure all apps except for a couple of banking apps that I redtore with titanium backup to save the hassle of contacting the banks again. This helps to clear the clogginf od data and keep the phone smooth.
For playstore you can wipe cache and data for google play & play services and stop them from running.
---------- Post added at 01:20 PM ---------- Previous post was at 01:08 PM ----------
Did you try deleting data/misc/wifi/wpa_supplicant.conf and rebooting and/or deleting the entire data/misc/wifi folder

JASONRR said:
Any specific reason why you do not want to wipe data. I always do it once in a couple of months and reconfigure all apps except for a couple of banking apps that I redtore with titanium backup to save the hassle of contacting the banks again. This helps to clear the clogginf od data and keep the phone smooth.
For playstore you can wipe cache and data for google play & play services and stop them from running.
Click to expand...
Click to collapse
Just pure lazyness . But it seems like that I have to go for the factory reset and backup/restore all apps after.
However I hope to find the source of this issue, who knows when it will happen again.

delta_ray said:
Just pure lazyness . But it seems like that I have to go for the factory reset and backup/restore all apps after.
However I hope to find the source of this issue, who knows when it will happen again.
Click to expand...
Click to collapse
If it works after factory reset, then I would say there is corruption in data. Try deleting 'data/misc/wifi' folder flash the wifi zip and restart

I restored the /data/misc/wifi folder from an older working backup.
Still the same error, there must be something else causing the problem.

delta_ray said:
I restored the /data/misc/wifi folder from an older working backup.
Still the same error, there must be something else causing the problem.
Click to expand...
Click to collapse
I would suggest that you delete thd folder itself. Also you could try with the Ktoonez kernel from here
http://forum.xda-developers.com/showthread.php?p=51925641

delta_ray said:
I restored the /data/misc/wifi folder from an older working backup.
Still the same error, there must be something else causing the problem.
Click to expand...
Click to collapse
Have you changed LTE-modem (NON-HLOS.BIN) from what's in stock *NE5 ROM you informed in OP?
http://forum.xda-developers.com/showthread.php?p=56955843

O-T said:
Have you changed LTE-modem (NON-HLOS.BIN) from what's in stock *NE5 ROM you informed in OP?
http://forum.xda-developers.com/showthread.php?p=56955843
Click to expand...
Click to collapse
No haven't change LTE-Modem Software, still have the stock NE5 installed.

JASONRR said:
I would suggest that you delete thd folder itself. Also you could try with the Ktoonez kernel from here
http://forum.xda-developers.com/showthread.php?p=51925641
Click to expand...
Click to collapse
I guess I should get KT-SGS4-KK4.4-AOSP-jactive_eur-04.19.2014.zip?
This kernel works with my Stock 4.4.2 rom?

delta_ray said:
I guess I should get KT-SGS4-KK4.4-AOSP-jactive_eur-04.19.2014.zip?
This kernel works with my Stock 4.4.2 rom?
Click to expand...
Click to collapse
Not that one, get KT-SGS4-KK4.4-TW-eur-01.03.2015.zip, there is an issue with touchscreen which is being looked into, I am currently using KT-SGS4-KK4.4-TW-eur-01.09.2015_debug2.zip from the debug folder.

JASONRR said:
Not that one, get KT-SGS4-KK4.4-TW-eur-01.03.2015.zip, there is an issue with touchscreen which is being looked into, I am currently using KT-SGS4-KK4.4-TW-eur-01.09.2015_debug2.zip from the debug folder.
Click to expand...
Click to collapse
The kernel did not work on stock rom. Anyway I did another factory reset and restored most apps and settings using TitanBackup Root.
And guess what happened after restore of all the apps & settings?
WIFI is broken again.
Does somebody know all data files are used by WIFI?

delta_ray said:
The kernel did not work on stock rom. Anyway I did another factory reset and restored most apps and settings using TitanBackup Root.
And guess what happened after restore of all the apps & settings?
WIFI is broken again.
Does somebody know all data files are used by WIFI?
Click to expand...
Click to collapse
It seems that something in the settings is breaking the wifi. You can wipe the data of settings and wifi individually and check if it fixes the issue.
If you are doing factory reset, I always recommend to redo the settings again rather than restoring through TB.
Can you take a logcat and send the entire one to check if there is anything there.

Not sure if I mentioned it but I removed "wpa_supplicant.conf" multiple times, it doesn't solve the problem.

JASONRR said:
It seems that something in the settings is breaking the wifi. You can wipe the data of settings and wifi individually and check if it fixes the issue.
If you are doing factory reset, I always recommend to redo the settings again rather than restoring through TB.
Can you take a logcat and send the entire one to check if there is anything there.
Click to expand...
Click to collapse
How can I just reset WIFI settings?

WiFi and Bluetooth won't turn on on any kernel and firmware (stock / custom)

Hello,
today I was working with my Xperia Z (C6603) and flashed a CM12 build. After having some problems with TWRP, I solved it in the end an TWRP and CM12 were working fine. But WiFi and Bluetooth won't turn on anymore. When I press "turn on" it takes some time and then the switch turns off again. A MAC address is not shown anymore. I tried to flash stock firmware with Flashtool, but didn't change anything.
Can someone help me to solve this? Is my phone partially bricked?
Thanks a lot!

Some update as I try to find the problem. I looked into logcat and only find this info when I try to turn on WiFi:
Code:
D/WifiService( 814): setWifiEnabled: true pid=1072, uid=10008
E/WifiStateMachine( 814): Failed to load driver
And when I try to execute wpa_suuplicant manually with "/system/bin/wpa_supplicant -Dnl80211 -iwlan0 -c/system/etc/wifi/wpa_supplicant.conf"
Code:
I/wpa_supplicant( 9440): rfkill: Cannot open RFKILL control device
E/wpa_supplicant( 9440): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 9440): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 9440): wlan0: Failed to initialize driver interface

Anyone? Just a hint to narrow down the problem?

Hi,
I have similar problem. My WiFi stopped working out of the blue.
I am quite sure I didn't changed anything. System crash occured when I was switching from Airplane mode to Normal mode (this usually turns WiFi on, if it was activated (and then deactivated) in Airplane mode). Then I got stucked in bootloop. Wiping dalvik-cache helped, but it was not the cause. At first, bluetooth was crashing too, but now it seems it works.
In *#*#INFO#*#* I can see
Code:
Supplicant state: UNINITALIZED
. LogCat issues are almost the same.
I've tried factory reset, but it didn't solved the problem. I've checked permissions, reflashed wifi-modules, tried WiFi Fixer app, reinstalled kernel, flashed another kernel, checked the wpa_supplicant.conf…but it still doesn't work.
EDIT: Oh, I forgot to mention my device: Xperi Mini St15i (Smultron), rooted, unlocked bootloader, Stock ICS ROM (only de-bloated, it worked until now) 4.0.4, build number 4.1.B.0.587. I've used kernel Kappa v1.6, but after the error occured, I tried switch to Rage kernel v2.32.
EDIT2: I've tried to restore original hosts, wpa_supplicant.conf, modules, wifi/*, etc....almost everything and nothing helped. I've flashed original stock ROM (you can find flashable stock ICS ROM for st15i here). I still don't know what happend and I'd like to know it. Hope I'll never see this problem again…