XDA Elite Recognized Developer AdamOutler is known for his wizardry opening up Samsung phones. However, this also extends to other manufacturers’ devices, such has how he recently dismembered the Oppo Find 5. And he’s not limited to phone devices, as he Poked at the JynxBox Network Streaming Android Device. However, it is often good to get back to your roots. That is why AdamOutler is taking on the Samsung Galaxy Note 10.1.
After tearing down and giving the Note 10.1 an Unboxing the XDA Way. He continues by giving a tour of the device’s components. AdamOuter demonstrates the device setup, as well as installing recovery and rooting the device. The device can be rooted easily, perhaps too easily, using CASUAL. So if you wanted the freedom to do what you want with a device you bought, check out this video. Also, check out the full Teardown Hangout and Jailbreak video.
Owners of the Verizon variant of the Samsung Galaxy Note 10.1 tablet will no longer feel left out, thanks to the unlock package that XDA Elite Recognized Developer AdamOutler posted late Friday night. Although he takes issue with the word ‘unlock,’ preferring to call it a ‘jailbreak’ because that term is exempted by the DMCA.
The process couldn’t be easier thanks to Adam’s CASUAL software. I’m sure you’ve heard of it before since it’s been features on XDA TV and several Portal posts. The software provides a GUI for scripts that use the Android Developer Bridge (ADB) and it works on Linux, Mac, and Windows. The power of CASUAL is well represented in this procedure. Adam’s demo video shows that clicking the Do It button and following the prompts is all it really takes. From there, the script performs an IROM unlock using exploits discovered by Lee Harrison (Recognized Developer Ralekdev).
Get your hands on the unlock package by heading over to the original thread. While you’re there, heed Adam’s warning about flashing once you unlock your Note. The exploit used leaves it vulnerable to being bricked if you flash a file not meant for this specific hardware.
Everyone has a secret place. Perhaps it is a restaurant tucked away on a side street that makes the best pulled pork. Perhaps it is a picnic table at the far corner of the park where you can sit and enjoy the serenity of the nearby babbling creek. Maybe it is not actually a place, rather a secret band or website that you and few select other know about. At the risk of sounding like a hipster, it almost seems like the Samsung Galaxy Note 10.1 tablet is that special secret device.
Originally released at the end of August in 2012 and just recently given the goodness of Jelly Bean 4.1. This device has been eclipsed by bigger announcements, like the Google Nexus 10. However, over the time I’ve had the device I’ve come to enjoy it and believe it is an underrated device.
January 29, 2013 By: jerdog
Anyone who has spent time on XDA, or in the Android community at large, knows that when a device receives inclusion in CyanogenMod’s device tree, it is a beautiful day. This is because CM support ensures that the device will have a longer-than-manufacturer-intended lifespan. This of course depends on the manufacturer providing the tools and documentation necessary for development to occur. In many cases, OEMs do a pretty good job at publishing the documentation for instances in which they deviate from the reference design of a device’s board. Other times, however, manufacturers seem to go into brain fart-mode when it comes to this.
Samsung, in their
infinite wisdom, has made it extremely difficult for devices based on the Exynos 4 reference design to receive CyanogenMod 10.x nightlies. This is not new news, as it’s been well-covered that Samsung continues to fail the community when it comes to devices based on their Exynos 4×12 devices (Galaxy S3, Galaxy Note 10.1, Galaxy Note 2, Galaxy Camera, Meizu MX). The sources from Samsung are consistently missing required pieces in order to be GPL-compliant, and recent investigations have found Gingerbread-remnants in their ICS sources.
All of that has not deterred XDA Recognized Developers espenfjo and Entropy512 from diligently laboring to bring the CM10.1 experience to the Galaxy Note 10.1. There have been obstacles, but they have pressed through. Thanks to their work, the Note 10.1 (N80o0 GSM and N8010/N8013 WiFi) recently began to receive CyanogenMod nightlies. As of the time of this posting, there are issues with Netflix working on CM10.1 but Entropy512 has put together a workaround for all Exynos 4 devices via the Xposed framework.
As is always the case, the typical disclaimers apply as CM10.1 is a work-in-progress, especially on these devices. So if you have a bug to report, make sure you post a logcat in the thread with a detailed description of what you were doing and what happened. In order to flash the builds, you will need to use either TWRP or Entropy’s CWM build because they are the only ones that are confirmed to work at this time. If you receive an ‘assert failed‘ error message, you should first confirm that you are indeed using one of the two aforementioned recoveries.
January 14, 2013 By: Joseph Hindy
Overclocking and underclocking your device’s processor can be very useful in certain circumstances. Overclocking can help aging hardware keep up with newer software, and underclocking (as well as undervolting) can help squeeze more time out of a battery charge.
One of the more popular CPU management applications, Tegrak, received an update recently to make it compatible with Galaxy Note 10.1 and all variants of the Galaxy Note 2. Here are the official change log for the app:
*supports all variants of Galaxy Note II and Galaxy Note 10.1
*fixed bug of the overclock-able max freq on Galaxy S III JB
… more in
There are a few fixes for other devices as well, but the main feature addition is support for the Note 2 and 10.1 devices. What’s more, it can overclock and underclock certain stock kernels to an extent. For instance, users have found that they can overclock their Galaxy Note 10.1 to 1.6 GHz to match the clock speed of the Galaxy Note 2. Reports state that anything higher than that will freeze the device. As with any instance in which you run your hardware outside of recommended specifications, there are risks involved, so be sure to be fully appraised of what you’re doing before doing it.
January 2, 2013 By: Pulser_G2
One of the major features of many recent Samsung phones (or should we say “phablets?”) or tablets with the S-Pen is a suite of TouchWiz additions, such as a keyboard featuring handwriting recognition and gesture typing. While other keyboards might offer handwriting functionality, and some may call this is a gimmick; XDA forum members were clear in their requests that, while they might choose to use other keyboards, they want to retain these features offered by the stock Samsung keyboard—without the hassle of manually changing keyboard.
Enter XDA Recognized Developer LegendK95, with his app SPenBoard Switcher. If your device is capable of detecting when the pen is removed, it should be possible to use this app to change your default keyboard between two of your choice. While it is likely that most users will want to use this application to change from a third party keyboard to the Samsung keyboard when the pen is removed (and back when it is re-inserted), it is possible to select any keyboard for either state.
This app is a good example of the benefits of Samsung’s S-Pen SDK, which is available from the Samsung Developer website. Through the APIs provided by Samsung, it is possible for apps to take advantage of features of the operating system pertaining to the S-Pen, such as identifying if the pen has been removed from the device, the pressure being applied to the pen, or the state of the side button on the pen.
While the app has been mainly tested on variants of the Galaxy Note II, it should work on any recent S-Pen enabled device that is capable of notifying you when the S-Pen has been removed from the holder. If you want to give the app a try, check it out over in the apps sub-forum, bearing in mind that it requires root access to install to the system partition. This is required in order to change the current keyboard input method without prompting you each time.
Apps like this offer users more choice in how they use their devices, beyond what Samsung chose to offer on their stock ROM. There are definitely many more opportunities for anyone willing to dive into the S-Pen SDK. What would you like to see as the next S-Pen utility app?
December 31, 2012 By: Joseph Hindy
Previously, we brought you news about the CSC file on the Galaxy Note. In a way, it is similar to the build.prop in that it can be used to enable and disable certain features and settings. As it turns out, there may be a way to enable the popular multi window feature on the Samsung Galaxy Note 10.1.
XDA Forum Member xperiacle began a thread with an idea that altering a certain part of the CSC file can allow multi window support for apps that don’t usually have it. This would mean that users can make a few simple CSC edits and have their apps work without any mods required. As xperiacle explains:
I came across a smali code fragment that checks for multiwindow supported apps in CSC file as well as excluded apps so I tried to investigate further and found out that you can actually add multiwindow support for almost any app by just adding it’s package name in feature.xml or other.xml in /system/csc folder.
Users have been trying this out and experimenting with similar alternatives. So far, the results have been mixed. However, a few have finally managed to get the ball rolling. It’s slow going, but a few have managed to get Dropbox working as a multi window app without altering the Dropbox APK itself.
To see more and stay apprised of the latest updates, please visit the original thread. Just make sure that once you start modifying your own CSC that you keep a backup in case something goes awry. In fact, it may be a good time to go about making a Nandroid of your /system partition for easy recovery.
The S-Pen is a pretty unique piece of hardware, especially on the latest generation of Note devices such as the Galaxy Note II and the Galaxy Note 10.1. However, the software for S-Pen is a little lacking. There are a number of fun drawing applications and other fun apps. However, there aren’t many killer S-Pen apps. Now, there is an image editing app optimized specifically for S-Pen.
XDA Forum Member lschiedel released a beta for an image editing application designed specifically around S-Pen functionality. As lschiedel explains:
Anyway, the app is a Photo Editor with paint tools, filter tools, and multiple floating layers including Image Layers, Text Layers, and Vector Layers.
The SPen support includes hover emulating moving the virtual mouse (a float brush icon that is see through when trimming layers) and uses the button on the pen to emulate left button/right button by click, letting you change from fore-ground color to back-ground color, as well as toggle between trimming layers by brush and untrimming layers by brush.
It supports large heap (meaning huge multi-mega-pixel images).
It has an image surface on the left, a toolbar on the top right, and a scroll pad/mouse pad on the bottom right.
It only needs some more icons and a little more debugging.
So for those who enjoy photography, image editing, and activities like these, this could be an extremely useful application. This is, of course, an open beta, so users will likely see some bugs here and there. Reporting them is generally helpful, so please report all you find.
December 8, 2012 By: Joseph Hindy
The Samsung Galaxy Note 2 multi-window feature started off lacking much functionality, but has since gotten rather useful. If you don’t know, multi-window allows Note II owners to use two applications simultaneously. The first app populates the top half of the screen, while the second populates the bottom half. Now, Galaxy Note 10.1 users can add multi-window functionality to any app.
XDA Forum Member Leppin released a tool for Windows that automatically adds everything needed. This is actually different from the other methods, which change system files so that any app can be used. While it may take longer, users don’t have to worry about messing up other system modifications to get the multi-window mod working for all apps.
The process is pretty simple. Users download the tool and grab the APK they want to modify off of their device. They then run the APK through the tool. Once done, they put it back, install it, and restore data. That application should be usable in multi-window after that. A nifty thing about this process is that users can create packs of apps that are multi-window compatible for future use in ROMs.
For more details, check out the original thread.
As XDA Member Advocate Admin egzthunder1 once said:
Quite possibly, one of the greatest advancements in the Android development world was the ability to run apps on external memory.
Of course, he was speaking about App2SD, which was released a really long time ago. It was only a matter of time before the now-famous script got itself an upgrade and now the next iteration of one of the greatest advancements in the Android development world has arrived.
Developed by XDA Senior Member TweakerL, the new script is called Super Apps2SD. It functions much like the original Apps2SD in that it installs the applications to your SD card to conserve internal storage. However, there is a reason why the word super was added to the title. There is a lot to like about it, but here are the headlines:
#1 Internal Storage remains mounted to the same exact location it was originally, meaning that backups go where they belong, you can still easily access your media by connecting the device to the PC. Bottom line, you have all space in the internal storage truly app free.
#2 No need to worry about backing up all your stuff and restoring after enabling app2sd. The script will move all relevant files to where they need to be so they don’t take any space in the internal storage.
#3 Once enabled, apps will be installed DIRECTLY into the external storage. What this means is that if you have an older device with say, only 512 MB internal storage, you can now install apps that you might have problems installing because they would have to go into internal storage before being moved to external
There is a whole bunch of awesome emanating from this new script. Older phones can now download newer games that have storage footprints larger than the device can handle. With the applications being installed directly to the SD card—and only the SD card—it fixes a lot of issues many users had with the original App2SD scripts. There are even some future features planned, such as the ability to revert to the original internal storage option and move all the apps back.
If you’re a regular Apps2SD user, this is definitely something to check out. Even though it was released in the Samsung Galaxy Note 10.1 forums, it should be compatible with a large number of devices.
To learn more, check out the original thread.
September 9, 2012 By: Joseph Hindy
We frequently bring you news about devices receiving unofficial updates to Jelly Bean. It is happy news, as it means the devs here at XDA are hard at work to bring the latest version of Android to the masses. That said, it’s always nice when OEMs release official Android version updates. Even if it has to be distributed by someone other than the OEM.
The latest device to get an official update leak is the Samsung Galaxy Note 10.1. Samsung will probably be updating their newest flagship tablet to Jelly Bean very soon as leaks are often a precursor to official updates. It should be mentioned that this update is for the N8000 version of the Galaxy Note 10.1 only. Flashing it on any other version of the Galaxy Note 10.1 is not recommended. So for those who don’t own a N8000 version of the Note 10.1, you’re likely better off waiting for a developer to make a ROM that is compatible with yours or until Samsung rolls out an OTA for your particular version.
A few weeks ago, we announced the creation of the Galaxy Note 10.1 forums. One day later, we announced ClockworkMod had been unofficially ported to the Note 10.1. We can now also announce that the first custom ROMs for the device have made an appearance. At the time of writing, there are 3 custom ROMs currently available in the forums.
XDA Senior Member zedomax brings us HighOnAndroid “TrainWreck” ROM. Based on European XXALG5 firmware, the intention of the ROM is to maintain a stock look. It keeps TouchWiz intact in order to maintain all stock features, such as S-Pen functionality.
Next up, XDA Senior Member safariking has released CleanRom. This ROM is also based on XXALG5 Firmware, but the devs intention is to remove as much of the Samsung Apps and bloatware as possible, in order to maintain a “clean ROM”.
Finally, XDA Member hani1980 has given us DR.AKRIM_ROM. This ROM is based on Indian N8000DDALH1 firmware. The dev has included full RTL Arabic support and Samsung Arabic keyboard.
All three ROMs contain the standard tweaks such as being Deodexed and Zipaligned, as well as each having their own unique tweaks by the individual devs. If you want some custom ROM goodness on your Glalaxy Note 10.1, head over to one of the threads:
The Samsung Galaxy Note 10.1 is moving right along. Just a few days ago, we gave the Note 10.1 its own forum space and the newest Samsung tablet has also been rooted. The only thing left was getting a custom recovery so users could start flashing the ROMs and kernels that the devs pump out. Now, they have that too.
XDA Senior Member zedomax, who’s also responsible for releasing the root tutorial, has brought an unofficial ClockworkMod Recovery Touch 126.96.36.199 for people to use until an official version can be brought to ROM manager. For installation, users simply need to flash it via Odin or Heimdall. Zedomax has also been kind enough to include the stock recovery, which users can flash to if they need to or just want to get an OTA update.
So far, reports are that the recovery works just fine. The only issue reported is that the touch is a little off when scrolling. Therefore, it is recommended to use the volume keys for scrolling for the time being to avoid accidental menu selections. Otherwise, it works as it should. Now users can flash whatever they need to and, more importantly, make those ever useful Nandroid backups.
To get it, head over to the original thread.