Database Users

Someone for building me a very simple app?

Hey guys,
i'm looking for someone who can build me a little app that simply redirects me to the "mobile network settings" page.
Probably, that's very simple and I can do this for myself but i haven't installed the SDK and also I haven't programmed for Android before.
I needn't to be a widget, a shourcut on homescreen without an icon would be absolutly OK.
There are some widgets in market but they caused some strange bugs on my LG P500
If there is someone who can spend some time for me, it would be great
Sorry for my english, i'm german...

Hey,
for some reason, I couldn't get the intent to work properly so I just made it so they app runs an am command in the shell. It should work though. Let me know if there are any problems.
Also, your english is fine. There are so many people here who are about 1000 times worse..

Works fine on first startup, but on relaunch there is only a blank activity with the programm title on top and I have to close the app manually with a task manager
Is there any possibility to fix this?

singmea1337 said:
Works fine on first startup, but on relaunch there is only a blank activity with the programm title on top and I have to close the app manually with a task manager
Is there any possibility to fix this?
Click to expand...
Click to collapse
Harr then let me take a shot at it .
.apk file is in attachment, let me know if it does what you wanted.
If it does it, i will be happy with a thanks!
und dein Englisch ist ok...

oh right, of course. That makes sense. I really didn't go about this the right way. Maybe someone else can come up with a better solution. Anyway, I updated it so the issue you were describing won't happen. However, now you can't back out of the application. As soon as you back out of the mobile network settings, my app comes back into focus and starts the mobile network settings again. I'm sure there's an easy fix. Maybe I'll look at it again after work.

okay, I wasn't thinking straight before. There was an extremely easy solution. Dark3n has probably already done it but whatever.

smaskell said:
oh right, of course. That makes sense. I really didn't go about this the right way. Maybe someone else can come up with a better solution. Anyway, I updated it so the issue you were describing won't happen. However, now you can't back out of the application. As soon as you back out of the mobile network settings, my app comes back into focus and starts the mobile network settings again. I'm sure there's an easy fix. Maybe I'll look at it again after work.
Click to expand...
Click to collapse
it is quite easy, let me help you out
if you have questions, feel free to ask
Code:
package eu.thedarken.nsq;
import android.app.Activity;
import android.content.ComponentName;
import android.content.Intent;
import android.os.Bundle;
public class NSQmain extends Activity {
/** Called when the activity is first created. */
@Override
public void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
//setContentView(R.layout.main);
Intent intent = new Intent(Intent.ACTION_MAIN, null);
intent.addCategory(Intent.CATEGORY_LAUNCHER);
ComponentName cn = new ComponentName("com.android.phone","com.android.phone.Settings");
intent.setComponent(cn);
intent.setFlags(Intent.FLAG_ACTIVITY_NEW_TASK);
startActivity(intent);
finish();
}
}

@smaskell
Now, there is only an black screen after the first launch.
But the solution by Dark3n works like a charm
Thanks!
edit:
Oh, too slow, i'm talking of post 5

As I told you already, the widgets I tested caused some bugs. The app from Dark3n got the same issue.
If I change network mode to 2G only, the telephone app crashes without any comments after clicking the call-button. That couldn't be normal?
I've tested this one (couldn't post direct links, search com.curvefish.widgets.network2g3gonoff on market) before and if I clicked on the widget (after such a crash) the call was started
The same thing happens if i launch the app from Dar3n directly from menu but not if i use the shortcut.
If I change the mode directly via menu or using this (de.softxperience.android.switchnetworktype) app there are no problems.
But the last linked app adds a shortcut on the status-bar drop-down and in my opinion that's stupid.
I've checked the app from smaskell but there's still a problem on relaunch...
edit: And there's the same problem..
Sorry for the double-posting..

I will take a look at that later in the evening.
Maybe the settings only gets saved properly after closing parent menus.
By directly calling the submenu this doesn't happen and thats why it FCs.

I dont know if this will help you, but you can start the setting via terminalemulator
Code:
am start -n com.android.phone/.Settings
Sent from my HTC Vision using XDA App

kingchris said:
I dont know if this will help you, but you can start the setting via terminalemulator
Code:
am start -n com.android.phone/.Settings
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Thats basicly how i start it too.

Building App: Buttons & Slider to send serial commands to wifi or BT connection
Ops, sorry, thought I was posting in a new thread. Didn't want to take over yours.

Cant you just use anycut and point it to the right activity?
Sent from my GT-I9100 using XDA App

[DEV] Working HTC touchscreen driver fix for ICS, no porting necessary

Alright. Well. This is interesting.
I've fixed the original HTC touchscreen driver for use in ICS. I'm assuming it will work on other HTC phones as well, since the fix is FAR less intrusive in terms of changing existing code, or trying to port other drivers.
I was working on trying to map out the Samsung and HTC drivers in terms of data they let the system see as they are running. Getting no where fast, I remembered a couple days ago when I was attempting to get the touch keys working with the Samsung driver. Originally, I had added this code to the mxt224 driver above the line 'set_bit(EV_ABS, ts->input_dev->evbit);':
added to mxt224.c
Code:
set_bit(EV_SYN, ts->input_dev->evbit);
set_bit(EV_KEY, ts->input_dev->evbit);
set_bit(BTN_TOUCH, ts->input_dev->keybit);
set_bit(BTN_2, ts->input_dev->keybit);
I assumed this may have something to do with the softkeys, since it was present in the HTC driver with all four lines. By this I mean that in the HTC driver, that section looked like this:
atmel.c
Code:
set_bit(EV_SYN, ts->input_dev->evbit);
set_bit(EV_KEY, ts->input_dev->evbit);
set_bit(BTN_TOUCH, ts->input_dev->keybit);
set_bit(BTN_2, ts->input_dev->keybit);
set_bit(EV_ABS, ts->input_dev->evbit);
It worked fine in CM7 after doing this, but I lost all touchscreen in ICS, with it not even registering touch data anymore.
Back to my main point, I decided to see what would happen if I totally removed those four lines from the atmel.c file (HTC driver) and see what happens in ICS. Long story short, it works. Apparently ICS doesn't use or absolutely hates one or all four of those input preprocessors. So yeah I kinda **** bricks that it was that simple.
I'm going to try to see if its one or just all of these keybits that's causing the problem and I'll report back.
Instructions
If you want to try this, follow along:
Get rid of build settings for the Samsung driver if you've been messing with that
open up our favorite driver driver/input/touchscreen/atmel.c
CRTL+F, search for EV_SYN
Comment or delete all of the set_bit() lines except for the last one, EV_ABS
Your atmel.c should only have this line now, where all five were before:
Code:
set_bit(EV_ABS, ts->input_dev->evbit);
Clean your make environment and make sure your config files are set to use atmel-touchscreen
**** bricks

so it should look like:
Code:
ts->input_dev->name = "atmel-touchscreen";
// set_bit(EV_SYN, ts->input_dev->evbit);
// set_bit(EV_KEY, ts->input_dev->evbit);
// set_bit(BTN_TOUCH, ts->input_dev->keybit);
// set_bit(BTN_2, ts->input_dev->keybit);
set_bit(EV_ABS, ts->input_dev->evbit);
?

twistedumbrella said:
so it should look like:
Code:
ts->input_dev->name = "atmel-touchscreen";
// set_bit(EV_SYN, ts->input_dev->evbit);
// set_bit(EV_KEY, ts->input_dev->evbit);
// set_bit(BTN_TOUCH, ts->input_dev->keybit);
// set_bit(BTN_2, ts->input_dev->keybit);
set_bit(EV_ABS, ts->input_dev->evbit);
?
Click to expand...
Click to collapse
Yeah try that. I've run into something though, which must be something stupid I'm doing but I can't figure out what the hell it is.
I've gone through each of those that I commented out to see if it was just one of the set_bits that was making it not work. But even with them all on now it's still working in ICS. I've cleaned my builds between each time. I think I'm going crazy! Because it didn't work before!

swm5126 said:
Yeah try that. I've run into something though, which must be something stupid I'm doing but I can't figure out what the hell it is.
I've gone through each of those that I commented out to see if it was just one of the set_bits that was making it not work. But even with them all on now it's still working in ICS. I've cleaned my builds between each time. I think I'm going crazy! Because it didn't work before!
Click to expand...
Click to collapse
I'm building now and I will see what I can find out. It might be as simple as it forced the build to refresh in some way? Ill see what happens and let you know.

I'm already engaged, but I think she will understand... Will you marry me? haha, it worked!
And then I see this : http://android.modaco.com/topic/348194-04-nov-icl23d-galaxy-nexus-boot-recovery-system-dump/

Can you post the zip with it working? Please

w9jds said:
Can you post the zip with it working?
Click to expand...
Click to collapse
http://dl.dropbox.com/u/11023553/imoseyon_leanKernel_184Mhz_vAOSP.zip
That is the Thunderbolt version
swm5126, I cannot than you enough for all the help. I really wouldn't have gotten anywhere without it. Least we can toast to a success!
But I am still looking into what needs to be commented, just a little excited to actually touch ICS. lol.

twistedumbrella said:
I'm already engaged, but I think she will understand... Will you marry me? haha, it worked!
And then I see this : http://android.modaco.com/topic/348194-04-nov-icl23d-galaxy-nexus-boot-recovery-system-dump/
Click to expand...
Click to collapse
Unfortunately I'm engaged too, so no dice!
Can't wait to take a look at those
Quick question, does your pointer in ICS seem to go back up to the top left hand corner of the screen? Or aren't you in pointer mode?

for me it does!!
but I still can't unlock the F screen...

LorD ClockaN said:
for me it does!!
but I still can't unlock the F screen...
Click to expand...
Click to collapse
Awesome! Glad I'm not crazy and this works. They must have deprecated some of the input preprocessors. I'm just surprised using them in the driver basically made the touchscreen inoperable in ICS.
One step closer...to something! Now to figure out those pesky idc files to get this to work without the pointers.

maybe better to focus on Paul's dump.. could be different regarding TS

My post for the stuff inside the new idc configurations system is here http://forum.xda-developers.com/showthread.php?t=1320170&page=16
hope it helps

swm5126 said:
Awesome! Glad I'm not crazy and this works. They must have deprecated some of the input preprocessors. I'm just surprised using them in the driver basically made the touchscreen inoperable in ICS.
One step closer...to something! Now to figure out those pesky idc files to get this to work without the pointers.
Click to expand...
Click to collapse
It reverts to the corner. I am working on a fix for that right now. Congrats, btw.
w9jds said:
My post for the stuff inside the new idc configurations system is here http://forum.xda-developers.com/showthread.php?t=1320170&page=16
hope it helps
Click to expand...
Click to collapse
What he said, lol
Sent from my ADR6400L using Tapatalk

LorD ClockaN said:
maybe better to focus on Paul's dump.. could be different regarding TS
Click to expand...
Click to collapse
Trying to haha filesonic is only letting me get one file at a time *sigh*

I already downloaded those.. I have a paid acount for filesonic
I posted this in DHD thread also:
my Touchscreen works, but it doesn't unlock anything... I mean, I pull the ring to unlock icon, it vibrates and it doesn't change screen..
so I unlock screen with adb shell, and when it gets unlocked I'm welcomed with SystemUi FC.. and every time like that.. if I turn off screen and back ON after trying to unlock screen, my touches are not working.. it must be because systemui already crashed... but it doesn't show it..

LorD ClockaN said:
I already downloaded those.. I have a paid acount for filesonic
I posted this in DHD thread also:
my Touchscreen works, but it doesn't unlock anything... I mean, I pull the ring to unlock icon, it vibrates and it doesn't change screen..
so I unlock screen with adb shell, and when it gets unlocked I'm welcomed with SystemUi FC.. and every time like that.. if I turn off screen and back ON after trying to unlock screen, my touches are not working.. it must be because systemui already crashed... but it doesn't show it..
Click to expand...
Click to collapse
With the fix from here for the driver? Or without anything?

with your fix here

Awesome! Now if only I could find someone to reverse engineer the 3D camera and Gallery for the HTC Evo 3D, I would be fat from all the Ice Cream Goodness I would be devouring! Good job guys

I got money for whomever gets a decent working (radio, touch screen, texts) ICS DINC build by the end of this weekend.....

wetbo529 said:
I got money for whomever gets a decent working (radio, touch screen, texts) ICS DINC build by the end of this weekend.....
Click to expand...
Click to collapse
Can we not do that? That's how things get sloppy. Just donate it to swm, he deserves it.
Sent from my ADR6400L using Tapatalk

[Q] 'Add To Split View' Not Working on Nexus 7 2013

Hey everyone,
I tried both the alpha and nighly builds of Omnirom for the Nexus 7 2013 flo. I am using the flow build. When I flashed it, I opened two apps, went to the Recent Apps, long pressed the app I wanted to add. Lo and behold 'Add to Split View' wasn't there. I have tried it with one of the apps open on the screen, I have tried it on the home screen and the add to split view will not appear. Anyone know what's going on here? I have seen other people on the Omnirom Nexus 7 2013 thread saying it works for them.

ezio2altair said:
Anyone know what's going on here?
Click to expand...
Click to collapse
Yeah, we know.
Multi Window feature has not yet been merged into Omnirom repo.

chasmodo said:
Yeah, we know.
Multi Window feature has not yet been merged into Omnirom repo.
Click to expand...
Click to collapse
Yup, which means you won't see it in any autobuild. (Unless the guys working on autobuild add the ability to do "experimental" builds that cherry-pick items from gerrit)
As to why it's not merged - still work to be done. It mostly works, but there are remaining issues. For example we need to either figure out how to fix G+ layout, blacklist G+ and any other apps known to misbehave, or implement a whitelist similar to Samsung's only allowing apps known to work. (If we do a whitelist, there needs to be a good way to add overrides/add to the whitelist as more people report compatible apps.)

Use pencil or any metal object as stylus on Galaxy S2 [Just like S5/Z Ultra/ Z1]

As you all know, Samsung has made a list of hidden features and one of them is where you can enable a pencil as stylus for you phone. This was USP of Xperia Z Ultra too and was also enabled via root on Xperia Z1.
But it looks like this feature will work on S2 too.
Requirements: [This was tested on SlimSaber running 4.4.2]
Any of the following:
1. Any AOSP based ROM which has the Galaxy S2 device setting included. OR
2. Any Sammy based ROM with Galaxy S2 device setting included (anyone confrim this is possbile?) OR
3. Any custom kernel which has option to change screen sensetivity (someone kindly suggest if this too is possbile)
What should be done? - Basically we need to increase the screen sensitivity
1. Open up the device settings. This can be in the app drawer depending on your ROM or integrated to the system settings. For example, in the in SlimSaber it is under: Settings - Advanced options - Device
2. Go to the "Screen" tab
3. Under "Touch sensitvity" change the value to "10"
4. Now try with pencil or any metal objects and have fun.
To quickly revert to default sensitivity turning off the screen does the job. This could be a bug.
Issues:
1. The sensitivity reverts back to default after screen off. At least in SlimSaber 4.4.2. The value will remain on 10, but i will need to tap on it again manually.
2. This will not work when the device in plugged into charger.
2. You need to go to all the way to the device setting screen each and every time. The screen is hyper sensitive for fingers when it is set to 10.
3. Of course, the screen is not as good as you to write down notes with handwriting like in Galaxy Note phones. But it is kinda cool to show it off.
3. The screen will get dirty Please don't use the phone while having food. Lead is bad for health
Video:
I am not sure whether screen sensitivity option is available for other phones like S3, S4 or other OEM too. If anyone know a way and have tried, let us know in the post.
Have you felt good about still holding on to Galaxy S2 yet?

Discovered so late

Awesome working .. Really appreciated dev works.
Just a question can we use it in stock s2 roms ?

kachrukamble said:
Discovered so late
Click to expand...
Click to collapse
I would not have discovered it if S5 hidden feature list was not announced. I have been using the high screen sensitivity option in AOSP from long time. Who knew it would do the trick

exynoss said:
Awesome working .. Really appreciated dev works.
Just a question can we use it in stock s2 roms ?
Click to expand...
Click to collapse
Yes. All credits go to the CM team who developed the Galaxy S2 device settings back in ICS days. This would not been possible the easy way without their app.
I have not used the stock ROM for a long time. The device settings was an app back in ICS days. Someone can try sideloading the app to stock ROM and see if it works. Or may be any custom kernel has this screen sensitivity feature?

Harsha Raj said:
Or may be any custom kernel has this screen sensitivity feature?
Click to expand...
Click to collapse
Ye right i guess I saw somewhere that screen sensitivey option in Kernel tweakers app. Will search for it

Eureka!!! After 2 yrs of s2 use, u have discovered something in it
Sent from my SM-N900 using Tapatalk

The DeviceSettings app writes the value selected for touch sensitivity to the following file to be picked up by the kernel:
Code:
/sys/class/sec/sec_touchscreen/tsp_threshold
Maybe some sort of scripting utility or tasker could help with rewriting the value to the file when the screen turns on and possibly save you having to go back in to force the update through the app??

AuSSiELaMbChOpS said:
The DeviceSettings app writes the value selected for touch sensitivity to the following file to be picked up by the kernel:
Code:
/sys/class/sec/sec_touchscreen/tsp_threshold
Maybe some sort of scripting utility or tasker could help with rewriting the value to the file when the screen turns on and possibly save you having to go back in to force the update through the app??
Click to expand...
Click to collapse
Thanks for the heads up. I'm no developer. I hope someone can make this, if possible. Tasker plugin app would be a best bet because I think scripts are good only at time of boot.
Sent from my GT-I9100 using Tapatalk

Harsha Raj said:
Thanks for the heads up. I'm no developer. I hope someone can make this, if possible. Tasker plugin app would be a best bet because I think scripts are good only at time of boot.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
I was thinking a little different to a addon.d script I believe Script Manager allows you to save a script then run it via a widget, there are probably other options as well but I remember SManager from using it a longtime ago.
Sent from my GT-I9100 using XDA Premium 4 mobile app

Harsha Raj said:
3. The screen will get dirty Please don't use the phone while having food. Lead is bad for health
Click to expand...
Click to collapse
its graphite/carbon, not lead. its not bad for your health.

AuSSiELaMbChOpS said:
I was thinking a little different to a addon.d script I believe Script Manager allows you to save a script then run it via a widget, there are probably other options as well but I remember SManager from using it a longtime ago.
Sent from my GT-I9100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes the app looks like it has many features. Hope someone can make it.
At default 50, my S2 screen has sensitivity issues o occasionally. Even if I decrease the value it's only until screen off.
The Jack of Clubs said:
its graphite/carbon, not lead. its not bad for your health.
Click to expand...
Click to collapse
Apparently my school teacher years back had different opinion. I stand corrected
Sent from my GT-I9100 using Tapatalk

Couldn't find the setting in Carbon Rom, musn't have included it. Too bad.

Pyvesb said:
Couldn't find the setting in Carbon Rom, musn't have included it. Too bad.
Click to expand...
Click to collapse
Maybe you can ask in the ROM thread if its buried somewhere else. Here is the device settings apk link from google search. But it did not install in mine, nor it worked when i side loaded it. https://code.google.com/p/slimics28/downloads/detail?name=GalaxyS2Settings.apk

Tried this one in NeatROM (Stock JB-Based) with Apolo Kernel and it worked, but it's seems too uncontrollable...
I made a script of the tsp_threshold value changing to 10, ran it, and tested my regular ballpen on it (empty, of course) and it worked, but most of the time, it won't detect the ballpen when I tried tapping it to type on a soft keyboard.
But when I do gestures like sliding and dragging, it works, though.
Is it safe to change the threshold to 5? I can't do it because I'm scared I might mess up some sh*t.
And also, I think when observed, that the threshold resets from 10 to 40 (my default) when screen turns off, since when I tried screen-off, then on, the touchscreen won't detect my ballpen anymore, and I have to re-run the script to do it again...

Harsha Raj said:
Maybe you can ask in the ROM thread if its buried somewhere else. Here is the device settings apk link from google search. But it did not install in mine, nor it worked when i side loaded it. https://code.google.com/p/slimics28/downloads/detail?name=GalaxyS2Settings.apk
Click to expand...
Click to collapse
Nope, app doesn't even want to install on KitKat. I'll try asking on the main thread as you recommanded.

souler456 said:
Tried this one in NeatROM (Stock JB-Based) with Apolo Kernel and it worked, but it's seems too uncontrollable...
I made a script of the tsp_threshold value changing to 10, ran it, and tested my regular ballpen on it (empty, of course) and it worked, but most of the time, it won't detect the ballpen when I tried tapping it to type on a soft keyboard.
But when I do gestures like sliding and dragging, it works, though.
Is it safe to change the threshold to 5? I can't do it because I'm scared I might mess up some sh*t.
And also, I think when observed, that the threshold resets from 10 to 40 (my default) when screen turns off, since when I tried screen-off, then on, the touchscreen won't detect my ballpen anymore, and I have to re-run the script to do it again...
Click to expand...
Click to collapse
It's not even as stable as I showed it in the video?
Can you make that script using SManager app? That way the script can work even after screen lock or something. I think this is the app https://play.google.com/store/apps/details?id=os.tools.scriptmanager
And I have no idea what happens when it's set to 5 try it out. Nothing bad might happen.
Sent from my GT-I9100 using Tapatalk

Harsha Raj said:
It's not even as stable as I showed it in the video?
Can you make that script using SManager app? That way the script can work even after screen lock or something. I think this is the app https://play.google.com/store/apps/details?id=os.tools.scriptmanager
And I have no idea what happens when it's set to 5 try it out. Nothing bad might happen.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
About the video, yes, it's not that stable. But I guess it's the ROM's/Kernel's fault, since it's unstable changing the thresholds, they don't bother fixing it...
As for the script, have a look atTasker for that. When it screens-off, the threshold reverts back to normal (the bug on the ROM, maybe?), right?
Then when you do screen-on, use Tasker and it will automatically run the script, and will change the thresholds to the desired percent...
for the script commands I just created a script file:
Code:
#!/system/bin/sh
#Change Touch Sensitivity Script
#Default Sensitivity is 40 on NeatROM
echo 10 > /sys/class/sec/sec_touchscreen/tsp_threshold
Then put it on /system/xbin, changed it's permissions to 777, then ran it on Terminal Emulator.
To test, run this on your Terminal Emulator:
Code:
$ su
# sh -x /system/xbin/<name of the script>
It must echo your desired sensitivity. Then if all's well, try your pen now...

souler456 said:
About the video, yes, it's not that stable. But I guess it's the ROM's/Kernel's fault, since it's unstable changing the thresholds, they don't bother fixing it...
As for the script, have a look atTasker for that. When it screens-off, the threshold reverts back to normal (the bug on the ROM, maybe?), right?
Then when you do screen-on, use Tasker and it will automatically run the script, and will change the thresholds to the desired percent...
for the script commands I just created a script file:
Code:
#!/system/bin/sh
#Change Touch Sensitivity Script
#Default Sensitivity is 40 on NeatROM
echo 10 > /sys/class/sec/sec_touchscreen/tsp_threshold
Then put it on /system/xbin, changed it's permissions to 777, then ran it on Terminal Emulator.
To test, run this on your Terminal Emulator:
Code:
$ su
# sh -x /system/xbin/<name of the script>
It must echo your desired sensitivity. Then if all's well, try your pen now...
Click to expand...
Click to collapse
The script is working good manually. But I setup a profile on tasker as "screen on" and then the script. But the script won't get executed when screen turns on.
I tried same profile for music and it works well.
Sent from my GT-I9100 using Tapatalk

Harsha Raj said:
The script is working good manually. But I setup a profile on tasker as "screen on" and then the script. But the script won't get executed when screen turns on.
I tried same profile for music and it works well.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Did you check "Use Root" when assigning the script? cause you need too...

T-Mobile Wi-Fi Calling.

So does anyone have an idea on how to get this to work on AOSP ROMS? I'm making new vebdor blobs and the only real new APK I see is CNEService. There's other files here and there but nothing I can tell that will help with this.

xanaxdroid said:
So does anyone have an idea on how to get this to work on AOSP ROMS? I'm making new vebdor blobs and the only real new APK I see is CNEService. There's other files here and there but nothing I can tell that will help with this.
Click to expand...
Click to collapse
I haven't been able to look into it yet and I don't have tmobile so it's going to be tough for me... I plan on checking into it tomorrow while I'm off work though...

Im very interested in helping with this as I would love wifi calling on my gpe htc one m8, anything you guys need to test ill do it. I even have an old m7 with aosp firmware on it I'm willing to brick for the cause if needed.

I'm on 5.1.1, and I'm on T-Mobile with my Nexus 6. Anything you need? My Bootloader is unlocked, but I'm stock and not rooted

swimdude1120 said:
I'm on 5.1.1, and I'm on T-Mobile with my Nexus 6. Anything you need? My Bootloader is unlocked, but I'm stock and not rooted
Click to expand...
Click to collapse
I already have a system dump which is here, and I've made some test blobs here. Now comes the hard part.

xanaxdroid said:
I already have a system dump which is here, and I've made some test blobs here. Now comes the hard part.
Click to expand...
Click to collapse
I am running the stock ROM (don't worry, bro, be back later today :victory: ) and I just got an update on an app I had never seen before: Google Connectivity Services. The tag line is "Improved Networking for Android", and the description talks about automatic wifi connections and Google VPN. Obviously this is a precursor to Fi, but I am wondering if the delay for T-Mobile WiFi calling was to wait for it to be built on the Fi platform for WiFi calling, which we know will be part of the deal.
Not sure what to make of it, other than it's looking very proprietary right now.

brizey said:
I am running the stock ROM (don't worry, bro, be back later today :victory: ) and I just got an update on an app I had never seen before: Google Connectivity Services. The tag line is "Improved Networking for Android", and the description talks about automatic wifi connections and Google VPN. Obviously this is a precursor to Fi, but I am wondering if the delay for T-Mobile WiFi calling was to wait for it to be built on the Fi platform for WiFi calling, which we know will be part of the deal.
Not sure what to make of it, other than it's looking very proprietary right now.
Click to expand...
Click to collapse
Yeah the Google Connection Service app has been on the Play Store for awhile. I already added it to my blobs. Yeah it is looking proprietary, but I'm sure we can get it to work. It's been done on other phones before.

i have faith is will be a short time before you guys get it to work

justcallmeTHEKID said:
Im very interested in helping with this as I would love wifi calling on my gpe htc one m8, anything you guys need to test ill do it. I even have an old m7 with aosp firmware on it I'm willing to brick for the cause if needed.
Click to expand...
Click to collapse
You won't brick, the WiFi calling feature requires framework changes that (I can pretty guarantee) are not open source.
Second: This is in the DEVELOPERS ONLY section, so if you guys want to discuss WiFi calling and aren't actually working on it then you need to move general discussion of it to a different thread. This area is strictly for development and discussion of such development (technical things, not "oh nice can't wait" or "I'll test for you" )

i think we should look at the file systems for the stock nexus 6 and t mobile nexus 6 and check for differences i know its a long shot but ill check it out tonight and see what i can find.
Second: see development were not just chatting anymore
Third: If anyones already done that please tell me so I don't have to its gonna take forever.

justcallmeTHEKID said:
i think we should look at the file systems for the stock nexus 6 and t mobile nexus 6 and check for differences i know its a long shot but ill check it out tonight and see what i can find.
Second: see development were not just chatting anymore
Third: If anyones already done that please tell me so I don't have to its gonna take forever.
Click to expand...
Click to collapse
you need tmobiles blobs. besides that, all n6 roms will be identical.

So I decompiled LYZ28E and took a look around in the Settings app. It has a class called WifiCallingSettings. Inside there it makes calls to ImsManager.isWfcEnabledByUser. It seems like Wfc is WiFi Calling. I took a look at frameworks/opt/net/ims/src/java/com/android/ims/ImsManager.java and it doesn't have a function called isWfcEnabledByUser. I looked at android-5.1.1_r4 and android-m-preview tags. I think we need to wait for Google to push androiid-5.1.1_r5. According to https://android.googlesource.com/pl...om/+/ecfa803f8e7ca0cb65e74fb4dda90c16156655f3 that's the tag for LYZ28E.

From what I've been told by a guy I know at Tmo, you can only use WiFi Calling on phones that have been authorized by Tmo. (Example) Nexus 5 with Android M preview shouldn't be able to do WiFi calling. Even though Google is now baking in WiFi calling into Lollipop and M.

Check out the latest revision (5.1.1_r5) on AOSP. It includes WiFi calling support. Check it!
https://android.googlesource.com/

Gandalf said:
You won't brick, the WiFi calling feature requires framework changes that (I can pretty guarantee) are not open source.
Second: This is in the DEVELOPERS ONLY section, so if you guys want to discuss WiFi calling and aren't actually working on it then you need to move general discussion of it to a different thread. This area is strictly for development and discussion of such development (technical things, not "oh nice can't wait" or "I'll test for you" )
Click to expand...
Click to collapse
I'll just leave this here since guarantees were made and all
https://github.com/codeaurora-unoff...mmit/2cc69a62cb1bc4989f0421e0006290e3985aa506
https://github.com/codeaurora-unoff...mmit/1a2e9e4a1dffe211bb503962bc42f476072dd216
https://github.com/codeaurora-unoff...mmit/98f974e95d880d76d653e2f4a36a057c667ce1b3
I will add that you don't just need the frameworks part but also kernel commits to support this WPC feature

I'll submit the specific changes made to bcmdhd driver (rather than just merge the entire m-preview kernel) to Omni Github once it is tested further and verified functional and stable for merge.

Gandalf said:
I'll submit the specific changes made to bcmdhd driver (rather than just merge the entire m-preview kernel) to Omni Github once it is tested further and verified functional and stable for merge.
Click to expand...
Click to collapse
Interesting. Todays nightly came closer than ever!
Stock CM Kernel allowed me to get the IWLAN status in SIM Status, but the Data Quick Toggle Shows TMOBILE (Not WiFi Calling), and I am unable to call out. Also, WiFi Calling Settings don't show up in the "More" Tab (Under Wireless & Mobile Network Settings), and no WiFi Calling toggle in the Dialer (Does CM use the Google Dialer? Or its own?).
Interesting. It seems like the hard part is done at least.

npjohnson said:
Interesting. Todays nightly came closer than ever!
Stock CM Kernel allowed me to get the IWLAN status in SIM Status, but the Data Quick Toggle Shows TMOBILE (Not WiFi Calling), and I am unable to call out. Also, WiFi Calling Settings don't show up in the "More" Tab (Under Wireless & Mobile Network Settings), and no WiFi Calling toggle in the Dialer (Does CM use the Google Dialer? Or its own?).
Interesting. It seems like the hard part is done at least.
Click to expand...
Click to collapse
To my knowledge, all wfc builds so far have merged the m-preview kernel into the lollipop-mr1 kernel. I believe I have the specific commits needed and it will be up on Omni's github once ready.

Gandalf said:
To my knowledge, all wfc builds so far have merged the m-preview kernel into the lollipop-mr1 kernel. I believe I have the specific commits needed and it will be up on Omni's github once ready.
Click to expand...
Click to collapse
Outstanding. Thank you for your work.