[MOD][XPOSED] Downloads2SD - Xposed Framework Modules

{
"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"
}
Redirect several internal SD card locations to the external SD card.
This *only* works if the app uses Environment.getExternalStoragePublicDirectory(String), directly or indirectly, to get the location for the download. At present, it won't redirect app data (stuff in /data/data or /sdcard/Android), I may look into that later.
Apps this works with so far:
* /sdcard/Downloads - Chrome, Firefox (@an0n981, @zouhaier1).
* /sdcard/DCIM - Stock JB 4.2 Camera app.
* /sdcard/Pictures - Screenshot (@JamMasterClay).
[size=+3]Requirements[/size]
* [FRAMEWORK ONLY!] Xposed - ROM modding without modifying APKs
[size=+3]Screenshots[/size]
[size=+3]Caveats[/size]
* Due to weird security measures that make no sense, this won't always work on KitKat.
[size=+3]Downloads[/size]
* Source: https://github.com/egingell/Downloads2SD
[size=+2]Version name: 1.0.8[/size]
Download: com.egingell.downloads2sd_v9_acf08f.apk (267.61 KB)
MD5 checksum: acf08f0476e9d1df8997feee1cd12c32
Changes: Using logcat instead of Xposed to log info (logcat | grep "Downloads2SD").
[size=+2]Version name: 1.0.7[/size]
Download: com.egingell.downloads2sd_v8_dcd0c1.apk (267.42 KB)
MD5 checksum: dcd0c152bc1fbf66e14bf3c2422d101e
Changes: Per @rovo89 and @GermainZ in the Xposed Framework thread, I have switched my hook up slightly. It is unlikely that you, the user, will notice a difference.
[size=+2]Version name: 1.0.2[/size]
Download: com.egingell.downloads2sd_v3_77e3e4.apk (264.94 KB)
MD5 checksum: 77e3e49aa80c9ffe968b18141fb19b61
Changes: Added a check to ensure the new destination is viable (e.g. not an unmounted/removed SD card).
[size=+2]Version name: 1.0.1[/size]
Download: com.egingell.downloads2sd_v2_63f388.apk (264.71 KB)
MD5 checksum: 63f3887beb333dd2ea6dff4a4577dd87
Changes: Graphical bug. Reboots may or may not be required for changes, but it never hurts to just reboot anyway.
[size=+2]Version name: 1.0[/size]
Download: com.egingell.downloads2sd_v1_803aac.apk (264.74 KB)
MD5 checksum: 803aac515c56cecc9fc6a39177f1e167
Changes: Initial commit.

Confirmed working with Firefox on Omni 4.4.2

Oy. Seems there's a weird bug on my GS4. Works flawlessly on my GS2.
The bug: Repeated listings on the app UI which are confusing to the mod making it not redirect as it should.
Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9

Confirmed working with firefox on SM N9005 running x-note 10.0 leonardo edition. Thnx
sent from my rooted SM-N9005 running x-note 10.0 Leonardo Edition

Just want to report that everything seems to be work here on 4.4.2. So far I tested taking a picture with stock camera and taking a screenshot with the native Android function.
Thanks! :good:

It does not work with downloading a picture in an MMS in Verizon Messages. No surprise there...I absolutely despise that app. Unfortunately since KitKat there's no way to have my messages sync between devices and use a different SMS client. Using the Verizon sync service works better than any 3rd party solution because messages go to Verizon before coming to the phone anyways so often times I'll get a message on my tablet before my phone. 3rd party solutions have to read the SMS database, monitor it for changes, and then forward messages to a separate server. Luckily I hardly ever text people anymore anyways, but I digress.
/rant

JamMasterClay said:
It does not work with downloading a picture in an MMS in Verizon Messages. No surprise there...I absolutely despise that app. Unfortunately since KitKat there's no way to have my messages sync between devices and use a different SMS client. Using the Verizon sync service works better than any 3rd party solution because messages go to Verizon before coming to the phone anyways so often times I'll get a message on my tablet before my phone. 3rd party solutions have to read the SMS database, monitor it for changes, and then forward messages to a separate server. Luckily I hardly ever text people anymore anyways, but I digress.
/rant
Click to expand...
Click to collapse
Does the Xposed log show "DOWNLOADS_PICTURES [OLD] => [NEW]", "DOWNLOADS_PICTURES [OLD] => null", or nothing?
Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9

egingell said:
Does the Xposed log show "DOWNLOADS_PICTURES [OLD] => [NEW]", "DOWNLOADS_PICTURES [OLD] => null", or nothing?
Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
Click to expand...
Click to collapse
Not a thing, sir.

Bummer.
Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9

I hope that can be connected to a Bluetooth folder on the external SD card on the next update.

JazzBlueWong said:
I hope that can be connected to a Bluetooth folder on the external SD card on the next update.
Click to expand...
Click to collapse
Eventually. I just need to figure out where Android gets the arbitrary folder name from. Hint: It's not the same place as the ones in this mod.
Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9

@egingell
When I tap 'Direct Download' here: http://forum.xda-developers.com/devdb/project/dl/?id=4318 using Chrome Beta the browser force closes. I've attached a screenshot of the stack trace occurring with no other modules enabled. I did the same test on both my Note 10.1 and S4 both running OmniROM 4.4.2 with the same behavior on both. Downloading other things works fine, for example long-pressing to download a image.
-Sent from My Galaxy Note 10.1 using Tapatalk

JamMasterClay said:
@egingell
When I tap 'Direct Download' here: http://forum.xda-developers.com/devdb/project/dl/?id=4318 using Chrome Beta the browser force closes. I've attached a screenshot of the stack trace occurring with no other modules enabled. I did the same test on both my Note 10.1 and S4 both running OmniROM 4.4.2 with the same behavior on both. Downloading other things works fine, for example long-pressing to download a image.
-Sent from My Galaxy Note 10.1 using Tapatalk
Click to expand...
Click to collapse
Works fine for me, but I'm not using Kit Kat. Even when testing and making other apps crash, I still got my file names and Xposed file names with line numbers in the logcat, so I can't even trap the exception let alone fix it since neither are present in that error log.
Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9

egingell said:
Works fine for me, but I'm not using Kit Kat. Even when testing and making other apps crash, I still got my file names and Xposed file names with line numbers in the logcat, so I can't even trap the exception let alone fix it since neither are present in that error log.
Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
Click to expand...
Click to collapse
I hoped it wouldn't be so involved to track down. Xposed log and logcat attached.
EDIT: It's late...forgot to mention Chrome Beta version 33.0.1750.126.

JamMasterClay said:
I hoped it wouldn't be so involved to track down. Xposed log and logcat attached.
EDIT: It's late...forgot to mention Chrome Beta version 33.0.1750.126.
Click to expand...
Click to collapse
I'm afraid I still don't see a viable error message, but I will give it a better look in the morning... and I successfully downloaded the file using Chrome Beta.
Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9

JamMasterClay said:
@egingell
When I tap 'Direct Download' here: http://forum.xda-developers.com/devdb/project/dl/?id=4318 using Chrome Beta the browser force closes. I've attached a screenshot of the stack trace occurring with no other modules enabled. I did the same test on both my Note 10.1 and S4 both running OmniROM 4.4.2 with the same behavior on both. Downloading other things works fine, for example long-pressing to download a image.
Click to expand...
Click to collapse
JamMasterClay said:
I hoped it wouldn't be so involved to track down. Xposed log and logcat attached.
EDIT: It's late...forgot to mention Chrome Beta version 33.0.1750.126.
Click to expand...
Click to collapse
I managed to get Chrome Beta to crash on my GS2, but for a different reason which I fixed and added an untested fix fr your problem. If you'd like to test it:
[size=+1]Version name: 1.0.3[/size]
Branch: beta
Download: com.egingell.downloads2sd_v4_eb5301.apk (265.48 KB)
MD5 checksum: eb5301465e38f0f7df46b2f24d0dec2c
Changes: Removing Security exception ensuring that the file goes to the "external" storage.

egingell said:
I managed to get Chrome Beta to crash on my GS2, but for a different reason which I fixed and added an untested fix fr your problem. If you'd like to test it:
[size=+1]Version name: 1.0.3[/size]
Branch: beta
Download: com.egingell.downloads2sd_v4_eb5301.apk (265.48 KB)
MD5 checksum: eb5301465e38f0f7df46b2f24d0dec2c
Changes: Removing Security exception ensuring that the file goes to the "external" storage.
Click to expand...
Click to collapse
Well, I'm no longer getting a FC. But the download consistently fails before actually starting (i.e. it never gets to showing the download percentage) I've tried multiple times on WiFi (literally sitting next to the router) and on 4G LTE. With the module enabled download fails, without it succeeds. FWIW, in the downloads app where the filename should be is black, and it says unsuccessful below that.
If you feel like continuing to look into this I've attached a new Xposed log and logcat.

JamMasterClay said:
Well, I'm no longer getting a FC. But the download consistently fails before actually starting (i.e. it never gets to showing the download percentage) I've tried multiple times on WiFi (literally sitting next to the router) and on 4G LTE. With the module enabled download fails, without it succeeds. FWIW, in the downloads app where the filename should be is black, and it says unsuccessful below that.
If you feel like continuing to look into this I've attached a new Xposed log and logcat.
Click to expand...
Click to collapse
I had a feeling it would do that. I'm bypassing that particular exception, but whatever is triggering it is still there. Does Chrome Stable have the same problem? Doesn't much matter, though. I don't think I can do anything about it.
Is purposely thrown and it doesn't make much sense why, but I digress.
Edit: Those error messages are even less useful.
Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9

egingell said:
I had a feeling it would do that. I'm bypassing that particular exception, but whatever is triggering it is still there. Does Chrome Stable have the same problem? Doesn't much matter, though. I don't think I can do anything about it.
Is purposely thrown and it doesn't make much sense why, but I digress.
Edit: Those error messages are even less useful.
Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
Click to expand...
Click to collapse
Yup, same behavior with the non-beta version of Chrome.

Just wanted to post that I'm having that same error when trying to download files from Goo.im, Android File Host, and Dev-Host as well. For now I simply changed the Downloads location back to the built-in storage location and everything's working fine. Not a big deal to me, but I just wanted to give you a heads up in case a lot more people on KitKat start using this.

Related

[KOT49H] Synman's GwT ROM for DEB

[KOT49H] Synman's GwT ROM for DEB
GwT is an experimental AOSP build for the N73G and N7LTE Nexus tablets for those wanting to stay as close to the intended Google Experience as possible.  SMS and MMS are fully functional as is tethering.  This ROM is slim with no bloat or non experience apps loaded and should serve well as a daily driver or as a base ROM for theming / framework hacks when the modder doesn't want to go through the trouble to create their own full build.
As with all things XDA, proceed at your own RISK.  
FEATURES / HIGHLIGHTS
Pure AOSP (built from source) 4.4 [aosp_deb-user KOT49H]
Dual Pane Preferences (including System Preferences)
Reboot and Reboot Recovery options added to shutdown menu
Bundled with Launcher2 (survives GAPPs install)
Native dialer is exposed, but GSM voice capability still not possible  
Orientation Sensor supported Dialer (not yet)
Tethering & Hotspot is enabled
Full APN list
Full SMS and MMS Send & Receive
APN Settings Editor Preference no longer a dialog (exposed actions)
Phone Settings (and its children) no longer dialogs (fixes SIP Providers Editor)
Rock Solid ROM - As stable as stock
/system/bin/mountrw.sh for ease of rw mounting
No SimpleSmsReceiver
Sun Beam Live Wallpaper included (NOT IN KOT49H)
Updated boot animation
CRT screen off animation
What's Broke:
GSM Voice Communication (SIP works fine)
Occasional crash switching orientation from sleep
SCREENSHOTS
{
"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"
}
​
Install Instructions (assumes already unlocked):
It is highly recommended that you start with a full wipe from a known good installation of the N7LTE stock binaries.  
If you don't know how to get to this initial state or how to proceed on your own bypassing this step then you have no business installing this ROM.
As of KRT16O GwT is installed via recovery. RC1 (based on the original Nexus 5 source) requires fastboot.
KOT49H Installation Instructions
Flash Google's Factory Image for KOT49H to your device and perform at least one full boot. This is the recommended baseline for KOT49H and ensures you have the most recent boot loader, kernel, and modem firmware installed.
Install the latest DEB version of TWRP or Clockwork Recovery and boot your tablet into it.
Download the GwT KOT49H zip file to your PC and copy it to your tablet's sd card.
Via recovery perform an install of the GwT KOT49H zip update.
Perform a factory reset of your tablet in Recovery.
Perform at least one full boot.
Optionally, Install GAPPs (a PA link is provided below) and once again perform a factory reset of your tablet in Recovery.
Optionally, root your tablet using the link provided below.
RC1 Installation Instructions
Download the GwT zip file and unzip it on your PC. Reboot your N7LTE into bootloader mode and from the directory where you unzipped the GwT archive to execute the following commands:
Code:
Shells-Retina-MBP:GwT shell$ [B]export ANDROID_PRODUCT_OUT=./[/B]
Shells-Retina-MBP:GwT shell$ [B]fastboot -w flashall[/B]
Once the install is complete if unsure of next steps or problems occur perform a Factory Reset of your N73G.  
Reboot and allow GwT to fully boot.
Optionally, install the recommended Google Apps package referenced below.
ROM DOWNLOADS
GwT KOT49H - ACTIVE
XDA Direct Link Synman_GwT-DEB-KOT49H.zip
GwT KRT16O - OBSOLETE
XDA Direct Link Synman_GwT-DEB-KRT16O.zip
RC1 (KRT16M) - OBSOLETE
XDA Direct Link Synman_GwT_for_DEB-RC1.zip
GAPPs DOWNLOADS
PA-GOOGLE APPS
craigacgomez's ThunderKat Google Apps Pack
ROOT DOWNLOADS
Root / SuperSU (http://forum.xda-developers.com/showthread.php?t=1538053)
SuperSU 1.51
Release Notes
GwT KOT49H
Forward ported all KRT16O optimizations
Fixed Home Systems Settings fragment
GwT KRT16O
Forward ported BT phantom dial bug fix -- yup it found its way into DEB and Kit Kat (thanks Google)
Found DEB's camera.
If you're unhappy with the Experience Launcher, AOSP Launcher2 will survive a GAPPs install if you want to revert to it
Dual Pane Preferences, including System Preferences
Advanced Power Menu (Reboot / Reboot Recovery)
DEB RC1
Forward ported BT phantom dial bug fix -- yup it found its way into DEB and Kit Kat (thanks Google)
If you know where Camera is please let me know
You'll very likely want to copy Launcher2 from /system/priv-app back into /system/app after installing GAPPS. Google's Experience Launcher is not quite ready for primetime on our tablet yet.
Packaged with TWRP 2.6.3.0 instead of the stock recovery... please thank the TWRP guys for all their hard work.
GwT Source Repository
https://github.com/synman/synman_aosp_tilapia
.
XDA:DevDB Information
Synman's Grouper with Tilapia (GwT) ROM, a ROM for the Nexus 7 (2013)
Contributors
Synman
ROM OS Version: 4.4.x KitKat
ROM Firmware Required: Start from Nexus Factory Image KOT49H
Based On: AOSP
Version Information
Status: Testing
Created 2013-11-07
Last Updated 2013-12-23
This looks Great! Downloading now! Many thanks!
Edit: never mind, I figured it out
One question, is there going to be any issue for going back to stock?
Hint to flashers: userdata.img is going to erase all your internal memory.
The dialer is just so great, I can run USSD codes, and that's perfect! How did you get it to work? Is there the possibility of voice calls too in the future?
There are no issues going back to stock. I have tested this path forward and backward a couple times now with zero issues.
The above instructions (in their current form) require a FULL WIPE. I recommend this approach so as not to have to fall into the pit of this didn't work and that didn't work, etc, etc when folks get creative in the way they try to install the ROM.
You can certainly veer from this course, and I'm certain a few will with great success.
Voice calls will work awesome so long as you configure a SIP provider.
I have also posted the AOSP Launcher2.apk in the downloads area as it appears the PA GAPPS installer is wiping it out completely. If you want to get back to the stock launcher, simply drop Launcher2.apk back into /system/app and reboot. Post lock screen you will be prompted for which Launcher to use.
Hey syn, I remember you digging into the nexus7 first gen for gsm calls as well (thanks) is it looking like it's blockered by goog again on second gen as well?!?
Sent from my HTC One using xda app-developers app
Yup... Very similar observations thus far.
Sent from my Galaxy Nexus using Tapatalk
Fantastic job, thanks a lot!
Google be damned for the voice calls though
Sent from my GT-P6800 using xda app-developers app
Very interresting project. If also the factory image & binaries are for deb avaialbe and you may update your current ROM I will test this ROM. Looks very promising.
Why we need to use these commands
Code:
Shells-Retina-MBP:GwT shell$ export ANDROID_PRODUCT_OUT=./
Shells-Retina-MBP:GwT shell$ fastboot -w flashall
to install the ROM. Why not a zip fo a recovery. What is the idea behind this process?
Also I can only install GApps AFTER the ROM boot up after installen. Not directly after the ROM flash?
...
Synman said:
The above instructions (in their current form) require a FULL WIPE. I recommend this approach so as not to have to fall into the pit of this didn't work and that didn't work, etc, etc when folks get creative in the way they try to install the ROM.
You can certainly veer from this course, and I'm certain a few will with great success..
Click to expand...
Click to collapse
Any news for the camera? Is it possible to port the drivers and libraries from official 4.4 Flo roms?
Gesendet von meinem Nexus 4 mit Tapatalk
Yeah, it is very doable using the flo sources but I'll likely wait for official deb to cut down on rework. My schedule is pretty booked.
Sent from my Nexus 5 using Tapatalk
Phone settings and it's children?? I've got a couple of questions if you don't mind.
This seems like an amazing ROM. I was looking at your thread for the original N7. I understand that GSM in not enabled, that is fine. But my question pertains to having the phone features enabled on this ROM. I am wanting to use my N7LTE as a primary device, I see that SIP is supported. This is great. However, what I am wanting to know is, does this dialer enabled ROM with the phone settings included, allow other devices to see this as a phone? My reason for asking is this. I have my tablet installed into the dash of my car. Bluetooth headsets can see the tablet having both Phone and Media tickboxes for connection over bluetooth. My car stereo, however seems to only recognize the tablet for Media audio. My current setup is stock KitKat, non-rooted. For activities like Play Music, only Media audio is ok, but for SIP or say Hangouts audio, I cannot get that to stream to the car stereo. My HTC One has the ability to do it all, therefore, I am wondering if it comes down to device profile and/or dialer and phone setting functions that are preventing me from achieving this.
Any help would be awesome. My dream is to do SIP (or Hangouts) calling over data, and stream EVERYTHING over bluetooth with no restrictions, one device to rule them all, out and about, in the car, at work, or simply on the couch.
Thanks again, your work is greatly appreciated.
Synman said:
GwT is an experimental AOSP build for the N73G and N7LTE Nexus tablets for those wanting to stay as close to the intended Google Experience as possible. *SMS and MMS are fully functional as is tethering. *This ROM is slim with no bloat or non experience apps loaded and should serve well as a daily driver or as a base ROM for theming / framework hacks when the modder doesn't want to go through the trouble to create their own full build.
Click to expand...
Click to collapse
SMS/MMS related question, since you seem to be the only one with it working in a KitKat ROM.
Do you have any idea how one might go about enabling this feature in the official 4.4 build? There seems to be a limitation in the stock telephony apk that prevents the option to set a default client form being exposed. Do you think replacing the telephony apk/odex from stock with the one from your rom here would be sufficient or would additional modifications be required?
If you mean SMS function, this is working fine on stock rom. Only need is installing a SMS app like 8sms ( www.8s.ms)
I've used a BT headset successfully with SIP calls. It presents both the phone and media profiles to connecting devices but can be a little buggy. There is very likely additional mapping opportunities... I simply haven't covered all scenarios yet with the LTE version.
Regarding framework jars its a bit bigger than just telephony but you are on the right track. There is also a BT connect bug that you'd need to hack via smali or is it smil? Far too many techs and acronyms floating around in my brain. Your approach is where I started last year and once I got an idea of the extent of it it was a lot easier to just build my own ROM .
Sent from my Nexus 5 using Tapatalk
User_99 said:
If you mean SMS function, this is working fine on stock rom. Only need is installing a SMS app like 8sms ( www.8s.ms)
Click to expand...
Click to collapse
No, no it doesn't not on the official google build. The option to set an app as the default SMS app is missing, and this results in 8SMS being "disabled".
Thanks for the reply. I guess my question is really this... With the native dialer (phone.apk and it's settings exposed) does this allow the Bluetooth stack in the Rom to enable the hands free profile (HPF) contained in the current Android version? I have researched that this function is tied to the dialer and it's presence. That is why tablets so far cannot enable audio for calling functions. If it does, my problems are solved, as well as many others installing in their cars. If not, would it be possible to do, and would you have any interest in trying to enable it? I truly think this is as best as we will get for in car calling over sip/data using a car stereo to stream and/or even sip/data calls using a regular headset if need be.
Thanks again for responding.
Sent from my Nexus 7 using xda app-developers app
All I can tell you is to try it. My N7LTE replaced my N73G in my car but I spend very little time trying to actually use it as a sip phone because my actual phone is usually easier to reach than the tablet.
I use mms/SMS quite a bit (my wife has gotten into the habit of texting my car to ascertain my whereabouts) and the hands free profile works perfectly with my grom.
If you come across any bugs or limitations I'll be more than happy to research, and very likely address, them like I did on GwT for the original N73G.
I have just enough time to make the framework changes and run the builds.... It is your job to test and provide feedback
Sent from my Nexus 5 using Tapatalk
I'm downloading 4.4_r1.1 now ... will likely have a new release out by the end of the weekend. I'm very curious to see how Launcher3 (Google Experience Launcher) is behaving in our "official" release.

[ROM-ADDON] Minin3; project MENDIOSUS v1.0 (aosp cm11) (1/14/14)

{
"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"
}
MININ3
(OPERATION MENDIOSUS)
{RELEASE 1.0 ALPHA TEST}
(I know this seems like a lot to read through but I highly recommend it)
SEE POST #2 FOR DOWNLOAD LINKS
SEE POST #3 FOR INSTALL INSTRUCTIONS
SEE POST #4 FOR CONTRIBUTOR AND TEST GROUP INFO
PLEASE BE AWARE-- THIS ROM IS NOT BASED ON OFFICIAL SAMSUNG FILES, IT IS BASED ON A RUNNING CM11 CYANOGENMOD SYSTEM.
AND WHILE THIS IS VERY GOOD, CM11 IS NOT 100% READY FOR OUR DEVICES, ALSO ANY SAMSUNG SPECIFIC FEATURES (MULTIWINDOW, PEN WINDOW, SHEALTH, ect) WILL NOT WORK (THOUGH I WILL ATTEMPT TO INCLUDE ALTERNATES), AND WHILE IT IS PRETTY STABLE, AT THIS TIME THERE WILL BE SOME MINOR BUGS. AS CM11 CHANGES THOSE WILL BE REDUCED. IF YOU NEED ABSOLUTE STABILITY AND EXCELLENT BATTERY LIFE PLEASE USE A TOUCHWIZ ROM BASED ON THE OFFICIAL mj4 UPDATE>
for a slightly better look at what touchwiz is vs what cm11 (aosp) is check out a few of these links.
http://forum.xda-developers.com/showpost.php?p=48773400&postcount=2
http://www.androidauthority.com/touchwiz-better-than-stock-android-215634/
I AM NOT TRYING TO SAY cm11 ISNT VERY GOOD. I LIKE IT QUITE A BIT.
or i wouldnt have gone through the effort of making this.
just that touchwiz is more than the launcher it is actually a whole set of files built directly into the system specifically designed for our devices.
MANY of the apps that come stock on the note 3 rely on these files to function.
and no its not as easy as just copying them over to cm11 based roms.
CM11 is more of a vanilla android experience (with some mods)
PLEASE READ POST #3 CAREFULLY.
THE INSTALL PROCEDURE FOR THIS ROM MAY BE A BIT DIFFERENT THEN WHAT YOU'RE USED TO.
MY TOUCHWIZ BASED ROMS
**BE SURE TO CHECK OUT MININ3.MINIMUS FOR A FULLY DEBLOATED, MORE STOCK EXPERIENCE**
**BE SURE TO CHECK OUT MININ3.MAXIMUS FOR A TOUCHWIZ BASED EXTREMELY STABLE CUSTOM EXPERIENCE**
update images under screenshots above.
PREVIEW VIDEO
-On top of the excellent features offered in CM11
INCLUDES:
-WANAM XPOSED FRAMEWORK INSTALLED
Special thanks @rovo89 for developing this spectacular framework.
FROM THE PLAY STORE:
-Halo windows
-Pie controls
-Hide apps
-boot manager
-XPOSED KIT
-xbmc
-texdroider dpi
SETTINGS PRE-SET AND MODS.
-battery around swipe to unlock
-clock centered
-network speed indicator (can turn off)
-swipe from left side for back
-pie controls on right by default (set in dropdown)
-quick icons in notification dropdown
-battery landscape with percent
-multi reboot menu enabled
-screenshot/ screen record on shutdown menu
-disable mobile data / airplane mode on power menu
-auto close notification if dismissing all notifications.
-auto close quicksettings on pick
-easily change dpi
-hold unlock on lockscreen for flashlight
-hold volume up on lockscreen for flashlight
-quick panel setup
-multiple settings pre set
-included themes for (stock,blackout,Touchwiz style)
-multiple launchers (launcher is google experience launcher with working hi galaxy on desktop)
-multiple keyboards (stock google)
- minor stability and speed tweaks
this is version 1 and is an alpha / test build (though so far has been very stable for me)
​
XDA:DevDB Information
MENDIOSUS, a ROM for the Sprint Samsung Galaxy Note 3
Contributors
mjcollum
ROM OS Version: 4.4.x KitKat
Based On: Cyanogenmod , AOSP
Version Information
Status: Testing
Current Beta Version: 1.0
Beta Release Date: 2014-01-14
Created 2014-01-15
Last Updated 2014-01-15
NO KERNEL INCLUDED>
MUST INSTALL OVER A CM11 BASED BUILD
which will have the kernel and a full system this rom only changes and adds features for cm11 builds
STEP ONE:
install a cm11 build tested over this one here...
thank @noobnl for his hard work bringing us a working cm
http://forum.xda-developers.com/showthread.php?t=2599669
i used:NEW NEW NEW BUILD from that thread.
there is now an official build page for the note 3 cm builds here.
latest official builds can be found here
http://download.cyanogenmod.org/?device=hltespr
Reports are it also works very well with VANIR based roms
http://www.emccann.net/nuclearmistake/VanirAOSPNightlies/hltespr/
STEP TWO GET THIS FILE:
DOWNLOAD
VERSION 1.0 ALPHA SOME MINOR BUGS (CM11 is not 100% yet)
(if downloading from phone gives a bin file download with a pc, should be.zip)
INCLUDES ALL NECESSARY GAPPS AND OTHER NEEDED FILES!
Built on top of cm11 for multiple reasons, (my upload bandwith is horrible right now, cm11 is getting constant updates, this will make things easier on me at least until everything gets worked out) (should also work UNTESTED on other cm11 builds/roms for the sprint note 3)
Install instructions
FOR THIS VERSION AT THE MOMENT CWM RECOVERY IS NOT SUPPORTED
cwm lacks the fix permissions script needed to ensure certain data settings remain intact
future versions will improve on this, however for now use TWRP
Install notes for test version 1 (this will change dramatically with upcomming versions)
FIRST (ESPECIALLY IF COMING FROM 4.3)
wipe everything in recovery except internal and external sd
(wipe>advanced)
reboot into recovery (IMPORTANT)
then install from there.
install cm11 first
boot to system
This is an update add on to cm11 based roms
flash update reboot (to write data to system)
flash update again, fix permissions, (edits data after a boot)
reboot
(i have been working on a much improved install procedure that should ensure a one step install,
the reason for editing data is to pre-set some app settings
without having to edit individual apk files, this increases
compatibility and ensures things still work as intended as apps get updated)
open pie control give admin
open wanam press update install (to force admin)
will need to open a few other apps also will list as found
future versions should take care of this automagically.
can use hide apps to hide unwanted apps from the launcher (this will also be preset in the future)
i usually use it to hide all the wanam modules and not the xposed installer.
then use xposed installer , modules to edit settings as needed.
also can hide anything else you want to leave installed but not see.
these apps may need root enabled (just open and try and change something) should prompt..
Xposed installer
Pie control
startup manager (if wanted)
texdroider dpi (if wanted)
file manager
xhalo floating windows (wanam module)
app hider (to hide apps optional)
also there are some included themes under the settings menu themes.
ignore the warning and just press apply, (stock cm11, blackout, twstyle)
may also want to uncheck and recheck all the wanam modules and reboot after to be sure they all actually get set.
ADVANCED USERS/USERS WANTING TO USE THIS ON TOP OF ANOTHER CM11 BUILD
STILL READ ABOVE NOTES>
Dirty flash on top of any running cm11 system should be fine (unconfirmed)
NOT WIPING DATA SHOULD BE FINE ALSO IF YOU ARE ALREADY ON A 4.4 BUILD.
DO THIS:
flash update reboot (to write data to system)
flash update again, fix permissions, (edits data after a boot)
reboot
If you like my work please consider buying me a beer by clicking the "DONATE" link below:
Please be sure to include your xda username if you make a donation so that we are able to add you to the contributor list.
***DONATE***
Special Thanks To the Contributers who help justify the time spent doing all of this to the girlfriend:
MiniN3 Day One Contributor List:
@micmars @spyke24 @neonflx @Tabs2006 @stashu11 @seVIIn7 @tgrrb5 @alexv59 @TrofeoSC @rslawson @duytienle @jconway1968 @quantumtransfer @lopies @ktron2g @lsvtec4dr @kingfisher @sgthwjack @syoumans54 @zdragon @mhutton @oxmis @Poetik @WeSiDe @geno_1 @TeCKNeiC @tdmodcon @milton007 @jdebutts @aglreg @nolimit06 @nayers1981 @Kompster
MiniN3;MENDIOSUS Contributor List:
---------------------------------------------------------------------
If you'd like another way to support the MiniN3;MENDIOSUS project, you can also use the code below in your signature: (remove the spaces)
[ URL ="http://forum.xda-developers.com/showthread.php?t=2519647"][ img ]http://i1294.photobucket.com/albums/b611/nala_/Development%20images/MiniN3LensflareSupporterSignature3_zpsbbae38f2.png[/ img ][/ URL ]
---------------------------------------------------------------------
MiniN3 Wallpaper:
https://files.secureserver.net/0sc5ISkYUedvIU
MiniN3 Lockscreen:
https://files.secureserver.net/0sEzRnjWAvSne2
---------------------------------------------------------------------​
You're a beast.
Sent from my calculator watch.
Awesome juice!
Sent from my SM-N900P using XDA Premium 4 mobile app
no problems, getting everything uploaded now...
should be just a little bit yet.
Been looking forward to this one.
Sent from my SM-N900P using Xparent Skyblue Tapatalk 2
Would we be able to downgrade back to 4.3 without any issues or do we need to do something special in order to do that?
You're on fire MJ
Sent from my SM-N900P using Xparent Green Tapatalk 2
Can't wait for this!
..
dam90042 said:
Would we be able to downgrade back to 4.3 without any issues or do we need to do something special in order to do that?
You're on fire MJ
Sent from my SM-N900P using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
I have had no issues going back to 4.3
both by install of a mj4 rom or by recovering a backup,
though i do recommend ..
wipe everything but internal and external sd
reboot recovery
then install whatever you want from there.
upload almost done...
everyone who posts in this thread by the time it finishes will get a test link by pm
everyone on the minin3 project test group will also get an email.
once some confirmation of no horrible issues will also post public download
file done pms and emails coming
So no need for a restore sd card zip? I wanna try some aosp just don't wanna look in twrp and see nothing in my restore folder lol
Sent from my SM-N900P using XDA Premium 4 mobile app
xyojimbox said:
So no need for a restore sd card zip? I wanna try some aosp just don't wanna look in twrp and see nothing in my restore folder lol
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i have had no issues at all restoring.
though every timebefore i even try i am sure to wipe everything but internal and externall sd and reboot back into recovery
from there i have restored from both with no problem
Oh hell yes. AOSP goodness!
Sent from my SM-N900P using XDA Premium 4 mobile app
Of course this would have to be out during rush hour traffic here in California haha
Thanks MJ
Sent from my SM-N900P using Xparent Green Tapatalk 2
oh hell yeah!!
mjcollum said:
i have had no issues at all restoring.
though every timebefore i even try i am sure to wipe everything but internal and externall sd and reboot back into recovery
from there i have restored from both with no problem
Click to expand...
Click to collapse
Oh ok cool. I always wipe before restoring no matter what
Sent from my SM-N900P using XDA Premium 4 mobile app

[XPOSED][GB*][ICS*][JB][KK*] UnToaster Xposed

{
"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"
}
[size=+3]What is it?[/size]
Devs these days think they need a toast for every little thing. I won't name names or apps, but you know what they are. Well, this module will block those pesky toasts with patterns or strings (escape all .?^&$*-()[]{} with \). See http://developer.android.com/reference/java/util/regex/Pattern.html
[size=+3]Requirements![/size]
* [size=+1]Xposed![/size] Get it here (Xposed repository) or here (XDA thread) and post any Xposed related issues in its thread.
* Your Android smart device. UnToaster should* support Gingerbread and up (the OSs that Xposed supports).
[size=+3]Things to Note[/size]
* I can't guarantee the functionality if this mood if you have another that also hooks into the Toast class. That said, this works with the latest Burnt Toast (1.0) and Buttered Toast (1.1).
* I'm too lazy, and there's not much room for it anyway, to add a Copy button. This can be achieved by clicking the package name you want to copy, change the package name, and click Save. The original file will be preserved and a new file added.
* Renaming is the same plus click the old one and click Delete.
* If you have a bug, give me the error.log from Xposed and a logcat *in this thread* - PM logs will be missed or ignored.
Code:
tail -n 100 /data/data/de.robv.android.xposed.installer/log/error.log >/sdcard/UnToaster.log;
logcat -d | egrep "System\.err|UnToaster" >>/sdcard/UnToaster.log;
** I get very temperamental about this. I will not accept any bug report that just says that it's broken unless it contains the log.
** I'm not flashing a ROM or buy a phone just to debug your problem and I only have an SGS2 and an SGS4.
* If you have a suggestion, post it. I will entertain just about any suggestion so long as it's feasible, practical, and within the scope of this mod.
* Donations are accepted, but are neither required nor expected and currently, there are no perks for donating. Any donations will be logged. And should I add any perks, they will be retroactive.
* If you would like it translated, translate it. You can get the strings.xml file from GitHub, but there's not much there to translate.
[size=+3]Examples[/size]
* (-v1.2.6) To get the package name, you can look in the Xposed log after you see the toast.
* (+v1.2.6) To get the package name, you can look in the logcat after you see the toast. Command line: logcat | grep "I/UnToaster"
* A blank pattern box is the same as ".*".
* (+v1.1.2) Using "all" as a package name will allow you to block the same pattern from all apps. Even newly installed ones. In 1.1.5 and up, you must put something in "all" or it won't get processed.
Code:
Connected to Wi-Fi.*
.*successful
.*loaded.*
Can\'t find phone number [\d]{7,11}
Can\'t find phone number 1{0,1} \([\d]{3}\) [\d]{3}[-\s][\d]{4}
^\[.*\].*
[size=+3]Screenshots[/size]
[size=+3]Disclaimer[/size]
I am not responsible for your device. It you mess it up, it's your fault. Not mine. Not the app's. Yours and yours alone.
[size=+3]License[/size]
Code:
/*
* Copyright 2014 Eric Gingell (c)
*
* UnToasted is free software: you can redistribute it and/or modify
* it under the terms of the GNU General Public License as published by
* the Free Software Foundation, either version 3 of the License, or
* (at your option) any later version.
*
* UnToasted is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU General Public License for more details.
*
* You should have received a copy of the GNU General Public License
* along with UnToasted. If not, see .
*/
[size=+3]Downloads and Source[/size]
[size=+2]Source[/size]
* GitHub
[size=+2]Current Version[/size]
[size=+1]Version name: 1.2.8[/size]
Download: com.egingell.untoaster_v20_8d0e67.apk (127.6 KB)
MD5 checksum: 8d0e671eb5758345544b7c4cb4826629
Changes: NPE's no longer shown in the log.
[size=+2]Older Versions[/size]
[size=+1]Version name: 1.2.7.1[/size]
Download: com.egingell.untoaster_v19_29957f.apk (127.38 KB)
MD5 checksum: 29957f2ac9f52fb419ea6252c977485e
Changes: Oops. I forgot to "finish" the log activity when switching back to edit mode.
[size=+1]Version name: 1.2.7[/size]
Download: com.egingell.untoaster_v18_be8cd5.apk (127.38 KB)
MD5 checksum: be8cd5b9e54f88e595b54fc0a9b8f09d
Changes: Added in-app logs.
[size=+1]Version name: 1.2.6[/size]
Download: com.egingell.untoaster_v17_112263.apk (72.9 KB)
MD5 checksum: 11226334106fd36542fd49ae3c01d351
Changes: Using logcat instead of Xposed to log info (logcat | grep "UnToaster").
[size=+1]Version name: 1.2.5[/size]
Download: com.egingell.untoaster_v16_706b5b.apk (72.9 KB)
MD5 checksum: 706b5ba4191d47d60d4b1a6f730282a1
Changes: Xposed v52 had issues with my module's constructor. I don't know why it suddenly cropped up, but there you have it.
[size=+1]Version name: 1.2.4[/size]
Download: com.egingell.untoaster_v15_849860.apk (72.75 KB)
MD5 checksum: 84986088b0ab42c13eba98ff3da7c5f1
Changes: Per @rovo89 and @GermainZ in the Xposed Framework thread, I have switched my hook up slightly. It is unlikely that you, the user, will notice a difference.
More...
[size=+3]Other Notes[/size]
* I haven't tested this on KitKat *, JB 4.3 *, ICS, or Gingerbread, but they may work just as well. * Other members have stated that this works on 4.3 and 4.4.
* This doesn't work without an internal (built-in) SD card.
* This was tested on Touchwiz JB 4.1.2 and JB 4.2.2 stock.
[size=+3]Thanks[/size]
* @MohammadAG: For Buttered/Burnt Toast.
* @defim: For suggesting that I cache compiled regex patterns.
* @rovo89: For the Xposed framework without which this would not be possible.
* The numerous people, @FemBlack, @wanam, MohammadAG, rovo89, @zst123, and many others, who posted their source code for me and others to look at and learn from.
* MohammadAG, rovo89, @JamMasterClay, @GermainZ: For assisting me in figuring out the SharedPreferences dilemma.
For example....words with friends, or picsart. Any help appreciated on removing toast notification.
I'm on note3 vzw 4.3 rooted stock.
Sent from my SM-N900V using XDA Premium 4 mobile app
spetzuu said:
For example....words with friends, or picsart. Any help appreciated on removing toast notification.
I'm on note3 vzw 4.3 rooted stock.
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That explains why it doesn't work with those apps. The toast thinks it's originating from the app that has the ad.
The next version will have a way to put in a pattern for all apps which should alleviate that issue. In the mean time you can use the pattern "\[Xad\].*" in a separate entry for each app. It's not case sensitive.
Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
spetzuu said:
For example....words with friends, or picsart. Any help appreciated on removing toast notification.
I'm on note3 vzw 4.3 rooted stock.
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Try the attached*. Use "all" as the package name for blocking the same pattern from multiple apps.
Edit: *It's now linked in the OP.
egingell said:
That explains why it doesn't work with those apps. The toast thinks it's originating from the app that has the ad.
The next version will have a way to put in a pattern for all apps which should alleviate that issue. In the mean time you can use the pattern "\[Xad\].*" in a separate entry for each app. It's not case sensitive.
Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
Click to expand...
Click to collapse
Amazing man!! Thanks you made my day today cause those toasts were killing me lol Thanks again man
Sent from my SM-N900V using XDA Premium 4 mobile app
spetzuu said:
Amazing man!! Thanks you made my day today cause those toasts were killing me lol Thanks again man
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't blame you. I was about ready to toss my phone in the first 5 minutes of having Xad installed. Not that I needed it, but I like to be sure before I publish.
Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
Seems another problem has come about, though. Fix one thing and break something else. Oy.
Edit: Fixed.
Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
Don't know why it doesn't work for me anymore!
Sent from my GT-I9300 using Tapatalk
pesiran said:
Don't know why it doesn't work for me anymore!
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Just let me put on my psychic helm and I'll get right on that.
Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
Im sorry, I don't think I get it. Has anyone managed to block all greenify toasts "hibernated."?
I thought this would do it:
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
egingell said:
* A blank pattern box is the same as ".*".
Click to expand...
Click to collapse
lovely, lovely stuff. I just wanted a quick way to disable all notifications.
I added an entry "all" and left the pattern box blank, which didnt seem to work.
However and entry "all" and a pattern ".*" works perfectly
many thanks
Hehe, nice commit https://github.com/egingell/UnToasted/commit/f3b31b7c2e62f8c9e1dc16856b079849441761e3
rootSU said:
Im sorry, I don't think I get it. Has anyone managed to block all greenify toasts "hibernated."?
I thought this would do it:
http://img.tapatalk.com/d/14/01/26/a2uqenus.jpg
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Click to expand...
Click to collapse
Works for me.
oopled said:
lovely, lovely stuff. I just wanted a quick way to disable all notifications.
I added an entry "all" and left the pattern box blank, which didnt seem to work.
However and entry "all" and a pattern ".*" works perfectly
many thanks
Click to expand...
Click to collapse
I changed it so one can't accidentally block all toasts. Just add ".*" (dot star) to the "all" entry.
defim said:
Hehe, nice commit https://github.com/egingell/UnToasted/commit/f3b31b7c2e62f8c9e1dc16856b079849441761e3
Click to expand...
Click to collapse
:thumbup:
Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
egingell said:
Works for me.
Click to expand...
Click to collapse
Oh ok, so i'm on the right lines? You can't see any errors?
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
rootSU said:
Oh ok, so i'm on the right lines? You can't see any errors?
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Click to expand...
Click to collapse
I see nothing obvious.
I seem to be having another problem which is not throwing errors (UI related), so that should be fun. (Clicking some items pulls up the wrong entry or sometimes nothing at all and the sort function isn't working. Bleh.)
Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
Doesn't seem to work for me... Has anybody gotten this working on KitKat?
When I hit Save the save button just gets grayed out, but nothing else happens. It doesn't save the entry.
HTC One, CM11 (4.4.1)
nineplymaple said:
Doesn't seem to work for me... Has anybody gotten this working on KitKat?
When I hit Save the save button just gets grayed out, but nothing else happens. It doesn't save the entry.
HTC One, CM11 (4.4.1)
Click to expand...
Click to collapse
I haven't tested on Kit Kat and I won't likely any time soon, but I compiled it with Kit Kat SDK. It should still work unless the way apps are allowed SD card access has changed.
I may add more logging in future releases. Right now it just logs when it decides if the toast should be allowed or blocked.
Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
Can anyone explain,how to do it step by step
I really didnt got it
My Bad :- Working Now
It does not seem to work with kit Kat 4.4. The logs show allowed.
bggold said:
It does not seem to work with kit Kat 4.4. The logs show allowed.
Click to expand...
Click to collapse
Since you didn't provide any information, I can only assume it's because you didn't make any filters.
logcat -d | egrep "System\.err|UnToaster" also might help.
Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9

[DISCONTINUED][ROM][4.4.2 - UEU2CNE2][N5110] Terok Nor v3 Release 6 - 06/30

{
"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"
}
***Disclaimer***​I am not responsible if you break your stuff. Use at own risk!
I am not a developer and do not pretend to be one. I'm an Android enthusiast.
Why no Aroma?
Because I've made this ROM to my liking for myself, removing apps I'd never use. I have no need for a customized installer. I'm sharing this with you all because I'm sure there's somebody else who wants a simple, optimized ROM with the basic, stable features. If you want more options or customizations, this ROM isn't for you.
No complaints
I do this in my spare time.
Special requests
I'll accept special requests, but that doesn't mean they'll come true.
Bug Reports
Bug reports are welcome! Keep in mind: This is mostly stock and most bugs will be official firmware bugs.
Updates will come along when I have time and when I see something I'd like changed :good:​
ROM: Terok Nor
Based on UEU2CNE2 US Official Firmware
DeKnoxed system and kernel
Deodexed
build.prop improvements
Slimmed down
Busybox
AOSP 4.4 KitKat system sounds
Added AOSP 4.4 ringtones, alarms, notifications, and UI sounds
Removed power on sound
Custom, smaller S Pen pointer
Scrolling Wallpaper enabled in SecLauncher3.apk (TouchWiz Launcher)
Android L Keyboard
Galaxy S5 Boot Animation
SELinux: Permissive
Special Feature: @civato SphereKat blazing fast kernel with S Pen fix! For more info on his kernel, please see the SphereKat thread!​
*
Samsung Milk Music - Powered by Slacker
- Milk is supposedly available for all Galaxy devices, except it's not available for all Galaxy devices. I've added it here for you all to enjoy
*
Amazon Kindle for Samsung
Special Note:
* Images are copyright to their respective owners​
A GT-N5110
One of the latest recoveries that supports Andoird 4.4. I recommend the latest PhilZ recovery: Found here, flash in ODIN​
Bootloader upgrade: With Civato's SphereKat kernel, the 4.4 bootloader upgrade is no longer required!
IF YOU DO NOT MEET THESE REQUIREMENTS.. STOP HERE!​
A full wipe is only necessary if coming from a different ROM, including Terok Nor v2. All updates to v3 r1+ can be dirty flashed (unless otherwise noted).
1. BACKUP BACKUP BACKUP!
2. Flash
3. Reboot​
(click the image ^)​
MD5 hash: 25e41bad0695fc543dd75bde681fefb0​
Don't forget to hit the thanks button!
XDA:DevDB Information
Terok Nor v3, ROM for the Samsung Galaxy Note 8.0
Contributors
MrHyde03
ROM OS Version: 4.4.x KitKat
ROM Firmware Required: 4.4.2 Bootloader and TZ
Based On: UEU2CNE2 Official 4.4.2
Version Information
Status: Stable
Created 2014-05-26
Last Updated 2014-08-18
2014-06-30
Release 6
Added Android L Keyboard!
Added Galaxy S5 Boot Animation
Updated @civato 's SphereKat to v4.0
2014-06-10
Release 5
Removed S Note 3.1 (If you want, the install this APK S Note 3.1 APK
Rebuild on UEU2CNE2 US Official Firmware (XAR)
Now released with @civato's SphereKat kernel! Make sure you hit THANKS in his SphereKat thread and send him a beer!
Bootloader upgrade: With Civato's SphereKat kernel, the 4.4 bootloader upgrade is no longer required!
2014-05-28
Release 4
Deodexed /system/app, /system/framework, and /system/priv-app
2014-05-27
Release 3
Corrected issues brought on by R2 where the device would not boot after a clean flash.
2014-05-26
Release 2
Enabled Scrolling wallpaper in SecLauncher3.apk (TouchWiz Launcher)
Corrected Text Cursor offset in framework-res.apk, Thanks Civato
2014-05-26
Release 1
Initial release​
Civato
All others who've made modding Android possible​
Thanks to all who have donated I hope I can continue bringing a stable, smooth experience to the great people here at XDA :good:
Each * represents an additional donation! Much appreciated!!
rfb813 *​
There are currently two versions of S Note installed. The orange-red icon is the new version which is available on the GS5 as a "Galaxy ESSENTIAL". The brown icon is the stock Note 8 version. I may remove one of them in future updates.
STOCK KERNEL AND RECOVERY
Download this zip file and extract. The kernel (boot) and recovery are in their own .tar.md5 archives. Flash each in ODIN.
yay!
@MrHyde03
Regarding the S-pen cursor offset (cursor when hovering above a text with the pen), I fixed it in the framework (for the s-pen pointer I'm still waiting for kernel source, I mailed samssung yesterday for the source)
Here is the file for the framework file.
Decompile the framework and drop it in res/drawable-tvdpi.
When compiling the framework again it will throw some errors.
To slove this:
Go to res/drawable-tvdpi and remove the following files
tw_scrubber_control_focused_holo_red.PNG
tw_scrubber_control_holo_red.PNG
Then go to res/values/strings
open that file and on the line 1795 remove the % before the d and before the 2$s
it should look like this
Code:
<string name="wifi_p2p_enter_pin_dialog_message">Enter the PIN and tap Connect within d seconds to connect to 2$s.</string>
now compile and the errors will be gone.
civato said:
@MrHyde03
Regarding the S-pen cursor offset (cursor when hovering above a text with the pen), I fixed it in the framework (for the s-pen pointer I'm still waiting for kernel source, I mailed samssung yesterday for the source)
Here is the file for the framework file.
Decompile the framework and drop it in res/drawable-tvdpi.
When compiling the framework again it will throw some errors.
To slove this:
Go to res/drawable-tvdpi and remove the following files
tw_scrubber_control_focused_holo_red.PNG
tw_scrubber_control_holo_red.PNG
Then go to res/values/strings
open that file and on the line 1795 remove the % before the d and before the 2$s
it should look like this
Code:
<string name="wifi_p2p_enter_pin_dialog_message">Enter the PIN and tap Connect within d seconds to connect to 2$s.</string>
now compile and the errors will be gone.
Click to expand...
Click to collapse
Awesome. You just saved me some time.:highfive: Also, you don't have to delete the two PNGs, just change the extension from PNG to png. I also emailed Samsung on Saturday but have not had as much as a peep from them. Aren't they required under GPL to release the source when their software is released?
Anyways, thanks again Civ.
Updated to Release 2! Check Change Log for details.
Clean flashing to R2 is broken. Only works if dirty flashing. Because of this I've pulled R2 from the download. Go back to R1 if you're having issues with booting. I know what the issues are, I just don't have time tonight. It's late.
I've udpated the download URL to reflect R1.
MrHyde03 said:
Awesome. You just saved me some time.:highfive: Also, you don't have to delete the two PNGs, just change the extension from PNG to png. I also emailed Samsung on Saturday but have not had as much as a peep from them. Aren't they required under GPL to release the source when their software is released?
Anyways, thanks again Civ.
Click to expand...
Click to collapse
Yep they should release it . But some delay is expected.
Fixed the issues from R2. R3 is out and stable.
I could not get R2 to boot at all past the Samsung splash. I'll download R3 tonight. Thank you.
Sent from my GT-N5110 using XDA Premium HD app
glockman4519 said:
I could not get R2 to boot at all past the Samsung splash. I'll download R3 tonight. Thank you.
Sent from my GT-N5110 using XDA Premium HD app
Click to expand...
Click to collapse
Yep.. that was my fault.. sorry. I didn't properly recompile a few APKs, but we're all good now.
Release three working fine! Thanks and have one on me:4C4716763M934291T.
rfb813 said:
Release three working fine! Thanks and have one on me:4C4716763M934291T.
Click to expand...
Click to collapse
Glad you're enjoying it! Thanks!
2014-05-28
Release 4
Deodexed /system/app, /system/framework, and /system/priv-app
I was beginning to think this ROM wasn't going to install for me. I did an MD5 check - it passed. I flashed the new bootloader firmware and then flashed the PhilZ recovery. Tried to install the ROM and got an Error: Status 7. Tried the newer CivZ recovery and same thing.
Finally got it to install using TWRP 2.6.3 (my favorite, anyway).
Now going to try restoring data from v2.1 and see how that goes.
mletchworth said:
I was beginning to think this ROM wasn't going to install for me. I did an MD5 check - it passed. I flashed the new bootloader firmware and then flashed the PhilZ recovery. Tried to install the ROM and got an Error: Status 7. Tried the newer CivZ recovery and same thing.
Finally got it to install using TWRP 2.6.3 (my favorite, anyway).
Now going to try restoring data from v2.1 and see how that goes.
Click to expand...
Click to collapse
That is odd.. I flashed and reflashed and wiped then reflashed over and over to make sure I didn't have any more duds like R2 was and haven't had any issues with R4. Regardless, I'm glad you got it to flash.
Let me know if you have any other issues.
MrHyde03 said:
Let me know if you have any other issues.
Click to expand...
Click to collapse
Well, don't try restoring data from v2.1, it'll just cause tons of crashes and an error message that the Android UID doesn't match. Guess I'll be TiBU-ing this morning. Just as well, I see that R4 just posted...
mletchworth said:
Well, don't try restoring data from v2.1, it'll just cause tons of crashes and an error message that the Android UID doesn't match. Guess I'll be TiBU-ing this morning. Just as well, I see that R4 just posted...
Click to expand...
Click to collapse
If you're restoring from the same version recovery the backup was created with, then you shouldn't have any issues. That's been my experience. I've always had things break if I restore with a different recovery.
Should you update the firmware to the new Canadian firmware found on samfirmware? It was released after the UK firmware and Canada is closer to the US but there are probably no differences... just asking

Cyanogenmod 11 - Galaxy Tab Pro 12.2 (T900)

{
"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"
}
A CM Port for the Galaxy Tab Pro 12.2 from @crpalmer 's ROM.
​
I'M NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR DEVICE OF ANY SORT.
BY FLASHING THIS YOU TAKE RESPONSIBILITY OF ANYTHING THAT HAPPENS.
PROCEED AT YOUR OWN RISK!​
Make sure your tablet is a Galaxy Tab Pro 12.2 (SM-T900)
Make sure your tablet has 50% battery remaining or more
The ROM downloaded correctly
You know what you're doing
You know the risks involved
​
Being Updated
​
Boot to TWRP
Advance Wipe everything except Internal & External SD
Flash and wipe cache/dalvik
​
Crpalmer for making the original ROM for the Tab S
Valera1978 for fixing Google Play Store Crash Errors & SD Card :victory:
​
Version R3​
Version R4​
Version R5​
Original Link to the rom: http://forum.xda-developers.com/galaxy-tab-pro-12-10-8/orig-development/sm-t520-cyanogenmod-11-0-unofficial-t2870151​
Changlog:
R3:
Fixed Google Play Issues - Please Check
Fixed Stereo Sound
Fixed Bluetooth
Fixed Tethering
Better & Smoother Performance
Changlog:
R4:
Added Chromecast Screen mirror app built in thank to @r3pwn
Fixed Wifi losing password issues (Please test it out it should fix it but i'm not 100% sure)
Fixed Recent Apps Button
Changlog:
R5:
ROM is now a port from @crpalmer's CM build for the Tab Pro 10.1
XDA:DevDB Information
Galaxy Tab Pro 12.2 Unofficial CM, ROM for the Samsung Galaxy Tab Pro 12.2, 10.1, 8.4
Contributors
Shaheer
ROM OS Version: 4.4.x KitKat
Based On: Cyanogenmod
Version Information
Status: Beta
Current Beta Version: R3
Beta Release Date: 2014-09-05
Created 2014-09-05
Last Updated 2014-09-23
Reserved
Reserved
This is incredible work!
I'll flash this evening and reply back.
Thank you for all of your efforts here!
liebowa said:
This is incredible work!
I'll flash this evening and reply back.
Thank you for all of your efforts here!
Click to expand...
Click to collapse
No problem! I'm glad to contribute.
There are some issues of course like camera not working and microphone but on the majority of it works well.
Please do check if Google Play downloads apps properly!
Thanks!
Great Progress
Shaheer, your teamwork with Valera1978 have brought a fantastic improvement to this ROM in just a few days.
Most things are currently working:
- Bluetooth
- External SD Access (use SD KitKat Fixer for initiatial run)
- Root
- Google Play (Market)
- Stereo Sound
- Sync
- WiFi (though you need to manually login after reboot, R4 fix is not working)
- Cromecast (full screen transfer with #MirrorEnabler hack)
- init.d support (need installation)
- Text-to-speech
- Downloads
- Recent apps button (in navigation panel)
currently not working:
- PC mount (I tried everything I could think of - no go)
- Camera (causes system to crash - don't use)
- Screenshots
- Torch (Flashlight)
- GPS lock (can't get GPS lock, though works over WiFi, and I can't tell about voice guidance in Google Maps)
- Microphone (recording apps crash)
- Xposed Installer (att. causes black screen and will eventually crash, but you can still get it to work by insisting, I'm currently running about 15 MOD's - but it's a real hazzle at every new flash)
If there is a way to get the PC-mount to work, it would significantly help as the T900 is incredibly slow to wipe and format. To go from cm11 to stock and back to cm11 is a 45 min process, and this just to download and re-flash an update...But, you could of course use Google Drive or DropBox.
However, as I earlier stated, I'm really impressed of what it already can do, notably as this was done w/o access to a T900. Thanks a lot for all your efforts.
arcadia2uk said:
Shaheer, your teamwork with Valera1978 have brought a fantastic improvement to this ROM in just a few days.
Most things currently work:
- GPS (though I'm still not sure about voice guidance in Google Maps - will test later)
- Bluetooth
- External SD Access (use SD KitKat Fixer for initiatial run)
- Root
- Market
- Stereo Sound
- Sync
- WiFi (though you need manual login after reboot)
- Cromecast (full screen transfer with #MirrorEnabler hack)
- init.d support (need installation)
currently not working:
- PC mount (I tried everything I could think of - no go)
- Xposed Framework (causes black screen)
- Camera (causes system to crash - don't use)
Click to expand...
Click to collapse
WOW! Thanks for the great list of things working & not working! :highfive:
About the Wifi not remembering password upon reboot, i've never had that on the CM for my Tab Pro 10.1. Will look into it! :good:
Thank You!
You're welcome. I've added a few more items to the list
The cm11 ROM is very light weight, just about an eight (1/8) of the stock touchwiz ROM, 226M to download and another 25M for a mini GApps. Boot time seens to be 3- 4x faster, and this feeling continues while running the ROM, everything mounts so much faster. Overall it's very smooth and responsive.
As soon as the PC mount is fixed, this will be a breeze, but it's already indespensible. Besides, I can always use DropBox, or Google Drive for file transfers.
Update coming in a bit. It will fix chromecast mirroring, recent menu, small things. :victory:
Uploading R4 right now!
Change-log in the meantime: (Remember little things )
Added Chromecast Screen mirror app built in thank to @r3pwn
Fixed Wifi losing password issues (Please test it out it should fix it but i'm not 100% sure)
Fixed Recent Apps Button
Please check if init.d support is working out of the box.
arcadia2uk said:
You're welcome. I've added a few more items to the list
The cm11 ROM is very light weight, just about an eight (1/8) of the stock touchwiz ROM, 226M to download and another 25M for a mini GApps. Boot time seens to be 3- 4x faster, and this feeling continues while running the ROM, everything mounts so much faster. Overall it's very smooth and responsive.
As soon as the PC mount is fixed, this will be a breeze, but it's already indespensible.
Click to expand...
Click to collapse
Yeah, CM does seem faster than touchwiz doesn't it. Not always the case though, I tend to like touchwiz better but sometimes it gets on my nerves too.
R4 is literally almost done uploading in 10 seconds then i'll add the link to the OP. :highfive:
If I could just get camera and PC Mount working
Alright, R4 is uploaded and link is posted in the OP. Enjoy!
PS: Please read the changlog in the OP and please check if Wi-Fi remembers password after rebooting
1st try with R4 was not successfull
Shaheer said:
Alright, R4 is uploaded and link is posted in the OP. Enjoy!
PS: Please read the changlog in the OP and please check if Wi-Fi remembers password after rebooting
Click to expand...
Click to collapse
In R4, the WiFi connection is actually slightly worse than it was. At times it states disabled and you need to turn off Wifi and turn it on again and, bien entendu, manually enter your credentials again. Additionally, you still lose connection on almost every reboot. The same issue exist with the T-520 ROM, see posts #; 42, 43 and 112 in the T-520 forum.
However, the built in init.d support, SD Fix as well as the recent apps button all work well.
Additionally, I can confirm that there is no GPS lock.
I also installed Jeeko's MOD PurePerformances X and I'm at least under the impression that it runs even smoother now...
Anther alternative would be to try PMB Nitro X, but there was no uninstaller, or JustArchi's ArchiDroid Optimizations, but I couldn't figure out how to deploy it at 5am...
I also opted to install ViPER4Android Audio Effects in order to improve the sound in comparison with the built in DSP Manager.
When I get time, I will suggest a comprehensible list of tweaks, MOD's and tools, that will improve your performance, or make it a more enjoyable working environment. But, for the moment I need to concentrate on my upcoming final exam (9/27), and on getting a job thereafter. Once screenshots are working it will make more sense.
Shaheer said:
Yeah, CM does seem faster than touchwiz doesn't it. Not always the case though, I tend to like touchwiz better but sometimes it gets on my nerves too.
R4 is literally almost done uploading in 10 seconds then i'll add the link to the OP. :highfive:
If I could just get camera and PC Mount working
Click to expand...
Click to collapse
What's different between the camera used in the T525 and T520?
Wouldn't it be possible to port over crpalmer's "SM-T525 cm11.0 LTE" - (picassolte) camera to the T520, and maybe also some of the other broken parts?
Are there more things than the LTE capability that are different?
If the port from T525 to T520 works, it might also be possible to use in the T900...
Have you had any contact with crpalmer?
It seems like he has ordered a T520, and was interested in working on an Exynos based device.
crpalmer said:
I just ordered one. Seems like as good a time as any to see what it's like to work on an Exynos based device.
Click to expand...
Click to collapse
Searching for volunteer
LibiSC said:
Stock based
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Wouldn't it be nice to get a AOSP kernel to go with this ROM?
LibiSC's LibidinosoSC kernel for touchwiz T520 was a first break-though.
I hope that now when we have close to complete AOSP ROM's for the Exynos based devices. It would be nice to take a next step with one for cm11. Maybe, a fully working kernel could even solve some of the outstanding issues with the T520 and the T900 versions, it seems like LibiSC got some of this done with his kernel.
You never get too old for dreaming...or playing...
GPS fix from T-520 not working
Valera1978 said:
GPS fix. Should work GPS and GLONASS.
Relpace all files from attach to CM11_SMT520PortR4.zip and flash it.
Or you can manually copy\replace it using es explorer or root explorer.
But in this case please check rights:
gpsd: -rwxr-xr-x
gps.default.so: -rw-r-r-
Click to expand...
Click to collapse
I ported the GPS fix to the T-900 ROM, but it did not work. I spent about 3/4 of an hour under open sky. I re-placed the files according to instructions, as;
system/bin/gpsd rwxr-xr-x
system/etc/gps.xml rw-r--r--
system/etc/gps.conf rw-r--r--
system/lib/hw/gps.default.so rw-r--r--
Unfortunately, I had no GPS lock, what-so-ever. I also tried applying the various "gps.conf" found in the "perfect solution" threads at XDA, but non of them succeeded in getting a lock, using GPS Status Pro
I'm sorry, but at least I tried my best...
arcadia2uk said:
What's different between the camera used in the T525 and T520? etc.
Click to expand...
Click to collapse
Apparently it wasn't as easy as I thought, crpalmer explained that the cores are completely different between the T-525 and the T-520, one is qualcom, while the other is Exynos based. Apparently they are not at all compatible. Well, back to the drawing board...
arcadia2uk said:
I ported the GPS fix to the T-900 ROM, but it did not work. I spent about 3/4 of an hour under open sky. I re-placed the files according to instructions, as;
system/bin/gpsd rwxr-xr-x
system/etc/gps.xml rw-r--r--
system/etc/gps.conf rw-r--r--
system/lib/hw/gps.default.so rw-r--r--
Unfortunately, I had no GPS lock, what-so-ever. I also tried applying the various "gps.conf" found in the "perfect solution" threads at XDA, but non of them succeeded in getting a lock, using GPS Status Pro
I'm sorry, but at least I tried my best...
Apparently it wasn't as easy as I thought, crpalmer explained that the cores are completely different between the T-525 and the T-520, one is qualcom, while the other is Exynos based. Apparently they are not at all compatible. Well, back to the drawing board...
---------- Post added at 09:48 AM ---------- Previous post was at 09:44 AM ----------
We would really appreciate your help in participating in the creation of cm11 T-900
Click to expand...
Click to collapse
I didn't get to it lastnight, but this is on my list for this weekend, without a doubt. Heading to a wedding/reception shortly that will last (hopefully) well into the night!
I was researching the best way to root the tablet. Seems there is still no way to root w/o tripping the KNOX flag, correct?
If not, I assume the steps at this the following thread are all that's needed?
http://forum.xda-developers.com/showthread.php?t=2734177
liebowa said:
I didn't get to it lastnight, but this is on my list for this weekend, without a doubt. Heading to a wedding/reception shortly that will last (hopefully) well into the night!
I was researching the best way to root the tablet. Seems there is still no way to root w/o tripping the KNOX flag, correct?
If not, I assume the steps at this the following thread are all that's needed?
http://forum.xda-developers.com/showthread.php?t=2734177
Click to expand...
Click to collapse
I wrote a guide on how to root the T-900 a while ago, this is it.
Finally!
Thanks for all your hard work! Looking back at the thread you seem to be on your game regarding bug fixing.
About to take the plunge myself but wanted to ask the guys who have already flashed it.
I use my tablet all the time. Would you recommend R3 or R4 as a daily driver?
Great Job
Sent from my SM-T900 using Tapatalk

Categories

Resources