yashsingh1/xdaforums huggingface dataset:
[E 2015 Original Android Development] Carlos Arriaga:
Hello [MENTION=6485916]squid2[/MENTION], it would be interesting if you could send the code otus CM to have an official version of CyanogenMod daily, besides this would bring benefits to the forum:

Much more development, the arrival of more Roma to the device.

-More Developers willing to work on this device.

Moto E 2014 despite having those errors have an official version of CM, we have just the Youtube error and error experienced by Indian users.

It would be interesting if you could send the code to CM to have official Nightlies.

Regards.
[E 2015 Original Android Development] Manish_Sky:
I Agree

Since its so popular budget smartphone many devs will be joined to give it their time.
[E 2015 Original Android Development] Manish_Sky:
[ISSUE]

IS Bluetooth broken. Its not turning on...
[E 2015 Original Android Development] squid2:
Heh, seems you are right. Bluetooth isn't working for me either. I'm surprised nobody noticed it earlier. I'll investigate the issue when I have time (that will be in around 2 weeks from now).

In the interim, I'll be posting a new build soon with the latest CM updates.
[E 2015 Original Android Development] raghavarora1997:
Bluetooth is working fine for me, I've tried sending some files over it, and it seems to be working okay.
[E 2015 Original Android Development] squid2:
I did a bit more experimenting and found that Bluetooth works fine when it is enabled at boot time. However, if you later turn Bluetooth off, and then try turning it back on, it will fail to turn on. Rebooting the device will make Bluetooth work normally again. I'll debug the issue when I get time.

EDIT: I left my phone running overnight, and now Bluetooth is working fine for whatever reason. I can turn it on and off to my heart's content. Certainly a curious issue, just like the time zone bug.
[E 2015 Original Android Development] squid2:
July 29 Release

I've posted a new build with the latest CyanogenMod updates. Apart from that, it should be pretty similar to the last build. Dowloads are up on the first post.
[E 2015 Original Android Development] squid2:
August 1 Release

As always, the download is up on the first post.

This new build should fix the Indian time zone issues. It has at least stopped the recents key and gapps crashes on my device when I set my time zone to India, and I expect it to do the same for actual Indian users too. I've also updated the kernel and blobs in this build. When I tested the new build, Bluetooth seemed to work fine, but I've left it on the list of known issues in case there is some case where the issue happens that I didn't test. The YouTube ADSP crash is still there, but as before, it only happens once in a while, so it's not too big an issue. I'll see what I can do about it when I have time a couple weeks from now. I'll also start looking at having this ROM made official in a few weeks.

Indian users can try setting their time zone back to the correct region and then rebooting. If the recents key and gapps continue to work, then we are golden. Let me know if you encounter any issues.
[E 2015 Original Android Development] india_motoe2015:
MinMinLock broken

Hello,

I installed the latest ROM & congratulations are in order to you for fixing the Indian-Timezone problem! Thank you!

Although it's none of your concern but it seems that latest ROM update has broken 'MinMin Lock' Xposed module. Is there anything I can do or are we supposed to wait for the MinMinLock developer to fix the issue?

Thanks for your hardword once again!
[E 2015 Original Android Development] squid2:
There were some changes to the lock screen API in CyanogenMod. They are probably what broke MinMinLock in this new release. The MinMinLock developer will have to update his module to support the API changes.
[E 2015 Original Android Development] india_motoe2015:
MinMinLock fixed

I wiped Dalvik & Cache, then disabled Xposed module for MinMinLock, rebooted. Enabled minMinLock & rebooted again. Somehow that seems to have fixed the problem - as of now.

However I feel (and I could be wrong) that current build seems to spend more time on boot-animation screen than the previous build (29th July). The previous build gave the impression that it took less boot-time.
[E 2015 Original Android Development] squid2:
There is a script to upgrade sensor hub firmware on the first boot of this new build. It should be the same speed on subsequent boots.
[E 2015 Original Android Development] india_motoe2015:
Xposed compatibility issue ??

I am beginning to think there's a compatibilty issue with latest ROM & Xposed. When I add a new Xposed module & reboot, I am thrown into a bootloop. However, booting into Recovery-Mode & wiping Dalvik & cache seems to fix the problem.

Additionally, I still experience longer boot-time as compared with the previous releases. It could be highly personal issue given the set of Apps I have installed (or misconfigured) but I want to put it out there for the record.
[E 2015 Original Android Development] india_motoe2015:
Bootloop with latest release

Hello,

I want to know whether the sensor script kicks in after wiping Dalvik-cache & Cache every time? I am experiencing bootloops every time I wipe Dalvik Cache + Cache where boot-animation runs for over 10 min, after which I force boot into Recovery Mode, wipe Dalvik Cache + Cache again & with any luck the phone boots normally.

How to reproduce the problem -

1. Boot into recovery mode.

2. Wipe - Advanced wipe - Select 'Dalvik Cache' & 'Cache'.

3. Swipe to clean.

4. Reboot - System.

5. Now the system boots & boot animation runs for over 15 min (bootloop).
[E 2015 Original Android Development] squid2:
I tried wiping cache and dalvik and rebooting, but didn't encounter any issues. It went through the usual process of rebuilding the cache for each app, then booted up normally. Does it misbehave for you even after a factory reset (wiping data)?

The sensor hub firmware script is run on each boot. It checks the installed firmware version is newer/older/same as the firmware that the ROM comes with. If the installed firmware is newer than what the ROM uses, it downgrades the firmware. If the installed firmware is older, it upgrades it. If it matches, it does essentially nothing. The current build comes with newer firmware than what the previous builds had, so it would have upgrades the firmware the first time this ROM was booted. It should do nothing (other than query the sensor hub) on subsequent boots. Querying the sensor hub should only take a few milliseconds.
[E 2015 Original Android Development] sidheshr:
thanx for fix and update in next build plz add screen off and reboot option in quick settings
[E 2015 Original Android Development] india_motoe2015:
Xprivacy compatibility

I found out that it's not just me who is experiencing problems with bootloop & Xposed.

Here's a link to the post where they suggested a workaround - http://xdaforums.com/xposed/xposed-lollipop-stuck-bootloop-t3055816

Similarly, as I had stated in earlier posts I suspected problem with Xposed framework / module & in personal experience I feel that a particular module - Xprivacy - was the culprit. After installing Xposed-framework & enabling Xprivacy, when I installed a new Xposed-module, enabled it - I was required to reboot for the module to take effect. At which point if I chose to wipe Dalvik & Cache before rebooting, then the phone got stuck on boot-animation endlessly.

I have since not only disabled but uninstalled Xprivacy & I have not faced similar issue ever since. So I may be wrong in jumping to conclusion that Xpriacy was the culprit but my case it certainly appeared as one.
[E 2015 Original Android Development] squid2:
August 9 Release

I've posted a new build with updated power management overlays (for more accurate battery stats), and cleaned up vendor blobs. As usual, it also includes all the latest updates to CyanogenMod. The download is up on the first post.
[E 2015 Original Android Development] india_motoe2015:
Bootloop problems fixed

Just reporting the fact that the boot-loop problems I faced with previous release seems to have been fixed with current release.

Thank you!
[E 2015 Original Android Development] harshwardhan ghundare:
Nice!
[E 2015 Original Android Development] squid2:
August 21 Release

Don't worry otus users, you haven't been forgotten. Today's new build does not have many outwardly visible changes, but I've been working on cleaning up and restructuring the device and vendor trees. This build also includes all the latest updates to CyanogenMod as usual. The download link will be up on the first post shortly.
[E 2015 Original Android Development] squid2:
YouTube ADSP Crash Fixed

I've figured out the cause of the YouTube ADSP crashes that were causing kernel panics. It was caused by AAC compress offload being broken on CM for devices sharing the 8974 audio HAL (8212, which is similar to 8610, uses the 8974 audio HAL on CM). The next release (tonight) will have reliable YouTube playback since I disabled AAC compress offload.

[MENTION=3445372]scritch007[/MENTION] - You might need to do the same for condor, since I've heard of similar problems there. I don't have the device, so I can't say this with certainty though.

EDIT: Damn, I encountered a crash after 40 minutes of testing. Oh well, it still seems more reliable than it was before I disabled AAC offload, so I think disabling it did something useful.
[E 2015 Original Android Development] squid2:
August 21 Build 2

This build disables AAC compress offload, and seems to have mostly fixed the YouTube ADSP crashes. I haven't encountered crashes during more than an hour of testing now, including quality level changes, switching between videos, minimizing/maximizing videos, etc. It used to usually crash in 5 minutes or less. I had encountered one crash on an earlier build after 40 minutes usage, but this build has another little change, and I haven't encountered any ADSP crashes with it. So I'm considering the YouTube bug to be fixed now.

EDIT: Later on I encountered another crash, so it isn't fully fixed, but oh well, it's headed in the right direction.
[E 2015 Original Android Development] Carlos Arriaga:
[MENTION=6485916]squid2[/MENTION] but good news: D, and hopefully this bug is resolved soon.

thanks for your work.
[E 2015 Original Android Development] Casper1982:
It works on MotoE 2nd gen xt1506 ...?
[E 2015 Original Android Development] squid2:
August 22 Release

In this release, I've replaced the source built CM libOmxVdec with a prebuilt one from Motorola. This fully fixes all YouTube issues. No more green pixels ever at any resolution, and no more ADSP crashes. This has put a big smile on my face :D

Now that the main bug this ROM had has been fixed, I've started some discussions to look at having CM support made official. I'll keep this thread updated as the effort progresses over the next few weeks.
[E 2015 Original Android Development] magdeoz:
thank you very much, very good news at last also this problem is solved in this device, now expect official support! ?
[AT&T Samsung Galaxy S 5] Goldie:
Reserved
[AT&T Samsung Galaxy S 5] Goldie:
Reserved2
[AT&T Samsung Galaxy S 5] meissen:
Awesome! Downloading now. I've heard a lot of great things about Alliance ROMs so I'm excited to give this a try.

One question though -- while it says it's "Lite" -- what about this makes it lite?
[AT&T Samsung Galaxy S 5] talkingmonkeys:
Glad to have this here. Thanks for allowing me to port it and make sure it was ready for this release.

[MENTION=3065070]Goldie[/MENTION] the links for the extra flashable zips I made aren't actually links. Thanks for getting this out man!

Extra Mods and G870A Support

We have the activekey working for the G870A. This also adds Active Mode app. Thanks to [MENTION=293887]Morningstar[/MENTION] and [MENTION=4405010]parkerj7uc[/MENTION] for helping me with this. I added it under Accessibility settings in Settings. This also changes the build.prop to reflect the G870A instead of G900A a little and a few files changed to the G870A ones just because its how I was taught. Should be full support for your device like [MENTION=3758230]cstayton[/MENTION] did for us on this device with 4.4.2. I will be adding that to any future version of alliancerom as well. It detects which device you have when you flash the rom and puts the appropriate files on there. For now dirty flashing this after alliancerom should do the trick. Or with the rom for a clean install. Make sure that it is flashed after the rom though.

Confirmed working as intended. Enjoy guys.

Active Key for the G870A: https://www.androidfilehost.com/?fid=23991606952611432
[AT&T Samsung Galaxy S 5] K-alz:
Life is good now......!

From my Allianced Note 3!
[AT&T Samsung Galaxy S 5] Bubba:
Whooohooo here we go again. Nice job talkingmonkeys on porting.

Cowboy from Hell on a twisted trail.

Koffed From my Big Ass Outlaw Phone.
[AT&T Samsung Galaxy S 5] jasonj711:
just flashed the rom on my g870a and when it flashed using FF it flashed good but when it went to load it when to the galaxy s5 active splash screen before when the samsung animation should show but it doesn't. it stayed on the galaxy s5 active splash screen. i did however here the samsung sound effects go but not visual. never booted up past the galaxy s5 active screen.

i did a battery pull and now it is loading. currently it is at the android is updating screen optimizing the apps. but it still didn't show the samsung screen. and now is on the initial start up to set up the phone. now is confirmed u have the same bug [MENTION=4708661]muniz_ri[/MENTION]'s had when he made the lollipop rom with root rom. it doesn't show the samsung splash screen animation and it has a 10-15 second delay when the screen loads after boot to lock screen that the touch screen is unresponsive. i can't unlock or touch anything til it loads that part of the phone to use the phone. might wanna get with him to see what it was. i help test his rom to get that fixed but don't know what it was.
[AT&T Samsung Galaxy S 5] talkingmonkeys:
Did you wipe before flashing? It doesn't really sound like it since it was upgrading apps. It flashed fine for me when I tested it with a full wipe.
[AT&T Samsung Galaxy S 5] meissen:
I had the same hiccup as jasonj711 - only I have a Samsung Galaxy S5 (not Active) and when it rebooted after installing the Alliance ROM it showed the Samsung Galaxy S5 splash screen and although I could hear it play the chime for the Samsung animation, it stayed on the Galaxy S5 screen. I had to do a battery pull and when I booted the 2nd time it was optimizing my apps.

I'm in the set up right now and I can see minit3d battery or whatever it's called so it appears the ROM flashed successfully. Just a hiccup with the initial boot.
[AT&T Samsung Galaxy S 5] jasonj711:
I am doing a re"reboot now then if same result I will refashioned see if something went wrong I know I put fill wipe. I will flash and let it sit for a bit to let it load. But the first flash acted exactly the same as [MENTION=4708661]muniz_ri[/MENTION] when he was making the lollipop\root stuff.

edit: rebooted got same result. i am reflashing now and so far it is sitting at the galaxy s5 active screen screen. i already heard the samsung logo splash animation sound but no samsung screen. i am letting it sit to finish loading to the actual phone screen. will update when finished.

edit 2: it loaded to setup screen and same delay as before will setup and reboot and see what happens.
[AT&T Samsung Galaxy S 5] talkingmonkeys:
I'll take a look at it later. I have a lot going on today. It worked fine when I tested it so it's going to frustrate me tonight.
[AT&T Samsung Galaxy S 5] jasonj711:
I think it might be just something on the g870a install of it. If I remember correctly [MENTION=4708661]muniz_ri[/MENTION] had same thing was just for the active variety. Other then that the rim runs great. Take ur time Bro not in a rush. I know it is gonna bug ya til it is fixed I know How it is I am the same way.
[AT&T Samsung Galaxy S 5] Ravenryan:
I had the same issue.
[AT&T Samsung Galaxy S 5] randiye:
This or tms5.0?

What's the difference between this rom and tms5.0 by talkingmonkey? Pros and cons of each? Battery life? Thanks.
[AT&T Samsung Galaxy S 5] jasonj711:
This has more customization then tms5.0 . Imo tms5.0 runs a Lil smoother.
[AT&T Samsung Galaxy S 5] jasonj711:
Also on the notice toon setting none of the icons are there just the words so there is no way to see if they are active or not. U can touch them to turn them on or off but no way to see if they are or not.
[AT&T Samsung Galaxy S 5] trapt_dew27:
Same issue

I had the same thing happen. It turns out that the SFinder bar overlaps the quick setting buttons. I removed the SFinder bar using the Alliance Control App (under Notification panel) and it sort-of fixed that problem. I now have a gap where the SFinder bar should be. If you try to re-enable the bar, it'll show up at the bottom (under the brightness). I haven't figured out how to get it back into the right spot yet. I tried to remove the brightness and quick setting buttons, to see if the SFinder bar would jump back up to the top, but it won't let you configure for less than 5 of the quick settings buttons.
[AT&T Samsung Galaxy S 5] Goldie:
Just enable and disable app bar and sfinder to get then in sync
[AT&T Samsung Galaxy S 5] Ravenryan:
How do i get rid of the content hidden on the lock screen lol?
[Moto G Q&A, Help & Troubleshooting] solauciel:
Hi, first, thanks for reading. Second, i've already searched de whole google world, and inside all this threads, but....

I CAN'T FLASH ANY RECOVERY! I don't know why!

In fastboot, i put the commands for flashing CWM, TWRP, Philz, and it works with no error. But, when i select the recovery option in my xt1032, it always boot the CUSTOM recovery. What can i do?

And sorry about my english, i´m from argentina.

Thank You!!
[Moto G Q&A, Help & Troubleshooting] outerspacebuddy:
Hi. I don't get it. TWRP or CWM or Philz is custom recovery, so if you flash them to your device, of course the stock recovery will be replaced by custom recovery, so when you select Recovery option in Bootloader screen, of course it will bring you to a custom recovery. Yesterday I flashed all kinds of recovery in order to flash ROM (flashable zip file) into my phone but it failed all the time, so I decided to install stock firmware by using mfastboot (and removed custom recovery also).
[Moto G Q&A, Help & Troubleshooting] solauciel:
So, i'm getting it wrong.... Please tell me: if i flash a custom recovery, like twrp, how can y acces to it? I though it was from fastboot>recovery

Actualy, I can't flash ANYTHING! :( It's so frustrating. I've tryied to flash the bootlogo, but it doesn't work either!
[Moto G Q&A, Help & Troubleshooting] solauciel:
Sorry, i misunderstand you. "so when you select Recovery option in Bootloader screen, of course it will bring you to a custom recovery", you said. But no, it only boot de stock recovery! No matter how many times i've flahsed twrp cwm philz...
[Moto G Q&A, Help & Troubleshooting] outerspacebuddy:
If you want to flash a custom recovery, you need to have:

- Minimal ABD & Fastboot. Extract it into a folder.

- The recovery's .img file from its website. Its name may be very long, so you should rename it into something shorter, for example "newrecovery.img". Put this file into the same folder that you've just extracted Minimal ADB & Fastboot.

- Boot your phone into Bootloader screen (by first keep holding your Volume Down then press Power button for a short while). Connect the phone to your computer. In your computer, open the folder that contains Minimal ADB & Fastboot and the .img file of the custom recovery aforementioned. Now hold Shift key on your computer's keyboard and right click your mouse on the blank space of the folder. Choose "Open command prompt here''. When you see a black window, type:

fastboot flash recovery newrecovery.img

then Enter. The custom recovery will be installed right away. After that, choose Recovery on your Bootloader screen and the custom recovery will open. Yesterday I read on a website that some ROMs overwrote your custom recovery when your phone rebooted so that might be the reason why you cannot use the custom recovery you've just installed. I don't know how to solve this as I'm just a noob.

However, why do you need to install custom recovery? Does your phone still work properly? What kind of ROM are you using? If your phone doesn't work since the ROM has been messed up, I suggest you do a fresh install as this thread tutors: http://xdaforums.com/showthread.php?t=2542219. After restoring your phone to a good state, you may try installing custom recovery again.
[Moto G Q&A, Help & Troubleshooting] solauciel:
I think you're rigth... I need to instal custom recovery because flashing from fastbooy doesn't worked at all... Realy, i've flashed a lot of firmwares and none of them seems to "get flashed" in mi device
[Sony Xperia S, Acro S, Ion] gauravsaini964:
Hello , I have recovery TWRP 2.8.0.1 installed on my Xperia S .I am not able to flash any roms via it (lollipop roms I've tried).Please tell me what to do ,I have to flash zip via sideload ,nothing else works.Adb and fastboot is also not working.

Please guide me properly as it is not my phone ,I do get this phone for flashing only.
[Sony Xperia S, Acro S, Ion] Mirhawk:
What error do you get exactly? Also, have You installed fastboot and flashmode drivers? Because that's why fastboot doesn't work most of the times. If You were able to go to fastboot, try following guide from here.
[Sony Xperia S, Acro S, Ion] gauravsaini964:
Link to the drivers please. I am not able to do much because its not mine device ,I get device for at-most an hour !!
[Sony Xperia S, Acro S, Ion] Mirhawk:
Download the Flashtool from here. After You install it, Under the folder "C:\Flashtool\drivers" You have Flashtool-drivers.exe. Install drivers from it which are related to Xperia S as well as the fastboot and flashmode drivers. Then You will be able to go into fastboot mode.
[Upgrading, Modifying and Unlocking] mongday:
Hello, Guys

I would like to modify altermis rom ( Add some Program into the rom ).

How can i do it. Could you please, introduce me about tools and method for this.

Thank you,

Mongday...Thailand:confused:
[Galaxy S6 Q&A, Help & Troubleshooting] nflwideout86:
Hey guys....so i just tried out wifi calling, but every time i called my s6 from my landline i get a busy tone. And the second i switch off wifi calling incoming calls work again. Anyone know how to fix this?

On normal calling every time i call someone they tell me i sound muffled or stuttery, or that i sound 'tinny' (whatever that means)...so i wanted to try the wifi calling but i can't even get that to work.
[Android Q&A, Help & Troubleshooting] Andre1299:
Hey,

I have a problem with my V875.

I made an error while flashing the stock ROM, and after that my internal memory was damaged. I was unable to mount and format anything. So, I format everything (except the bootloader) with sp flash tool, but now my phone is dead. The only thing he does is turning on the led when usb charger is plugged (on a computer, or on the charger). And when I unplug it, the led remains on, and I have to remove the battery for turning it off..

I looked for a solution, and now I have the firmware for my device. But I need also the preloader.bin file...

Do anyone have it?

Thank you
[Verizon Samsung Galaxy S 4] screamwork:
Hello..

I'm on 4.4.2 and I have a stock NC5 ROM, only ROOTED by Towelroot so I don't really have a recovery or anything.

I want the Lollipop OC1, I know that it has no root I just want to know where to start? do I just flash it through ODIN? Thank you.!!!
[Verizon Samsung Galaxy S 4] meazz1:
Yes.

Follow the OP in the thread.

http://xdaforums.com/galaxy-s4-verizon/general/how-to-update-to-i545oc1-5-0-1-keeproot-t3096558

or

http://xdaforums.com/galaxy-s4-verizon/development/rom-i545oc1-5-0-1-100-stock-mdk-t3097902
[HTC One X] lakatosbalazs:
Hi

I have updated Lolipop from 4.2.2 android,

And i made nandroid backup 2.17.401.2 (couse i didnt like Lolipop)

Now my screen not responding, what is the problem?