Develop Bugs

[ROM] Vanilla AOSP 4.0.4 IMM76L with root and busybox (Updated with MODS) 6/12/12

Hey everyone.
I just wanted to share an ultra prestine build of the latest AOSP source, sync'ed tonight and compiled clean. I know there are ROMs with all sorts of great mods, pieces taken from CM9 and AOKP, linaro optimization, etc.... that isn't this ROM. This is simply the latest Google source of 4.0.4 IMM76L with root and busybox.
I built it for me and thought I'd share. Feel free to use it... or not.
As always, don't forget to Nandroid.
ROM:
http://www.mediafire.com/?o9xkbxocy3yqhf5
3/12/12 11:30pm - Updated so reported model is "Galaxy Nexus". Thanks al2x for pointing it out.
The latest ICS GAPPS work for this one too:
http://goo.im/gapps/gapps-ics-20120429-signed.zip
MODS:
The following mods I've tested and work with this ROM:
Mods found in mwalts AOSP ROM also work for mine.
http://forum.xda-developers.com/showthread.php?t=1631796
Native Tethering Patch (mwalt2)
http://d-h.st/6se
Enhanced Power Menu with Native Tether (mwalt2)
http://d-h.st/RdT
Battery with Percentage Mod (CMO220)
http://dl.dropbox.com/u/31971676/BatMod.zip
Stock Boot Animation - hi-res (Thanks NHLWil)
http://forum.xda-developers.com/showpost.php?p=27332536&postcount=13
Keyboard APK with dictionary (for now)
http://www.mediafire.com/?qdavsrl5c64rxbf

I've been struggling to get all my binaries together to build from source and what
I have to know are tethering provisions removed in a build like this?
****Tether Subscription Check is not removed in build 061112_211425****

doobie711 said:
I've been struggling to get all my binaries together to build from source and what
I have to know is are tethering provisions removed in a build like this?
Click to expand...
Click to collapse
I don't think anything is taken out from vanilla to prevent you from using a tethering app for rooted phones in the market. I don't tether so I don't know for sure though.

I was referring to the native ICS tethering option under "More..." in "Settings". I'll try it out and update my own post with an answer.

This is great, I hope you can continue this style of being 100% stock with root/bb as the updates continue to flow for the GN...
I'm going to be flashing soon but I do tether so I hope it bypasses the subscription check...

It does not bypass the subscription check. but I'm pretty sure an edit of the framework.apk can fix that.

I'll try to update op with some mods tomorrow.
Sent from my Full AOSP on Toro-VZW using Tapatalk 2

doobie711 said:
I was referring to the native ICS tethering option under "More..." in "Settings". I'll try it out and update my own post with an answer.
Click to expand...
Click to collapse
You have to make a couple changes to the device repo to get the stock ICS tethering options included.

imnuts said:
You have to make a couple changes to the device repo to get the stock ICS tethering options included.
Click to expand...
Click to collapse
Thanks. I think I found the changes. I'll give it a shot when I get home from work.

Updated OP with Tethering, Menu, and Battery mod links.

mmuzzy, I've been using the ROM and it's been pretty snappy. The first flash didn't go so well, there were a few force close/force waits but i reflashed it now with a new download and I think it's been good.
One request is if you could possibly edit the name computers pickup as the MTP device... it recognizes it as "Full AOSP on Toro-VZW" rather than simply "Galaxy Nexus" lol

If there is any way you could include the stock Galaxy Nexus boot animation, that would be great, otherwise this rom is great!
thanks

Snakehn said:
If there is any way you could include the stock Galaxy Nexus boot animation
Click to expand...
Click to collapse
Attached.
Higher definition versions here:
http://forum.xda-developers.com/showthread.php?t=1380655

This intrigues me. Might try it soon. I've wanted a 100% stock build and nobody had really made one. They all usually come with "tweaks and enhancements" pre installed.
Sent from my Galaxy Nexus using xda premium
Edit: flashed it so far so good but it thinks every word I type is wrong. As well as the IME switcher always being shown when typing and no other keyboards installed
{
"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"
}
Edit #2: saw a thread about a differnt rom needing specific gapps and without them it would do that gonna flash the ones from OP even though I have the 429 gapps already
Edit #3: thought that fixed it but it didn't. Maybe with a clean install with the gapps. I'll have to try in the morning.
Edit...again: more searching is bringing up that the ICS dictionary is missing or that there is a problem with the keyboard apk.

al2x said:
mmuzzy, I've been using the ROM and it's been pretty snappy. The first flash didn't go so well, there were a few force close/force waits but i reflashed it now with a new download and I think it's been good.
One request is if you could possibly edit the name computers pickup as the MTP device... it recognizes it as "Full AOSP on Toro-VZW" rather than simply "Galaxy Nexus" lol
Click to expand...
Click to collapse
Snakehn said:
If there is any way you could include the stock Galaxy Nexus boot animation, that would be great, otherwise this rom is great!
thanks
Click to expand...
Click to collapse
NHLWil said:
Attached.
Higher definition versions here:
http://forum.xda-developers.com/showthread.php?t=1380655
Click to expand...
Click to collapse
Op updated with changes. Thanks.
Anthonok said:
This intrigues me. Might try it soon. I've wanted a 100% stock build and nobody had really made one. They all usually come with "tweaks and enhancements" pre installed.
Sent from my Galaxy Nexus using xda premium
Edit: flashed it so far so good but it thinks every word I type is wrong. As well as the IME switcher always being shown when typing and no other keyboards installed
Edit #2: saw a thread about a differnt rom needing specific gapps and without them it would do that gonna flash the ones from OP even though I have the 429 gapps already
Edit #3: thought that fixed it but it didn't. Maybe with a clean install with the gapps. I'll have to try in the morning.
Edit...again: more searching is bringing up that the ICS dictionary is missing or that there is a problem with the keyboard apk.
Click to expand...
Click to collapse
Weird. I didn't notice that because I use SwiftX. Thanks for pointing it out. I don't know that is yet.

Anthonok said:
This intrigues me. Might try it soon. I've wanted a 100% stock build and nobody had really made one. They all usually come with "tweaks and enhancements" pre installed.
Sent from my Galaxy Nexus using xda premium
Edit: flashed it so far so good but it thinks every word I type is wrong. As well as the IME switcher always being shown when typing and no other keyboards installed
Edit #2: saw a thread about a differnt rom needing specific gapps and without them it would do that gonna flash the ones from OP even though I have the 429 gapps already
Edit #3: thought that fixed it but it didn't. Maybe with a clean install with the gapps. I'll have to try in the morning.
Edit...again: more searching is bringing up that the ICS dictionary is missing or that there is a problem with the keyboard apk.
Click to expand...
Click to collapse
I'm not sure why the keyboard as compiled from source doesn't have the dictionary but I installed a different keyboard apk and the dictionary works. Weird.
Edit: I put the APK in OP

mmuzzy said:
I'm not sure why the keyboard as compiled from source doesn't have the dictionary but I installed a different keyboard apk and the dictionary works. Weird.
Edit: I put the APK in OP
Click to expand...
Click to collapse
Didn't work for me still showing everything as wrong. If I turn off auto correction in the keyboard settings and use SwiftKey it works fine. It'll have to do for now
Sent from my Full AOSP on Toro-VZW using xda premium

Anthonok said:
Didn't work for me still showing everything as wrong. If I turn off auto correction in the keyboard settings and use SwiftKey it works fine. It'll have to do for now
Sent from my Full AOSP on Toro-VZW using xda premium
Click to expand...
Click to collapse
That's strange. I had the Dictionary issue until I used this APK.
I navigated to where the APK was in ES Explorer, clicked it, it asked if I wanted to replace the system file and after that I had word suggestions as I type.

mmuzzy said:
That's strange. I had the Dictionary issue until I used this APK.
I navigated to where the APK was in ES Explorer, clicked it, it asked if I wanted to replace the system file and after that I had word suggestions as I type.
Click to expand...
Click to collapse
Exactly what i did. But still doesn't work with stock keyboard.
Sent from my Full AOSP on Toro-VZW using xda premium

Anthonok said:
Exactly what i did. But still doesn't work with stock keyboard.
Sent from my Full AOSP on Toro-VZW using xda premium
Click to expand...
Click to collapse
That is strange. I also notice that unlike what I had happening you actually have some words that aren't highlighted. So either you added them or maybe the language isn't set? In the Notification area does yours say "English (US)" in input method when the keyboard is up?

[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] Galaxy Tab Pro 10.1 4 apps in Multi Window

Hey, so is there any way to get the 4 Multi Window feature, instead of just the 2 Multi Window feature, on the Galaxy Tab Pro 10.1, just like the Galaxy Note Pro 12.2 has?

I was wondering the same thing. I wonder if it's a Note (S-Pen) exclusive, and therefore not available on the Samsung Galaxy Tab Pro 10.1?

quadview or 4 multiwindow apps simultaneously 8.4 & 10.1
EDIT: THIS HAS BEEN CONFIRMED WORKING BY @GreenMachine...SEE POST BELOW. ALSO...THE FIXED ZIP HAS BEEN ATTACHED TO THIS POST.
PaRaNoidNeM said:
Hey, so is there any way to get the 4 Multi Window feature, instead of just the 2 Multi Window feature, on the Galaxy Tab Pro 10.1, just like the Galaxy Note Pro 12.2 has?
Click to expand...
Click to collapse
senatemdm said:
I was wondering the same thing. I wonder if it's a Note (S-Pen) exclusive, and therefore not available on the Samsung Galaxy Tab Pro 10.1?
Click to expand...
Click to collapse
whats going on guys...i've ported the multiwindow mod to several other devices & just wanted to post the instructions to enable quad view for the tab pro models that shipped without it. If this does in fact enable the new option then feel free to donate a dollar to the multiwindow master himself @xperiacle since he is the one that made this discovery and has put in the most effort in making these mods work on devices that dont have them by default....i have linked to his paid app below which does the same thing as the zip (unfortunately i cant suggest purchasing it because i'm not sure whether or not it will work on the tab pros) but as for me a simple click on the thanks button will suffice
https://play.google.com/store/apps/details?id=mobi.xperiacle.multiwindowplus
^QUADVIEW APP BY @xperiacle (not sure if this will work...just wanted to give him credit)
INSTALL INSTRUCTIONS (U WILL NEED TO BE ROOTED & MANUALLY INSTALL)
1. unzip package
2. copy xml file in "system/etc/permissions" to the same location on your device then change the perms to 0644 (or rw-r--r--) then reboot.[/B]
(attention wifi only 10.1 users u MUST manually install...do NOT attempt to flash these as i believe the mount syntax is different for your device)
View attachment QuadViewPermissionsFile.zip
^QUAD VIEW PERMISSION FILE (this zip is NOT flashable..the perm file included will work with bith the 8.4 & 10.1 models)
EDIT: As an alternative...8.4 LTE owners (no wifi version yet) can just flash the custom rom i created which is available at the link below
http://forum.xda-developers.com/showthread.php?t=2752944
^ProPlusV1 THREAD (Custom rom for T320/T325/T525/T905)

THEDEVIOUS1 said:
whats going on guys...i've ported the multiwindow mod to several other devices and i just threw together a quick zip which SHOULD enable the quadview feature which allows us to use 4 apps in multiwindow at the same time. Please keep in mind that i do NOT have the device myself yet (plan on getting the LTE 8.4) so i will need someone to test and confirm that this does indeed work...dont worry about it harming your device as all the zip file does is add a few xmls to the "etc/permissions" folder. I also would like to add that if this does in fact enable the new option then feel free to donate a dollar to the multiwindow master himself @xperiacle since he is the one that made this discovery and has put in the most effort in making these mods work on devices that dont have them by default. i have linked to his paid app below which does the same thing as the zip but unfortunately i cant suggest purchasing it because i'm not sure whether or not it will work on the tab pros...as for me a simple click on the thanks button will suffice
https://play.google.com/store/apps/details?id=mobi.xperiacle.multiwindowplus
^QUADVIEW APP BY @xperiacle (not sure if this will work...just wanted to give him credit)
8.4 INSTALL INSTRUCTIONS (U WILL NEED TO HAVE A CUSTOM RECOVERY INSTALLED IN ORDER TO FLASH THIS FILE)
1. JUST BOOT INTO RECOVERY & FLASH...THATS IT!
10.1 INSTALL INSTRUCTIONS (U WILL NEED TO BE ROOTED & MAnUALLY INSTALL SINCE THERE IS NO RECOVERY AVAILABLE FOR YOU GUYS YET)
1. ROOT DEVICE
2. UNZIP PACKAGE
3. COPY XML FILES IN "SYSTEM/ETC/PERMISSIONS" TO SAME LOCATION ON YOUR DEVICE AND CHANGE PERMS TO 0644 (OR RW-R--R--) THEN REBOOT. U should actually only need to add 2 of the included xmls (maybe even 1) with the obvious one being "com.sec.feature.multiwindow.quadview.xml" and the other possible one being "com.sec.feature.multiwindow.xml" that has an identical name as a file already on your device but is actually different when opened which means it needs to be replaced (the copy included in the TEST1 zip is the NOTE 12.2 version which we know has working 4 way multiwindow while the copy in TEST 2 is the one that originally came on the 8.4)
(attention 10.1 users u MUST manually install...do NOT attempt to flash these as i believe the mount syntax is different for your device)
View attachment 2614869
^TEST1 (This 1 should work but if not then try TEST2)
View attachment 2614870
^TEST2 (Try this if TEST1 doesnt enable quadview)
If quadview works then can someone please post a few screen shots which i will use to make a proper thread...thx in advance. Also....please confirm that the create template function will now allow u to save a shortcut with 4 apps instead of 2
Click to expand...
Click to collapse
So... I got an error when I flashed it on my 8.4 (Test1) but, it still worked. The error I got was...
Mounting filesystems...
Extracting files...
Setting permissions...
set_perm: some changes failed
E:Error in /data/media/0/Download/TabProMultiwindowmodTest1.zip
(status 7)
Installation aborted.
Click to expand...
Click to collapse
Here are a few screenshots of it working. And yes, templates do work.
{
"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"
}
Sent from my SM-T320 using Tapatalk

GreenMachin3 said:
So... I got an error when I flashed it on my 8.4 (Test1) but, it still worked. Here are a few screenshots.
Sent from my SM-T320 using Tapatalk
Click to expand...
Click to collapse
AWESOME...can u please check the create option on the the multiwindow launcher and see if it will let u save a shortcut with 4 apps instead of 2 please

THEDEVIOUS1 said:
AWESOME...can u please check the create option on the the multiwindow launcher and see if it will let u save a shortcut with 4 apps instead of 2 please
Click to expand...
Click to collapse
I have edited my post with that info, yes the shortcuts do work for 4 apps
Thank you very much for doing this!

Code:
GreenMachin3 said:
I have edited my post with that info, yes the shortcuts do work for 4 apps
Thank you very much for doing this!
Click to expand...
Click to collapse
:highfive:
thanks for testing... i believe we actually only need one of the perms included but added all of the ones i've noticed missing from other devices just in case some other hidden feature may be available (there's a level 3 sensor xml that i found in a note 3 rom but i doubt that it does anything extra). Also...i found the source of the error which was just my sloppy editing of the updater-script.

THEDEVIOUS1 said:
Code:
:highfive:
thanks for testing... i believe we actually only need one of the perms included but added all of the ones i've noticed missing from other devices just in case some other hidden feature may be available (there's a level 3 sensor xml that i found in a note 3 rom but i doubt that it does anything extra). Also...i found the source of the error which was just my sloppy editing of the updater-script.
Click to expand...
Click to collapse
No problem, glad I was able to assist. Glad to hear that you were able to find the error.

How is the performance with 4 windows ? is it ok ?

Yogaxl said:
How is the performance with 4 windows ? is it ok ?
Click to expand...
Click to collapse
Yeah it runs really well. I don't understand why Samsung didn't give the option for 4 Windows to us 8.4 owners. Maybe they thought that the 8.4 screen wasn't logical for 4 windows.
Sent from my HTC One using Tapatalk

Thank you ! I was pretty upset when i discovered that there are not 4 windows just like the tab pro 12.2 .
OK a 8.4 " tablet may be too small but they could at least give the option for people , i don't get it too :/
I'll definitely flash it, my LTE version should arrive on monday !
What's the difference between TEST 1 and 2 ?

Yogaxl said:
Thank you ! I was pretty upset when i discovered that there are not 4 windows just like the tab pro 12.2 .
OK a 8.4 " tablet may be too small but they could at least give the option for people , i don't get it too :/
I'll definitely flash it, my LTE version should arrive on monday !
What's the difference between TEST 1 and 2 ?
Click to expand...
Click to collapse
both zips contained the same files including an xml labeled "com.sec.feature.multiwindow.xml" that has an identical name as one thats already on your device but is actually different when opened which means it MAY have needed to be replaced/renamed...the copy included in the TEST1 zip was the NOTE 12.2 version (also included in the V1) which we know has working 4 way multiwindow while the copy in TEST 2 is the one that originally came on the 8.4(Wont bother switching it back unless the other copy removes features or causes conflicts)
off-topic @Yogaxl
i know that the LTE version is SUPPOSED to do calls because it has the phone app & earpiece but i just want to know if u could please confirm when u receive your unit because I live in the usa where the 3g/4g versions usually have the voice function disabled & have to order from overseas so i would like to know for sure...thx in advance
GreenMachin3 said:
Yeah it runs really well. I don't understand why Samsung didn't give the option for 4 Windows to us 8.4 owners. Maybe they thought that the 8.4 screen wasn't logical for 4 windows.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
this is actually a question for anyone who can answer...is it true that samsung removed the icon to go from full screen to floating mode? i played with a demo unit and didnt see it...i was wondering if it was because there was no multiwindow manager app installed or what. Not sure if u guys are familiar with what i'm talking about but there used to be a black cascade icon in the lower right corner (which could be moved wherever u wanted it) that when pressed performs like the restore icon in windows (even looks similar)...if any of u guys owned any 4.1.2 samsung with multiwindows then u should be familiar with it especially if u had a tab plus or 7.7. Also...can someone that uses allshare cast/miracast/screen mirroring please tell me if multiwindow will work at the same time? This used to be a limitation of older versions so i would like to know if that has changed or will that need to be my next project...thx in advance

Change perms?
I am trying to get the 4 multi window feature to work on my Pro Tab 10.1. I copied the xml files to system/etc/permissions but I don't know what to do next. You said "copy xml files in "system/etc/permissions" to the same location on your device then change the perms to 0644 (or rw-r--r--) then reboot." What do you mean by change the perms to 0644? can you please explain how to do that? Thanks!
EDIT: So I figured out how to change the perms, so I changed them for all the xml files for the multiwindow feature. I rebooted my device and now it wont turn back on...PLEASE HELP?

Cheesefreak said:
I am trying to get the 4 multi window feature to work on my Pro Tab 10.1. I copied the xml files to system/etc/permissions but I don't know what to do next. You said "copy xml files in "system/etc/permissions" to the same location on your device then change the perms to 0644 (or rw-r--r--) then reboot." What do you mean by change the perms to 0644? can you please explain how to do that? Thanks!
EDIT: So I figured out how to change the perms, so I changed them for all the xml files for the multiwindow feature. I rebooted my device and now it wont turn back on...PLEASE HELP?
Click to expand...
Click to collapse
i apologize for any problems u may be having as i should have deleted the other zip i posted...the best way to get back going would be to flash TWRP through odin then use it's built in file manager to delete all of the permissions files u just added EXCEPT "com.sec.feature.multiwindow.quadview.xml" which is the only file u actually need. I believe the file thats keeping your device from booting is the "sensorhub_level3" file but delete all of the others just to be safe...once finished your device should boot and also have the 4 way multiwindow function from the 12.2 tabs. If u choose to or have already reflashed the stock firmware then just re-root and add ONLY the above mention "quadview.xml" with proper permissions & u should be good to go...sorry for the setback

THEDEVIOUS1 said:
i apologize for any problems u may be having as i should have deleted the other zip i posted...the best way to get back going would be to flash TWRP through odin then use it's built in file manager to delete all of the permissions files u just added EXCEPT "com.sec.feature.multiwindow.quadview.xml" which is the only file u actually need. I believe the file thats keeping your device from booting is the "sensorhub_level3" file but delete all of the others just to be safe...once finished your device should boot and also have the 4 way multiwindow function from the 12.2 tabs. If u choose to or have already reflashed the stock firmware then just re-root and add ONLY the above mention "quadview.xml" with proper permissions & u should be good to go...sorry for the setback
Click to expand...
Click to collapse
I went back to stock, I will re-root soon and try that. So, just to be clear, I only add the quadview.xml file with the correct perms for that one file? Nothing else in the download? Thanks for replying and helping, I will tell you if i get it working or not. Thanks!!!

Cheesefreak said:
I went back to stock, I will re-root soon and try that. So, just to be clear, I only add the quadview.xml file with the correct perms for that one file? Nothing else in the download? Thanks for replying and helping, I will tell you if i get it working or not. Thanks!!!
Click to expand...
Click to collapse
Yes...u only need the one file named quadview. The others were just a test from older versions of multiwindow to see IF they might add any extra features but not only did they not work they also cause the device to get stuck as u found out the hard way...no problem with the help since it was my fault in the first place

THEDEVIOUS1 said:
Yes...u only need the one file named quadview. The others were just a test from older versions of multiwindow to see IF they might add any extra features but not only did they not work they also cause the device to get stuck as u found out the hard way...no problem with the help since it was my fault in the first place
Click to expand...
Click to collapse
I just re-rooted and it works! Thanks so much!! This is awesome! :good: Do you know if there is a way that I can add any app I want to the multi-window feature?

Cheesefreak said:
I just re-rooted and it works! Thanks so much!! This is awesome! :good: Do you know if there is a way that I can add any app I want to the multi-window feature?
Click to expand...
Click to collapse
If u are familiar with xposed framework then just install the wanam module and there is an option in "system-select multiwindow apps" that will allow u to add any app...once u do this u will need to reboot then u will still need to add the apps to the multiwindow launcher by opening the multiwindow tab & pressing the 2 lines at the bottom then pressing "edit" & finally dragging the apps u just added from the left over to the launcher on the right. If u just want to download an app from the playstore that will allow u to add any then i suggest "muliwindow apps manager" which i will link to below but u will still need to reboot & add apps the same way i just described
https://play.google.com/store/apps/details?id=mobi.xperiacle.mwappsmanager
^MULTIWINDOW APPS MANAGER

[PORT] ANDROID L Preview for GEE

Here it is guys! Android L for all of us! We all need to thank @Kevinjoa for this wonderful port, because he's the dude who got it. Thanks!
Now for legal junk
Code:
Its your device
you choose what you do with it
if your phone explodes after flashing this, or melts, not our (or Kevins) fault. K?
Now for current bugs
Personally, I feel it can be used as a daily driver
Heat issue (Fixed soon no ETA's) ((Or run start Thermald in terminal emulator))
Charging slow issue (Will be fixed with Heat)
Service may take some tweaking to work on sprint (Flash Release3 first, add your carrier in carrier settings, then flash latest)
Random Device Update FC (rename /system/app/OmaDmclient.apk to OmaDmclient.apk.bak thanks @dwielunski)
No SD Card error (go to corresponding app in /sdcard/android/data and delete the folder)
NFC isnt working
Camera is a bit wonky
DOWNLOAD
DOWNLOAD L HERE
Please, before you report bootloop, give it at least 20 minutes to boot.
Enjoy!
Thanks to Google, Kevin, and whoever i forgot

Correct download link: https://s.basketbuild.com/devs/Kevinjoa/old/gee-l

ThatKawaiiGuy said:
Here it is guys! Android L for all of us! We all need to thank @Kevinjoa for this wonderful port, because he's the dude who got it. Thanks!
Service may take some tweaking to work on sprint (Flash Release3 first, add your carrier in carrier settings, then flash latest)
Random Device Update FC (rename /system/app/OmaDmclient.apk to OmaDmclient.apk.bak thanks @dwielunski)
Click to expand...
Click to collapse
OMG you guys figured that out! Amazing. I was wondering about the carrier part. I went from release two then clean flashed 8-11. Never tried any in between.
And @dwielunski seriously, tons of thanks for figuring out the update FCs. I tried renaming and deleting all kinds of apks and lines in some update xml's and whatnot. The fact that you figured that out and got them to stop is great. Thanks again to @dwielunski @ThatKawaiiGuy @Kevinjoa.
Has anyone else tried this?
itsdacj said:
I froze the nfcservice.apk with Titanium Backup and the nfcservice in battery awake time stopped going up ��
Click to expand...
Click to collapse
Seems like it would help.

I am very pleased to be rid of the update device FC! Also this may be my first actual meaningful contribution on xda so there's a milestone.
I saw the note about the NFC service. I don't use Titanium, but I downloaded an app from the Play Store called Disable Service and used that to disable "Nfc service". I assume it's the same thing? (Not entirely clear on what the issue is with NFC.)
For 3G data, I think have a more sensible fix that doesn't require flashing multiple versions of the ROM. If you are getting LTE but not 3G, you probably need to add "default" to the the plain vanilla Sprint APN. I will post a guide on how to do this with screenshots in a minute.

dwielunski said:
I am very pleased to be rid of the update device FC! Also this may be my first actual meaningful contribution on xda so there's a milestone.
I saw the note about the NFC service. I don't use Titanium, but I downloaded an app from the Play Store called Disable Service and used that to disable "Nfc service". I assume it's the same thing? (Not entirely clear on what the issue is with NFC.)
For 3G data, I think have a more sensible fix that doesn't require flashing multiple versions of the ROM. If you are getting LTE but not 3G, you probably need to add "default" to the the plain vanilla Sprint APN. I will post a guide on how to do this with screenshots in a minute.
Click to expand...
Click to collapse
I agree since when booting release 3 for the first time there is no mobile network because it tries for global. I have no type of service at boot and have a feeling that if I could get through setup it would say I have no prl, min, meid information listed. I saw this problem with release 2 but was able to get through setup using wifi. I cannot do that at work. Also, once past that part I still could get nothing for data. I seriously think it is due to having EvDo and not eHRPD in this area.
On the note of NFC, I am thinking it can be removed or renamed much like the oma file. I found nfcnci.apk and renamed it to bak, also there is an nfc_nci.mako.so file here \system\lib\hw so maybe that can be removed or edited even. I don't know how NFC polls things but maybe those files are useful. I don't think using an extra app is useful all the time.
I tried this again while at work but still had nothing at boot on rel3 it sets the network to sim mode or something.

All right. You only need one APN. (Others are for ota updates which we don't want, and separating eHRPD & LTE appears to create problems with handoff.) See screenshots for how it should look.
Now, to edit the APNs:
1) am start -n com.android.settings/com.android.settings.ApnSettings from terminal emulator; or
2) download an app from the play store like quickshortcutmaker or various APN editor apps (can't tell you which will work though).
We could make a flashable zip out of it, or build into the ROM. Until then, for those trying to activate the ROM over 3G, maybe use a tool like aromafm to edit/swap out the APN XML file after flashing but before first boot.
{
"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"
}

dwielunski said:
All right. You only need one APN. (Others are for ota updates which we don't want, and separating eHRPD & LTE appears to create problems with handoff.) See screenshots for how it should look.
Now, to edit the APNs:
1) am start -n com.android.settings/com.android.settings.ApnSettings from terminal emulator; or
2) download an app from the play store like quickshortcutmaker or various APN editor apps (can't tell you which will work though).
We could make a flashable zip out of it, or build into the ROM. Until then, for those trying to activate the ROM over 3G, maybe use a tool like aromafm to edit/swap out the APN XML file after flashing but before first boot.
Click to expand...
Click to collapse
Do you have or can you share the apn config file after you edited it? Keep in mind that if you give only one apn and it is for sprint then this is no longer a gee rom, that's why it shouldn't be included in the rom. Just my 2 cents. but if you can share the xml then us here in the sprint section can replace it before flashing.
Also, whatever you do, do not rename the nfcnci.apk because you will no longer have access to settings for the phone.
EDIT: However, your idea works. I am using 3G, I sent a pic and went on chrome with it. I have EvDo rev a not eHRPD and can confirm it works. You're on a roll today.

dopy25 said:
Do you have or can you share the apn config file after you edited it? Keep in mind that if you give only one apn and it is for sprint then this is no longer a gee rom, that's why it shouldn't be included in the rom. Just my 2 cents. but if you can share the xml then us here in the sprint section can replace it before flashing.
Also, whatever you do, do not rename the nfcnci.apk because you will no longer have access to settings for the phone.
EDIT: However, your idea works. I am using 3G, I sent a pic and went on chrome with it. I have EvDo rev a not eHRPD and can confirm it works. You're on a roll today.
Click to expand...
Click to collapse
Yes, it would be bad if we were deleting all the other carriers' APNs. But editing the APNs within system settings as I described does not alter or delete anything from the APN xml files in /system/etc/, it sits on top of those somehow. And also, though I didn't show this, the only APNs I am proposing to remove are unnecessary Sprint APNs (not other carriers). I am experimenting with editing apns-conf.xml in order to try to get it up and running from first boot and I will post the edited xml if it works.

dwielunski said:
Yes, it would be bad if we were deleting all the other carriers' APNs. But editing the APNs within system settings as I described does not alter or delete anything from the APN xml files in /system/etc/, it sits on top of those somehow. And also, though I didn't show this, the only APNs I am proposing to remove are unnecessary Sprint APNs (not other carriers). I am experimenting with editing apns-conf.xml in order to try to get it up and running from first boot and I will post the edited xml if it works.
Click to expand...
Click to collapse
I see. I thought you meant to place only one APN in the ROM file. But what I did was use APN manager and add the information you provided as a new APN. Thanks for the settings info BTW.
Does anybody know if "start thermald" in any spot of android terminal emulator is OK or do I need special permissions or to be in a certain folder. I typed that and pressed enter but nothing happened visually.

No luck on incorporating the APN into the XML file. Not sure what I'm doing wrong. Try again tomorrow.
On the bright side, I realized you can fire up the APN settings menu over ADB, so you can complete the setup without WiFi or LTE...if you have access to a computer with the Android SDK installed.

Is the included kernel the only one we can use? I can't live without s2w2 (my power button is almost unresponsive at this point....)

sorry for the question...how did you get working data and wifi? we are porting the L for htc one (here http://forum.xda-developers.com/htc...-android-l-developer-preview-htc-one-t2812816) but even if the libril-qc-qmi-1.so is working we have unknown baseband and so no sim reading...any help? ^^

Has anyone been able to set a text alert other than the default hangouts alert? I tried and when it is anything other than default I don't get anything. I tried a bunch. I even tried another sms app and tried disabling and enabling notifications but I still get no alert.
Here is what I tried:
1) changing default = no notification sound
2) using different SMS app, no changes to settings of hangouts = no notification sound
3) disabling notifications in hangouts and still using other app = no notification sound

dwielunski said:
No luck on incorporating the APN into the XML file. Not sure what I'm doing wrong. Try again tomorrow.
On the bright side, I realized you can fire up the APN settings menu over ADB, so you can complete the setup without WiFi or LTE...if you have access to a computer with the Android SDK installed.
Click to expand...
Click to collapse
I have tested with a lot of clean flashes and replacing apns-conf.xml before first boot and it is totally inconsistent as to whether I get data or not. Yesterday I got LTE on a clean flash of release11 with no changes, today I do not. So I am sticking with the manual edit of the APNs in system settings after boot as the recommendation to get data working.
Now, onto MMS. Anyone having success with MMS send or receive? If you do please post your APNs. Again, you can view these by running in terminal "am start -n com.android.settings/com.android.settings.ApnSettings". There are also APNs viewable within Hangouts that might help.

dwielunski said:
I have tested with a lot of clean flashes and replacing apns-conf.xml before first boot and it is totally inconsistent as to whether I get data or not. Yesterday I got LTE on a clean flash of release11 with no changes, today I do not. So I am sticking with the manual edit of the APNs in system settings after boot as the recommendation to get data working.
Now, onto MMS. Anyone having success with MMS send or receive? If you do please post your APNs. Again, you can view these by running in terminal "am start -n com.android.settings/com.android.settings.ApnSettings". There are also APNs viewable within Hangouts that might help.
Click to expand...
Click to collapse
I have sent a few using whatever is defaulted in hangouts and by adding the information you provided to my system and setting as default (active). But I used an apn manager to do it.
I haven't had anyone send ME an mms yet so I'm not sure. I will ask someone to and report back.

manups4e said:
sorry for the question...how did you get working data and wifi? we are porting the L for htc one (here http://forum.xda-developers.com/htc...-android-l-developer-preview-htc-one-t2812816) but even if the libril-qc-qmi-1.so is working we have unknown baseband and so no sim reading...any help? ^^
Click to expand...
Click to collapse
This device is literally the same as N4, so not as much work is needed to port things from them

fjsferreira said:
Is the included kernel the only one we can use? I can't live without s2w2 (my power button is almost unresponsive at this point....)
Click to expand...
Click to collapse
I'm not sure, I'd run L to test but it screws up my phone

I too can send MMS but cannot download when I receive it.
Sent from my Optimus G using XDA Premium 4 mobile app

Here's a screenshot of my APN through hangouts.
Sent from my Optimus G using XDA Premium 4 mobile app

PartimusPrime said:
I too can send MMS but cannot download when I receive it.
Sent from my Optimus G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Mine sits and then eventually fails. It took quite some time to even receive the message that there is one to download but once it got to my phone and I chose download it wouldn't.
I chalked it up to having bad reception, but now that I am not the only one it could be setting/rom related.
On another note, on release 3 I have a baseband, but when I flash 11 over it the baseband goes away and I get tons of FCs and the appearance of random UI restarts. It flashes and doesn't want to load the notification bar.

[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