Database Develop

[Q] Change CM10.1 to work in Tablet mode

Just recently pulled my old DS7 out of the corner and after seeing, nvflashed this really great Unofficial CM10.1 for Dell Streak 7 ROM on it. Works great, apart from the one tiny problem - it thinks it's a phone ... I already used Uninstall Master to remove some Phone features, such as: SIM Toolkit(it's called Mobile Data i think?), Messaging and Mobile Network Configurator. Was wondering how or where can I change or modify the settings related to how the Cyanogenmod acts as a Phone or a Tablet so that many apps from Play Store wouldn't default to the portrait mode.
On a sidenote - thanks to giveen and anyone involved in making this really awesome CM port to DS7 :good:

karlis1989 said:
Just recently pulled my old DS7 out of the corner and after seeing, nvflashed this really great Unofficial CM10.1 for Dell Streak 7 ROM on it. Works great, apart from the one tiny problem - it thinks it's a phone ... I already used Uninstall Master to remove some Phone features, such as: SIM Toolkit(it's called Mobile Data i think?), Messaging and Mobile Network Configurator. Was wondering how or where can I change or modify the settings related to how the Cyanogenmod acts as a Phone or a Tablet so that many apps from Play Store wouldn't default to the portrait mode.
On a sidenote - thanks to giveen and anyone involved in making this really awesome CM port to DS7 :good:
Click to expand...
Click to collapse
The reason why it is that way is because there are 4G models of the DS7

giveen said:
The reason why it is that way is because there are 4G models of the DS7
Click to expand...
Click to collapse
Understandable, but since I have a Wi-Fi only version I wanted to know if It's possible to change this in form of a setting or a few lines inside a configuration file without involving compiling. I even faintly remember stumbling upon something like this on a CM9 version I had on my old Xperia MT15i Neo ... if only I could remember or find where or how (currently strolling through the developer and CM10 related menus) - deleted my Xperia related bookmarks when I sold it.
p.s. - people mentioned some problems with the on-screen keyboard disappearing as described in one of the posts on the main CM10.1 thread, I've noticed them myself too and they tend to be application specific ... it feels like the keyboard crashes or force-closes due to not enough memory, like in lighter applications the keyboard works fine, but when trying to use the keyboard for writing for example a post in the comments section in a website will most likely result in keyboard disappearing after first input character.

So I am still trying to figure out why you started a new thread about this and what your question is.
To remove mobile data completely requires a new compile, something that cannot be done right now for a variety of reasons.

I guess I simply went too far off topic while trying to explain why I'm writing here... sorry.
So, to clear things up, the question still remains the same - what can I do to make it act more like a tablet and less like a phone on my Wi-Fi only DS7. So what I'm trying to find in the developer and CM menus is if I can more or less simply switch between some sort of "phone" and "tablet" mode so that some applications from Play store wouldn't default to portrait view mode.
And I noted that I've already uninstalled/disabled (call it how you want - I can restore them from the Unnstallers Recycle Bin if something weird starts to occur) some of the system .apks and as You already pointed out:
To remove mobile data completely requires a new compile, something that cannot be done right now for a variety of reasons.
Click to expand...
Click to collapse
... so thanks for clarifying that and no need to do any special versions - it's just fine how it is now. I didn't come here to request anything to be compiled or modified for me but just to ask for info, heck, I wasn't even expecting You to be answering on this thread.

karlis1989 said:
I guess I simply went too far off topic while trying to explain why I'm writing here... sorry.
So, to clear things up, the question still remains the same - what can I do to make it act more like a tablet and less like a phone on my Wi-Fi only DS7. So what I'm trying to find in the developer and CM menus is if I can more or less simply switch between some sort of "phone" and "tablet" mode so that some applications from Play store wouldn't default to portrait view mode.
And I noted that I've already uninstalled/disabled (call it how you want - I can restore them from the Unnstallers Recycle Bin if something weird starts to occur) some of the system .apks and as You already pointed out: ... so thanks for clarifying that and no need to do any special versions - it's just fine how it is now. I didn't come here to request anything to be compiled or modified for me but just to ask for info, heck, I wasn't even expecting You to be answering on this thread.
Click to expand...
Click to collapse
I make it my special concern to answer questions, even if it with sarcasm
I'm not sure what more you can do besides deleting the phone. Comment out in build.prop the rild stuff

I wonder if he is referring to TabUI? Which I as well am trying to relocate the flash able .zip which enabled this display difference. I have been running cm10.1 2/12 because of the sensors not working on the 2/14 build.
Sorry to piggyback the thread, but is there an answer for where the tab ui .zip is for the 2/12 build?
Sent from my Galaxy Nexus using xda premium

[Q] APK conversion and HTC keyboard

I am not sure if I have posted this in the right place, I hope so!
For me the 4.3 update to the HTC One brings both grief and joy, the joy is I can turn off Blinkfeed but the grief is that it brings emojis. For me they are not that helpful and I would like to revert to the previous keyboard that was in 4.2.2. The emojis most of my friends cannot receive so I am looking for an alternative. I have tried Swype but I don't like the layout and find it frustrating. I tend to use swyping as my main method of input and I also use smilies a lot.
So I was wondering if it was possible to convert the 4.2.2 HTC_IME.apk to an installable apk. I have tried taking it from another ROM and installing it but for reason it doesn't like life. I think I need root access but as my phone is in warranty I do not want to fiddle with it until that expires.
Is there a way to convert it to an installable APK? I think it might be framework attached so not possible. I am pretty new to this so what I am attempting to do might be waaaaay beyond me.

[Q] Capture Stylus events before they go to Apps

Reposting from where I previously put this, on the suggestion that folks here might have more idea what I am talking about.
Yes, this is a question but I couldn't see that it fit in better to one of the other forums. If I am wrong please accept my apologies and redirect me, thanks.
I'm trying to work with a custom build of Android based on KitKat to incorporate a stylus, copying some of the functionality (though not code) from Samsung which sells Android-with-stylus builds for e.g. the Note 3. I'm not including details of the specific device because right now I am working on a custom dev device and my aim is to write code which is generic enough to be usable from any Android (based on KitKat). The build (written by others) already incorporates drivers and sends stylus events correctly as motion events etc. Programming at the app level I can receive onHover, onTouch, onClick etc
The specific functionality I am trying to achieve is to pick up a stylus-button-click while hovering. It's perfectly possible to do this in any app, using an onGenericMotion Listener.
However, I want to make my "stylus-action" have system-wide effect - so that anywhere (in any other app, or in the launcher or whatever) I will pick up the event (prior to any other app) and bring up my custom menu. (just like AirCommand in Samsung Note 3) I guess in my custom Android this would then make that particular action somewhat protected or unusable for other users, but I'm ok with that.
In older Android (prior to ICS) you could try something by putting up a System Overlay (i.e in regular app code, without hacking the ROM at all), but this is no longer possible.
This is not an attempt to tapjack or whatever, I understand why this functionality has been removed from the domain of the regular programmer, and I don't want to regress my ROM back to pre-ICS behaviour by allowing the System Overlay hack. Now I am programming the system (if my change is good enough I'd like to submit it back to AOSP) so I would like to know the best method to address this. Since Samsung have already done this, it must be legal (using legal in the terms of "Android will allow it"), and I want to do it right.
Is it possible to write something similar to the System Overlay when you are running from a system service? Or is there a good choke-point to capture events before they are broadcast to the current running apps?
I was looking at (sorry, not allowed to post links) AndroidXRef /frameworks/base/core/java/android/view/View.java specifically in the function dispatchHoverEvent() which looks like a promising place. My naive idea is that I would place code here checking the MotionEvent to see if the button is pressed and if it is, don't call any listeners and instead call my little menu app (or broadcast a custom message, or something anyway). However, I've never written code on the ROM level before (LOTS of experience writing app code) so I don't know if this is a really bad point or a good point to add in code. Should I be putting things at a higher level or a lower one? Will this capture all events or not? Is it all just trial and error?
If this is the wrong place to ask questions like this, please tell me where on XDA I should be asking it. If it's the right place - please answer
Thanks
Kibi

[5/12] Advanced Feed Development

Alright everyone, I'm Trailblazer101, an Android Developer who likes to take advantage of, and make better, the unique features of the phones I purchase. I started off with the Samsung Continuum back in 2010, which had a ticker ahead of its time, and went from there. I work 2 jobs, so time is tight sometimes, but I still manage to work on these things, a fun passion/hobby.
Status Updates
Code:
5/12
--- I got my patch working, and tested it out with a simple demo that takes advantage of the new capabilities. I've posted a Guide below!
5/10
--- Now that Verizon users have root, I will begin testing this myself :) Thanks to those who helped me figure out what we'd have to do, so I can get started right off the bat! I'll keep you posted.
What is this?!!
Okay, so by default the Feeds that you can make are restricted to the capabilities of a RemoteView. This severely limits what you can do with the Feed. Take a look here to see what exactly is supported, by default: http://stackoverflow.com/a/16089389
However, any Samsung App (which includes a few signed by Samsung on the Galaxy Apps Exclusives page) has the ability to put whatever it wants on the screen, just like a regular App. I've now extended that invitation on over to you/us!
Guide
The steps to take advantage of this is a little convoluted, so let me break it down for you easy!
STEP 1:
You have to flash my patch to allow this development to actually work. You can download it here: View attachment Trailblazer101_S6Edge_Advanced_Feeds_Patch.zip. Then flash it using FlashFire, or extract the zip and put everything where it needs to go, making sure to set the permissions appropriately!
STEP 2:
Now you can start developing your new Custom Feed! I would suggest using my simple demo project as your base, and going from there! You can find that here: View attachment EdgeScreen-BACKUP.zip. Extract it and take a look at the source!
STEP 3:
From here on out is where things get tricky... Without changing a thing, if you build from source and try to debug, it won't work. Why? Because the API that Samsung gives developers, like us, is different than the one they use for themselves. So Here's what you gotta do-- without changing a thing, build the Project. The best way to do that without debugging within Android Studio is to go to Gradle Projects -> :app -> Tasks -> build -> assembleDebug. This'll make the built apk and put it within "..\.EdgeScreen-BACKUP\app\build\outputs\apk\app-debug.apk".
STEP 4:
I'm assuming you have the latest Java Development Kit, and Android SDK, installed and configured properly, with their paths in the PATH variable, accordingly. You should also know how to use apktool for decompilation, at least a little I've compiled a toolkit folder based off of the test Project I shared above, which includes apktool, the NEW Samsung API files, the original built apk, and the already modified decompiled source/apk. You can download that here: View attachment Decompilation_Data.zip. Then, open a Command Prompt window and "cd" to the extracted folder.
STEP 5:
Decompile the built apk, which should be the same as the one in the extracted folder, using apktool like this:
Code:
.\apktool\apktool d -f TestFeed_orig.apk
STEP 6:
Compare the decompiled folder "TestFeed_orig" with my already modified "TestFeed_modded" one. I suggest using WinMerge! You'll see that the 'TestFeed_orig\smali\com\samsung\android\sdk' folder is very different. That's what I was talking about before, how Samsung Feeds have more options in their API. So delete the 'TestFeed_orig\smali\com\samsung' folder, and replace with the one in the '---SAMSUNG API---' folder.
STEP 7:
Continue comparing the two folders. Basically the rest of the changes are just getting our application to call the new Samsung API properly, instead of the stubs I was using in the Project. There aren't many changes you have to make, but they're all important!
STEP 8:
Once the two folders are the same, recompile it using apktool, like so:
Code:
.\apktool\apktool b TestFeed_orig
STEP 9:
Sign the new compiled apk stored in 'TestFeed_orig\dist' using your signing key. You can make your own, then use it to sign the app, following the instructions here: Official Instructions for Manual Signing.
STEP 10:
Install the newly signed apk, and enable the Feed by going to: Settings-> Edge screen -> Information stream -> Manage Feeds -> *ENABLE* FeedsCocktailExample! You may have to restart, or just hit 'reorder' in the top left. That sometimes fast-triggers it. Now turn off the screen, do the Feed Gesture to get it to turn on, and you should see our Custom Feed! It doesn't look like much, but it's using a custom view, HorizontalTextView, that would not work otherwise.
From here the options are endless. You can follow these steps and my Sample Project to play a video for a feed, if you wanted! Whatever strikes your fancy!
If you followed these steps and appreciate the help, show this thread some love, and maybe. Well i'd say buy me a beer, but it'll probably go to textbooks instead
Developer/Advanced Information!
We can make our own Feeds no problem, without root, they are just forced to use a RemoteView directly, which for all intents and purposes, is a pain in the kiester. Instead, it would be a lot nicer/convenient, without even mentioning the more advanced functionality we could bring, to use our own Views. However the version of SlookCocktailManager.UpdateCocktail that allows this is only found within a more advanced API, one I/no typical user don't have access to directly. BUT, I can still access it by decompiling for example the Edge RSS app from the Samsung AppStore, and putting/replacing the "sdk" folder from that into my own decompiled app, and recompiling. Easy enough, with apktool! (Of course with the headache of adding in my own temporary shell classes, in the project, so that I can actually write the calls, and just change the reference within the smali code once that sdk is replaced) The problem is, even when you do this, and it builds fine, installs great, and even begins initializing properly, we get an error from within CocktailBarService, the file I'm having you replace. More specifically, I tracked down the actual problem, and it comes back to "CocktailWhiteList", a class within CocktailBarServices, then checks the signature of the calling application, our Custom Feed, and sees if it comes from Samsung. This none of my expertise can fix, without being rooted, but trust me I tried. Now that we are rooted I was able to patch said apk, and get my own apps to work! Hurray!

cocktailbar service crashes when going into 'edge screen' option in settings menu.
logcat attached
Edit: sorry didn't rename cocktail bar (cocktailbarservice_signed to cocktailbarservice)
now it doesn't visibly crash, it just wont let me go into 'edge screen' option in settings menu
new log cat uploaded

This man looks promising! You have my S6 edge as soon as I have an official TWRP with working backup and restore

ktetreault14 said:
This man looks promising! You have my S6 edge as soon as I have an official TWRP with working backup and restore
Click to expand...
Click to collapse
I will help as well, when these tools are out for us..
Thanks for bringing cool stuff like this to the phone at this early date!

ktetreault14 said:
This man looks promising! You have my S6 edge as soon as I have an official TWRP with working backup and restore
Click to expand...
Click to collapse
How deep are you willing to go? Because it would be awesome if you could clear dalvik-cache, since I see this, right off the bat:
Code:
: Failed to find OatDexFile for DexFile /system/priv-app/CocktailBarService/CocktailBarService.apk ( canonical path /system/priv-app/CocktailBarService/CocktailBarService.apk) with checksum 0xfbfcb9f7 in OatFile /data/dalvik-cache/arm64/[email protected]@[email protected]@classes.dex
EDIT: could you also make sure that you set the right permissions for the apk? I'm getting the impression that they might be off with:
Code:
msg=audit(1429397519.049:355): auid=4294967295 uid=10001 gid=10001 ses=4294967295 subj=u:r:untrusted_app:s0 pid=12605 comm="ktailbarservice" reason="memory violation" sig=11
EDIT2: We might have to disable SELinux... That's rather unfortunate/puts a rather large damper on things, until custom kernels come out at least... After starting a root shell, can you try:
Code:
setenforce 0
I don't know if it'll work, but if that goes through successfully try and launch the Edge Settings Screen again!
EDIT3: Do'h. It may have been something really simple *crosses fingers* Could you please re-download the CocktailBarService, and try doing the same thing you did last time, with right permissions, and maybe a dalvik-cache wipe if it doesn't work!?

Tried the new apk you uploaded. Getting a force close still when trying to open. I changed SELINUX to permissive, wiped dalvik, even tried deleting arm64 folder as well. No luck.
04-19 00:25:09.907 E/AndroidRuntime(15867): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.samsung.android.app.cocktailbarservice/com.samsung.android.app.cocktailbarservice.settings.EdgeScreenSettingsMain}: java.lang.SecurityException: Permission Denial: get/set setting for user asks to run as user -2 but is calling from user 0; this requires android.permission.INTERACT_ACROSS_USERS_FULL
Was searching through logcat and found this. May this have something to do with the issue?

wase4711 said:
I will help as well, when these tools are out for us..
Thanks for bringing cool stuff like this to the phone at this early date!
Click to expand...
Click to collapse
Don't mean to hijack thread, but "Tool" is already available here:
NB: Chrome and IE don't translate into "Save file" - Use Mozilla which does > copy to phone and flash.
https://blck.io/twrp-2.8.6.0-zeroltetmo.img
Perfectly working on T-Mobile S6 Edge
Will

RoM_Addict said:
Don't mean to hijack thread, but "Tool" is already available here:
NB: Chrome and IE don't translate into "Save file" - Use Mozilla which does > copy to phone and flash.
https://blck.io/twrp-2.8.6.0-zeroltetmo.img
Perfectly working on T-Mobile S6 Edge
Will
Click to expand...
Click to collapse
that version doesn't work properly for me and many others; waiting for an "official" version from the TWRP folks..

trailblazer101 said:
How deep are you willing to go? Because it would be awesome if you could clear dalvik-cache, since I see this, right off the bat:
Code:
: Failed to find OatDexFile for DexFile /system/priv-app/CocktailBarService/CocktailBarService.apk ( canonical path /system/priv-app/CocktailBarService/CocktailBarService.apk) with checksum 0xfbfcb9f7 in OatFile /data/dalvik-cache/arm64/[email protected]@[email protected]@classes.dex
EDIT: could you also make sure that you set the right permissions for the apk? I'm getting the impression that they might be off with:
Code:
msg=audit(1429397519.049:355): auid=4294967295 uid=10001 gid=10001 ses=4294967295 subj=u:r:untrusted_app:s0 pid=12605 comm="ktailbarservice" reason="memory violation" sig=11
EDIT2: We might have to disable SELinux... That's rather unfortunate/puts a rather large damper on things, until custom kernels come out at least... After starting a root shell, can you try:
Code:
setenforce 0
I don't know if it'll work, but if that goes through successfully try and launch the Edge Settings Screen again!
EDIT3: Do'h. It may have been something really simple *crosses fingers* Could you please re-download the CocktailBarService, and try doing the same thing you did last time, with right permissions, and maybe a dalvik-cache wipe if it doesn't work!?
Click to expand...
Click to collapse
Hi trailblazer, I set the permissions the same as the original apk ,
right lets try again: I've downloaded the new version and set permissions, wiped dalvik-cache but when trying to disable SELinux i get
tmp-mksh: 0 : not found.
and when going into 'edge screen' settings i get unfortunsatly cocktailbar service has stopped.
Catlog attached:

I used this to modify SELINUX. For anyone else who is helping out, try this.

[4/19] QuickLaunch Demo And Advanced Feed Development Request For Rooted Users
b-reezy said:
I used this to modify SELINUX. For anyone else who is helping out, try this.
Click to expand...
Click to collapse
I sent you a PM! I explicitly declared that permission for each activity, so let's see how it goes now! I put the same apk I sent you now on the OP, so the other testers can try it! In the mean-time, I do have something real for you guys to play with! It's the QuickLaunch window, customizable and all (from hitting the Feeds Settings Icon). I'll put that in the OP with the tag "WORKS(Kinda)"!
One thing, which is a big reason why I'm trying to do it this way-- clicking the icons launches the app, it just doesn't turn the screen back on! I've tracked it down, and it seems as if when the Feed Screen is on, it has the SCover flag set to on, manually, but when a user clicks a button from another Feed, it turns that flag back off, thus turning the screen back on. The easiest/cleanest way for us to do that too would be our Custom Feed Panel implementing the same OnClickHandler that the others do, just can't without doingwhat we're trying to do!
EDIT: Please still use the QuickLaunch apk with the tag "Signed" though for testing the replacement of CocktailBarService! My new one just does it the bad way, and had to get rid of the code for trying the good.
(There's other ways to turn the screen on, but the way I'm trying to do it does it easily, and allows for more advanced functionality!)
FOR DEVELOPERS:
If you are interested in taking what I have and running with it/collaborating, I am more than willing to send all sources of what I have so far, my resources that I've been using, along with all information gathered so far. Just ask!

Hopefully this will become available for non-rooted. I am DIEING to get more functionality out of the Edge API for this phone. The feed is an awesome option, but having to swiping finger is a pain in the @$$. A double tap on the edge or an automatic turn on would be AWESOME when Texts or missed calls are there.

b-reezy said:
I used this to modify SELINUX. For anyone else who is helping out, try this.
Click to expand...
Click to collapse
BTW.. can be disabled in the kernel source also.. I did that in m8 times

trailblazer101 said:
I sent you a PM! I explicitly declared that permission for each activity, so let's see how it goes now! I put the same apk I sent you now on the OP, so the other testers can try it! In the mean-time, I do have something real for you guys to play with! It's the QuickLaunch window, customizable and all (from hitting the Feeds Settings Icon). I'll put that in the OP with the tag "WORKS(Kinda)"!
One thing, which is a big reason why I'm trying to do it this way-- clicking the icons launches the app, it just doesn't turn the screen back on! I've tracked it down, and it seems as if when the Feed Screen is on, it has the SCover flag set to on, manually, but when a user clicks a button from another Feed, it turns that flag back off, thus turning the screen back on. The easiest/cleanest way for us to do that too would be our Custom Feed Panel implementing the same OnClickHandler that the others do, just can't without doingwhat we're trying to do!
EDIT: Please still use the QuickLaunch apk with the tag "Signed" though for testing the replacement of CocktailBarService! My new one just does it the bad way, and had to get rid of the code for trying the good.
(There's other ways to turn the screen on, but the way I'm trying to do it does it easily, and allows for more advanced functionality!)
FOR DEVELOPERS:
If you are interested in taking what I have and running with it/collaborating, I am more than willing to send all sources of what I have so far, my resources that I've been using, along with all information gathered so far. Just ask!
Click to expand...
Click to collapse
Liking the Quicklaunch app , are you still needing testers? or have you got all the info you need?

Alex-V said:
BTW.. can be disabled in the kernel source also.. I did that in m8 times
Click to expand...
Click to collapse
Exactly and imo its better if its done this way..
for anyone interested
you need to edit the security/selinux/selinuxfs.c file from source
FIND:
Code:
selinux_status_update_setenforce(new_value);
#else
ADD RIGHT BELOW "#else":
Code:
new_value = 0;
So it becomes:
Code:
selinux_status_update_setenforce(new_value);
#else
new_value = 0;
or use this one (from the G925F source)

friedrich420 said:
Exactly and imo its better if its done this way..
for anyone interested
you need to edit the security/selinux/selinuxfs.c file from source
FIND:
Code:
selinux_status_update_setenforce(new_value);
#else
ADD RIGHT BELOW "#else":
Code:
new_value = 0;
So it becomes:
Code:
selinux_status_update_setenforce(new_value);
#else
new_value = 0;
or use this one (from the G925F source)
Click to expand...
Click to collapse
yeah.. that's the one I used.. I'm still for and back to root or not..means for me.. develop roms and kernels ..or use it as it is.. lol..

friedrich420 said:
Exactly and imo its better if its done this way..
for anyone interested
you need to edit the security/selinux/selinuxfs.c file from source
FIND:
Code:
selinux_status_update_setenforce(new_value);
#else
ADD RIGHT BELOW "#else":
Code:
new_value = 0;
So it becomes:
Code:
selinux_status_update_setenforce(new_value);
#else
new_value = 0;
or use this one (from the G925F source)
Click to expand...
Click to collapse
Hii my friend, i also still , have a non rooted S6 Edge :thumbup:

Hey guys, I finished the QuickLaunch Feed and posted it in the Apps Folder here:
Click Me!
I did manage to get it to turn the screen on, then, with the clicking of the shortcuts, and it still launches it once unlocked (if you have a lockscreen). I am going to begin work on a music player Feed, now
I will continue development on more advanced Feeds, and also delve into enhancing the edge in other ways, once we Verizon users get root (or until I win the lottery and get a Sprint version ). I see all these great opportunities to make it better, I just can't do anything with it until I'm rooted, since this didn't go as well as I planned. Where we are stuck at now is this, and where it would be too much of a pain for me to do without a phone of my own to test one:
We need to re-sign the system with a signature key we have access to. This includes framework, apps, and the priv-apps signed with the samsung key. Then I can go about doing what I wanted to do, but otherwise, it's a no go.
A developer who does have a Sprint or T-Mobile version with root, I can tell you the information I gathered so far. I have seen where the 'turn screen on gesture' is stored, and all these other great things, I just can't right now

trailblazer101 said:
Hey guys, I finished the QuickLaunch Feed and posted it in the Apps Folder here:
Click Me!
I did manage to get it to turn the screen on, then, with the clicking of the shortcuts, and it still launches it once unlocked (if you have a lockscreen). I am going to begin work on a music player Feed, now
I will continue development on more advanced Feeds, and also delve into enhancing the edge in other ways, once we Verizon users get root (or until I win the lottery and get a Sprint version ). I see all these great opportunities to make it better, I just can't do anything with it until I'm rooted, since this didn't go as well as I planned. Where we are stuck at now is this, and where it would be too much of a pain for me to do without a phone of my own to test one:
We need to re-sign the system with a signature key we have access to. This includes framework, apps, and the priv-apps signed with the samsung key. Then I can go about doing what I wanted to do, but otherwise, it's a no go.
A developer who does have a Sprint or T-Mobile version with root, I can tell you the information I gathered so far. I have seen where the 'turn screen on gesture' is stored, and all these other great things, I just can't right now
Click to expand...
Click to collapse
very nice.. thanks my friend ?

This is just sounding AWESOME! I am on AT&T so will have to wait as well for Root. I was wondering if there is a possability for the edge to just turn on, on its own without the need to swipe the screen? Like when a new notification comes in it will just scroll across the edge (or maybe the icon will blink on and off until you see it and swipe).
I still feel the swipe is to hard to do consistantly and would rather use a double tap or something if the auto on isn't possible.

Haw can I use Chroma Dialer on Stock 5.1.1?

I have used Chroma in the past with minimal issues, but prefer the pure stock over a rom - so my question is; is there any way to use the Chroma Rom Dialer on the stock 5.1.1? (since I know there's several telephony, dialer, phonesky apps/files) I am not sure how I would go about doing that, or what all I would need to change in order to pull it off - if this is even possible at all?
Reason for my question, I like that it has BUILT IN native call blocking ability that the stock dialer doesn't, other than THAT feature it's identical to the stock dialer. I don't care if it's the Chroma dialer, or another rom dialer, I just want the STOCK dialer (or stock-like) to have this ability.
I know there's 3rd party apps for this type of thing, and I've used many of them, but I very much so prefer NOT to have to use a 3rd party app for something that (IMO) should have been built in to begin with.
If you wish to know why this is important to me, read the spoiler:
So, I get ~3-6 calls every day that's just the same BS; Scam calls saying I can lower my CC interest rates and to press 1 to speak to a representative. They always call from a different number, so blocking them individually doesn't work since it's never the same twice (typically - you'll understand after reading below). If you DO press 1 you get a rude person who will cuss at you, call you names, or laugh at you if you ask to be removed from their calling list. Doing that will only make it worse. I've recorded dozens of calls where they say really effed up things to me. Beyond harassment, it's straight up abuse.
I have been getting them for years, I DO NOT own a credit card, never have owned one, and have never even applied for one - plus there's THOUSANDS of pages on Google about these type of calls being a major problem. Even the FCC has a $50,000 bounty for anyone who can legally or illegally stop them - no questions asked (how badass is that!?) - THAT should tell you how hard they are to catch, find, or stop.
After more than 2 years of filing formal complaints/reports with the FCC, Local PD, FBI (as told to by the FCC), USCC, and have seeked legal advice from my lawyer as to getting this stopped via getting a subpoena so uscc has to release the real call origin trace, I'm on the Do Not Call list... - I've been met with ONE solution that has been common on all counts; change my number. That's not really an option, I've had this number since 1997, I'm not about to change it for obvious reasons.
Now, I've tried many apps to get this stopped, ranging from free to paid, and have not found one that ACTUALLY works toward getting it stopped, many are difficult to use or require WAY too much effort and personal information in order to do anything but ask you to donate.
So far I have logged (through Google Voice VM) a growing total of 566 *different* numbers they have called me from - from all over the US and some that are unused anywhere on earth.
In conclusion, Ive logged 566 different numbers that have called me a total of 11,925 times since 2008.
If that isn't justification for this request, then IDK what is. Shy of ditching my phone altogether, I'm out of ideas.

Bumping - I'd really appreciate any help, gents.

iRub1Out said:
Bumping - I'd really appreciate any help, gents.
Click to expand...
Click to collapse
Have no idea. If dialer would work would need boh contacts and dialer apk. Have no idea where the code for that mod is and if ASOP dialer will even work on stock. Then you have odex vs deodex to work through.

If it CANT work on stock (which, honestly, I didn't expect it to) given, as you said, the differences are small on the surface but in the actual build they're very different. I understand that, and those are things I considered leading me to wonder.
Can anyone MAKE the stock dialer with that mod added in, or a otherwise stock rom with that?
It seems like a lot to request, I know, but I've been looking for this for months, I've even set up a bounty in a thread on TUSCC, its something that I've really hoped would become a mod thru xposed or "Pure Shamu" rom with it. However, it seems that others don't experience this ridiculous problem, leading to it not being as popular as I wish it was.
Trying to stop an ex from calling is one thing, but trying to stop every call that isn't a contact, I realize that's quite another. Thus is my case, its crazy how many spoofed numbers they use. I'm more amazed that the carrier hasn't done something than I am that it's not a mod. There's tens of thousands of people with this problem and the one solution that requires no effort on the end user isn't available to cell phone users.
I don't know - I'm just at my wits end with these calls. I'd be happy to do it myself if a dev is willing to give me some direction, or ideas to try out.
As a side note, I've recorded several where I just screw with them for as long as I can - then put it on YT after they realize they've been trolled and blow up. It's a small, yet, satisfying "middle finger" I can do.

iRub1Out said:
If it CANT work on stock (which, honestly, I didn't expect it to) given, as you said, the differences are small on the surface but in the actual build they're very different. I understand that, and those are things I considered leading me to wonder.
Can anyone MAKE the stock dialer with that mod added in, or a otherwise stock rom with that?
It seems like a lot to request, I know, but I've been looking for this for months, I've even set up a bounty in a thread on TUSCC, its something that I've really hoped would become a mod thru xposed or "Pure Shamu" rom with it. However, it seems that others don't experience this ridiculous problem, leading to it not being as popular as I wish it was.
Trying to stop an ex from calling is one thing, but trying to stop every call that isn't a contact, I realize that's quite another. Thus is my case, its crazy how many spoofed numbers they use. I'm more amazed that the carrier hasn't done something than I am that it's not a mod. There's tens of thousands of people with this problem and the one solution that requires no effort on the end user isn't available to cell phone users.
I don't know - I'm just at my wits end with these calls. I'd be happy to do it myself if a dev is willing to give me some direction, or ideas to try out.
Click to expand...
Click to collapse
If I knew what the mod is it would be possible to port to stock. My guess it is in smali which cannot access on stock odex. Stock Would have to be deodexed to access smali which is also possible in rom form. Nobody I know of is deodexing stock 5.1.1 We have done it and got it working but don't post as we still don't know if everything works. Lollipop is still hard to make fully working rom from stock image. M is even going to be harder. Would still need the code required to enable the mod.

prdog1 said:
If I knew what the mod is it would be possible to port to stock. My guess it is in smali which cannot access on stock odex. Stock Would have to be deodexed to access smali which is also possible in rom form. Nobody I know of is deodexing stock 5.1.1 We have done it and got it working but don't post as we still don't know if everything works. Lollipop is still hard to make fully working rom from stock image. M is even going to be harder. Would still need the code required to enable the mod.
Click to expand...
Click to collapse
I concurr, your talking about taking apk's not meant for a certain rom and adding them in to pray it works. Did you look in the market t.o see if there was a KB you liked there? You can't just switch around apk's like that because you could easily get force closes. If you want to try just copy and paste it into a rom. you wont brick doing that, it may work

I know it isn't as easy as swapping apks - I had *hoped* it would be similarly easy, but figured there was no way.
Idk what the mod is, or how Chroma did it - but the dialer looks stock other than the addition of that option under the advanced menu in the dialer settings.
I've looked in the market, used many of them, Mr. Number was my go to for a long time but it is iffy on 5.1 as *sometimes* a call will get through for a couple rings then gets blocked. It would also block known contacts on a rare occasion, I would go a couple days without knowing I had missed a call from a family member because it didn't show up in Mr. Number or the stock dialer - somehow it blocked it and had no record of the call even coming in.
That's why I was hoping to find a way to get this option in the stock dialer - without porting anything or swapping apks, that way it's a native feature to the dialer and I wouldn't have to depend on 3rd party apps to do it.
I've asked Google, but their solution was to add them to one contact and send the calls to VM - while that essentially works, that means I'd have to add all 500+ numbers to a single contact, and they OFTEN call from spoofed numbers I've never seen before - so that really doesn't solve anything.