yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ General] ieatabiscuit:
Here's what I got so far: when changing between land scape, and portrait there is some graphical distortion, and a touch of lag which clears up after about a second. There is no advanced reboot option, and when I sure down, it reboots instead. When multitasking, there is a general UI lag which clears up spoon after., and it does not save WiFi information so you have to reenter WiFi information after every boot. So far, aside from slims slimming causing a desire for menu options, and theming, this is all I found.
[Nook HD, HD+ General] DarkWolffe:
Is this in continued development?
[Nook HD, HD+ General] Jon Lee:
No, unless someone wants to take over. Basically it was an experiment for me to see if graphics in lollipop could match that of cm10(.2). In short the answer is they can't... (without a ducati upgrade).

The other reasons are twofold. First, the lollipop browser completely sucks (I know, there's alternatives).

Lastly, I don't believe I would ever achieve the level of performance as I have with my yellow kernel 10.2 ROM (which is my daily driver), this again is related to the ducati.

I would like to take another stab at a kitkat ROM and see if I can incorporate some of the stuff I have picked up recently.

I would have updated liquidsmooth, but they have already pulled kitkat source. So I am debating which ROM repo to use (I'm thinking probably Carbon 4.4? Tabletui is important to me...)
[Nook HD, HD+ General] neonleon29:
Hey Jon, I'm excited to hear you might be building a Kit Kat ROM. Would like to try one that has your improvements such as no screen flicker and still be able to use screen casting. Looking forward to your build.
[EVO 4G General] swagstr:
So, I haven't updated my ROM in like a million years and I'm not making any promises. But my life schedule just got a sh*t ton easier. Wondering how many people still use the EVO or would want a final version of SOS?

Thoughts below...
[Galaxy S 5 General] mateorod:
Seeking: An experienced flasher who is willing to test a CM-11.0 klteusc build on an S5.

I am helping a colleague who creates custom ROMs. We are investigating a crash in the latest

cm-11.0 for the S5. This is just a vanilla build of the stable/cm-11.0-XNG3C tag. But I don't have

a device to test with. If this boots than I know that we can safely base the image off that tag.

Would anyone be willing to flash the ROM and see if it boots? Bonus points if you are able to

submit a logcat if it crashes :cool:

Obligatory warning

: I haven't tested this build. But it is just vanilla CM11. It may boot loop

but you should be able to boot right back into recovery and flash your old rom. I don't own

a Samsung device so I cannot walk an inexperienced person through any of this. If you are

a nightly flasher I would appreciate a quick test.

Link: https://drive.google.com/file/d/0B9AtPXmoEFUzSE0tcXdYSXU1dmM/view?usp=sharing

ETA: Builds from this same source ARE booting for OnePlusOne and a handful of Nexus devices. I just need

confirmation that it works or does not work on the S5 in particular.
[Galaxy S 5 General] mateorod:
Okay, well no one here ever responded but I found someone on Twitter to help.

It boots and runs fine, if anyone is curious.
[Android General] DonaldDuck_99:
Hey!

I am running into a issue here and need some outside thinking as it's driving me insane...

I am porting Android on a new hardware, everything is fine except the audio over HDMI.

The cable is good, and is work under other OS like GNU/Linux...

It's seems to be a Permission error, I can see this in my dmesg:

init: sys_prop: permission denied uid:1000 name:audio.hdmi.available

So I am guessing it's a permission issue, I've try to put at 777 the /dev/hdmi

and all files in /dev/snd/*

Still same issue, added it in /init.rc and rebooted, still same permission denied issue...

What file it use and where do I set this permission?

Thanks, it's on Android 4.2.2 With Linux Kernel 3.4.39 on a A20 arm processor.
[T-Mobile Samsung Galaxy S6 Edge] krntehknik303:
Is it normal when the play store has you update your apps again after you rebooted? When I go into my apps it shows that there are new updates when I have already updated them. It has done it before when I first got the phone. Is that a glitch with the play store?

Side Note: after the 5.1.1 update my battery life tremendously dropped compared to 5.0.2. I updated through Smart Switch and did a factory reset. Is it worth my time to do it again been reading around and seems like it's because of the memory leak issue that lollipop has. Just wondering if it's worth the time to reset for a "temporary fix"
[Galaxy Note 4 Q&A, Help & Troubleshooting] simon330:
Hi All,

I am using the Note4 N910S (exynos), I cannot find any kernel or rom support for this model, can anyone know that?

Many Thanks!

Simon
[Xperia Z1 Compact Q&A, Help & Troubleshooting] starsmydestination:
Hello everyone, I searched around a bit but could not find an answer to this. I am currently on MetroPCS, does anyone know if there is a ROM out there that has TMobile or MetroPCS wifi calling built in?
[Verizon LG G2] reasonz20:
Hey guys what are your thoughts on this? The phone didn't drop or anything like that
[Verizon LG G2] hardball 45:
I've had the dead spot for about a year. It sucks. I just deal with it.

No ghost touches, though.
[Verizon LG G2] dockmaster:
I had touchscreen problems and got a new phone on insurance
[Verizon LG G2] neondunker:
Just replace the acreen is not that complicated, i replaced mine twice

Enviado desde mi VS980 4G mediante Tapatalk
[Verizon LG G2] compuser84:
Well at least I'm not the only one? neodunker, is there an online guide to replacing the screen that you used?
[Verizon LG G2] reasonz20:
Which method you used to root 5.0.2?
[8525, TyTN, MDA Vario II, JasJam General] Jumpie:
Active Sync can't either connect or when it does it fails after about 2 minutes. I can only connect via USB and can't with Bluetooth. I've set the phone up according to directions for BT but nothing.

I'm using....

ROM version 2.15.502.3

ROM date 04/09/07

Radio version 1.40.30.00
[8525, TyTN, MDA Vario II, JasJam General] singhnx:
Is activesync failing after two minutes for both bluetooth and usb or just for bluetooth?
[Galaxy Note Pro 12.2 Q&A, Help & Troubleshooting] Agrajag27:
I just flashed the latest CM12 and it's great. Also installed TWRP.

The only issue is that now when I boot my P900 shows in red: Kernel is not seandroid enforcing.

Is this a problem and, how do I get rid of it?
[Galaxy Note Pro 12.2 Q&A, Help & Troubleshooting] Sterist:
your bootloader detects that, so there is no way to get rid of it.

my note 4 does this but I have actually never seen it on my P900, could you give more details on your exact model, rom, and kernel? I'm curious.

one way around that, I think, would be a kernel that is enforcing at boot, then use a script or an app to toggle it back to permissive (if necessary for your purposes)

edit: oops I see now -- CM 12, but still.. are you using the lollipop bootloader from the official update?
[Galaxy Note Pro 12.2 Q&A, Help & Troubleshooting] shonkin:
Hmmm.... I just rooted my Note Pro last night, stock rom with TWRP (latest). And though it boots up fine otherwise, I'm also getting the "Not SEAndroid enforcing" message. Would like that gone. And it is interesting that CM12 is having the same issue, because I was beginning to think about flashing it and ditching stock Lollipop.

Specifics: I used Odin 3.10 from a Windows 7 laptop for my initial boot flash of the CF-Auto-Root-v1awifi-v1awifixx-smp900.tar.md5 file to the tablet. No errors were reported. I also flashed TWRP 2.8.7 that way. Again, no errors. There was a beta version of SuperSU (2.49) but I didn't install that. Think I'll try it next... and hope for the best. I did install SuperSU Pro (2.46) once I'd booted the tablet, but maybe that's not available on boot?
[Galaxy Note Pro 12.2 Q&A, Help & Troubleshooting] Agrajag27:
SM-P900 like you.

CyanogenMod Version: 12.1-20150707-UNOFFICIAL-v1awifi

Android version 5.1.1

Kernel version: 3.4.104-g7e89e2e

fox@fox-ubuntu #1

Tue Jul 7 19:20:11 MSK 2015
[Galaxy Note Pro 12.2 Q&A, Help & Troubleshooting] Sterist:
but did you at some point OTA or odin to Samsung lollipop before CM12.1?
[Galaxy Note Pro 12.2 Q&A, Help & Troubleshooting] Agrajag27:
Yes. I OTA 5.0.2.

I guess the big questions are:

1. Is there a fix that doesn't involve jumping back to KitKat?

2. Is having this issue in any way bad other than seeing that message on boot as everything else seems to be working.
[Galaxy Note Pro 12.2 Q&A, Help & Troubleshooting] Sterist:
I don't think there would be a way to go back to kitkat, even if you wanted to, after having installed the lollipop bootloader (happens when you OTA or Odin to stock lollipop)

to the user it's no problem at all -- it's just a visual notification to stores when you take the device back that it's been customized / modded, and voids the knox warrantee hence "Set warrantee bit: kernel"

knox, despite popular belief, is just a form of security and productive software for corporations to rely on when giving their employees a "work phone" to use, so they know that any potentially sensitive corporate information is safe from the security risks of rooting (though virtually never exploited, rest assured)

that's the most relevant answer I can give you, without repeating what I explained in my previous post *hint* lol
[Galaxy Note Pro 12.2 Q&A, Help & Troubleshooting] Agrajag27:
Slightly confused about something I'm seeing. The error is that it's NOT enforcing, but Settings, About Tablet says it IS enforcing.

Also, you mention setting to Permissive with an app (which I've found) but that sounds like it won't be enforcing either and thus we'll still have the message.
[Galaxy Note Pro 12.2 Q&A, Help & Troubleshooting] Sterist:
the display at boot is not an error, just a notification of sorts.

the only thing I can think of is the CM maintainer may have compiled the kernel to boot as permissive and switch back via script for compatibility.

I have seen some roms that do this. not many, nor recently. I wouldn't worry about it though, especially since it's a Wi-Fi device that doesn't have any reason to visit a carrier store.

also note that the notification will show when booting a permissive recovery kernel -- these notifications are not permanent nor need to be "cleared" or "reset" they just inform the user (or technician) of the S.E.A. mode of the respective kernel at the time of boot.
[Galaxy Note Pro 12.2 Q&A, Help & Troubleshooting] Agrajag27:
Thanks. I can live with that. I'm a bit OCD and an old QA professional so it'll give me pause every time I reboot and see it, but I'll get over it. <grin>

Otherwise, I have to say, the tablet is working better than EVER with CM 12.x. Apps that caused crashes no longer do. Bluetooth keyboard works again. It's faster. I have only a single bug (the running apps list sometimes has graphic issues).
[Verizon Motorola Droid Turbo General] Kiwironic:
Ok, I love my Moto Maxx. I knew I will get limited support, limited developers support, even compared to its less capable cousin Moto X. But I didn't expect this much suffering.

People are trying to unlock bootloader, update, root, and months after months of struggles and hard work from our beloved contributing developers.

For the US Verizon customers, it was the bootload and root, then after months of trying they got it and it was the update they were promised by the end of 2014 which just arrived, then the cycle starts over.

For us, the international Moto Maxx users, we gambled big, the phone is only known in a few countries with no real developer support but it was (as I said before) a SuperPhone. Unlocking bootload and rooting for us wasn't that hard, but here we are waiting and waiting for the lollipop update (I'm still on 4.4.4) and for the work corporate apps I am using I cannot root or use CM sadly.

I hereby declare the Droid franchise developer and power users unfriendly. I would like to extend this to any phone that is not worldwide mainstream. I will think a million times before doing this to myself again, despite the battery and superior user experience.

My company offered to buy me an iphone 6 (lol) or a Samsung galaxy s6 or s6 edge and I said no and jumped through hoops to get approval to use my Moto Maxx. I regret this completely. The first chance I will get, I will revisit this, I might get lucky and get them to get me the new international version of Moto X 2015.

So yes, this is an open letter to Motorola and Verizon. This is a whiny complainy angry thread and you can all express your feelings about this here.

I am keeping an open mind and still giving Motorola another chance. After all they have tried hard to look at our user experience pain points and provide good solutions for it.

So I hope I have learned my lesson. I hope I don't fall for this trap again. Even if this means I lose touchless controls, assist, twist to camera and active display which became part of my daily routine.

What do you guys think? am I over reacting?
[Verizon Motorola Droid Turbo General] Cobra04:
Every variant of this phone can be updated to Lollipop. Seems like your problem is your employer since the Maxx has an unlockable bootloader and CyanogenMod. Yeah the support for these devices has been horrible but oh well.
[Verizon Motorola Droid Turbo General] Kiwironic:
I would have considered CM if it had support for touchless controls, assist, twist to camera and active display. These are important to me, and some of the reason I went for the Moto Maxx. What you are saying is, I should give up most of the features I got this phone for just to get lollipop??? How convenient is that?

Motorola nor Verizon have anything to do with CM, my pain points are not coming from CM but from Motorola.
[Verizon Motorola Droid Turbo General] adrynalyne:
You can't really call yourself a power user and gloss over the fact you could have flashed Lollipop many months ago. It doesn't even have to be CM.
[Verizon Motorola Droid Turbo General] fedecape:
I don't get why your phone is still on 4.4.4. I'm running stock 5.0.2 with all the features that you like
[Verizon Motorola Droid Turbo General] JasonJoel:
Yawn.
[Verizon Motorola Droid Turbo General] richii0207:
I'm not sure why this is a surprise. The DX, released 5 years ago, and the next generations are on the same boat.

IMO, rooting and custom ROMs is not the same as it used to be as Android has taken so many steps forward.
[Verizon Motorola Droid Turbo General] ChazzMatt:
Moto MAXX XT1225 got stock Lollipop back in March, soon after Moto Turbo XT1225 (same device, same FCC ID) launched with Lollipop in India. 5.0.2.

I ran stock 5.0.2 for months on my Puerto Rico Moto Maxx, and on my Mexico Moto Maxx.

It was the Droid Turbo XT1254 stuck on 4.4.4, not the XT1225. ;)

The stock 5.0.2 files are in the development section, if you want to flash them. For Brazil, Mexico and India.

http://xdaforums.com/showthread.php?t=3063470

Claro in Puerto Rico (and I think Chile, also) had a falling out with Motorola, so the Puerto Rico/Chile Moto Maxx never got an official OTA to 5.0.2. But if you have Puerto Rico XT1225, you just flash your phone to another country and get 5.0.2. Or flash the 5.0.2 image of your choice (Brazil, Mexico, India).

______

Stock 5.1 is coming for the XT1225, but custom ROM 5.1.1 has been here for months. There's two custom 5.1.1 ROMs available -- one is AOSP, not CM based. So development support is here.

AOSP:

http://xdaforums.com/showthread.php?t=3108708

CM 12.1:

http://xdaforums.com/showthread.php?t=3060089

We also have cool boot logos and animations like these:

BOOT ANIMATION

http://xdaforums.com/showthread.php?t=3141711

BOOT LOGO

http://xdaforums.com/showthread.php?t=3065141

(Many more, just an example of each.)

_____

However, you say you can't run custom ROM, that you have to stay stock. Therefore, why have you not flashed stock 5.0.2 which has been available for the XT1225 since March?
[Verizon Motorola Droid Turbo General] Semseddin:
I care less about CM for Quark but i am surprised to see that nobody released a stock based rom for our phones yet.
[Verizon Motorola Droid Turbo General] ChazzMatt:
There's an AOSP one. I know, not exactly the same as "stock". But we do have two completely different custom 5.1.1 ROMs.

You can also run stock 5.0.2, root and run xposed/Gravity Box and get as few or as many custom ROM features you want... While remaining on stock.
[Verizon Motorola Droid Turbo General] Semseddin:
I would be very fine if someone provided us a custom rom based on stock brazil build of maxx, just something like computerfreak provided to Turbo users. It is funny that what i wanted for my phone is already available for the bootloader locked variant and missing from our bootloader free variant. This very well explains the popularity of the device within people is the key to its development potencial.

edit : even opened a request thread for it but nobody gave a f. , even our maxx users, leave alone the uninterested developers. :)

i think we should collect 450$ and buy juacos's maxx to a developer who would be happily developing good stuff for us.
[Verizon Motorola Droid Turbo General] Jaocagomez:
i totally agree, last year i got the droid maxx and it had little development but i thought that the moto maxx being released worldwide would have a lot of support, i really love motorola, but i dont like this, its like having a lamborgini that only you can drive, theres no much development, i regret trading my oneplus one, it even had better battery than my moto maxx, and worse camera but under same usage my battery lasted more than moto maxx and the speakers were louder, this year i think i will buy a moto x or the new oneplus two, its real sad to write this but its the truth. no more moto maxx or droid maxx for me.
[Verizon Motorola Droid Turbo General] Kiwironic:
So I change to Mexican rom to be able to get 5.0.2 and then what? I don't force upgrades unless I see a clear upgrade path. If then Motorola releases an 5.1 OTA upgrade from 4.4.4 for PR and not Mexico, then I am screwed. I don't take the downgrading risk.

Being a power user doesn't mean I go foolishly and pick the only upgrade path and not worry about the future. I don't gamble with my devices.

Anyway, yesterday Motorola has announced 5.0.2 for PR among many other versions. I will post the updates in this thread

International Moto Maxx 5.1 official update (Non Droid Turbo)
[Verizon Motorola Droid Turbo General] adrynalyne:
Power users and developers absolutely gamble with their devices. What it really comes down to is not about being power user nor developer friendly, but instead you want frequent and fast updates. The only device that will give you that is a Nexus and at this time you can have that on Verizon too.

Your stance defies everything an unlocked bootloader stands for.
[Verizon Motorola Droid Turbo General] ChazzMatt:
As Mexico, Brazil and India factory unlocked phones got 5.0.2 first, I imagine they will get 5.1 first.

Under no scenario does Claro Puerto Rico phones get 5.1 and factory unlocked XT1225 (Mexico, Brazil, India) does not.

You say Motorola has just announced 5.0.2 for Puerto Rico Claro. Well, this is mid July. Factory unlocked has had it since March, and will soon get 5.1 stock.

You sound a little silly saying if you flash the XT1225 to another country image or another Android version, you can't flash back if you want. Many people have flashed to 5.0.2 to custom ROM 5.1 and back to 4.4.4 on the XT 1225. One guy -- [MENTION=5212967]Fulbring[/MENTION] -- said he's done it at least 5 times... See this post:

http://xdaforums.com/showthread.php?p=61498706

Many flashed to India, then to Brazil, then to Mexico to see difference (if any) in performance. You can also downgrade back to 4.4.4.

I flashed my Puerto Rico Moto Maxx 4.4.4 to India 5.0.2 and then to CM 12.1 Lollipop 5.1. I could easily flash it back to Claro Puerto Rico 4.4.4, if I wanted.

There's instructions. You just have to read. [MENTION=2920544]Jaocagomez[/MENTION] wrote an excellent thread about all this. See here:

http://xdaforums.com/showthread.php?t=3074724

The key is having an unlocked bootloader. Where people have gotten into trouble is trying to flash update with locked bootloader.
[Verizon Motorola Droid Turbo General] Kiwironic:
I guess you guys are really happy with what you got. I expressed my opinion and not going to change it to please you.

I think Motorola can do better than this, and I think we deserve better than this. I will leave you guys to give me more lessons about how to be a power user.
[Verizon Motorola Droid Turbo General] ChazzMatt:
I'm not disagreeing that Motorola dropped the ball on the XT1225 with a narrow release, instead of a world wide release that would have included Europe, all of Asia, and Canada. It is a super phone, and Motorola made people jump through hoops to get it.

It should have been as widely released as the Moto X, or even better this is the phone Motorola should have released as the Moto X.

____

But still running 4.4.4 on the XT1225 is your fault, not Motorola. ;) This phone -- the XT1225 -- has had stock 5.0.2 since March on all factory unlocked phones and many Brazil and Mexico carriers and you refuse to flash it on your XT1225.

There's clear instructions on how to do it. Instead you are waiting for a specific carrier OTA, when you do not need to do so.

The XT1225 is the same device across all regions, all countries. The India Moto Turbo XT1225 IDENTICAL in every way to the Latin America Moto Maxx XT2225.

Many, many people in these threads have upgraded, downgraded 4.4.4 to 5.02 and back again, flashed images from different countries, to prove it's not hard -- since our bootloader can be unlocked. The Droid Turbo XT1254 owners WISH they had our advantage!
[Verizon Motorola Droid Turbo General] Kiwironic:
The only reason I did not change region as I mentioned before is to be sure about a good upgrade path. However, since all updates indicates that BR has the highest chance for 5.1 update, then I have just flashed stock BR. People report that they are able to upgrade then downgrade, while others report bricked on downgrade. A smart user knows that gpt doesn't like being downgraded, and so I will not try this path.

I don't want just to update to lollipop, first of all I do not want to lose themoto features I already have, flashing custom or CM will not help, as it doesn't support the stock moto features. 5.0.2 is buggy and less secure and I do not want to flash it unless I have evidence 5.1 is around the corner. (even before having corporate apps)

Here I am now with BR stock, OTA updates are not available, I think I will have to flash the OTA manually. Let's see how that goes.

Now, since I am being accused of being "unreasonable", the question here is, are you satisfied with how Motorola is handling the device??? You can answer this question (at least to yourself) or you can just blame things on me and lecture me on how to be a power user because you know all about it :)

Up to you.

Thanks to all of you who objectively expressed your opinion without the bullying attitude some adopt.
[Verizon Motorola Droid Turbo General] Digital DJ:
I've had just about every Samsung phone since the galaxy S2 and note 1. I've also had the old razor maxx by Motorola and it was horrible. I have the droid turbo un rooted and I have to say it's been the best phone I've ever had. It's fast, great battery, awesome features. I don't care to root anymore because I personally don't see an advantage to it. Please don't argue with me, it's just my point of view for me. I love LP so far. And since the camera update this phone to me is flawless. I think you may be over reacting a bit OP.
[Verizon Motorola Droid Turbo General] Semseddin:
[MENTION=267247]MaxX[/MENTION] folks around the world, since we didn't pay for root or bl unlock, maybe we could collect some money and donate a mint condition moto maxx device to a developer who would develop rom / kernel support for his & our devices.. We could have had the faux123 kernel, imagine that with 3900mah battery.