Z3/Z3C Sony Stock camera on AOSP/CM - Xperia Z3 Compact General

Not being stranger to ROM changing, after buying my Xperia Z3 Compact, I went straight for the bootloader unlock (following CM official wiki page). I did not backup my TA partition and therefore, my DRM keys are gone forever. Such is life. But I am not giving up...
I installed ResurrectionRemix (AOSP/CM based) and I am quite happy with it, but I thought it would be nice to have the original stock Sony camera functionality.
What I managed to do so far:
Mod the RR framework using this guide, which means:
- get /system/framework/framework.jar from your phone
- unpack classes.dex using your favorite archive tool
- decompile the classes.dex using Rom Tools (direct download link)
- overwrite the files with the ones from the linked guide
- compile it back to new classes.dex
- pack the modded classes.dex to the framework.jar
- copy the new framework.jar to /system
Install Sony Stock camera using this guide:
- flash the stock camera port
- flash panorama sweep fix
- flash face detection fix
Deactivate the standard CM camera apps
- including CameraWorkaround, Camera2, etc.
Clear data of all camera-related apps
- if you don't, the Sony Stock camera might crash, I checked logcat and found out it was because of SQLite DB version mismatch that the CM camera created and the Sony Stock camera couldn't use.
Then I found this thread:
[Z~Z5 Series][EXRxTHS]SONY DRM FUNCTION RESTORATION FOR UB DEVICE | Z3 lines support!
If what is claimed there really works, then the Sony proprietary image processing can be enabled even without the DRM keys. That basically means that the DRM keys are only used as verification, but the software performing the processing is indeed in the ROM.
The thread itself states that it is only for stock-based ROMs as AOSP/CM ROMs don't have the functionality in the first place. I might be wrong, but I believe that by modifying my framework I have imported some of these functionalities back into the phone.
If it was possible to port some parts, it should be possible to port more of them, including the image processing.
So I am starting this thread to track progress in this and to find the last piece of the puzzle - to bridge the gap between having Stock Camera framework and app on AOSP/CM ROM and the DRM patch, which probably patches the DRM-checking core to always return "keys are fine" even if they are missing,

I am interested in this as well, because I always prefer using AOSP than stock rom, be it on Sony device, Samsung, whatever. But lack of proper camera is keeping me away, mainly the reversed fish eye effect.
Have you experienced some crashes with that setup? I remember that people reported various crashes with that port.
I would help, but I have zero knowledge about coding and porting and everything associated with it unfortunately.

no crashes for me like this. but i have uninstalled most of the "fancy effects" apps in the bundle. so i got superauto, manual, livecast, some fx and stickers and thats about it

Hey, I'm also interessted in your work. How do you handle updates with this mod?

curlyboi said:
no crashes for me like this. but i have uninstalled most of the "fancy effects" apps in the bundle. so i got superauto, manual, livecast, some fx and stickers and thats about it
Click to expand...
Click to collapse
I don't need fancy stuff either, I would keep 4k video and Slow motion video out of all those and that's it. So I guess I could try some AOSP if it works on your side as you say
Some questions though. Do you think I can use zezadas' unlocked camera app with this port? It's just a matter of replacing apk only, nothing else.
And which version of RR do you use, based on CM13 or CM12.1?

It's RR based on 12.1.
And I don't plan on updating too often... Maybe once some very important fix comes out, but before that it's not necessary. I customize everything so every ROM reinstall is so much pain in the ass for me, hours going thru all the 200 apps and setting everything

Related

useful link

https://opensource.motorola.com/sf/projects/flipout
particular
https://opensource.motorola.com/sf/sfmain/do/go/rel1490?returnUrlKey=1294483663414
Wow! Cool!
It seems the china release is the latest. (That's what you link to). What I'd really like to fix is the x-y-z axis mapping of the accelerometer. So many apps don't work....
How do we use the files? Is it easy to pack roms, create Update.zip files, or just copy them to the right place?
ghostwheel said:
Wow! Cool!
It seems the china release is the latest. (That's what you link to). What I'd really like to fix is the x-y-z axis mapping of the accelerometer. So many apps don't work....
How do we use the files? Is it easy to pack roms, create Update.zip files, or just copy them to the right place?
Click to expand...
Click to collapse
Full ack with the accelerometer. But I fear it's not possible to install a custom rom without signing it with the Motorola key (at least that's what I heard).
/edit: After reading this, and this, its clear that the problem lies with Android 2.1: "FLIPOUT runs Android 2.1, or API level 7. The Display.getRotation() method is available as of Android 2.2, or API level 8. To handle this, you can detect the API version and on version 7 or below, use Display.getOrientation(), like this."
Nobody will use the workaround, so we will be stuck with a broken orientation sensor until (and only if) 2.2 is released for the Flipout.
zerghase said:
/edit: After reading this, and this, its clear that the problem lies with Android 2.1: "FLIPOUT runs Android 2.1, or API level 7. The Display.getRotation() method is available as of Android 2.2, or API level 8. To handle this, you can detect the API version and on version 7 or below, use Display.getOrientation(), like this."
Nobody will use the workaround, so we will be stuck with a broken orientation sensor until (and only if) 2.2 is released for the Flipout.
Click to expand...
Click to collapse
Interesting.
But I don't think this is the problem with the Flipout. Many apps actually adjust for screen orientation. Just the wrong way. No matter which way you hold the screen, orientation is off (e.g. Layar, wikitude).
And, the problem is old. It was around before 2.2 came out, or maybe when 2.2 was very young. So, I think most apps weren't written for 2.2 at that stage.
But to a question:
To produce a custom firmware we need to be able to sign stuff. (How was this found for droid?). But with root, we can overwrite anything on the phone, probably except for the init.rd, where the kernel is stored. Is that true? Could we patch by overwriting some files in, for example, /system/lib ?
Yes, with root you can change everything in the running system, but I don't know how far the kernel is protected. It could be possible that the kernel is signed and the system refuses to boot if it has been altered (but you should ask that a Motorola-pro, I'm new to that).
I think it's easier to modify the apps themselves. When they're open-source just apply the fix and recompile, if not...
maybe the developers will be grateful for some hints on bugs in their apps (I would be). And if they are not, it still appears easier to make a change to the bytecode of the erroneous apps than hacking something into the system to make some apps work (and maybe breaking others...).
If I have time, I'll read into the dalvik system and play around a bit with some apps.

best mod for elocity A7

My tablet was runnin dexter mod 1.4 with all the patches, buy always had problems with the sd card and the usb thumb and I also had problems running some applications. Right now my A7 is running [mod] update04-19 patched market + google apps and my tablet is working almost perfect. I think this mod is better that dexter mode.
I hope everybody use this mode in their tablets.
Thanks Bestialbub for your great job.
i jus got my elocity a7
i tried to mod mine with the dexter mod 1.41 and mines wont work,
1st- i download the file didn't unzip it then i sent it to the SD card and rename it "update.zip".
2nd- i did the factory wipe/reset then i select to wipe all data
3rd- i select update.zip but i notice an message saying( E. can't read from SD card). i dont know if that is apart of the mod or what.
4th- when it is finish then i select reboot option and when it is done rebooting i get nothing new. can you help me out are do you know something that i might be doing wrong. i also did do the 1.42 patch aswell didn't work. are is there another mod that you can tell me how to get it.
hasn't been tested for application on dexter's rom, though i don't know of reason they shouldn't work. gapps can be flakey like that; actually, the files are all stock as they come from cyanogen, minus my patched market, which doesn't have any reason not to work on dexter's rom and has nothing to to with the installation of the rest of google applications, including the calendar and text messaging services; i introduced no signature issues else it wouldn't install on stock firmware.
what i can suggest, is that if you're doing this under wiped conditions; is that you need to do a "factory reset" in recovery AFTER applying my gapps update.
if you don't do the factory reset, there will be settings put in place by the provision.apk in dexter's rom (not sure if this has changed in 1.42) that may conflict with the setup of google-apps. it didn't w/ the gapps in v1 i ported from dexters rom in previous tests, but i was going for a vanilla install w/out mixed signatures/versions/dates. provision.apk is generally suggested to be removed when google-apps is intended to be installed, and it is by my installer, but not the changes done in the data folders, which is why the wipe is suggested. i think its role is replaced by the googlepartnersetup.apk, but i could be wrong.
theres also some build prop differences; some unnecessary (gsm provider info), some improved (fingerprint for added apps in addition to patched market and added permissions), and the same ones necessary for apps like skype to run.
sorry if that was too much info. i do that.
EDIT: i reviewed my original post, its step *2B*. i did update it to underline it, and provide explanation for its probable necessity.
bestialbub said:
provision.apk is generally suggested to be removed when google-apps is intended to be installed, and it is by my installer, but not the changes done in the data folders, which is why the wipe is suggested. i think its role is replaced by the googlepartnersetup.apk, but i could be wrong.
Click to expand...
Click to collapse
SetupWizard.apk replaces "provision.apk".
bestialbub said:
theres also some build prop differences; some unnecessary (gsm provider info), some improved (fingerprint for added apps in addition to patched market and added permissions), and the same ones necessary for apps like skype to run.
Click to expand...
Click to collapse
Audio fix, which enhances EQUlizer and probably a 10% audio increase, and rotation support for games is another one..
the gsm props were actually very much needed, as Google for a period enabled provider checking, so if no gsm provider was there, you could not activate a google account, so instead of ppl getting lost without MarketEnabler on a clean device, i included it for safety reasons so next time, we're prepared for such checks.. so it all serves a purpose, if you like to know more, XDA has excellent information on those topics.
SetupWizard.apk replaces "provision.apk".
Click to expand...
Click to collapse
thanks for the tip. i did concede i could be wrong, and you're right, i could find that small detail that setupwizard is known to replace functions for provision.apk. the same posts i'm finding on xda and cyanogenmod don't say anything about googlepartnersetup, however, yet its provided with gapps packages..
i also learn from demonstrated and practiced examples..
demonstrated examples i learned from, including your 1.2 rom shows your remove provision.apk and provide googlepartnersetup.apk, then reverse the decision in 1.4, i ASSUME based on signiture issues you had stated (i generally don't have those as i know i can re-use existing containers without having signature issues).
i also learned/ported from various sdk's, including google's sdk for gapp imports, and neither is required, but what is provided is sdksetup.apk.. me seeing a relation from sdksetup for an sdk/emu android device kinda indicates one might want googlepartnersetup as a counterpart on a physical device. (your 1.4 example does prove that doesn't have to be true).. but the google sdk shows that i don't need setupwizard.apk for google services either.
thought i'd relate, since most the general posted information i've seen on xda and cyanogenmod seem like vague gueses at best. though i suspect the people posting this information aren't necessarily the devs working closely with the files. just hobbists and modders making educated guesses like me.
Audio fix, which enhances EQUlizer and probably a 10% audio increase, and rotation support for games is another one..
the gsm props were actually very much needed, as Google for a period enabled provider checking, so if no gsm provider was there, you could not activate a google account, so instead of ppl getting lost without MarketEnabler on a clean device, i included it for safety reasons so next time, we're prepared for such checks.. so it all serves a purpose, if you like to know more, XDA has excellent information on those topics.
Click to expand...
Click to collapse
i was refering to MY gsm provided build prop information, i wasn't ragging on your build prop or rom addons. i followed suit to the gtab tnt modrom and added DIFFERENT gsm provider information than yourself (service provider id, not google client information). but it made no difference in gapps present demonstrated performance as this information DOES NOT (the stuff i provided/borrowed from tntlite) get passed into the android system or database files, as no service provider id is listed when opening marketaccess.apk, as it does on a phone device that does genuinely have this information.
i do concede to the thread discussion, tho, DEXTERS ROM IS THE BEST AND ONLY FULL ROM MOD FOR THE A7 TABLET!!!
my gapps mod is only intended to provide google applications ommitted by the manufacture. nothing more.
thanks for the indirect market patching instructions!
thanks am going to retry and see what happends
bestialbub said:
but it made no difference in gapps present demonstrated performance as this information DOES NOT (the stuff i provided/borrowed from tntlite) get passed into the android system or database files, as no service provider id is listed when opening marketaccess.apk, as it does on a phone device that does genuinely have this information.
Click to expand...
Click to collapse
Had the same issues, so i found the trick to be adding it in the boot.img using the default.prop, and it is added during bootup.. but now we're OT! so let's leave it at that.
a7 installation problem
these are the exat message i got (E:can't open/usb/update.zip)
(E:Can't mount USB:update.zip)
then underneath that it say (Finding update package)
then it say (Wait for 5 second)
(Installation time out)
(installation aborted)
(Formatting MISC)
these are all the thing it say during installation
these are the exat message i got was (E:can't open/usb/update.zip)
(E:Can't mount USB:update.zip)
then underneath that it say (Finding update package)
then it say (Wait for 5 second)
(Installation time out)
(installation aborted)
(Formatting MISC)
these are all the thing it say during installation
why post the same thing every 10 minutes?
.............................
demamalu said:
My tablet was runnin dexter mod 1.4 with all the patches, buy always had problems with the sd card and the usb thumb and I also had problems running some applications. Right now my A7 is running [mod] update04-19 patched market + google apps and my tablet is working almost perfect. I think this mod is better that dexter mode.
I hope everybody use this mode in their tablets.
Thanks Bestialbub for your great job.
Click to expand...
Click to collapse
That is not a mod it's the factory firmware with a patch to get market, I don't see in what way it is better than Dexter mod.
kevinppk said:
these are the exat message i got was (E:can't open/usb/update.zip)
(E:Can't mount USB:update.zip)
then underneath that it say (Finding update package)
then it say (Wait for 5 second)
(Installation time out)
(installation aborted)
(Formatting MISC)
these are all the thing it say during installation
Click to expand...
Click to collapse
When this happen I remove the .zip from file name or just rename the file but most time removing. .zip does the job...

[REF] Nexus S ROM&Kernel Survival Guide

Introduction:
Please read and try to do some research instead of bombarding the developers with the same questions over and over, cluttering the threads with useless and recursive information. I will try to include terms for all the ROMs and Kernels in the Development Section, and remove the obvious things as much as possible. That doesn’t mean it will be perfect! I hope this will be useful for beginners, because it provides most of the basic information you need to get started. From now on, it’s up to you what you do.
I am fully aware that the information included here is for one time use, enough to get you started. Some of these things ARE well known by many of you, but they are still useful for others that are just beginning to learn about their NS. Besides definitions and explanations, I’ll also link to useful posts around xda and other sites, which provide further information on the respective subject.
ROMs​(ROM: a firmware that contains the Android operating system, and at least critical apps necessary for running your phone (but usually more apps than just those); can be stock or custom, and comes packaged in a *.zip file, flashable under recovery)
AOSP-built ROMs
Features: these are built from source code, from the Android Open Source Project, delivered free of bloatware and with rich customizations.
Some of the most popular (at the moment):
GSM VERSION: i9023/i9020A/i9020T
CyanogenMod 9 (still in alpha stages for now)
IML74K Android 4.0.3 Build 4 - Quad Lockscreen + More MODS (1/15/12)
nuhetri- v1.0.0
Slim ICS
AOSP+ V2.3|ICS 4.0.3|Source Built|Status Bar Widgets + Nice Mods
4G VERSION
vhgomez36-ICS-NXS-4G-4.0.3 r2.0
IML74K Android 4.0.3 Build 3 - Quad Lockscreen+More MODS
Crossbones v0.1.3
CyanogenMod 9 v4.0.3 - Alpha 20
Click to expand...
Click to collapse
Moddified ROMs
Features: these are modified versions of stock/AOSP ROMs/other custom ROMs, that keep the look of the base ROM up to a certain point. Also generally free of bloatware and with some additional modifications.
Some of the most popular (at the moment):
GSM VERSION: i9023/i9020A/i9020T
CyberGR-MOD|NS.NGN ver. 4.0 Ultimate
NSCollab 1.0.60
Ultimate ICS v4.0
-=Nexus MV 1.12.09=-
KANGY6 | ICS | AOKP |
NexusBeam 4.2.3
CyberGR-MOD|NS.NGN ver. 3.0 Hybrid ICS
Click to expand...
Click to collapse
MIUI-style ROMs
Features: unique type of ROM, developed by the Chinese. Has a strong iOS feel, highly customizable.
Some of the most popular (at the moment):
GSM VERSION: i9023/i9020A/i9020T
◄ ▌ [09.Jan.12] [ROM] Brainmaster's MIUI 2.1.6 ICS | Stable 2.3.7b v2 GB ▌►
DianXin OS (DX ROM) ICS | GB ROM
4G VERSION
◄ ▌ [28.Nov.11] [ROM] brainmaster's MIUI NS4G 1.11.25 | OTA ▌►
Click to expand...
Click to collapse
Stock ROM
Official releases from Google. The reasons most people here flash a stock ROM are: they want to update/ are bored of custom ROMs/ want to start over with their phone/ warranty reasons.
If you want to go back to stock for some reason, check this thread and read carefully, so you get the correct version for you.
Click to expand...
Click to collapse
Once we decide for a type or ROM (except stock), we head over to the ROMs thread and begin reading the list of features. Now would be a good time to PANIC! No, no, just kidding Those words do exist in some kind of language (not necessarily English). So here’s a very basic list of the most common terms found in our ROM threads:
Code:
[B]AOSP[/B]
[quote]Short for [url=http://source.android.com/]Android Open Source Project[/url]. Its purpose is to maintain the development
of the Android platform. Anyone can use the Android source code for
any purpose, and this is when custom ROMs come in. The [AOSP]
tag is used here to signal a ROM built from Google’s source, a pure
ROM, free of bloatware, with very good performance (generally)
and a very extended degree of customization. [/quote]
[B]Build.prop[/B]
[quote]This file is located in /system/build.prop. It holds the majority
of the runtime flags that are used when Android boots. Basically, it
lists specific information about your device, for applications to use.
You can also edit lines, with a file manager that has access to
/system, in order to change LCD density, build number, device
model and many more. [/quote]
[B]Busybox(ed)[/B]
[quote]Busybox is a collection of simple, but powerful Linux
utilities, that Android doesn't come with by default. It is used
by applications like MetaMorph and Titanium backup in order
to do special operations. You can manage ther version installed
on your phone with various apps from the [url=https://market.android.com/search?q=busybox&c=apps]market[/url] [/quote]
[B]/boot partition[/B]
[quote]This partition includes the bootloader and kernel, and
it enables the phone to boot. Wiping it must be done only if
requested, and the phone must not be rebooted after this operation.
Instalation of a new one is done by flashing a ROM that includes
the /boot partition. [/quote]
[B]/cache partition[/B]
[quote]Inside this partition, Android stores frequently accessed
data and app components. Performing a wipe of the /cache does
not affect personal settings or files, but simply gets rid of existing
data there, which gets automatically rebuilt in time. [/quote]
[B]Dalvik cache[/B]
[quote]Dalvik cache collects the information about the installed
applications and frameworks, and organizes them into a writeable
cache. Under this writeable cache, it stores the “optimized”
bytecode of the applications which is used by the applications
themselves later for a smoother operation. This dalvik cache can
grow as more applications are installed on your phone. It is safe
to wipe dalvik-cache. It will be rebuilt again when the phone
boots. This also explains why your phone takes ages to start up
for the first time. [/quote]
[B]/data partition[/B]
[quote]Also called userdata, the data partition contains the user’s
data – this is where your contacts, messages, settings and apps
that you have installed go. Wiping this partition essentially performs
a factory reset on your device, restoring it to the way it was
when you first booted it, or the way it was after the last official
or custom ROM installation. When you perform a wipe data/factory
reset from recovery, it is this partition that you are wiping. [/quote]
[B]Deodex(ed)[/B]
[quote]In Android file system, applications come in packages with
the extension .apk. These application packages, or APKs contain
certain .odex files whose supposed function is to save space.
These ‘odex’ files are actually collections of parts of an application
that are optimized before booting. Doing so speeds up the boot
process, as it preloads part of an application. Deodexing is basically
repackaging of these APKs in a certain way, such that they are
reassembled into classes.dex files. By doing that, all pieces of an
application package are put together back in one place, thus
eliminating the worry of a modified APK conflicting with some
separate odexed parts. The advantage of deodexing is in modification possibilities. On the other hand, since the .odex files were supposed
to quickly build the dalvik cache, removing them would mean
longer initial boot times. However, this is true only for the first
ever boot after deodexing, since the cache would still get built
over time as applications are used. [/quote]
[B]EFS folder[/B]
[quote]This is a VERY important folder. It contains phone-specific
information, like IMEI (encrypted in the nv_data.bin), wireless
devices MAC addresses, product code (also in the nv_data.bin)
and more. I advise you to make a backup of this folder, and keep
it safe. Remember, backup BEFORE flashing anything. Use [url=http://forum.xda-developers.com/showthread.php?t=1138873]this tool from forum member Borky_16[/url]. [/quote]
[B]Init.d[/B]
[quote]Init.d is very useful because it runs scripts that you can
just delete or replace in the /system/etc/init.d folder. The scripts
are also very flexible and can be used to call other scripts or set
a variety of system settings. [/quote]
[B]G-apps/Gapps[/B]
[quote]A long time ago, in a galaxy far far away, there was a
developer. And he used the Force for developing something called
CyanogenMod. For the happiness of the other folks in the galaxy,
he included some applications from Google. But the Emperor…
oh, sorry… But Google didn’t agree with him including these
proprietary apps, so they sent him a cease and desist letter.
Long story short, the Google Applications are provided separately
via a flashable .zip file. This is the case for pure AOSP ROMs,
and theoretically this is how it should be done. Theoretically. [/quote]
[B]Host File[/B]
[quote]Located in the /etc/ folder, it is used to block ads.
Most ROMs come with a “blocks ~95% of ads” statement. You
can also manage it with apps from the [url=https://market.android.com/search?q=ad+block&c=apps]market[/url]. [/quote]
[B]Logcat[/B]
[quote]The Android logging system provides a mechanism for
collecting and viewing system debug output. Logs from various
applications and portions of the system are collected in a series
of circular buffers, which then can be viewed and filtered by
the logcat command. You can use logcat from an ADB shell to view
the log messages.[/quote]
[B]NANDroid[/B]
[quote]When you take NANDroid backup, it means you are
backing up entire ROM. It’s basically a picture of the ROMs’
state . So when something goes wrong, you have the
chance to restore your phone to the backup state using the NANDroid. [/quote]
[B]NSTools[/B]
[quote]An essential tool that manages tweaks like BLN,
BLD, BLX, Liveoc, OC, CPU Governor, Deep idle and so on.
Written by arifhn, available in the [url=https://market.android.com/details?id=mobi.cyann.nstools&feature=search_result#?t=W251bGwsMSwyLDEsIm1vYmkuY3lhbm4ubnN0b29scyJd]market[/url] and on [url=http://forum.xda-developers.com/showthread.php?t=1333696]xda[/url],
this is a must have application for managing these various options. [/quote]
[B]Odex[/B]
[quote]These ‘odex’ files are actually collections of parts
of an application that are optimized before booting. Also explained at deodex(ed). [/quote]
[B]Power Menu[/B]
[quote]A multiple choice menu that appears when long pressing
the power button. In stock, these are critical options,
such as powering down the device. Developers have also
added options for taking snapshots,
rebooting normally/into bootloader/into recovery and so on. [/quote]
[B]Radio[/B]
[quote]The radio controls basic low-level functions like
network connectivity, Wi-Fi, and GPS. It comes as a radio.img file,
and generally, developers try to leave this out of their
ROMs because different areas require different radios. Pay attention
to this when choosing to flash a new ROM. There is a reference
thread with all the radios [url=http://forum.xda-developers.com/showthread.php?t=1116884]HERE[/url]. [/quote]
[B]Ramdisk[/B]
[quote]Ramdisk.img is a small partition image that is mounted
read-only by the kernel at boot time. It only contains /init
and a few config files. It is used to start init, which will
mount the rest of the system images properly and run the
init procedure. A Ramdisk is a standard Linux feature. [/quote]
[B]Recovery[/B]
[quote]Recovery mode in Android provides an environment for
users to wipe cache, data, factory reset the phone or update
it with a .zip file. There are custom recoveries like [url=http://www.clockworkmod.com/rommanager]ClockworkMod[/url] or [url=http://forum.xda-developers.com/showthread.php?t=1399565]TWRP[/url], which provide additional functionality,
and are very popular for this reason. [/quote]
[B]RTL[/B]
[quote]Short for Right-to-Left and refers to support for languages requiring this type of writing. [/quote]
[B]SetCPU[/B]
[quote]An application built by coolbho3000, which allows CPU speed tweaking and management, allows overclocking, and sets CPU governors. Available on [url=http://forum.xda-developers.com/showthread.php?t=505419]xda[/url] and the [url=https://market.android.com/details?id=com.mhuang.overclocking&feature=search_result#?t=W251bGwsMSwyLDEsImNvbS5taHVhbmcub3ZlcmNsb2NraW5nIl0.]market[/url] (try to buy from the market if you want to support his work). [/quote]
[B]SIM Toolkit (STK)[/B]
[quote]Now if you live in the States, you might not even know what
the STK is, so a bit of explaining is in order. Put simply, the STK
allows carriers to load a simple set of menus and 'applications' on
your SIM card. Earlier versions of Android, up to 1.6, actually
included a rather rough, but functional Sim Toolkit application, but
at some point it was dropped. [/quote]
[B]/system Partition[/B]
[quote]This partition basically contains the entire operating system,
except the kernel and the bootloader. This includes the Android
user interface as well as all the system applications that come
pre-installed on the device. Wiping this partition will remove Android
from the device without rendering it unbootable, and you will
still be able to put the phone into recovery or bootloader mode
to install a new ROM. [/quote]
[B]Unsecured Boot.img[/B]
[quote]Used for adb remount, gets you root by default on a shell. (ro.secure=0) [/quote]
[B]V6 Supercharger Script[/B]
[quote]A more technical explanation could be done here, but
the bottom line is that this is used to make your phone run
faster, by better management of memory. [/quote]
[B]Zipaling[/B]
[quote]Zipalign is an archive alignment tool introduced first
time with 1.6 Android SDK (software development kit). It
optimizes the way an Android application package (APK) is
packaged. Doing so enables the Android operating system to
interact with the application more efficiently, and hence has
the potential to make the application and overall the whole
system much faster. Execution time is minimized for zipaligned
applications, resulting is lesser amount of RAM consumption
when running the APK. [/quote]
Kernels​
(Kernel: provides the most basic level of control over all of the phone's hardware; consider them a link between the hardware components and the ROM)
With kernels it’s a little bit easier. At least this is how it may seem. Right after rooting the device, many choose to first flash a kernel (including me) mostly because it gives the opportunity to flash something while not modifying the appearance of the phone. Furthermore, it gives you the ability to change things like CPU clock speed, internal and ARM voltages, and also have different patches and mods designed to prolong battery life/improve speed/provide stability.
Kernels are abundant for the NS, so I’ll be naming the most popular:
GLaDOS
ICUP Kernel Edition
*Matr1x*
SG-NS-ICS - 14-01-2012 - 11UV|Voodoo|BFQ|BIGMEM|BLN|BLD|BLX|TW|Lazy|3.0.15
Netarchy Nexus
NS+4G Trinity (E)UV and OC CM9 + m(any) roms
Click to expand...
Click to collapse
Many users ask around about which could be the best kernel. For this, xda member bedalus decided to set up a thread where he benchmarked ICS kernels (accurately enough). This should give you an idea where to start from.
Also, there are terms which appear frequently in the features list of kernels, so here’s a very basic list of the most common terms found in our kernel threads:
Code:
[B]BFS[/B]
[quote]A Brain F**ked Scheduler will perform better on CPU intensive
process, which usually cause them to get higher benchmark scores.
However because it only dedicates minimal CPU to background
processes you may experience lag when switching quickly between
different tasks. [/quote]
[B]BLD[/B]
[quote]Backlight Dimmer provides an option for the lights of the
touchkeys to be turned off after a certain period. This can be
tweaked from NStools. [/quote]
[B]BLN[/B]
[quote]Backlight Notification is a mod developed by neldar,
which converts the touchkey backlights into a notification led. [/quote]
[B]BLX[/B]
[quote]Battery Life eXtender, from Ezekeel, manages the maximum
percentage to which the battery is being charged. By default,
the Nexus S is charged to about 95% capacity. [/quote]
[B]CFS[/B]
[quote]A Completely Fair Scheduler is more suited for multitasking.
You may notice performance issues when using CPU heavy
activities like HD games because it is trying to keep the other
processes in the background equal to the one that is hogging the
CPU. It should also be noted that, as designed, this type of
kernel should handle going from listening to music to sending a
text to surfing the web with minimal lag. [/quote]
[B]Deep IDLE[/B]
[quote]Another mod by Ezekeel, which allows the phone to
enter a “deep idle” state while performing tasks when the screen is
off. For example, listening to music with the screen off and
Deep Idle turned on, you should get better battery life than
without Deep Idle. [/quote]
[B]Governors [/B]
[quote]There is a much to be said here, and this would stretch
this dictionary too much. I recommend reading [url=https://github.com/CyanogenMod/cm-kernel/blob/android-msm-2.6.37/Documentation/cpu-freq/governors.txt]THIS[/url], a very good explanation of
governors—from CyanogenMod. [/quote]
[B]OC (Overclock)[/B]
[quote]An overclock is usually one of the first things users
figure out after gaining root access on a new phone. If you
want to push your smartphone's CPU to run more clock cycles,
you have to know that extra power isn't coming from nowhere.
However, it is generally considered good practice, but it
depends on your handset. Some phones may be able to support
overclocking to 1.4 GHz, while others may never get past
1.2 GHz. Just proceed with caution. [/quote]
[B]Touch Wake[/B]
[quote]Yes, yes, Ezekeel again. This mod allows the user to
wake the device after a set amount of time, just by touching
the screen or the capacitive buttons. The time after which the
screen no longer responds to a touch is set with NStools. [/quote]
[B]UV (Undervolt)[/B]
[quote]This refers to lowering the voltage to conserve power while
still achieving the same performance, assuming your settings
remain stable. Both SetCPU and NStools allow the user to change
voltages. Like overclocking, this is also a trial and error process,
because each phone is different. The benefits are low energy
consumption and less thermal output. [/quote]
Tools & Mods​
So you have a rooted phone. Maybe even a custom Kernel or ROM, whatever works for you. But you still want to be a tad different from the other guys using the same configuration as yours. So here's a small selection of mods and apps developed by members of the community, enough to get you started. Feel free to experiment, and remember: read before flashing, search before asking and you should be alright!
Mods for AOSP+ Rom
[BOOTANIMATION] Plain, Simple & Colorful + color variants
Nova Launcher
Flavours for stock OTA ICS 4.0.3
Search key to ICS recent apps [add CM9 version]
[NS][NS4G]FaceLock for ICS 4.0.3
Enable on-screen buttons in ICS roms
Click to expand...
Click to collapse
NOTES:
I am hoping this little survival guide is useful FOR BEGINNERS in understanding the basic terminology used here in the Nexus S sections. As the title suggests, it was made with beginners in mind, so I don’t want posts of so called “experts” saying how they already knew this.
IMPORTANT: I do NOT guarantee the explanations written here are completely accurate or complete, FOR NOW. I will keep working on this, correcting mistakes as I continue to read.
If you find something that you think is not correct, or consider something must be added, please post here, together with a link to a credible source.
All of this came from sources off the internet, so please bear with me. Also, sorry for any typing mistakes. If you see any, please be sure to signal them
If I have helped you in any way, or if you appreciate the work invested in this (now and for the future), press the THANKS button.
Thank you! (Hoping to see this stick) And many thanks to all the great devs working on ROMs and Kernels for us. Keep up the great work!
W O R K - I N - P R O G R E S S
(I will be sure to notify you when I believe this is complete)​
Wow this is a very good idea. Thanks!
Sent from my Nexus S using Tapatalk
ljordan2 said:
Wow this is a very good idea. Thanks!
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Thank you! I'm just worried it is a little bit long... but in the next couple of days I will be making it more reader friendly
Transmitted from somewhere in space... from my Nexus S... and Tapatalk.
nice thread! thanks
Hey great post, i still haven't rooted my nexus s but you just made me flash a kernal. I was tkinking about it but never too serious.
thanks!
Love it!!! Cleared so much up (you recieved my first Thanks button click!)
Just wanted to clarify something about the Kernel. My Rom is stock 2.3.6 that was received OTA when I unboxed the phone (Nexus S GSM i9020A, I'm in Canada). The bootloader is unlocked, phone rooted with CWM recovery via one click (QBKing's Video). Am I able to flash a custom Kernel to a stock Rom? Reading the above seems to lean towards the "yes", but wanted to make sure first.
Also, do not use the one click method on the Nexus S GSM if you want to easily return to stock. The one click stock only supports the 4G, which is extremely silly and inconvenient IMO. I'm currently still trying to figure out how to return to stock, incase something does happen and the phone needs warranty work. Let's just say, I'm not making much progress and this is extremely uncomfortable ATM..
Great thread and idea, all seems spot on. I vote for sticky.
Also, heX, you can flash a custom kernel on a stock rom as long as you have an unlocked bootloader and custom recovery. I'd recommend you backup all you need with TB or similar, then do unlock your bootloader if you havn't already (search around for how to do this, described in rooting guides). Just remember this will delete -ALL- user data, including sdcard. After this you can flash a su.zip to have proper root access, and you can easily install a stock image with a custom bootloader then lock the bootloader afterward for pure stocky goodness.
Thanks so much for taking the time to do this
Sent from my Nexus S using XDA App
Harbb said:
Great thread and idea, all seems spot on. I vote for sticky.
Also, heX, you can flash a custom kernel on a stock rom as long as you have an unlocked bootloader and custom recovery. I'd recommend you backup all you need with TB or similar, then do unlock your bootloader if you havn't already (search around for how to do this, described in rooting guides). Just remember this will delete -ALL- user data, including sdcard. After this you can flash a su.zip to have proper root access, and you can easily install a stock image with a custom bootloader then lock the bootloader afterward for pure stocky goodness.
Click to expand...
Click to collapse
TYVM Harbb!
Yes, currently the bootloader is unlocked, phone rooted and CWM installed. I did a TB backup prior so I could quickly restore my apps and settings. All is running well.
I tried to flash a full stock Rom back to the phone, but have run into an issue in doing so, posted here
I'm still awaiting some help with regards to that one, hopefully all will be well soon.
I'm not sure why I got spooked in doing this. I'd like to try the Matrix kernel and there are various Roms that definitely sound fantastic, but part of me just wants it back to stock so warranty and OTA are restored as the phone is only a few weeks old.
very useful for us newbie, thanks for sharing
heX79 said:
TYVM Harbb!
Yes, currently the bootloader is unlocked, phone rooted and CWM installed. I did a TB backup prior so I could quickly restore my apps and settings. All is running well.
I tried to flash a full stock Rom back to the phone, but have run into an issue in doing so, posted here
I'm still awaiting some help with regards to that one, hopefully all will be well soon.
I'm not sure why I got spooked in doing this. I'd like to try the Matrix kernel and there are various Roms that definitely sound fantastic, but part of me just wants it back to stock so warranty and OTA are restored as the phone is only a few weeks old.
Click to expand...
Click to collapse
Ok I see you have the att version, so i9020A. When android 4.0.3 came out, I wanted to go back to stock 2.3.6 so that I could update officially. Anyway, I downloaded a full stock ROM, flashable via recovery, from HERE and all went smooth for me. (the link is to the i9020A version, of course I used the i9023 version). Try the stock posted there, and see if you get any error. I think you should be ok now, if not, post back. Remember, this takes you fully back to stock, no cwm, no nothing custom.
I am glad to see that I helped somenone, I will make some modifications this afternoon, still 9am here (maybe add stuff to the dictionary and post it to google docs or something like that, just to make it easier to scroll through and more). Any suggestions or critics are welcome!
EDIT: Guide updated:
-better arrangement of the dictionary (will be adding new terms tomorrow, had to study for an exam today)
-added Tools & Mods section (will build on that later on)
-more to come...
great post OP
Nice thread! Great Work ,Thanks
Hey thanks! Happy to see good feedback on this.
Transmitted from somewhere in space... from my Nexus S... and Tapatalk.
Great beginners guide, and thanks for the link!
For kernel benchmarks and more, see here: http://goo.gl/mpeHI
Thanks very much! I will give it a try shortly, just to confirm if I recieve any issues. I've also installed the recommended CWM version for my model, not sure if it makes a difference, but I flashed 5.0.2.0 anyway as the version I was getting an error with had a higher build number.
Right now I'm enjoying AndroidME 1.2.3 with Speedy 6 kernel and have no complaints so far! (Kernel updated this morning from Speedy 5)
I will report back with any issues once I have some time to do a Nandroid backup and test the stock Rom.
Thanks for your help!
It's nice to know there's a way to revert back to stock, should anything need servicing! I've also started reading up on Odin
flodb113 said:
Ok I see you have the att version, so i9020A. When android 4.0.3 came out, I wanted to go back to stock 2.3.6 so that I could update officially. Anyway, I downloaded a full stock ROM, flashable via recovery, from HERE and all went smooth for me. (the link is to the i9020A version, of course I used the i9023 version). Try the stock posted there, and see if you get any error. I think you should be ok now, if not, post back. Remember, this takes you fully back to stock, no cwm, no nothing custom.
I am glad to see that I helped somenone, I will make some modifications this afternoon, still 9am here (maybe add stuff to the dictionary and post it to google docs or something like that, just to make it easier to scroll through and more). Any suggestions or critics are welcome!
EDIT: Guide updated:
-better arrangement of the dictionary (will be adding new terms tomorrow, had to study for an exam today)
-added Tools & Mods section (will build on that later on)
-more to come...
Click to expand...
Click to collapse
You're welcome! Looking forward to an update with your stock flashing situation. I also used ClockworkMod 5.0.2.0 a long time. I'm now on 5.0.2.3 only for the better menu layout.
Transmitted from somewhere in space... from my Nexus S... and Tapatalk.
just one question...
can i install more than one kernel at a time...
for eg.like one i installed for battery usage and othr for sound..
can i do tht

LG G2 F320S Camera Shutter Sound & Info About Camera Workings

About two months ago I purchased an LG G2 F320S which is really good, except for one thing that's really annoying me: because it's a Korean variant, I'm unable to silence the camera when taking a picture.
I've rooted my phone and tried installing LGCamera.apk from: http://forum.xda-developers.com/showthread.php?t=2670972
Given the poster of the apps seems to have the D802 variant, which I believe gives you the option of silencing the camera when taking a picture, I would have expected that installing this APK to provide me the same option. However, after placing the APK and ODEX files in the priv-app directory and restarting, my camera still has no option to silence it (the same 4 shutter sound options).
I have seen some flashable camera packages posted on here which also contain native libraries, but I don't see how these help because the sound files are contained in the APK (also, I don't have a custom recovery flashed as I nearly bricked the phone permanently the last time I tried - had even managed to mess up download mode). I've previously unzipped the APK and tried to remove or change the sound files, but it looks like the resources are signed in some manifest file so that changing them isn't possible without going through the process of creating a signed package (and I would assume you'd need LG's private key in order to achieve that, rather than being allowed to sign your own). What does flashing the C/C++ native libraries give you?
The most annoying thing is that the shutter sound wouldn't even stop a determined perve, as there are camera apps in the Play Store which just save the screen preview (ie full HD image, in the case of the G2) as a photo without making a sound, so the whole thing is just pointless and annoying.
Can anyone provide me with information or pointers to information on how to get rid of the stupid shutter sound on the F320S variant while being able to take 13 megapixel pictures? I am a C# developer and am not a complete stranger to Linux or Java, so feel free to be technical. Even just some information on why my bundled camera APK will install, but others won't (though some will when you restart the device after placing them in the priv-app folder when the phone does an 'installing update' thing) would be useful to know.
Thanks in advance!
Ascy said:
About two months ago I purchased an LG G2 F320S which is really good, except for one thing that's really annoying me: because it's a Korean variant, I'm unable to silence the camera when taking a picture.
I've rooted my phone and tried installing LGCamera.apk from: http://forum.xda-developers.com/showthread.php?t=2670972
Given the poster of the apps seems to have the D802 variant, which I believe gives you the option of silencing the camera when taking a picture, I would have expected that installing this APK to provide me the same option. However, after placing the APK and ODEX files in the priv-app directory and restarting, my camera still has no option to silence it (the same 4 shutter sound options).
I have seen some flashable camera packages posted on here which also contain native libraries, but I don't see how these help because the sound files are contained in the APK (also, I don't have a custom recovery flashed as I nearly bricked the phone permanently the last time I tried - had even managed to mess up download mode). I've previously unzipped the APK and tried to remove or change the sound files, but it looks like the resources are signed in some manifest file so that changing them isn't possible without going through the process of creating a signed package (and I would assume you'd need LG's private key in order to achieve that, rather than being allowed to sign your own). What does flashing the C/C++ native libraries give you?
The most annoying thing is that the shutter sound wouldn't even stop a determined perve, as there are camera apps in the Play Store which just save the screen preview (ie full HD image, in the case of the G2) as a photo without making a sound, so the whole thing is just pointless and annoying.
Can anyone provide me with information or pointers to information on how to get rid of the stupid shutter sound on the F320S variant while being able to take 13 megapixel pictures? I am a C# developer and am not a complete stranger to Linux or Java, so feel free to be technical. Even just some information on why my bundled camera APK will install, but others won't (though some will when you restart the device after placing them in the priv-app folder when the phone does an 'installing update' thing) would be useful to know.
Thanks in advance!
Click to expand...
Click to collapse
I have a UK EE LG G2 and I can assure you that that trying to silence the camera click doe NOT work! By all accounts you need to 'root' the phone and delete 'cameraclick.ogg' (which I believe is only accessible when in root (which you appear to have?)
.
Michael
A Bit of an off-topic thing, but i am facing the same problem on my Lg g3 as well.
Removing the camera_click.ogg from the system>media>audio>ui folder does not do the trick.
The actual LGCamera.apk will need to be decompiled and the audio file contained in the res>raw folder will need to be replaced with a silent one.
However i do not know the exact procedure to recompile and re-sign the apk again
nisargz said:
A Bit of an off-topic thing, but i am facing the same problem on my Lg g3 as well.
Removing the camera_click.ogg from the system>media>audio>ui folder does not do the trick.
The actual LGCamera.apk will need to be decompiled and the audio file contained in the res>raw folder will need to be replaced with a silent one.
However i do not know the exact procedure to recompile and re-sign the apk again
Click to expand...
Click to collapse
Exactly the issue, so I've given up on it. In fact, I removed root entirely (not an easy job) as it was preventing updates.
I had tried replacing the sound files in the camera app, but the package needs to be signed. I would assume that just signing the package isn't enough, but that it would need to be signed by an LG authorised key for it to be recognised.
Ascy said:
Exactly the issue, so I've given up on it.
Click to expand...
Click to collapse
Just to let you know the new G3 Tweakbox Xposed Module works like a charm and silences all the annoying camera sounds. Time to root again I guess lol

CleanMyXperiaZ2Tablet - Flashable DeBloater (MM 23.5.x compatible)

--- [ introduction ]
this script removes bloatware from Sony Xperia Z2 Tablet with MarshMallow Stock Rom (23.5.x) and should work with all models and regions.
initially designed to debloat SGP511, SGP521 & SGP551, it should be the best companion for your prerooted flash image
--- [ how to ]
just flash it with your favorite recovery
--- [ requeriments ]
recovery, busybox
--- [ not removed ]
radio, gapps, infraredremote, tv (SGP551), dualshock, mirrorlink, mhl, screenmirroring, myxperia (device location), remote shares, smallapps framework , xperia home, xperia themes framework, throw, display enhancements, tap & play, soundpicker
--- [ removed ]
Code:
/data/app/com.google.android.apps.genie.geniewidget-1
/data/app/com.google.android.marvin.talkback-1
/data/app/com.linkedin.android-2
/data/app/com.mobisystems.fileman-1
/data/app/com.navigon.navigator_select_sony_eu-1
/data/app/com.s.antivirus-1
/data/app/com.scee.psxandroid-1
/data/app/com.sony.nfx.app.sfrc-1
/data/app/com.sony.snei.np.android.account-1
/data/app/com.sony.snei.vu-1
/data/app/com.sonyericsson.album-1
/data/app/com.sonyericsson.extras.liveware-1
/data/app/com.sonyericsson.music-1
/data/app/com.sonyericsson.music-2
/data/app/com.sonyericsson.video-1
/data/app/com.sonyericsson.xhs-1
/data/app/com.sonymobile.androidapp.audiorecorder-1
/data/app/com.sonymobile.androidapp.cameraaddon.areffect-1
/data/app/com.sonymobile.backgrounddefocus-1
/data/app/com.sonymobile.calendar-1
/data/app/com.sonymobile.entrance-1
/data/app/com.sonymobile.lifelog-1
/data/app/com.sonymobile.moviecreator.rmm-1
/data/app/com.sonymobile.sketch-1
/data/app/com.sonymobile.smallbrowser-1
/data/app/com.sonymobile.support-1
/data/app/com.sonymobile.xperialink
/data/app/com.sonymobile.xperialink-1
/system/app/AntHalService
/system/app/ar-effect
/system/app/BasicDreams
/system/app/br.com.camposony
/system/app/BrowserProviderProxy
/system/app/CameraAddonPermission-release/CameraAddonPermission-release
/system/app/CameraCommonPermission-release/CameraCommonPermission-release
/system/app/CameraExtensionPermission-release/CameraExtensionPermission-release
/system/app/ClockWidgets-release
/system/app/com.sonyericsson.xhs
/system/app/com.sonymobile.brazil.blogsony
/system/app/com.sonymobile.xperialounge.services
/system/app/enchantedforest-release
/system/app/ExactCalculator
/system/app/Exchange2
/system/app/experienceflow2livewallpaper-release
/system/app/ExternalKeyboardJP
/system/app/FaceLock
/system/app/Galaxy4
/system/app/GetMoreClient-release
/system/app/GoogleAnalyticsProxy
/system/app/GoogleLyricsPlugin
/system/app/HoloSpiralWallpaper
/system/app/IddAgent
/system/app/Lifelog-googlePreloadLive-release-3.0.P.1.24-6292504
/system/app/LiveWallpapers
/system/app/LiveWallpapersPicker
/system/app/LockscreenSettings-release
/system/app/NewsWeather
/system/app/NoiseField
/system/app/OmaDownload
/system/app/OmaV1AgentDownloadServices
/system/app/PartnerBookmarksProvider
/system/app/PhaseBeam
/system/app/photoslideshow-release
/system/app/PhotoTable
/system/app/PhotoWidget-release
/system/app/PrintSpooler
/system/app/SemcAutoPowerOff
/system/app/SemcEmail
/system/app/socialife
/system/app/SomcPOBox
/system/app/SoundEnhancement
/system/app/Stk
/system/app/support
/system/app/talkback
/system/app/textinput-tng-live
/system/app/Theme000-sw720dp-hdpi-release
/system/app/Theme001-sw720dp-hdpi-release
/system/app/Theme002-sw720dp-hdpi-release
/system/app/Theme003-sw720dp-hdpi-release
/system/app/Theme004-sw720dp-hdpi-release
/system/app/Theme005-sw720dp-hdpi-release
/system/app/Theme006-sw720dp-hdpi-release
/system/app/Theme007-sw720dp-hdpi-release
/system/app/Theme008-sw720dp-hdpi-release
/system/app/TopContactsWidget-release
/system/app/TouchBlock
/system/app/wallpaperpicker-release
/system/app/WAPPushManager
/system/app/WeatherWidget-release
/system/app/WikipediaPlugin
/system/app/WorldClockWidget-release
/system/app/YouTubeKaraokePlugin
/system/app/YouTubePlugin
/system/priv-app/ActiveClipper
/system/priv-app/album-albumLive-release
/system/priv-app/ArtFilterCamera-hdpi-release
/system/priv-app/BackupRestoreConfirmation
/system/priv-app/CameraCommon
/system/priv-app/CameraWearableBridgeHandheldServer
/system/priv-app/CellInformationNotification
/system/priv-app/CrashMonitor
/system/priv-app/CrashMonitorSystem
/system/priv-app/CustomizationSelector-hdpi-release
/system/priv-app/DefaultCapabilities
/system/priv-app/DualCamera-hdpi-release
/system/priv-app/GetMore-release
/system/priv-app/livewaremanager
/system/priv-app/ManagedProvisioning
/system/priv-app/OMAClientProvisioning-release
/system/priv-app/OnlineRemoteCamera-hdpi-release
/system/priv-app/ScreenRecording
/system/priv-app/SemcCamera3D-hdpi-release
/system/priv-app/SemcCameraUI-hdpi-release
/system/priv-app/SemcClock
/system/priv-app/SemcMusic
/system/priv-app/SemcPhotoEditor
/system/priv-app/SemcVideo
/system/priv-app/SmallApp-Calculator-release
/system/priv-app/SmallApp-Timer-release
/system/priv-app/SomcMovieCreator-release
/system/priv-app/SomcPhotoAnalyzer
/system/priv-app/SomcPodcast
/system/priv-app/sonyentrance2-release
/system/priv-app/SoundPhotoCamera-hdpi-release
/system/priv-app/SoundRecorder
/system/priv-app/Tag
/system/priv-app/textinput-chn-hdpi
/system/priv-app/TimeShiftCamera
/system/priv-app/UpdateCenter-release
/system/priv-app/WapPush
/system/priv-app/youtubelive
--- [ download ]
View attachment cleanmyxperiaz2tablet-v01d.flashable.zip
reserved
Looks like this removes just about everything. Does it have aroma or the like? Just in case you want to keep things like Gmail and time shift camera?
I just the user could go through all the list and delete as they see fit, with root and a file manager.
Are there any plans for that?
Definitely a fantastic idea though. Great stuff. Thanks
Sent from my SGP511 using Tapatalk
voryzen said:
Looks like this removes just about everything. Does it have aroma or the like? Just in case you want to keep things like Gmail and time shift camera?
I just the user could go through all the list and delete as they see fit, with root and a file manager.
Are there any plans for that?
Definitely a fantastic idea though. Great stuff. Thanks
Click to expand...
Click to collapse
I'd love an aroma option for this mod
voryzen said:
Looks like this removes just about everything. Does it have aroma or the like? Just in case you want to keep things like Gmail and time shift camera?
I just the user could go through all the list and delete as they see fit, with root and a file manager.
Are there any plans for that?
Definitely a fantastic idea though. Great stuff. Thanks
Sent from my SGP511 using Tapatalk
Click to expand...
Click to collapse
gmail is not removed, pre-installed google stuff is untouched
time shift camera can be installed from google play, you can move from internal to system partition if you want, the debloater will leave around 0.9GB to 1GB free space
also you can edit this script easily, just open with a proper text editor and edit the lines.
danalec said:
gmail is not removed, pre-installed google stuff is untouched
time shift camera can be installed from google play, you can move from internal to system partition if you want, the debloater will leave around 0.9GB to 1GB free space
also you can edit this script easily, just open with a proper text editor and edit the lines.
Click to expand...
Click to collapse
Actually under the OP 'removed' heading, it mentions /system/app/gmail2
This isn't the Gmail app?
It says it right in between 'getmoreclient-release' and 'googleanalyticsproxy'
Sent from my SGP511 using Tapatalk
voryzen said:
Actually under the OP 'removed' heading, it mentions /system/app/gmail2
This isn't the Gmail app?
Click to expand...
Click to collapse
oh my bad, forgot to separate my personal version
indeed, it is removing the gmail2 from system partition
but it gets updated so often, it would be better to move it entirely to system (plus updates) if you use it a lot
if you require to add or remove a line, just edit the update-script and everything will be ok
when I get more time, will write an online builder, so we can customize options before download, waddya think?
Yea, perfect. Would work great for me. That would be a good idea for you too, if you had a website that had (non-invasive) ads on it.
It would drive more traffic to your site and give you some monetary incentive.
If you were to make it downloadable from this xda thread though, it might be worthwhile to have an aroma version hosted here, as well.
The idea being, that if the user can't build it online before downloading, they can customise the end result themselves, after downloading.
Couple of ideas for you, to think about.
I look forward to seeing what you can do with this marvellous little project you've started. Keep up the good work, it is appreciated.
Thanks danalec, it's cleaned up my home screen nicely, the only apps I want back are Music, Video, Album and Camera. I can add all that stuff back in with a script editor? Also Keyboard disappeared and got this blank area at the bottom where it's set up for mic.
lionelglitchie said:
Thanks danalec, it's cleaned up my home screen nicely, the only apps I want back are Music, Video, Album and Camera. I can add all that stuff back in with a script editor? Also Keyboard disappeared and got this blank area at the bottom where it's set up for mic.
Click to expand...
Click to collapse
yes, google play has it. the script is made for those who already installed some apps before cleaning.
I don't really recommend to use the script in the current state.
I've started to code the Aroma version but it will take a while.
remember this script is much easier to edit, you just need to use a unix text format compatible (like notepad+).
I've got ROM Toolbox Pro so I will try the editor on that. I grabbed keyboard and album from google play, but when I installed music I got the generic ''unfortunately, music has stopped working'' message.
I can't find the z2 camera app anywhere but I found another thread with the 2.0 port from the Z5 which apparently works on the z,z2,z3. optimistically, I flashed it but of course it failed :laugh: some have had success with it on lollipop but not MM
lionelglitchie said:
I've got ROM Toolbox Pro so I will try the editor on that. I grabbed keyboard and album from google play, but when I installed music I got the generic ''unfortunately, music has stopped working'' message.
I can't find the z2 camera app anywhere but I found another thread with the 2.0 port from the Z5 which apparently works on the z,z2,z3. optimistically, I flashed it but of course it failed :laugh: some have had success with it on lollipop but not MM
Click to expand...
Click to collapse
what? just remove the lines at update-script
danalec said:
reserved
Click to expand...
Click to collapse
ь [SGP521][23.5.A.1.291][6.0.1] VMo RU:UA:KZ flashable-prerooted
Your zip does wonders, running smooth as butter keep up this mod updated:good:
I tried running many non stock Roms but I get random reboots so Im forced to run stock and your mod does magic.
The script is nice, however I would modify it in order to:
- remove Google apps that can be installed from Google Play: there is no point in having them pre-installed when they will be duplicated in /data at the first update;
- restore stock camera functionality;
- restore default keyboard as it would be impossible to use the tablet if you flash before the first login;
- remove PS Video and Sketch which are currently left untouched.
Maybe I will post my version as soon as I have finished it.
maxlnc said:
- restore default keyboard as it would be impossible to use the tablet if you flash before the first login;
Click to expand...
Click to collapse
that's a huge issue , if u (like i did) flash this file after u installed a "stock based" rom in twrp, u gonna sit there at first startup without any keyboard and unable to install some

Categories

Resources