Hey all,
I am new to the Android community. I just rooted my Nexus and flashed the Oxygen rom on it. It comes with the Netarchy kernel 1.3.5.(has awesome battery life) On the forums i noticed a lot of people posting about a trinity uv kernel for oxygen. Can anyone explain the difference between the kernels. Will changing the kernel affect my battery life?. And there is a new netarchy, should i update it to the latest version or just use the one which comes with the rom.. I am really a novice here, So any help would be appreciated. .
In computing, the kernel is the main component of most computer operating systems; it is a bridge between applications and the actual data processing done at the hardware level. The kernel's responsibilities include managing the system's resources (the communication between hardware and software components).[1] Usually as a basic component of an operating system, a kernel can provide the lowest-level abstraction layer for the resources (especially processors and I/O devices) that application software must control to perform its function. It typically makes these facilities available to application processes through inter-process communication mechanisms and system calls.
{
"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"
}
And yes, a new kernel might make your device faster with less battery drain. If you would like to flash a new kernel, then go do it. If you're not happy with the performance then flash a new kernel or revert to the original. But remember to do a NAND backup (full backup of your system/current OS) with ROM Manager before you begin.
Related
{
"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"
}
Adobe has released a new version of its Flash Player for Android that fixes some critical security bugs. The new version of Flash, which, incidentally, is also available for Windows, Linux and OS X, fixes security vulnerabilities in Flash Player 11.1.115.6 and earlier versions for Android 4.x, and Flash Player 11.1.111.6 and earlier versions for Android 3.x and 2.x. These vulnerabilities, if exploited, could cause a crash and potentially allow an attacker to take control of the affected phone or tablet.
The update fixes two problems – the first is a memory corruption vulnerability in Matrix3D, a part of Flash which is used to determine the position and orientation of a three-dimensional object, that could lead to unauthorized code execution. The second vulnerability patched is an integer error that can lead to information disclosure.
Don’t Panic
Although these vulnerabilities are seen as critical, Adobe has rated them as “priority 2″ which means that there are currently no known exploits, and, based on previous experience, Adobe does not anticipate that exploits are imminent. As a result, Adobe is recommending users to install the update within the next 30 days.
The new update should be aviliable in the market but all of us know that in the market no adobe flash player for galaxy fit.
Any one upload new arm6 adobe player version ?
{
"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"
}
What is an APK List?
It's a developers tool. Sometimes I find an app which design I really like but have no idea how it is done. Besides that most of the time my phone isn't rooted (or I'm using some other phone). With all unpack/decompile tools out there the only thing I need is a way to copy APK files from phone memory to SD card for later analysis. Well this tool is just that, it lists all installed apps on any phone and let's you copy all or selected APKs to SD card. Currently there are no settings so destination defaults to "Apks".
Where can I get this app?
Download APK here
Or grab source from https://bitbucket.org/grupatnt/apklist/overview and compile with MonoDevelop or VS2010 (Mono for Android 4.x)
What can I do to help?
Fork hg repository, make fantastic changes and add Pull request.
I've found a bug! What do I do?
Keep calm and report it! You can report it either on this thread or on project Issues tracking register. Bug reports will be taken seriously and fixed when I have the time.
Thanks to _Logie from whom I've copied format for this post
Kudos to Android SDK and Intel teams for releasing VM Accelerated x86 Emulator.
Version 0.0.2 Released
Get it here
Changes
Cancelable progress dialog
Fixed APK Icon sizes
Beautified progress dialogs
Replaced ApkListAdapter with generic FastListAdapter
Mono for Android developers
Take a look at FastListAdapter and ViewHolderBase which implement View Holder pattern in generic way. You only need to implement abstract ViewHolderBase, instantiate new FastListAdapter and assign it to ListView Adapter. You can find example implementation in ApkViewHolder, easy
[ZIP][First-aid 4 Android]: Fastest way to fix "too many pattern attempts" and others
{
"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"
}
First-aid 4 Android
First-aid 4 Android is a custom recovery flashable zip powered by AROMA Installer of XDA Developer @amarullz to provide you the ability to choose between packaged quick fixes to specific problems which renders your phone unusable without the need to resort to Reflashing of ROMs or Factory Reset. First-aid 4 Android utilizes the reverse-engineering idea to undo the process.
For now, First-aid 4 Android only contains fixes for the problems listed below:
(But we will add more in the future.)
Screen Security: Too Many Pattern attempts
Soft-brick after installing new custom font
System Requirements:
From Aroma Installer Thread: Your device must have ARM Neon support.
Custom recovery like CWM, TWRP or others...
If you know other non-manufacturer-specific android problems that can be recoverable and want to contribute the idea to us, you are welcome reach us by posting it here. Please show us how to reproduce the problem and if you also knew the steps of fixing it, please add it too but it is not necessary... we will do our best to reverse engineer it...
Please HIT the Thanks button if you find this useful! XD
Click to expand...
Click to collapse
Hi all,
I combined the default installed packages on most of the popular ROMs for this phone in an easy to read spreadsheet. Now you can see what differences each ROM has in stock installed packages, for me it was useful to check if a particular system app was available on another ROM without having to install that ROM. All the ROM maintainers do a great job, it was hard to decide.
Included is the stock Motorola 24.49.18.3 (Marshmallow) ROM, compared to TrupureXMM, Temasek, Vanilla CM13, AICP, Bliss, Dirty Unicorns and the Nexus 5X CM13 ROM (as it uses the SD808 as well, some of the system and radio packages will be the same).
The motivation for this was noticing a few unrecognised system apps in the ROM I was using, then I wondered if they existed on other ROMs, or the stock ROM as well. I built the list by extracting the system .dat images and pulling the package names from the manifest XMLs to make comparing easier. It's now all scripted so adding more ROMs is quick.
Hopefully this will help some people decide on ROMs or raise some questions as to what different packages are. For example, what is com.motorola.motocit or com.verizon.omadm or com.android.sprint.lifetimedata doing on AOSP and is it required?
Full Spreadsheet can be viewed/downloaded here:
https://docs.google.com/spreadsheets/d/1YRD2NDWg9JPvOy6WMytF3HXQu69fTX-OlJfWT4MRJjg/edit?usp=sharing
Screenshot (partial):
{
"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"
}
Note:
* These are just packages only, does not correlate to features, or performance/reliability, etc. Just for reference/curiosity only. Any questions about the ROMs themselves please go to the ROM thread, the maintainers have put in alot of hard work on their ROMs.
* Removing pre-installed apps may have adverse effects, also will not free up space as the /system partition has a pre-set size.
* If there are other ROMs you want added, let me know. Depending on public interest, I might add human-friendly names, or more information like permissions required / file size.
{
"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"
}
Boot Control is an Android app that toggles the active boot slot.
Notes
It uses the same HIDL interface as bootctl to read the data and make the change.
Credits
@badabing2003 for the idea and for testing the many builds of both the app and bootctl
Latest Update
2023-06-22 v1.0.0-alpha02
capntrips said:
(...)
Latest Update
2023-06-22 v1.0.0-alpha02
Click to expand...
Click to collapse
BootControl-main.zip = 120 KB
BootControl-v1.0.0-alpha02.apk = 38.8 MB
Why such a drastic difference between SC and APK?
ze7zez said:
Why such a drastic difference between SC and APK?
Click to expand...
Click to collapse
The size of the source code has basically zero bearing on the size of the APK. As for why the APK is so large, I can sum that up with a link to one line in the app's build.gradle file.
The longer explanation is R8 breaks HIDL for some reason. I tried a variety of ProGuard rules with no luck. If I build it with Soong instead of Gradle it works fine, but it can't be installed on older devices. I may have been able to find a workaround for the latter issue, but it's much more convenient to build it with Gradle. Beyond that, the Soong build had issues with the Java HIDL interface, so I had to make a C++ library for HIDL and use JNI to interface with that, making the whole thing a bit more complex.
The broken minified Gradle build is ~8mb and the limited Soong build is ~14mb.
@capntrips
On p6, you need to disable verity (but not verification) in vbmeta on both slots to get Boot Control to switch slots without getting a corruption message.
Can the tool be modified to perform this task?