Develop Bugs

SGS3 themed Accuweather widget

Hi everyone,
----Attention to anyone on CM9 wanting to use this package-----
The zip seems to be causing some trouble with CM9 and some users have reported having boot loops after flashing (only on CM9)
If you are on CM9 and want to use the package please push the files across manually to where they need to be.
eg. /system/app and /system/etc read page 2 of this thread for detailed instructions.
**************Update 08/06/2012**************************
Another new update v1.2.1
fixed CWM package file...
added some permission xmls from touchwiz roms, and some libs etc. Hopefully will fix the problems some have been having again with the package.
Link updated below in downloads.
**********
Sorry to those of you who are on a CM based rom who weren't able to get the zip to work, I've updated the zip so it should work on CM, I am unable to test as I'm not on a CM rom so can someone please check it for me and let me know? Thanks.
Download link updated below.
ps. 100 downloads in less than a day!
***********************************************
I like many others have been working hard to port the SGS3's lovely widgets, but like everyone else, I haven't had any real luck ripping them, it seems samsung worked hard to make these ONLY available on the SGS3, but I guess it is just a matter of time until someone is able to port them.... hopefully
Until that time, I decided the next best thing would be to use the SGS2's ported accuweather widget and theme it with the nice images from the SGS3 widget
The background image is semi-transparent and changes depending on daytime/night time/cloudy weather
Have a look at screenshots
Daytime -
Night time -
Cloudy -
Installation
Copy zip file to phone
Then reboot into CWM and flash this file.
Clear dalvik cache
Reboot and enjoy
**If you already have either the digital clock widget or the sgs2 accuweather widgets installed, I would suggest to do a backup with titanium (just in case you want to revert to your old one) and then uninstall them**
Download
http://www.mediafire.com/download.php?r90ug8t219kd5sk
If you are happy with the app please hit the thanks button
And if you are really really happy feel free to buy me a beer / donate
In the zip, there is also a digital clock widget, with the number images from the SGS3 ported over too

IT doesnt work..
Sent from my GT-I9000 using XDA

santosxen said:
IT doesnt work..
Sent from my GT-I9000 using XDA
Click to expand...
Click to collapse
1st post! welcome to XDA.
Can you tell me which rom are you using, maybe you can try to manually put the files in /system/app and set permissions to 0 , 0 then r-w, r, r,
Did the install with CWM say it was sucessful or not?

xxx posts, still does not work..
Cyanogenmod 9, also setted permissions..

Try here dude,it's a GSIII's weather widget and it works on my GS
http://forum.xda-developers.com/showthread.php?t=1689520

Hi OP, sorry I haven't posted sooner, but it works fine.
Manually copied the two apk with rootexplorer + perms + reboot
Btw, I use Nova Launcher.
Thanks !

work`s on jw4?

saphirrot said:
xxx posts, still does not work..
Cyanogenmod 9, also setted permissions..
Click to expand...
Click to collapse
Haha! I wasn't implying that it wasn't working for santosxen because he has only made one post! that just silly!
I was only welcoming him to this great forum full of helpful people!
I forgot to mention after setting the permissions correctly (to 0 , 0 then r-w, r, r,) that you need to reboot and then it will work.
filou75 said:
Hi OP, sorry I haven't posted sooner, but it works fine.
Manually copied the two apk with rootexplorer + perms + reboot
Btw, I use Nova Launcher.
Thanks !
Click to expand...
Click to collapse
Excellent, thanks for the feedback! It is working fine on Apex launcher too.
norocosul3 said:
work`s on jw4?
Click to expand...
Click to collapse
Yes it should work fine on JW4.
However as you are on a Touchwiz based rom you might be able to get the real sgs3 widget to work from Twics latest 1.5.1 update see here it is a big pack which adds on a lot of content to your phone and changes icons etc. if you dont want all that stuff I can edit his CWM package if you want so it just includes the widgets...
Here is the link, http://www.mediafire.com/download.php?4dwy7yvy5ekhj7i
I edited out all the other stuff and you just have the new touchwiz launcher and the sgs3 widgets. Just put the file on your phone and flash with CWM, I can't guarantee it will work, but if you are on a samsung rom your chances are better than the rest of us I think, let me know how it goes.

New zip added to OP for those of you who are using CM roms, sorry the last zip seems to have only worked for some people, this one should work for everyone fingers crossed.

Haha! I wasn't implying that it wasn't working for santosxen because he has only made one post! that just silly!
I was only welcoming him to this great forum full of helpful people!
I forgot to mention after setting the permissions correctly (to 0 , 0 then r-w, r, r,) that you need to reboot and then it will work.
Click to expand...
Click to collapse
doesnt meant it bad too bro, but it still does not work. Please try your mod with this launcher :
http://forum.xda-developers.com/showthread.php?t=1571527
It wont work :/

sorry it's not working for you
thanks for the heads up with this link, I'll try it out

Yeah but... Touchwiz is... just touchwiz ^^'

It's atm not working for me too. I manually copied these two .apk Files to the /system/app Folder. After that i have wanted to change the permissions but i guess i failed that way...the permissions seem to be basically accurate... Help me guys please

I have just updated the file in the OP, version 1.2
now includes added touchwiz permission xml files and some lib files to system.
Hopefully with these added files it will work for everyone.
Let me know if it works

santosxen said:
It's atm not working for me too. I manually copied these two .apk Files to the /system/app Folder. After that i have wanted to change the permissions but i guess i failed that way...the permissions seem to be basically accurate... Help me guys please
Click to expand...
Click to collapse
I use an app from the market called 'super manager' download that and go into the 4th tab to the file manager, once you are in the file manager choose 'back up level folder' up the top of the list, choose this until it takes you back to / (which is root) up the top you should see '/ (r/o)' then go to system, (when going into system it will ask you if you want to modify the file system, it will give you three options 1. do nothing 2. read only, and 3. r/w choose R/W. Now you are in the system folder of your phone, but be careful here because if you change something without knowing what you are doing you could have big problems.. ok now go into app folder and find your file, it will be near the bottom, it is called accuweather.com and under that it will say 'samsungwidget_weatherclock.apk'.
Once you have found the file choose the tick box next to it, now down the bottom of the screen you will see a list of icons; home, copy, cut, paste etc. now slide across to the right and you will see 'attribute' the icon has 777 on it.
Ok now where it says owner: set this number to 0
and where it says group: set this number to 0 as well.
under that you will have your permissions.
you can set owner to read, write, and execute
you can set group to read, write, and execute as well
and you can set other to read, write, and execute as well
it will also work if you just have owner as r-w-- group as r---- and other as r---- but try the above settings first to see if that works for you.
Now you just have to reboot and your widget should install properly
I will assume that you are on a rooted rom though?
And please try the new version 1.2 in the opening post too
Let me know if you have any troubles

1.2 doesnt work -> signature verification failed
Sent from my GT-I9000 using XDA

I fixed the permissions, still wont work: (
Sent from my GT-I9000 using XDA

Sorry about that... new link uploaded....
v1.2.1
this time I tested it and it is working for me (sorry I didn't test that last one v1.2, must have been a problem with the zip file)

1.2.1 -> sugnature verification failed
Sent from my GT-I9000 using XDA

santosxen said:
1.2.1 -> sugnature verification failed
Sent from my GT-I9000 using XDA
Click to expand...
Click to collapse
You don't need a signed zip if you use a cwm recovery
Witch kernel do you have on your gs ?

[DEV][WIP] Enabling Google Wallet on the Note II

Another EDIT as of 7/12/13. go here for additional info/How to do it.
LINKY
EDIT: GO HERE FOR WORKING GOOGLE WALLET. DO NOT DOWNLOAD CWM.ZIP INFORMATION BELOW IS FOR INFORMATIVE PURPOSES ONLY
http://forum.xda-developers.com/showthread.php?t=2031127
If you've been trying to run Google Wallet on your USA variant Note II you've probably ran into some problems. like this one..
"Insufficient secure element privileges for this system image (release-keys)."
why is this happening? check HERE for more detail.
But for the sake of keeping everything together in this thread..
Ok, first a little background
basically what you are seeing if you try to install google wallet on at&t, tmo, etc, is you get stuck on "activating device"
If you dig a little further and ran a logcat, you will see that there it no "SMX detected"
What this means, when compiling the rom you need to enable SmartMX in the config headers located in the external/libnfc-nxp library. (thats why it works on CM9, they do this)
this is impossible for us because there is no source for samsung's TouchWiz. We got a break on the international sgs3 as the latest update has the secure element enabled...so does the sprint sgs3
Click to expand...
Click to collapse
So, All i did was rip a handful of lib files and whatnot out of a International SGS3 (I-9300) and push them onto my Note II. and viola! you get all the ways to the point where you actually try and add the card. then things go downhill.
{
"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"
}
you can find information on people having the same problem we're now stuck at HERE
all you need is a rooted Galaxy Note II to flash the zip. must be running Touchwiz. should work on all US and International variants (providing it has an Exynos4412 in it)
Should go without saying, but this is my first CWM zip. it's been working fine for me the multiple times I've tested it. but you're on your own if you have problems. And i'm not responsible for damage.
NOTE: in my experience it doesn't matter where you get the Google Wallet APK from. I modified my build.prop to match the Galaxy Nexus and got it from the market. also tried the modified Modaco one from HERE with no change.
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Nice work!
Sent from my SGH-T889 using xda premium

Thank you !

crazy talk said:
If you've been trying to run Google Wallet on your USA variant Note II you've probably ran into some problems. like this one..
"Insufficient secure element privileges for this system image (release-keys)."
why is this happening? check HERE for more detail.
But for the sake of keeping everything together in this thread..
So, All i did was rip a handful of lib files and whatnot out of a International SGS3 (I-9300) and push them onto my Note II. and viola! you get all the ways to the point where you actually try and add the card. then things go downhill.
you can find information on people having the same problem we're now stuck at HERE
all you need is a rooted Galaxy Note II to flash the zip. must be running Touchwiz. should work on all US and International variants (providing it has an Exynos4412 in it)
Should go without saying, but this is my first CWM zip. it's been working fine for me the multiple times I've tested it. but you're on your own if you have problems. And i'm not responsible for damage.
NOTE: in my experience it doesn't matter where you get the Google Wallet APK from. I modified my build.prop to match the Galaxy Nexus and got it from the market. also tried the modified Modaco one from HERE with no change.
Click to expand...
Click to collapse
Did you by chance change your build prop?

crazy talk said:
If you've been trying to run Google Wallet on your USA variant Note II you've probably ran into some problems. like this one..
"Insufficient secure element privileges for this system image (release-keys)."
why is this happening? check HERE for more detail.
But for the sake of keeping everything together in this thread..
So, All i did was rip a handful of lib files and whatnot out of a International SGS3 (I-9300) and push them onto my Note II. and viola! you get all the ways to the point where you actually try and add the card. then things go downhill.
you can find information on people having the same problem we're now stuck at HERE
all you need is a rooted Galaxy Note II to flash the zip. must be running Touchwiz. should work on all US and International variants (providing it has an Exynos4412 in it)
Should go without saying, but this is my first CWM zip. it's been working fine for me the multiple times I've tested it. but you're on your own if you have problems. And i'm not responsible for damage.
NOTE: in my experience it doesn't matter where you get the Google Wallet APK from. I modified my build.prop to match the Galaxy Nexus and got it from the market. also tried the modified Modaco one from HERE with no change.
Click to expand...
Click to collapse
Im not even able to get past anything it just says my device is not supported

xso0j1nx said:
Im not even able to get past anything it just says my device is not supported
Click to expand...
Click to collapse
did you edit the Build.Prop to this?
Code:
ro.product.model=Galaxy Nexus
ro.product.name=yakju
ro.product.device=maguro
i had zero success editing the build.prop using the free stuff from the market. either make the changes from Root Explorer, or use ADB to pull it off the device, edit it and push it back on.

Well, I got Wallet to launch successfully, haven't used it yet but will do so tomorrow. Thanks for the help!

How did u add a card

farfromovin said:
Well, I got Wallet to launch successfully, haven't used it yet but will do so tomorrow. Thanks for the help!
Click to expand...
Click to collapse
And then I couldnt add a card...
Sent from my Galaxy Note 2

farfromovin said:
And then I couldnt add a card...
Sent from my Galaxy Note 2
Click to expand...
Click to collapse
this is where we're all getting stuck at. not sure what to do after that point. or what's causing the error in the first place...

I have used Google wallet and I already have cards added to my wallet account. Besides adding the card, has anyone tried just activating their current cards?

Esteef said:
I have used Google wallet and I already have cards added to my wallet account. Besides adding the card, has anyone tried just activating their current cards?
Click to expand...
Click to collapse
Yes tried activating current card , new cards, diffrent gmail. Maybe it has something to do with the nfc.apk if u try and change it. u wull lose nfc I think tmobile learned from the s3 not to make it so easy to get wallet working. If u open the apk w winrar you can see a lib file inside. Maybe thats key because wallet isnt seeing something from are phone that will get it to work like the s3 thread if u go into about in gwallet. Ull see controller applet version is empty thats what we need to figure out how to fix.esteef go into gwallet, about see if u have a controller applet version.thanks

b3ltazar said:
Yes tried activating current card , new cards, diffrent gmail. Maybe it has something to do with the nfc.apk if u try and change it. u wull lose nfc I think tmobile learned from the s3 not to make it so easy to get wallet working. If u open the apk w winrar you can see a lib file inside. Maybe thats key because wallet isnt seeing something from are phone that will get it to work like the s3 thread if u go into about in gwallet. Ull see controller applet version is empty thats what we need to figure out how to fix.esteef go into gwallet, about see if u have a controller applet version.thanks
Click to expand...
Click to collapse
If you were using GW on your last phone you have to either reset GW on the old device or login to GW in a browser and disable it. then you should be able to add the card. thats what i did at least. i also do it every time i flash a rom.

Ghuslez28 said:
If you were using GW on your last phone you have to either reset GW on the old device or login to GW in a browser and disable it. then you should be able to add the card. thats what i did at least. i also do it every time i flash a rom.
Click to expand...
Click to collapse
and that's letting you add the card on the Note II?

google wallet not working no matter what I try
so i get an error about root
ive installed the zip
changed the build.prop. with no luck
im on frosty v1

Has anyone tried using the older version?
1.5-R79-V5 -?-
http://forum.xda-developers.com/showthread.php?t=1881914
This works for others who get the same error message--
They say you have to push the .apk to /system/app, though--
(I'm not rooted yet, so I can't try it-- might root tonight and give it a shot.)

prepaidguy9081 said:
so i get an error about root
ive installed the zip
changed the build.prop. with no luck
im on frosty v1
Click to expand...
Click to collapse
it would still work when you get the unsupported device message the problem we are having is when adding cards we get unexpected error.

Going to try pulling more of the NFC based stuff from the international variants and pushing them onto ours to see if that makes an improvement. Right now all that zip does it update the libs down in /system/lib and /system/etc.
so, next test= NFC.apk and NFCtest.apk from the N7100. using the apk's from the I9300 cause bootloops.
EDIT: successfully pushed in the NFC apks from the N7100. but no change in Google Wallet when using the Modaco version.

crazy talk said:
Going to try pulling more of the NFC based stuff from the international variants and pushing them onto ours to see if that makes an improvement. Right now all that zip does it update the libs down in /system/lib and /system/etc.
so, next test= NFC.apk and NFCtest.apk from the N7100. using the apk's from the I9300 cause bootloops.
EDIT: successfully pushed in the NFC apks from the N7100. but no change in Google Wallet when using the Modaco version.
Click to expand...
Click to collapse
even the sprint and international note 2 users are having the same problems as us when adding cards. we need to find a note 2 that has gwallet enabled sucessfully. maybe the note 2 is lacking hardware?? this is frustrating

RANT
WTF!!! isnt this illegal for the to block since they are trying to "monopolize" so that we have to use their sh!t(ISIS) they are not allowing competition so that they can implement their own payment system whenever they get it ready????
sorry this has bugged me since i got my first note. and i know its been covered... i feel much better now.

[Q] How to use "Restrict background data" WITHOUT notification ?

Hi,
I wish to permanently use the "Restrict background data" feature ( under settings->data usage ) on my JB rom, but the problem is that when I enable that feature, I always get a notification, asking me to "touch to remove" that feature...
I don't wish to do that, even by mistake! I want that notification GONE completely, but to retain the "restrict" feature...
I understand, it's possible to permanently disable notifications, by altering "Settings.apk" somehow - but I don't know what and where to change ( wish file inside that apk ).
I used "apktool" to unpack the apk, but again - which file should I change ? what value/line should I delete ?
My rom is VJ's AOKP v2.2, so "Settings.apk" file is from that rom's version.
Any help would be great :highfive::fingers-crossed:
EDIT:
Guess it has something to do with "DataUsageSummary.smali" (after unpacking the Settings apk -> smali\com\android\settings):
BUT WHAT SHOULD I CHANGE ?!

please reply
gps3dx said:
Any help would be great :highfive::fingers-crossed:
Click to expand...
Click to collapse
Seriously ? Not even the smallest hint you ppl can give me ?:crying::crying:
Can't you even redirect me to the most prevalent sub-forum, here at XDA, for that kind of question ?:silly:

gps3dx said:
Seriously ? Not even the smallest hint you ppl can give me ?:crying::crying:
Can't you even redirect me to the most prevalent sub-forum, here at XDA, for that kind of question ?:silly:
Click to expand...
Click to collapse
Something called the search function; it's really useful.
You can't just expect others to answer your questions promptly. As for your questions, that's part of the android system and if you want to modify it, go ahead. It's not a notification because you can't swipe it away; it's an ongoing thing. SO if you want to go on with that kind of attitude, you can try it yourself.

droid_<3er said:
Something called the search function; it's really useful.
As for your questions, that's part of the android system and if you want to modify it, go ahead. It's not a notification because you can't swipe it away; it's an ongoing thing.
Click to expand...
Click to collapse
I really do appreciate your reply man - even though I googled xda from top to button.
( there are thread about modifying various stuff inside settings.apk / SystemUI.apk - but NON are about that "restriction notification" i'm talking about. )

I've seen this thread in the unread threads of XDA app and although I don't use that feature, I got curious to try it out. So I've quickly put together an Xposed module that removes the notification.
You have to install Xposed framework. Get it here: http://forum.xda-developers.com/showthread.php?t=1574401
Also, install my module from the attachment, enable it and do a soft reboot in Xposed.
It works for me on my Galaxy R with CM10.1 and I assume it will work for you too, as the module doesn't change the Settings, but com.android.server.net.NetworkPolicyManagerService class. If you have any problems, post a logcat and /data/xposed/debug.log
Update: For a while now it's already available in Xposed modules repository: http://repo.xposed.info/module/org.adam77root.removerestrictednotification.

Adam77Root said:
I've seen this thread in the unread threads of XDA app and although I don't use that feature, I got curious to try it out. So I've quickly put together an Xposed module that removes the notification.
You have to install Xposed framework. Get it here: http://forum.xda-developers.com/showthread.php?t=1574401
Also, install my module from the attachment, enable it and do a soft reboot in Xposed.
It works for me on my Galaxy R with CM10.1 and I assume it will work for you too, as the module doesn't change the Settings, but com.android.server.net.NetworkPolicyManagerService class. If you have any problems, post a logcat and /data/xposed/debug.log
Click to expand...
Click to collapse
WOW thnx... but just a few moments before you posted your message I to fulfill that wish of mine... I SOLVED IT !
Although I admit - I DO NOT KNOW if I disabled all of the "restrict background" feature, but I DO managed to enable the "restrict backgound data" checkbox ( then press OK at the popup ) WITHOUT getting any notification at all !
HOW TO DISABLE NOTIFICATION ALERT FOR "RESTRICT BACKGROUND DATA" ( under settings-> data usage-> options )​( I tried that fix on JB 4.2.2 ( to be specific: AOKP VJ Jelly Bean v2.2), BUT I guess it works on all JB 4.2.2 )​1. copy "services.jar" from "/system/framework/services.jar" to your computer.
MAKE A SAFE COPY OF THIS FILE IF SOMETHING HAPPENS TO YOU.
2. extract the jar file using Winrar or any compatible app.
3. using MultiTool decompile the "classes.dex" file as instructed by Multitool's thread.
4. open with any txt editor ( I used Notepad++ ) the file "NetworkPolicyManagerService.smali" under "decompiled\classout\com\android\server\net\" ( which is a sub-folder of Mulitool's folder that you've previously extracted )
5. A . search for:
Code:
invoke-interface/range {v0 .. v6}, Landroid/app/INotificationManager;->enqueueNotificationWithTag(Ljava/lang/String;Ljava/lang/String;ILandroid/app/Notification;[II)V
delete completely that line or add "# " in the start of that line ( which is what I did ) so that line looks like that:
Code:
# invoke-interface/range {v0 .. v6}, Landroid/app/INotificationManager;->enqueueNotificationWithTag(Ljava/lang/String;Ljava/lang/String;ILandroid/app/Notification;[II)V
B. search for:
Code:
invoke-virtual {v0, p1}, Ljava/util/HashSet;->add(Ljava/lang/Object;)Z
add "# " in the start of that line ( which is what I did ) or delete completely that line
6. SAVE that smali file that you've just edited.
7. using Multitool, recompile the classes.dex file.
if everything went good, you'll have classes.dex file under MultiTool's sub-folder named "output"
8. using Winrar, open "services.jar", replace the current "classes.dex" with the recompiled one that you've made.
9. copy the remade "services.jar" to your device(using adb etc ):
Code:
adb push "services.jar" /system/framework/services.jar
10. chmod "services.jar" to "-rw-r--r--", meaning you need to:
Code:
adb shell chmod 644 /system/framework/services.jar
11. restart your device, and It should rebuilt your dalvik cache.
ONLY if it didn't, I guess you should delete "/data/dalvik-cache/[email protected]@[email protected]" file, reboot again so your OS will create that dalvik-cache file.
I'll be happy to know if anyone can verify that indeed my fix just remove his/her notification, but retain the ability to disable background data. THANKS !

Sorry I doubted you. You are a genius!

Many thanks!!
Adam77Root, thank you so much for that module! I can confirm it working on my Galaxy Note 2. That notification was unbelievably annoying.
gps3dx, thank you too for this thread and your fix. While I didn't try it because I already have Xposed framework installed and I'd rather use the less invasive approach, I am still grateful for your seeing a problem, addressing it, and proactively doing something about it. My respects to you. I searched around quite a bit and came across many other forums on different sites where people had this same problem unanswered. I hope they find their way to this thread.
To the above poster who jumped down the OP's throat for bumping this topic 4 days after it went unanswered, obviously you didn't do any search on this topic yourself. I did. And until this thread, I found nothing really useful. And lo-and-behold, someone was kind enough to actually do something useful instead of pointlessly sitting there and criticizing. The squeaky wheel gets the grease. Rudely telling someone to 'check their attitude and search' is not helpful- it's just rude and pointless. Just FYI.

I have an i9300 and I can't find the first line in that archive...

eXtremeDevil said:
I have an i9300 and I can't find the first line in that archive...
Click to expand...
Click to collapse
mybe it is because you run JB 4.1.2 not 4.2.2 like I do, plus mybe you're running some custom framework ( it is not AOKP as I suspect from you sig )

Adam77Root said:
...I've quickly put together an Xposed module that removes the notification.
Click to expand...
Click to collapse
@Adam77Root
Big thanks for this module: I installed another 4.2.2 JB rom for my HTC Desire, and your module works !:good::good:

Adam77Root said:
I've seen this thread in the unread threads of XDA app and although I don't use that feature, I got curious to try it out. So I've quickly put together an Xposed module that removes the notification.
You have to install Xposed framework. Get it here: http://forum.xda-developers.com/showthread.php?t=1574401
Also, install my module from the attachment, enable it and do a soft reboot in Xposed.
It works for me on my Galaxy R with CM10.1 and I assume it will work for you too, as the module doesn't change the Settings, but com.android.server.net.NetworkPolicyManagerService class. If you have any problems, post a logcat and /data/xposed/debug.log
Click to expand...
Click to collapse
this was working fine on my aokp jb mr1 Milestone 2, but stopped working when i installed the nigthly nightly (jb-mr1)2013-08-21 (wich fixes my camera issues and soe other stuff)
is there anything i can try myself to fix this or is it just incopatible with that nightly? (its still 4.2)

I'm using Lenovo phone, 4.2.1 Version. In "services.jar" I see only folder "META-INF" and file "MANIFEST.MF". I tried to rename the file to classes.dex then using MultiTool decompile but I receive: "Unexpected top-level exception:java.lang.RuntimeException:bad magic value...etc"
So what's wrong, where to find classes.dex? Someone?
new edit: Thanks a lot for all the replies, also Xposed framework+module didn't work.

Adam77Root said:
I've seen this thread in the unread threads of XDA app and although I don't use that feature, I got curious to try it out. So I've quickly put together an Xposed module that removes the notification.
You have to install Xposed framework. Get it here: http://forum.xda-developers.com/showthread.php?t=1574401
Also, install my module from the attachment, enable it and do a soft reboot in Xposed.
It works for me on my Galaxy R with CM10.1 and I assume it will work for you too, as the module doesn't change the Settings, but com.android.server.net.NetworkPolicyManagerService class. If you have any problems, post a logcat and /data/xposed/debug.log
Click to expand...
Click to collapse
Thanks a lot. Works awesome. Is it possible to post the source code to this?

css771 said:
Thanks a lot. Works awesome. Is it possible to post the source code to this?
Click to expand...
Click to collapse
I'm almost certain I don't have the original files anymore. Since it's pretty simple, you can either decompile the apk or check Android source of the class I mentioned in the post you quoted. Only one function is replaced with returning null.
Edit: Just checked, the function is enqueueRestrictedNotification.
Sent from my OmniROM-powered LG Optimus 4X HD

Xposed module works perfect on LG G2. Thanks a bunch!
Sent from my VS980 4G using Tapatalk

Adam77Root said:
I've seen this thread in the unread threads of XDA app and although I don't use that feature, I got curious to try it out. So I've quickly put together an Xposed module that removes the notification.
You have to install Xposed framework. Get it here: http://forum.xda-developers.com/showthread.php?t=1574401
Also, install my module from the attachment, enable it and do a soft reboot in Xposed.
It works for me on my Galaxy R with CM10.1 and I assume it will work for you too, as the module doesn't change the Settings, but com.android.server.net.NetworkPolicyManagerService class. If you have any problems, post a logcat and /data/xposed/debug.log
Click to expand...
Click to collapse
nice module.. work perfectly.. thanks

rooting?
do i have to root my phone to do this? will the module work without rooting? i'm new to playing with codes on my phone but I have done a lot of work with linux before so i can understand the process, i've just never rooted my phone before. i'd really like to get rid of this notification and the "usb connectivity" app's notification: internal storage &SD card- internal storage &SD card connected to PC. I mean, do i really need a notification to tell me that my phone is connected to my PC?
that last request isn't as important, at least if i accidentally click on that i'm not turning on background data use!
-yasboss
xperia z1s
jb 4.3
(just joined xda devs)
p.s.
is this the right place to ask this question?

yasboss said:
do i have to root my phone to do this? will the module work without rooting? i'm new to playing with codes on my phone but I have done a lot of work with linux before so i can understand the process, i've just never rooted my phone before. i'd really like to get rid of this notification and the "usb connectivity" app's notification: internal storage &SD card- internal storage &SD card connected to PC. I mean, do i really need a notification to tell me that my phone is connected to my PC?
that last request isn't as important, at least if i accidentally click on that i'm not turning on background data use!
-yasboss
xperia z1s
jb 4.3
(just joined xda devs)
p.s.
is this the right place to ask this question?
Click to expand...
Click to collapse
you need root to use xposed installer..

what else can it be used for?
ajeesh vijayan said:
you need root to use xposed installer..
Click to expand...
Click to collapse
can i use it for other notifications like i asked? I mean there's more than just the USB connectivity etc

[MOD][WIP] Google Wallet - Tap and Pay - Post 2 important link[8 Oct 13]

This is a work in progress. All that is needed is now are the correct libs or a lib fix. Tap and Pay will not even attempt to set up with the stock build.prop. What you have to do is change the build.prop to the Galaxy Nexus and then it will have you turn NFC on and attempt to set up the phone but we will need a lib fix much like for the S4
{
"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"
}
IMPORTANT INFO AND LINKS - PLEASE READ - ESPECIALLY AOSP USERS​
Note II - I got Working Google Wallet from here - Refer to Crazy Talk OP ----> Click Here
For Galaxy S4-----> joemagistro thread - Click Here
Click to expand...
Click to collapse
Recommended build.prop Editor - Jrummy Build Prop Editor
Click to expand...
Click to collapse
AOSP USERS - FOR OLDER METHODS ONLY - Method 1 was an attempted way to reduce steps, if this does not work, do not worry, uninstall Google Wallet and clear the app data and cache, reboot to recovery and do a wipe cache and dalvick cache, reboot and move to Method 2, you should have no issues
Click to expand...
Click to collapse
ALWAYS! ALWAYS! ALWAYS! RESET GOOGLE WALLET BEFORE YOU FLASH A NEW ROM OR YOU COULD LOSE IT FOREVER
Click to expand...
Click to collapse
BEWARE - BEFORE YOU BEGIN - 1st Picture provided by fireishott - 2nd Picture by firstflyer
After seeing people struggle and research, this appears to still block Google Wallet from completely setting up and initializing. The regular SIM cards do not do it, but the ISIS or NFC appears to be doing the damage. I am not sure if it is possible to switch to a non NFC SIM, but you are more than likely OUT OF LUCK with this SIM Card...Remember this does not guarantee success, but if you hit a wall and just can't get any luck it is a last ditch effort and probable cause to your issues
Refer to Troubleshooting Step 4 in post #2 to possibly solve the issue
Click to expand...
Click to collapse
​
Work in Progress - Method 1 - Preferred - This will be what it looks like - Universal for TW/AOSP/Deodex/Odex ROMS
1. Make sure you don't have the wallet apk installed and if you do, wipe the data and cache of the app, then uninstall or if you have it in the system, delete it.
2. Make sure you turn off "auto-update" in the play store for the wallet app.
3. Download
TouchWiz Only----> DO NOT DOWNLOAD YET!! Patched Wallet & NFC Lib Fix
AOSP Only----> DO NOT DOWNLOAD YET!! AOSP Wallet
4. Change build.prop to Galaxy Nexus - Use Jrummy Build.prop Editor (Changes did not stick with reboot) or Root Exolorer - (DO NOT RESTART UNTIL ALL 3 PARTS ARE CHANGED)
Galaxy Nexus
ro.product.device=maguro
ro.product.model=Galaxy Nexus
ro.product.name=yakju
5. Reboot into Recovery
6. Flash Note 3 Libs You downloaded in Step 2 - (ALWAYS WIPE CACHE AND DALVICK BEFORE FLASHING ZIPs)
7. Reboot Phone
8. Open the wallet app and start the setup. Wallet should already be installed from when you flashed the zip in recovery! It might take some time, so be a bit patient. (Make Sure NFC is ON)
10. Set Up Tap and Play so it's 100% and ready to make purchases (you should see the credit card you have on file - if not Add One).
11. Reboot again, just so you can test
12. Change Your build.prop back to stock once you verify Wallet Opens with no issues
T-Mobile Galaxy Note 3
ro.product.device=hltetmo
ro.product.model=SM-N900T
ro.product.name=hltetmo
MORE INFO
Originally Posted by siraltus View Post
OK, here's some technical info.
The Play Store installs two different versions of the Wallet 2.0 app, depending on whether you present yourself as an NFC-pay supported phone (via build.prop values) or not.
If you change your build.prop to be, say, the Sprint Note 2 (SPH-L900 t0ltespr) and then install Wallet from the Play Store, you will get the NFC-pay enabled version. All other phones get the "castrated" version.
Now, on Note 3, even if you do that, there a few things Sucksung/T-Mobile did in the stock ROM (completely reversible) to make NFC-pay on Wallet not work.
First, they removed the Wallet signature keys from /etc/nfcee_access.xml, so Wallet will complain it doesn't have sufficient privileges to the secure element. That's fine - you just add the keys back (get them from any AOSP ROM), and boom, Wallet has access to the secure element again.
Then, there are a few other bits and pieces of system software (libraries and kernel modules) that I'm trying to figure out that need to be in place for Wallet to work, as right now it just FCs. If not me, then someone will probably beat me to putting together a "fix" ZIP package that will re-enable Wallet on the stock ROM.
This problem, of course, will not be present on any AOSP ROM as all the required bits are included in those by default.
Also, remember Wallet 2.0 no longer includes a root, region, or carrier check, so "Wallet Patcher" plugins for XPosed or anything like that are not required.
The way to set up NFC-pay enabled Wallet 2.0 on an unsupported device (with a ROM that hasn't been carrier-castrated to disable NFC-pay):
1. Change your build.prop to masquerade as a supported device (e.g., SPH-L900 t0ltespr) and reboot.
2. Go to Play Store, install Wallet.
3. Launch Wallet and set it up as usual. Once it finishes and you see "Ready to Tap and Pay" undearneath your Wallet balance, you're good.
4. Restore your build.prop to its original values and reboot. Wallet NFC-pay will remain working.
Click to expand...
Click to collapse
Give Thanks To:
Hopefully Can Fill This In Soon!
If you were left out its not by intention just PM Me

CLICK RED LETTERS....... IT IS A LINK ON WRITE UP TO MODIFY NfcNci.apk to use secure element
Based on this read, all I think we need is the nfcee_access.xml with the google Keys which I already have.....and then we need to modify the NfcNci.apk
As far as the libs go, they might be extra, however they don't cause harm being in the system at all....I want to try with and without...I will if I can learn how to decompile the apk like in the write up. Pretty close to an answer at this point

Got the Release Keys from AOSP ROM and got past the error above but Wallet is foreclosing......I have tried pulling the libs from sprint but im sure there is some framework edits minor if at all. Giving it a rest tonight...Reaching out from help and keeping a look out on progress

Op I don't know if this will help you any but it worked well on my old s3 alot of people claim it works on the s4 you might want to check it out.
http://forum.xda-developers.com/showthread.php?t=2457569
Sent from my SAMSUNG-SM-N900A using xda app-developers app

Just to warn everyone, as it says in the OP, do not flash that package at all. Especially since TWRP restoring doesn't work.

Glad you are taking this project on!I'll I can't wait until you get it figured out! Keep up the Good work!
Sent from my Galaxy Nexus using XDA Premium 4 mobile app

Anyone try ISIS?
It's ****. They disable amazing gwallet for this stupid proprietary ****.
Doesn't work on root, only supports 3 card companies.
Note 3 came with isis card and bloatware, yet they forgot this app. Avoid this trash. They are cowards.
Let's get gwallet working

wing_addict_usa said:
Anyone try ISIS?
It's ****. They disable amazing gwallet for this stupid proprietary ****.
Doesn't work on root, only supports 3 card companies.
Note 3 came with isis card and bloatware, yet they forgot this app. Avoid this trash. They are cowards.
Let's get gwallet working
Click to expand...
Click to collapse
It works on root if you install the ISIS Root Bypass mod for Xposed.
That said, it is utter garbage. Slow, clunky, poorly laid out, and generally trash. Good it uses the secure element in the ISIS SIM card and not in the phone so you can use Google Wallet concurrently.

firefreak664 said:
Op I don't know if this will help you any but it worked well on my old s3 alot of people claim it works on the s4 you might want to check it out.
http://forum.xda-developers.com/showthread.php?t=2457569
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
Def am looking at that, thanks for that info, I am trying to pull from the international version as well as any CM bases

@bdorr1105 I see something in the zip that may be causing an issue....
system > lib > hw > nfc_nciMSM8960.so
MSM8960 is for dual core qualcomm not quad core. For Note 3 it's nfc.MSM8974.so
If you're going to add a nfc_nci patched file, it'd still have to be MSM8974 I believe...

itsmikeramsay said:
@bdorr1105 I see something in the zip that may be causing an issue....
system > lib > hw > nfc_nciMSM8960.so
MSM8960 is for dual core qualcomm not quad core. For Note 3 it's nfc.MSM8974.so
If you're going to add a nfc_nci patched file, it'd still have to be MSM8974 I believe...
Click to expand...
Click to collapse
Yea thanks I have the MSM8974.so from the sprint Note 3, thats what I am pulling from as well as from the international and seeing what works. Those zips are for the Note 2, its just an example, I didn't remove the links from my other OP, I am just giving a preview of what the OP will look like

bdorr1105 said:
Yea thanks I have the MSM8974.so from the sprint Note 3, thats what I am pulling from as well as from the international and seeing what works. Those zips are for the Note 2, its just an example, I didn't remove the links from my other OP, I am just giving a preview of what the OP will look like
Click to expand...
Click to collapse
AH I see ok gotcha. Great, if anything comes to mind I'll let you know bro...

darkjedi said:
Just to warn everyone, as it says in the OP, do not flash that package at all. Especially since TWRP restoring doesn't work.
Click to expand...
Click to collapse
huh?
Restore worked for me....

itsmikeramsay said:
AH I see ok gotcha. Great, if anything comes to mind I'll let you know bro...
Click to expand...
Click to collapse
Thanks appreciate it

thinkjoey said:
huh?
Restore worked for me....
Click to expand...
Click to collapse
Which version are you using?

So I tried everything so far, libs, etc, I noticed that NFC will turn on with the NFC apks, but when you swap back to the originals NFC turns on, I am still stock and I think ODEX has something to do with it, I will experiment now on the Deodexed ROM and see what happens.

itsmikeramsay said:
Which version are you using?
Click to expand...
Click to collapse
I am trying to find it. I guess i can go into recovery
i have v2.6.3.1
I had to restore yesterday when something did not install alright...restored fine

bdorr1105 said:
So I tried everything so far, libs, etc, I noticed that NFC will turn on with the NFC apks, but when you swap back to the originals NFC turns on, I am still stock and I think ODEX has something to do with it, I will experiment now on the Deodexed ROM and see what happens.
Click to expand...
Click to collapse
Yeah I'd recommend using a deodexed ROM... Try stock deodexed....
thinkjoey said:
I am trying to find it. I guess i can go into recovery
i have v2.6.3.1
I had to restore yesterday when something did not install alright...restored fine
Click to expand...
Click to collapse
Ok cool, seems the most stable is 2.6.3.1, users can't restore with x.x.x.0 or x.x.x.2

itsmikeramsay said:
Yeah I'd recommend using a deodexed ROM... Try stock deodexed....
Ok cool, seems the most stable is 2.6.3.1, users can't restore with x.x.x.0 or x.x.x.2
Click to expand...
Click to collapse
Def trying stock deodexed, the libs are not named the same either....
I can give examples from the lib folder....changing any of the names of the Sprint libs to match TMO Stock don't work, but I think i was on to something, I think the can coexist together, and it will use depending on the nfc.apk, but ODEX cause me issues, I redolved the Google RSA Keys issue, thats bypassed, if I can get NFC to turn on after the lib swap then hopefully will be good. the NFC Access is good to go. I know it didnt force close NFC until I went back to the stock NFC apk

No luck still....wallet force closes, not exactly sure what is causing it. I switched the NfcNci.apk and NfcTest.apk with Sprint and it broke NFC....went back to stock and NFC turns on. I can only fix Insufficient RSA Keys.
Sent from my SM-N900T using XDA Premium 4 mobile app

[Q] could someone help me in Bluetooth.apk?

I did some modifications to Bluetooth share in /system/app/Bluetooth.
But after that I pushed the app via adb...then a lot of error messages that said (Bluetooth Share Stopped).
Then I removed the modified Bluetooth app and pushed the stock one via adb and rebooted the device but the error message still appears although I make
1) wipe cache+dalvik
2) reflash the kernel
Why the error message still appears although I used the stock unmodified app.
Where is the problem?
Could someone help me with this problem?
Here are some logs
{
"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"
}

Check your ROM zip for symlink. Different Bluetooth Sharing apk may require different different libbluetooth_jbi.so if linked to /system/app/Bluetooth/lib/arm folder from /system/lib/libbluetooth_jni.so For that reason, you have to watch for 0 bit lib files when pulling application from another ROM flashed on phone. (It may been a symlink if true).
Did you try verifying permissions and ownership and clearing data for Bluetooth Sharing and reboot?
Got a backup? If not, try dirty flashing ROM. You may just have to start over. Consider making a backup before making changes.
Sent from my SM-N930P using Tapatalk

samep said:
Check your ROM zip for symlink. Different Bluetooth Sharing apk may require different different libbluetooth_jbi.so if linked to /system/app/Bluetooth/lib/arm folder from /system/lib/libbluetooth_jni.so For that reason, you have to watch for 0 bit lib files when pulling application from another ROM flashed on phone. (It may been a symlink if true).
Did you try verifying permissions and ownership and clearing data for Bluetooth Sharing and reboot?
Got a backup? If not, try dirty flashing ROM. You may just have to start over. Consider making a backup before making changes.
Sent from my SM-N930P using Tapatalk
Click to expand...
Click to collapse
How to verify permission and ownership from terminal?
Yes I have a backup but I want to know more about the problem.
I have some logcat about the problem.
It may help to figure out what happened
And

Could be mismatch of apk and lib. Did you replace both and set a new link?
It's easy to set with a root browser.
Sent from my SM-N930P using Tapatalk

samep said:
Could be mismatch of apk and lib. Did you replace both and set a new link?
It's easy to set with a root browser.
Sent from my SM-N930P using Tapatalk
Click to expand...
Click to collapse
Thank you very much @samep
Yes that works like a charm.
Recreate the symlink solve my problem.

samep said:
Could be mismatch of apk and lib. Did you replace both and set a new link?
It's easy to set with a root browser.
Sent from my SM-N930P using Tapatalk
Click to expand...
Click to collapse
can u give me a easy throughput as a newbie ?

hessamx said:
can u give me a easy throughput as a newbie ?
Click to expand...
Click to collapse
I think the members moved on to oyher endeavors. Not much activity on the Sprint Note 4. However, I used this method posted by Lawyer-06 to port some system apps and CSC files from my stock rooted rom to a customer rom I was having issues with.
https://forum.xda-developers.com/showpost.php?p=60831252&postcount=3443

hessamx said:
can u give me a easy throughput as a newbie ?
Click to expand...
Click to collapse
Mr. JAVI said:
I think the members moved on to oyher endeavors. Not much activity on the Sprint Note 4. However, I used this method posted by Lawyer-06 to port some system apps and CSC files from my stock rooted rom to a customer rom I was having issues with.
https://forum.xda-developers.com/showpost.php?p=60831252&postcount=3443
Click to expand...
Click to collapse
Nice tutorial share. Thanks for helping.
What may be missing is linking the lib so the application works. It's a matter of checking original file as installed on phone before replacing and duplicating with a root browser. Long press the lib file, scroll through options, select link to this folder (maybe last option) and then browsing and selecting same folder location as seen from original link. Hint: the lib linking and appearance in its location will look the same when linked properly.
In the case of this thread, unzipping the ROM and reading the install scripts for proper linking may have been done to link the files after installing. The Bluetooth application simply needed to know where to get it's vital resources to work with. There are exceptions where replacing apk and lib, setting permissions, clearing data and rebooting aren't enough. Developers may write install scripts into patch zip accordingly as needed to get this done without a ROM update. Or even alternately in an aroma installer. Or those that test ROMs to support a developer may need to do this manually in that support capacity. Then again, it could be user in another country or region needing to make changes for themselves in order to use a developed ROM.
Sent from my PH-1 using Tapatalk

samep said:
Nice tutorial share. Thanks for helping.
What may be missing is linking the lib so the application works. It's a matter of checking original file as installed on phone before replacing and duplicating with a root browser. Long press the lib file, scroll through options, select link to this folder (maybe last option) and then browsing and selecting same folder location as seen from original link. Hint: the lib linking and appearance in its location will look the same when linked properly.
In the case of this thread, unzipping the ROM and reading the install scripts for proper linking may have been done to link the files after installing. The Bluetooth application simply needed to know where to get it's vital resources to work with. There are exceptions where replacing apk and lib, setting permissions, clearing data and rebooting aren't enough. Developers may write install scripts into patch zip accordingly as needed to get this done without a ROM update. Or even alternately in an aroma installer. Or those that test ROMs to support a developer may need to do this manually in that support capacity. Then again, it could be user in another country or region needing to make changes for themselves in order to use a developed ROM.
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
thanks for replying but i have log cat and its said cant find some files can u help me ?
E/AndroidRuntime(11055): Process: com.android.bluetooth, PID: 11055
E/AndroidRuntime(11055): java.lang.RuntimeException: Unable to instantiate application com.android.bluetooth.btservice.AdapterApp: java.lang.ClassNotFoundException: Didn't find class "com.android.bluetooth.btservice.AdapterApp" on path: DexPathList[[zip file "/system/framework/javax.obex.jar", zip file "/data/app/com.android.bluetooth-2/base.apk"],nativeLibraryDirectories=[/data/app/com.android.bluetooth-2/lib/arm64, /data/app/com.android.bluetooth-2/base.apk!/lib/armeabi-v7a, /vendor/lib, /system/lib]]
Click to expand...
Click to collapse

hessamx said:
thanks for replying but i have log cat and its said cant find some files can u help me ?
Click to expand...
Click to collapse
Sorry. Gotta say I'm not experienced with resolving an issue like this. Not sure what you're doing when getting this logcat? References to zipped files? Should they be zipped?
What I would do in a situation like this and ensure I've done everything properly. Could be a simple mistake.
Otherwise, no idea if this helps you or not but a little searching found this blog:
https://javarevisited.blogspot.com/2011/08/classnotfoundexception-in-java-example.html?m=1
If Java tutorials makes sense to you, there's some suggested fixes to look into. Maybe it helps? Best wishes you resolve this and learn enough to help the next guy.
Sent from my PH-1 using Tapatalk

samep said:
Nice tutorial share. Thanks for helping.
What may be missing is linking the lib so the application works. It's a matter of checking original file as installed on phone before replacing and duplicating with a root browser. Long press the lib file, scroll through options, select link to this folder (maybe last option) and then browsing and selecting same folder location as seen from original link. Hint: the lib linking and appearance in its location will look the same when linked properly.
In the case of this thread, unzipping the ROM and reading the install scripts for proper linking may have been done to link the files after installing. The Bluetooth application simply needed to know where to get it's vital resources to work with. There are exceptions where replacing apk and lib, setting permissions, clearing data and rebooting aren't enough. Developers may write install scripts into patch zip accordingly as needed to get this done without a ROM update. Or even alternately in an aroma installer. Or those that test ROMs to support a developer may need to do this manually in that support capacity. Then again, it could be user in another country or region needing to make changes for themselves in order to use a developed ROM.
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
I just want to say, thank you samep. I really appreciate your input on this subject. Your way of explaining this is well put and your points are valid. Bluetooth issues is something I have not had in any custom rom as of yet. However, I like to be prepared and knowledge is power.
Thought I'd give a little of my personal background followed by a few questions. I have no formal education with computers or Android. Although, I have not been a member on XDA for very long, I have been on this site for many years. Having lost my previous N4,
the only n910ps for sale were on the latest update 5DQ15. The fused 5 aboot prevents downgrading to previous firmwares. No chance of downgrading the boot or modem without SW REV CHECK Odin fail. Fortunately, 6.0 MM roms can still be flashed. With every single custom rom I flashed, my hotspot settings disappeared, except stock rooted deodexed roms. in which the hotspot setting remained. I remember reading a post somewhere on XDA stating that it was in CSC others.xml so I copied the entire CSC in stock rooted rom to external sd then flashed the custom rom and with the tutorial in the link above I replaced the custom roms CSC's with the stock rooted CSC's. Rebooted to TWRP wiped dalvik /chache and booted the phone. My Hotspot now appeared in the custom rom settings. However, I am not questioning your information. In fact, I remember reading an XDA thread about custom rom development that specifically backs up what you stated. More to it than simple copy and past, Its just I didnt know any other way. Although this worked for me with setting option , I know the phones Bluetooth connection is a bit more intricate than a simple CSC others.xml.
Which brings me to my question and I quote "Long press the lib file, scroll through options, select link to this folder (maybe last option)" What root browser do you recommend. This option is not provided as an option when I long press with my current root file manager. Yea, I know ES file manager has been kick of Google PS but Im still using it . LOL.. I wish to thank you ince again for your very informative posts.

Mr. JAVI said:
I just want to say, thank you samep. I really appreciate your input on this subject. Your way of explaining this is well put and your points are valid. Bluetooth issues is something I have not had in any custom rom as of yet. However, I like to be prepared and knowledge is power.
Thought I'd give a little of my personal background followed by a few questions. I have no formal education with computers or Android. Although, I have not been a member on XDA for very long, I have been on this site for many years. Having lost my previous N4,
the only n910ps for sale were on the latest update 5DQ15. The fused 5 aboot prevents downgrading to previous firmwares. No chance of downgrading the boot or modem without SW REV CHECK Odin fail. Fortunately, 6.0 MM roms can still be flashed. With every single custom rom I flashed, my hotspot settings disappeared, except stock rooted deodexed roms. in which the hotspot setting remained. I remember reading a post somewhere on XDA stating that it was in CSC others.xml so I copied the entire CSC in stock rooted rom to external sd then flashed the custom rom and with the tutorial in the link above I replaced the custom roms CSC's with the stock rooted CSC's. Rebooted to TWRP wiped dalvik /chache and booted the phone. My Hotspot now appeared in the custom rom settings. However, I am not questioning your information. In fact, I remember reading an XDA thread about custom rom development that specifically backs up what you stated. More to it than simple copy and past, Its just I didnt know any other way. Although this worked for me with setting option , I know the phones Bluetooth connection is a bit more intricate than a simple CSC others.xml.
Which brings me to my question and I quote "Long press the lib file, scroll through options, select link to this folder (maybe last option)" What root browser do you recommend. This option is not provided as an option when I long press with my current root file manager. Yea, I know ES file manager has been kick of Google PS but Im still using it . LOL.. I wish to thank you ince again for your very informative posts.
Click to expand...
Click to collapse
I can appreciate your background and effort and even the experiences you share. Best wishes for your success.
I used to use script manager pro for a root browser. When I started working with developers in XDA, they pointed me to Root Explorer by speedsoftware (link below). I use it exclusively since and find it as capable as the other. I had gotten this one years earlier as a free promotional app on Amazon Prime through their Android app store. I was ecstatic when the developers of Root Explorer asked for my license key to transfer it to Google Play! Really? I asked, not expecting satisfaction, and they complied stating they've done it for others as well. It's their discretion and pleasure to do so. The app is still in Google Play; I get my updates there now.
https://play.google.com/store/apps/details?id=com.speedsoftware.rootexplorer
But I haven't done much at all since leaving the Note 4 and Sprint. I forget so much when not using it. Sad but true and being honest. I miss those days but always wanted better data coverage and a faster phone. But even that's a work in progress.
Sent from my PH-1 using Tapatalk