Database Info

Wifi Calling issues

I'm running Android Revolution XE 3.6.0 with the new wifi calling patch and I can't seem to get the Wifi Calling to work. I can open the app, it sees that I am on wifi, and it just sits at the "Wifi Calling: Enabling" "Please wait while connecting to T-Mobile Network". Any ideas?
Here is what I can see when doing logcat:
E/KINETO ( 4272): KLOG103- ganswitch_init - error sending message!
I/Kineto::Receiver( 4272): onReceive Enter
I/Kineto::main( 4272): Kineto: SendAlarmEvent Enter
E/KINETO ( 4272): KLOG0A2- ERROR: IBS Msg Q Post: size is too large
E/KINETO ( 4272): KLOG0A2- ERROR: Failed to post to Queue
I/Kineto::Receiver( 4272): onReceive Exit
D/KIPCapp ( 4272): KIPC_SendMessage: len = 1, socket = 0
D/KIPCapp ( 4272): Connecting... socket = 47, state = 0
D/KIPCapp ( 4272): Address is 127.0.0.1, Port is 45211
E/KIPCapp ( 4272): Connect failed 111
Click to expand...
Click to collapse

[/thread]
Wound up just doing a clean wipe and reinstall of the ROM since I ran into some other very weird issues after looking for why it was not working. Probably a bad install.

I don't see the wifi calling app after I flashed to 4.1.0. I also rooted, superCID, S-off my phone already. Is your Sensation superCID off too?

If you messed with your CID, WiFi calling won't be installed. Check out this thread on how to install it. Do NOT flash the file, you must follow the directions. You have to copy some files over, install an APK, and change the build.prop file.
http://forum.xda-developers.com/showthread.php?t=1193142
Sent from my HTC Flyer P512 using xda premium

[KERNEL][BML] BlastOff - v2.5 [2012-11-18]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​MOD NOTICE:
This is a development thread.
If your statement ends in a ? it belongs in the Q/A thread linked in the OP.
If something doesn't work correctly, first of all do a full wipe and see if the problem persists.
If it does, and it is repeatable, grab a logcat if you can, there are apps on the market for that such as aLogcat, and then post here with detailed information about what happened, how often it happened, and what happened when you were doing it.
Anyone that does not comply with these rules will receive an infraction, this is your warning.
--sixstringsg
​
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, broken hearts,
* thermonuclear war, you getting fired because the alarm app failed, or
* unfulfilled sexual partners. Please do some research if you have any
* concerns about features included in this ROM before flashing it! YOU are
* choosing to make these modifications, and if you point the finger at me
* for messing up your device, I will point that finger back at you and laugh.
* Then I will put it in your eye.
*/
By using the ROM you agree with the above terms!
Hey all, I made a new BML kernel because the ones that are out are getting old and are not being updated.
For those of you that still use BML roms, you'll be happy to know that this kernel will keep getting supported by me.
The Goals of this kernel are:
Low power usage
OC/UV (thanks AntonX!)
High quality
This will also be the kernel eollie will use in his next OneClick.
Eventually, this kernel will have an MTD branch. But this is still not the case.
Please, do not ask questions in this thread. That is why I setup the Q&A Thread here.
In v2.5, FBis251 added support for updating the /system/etc/wifi directory so you shouldn't have to much around with your rom to get wifi working! Give thanks to FB!
AntonX - For all of his great work that I cherry-picked! We miss you! Come back!
teamhacksung - For the bcm4329, mmc, and PowerVR changes I ported.
FBis251 - updater-script updates bootlogos and testing!
If I'm missing anything, let me know!
As usual, the changelog for the kernel is here.
And the changelog for the initramfs is here.
No reason to duplicate the data here.
Get the latest release here.
To install:
Reboot to recovery
Install from sdcard
Enjoy
Note:
Your rom also must change to use wifi.
You will need to update /system/etc/wifi/wifi.conf, and replace anything that says 'dhd' with 'bcm4329'
Also the module path is: /lib/modules
instead of /system/lib/modules
Again, FBis251 has fixed the cwm updater-script in v2.5 to do this for you automatically. No need to manually do this anymore. But I left what it does here incase you need help.

If you had previously downloaded v2, please deleted it and download it again.
eollie found a bug with the initramfs, and it has been fixed.
Sorry for the inconvenience.
BUG: you have to try mounting rfs before you try mounting ext4

so ive noticed that there is no folder in the /lib/ called /moduels/, i should learn more about android, im coming from AntonX's basic w/ a twist 1.1.3, which has the DRIVER_MODULE_PATH location set to /lib/modules/*.ko, which is gone when i flashed this kernel, had to change to "DRIVER_MODULE_PATH=/lib/modules/bcm4329.ko", which isn't there... this is what my /system/etc/wifi/wifi.conf looks like:
FIRMWARE_LOADER=wlan_loader
DRIVER_PROP_NAME=wlan.driver.status
SUPPLICANT_NAME=wpa_supplicant
SUPP_PROP_NAME=init.svc.wpa_supplicant
MODULE_FILE=/proc/modules
IFACE_DIR=
DRIVER_MODULE_NAME=bcm4329
DRIVER_MODULE_TAG=bcm4329
FIRMWARE_LOADER=
SUPP_CONFIG_TEMPLATE=/system/etc/wifi/wpa_supplicant.conf
SUPP_CONFIG_FILE=/data/wifi/bcm_supp.conf
DRIVER_MODULE_PATH=/lib/modules/bcm4329.ko
MFGDRV_MODULE_ARG=firmware_path=/system/etc/wifi/bcm4329_mfg.bin nvram_path=/system/etc/wifi/nvram_mfg.txt
DRV_AP_MODULE_ARG=firmware_path=/system/etc/wifi/bcm4329_aps.bin nvram_path=/system/etc/wifi/nvram_net.txt
DRIVER_MODULE_ARG=firmware_path=/system/etc/wifi/bcm4329_sta.bin nvram_path=/system/etc/wifi/nvram_net.txt
DRIVER_APS_FIRMWARE_NAME=bcm4329_aps.bin
DRIVER_STA_FIRMWARE_NAME=bcm4329_sta.bin
INTERFACENAME=eth0
WAPI_SUPPORT=false
SUPP_CONF_FILEPATH=/data/misc/wifi/
SUPP_WAPI_AS_CERT_FILE_PATH=/data/misc/wifi/cert/as/
SUPP_WAPI_USER_CERT_FILE_PATH=/data/misc/wifi/cert/user/
SUPPLICANT_STATUS=wlan.supplicant.status
Click to expand...
Click to collapse
unable to turn wifi on, cleared cache and dalvik mutliple times in succession. im on AntonX's UVKJ6 1.1.3 barebone rom. any help?
Edit:
Probably not:
"DUH! the copy/paste action in the text editor added a space on both ends of the string
"DRIVER_MODULE_TAG= bcm4329 " -> "DRIVER_MODULE_TAG=bcm4329""
Definitely:
"DRIVER_MODULE_PATH=/system/modules/bcm4329.ko" -> "DRIVER_MODULE_PATH=/lib/modules/bcm4329.ko"
thanks!

xakuvo said:
so ive noticed that you also need to change the driver module location, im coming from AntonX's basic w/ a twist 1.1.3, which has the location set to /lib/modules/*.ko, this is what my /system/etc/wifi/wifi.conf looks like:
unable to turn wifi on, cleared cache and dalvik mutliple times in succession. im on AntonX's UVKJ6 1.1.3 barebone rom. any help?
Click to expand...
Click to collapse
Use the wifi.conf from here.

my logcat w/ "wifi" filter:
E/WifiSettingButton( 219): activate()
D/WifiManager( 219): setWifiEnabledDialog
W/System.err( 144): android.provider.Settings$SettingNotFoundException: wifi_enabled
W/System.err( 144): at com.android.server.WifiService.setWifiEnabledDialog(WifiService.java:540)
W/System.err( 144): at android.net.wifi.IWifiManager$Stub.onTransact(IWifiManager.java:209)
D/WifiService( 144): setWifiEnabledDialog: true
D/WifiService( 144): ****************setWifiEnabledDialog(), allowWifi****************true
I/WifiService( 144): setShowAccessPointListDialog():true
I/WifiService( 144): setWifiEnabledDialog(): true
E/wifi ( 144): android_net_wifi_set_talk_battery() connect=1
E/WifiHW ( 144): DRV_AP_MODULE_ARG.
E/WifiHW ( 144): WIFI_CONF_PATH. /system/etc/wifi/wifi.conf
E/WifiHW ( 144): DRIVER_MODULE_PATH. /system/modules/bcm4329.ko
I/WifiHW ( 144): [WIFI] Load Driver
I/WifiHW ( 144): ro.revision 48
E/WifiHW ( 144): [WIFI] Load Driver UNIV02 - CLK 37400
I/WifiHW ( 144): [WiFi.c] insmod() Start!!
E/WifiHW ( 144): insmod load_file "/system/modules/bcm4329.ko"
I/WifiHW ( 144): [WiFi.c] start init_module() Start!!
I/Kineto::wifi( 234): onReceive Enter
I/Kineto::wifi( 234): onReceive Exit
E/WifiSettingButton( 219): onReceive()-S:2
E/WifiHW ( 144): return of insmod (args:firmware_path=/system/etc/wifi/bcm4329_sta.bin nvram_path=/system/etc/wifi/nvram_net.txt) : ret = -1, Exec format error
E/WifiService( 144): Failed to load Wi-Fi driver.
I/Kineto::wifi( 234): onReceive Enter
I/Kineto::wifi( 234): onReceive Exit
E/WifiSettingButton( 219): onReceive()-S:4
Click to expand...
Click to collapse
error codes are in()? im trying my best to debug.
uuuhhh "/lib/" not "/system/" whops

xakuvo said:
my logcat w/ "wifi" filter:
Code:
E/WifiHW ( 144): DRIVER_MODULE_PATH. /system/modules/bcm4329.ko
error codes are in()? im trying my best to debug.
Click to expand...
Click to collapse
Pay attention to what I said in my previous post. Use the wifi.conf I provided.
If you have any more questions use the Q&A thread in the OP.

I tried deploying the wifi.conf suggested, and it didn't work.
ROM is ROM-sms-T959V-GB2.3.6-antsvx.1.1.3

galets said:
I tried deploying the wifi.conf suggested, and it didn't work.
ROM is ROM-sms-T959V-GB2.3.6-antsvx.1.1.3
Click to expand...
Click to collapse
It works just tried it to see.I have data and wifi with blastv2 using the wifi config provided by bh.
Sent from my Amazon Kindle Fire using xda app-developers app

I tried the provided wifi.conf, and WiFi does NOT work. ROM: AntonX's Barebones. Copied the file to /system/etc/wifi, flashed BlastOff, rebooted back - no WiFi.
Sent from my SGH-T959V using xda app-developers app

g4ry12 said:
I tried the provided wifi.conf, and WiFi does NOT work. ROM: AntonX's Barebones. Copied the file to /system/etc/wifi, flashed BlastOff, rebooted back - no WiFi.
Click to expand...
Click to collapse
So let me try to work through this, in order.
1) You got the working file.
2) You copied the working file to the phone.
3) You wiped out the working file by reflashing.
4) You rebooted and it didn't work.
Do you see two steps where the order looks reversed? Also... Questions, without logs, go in the Q/A thread.

Well, I was inder the impression that /system/etc/wifi/wifi.conf was the part of the ROM, not the kernel, and should not've been wiped by flashing a kernel.
Anyway, I tried flashing BlastOff first, and changing wifi.conf after, it did not help, still no WiFi.
It's not a question, it's a statement of fact, I flashed the kernel, I used the file, and got the WiFi error. I'm reporting an error, not asking for help.
Sent from my SGH-T959V using xda app-developers app

g4ry12 said:
Well, I was inder the impression that /system/etc/wifi/wifi.conf was the part of the ROM, not the kernel, and should not've been wiped by flashing a kernel.
Anyway, I tried flashing BlastOff first, and changing wifi.conf after, it did not help, still no WiFi.
It's not a question, it's a statement of fact, I flashed the kernel, I used the file, and got the WiFi error. I'm reporting an error, not asking for help.
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
I just flashed this and replaced the wifi.conf file as stated in the OP and can confirm that wifi does work. This includes wireless AP. Can you verify that you are replacing the the wifi.conf file in root/system/etc/wifi and not root/etc/wifi? That's the only obvious user error that I could see someone easily making. As for you not wanting help, well you're posting on a public forum where people come to help and be helped. That's the spirit of open source and XDA, if you don't want any help then I would humbly suggest not posting
Sent from my SGH-T959V using xda app-developers app

Check the md5 of the file in question on the phone against that supplied. md5 is the same for the same file if calculated on the phone, Windows, Linux, and whatever.
Posted from my SGS4G, thanks to Team Acid development

already forked and adding open source ipc to your bml repo should be up in a few.... or not lol... gotta make a few changes for the bml version

I redownloaded the provided wifi.conf using a PC, and finally made WiFi work.
The error was to create an empty wifi.com and copy-paste the content there That did not work, but the original file does.
By the way, I changed the conf file first, flashed the kernel second, and it still went fine, so it seems the order does not matter after all.
Thanks for the kernel! Proudly changed the signature

g4ry12 said:
...and copy-paste the content there That did not work, but the original file does.
Click to expand...
Click to collapse
Line endings and white-space differences have stumped even the most seasoned sysadmins and developers for years. There are at least four different line endings in use on various computer systems, and not all programs handle them gracefully.

Hey so why isn't there an easy to flash zip file that replaces wifi.conf for you? I'll work on this when I get home. I was seriously annoyed trying to edit the file without using adb.

FBis251, Thanks for the contribution! I'm sure many will be happy about this. I've modified FB's updater script to also just nuke the wifi directory, recreate it, and extract the stock wifi firmware and nvram files for /system/etc/wifi/. This should keep the wifi experience consistent.
The OP is updated.

Can't seem to get this flashed over hefe
Sent from my SGH-T959V using xda app-developers app

That's because this is a BML kernel, not a MTD kernel... as per the OP...

Update failing

I am trying to install the just released update from Verizon but I klept getting the message that the software failed. Do I need to unroot the device first?

You can keep root but make sure you have stock recovery otherwise the ota will fail.
Sent from my SGH-T999V using xda premium

shahkam said:
You can keep root but make sure you have stock recovery otherwise the ota will fail.
Sent from my SGH-T999V using xda premium
Click to expand...
Click to collapse
If I am running an unrooted VRBLI5 will OTA work to update to VRBLK3? I keep trying to check for a software update and it says that there is no new software update available.

The OTA will not show up unless you downgrade to VRALHE. Since VRBLI5 was not an official version it won't offer you the OTA. You could also upgrade to VRBLK3 using one of the guides in the development section which would probably be a lot easier.

fromaap integrable
BigErnM said:
The OTA will not show up unless you downgrade to VRALHE. Since VRBLI5 was not an official version it won't offer you the OTA. You could also upgrade to VRBLK3 using one of the guides in the development section which would probably be a lot easier.
Click to expand...
Click to collapse
Thanks so much for the quick response and for the insight - very appreciated. I was bummed when my wife got the OTA and I didn't! I will probably just upgrade to the new stock rather than downgrade and upgrade.

My completely stock S3 is failing checking for updates saying that the update service is not available. It doesn't seem to ever have been able to successfully check for updates (last checked time is blank).
I noticed the following in adb logcat when I tried to check for updates:
Code:
E/SyncmlDMGenericExtHandlerConnector( 1913): Can not route to Mobile Admin Network 64.186.176.220
However, on the phone, I can ping that IP address just fine, at the same time as it's supposedly trying to check for updates:
Code:
[email protected]:/ $ ping 64.186.176.220
PING 64.186.176.220 (64.186.176.220) 56(84) bytes of data.
64 bytes from 64.186.176.220: icmp_seq=1 ttl=248 time=61.6 ms
64 bytes from 64.186.176.220: icmp_seq=2 ttl=248 time=58.4 ms
64 bytes from 64.186.176.220: icmp_seq=3 ttl=248 time=56.5 ms
This happens on wifi or mobile data. Any suggestions on how to make this thing check for updates?
Thanks.
---------- Post added at 12:04 PM ---------- Previous post was at 12:02 PM ----------
The rest of the error:
Code:
D/ConnectivityService( 650): requestRouteToHostAddress on down network (10) - dropped
I/ ( 1913): HTTP: http_socket_connect ret:-1 Errno:115
I/ ( 1913): connect wouldblock: EINPROGRESS
D/memalloc( 340): ion: Allocated buffer base:0x42f61000 size:630784 fd:62
D/memalloc( 1913): ion: Mapped buffer base:0x5e66b000 size:630784 offset:0 fd:77
D/KeyguardViewMediator( 650): setHidden false
I/Adreno200-EGLSUB( 340): <CreateImage:893>: Android Image
I/Adreno200-EGLSUB( 340): <GetImageAttributes:1102>: RGBA_8888
D/KeyguardViewMediator( 650): setHidden false
I/ ( 1913): HTTP: SSL_CTX_load_verify_locations ret :0
I/ ( 1913): SSL_load_verify_locations failed
I/ ( 1913): HTTP: xaction 1574547464 ssl init error
I/ ( 1913): HTTP: status code 0
I/ ( 1913): [s]:[ERROR]:
I/ ( 1913): vendor/samsung/common/packages/apps/SyncMLSvc/native/syncmlcore/base/dm/src/tsldm_ses.cpp:Line:683 SesWaitForMsgSt:Error:9 happend while Recv Msg
I/ ( 1913):
I/ ( 1913): [s]:[ERROR]:
I/ ( 1913): vendor/samsung/common/packages/apps/SyncMLSvc/native/syncmlcore/base/dm/src/tsldm_ses.cpp:Line:788 Session Status :100663305
I/ ( 1913):
D/KeyguardViewMediator( 650): setHidden false
I/ ( 1913): shutdown Socket :50 return: 0
I/ ( 1913): HTTP: http_dispatch trans is already freed 5dd9b008

shahkam said:
You can keep root but make sure you have stock recovery otherwise the ota will fail.
As far as I know I have stock recovery. I did not flash a new ROM
Click to expand...
Click to collapse

I cant upgrade mine either, all I did was root
no unlocked bootloader, everything is stock
all stock apps are installed and running

Seems like lots of other Verizon customers are having the same problem. My phone is rooted, bootloader is unlocked and I have stock ROM

Please read forum rules before posting
Rule 15 tells you where to post if you are confused
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
And please search, this has been asked and answered several times

Problem with the Wi-Fi

Hi,
(First : I don't speak a lot of English and excuse me if I write some wrongs things on my posts )
I've got a big problem from some weeks, the Wi-Fi of my Xperia E3 doesn't work (he doesn't start and when he starts, he stops to find networks), sometime he works correctly and after sometime he stops with any reasons...
When I do
Code:
adb logcat
and I start Wi-FI by the notifications it's written :
Code:
D/WifiStateMachine( 1063): handleMessage: E msg.what=131083
D/WifiStateMachine( 1063): processMsg: InitialState
D/WifiHW ( 1063): Unable to unload driver module "wlan": No such file or directory
D/WifiService( 1063): setWifiEnabled: true pid=1178, uid=10026
E/WifiHW ( 1063): size = 6
E/WifiHW ( 1063): size = 29816
V/DexLibLoader( 5047): wrote 4968796 bytes to dex prog-a0af7cb08408279384aaa0ef36b024a6fdddb642.dex.jar
E/WifiStateMachine( 1063): Failed to load driver
D/WifiStateMachine( 1063): handleMessage: X
Thanks a lot for all the answers you will give me

toinedu27 said:
Hi,
(First : I don't speak a lot of English and excuse me if I write some wrongs things on my posts )
I've got a big problem from some weeks, the Wi-Fi of my Xperia E3 doesn't work (he doesn't start and when he starts, he stops to find networks), sometime he works correctly and after sometime he stops with any reasons...
When I do
Code:
adb logcat
and I start Wi-FI by the notifications it's written :
Code:
D/WifiStateMachine( 1063): handleMessage: E msg.what=131083
D/WifiStateMachine( 1063): processMsg: InitialState
D/WifiHW ( 1063): Unable to unload driver module "wlan": No such file or directory
D/WifiService( 1063): setWifiEnabled: true pid=1178, uid=10026
E/WifiHW ( 1063): size = 6
E/WifiHW ( 1063): size = 29816
V/DexLibLoader( 5047): wrote 4968796 bytes to dex prog-a0af7cb08408279384aaa0ef36b024a6fdddb642.dex.jar
E/WifiStateMachine( 1063): Failed to load driver
D/WifiStateMachine( 1063): handleMessage: X
Thanks a lot for all the answers you will give me
Click to expand...
Click to collapse
I have the same problem,
which rom are you using?

berni987654321 said:
I have the same problem,
which rom are you using?
Click to expand...
Click to collapse
Hey,
Before I was using the normal ROM, for the Xperia E3, and now I use this ROM : http://forum.xda-developers.com/xperia-e3/development/rom-t3067374
I'm still with this problem, but less than before (with the old ROM).

toinedu27 said:
Hey,
Before I was using the normal ROM, for the Xperia E3, and now I use this ROM : http://forum.xda-developers.com/xperia-e3/development/rom-t3067374
I'm still with this problem, but less than before (with the old ROM).
Click to expand...
Click to collapse
It seems to be a hardware issue even if the logcat(got the same) tells us it's a driver related thing.
Tried a lot of stuff and didn't give up yet, but if it is realy a hardware thing, I don't think I'll find a solution.
For me it started with not finding networks, then stoping to let me enable wifi from time to time and now
it's impossible for me to enable it.

berni987654321 said:
It seems to be a hardware issue even if the logcat(got the same) tells us it's a driver related thing.
Tried a lot of stuff and didn't give up yet, but if it is realy a hardware thing, I don't think I'll find a solution.
For me it started with not finding networks, then stoping to let me enable wifi from time to time and now
it's impossible for me to enable it.
Click to expand...
Click to collapse
Hey,
Do you try to enable the wi-fi (in the settings) and shutdown the phone, that work for me, when that don't work I enable the Wi-Fi, I open "Xposed" and I do a normal reboot of the phone, if the Wi-Fi is already enabled I just do a soft reboot.
Same if I resolve this problem, I've got a lot of others problem (I changed my display and I think I do some wrong things). I buy the Xperia E5 and I will receive him on the next week.

Try "wifi connection fixer" from Google play give it a try

[ROM & discussion][7.1.2_r11][Grouper|Tilapia][3May2017]AOSP - UNOFFICIAL

In Android ROMs' developments, I always start with AOSP. It is the root and if I want to do it right, I have to make it work for AOSP first. Putting the AOSP tests in my kernel thread is getting messy. As I would continue my work here for a while. Starting a thread for AOSP seems reasonable.
Here is for sharing of experiences and discussions.
There would be no nightly, weekly or monthy. I would follow the releases of AOSP and keep it as genuine as possible. If you are looking for a feature, there are many nice ROMs out there.
Known Issues:
　1. AOSP Camera App　The AOSP Camera2 app is not working with the Nexus 7 (2012) which is the only (I think) Nexus device with a Front Camera but not the Back Camera. The new Camera2 app set the back camera as default. I can make the preview shown by a simple overlay configs. But, make it really work would be quite a work. In the app market(s), there are many camera apps already taking care of that and would work flawlessly. I see no reason to waste time on that.​　2. "E:unknown command [log]"　If you got this message when flashing, don't panic. It's the new "block_image_update()" in recovery cause that. It would do no harm and it would be gone in the next TWRP.​　3 Please report.
Tips:
　1. DT2W　At deep sleep, the idled CPU takes time to resume. If the taps are too close, it might not be recognized. Delay the duration between taps would give you better results.​　2. Built-in File Explorer　There is an built-in file explorer in AOSP. We can explore the files as well as installing apks.
Its in: Settings > Storage > Explore (under the storage you want. In case of Nexus 7, only the internal and OTG exist.)​Change log:
Code:
[COLOR="Blue"]2017/5/3[/COLOR]
　- Android-7.1.2_r11 (NHG47L)
[COLOR="Blue"]2017/4/9[/COLOR]
　- Android-7.1.2_r5 (N2G47J)
　- PerformanceControl: boot up settings fixed
　- Fix Wifi hotspot
　- Performance patches
[COLOR="Blue"]2017/3/8[/COLOR]
　- Android-7.1.1_r28 (N6F26U)
[COLOR="Blue"]2017/2/8[/COLOR]
　- Android-7.1.1_r21 (NOF26W)
[COLOR="Blue"]2017/1/6[/COLOR]
　- Android-7.1.1_r13 (N6F26Q)
　- Camera: Fix video recording
[COLOR="Blue"]2016/12/16[/COLOR]
　- Android-7.1.1_r6 (NMF26Q)
　- SEPolicy update
[COLOR="Blue"]2016/12/7[/COLOR]
　- Android-7.1.1_r4 (NMF26O)
　- Fix the Camera
[COLOR="Blue"]2016/11/11[/COLOR]
　- Android-7.1.0_r7 (NDE63X)
[COLOR="Blue"]2016/10/24[/COLOR]
　- Android-7.1.0_r4 (NDE36P)
　- Remove every recovery related resources
[COLOR="Blue"]2016/10/14[/COLOR]
　- Android-7.0.0_r14 (NBD90Z)
　- Shield the occasional crash in MTP Document provider
　- USB and Bluetooth Tethering support enabled
[COLOR="Blue"]2016/9/23[/COLOR]
　- Android-7.0.0_r6 (NRD90U)
　- latest DC kernel (Android-7.0 branch)
　- PerformanceControl: version 2.1.6
　- Find a way to fix the hwcomposer for video/audio playback, need to review later
　- A few sepolicy patches for Gapps and Mediaserver
　- SELinux: Enforcing
Downloads: :highfive:
　Hosts: Android File Host　MEGA　mirror: 百度网盘
　Note: I only tested it in TWRP 3.0.2.
　 　 　PerformanceControl app requires ROOT access.
　 　 　Root access can be obtained by the systemless SuperSU from @Chainfire.
　Gapps: opengapps (pico) and BaNKs Gapps for 7.0 are tested
Sources:
　Sources in github
Credits: :good:
　** Definitely the AOSP
　** The AndroidFielHost provide a FREE host with no limits and expiration.
　** All the developers who help the Nexus 7 (2012) development
　** All those who donate and/or help the developers. Giving us the resources and reason to carry on.
Donations: :angel:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Discussions
Anyone has any idea are welcome to post here
DT2W
Sometimes it won't wakeup after a long DEEP_SLEEP
When volume buttons are also enabled for wakeup. It won't work too. Seems there are situations "soft pwr button press" won't work.
Fail after reboot
Code:
Supported API: 3
E: unknown fs_type "f2fs" for /cache
E: Can't mount /cache/recovery/last_locale
Some of you might encounter the above message after reboot. I never encountered before but there is definitely something wrong.
@millosr found that it was the recovery being replaced. I think that make sense and I want to study why.
I looked into the source. In the original AOSP, an OTA might come with a recovery patch. Stated in the build/core/Makefile "boot.img + recovery-from-boot.p + recovery-resource.dat = recovery.img"
It would generate the "recovery.img by the above formula itself. Custom ROMs usually won't carry a recovery and this part was usual ignored.
There is a warning in TWRP before reboot. Some of you might not read clearly and slide to continue immediately. In that case, the above mentioned recovery.img will be generated and flashed to the /recovery partition. Everything seems normal but after reboot.
When the script kick in, it would execute the "new" recovery. As a normal recovery, it would load the fstab and try to mount the partitions. The current fstab version is API 3. Almost all ROMs (no matter how close to AOSP) would have F2FS support. When we open a typical fstab:
Code:
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache f2fs noatime,nosuid,nodev,nodiratime,discard,inline_xattr,inline_data,inline_dentry wait,check
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 noatime,nosuid,nodev,nomblk_io_submit,journal_async_commit,errors=panic wait,check
Note that the second line is the declaration for the /cache in f2fs. Stock AOSP recovery doesn't support f2fs. That's why the above error shown. Since it fail to mount /cache, the last_locale is not loaded and recovery would hang.
How to recover?
Naturally, you have to flash TWRP again.
First of all, you need to boot into bootloader (fastboot mode)
Some init.xxx.rc might start adbd earlier and in this case "adb reboot bootloader" would do the job.
If adbd was not started before the hang, the command won't work. In this case you can only use the pwr+vol. down combination.
If it is still hanging, the buttons might not work. Press the power button continuously might lead to repeatedly reboot. It is better to make sure the device is OFF first.
1. Connect to a charger.
2. Press the power button until you see the charging image
3. Release the power button immediately.
4. After that, press the volume down button first, and then the power button.
It would go to the bootloader.
Note: /system is not really formatted during flashing. To make sure no residue left in /system, it is better to wipe the /system before flashing.
For ROM builders, there is a flag BOARD_USES_FULL_RECOVERY_IMAGE. Set it to true will stop the generation of recovery-resource.dat (in /system/etc) and break the above formula.

Does D2TW require the digitizer to remain permanently on? Trying to guage the impact of such a feature before I turn it on.

Nintonito said:
Does D2TW require the digitizer to remain permanently on? Trying to guage the impact of such a feature before I turn it on.
Click to expand...
Click to collapse
obviously.
---------- Post added at 09:52 AM ---------- Previous post was at 09:46 AM ----------
@daniel_hk good to see a separate thread. Will test this build this weekend as i am already on grouper.

：手指划线：

Thanks for bringing nougat to our beloved Nexus 7!!!
I just flashed but no matter which gapps I use, I can't make playstore and google play services installed.
Any hints?
Thanks.

ho0o0o11111 said:
Thanks for bringing nougat to our beloved Nexus 7!!!
I just flashed but no matter which gapps I use, I can't make playstore and google play services installed.
Any hints?
Thanks.
Click to expand...
Click to collapse
If you want anyone to help, you have to provide details.
The tested Gapps' are listed in OP. "No matter which gapps" ?
Can you tell us which one and version you actually tried?
What's your flashing procedures? etc.

daniel_hk said:
If you want anyone to help, you have to provide details.
The tested Gapps' are listed in OP. "No matter which gapps" ?
Can you tell us which one and version you actually tried?
What's your flashing procedures? etc.
Click to expand...
Click to collapse
Procedures (clean flash)
- rom
- gapps
- supersu
- reboot
- no playstore/play services have been installed after reboot
I used explorer to check and found that those gapps are installed (e.g. Vending.apk) but their sizes are all in 0kb.
the gapps I used were opengapps PICO and Banks. (I tried both. All after clean flash)
Finally I got playstore installed as follows
- flash rom/gapps/supersu
- reboot
- uninstall some system apps I don't need
- flash gapps again
then the playstore appears in app drawer. (And it works)
However, I have another big problem after reboot.
My device is now stuck in bootloop after splashscreen.
It just shows message as follows and I can't enter recovery/bootloader.
Supported API: 3
E: unknown fs_type "f2fs" for /cache
E: Can't mount /cache/recovery/last_locale
In the following page I found a solution "adb reboot bootloader" but I can't even enter bootloader/fastboot mode.
http://forum.xda-developers.com/nex...ip-linux-tegra-nv-3-4-bringup-t3128195/page46
still trying...
Any helps would be appreciated.
Thanks.

ho0o0o11111 said:
Procedures (clean flash)
- rom
- gapps
- supersu
- reboot
- no playstore/play services have been installed after reboot
I used explorer to check and found that those gapps are installed (e.g. Vending.apk) but their sizes are all in 0kb.
the gapps I used were opengapps PICO and Banks. (I tried both. All after clean flash)
Finally I got playstore installed as follows
- flash rom/gapps/supersu
- reboot
- uninstall some system apps I don't need
- flash gapps again
then the playstore appears in app drawer. (And it works)
However, I have another big problem after reboot.
My device is now stuck in bootloop after splashscreen.
It just shows message as follows and I can't enter recovery/bootloader.
Supported API: 3
E: unknown fs_type "f2fs" for /cache
E: Can't mount /cache/recovery/last_locale
In the following page I found a solution "adb reboot bootloader" but I can't even enter bootloader/fastboot mode.
http://forum.xda-developers.com/nex...ip-linux-tegra-nv-3-4-bringup-t3128195/page46
still trying...
Any helps would be appreciated.
Thanks.
Click to expand...
Click to collapse
I think you are not using the Official TWRP. There are similar reports having the same problem for other MM ROMs too.
You may try the Official TWRP 3.0.2 here (follow the link if you have a Tilapia) and flash everything again.
You might have corrupted your /cache and /data. It is better format them (to ext4 or f2fs) in the Official TWRP again.
Good luck!

daniel_hk said:
I think you are not using the Official TWRP. There are similar reports having the same problem for other MM ROMs too.
You may try the Official TWRP 3.0.2 here (follow the link if you have a Tilapia) and flash everything again.
You might have corrupted your /cache and /data. It is better format them (to ext4 or f2fs) in the Official TWRP again.
Good luck!
Click to expand...
Click to collapse
Thanks for your suggestion but the TWRP I used were downloaded from TWRP's official website, so I supposed it is official version.
I can't flash TWRP again as I am still struggling to enter bootloader mode.

ho0o0o11111 said:
Thanks for your suggestion but the TWRP I used were downloaded from TWRP's official website, so I supposed it is official version.
I can't flash TWRP again as I am still struggling to enter bootloader mode.
Click to expand...
Click to collapse
Which version? eariler version might have a wrong fstab which have issue on f2fs.
Make sure you got the latest version 3.0.2
You can't go to boot loader?
That means you press pwr+vol down and it won't reboot to bootloader?
That's strange.
"adb reboot bootloader" only work if the adbd is up. That means you can use "adb devices" to check the existance of your device.
You may try this:
1. connect to the charger
2. pressing the pwr button for > 8 seconds.
See if the tablet reboot. If yes, it would boot into charging mode. Pwr+vol down again would work.
If it doesn't reboot after you pressed say 20 seconds, you need to remove the battery.
Good luck!

@daniel_hk
Thanks for the new AOSP build Daniel. Nice work fixing the hardware decoder, my Netflix is now working and I was able to play one of my MP4 movies with BS Player in HW mode. I've been changing back and forth between your first AOSP 7 build and your DU 7 build with dirty flashes. With this build I decided to clean flash and at first things were very sluggish but settled down after a reboot and probably after Google finished whatever it does in the background. LOL Aside from a few occasional random force closes, it's running pretty well.
A couple of observations:
As mentioned, I did a clean install with this build. I'm using official TWRP 3.02 and installed the rom and 7.0 Open Gapps nano 20160915 at the same time and when it booted up for the first time, there were no gapps installed. I powered down and then went back into TWRP and reflashed the gapps, this time they were there upon reboot. Surprisingly, I didn't have to set permissions for Google Play or Play Store, as they were already correctly set??? I did run into a snag when trying to download apps from PS, clearing the data for the download manager app solved that problem for me.
I installed a camera app (HD Camera) from Play Store and it works but when I use my phone's camera, it reminds me how crappy the N7 camera is. LOL
After setting things up, I wanted to try phhsuperuser (no Magisk) to root and it went fine. All of my apps that require root worked...except Titanium Backup. I tried uninstalling/reinstalling both phhsuperuser and Titanium but couldn't get it to work. I rely on Titanium quite a bit, so I flashed Supersu 2.78 and all's well.
Thanks again.
Mike T

Do games work on this rom?

Hi,
This is the best 7.0 ROM so far !!!
Smooth, video HW decoding is working, games work perfect.
As webdroidmt said I also had to reflash GAPPS to have GAPPS installed and i had to give proper permissions on Google Play service to stop seeing the "google play service stop" message.
All Apps/games that i installed are working properly.
Thanks Daniel_hk for your work

Many thanks Works like a charm !
Is SEpolicy restrictive in your build? (I cannot see it from Settings -> about tablet)
.
Can you post your manifest on Your Github for easier building ?

Hi, currently testing your ROM, looks awesome!
When Browsing the web with Chrome, loads and loads of SELinux denials, mostly when the page loads:
Code:
09-26 13:34:20.990 4424 4424 W Thread-4: type=1400 audit(0.0:174): avc: denied { ioctl } for path="socket:[45348]" dev="sockfs" ino=45348 ioctlcmd=8b1b scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:untrusted_app:s0:c512,c768 tclass=udp_socket permissive=0
This message times * 100 for every page load.

paasoares said:
Hi,
This is the best 7.0 ROM so far !!!
Smooth, video HW decoding is working, games work perfect.
As webdroidmt said I also had to reflash GAPPS to have GAPPS installed and i had to give proper permissions on Google Play service to stop seeing the "google play service stop" message.
All Apps/games that i installed are working properly.
Thanks Daniel_hk for your work
Click to expand...
Click to collapse
In any case, it's a good practice to read the console after flash anything. There might already be essential messages which not necessarily in red.
I also experience SuperSU need to flash again. I just found out something that might help. Seems SuperSU would use the cache to start a checking process in the next boot. I don't know if it would help gapps too.
1. Try factory reset before flashing.
2. Flash ROM+Gapps+SuperSU
3. After that don't do wipe cache/d-cahce again. (factory reset already include this action)
Good luck!
3yan said:
Many thanks Works like a charm !
Is SEpolicy restrictive in your build? (I cannot see it from Settings -> about tablet)
.
Can you post your manifest on Your Github for easier building ?
Click to expand...
Click to collapse
I think you meant "Enforcing". Yes, it is enforcing. Only some Custom ROM would show this in About but not AOSP.
There is a shell command "getenforce" which you can check the SEPolicy status.
If you read the OP, you would know its an AOSP without any mod/tweak, just porting. You can get the manifest and all the helps in https://source.android.com.
Good luck!
fat-lobyte said:
Hi, currently testing your ROM, looks awesome!
When Browsing the web with Chrome, loads and loads of SELinux denials, mostly when the page loads:
Code:
09-26 13:34:20.990 4424 4424 W Thread-4: type=1400 audit(0.0:174): avc: denied { ioctl } for path="socket:[45348]" dev="sockfs" ino=45348 ioctlcmd=8b1b scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:untrusted_app:s0:c512,c768 tclass=udp_socket permissive=0
This message times * 100 for every page load.
Click to expand...
Click to collapse
Chrome has many versions and it should not be an untrusted app. I'm testing the CarbonROM which has a bloated Chrome and being treated as isolated app. It might take time for those UID's being properly handled.
I already included some extra permissions which would be include in my later builds.
Anyway, we would encounter denials more often in apps. That's what newer Android intent to do.

Code:
09-26 19:14:02.119 189 344 D hwcomposer: hotplug_thread: processing control fd
09-26 19:14:02.119 189 344 I hwcomposer: hotplug: connected = 0
09-26 19:14:03.469 503 579 W AlarmManager: Unrecognized alarm listener [email protected]
09-26 19:14:03.469 503 579 E WifiScanner: listener cannot be found
09-26 19:14:03.478 677 677 E wpa_supplicant: wlan0: Failed to schedule PNO
09-26 19:14:03.481 503 581 E SupplicantWifiScannerImpl: PNO state change to true failed
09-26 19:14:03.481 503 581 E SupplicantWifiScannerImpl: Failed to start PNO scan
09-26 19:14:03.484 503 581 W SupplicantWifiScannerImpl: No PNO scan running
09-26 19:14:03.486 503 579 E WifiConnectivityManager: PnoScanListener onFailure: reason: -1 description: pno scan failed
This is repeated every 5 minutes during deep sleep. I'm not an expert, but this probably doesn't help with battery drain
I'm also having some touch sensitivity issues when coming out of deep sleep or off the charger. I have to do some more testing, then I will have more details.

I wanted to try this 'Sept 23' ROM as it should play video OK: in the end I got it to work, and I can now indeed play video in some video based apps that did not work before. I used the older DU ROM and also the nAOSP ROM of millosr. There video does not work yet.
But with this Sept23 ROM I had a fight with Gapps to get it to work... First the Gapps I normally use failed to install in TWRP. At least, that is what I think I saw: the progress bar suddenly jumps ahead as if the install process was broken off somehow. So I again clean wiped all and now used opengaps-pico. That installed fine, but on first boot, no gapps. So I again installed opengapps and now finally I had working playstore. Strange, I never ran into something like this before (I am mostly active on Xperia S with nAOSP).
But the story ends well, as my video now works: great job !

fat-lobyte said:
Code:
09-26 19:14:02.119 189 344 D hwcomposer: hotplug_thread: processing control fd
09-26 19:14:02.119 189 344 I hwcomposer: hotplug: connected = 0
09-26 19:14:03.469 503 579 W AlarmManager: Unrecognized alarm listener [email protected]
09-26 19:14:03.469 503 579 E WifiScanner: listener cannot be found
09-26 19:14:03.478 677 677 E wpa_supplicant: wlan0: Failed to schedule PNO
09-26 19:14:03.481 503 581 E SupplicantWifiScannerImpl: PNO state change to true failed
09-26 19:14:03.481 503 581 E SupplicantWifiScannerImpl: Failed to start PNO scan
09-26 19:14:03.484 503 581 W SupplicantWifiScannerImpl: No PNO scan running
09-26 19:14:03.486 503 579 E WifiConnectivityManager: PnoScanListener onFailure: reason: -1 description: pno scan failed
This is repeated every 5 minutes during deep sleep. I'm not an expert, but this probably doesn't help with battery drain
I'm also having some touch sensitivity issues when coming out of deep sleep or off the charger. I have to do some more testing, then I will have more details.
Click to expand...
Click to collapse
Did you set "keep wi-fi on during deep sleep" to NEVER?
My tablet drain 5% during this night (about 8 hours), so i guess this is normal/acceptable