yashsingh1/xdaforums huggingface dataset:
[Huawei Ascend Mate 2] p51d007:
I see a 5.1.01 or something coming soon...
[Sprint Samsung Galaxy S6] aaronfrickinaustin:
Is it possible as of yet to install Xposed on 5.1 with the S6?

I have root, but the last time I tried to install TWRP and Xposed, I bricked my phone :c

Fortunately, I got it replaced
[Sprint Samsung Galaxy S6] koop1955:
Not at this time. No Xposed.
[Xperia Z4/Z3+ Q&A, Help & Troubleshooting] nansensical:
Hey guys. My first review here but I think this really need to be addressed.

On my Z2, music was great till I had a note 4, root it and installed viper4android. So I managed to root my Z2 and install fauxsound and sold of my note 4 just cause it made the volume louder and its easy to drive my senheisser.

Then I got the Z3 and managed to install viper4android just to make it enough gain to drive my sennheiser. Sound was nearly perfect.

However, Z3+ seems has louder volume output then its predecessors. Is it my ears or is it louder now?

Still waiting for root just to install viper4android. Have a spare S6 Edge and with viper4android installed, I still think S6 Edge sound output is superior.

What do you guys think?
[Xperia Z4/Z3+ Q&A, Help & Troubleshooting] hasona:
The whole sound output on the Z3+ is refined as seen here. There are some real nice additions in the Z3+ compared to earlier models. I hear a difference on my Z2,Z3+ but no idea how it was on Z3
[Xperia Z4/Z3+ Q&A, Help & Troubleshooting] asking:
Biggest change is what i feel from my old Z2 is Size.... Z3+ is really... comfortable to handle with such impressive design. also there are 35 Sensors while in Z2 it was 18 Sensors...i don't know more sensor is good or bad...
[Xperia Z4/Z3+ Q&A, Help & Troubleshooting] AlvinZahran98:
What sensors are those?
[Xperia Z4/Z3+ Q&A, Help & Troubleshooting] asking:
Obviously basic sensors like gyroscope,magnetometer,pressure sensor,etc. Z cpu shows 35 sensor count. Lol i think this phone is having highest no. Of peripherals installed.
[Moto X Q&A] fishline:
I recently got a xt1053 with Lollipop 5.1. One thing that I found different from my previous xt1058 on 4.4.4 is this: I set the bluetooth connection to my car to use for "phone audio" but not "media audio", because I listen to the radio or my ipod in the car, but need the phone for calls and navigation (and when I use nagivation I want the instructions to come from the phone instead of the car through BT). With the xt1058/4.4.4, it worked beautifully. However, with the xt1053/5.1, when I use Moto Voice to give command, the initial reply from xt1053 always comes through BT instead of the phone's loudspeaker. If I was listening to FM, that won't come through at all (which was the reason I set the bluetooth to be use for phone only). After that initial response, the rest comes from the phone itself. As an example, if I ask what's the weather, the audio will only come from the phone after google now launched. Has anyone noticed this? Looks like a bug to me...
[G3 Q&A, Help & Troubleshooting] JPHamlett:
Anybody having issues with OK Google constantly "listening" but only when playing music with headphones on?

I will play music through headphones and every 30 seconds or so OK Google, will cut my music off and listen for a command. I had to freeze the Google app in order for it to stop.

I know the issue only occurs in 5.1.1 because when I flash other stock roms, the issue goes away.

Thanks
[Android Q&A, Help & Troubleshooting] jayddie51:
hey guys

can anyone please tell me or guide me how and what custom rom should i use with my o+8.93?

thanks! :fingers-crossed:
[Android Q&A, Help & Troubleshooting] joshua07111496:
same problem with you

i have the same phone also (0+ 8.93) and i expend many data surfing to google,watching videos but i came up empty.I hope they make us a custom rom for our phone because its very disgusting because of lags
[Galaxy S 5 Q&A, Help & Troubleshooting] phillytemptation:
Hey all,

I just got an s5 active, and I'm currently coming from lg g2 running crdroid. I'm about to downgrade to NE4/root/safestrap in a little bit, but I was just curious what roms folks are using as their daily driver? would love to get some suggestions to get up and running asap. Also, do any of these roms support the active button?
[P3300, MDA Compact III General] swisher:
Hi!

i'm really disappointed! Today i got the HTC W100 Remote Control. I tought, now i can take my Orbit in my bag and control my MP3 Player with the shortcuts of the W100!

BUT

The W100 has a big disadvantage!

it seems just to be compatible with the WMP! But this player isn't really comfortable if you take your Orbit in a bag, because the Touchscreen is alway on!

Mortplayer (a really good MP3-Player) doesn't recognize the shortcuts of the W100. So you can't use the shortcuts of the W100 for any funktion for the Mortplayer. If you push any button of the W100, the WMP starts automaticly.

Is there any solution:

- to lock the screen of the WMP very easy

or

- to use thr W100 for the MortPlayer or any other Musikplayer, that has a simple Sceen-Lock funktion!?

Greeds

Swisher
[P3300, MDA Compact III General] luxmen:
Hi,

Hi,

Pocket Music don't work too....

HTC Audio manager don't wotk too...

Can good guy find a solution (reg edit ??) for change that...
[P3300, MDA Compact III General] Dlaf42:
i just got the HTC W100 Remote Control and i can use wmp and htc audio player fine....when i press play on the remote it opens htc player then i just press play again to start music. the thing is i want it to open wmp not htc one, does anyone have any clues how to make wmp the default player not htc one.
[P3300, MDA Compact III General] hays:
Goto WMP - Options - Buttons - define a key for toggle screen

allows you to switch of the screen but keep WMP working

I've no idea how this works with ur W100
[P3300, MDA Compact III General] dcbehan:
I couldn't find anything in the registry that allowed you to change the default player. I suspect the references are hard coded into the dll. Sent mine back after two days of screwing with it to no avail.

db
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Andmoreagain:
valexKernel

For SM-P600, AOSP/CM13-based 6.x ROMs ONLY!​

Disclaimer: This kernel is for use with AOSP/CM13-based ROMs only and will not work on stock ROMs. If your device bricks, breaks or explodes as a result from flashing this kernel I am not to be held accountable for it. Flash this at your own risk.

About: This kernel focuses mainly on backports and improvements from more recent versions of Linux. As of now, major updates have been made to the scheduler, SMP, hotplug, memory management, random, the user namespace, and the ARM architecture in general. Compiled with Cortex-A15 optimized GCC 4.9.4. For full changelog, see my git repository here: https://bitbucket.org/sigma-1/valex_kernel_mm/commits/branch/valex_master

Features: My kernel contains no "gimmicky" features other than the ones that are already present in the CM13 kernel base for our device which includes voltage control, haptic intensity control and AndreiLux's sound control feature to mention a few. Again, my kernel focuses mainly on updates and backports from mainline so it can be said that those are its main features.

Known bugs: None so far. If you are encountering freezes and reboots with the S-Pen, audio crackling or lags then try this fix: http://xdaforums.com/galaxy-note-10-2014/development/lt03wifi-temaseks-unofficial-build-t2980604/post65631142. If you encounter any bugs that you think may be kernel-related, please report them here along with logcat or dmesg.

Other issues: While it can't be said that this kernel should be considered "stable" that does not mean that it is necessarily "unstable" either. Some of the backports are experimental at best so if you run into any new issues please report them here along with a dmesg log or a logcat.

Support: Currently this kernel only supports the SM-P600. Support for the P601 will be added soon.

Licence: The Linux kernel is licenced under the GNU General Public Licence v2. What this means is that if you want to develop a custom kernel using mine (or anyone else's for that matter) as your base then you are free to do so without asking for my permission. That is the nature of the Linux kernel so go nuts.

Installation: Just flash the zip in recovery and reboot. The installation procedure does not replace your current boot.img but rather just decompresses it to swap out the kernel binary (zimage) itself. This should make it compatible across different CM13-based ROMs for the SM-P600.

Download the latest build here:

valexKernel MM v1.00 https://drive.google.com/open?id=0B7Ui4IHpV48JMXNsMV96T1ZuLWc

XDA:DevDB Information

valexKernel, Kernel for the Samsung Galaxy Note 10.1 (2014 Edition)

Contributors

Andmoreagain, RaymanFX

Source Code: https://bitbucket.org/sigma-1/valex_kernel_mm

Kernel Special Features:

Version Information

Status: Beta

Current Beta Version: 1.0

Created 2015-07-10

Last Updated 2015-07-11
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Andmoreagain:
Manual cherry-picking: If you are cherry-picking from my tree and a patch needs to be manually applied for whatever reason, I find it preferable to amend the original author to the commit in order to avoid confusion in regard to authorship. This is done using the following command before pushing the commit:

git commit --amend --author="Author Name <author@email.com>"

The commit editing screen should now pop up, where at the bottom you may then add:

Signed-off-by: Your Name <your@email.com>

This helps keeping track of the patch's original authorship along with any modifications made to the patch. While this is not strictly a mandatory rule, I would prefer that anyone who wishes to utilize my backports in the future would follow this procedure.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Orion116:
Mind if I include some of this in my feature rich kernel[emoji6]
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Andmoreagain:
Do it! :good:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Orion116:
Cannot wait to see the result :)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Andmoreagain:
Bump!

v2.0 release candidates have been added. Both tested and running good so far. RC2 is a bit more bleeding-edge since it contains some more preparatory backports for MCPM integration. I uploaded RC1 too in case anyone runs into a bug and wishes to fall back to a more stable version. See changelog for more info on both RCs. Enjoy!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirkStorck:
Hi. Do you plan to add other govenors ?

Thank you!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] buhohitr:
So what is the different between this kernel and stock? better battery life? performance? both? I'm looking for the main shine feature of this kernel.. :))
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Andmoreagain:
Performance is significantly better compared to stock as both the scheduler and SMP/hotplug functionality have been updated and improved. At first this came at the cost of power consumption but as of the latest updates this seems to be fixed. A lot of the updates included are also preparatory patches for HMP support.

It is not my main focus at the moment but I haven't really made a final decision in that regard.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirkStorck:
Ok, I understand. I am only asking because with another kernel I have used "weathley" and had a good balance between speed and battery! :)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Orion116:
Governors is my job once I rebase BrokenNote kernel to use this as the base.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Andmoreagain:
Cool! I personally don't have any particular interest in custom governors so this sounds like a good solution for those who want more customizable options. :)

But anyway...

I added SCHED_HMP to see if the scheduler was ready for it. Two additional commits and one revert later, that turned out to be the case indeed.

I won't be adding it in to my distribution here until I've made sure everything else is in good shape. MCPM still needs to be pulled in. RaymanFX has it partially backported, but like I've said before I have no idea whether it will actually work with the current CCI implementation. I wonder if it would be possible to support the upstream CCI driver by parsing a minimal FDT to the kernel at boot, something like:

/ {
compatible = "samsung,exynos5420", "samsung,exynos5";

cpus {
#address-cells = <1>;
#size-cells = <0>;

cpu0: cpu@0 {
device_type = "cpu";
compatible = "arm,cortex-a15";
reg = <0x0>;
clock-frequency = <1800000000>;
cci-control-port = <&cci_control1>;
};

cpu1: cpu@1 {
device_type = "cpu";
compatible = "arm,cortex-a15";
reg = <0x1>;
clock-frequency = <1800000000>;
cci-control-port = <&cci_control1>;
};

cpu2: cpu@2 {
device_type = "cpu";
compatible = "arm,cortex-a15";
reg = <0x2>;
clock-frequency = <1800000000>;
cci-control-port = <&cci_control1>;
};

cpu3: cpu@3 {
device_type = "cpu";
compatible = "arm,cortex-a15";
reg = <0x3>;
clock-frequency = <1800000000>;
cci-control-port = <&cci_control1>;
};

cpu4: cpu@100 {
device_type = "cpu";
compatible = "arm,cortex-a7";
reg = <0x100>;
clock-frequency = <1000000000>;
cci-control-port = <&cci_control0>;
};

cpu5: cpu@101 {
device_type = "cpu";
compatible = "arm,cortex-a7";
reg = <0x101>;
clock-frequency = <1000000000>;
cci-control-port = <&cci_control0>;
};

cpu6: cpu@102 {
device_type = "cpu";
compatible = "arm,cortex-a7";
reg = <0x102>;
clock-frequency = <1000000000>;
cci-control-port = <&cci_control0>;
};

cpu7: cpu@103 {
device_type = "cpu";
compatible = "arm,cortex-a7";
reg = <0x103>;
clock-frequency = <1000000000>;
cci-control-port = <&cci_control0>;
};
};

cci: cci@10d20000 {
compatible = "arm,cci-400";
#address-cells = <1>;
#size-cells = <1>;
reg = <0x10d20000 0x1000>;
ranges = <0x0 0x10d20000 0x6000>;

cci_control0: slave-if@4000 {
compatible = "arm,cci-400-ctrl-if";
interface-type = "ace";
reg = <0x4000 0x1000>;
};
cci_control1: slave-if@5000 {
compatible = "arm,cci-400-ctrl-if";
interface-type = "ace";
reg = <0x5000 0x1000>;
};
};
};
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Andmoreagain:
New build is up. It's far from being stable, but I have removed the stock big.LITTLE switcher and replaced it with the upstream version along with multi-cluster PM (MCPM). These are the main prerequisites for HMP/true octa support. It boots, it runs, but it has a few hiccups as well.

In light of this latest testing build, I thought I'd share this clip. It's an interesting interview with Nicolas Pitre who developed the big.LITTLE switcher, and did it blindly in a very literal sense. ;)

[YOUTUBE]_NchUg4401I[/YOUTUBE]​
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Orion116:
Very cool. Once I get my device files straight back out and have time I am going to rebase my kernel. I am just very short on time, lol.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Stevethegreat:
It's both sad and impressive that the community does what Samsung does not for her own devices.

Good luck good sir! A proper hmp implementation also helps with battery life which -I believe- is much needed for our device (no more big core switching for the simplest things)...
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Andmoreagain:
This is just the nature of the Linux Kernel. Samsung have done an excellent job at maintaining and developing the Exynos platform in mainline and even the max77802 PMIC got supported not too long ago. The rest is up to the community. The fact that our stock kernel is stuck at 3.4 is just as much Google's fault as it is Samsung's due to them relying on LTS releases instead of following Linus Torvalds' motto: "release early, release often".
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Stevethegreat:
Yeah but Galaxy Notes are Samsung's flagships and most expensive devices. One can see why they can't support every last of their devices, I can't see why they don't do it for many of their most expensive devices neither. iPad 2 , a 4 and a half year old device which was cheaper at its release time than this Note, is still getting updates (it's going to get ios9!).

I know that the nature of Linux's mainline is to be often developed by the community, but Samsung could at least offer great documentation, update drivers, etc ... I think we paid that much (for it). "If you can't develop for your expensive devices anymore, at least make it easy for your community to do so". That's my understanding, at least when expensive hardware is involved in the equation...
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Orion116:
How long does your tablet usually take to boot after flashing the kernel?

---------- Post added at 05:31 AM ---------- Previous post was at 05:28 AM ----------

I want to know so I can get a log in the morning.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Andmoreagain:
v2 RC2: About 4 minutes in total if we count "Optimizing apps" as part of the boot process. Up until that part it takes slightly over a minute.

MCPM build: Got a freeze/kernel panic during the boot animation now. I suspect it was due to a root app having been updated before I flashed the kernel and it was requesting to be granted root access again. I've seen this pattern before with some of my unstable kernels. Last time I tested it though it took slightly longer to boot than RC2.

I totally agree. It's not exactly a smart move to release a kernel source without a slightest hint of documentation. At least if they'd provide a changelog of patches applied on top of the 3.4 base then it would be easier to track down the actual patches. The truth is that some of the patches they rely on are early and incomplete revisions, while others are custom hacks plain and simple.

One good example is the max77803 driver. The P600 uses it a bit differently than other devices so what they did was modifying the max77888 driver to be used as a secondary driver for the max77803, just so that it could be handled "correctly" on the P600. Sure, there are instances of combined drivers for the Maxim PMICs such as the 77686/802 driver but that's actually the opposite of what Sammy did. Instead of making the actual driver smarter they just duplicated it. I'm starting to think that one of the reasons why Samsung don't want to provide documentation with their kernels is because of instances like this one: bloat, poor coding and lazy hacks.

Thought I'd also say that I made some progress with my other kernel tree (Linaro Stable Kernel - Linux v3.13) yesterday. It now supports the max77802 pmic and I've just begun pulling in the base which I will use for porting over the max77803 drivers. Everything compiles so far. Also, I've decided to just hire someone to port over the LCD driver as soon as I can afford it. So far it's the only driver that's an actual hindrance since it can't be found in any of Samsung's 3.10 kernel trees and I haven't been able to find any similar drivers either. If all turns out well, then maybe Sammy could be convinced to push it into mainline lol.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Orion116:
What ROM do you test your kernel on?

I waited 10 minutes for the tablet to boot. I used thishttps://play.google.com/store/apps/details?id=eu.chainfire.liveboot to get a log. I notice as it booted there were a bunch of errors. I will upload the log for you.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Andmoreagain:
Thanks I'll have a look at it as soon as I can. If there turn out to be some critical errors I'll throw together a debug build to get a more detailed log.

I'm using Temasek CM12.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Orion116:
Thanks man. Do you use hangouts? It maybe easier to troubleshoot that way.

I will also experiment with building it inline with BrokenOS. Then adding features to it.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Andmoreagain:
I've never used hangouts but I think that might be a good idea. I'll have to do it after the weekend though since I'm out of town with some very poor connection.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Orion116:
No problem. It just makes communicating easier?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Orion116:
Log https://drive.google.com/file/d/0B6DsKZjOgEFRZ0h6WHEya0xuSk0/view?usp=docslist_api
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
I thought you're not able to use custom kernels on the temasek builds?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Andmoreagain:
Where did you read that nonsense? :eek:

I took a log using chainfire's app as well but made it only show the kernel dmesg log plus logcat errors. The actual errors seem mostly to be coming from android's side and not the kernel, and none of them seemed to be critical ones. I'll test it with BrokenOS as well when I have time and see what I can find. :)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
I got the idea from here: http://xdaforums.com/galaxy-note-10...fi-temaseks-unofficial-build-t2980604/page115

Here: http://xdaforums.com/galaxy-note-10...fi-temaseks-unofficial-build-t2980604/page121

And here: http://xdaforums.com/galaxy-note-10-2014/development/kernel-brokennote-insanity-t3143785/page6
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Orion116:
Yeah custom kernels bootloop on every ROM but the one they are compiled for it seems. I can try letting the tablet sit for an hour and see if it boots. I will also try building it inline with BrokenOS for some reason custom kernels seem to bootloop on certain Roms.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Andmoreagain:
There was also an issue with RaymanFX's kernel source some time ago that has since then been fixed. I remember trying to build it while it was still broken and it just wouldn't boot no matter what. After syncing with RaymanFX a few weeks later everything was fine again and I've been able to boot my kernels without an issue.

This temporary issue in the kernel was also causing joshndroid's temasek builds to bootloop before someone pointed out to him that he just had to sync his kernel source with RaymanFX if I remember correctly.

It actually seems quite ridiculous that installing a new kernel should cause bootloops unless the kernel itself was broken somehow. Also, I use Philz recovery since it doesn't seem to suffer the same issues as TWRP. Maybe that helps...

Edit:

In any case there is something fishy about these bootloops because I haven't been experiencing this issue. I think it might be a good idea to get to the bottom of this.

My setup:

Base source: Latest RaymanFX tree

- Compiled outside of any particular ROM source

Toolchain: Cortex-A15 optimized Linaro GCC 4.9.3

Rootfs: Prebuilt CM12.1 boot.img - I use ArchiKitchen to unpack/repack

- I have also enabled support for all decompression methods in the kernel config which may or may not help.

Recovery: Philz Touch, because it has never failed me unlike TWRP which tends to mess things up :S

I'll install BrokenOS today and see if I get these same strange results. I find it very unlikely that the kernel itself is the issue here. I think it's more likely that the issue may be differences in the ramdisks, which could be resolved by packing several different ramdisks within the boot.img and tell it to decompress them according to the build.prop information.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Orion116:
BrokenNote kernel is using the latest raymanFX updates and it bootloops on temasek.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] RodrigoLemos:
Works on P601 ?