yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] hokiealumnus:
crDroid v3.4 is Up!

June security patch anyone? :cool:

crDroid v3.4 for Pixel XL (marlin) is live and ready to go! Per our dev, neobuddy89:

Changes specific to our device:

* You need the NJH47B vendor image, DOWNLOAD HERE

The LOS Google Camera bug is still present (where it crashes trying to save 30 FPS videos; 60 FPS works fine) and will be until LOS fixes it. Photos are as they should be.

Gapps still have to be included for now. Required updates should be few.

As always, download link & instructions are in the OP. Dirty flash should be fine, but remember to always clean flash before reporting any problems. Enjoy! :good:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] blaze9090:
Is the cloud restore bug at first setup fixed?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] hokiealumnus:
I'm sorry to say I have no clue; I never use it.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] blaze9090:
Bug is still present.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] hokiealumnus:
Ok, thanks. I'm wondering if it is the older Gapps setup I use. I wanted to keep the pixel graphics. I'll pop off a build with an updated one after I finish my device builds on 3.4 if you feel like trying it.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] socioteq:
Can anyone confirm that NFC is no longer functional on 3.4?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] BHermes211:
It's not turning on for me either
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] hokiealumnus:
Huh. I don't use it, but it's not turning on for me, that I can confirm.

Did it work on 3.3?

Edit - Sorry guys, this is actually the device I own, but I don't use NFC for anything, so I didn't catch this.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] socioteq:
Ya I use it for Android Pay... Hopefully neobuddy can get us an option for NFC screen off at some point that would​ be sick :D
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] hokiealumnus:
There is a new commit from yesterday in the LOS device tree having to do with NFC that wasn't there when I built mariln/sailfish. I'll commit that and rebuild, then try a 3.4.1 release. Hoping to get that up by this evening or tomorrow morning.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] hokiealumnus:
Ok folks, I have uploaded v3.4.1 for marlin here: link removed - storage bug.

I have not had the chance to test it, just build it and upload. I won't be able to test it until this evening and will report back when I do, but since it's up, if anyone is feeling adventurous and has time during the day, feel free to test and let us know whether NFC is working!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] hokiealumnus:
Ok, I have good news and bad news. The good news is that NFC seems to be fixed. The bad news is that the new storage bug is present on this build. We will need to wait until that's fixed before releasing a build with NFC fixed.

As such, I'm removing this build from AFH. Don't install if you've downloaded. It won't brick you, I'm typing on it right now. You'll just have to dirty flash back to the earlier 3.4 to access storage.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] BHermes211:
Thanks for the heads up...

I wanted to flash it but couldn't be without the phone at work.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] hokiealumnus:
crDroid v3.4.2 is Up!

EDIT - I'm not 100% confident in this interim release either. It's giving me fits with storage, and it's totally random - sometimes it works, sometimes it locks & restarts. My current recommendation is to use v3.3 (with the May vendor image). Since it's a device I own, I hope to get this licked more easily. I will report back.

Please accept my most humble apologies. We will get this back on track.

All right, NFC bug is squashed, as has been the storage bug! As such, crDroid 2.4.2 is up for marlin here: https://www.androidfilehost.com/?w=files&flid=157906.

To sum up, there was an NFC issue on the Pixels that needed a commit to the device tree to fix. It is now fixed. There was a separate issue caused by some aggressive sdcardfs optimizations that didn't affect these devices on 3.4 (but did on marlin's short-lived 3.4.1 release), but it's also fixed too. :good:

PS - I did not update the first boot setup app, so you probably still can't restore apps from the google cloud. To repeat from previously Photos still backs up/restores full resolution photos to/from the cloud just fine, which is why I think it's the setup apk. Use Titanium Backup if you want to clean install. I just wanted to get these bugs fixed ASAP and will try fixing that for the next release.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] BHermes211:
Thank you for the rapid releases. Much appreciated
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] hokiealumnus:
I'm not 100% confident in this interim release either. It's giving me fits with storage, and it's totally random - sometimes it works, sometimes it locks & restarts. My current recommendation is to use v3.3 (with the May vendor image). Since it's a device I own, I hope to get this licked more easily. I will report back.

Please accept my most humble apologies. We will get this back on track.

EDIT - I have rolled back the OTA check to v3.3 so you don't keep getting notified there is a new version available. I am leaving the new one up if you feel like checking it out, but I recommend against it at this juncture.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kirschdog1:
I couldn't get this to work coming from June stock any idea for steps to flash. I tried wiping, flashing rom, twrp, V8 bootsigner then reboot recovery to a bootloop. Any ideas?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] hokiealumnus:
Hmm. Before the steps you mention, did you fastboot -boot- to TWRP, and then flash TWRP from there? If you did a fastboot flash of TWRP, recovery is only on one of the partitions.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kirschdog1:
so i would need to flash recovery on the other partition?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] hokiealumnus:
Yep, that's why you are boot looping. You don't want to bother doing that from fastboot. Fastboot boot to the TWRP image, and then flash TWRP from within TWRP, which will flash it to both partitions automatically.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] hokiealumnus:
Ok, seems a totally unrelated LOS device tree commit snuck in enabling sdcardfs. They had a different commit specifically for that which I had not committed before because it doesn't work with ElementalX.

I have now fixed that and am rebuilding. I'm reasonably certain that is what caused all the issues and will have this version uploaded after I test it, either tonight or tomorrow.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] hokiealumnus:
Finally, marlin (and sailfish) is all good.

Download marlin 3.4.4 here: https://www.androidfilehost.com/?fid=961840155545572729

No bugs as far as I can tell (except the yet to be addressed restore apps from cloud). Again, my apologies for the issues. Enjoy the new release!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kirschdog1:
Can I dirty flash over 3.4?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] hokiealumnus:
Absolutely, that's what I did and no issues.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] BHermes211:
Going to flash the new build. I'll report back if any issues arise...

Thanks again, really appreciate your never ending effort and support
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kirschdog1:
Loving this new rom. Keep up the good work.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Reuben_skelz92:
Any chance of adding pixel icon support for the pixel launcher?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] hokiealumnus:
I probably could, and thought about it. The reason for hesitating is download size. The ROM is already huge with having to include Gapps, I was trying not to make it any bigger.

That said, it wouldn't be too hard to reverse. I'll give it a try; but if I decide against it, size will be the reason.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Reuben_skelz92:
Ah ok

Only thing that stops me using some ROMs:( just out of interest why is size an issue?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] hokiealumnus:
Just instinct from past experience. This thing is a whopping 630 MB, compared with 350-400 for ROMs without Gapps. Smaller is better, especially for those with download caps.

If I'm feeling Pixel though, I use Nova prime + PixelIP from the play store. FWIW.

I'll still try and see. :)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Reuben_skelz92:
Yeah nova is cool but I love the pixel launcher. With its swipe to Google now . And the Google widget is bigger. I don't novas version is too small if I make the icons bigger
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kirschdog1:
I'm not able to get swipe to Google now with pixel launcher on this rom? Not sure if it's available with the download from the play store or if I just don't have it activated??
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Reuben_skelz92:
You mean Google now or pixel launcher?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kirschdog1:
I mean I have pixel launcher running currently but I can't swipe to the left get Google now page like on stock.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] hokiealumnus:
It requires the launcher to be installed as a system app. Which means either I build it in, or you sideload it.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] MArtyChubbs:
In Nova, I set up a gesture to swipe down to Google (Google Now) ... Love it.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kirschdog1:
Anybody have viper running on this rom?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] socioteq:
Yes. It takes some work, but research Arise4Android. You'll have to modify a file in the install zip with the parts that you want to have installed, but it's been solid for me
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kirschdog1:
I flashed arise v2.94 aroma and it didn't work. The viper dcale showed up but couldn't get it to work. What file did you use and what change did u make to it if u don't mind me asking?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] socioteq:
I went ahead and uploaded my modified zip that includes only the newest version of v4a. All you have to do is flash it in TWRP and boot it up. Basically, if you want to add any of the other modules (which I'm not sosure that you need based on what you've told us) you open this zip with an archive manager and modify the following file and follow the directions.

/getting_started/your_system/arise_customize.prop

If you don't want to add a module, you leave it blank (leaving it blank stands for "false") or type true if you want to add the module. The way it is set up right now in this zip file is to add v4a (which shows up as Viper4Arise in your app drawer.)

Once you boot into Android it should just work. FYI: I am using Magisk for Pixel, not SuperSU for root. It shouldnt make a difference, but I thought I'd throw that out there.

https://drive.google.com/open?id=0B4AvjErvDaHCWkxEejd4czVnblk
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] hokiealumnus:
I use ARISE Magnum opus 5/24/17, with Magisk and the built in ARISE Magisk compatibility module (it is an option in the customize prop file).
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kirschdog1:
I flashed it however I'm not sure if it's working? No app showed up?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] socioteq:
This also requires that you have TWRP RC2, if you're on RC 1 it won't show
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] hokiealumnus:
[MENTION=7966837]BigM69[/MENTION] I think you forgot to type anything in there. What's up?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] hokiealumnus:
Hey folks. I have tried two Gapps updates in a test version. Note this is NOT an official incremented build, just same old 3.4 but with a couple things changed, mostly specific things for two requests.

[MENTION=6200521]blaze9090[/MENTION] - I switched to the newest setup apk. If you feel like testing whether apps restore on setup, feel free. No promises that the app update will fix that though. Make a backup if you try. :)

[MENTION=7293647]Reuben_skelz92[/MENTION] - The pixel launcher is built in on this version, but I didn't get the icons as intended (pretty sure I know how to fix that). If you really want swipe to Google Now, dirty flash and use this version, but you won't have round icons.

Download link: https://www.androidfilehost.com/?fid=889764386195907995

Nothing else was updated, so there's no reason to even download aside from that. :cool:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Reuben_skelz92:
Thanks:) look forward to round icons too:)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] hokiealumnus:
crDroid v3.4.6 is up!

OMG I'm so excited. I try never to release like this in between crDroid official releases, but thanks to [MENTION=6044187]yung40oz84[/MENTION] linking to the fix that was noticed and verified by [MENTION=3515982]apascual89[/MENTION] , 30 FPS video is working! I just tested it by recording, saving, viewing and deleting three separate videos. That means the only remaining bug is killed!! I'm building sailfish now b/c this is what I consider a huge deal.

Download here: https://www.androidfilehost.com/?fid=889764386195908352

[MENTION=7293647]Reuben_skelz92[/MENTION] - The fix to get round icons didn't work like I thought it would. I'm not giving up though! The launcher still works fine and has swipe-to-Google-Now though.

For now, I'm done until we release 3.5, unless you guys find something that's not working that I haven't found yet. Enjoy!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Reuben_skelz92:
That's cool still going to run newest build:) nova launcher just launched an apk so it has swipe to Google now on nova!! So that will be cool for now. I still prefer pixel launcher mainly cause the Google widget widget matches the bigger icons....I'm a bit ocd haha. Thanks though. Look forward to flashing newest build
[T-Mobile Samsung Galaxy S7 Questions & Answers] dman777:
I have an American Tmobile S7 and I just got the Nougat update the other day. There's no bugs or issues, I'm just not loving Nougat. The Marshmallow was a better user experience for me and I also liked the material design look better.

How could I revert back to Marshmallow? I read where I could use use a rom but then I would have to have my phone rooted and that is not possible, correct?

I thought about factory reseting my phone, but then I would constantly have that naggy T mobile upgrade notification in my drop down bar, right?
[T-Mobile Samsung Galaxy S7 Questions & Answers] Snow755:
i love Nougat updated on mind i have not had not one issue with my Nougat updated i did a full wip after the updated too get ride of any bugs the Nougat updated has been grate for me
[T-Mobile Samsung Galaxy S7 Questions & Answers] Corwinder:
Factory resetting won't work. You will still be on Nougat.
[Android Q&A, Help & Troubleshooting] DonJoee:
Is there a solution to the problem above?
[Android Q&A, Help & Troubleshooting] DonJoee:
I saw a "Sound Device Manager" section within Settings of Android 4.x.x on other TV-boxes.

Maybe there is a way to "enable" such a settings block within Android 6.0.1, too?
[Android Q&A, Help & Troubleshooting] Lechaxda-developers:
Hi, just faced same problems as DonJoee: (Scishion V88 Mini II TV Box, Rockchip RK3229,2 Gb/8Gb, Android 6.0), also after some research (tried already 3 webcams (Trust, Microsoft, No-name) :

-All cams detected by system

-All cams are showing/sending videostream perfect everywhere (skype, viber, UsbWebCameraPro etc.)

Webcam build-in microphone (also all cams): works perfect in Google voice search, UsbWebCameraPro. Problem: Does not work in messaging Apps (both Skype and Viber).

-Recommended disabling „OK Google on every screen“ does not help.

-Looks like after plugging, webcam’s microphone is detected correctly in /dev/snd/ as pcmC3D0c.

-Looks like messaging app always forced to use device internal microphone (TV boxes have no internal microphone), just ignoring others.

In addition to methods of DonJoee i have tried add in bild.prop:

usb.audio.cap.device=pcmC3D0c

audio.input.active=AUDIO_CODEC

Regretfully it does not help.

Any hint on app, that manages audio devices on Android 6.0?

Any other ideas?

Thanks
[Android Q&A, Help & Troubleshooting] Snirkflonk:
I faced a similar issue with my Huawei Honor 8 connected through USB OTG (USB C) to my USB microphone Blue Yeti. Tested on a Sony Xperia Z3 Compact as well with the same behaviour. When calling the Echo / Sound test service no audio was recorded at all. On a similar note, attempting to record using one of the few audio recording apps that allow input from USB microphones (RecForge II) was unsuccessful: when set up to use the "default" (and not the internal) microphone the recordings would not start (i.e. the visual representation of the sound input normally seen was static and zero and the time indicator did not move). However, a sound file with length "-596:-31:-23" was still created at every attempt.

I attempted a wide range of options, including enabling/disabling USB Debuggning and selecting different options in Select USB Configuration (including Audio source and MTP) in Developer options. I also made sure USB audio routing was not disabled in Developer options. No change had any effect, and I was confused that upon changing USB mode in the scrolldown menu that appears upon connecting the Blue Yeti to anything else than "Reverse charging" only made the red LED on the Blue Yeti turn off for a second, and then come back on as the phone automatically reverted the setting to Reverse charging. I also tried different USB cables and different OTG adapters to no avail.

The solution I found after much experimenting was not really related to the above. I found that, when attempting to record using the USB microphone in RecForge II, the recording would start if I disconnected and reconnected the USB microphone while recording. What happens is that the phone phone reverts to recording with the internal microphone when the USB microphone is disconnected, hence starting the recording since the audio input is valid. Upon reconnecting the USB microphone (still during recording), there is a few seconds of silence but then the phone switches to taking audio from the USB microphone input and I can record as normal.

The same applies for Skype. When calling the Echo/Sound test service with the USB microphone connected, I wait for the signal to start recording a message and then quickly disconnect and reconnect the USB microphone. This way, I am able to record a message using the USB microphone that is played back to me afterwards. I expect the same solution to apply during Skype calls (disconnecting and reconnecting should enable Skype to take audio from the USB microphone) but I have not tested this.
[Moto G4 Plus Questions & Answers] Mexickano:
It's so common to get a weak signal after flashing a new ROM?

I've been using RR since a few months, I'm a G4 regular owner and AT&T user in Mexico, I didnt use my phone with stock rom enough time to say if there's a big difference between after and before.

I just did:

1- Unlock Bootloader

2- Flashed recovery

3- Flashed ROM and GApps

Do you think I failed flashing Modem or anything?

Any other user from Mexico using AT&T as provider with signal issues?
[Moto G4 Plus Questions & Answers] Danielikto:
Instala stock de android 7.0 y despues instala roms, creo eso mejora lo de la señal, yo hice eso y ya no tuve problemas con la señal en las roms..... https://xdaforums.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
[Moto G4 Plus Questions & Answers] Droidphilev:
If you have never flashed a modem to your device it is better to leave it this way. All modems you can find are leaked ones.
[Moto G4 Plus Questions & Answers] Mexickano:
what happen if I'm already in 7.1.1?

Just downgrade to stock and after that upgrade again?

There are no any issue doing that?

[MENTION=803530]Droidphilev[/MENTION] Thank you for the advice, I'll not do that then.
[General Questions and Answers] jandebor93:
What are the best apps for Android enthusiasts??
[General Questions and Answers] Droidriven:
That question is pointless because the best apps for YOU depends on YOUR purposes, best for someone else may not be best for you.

Also, it depends on if you're rooted or not. In addition, it can also depend on your hardware or android version.

Basically, just do some google searching to see what catches your interest because even if you get suggestions it will only bring you to ask more questions about what to do with those apps or how to set them up properly.

Searching for yourself and then searching what to do with them and how to set them is going to be the best thing for you to do, that way you understand what you find instead of asking a million questions here.
[General Topics] Hguerredo:
HELLO!!!:)

I'm new here,and i need some help...

I have an Hp ipaq 1910 series(I now that is very hold),and i'm looking for a rom to my device..if that some please help me?:(

my device have windows mobile 2003(in spanish) and i look for one in another language, if that possible in portuguese or in english...

if is'nt possible,some upgrade for him, or an application that change the language...

someone,please can help me?

sorry for my english,and thank you......
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] wheelsofsteel:
I've acquired an S4 Mini i9195 that is "soft bricked" and worth repairing.

It sticks at the "Samsung S4 Mini" (white on black) screen, but is happy to boot into ODIN or recovery partition.

I tried to flash a new recovery using heimdall; it aborts with "mmc_read fail", even if I specify a PIT file. I also attempted the --repartition from a full backup, which also fails with the same message (followed by "SECURE CHECK FAIL: PIT")

It's sensible to presume the "mmc_read fail" messages aren't normal and the device is clearly telling me what the problem is .

Except the stock recovery partition boots can and can even wipe and reformat /data and /cache. So the MMC seems fine here and it's strange it would be reliable at one thing, but totally broken for another?

What could I try next so I can start flashing the recovery etc.?

Thanks
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] IronRoo:
What happens if you try to flash a FULL stock ROM?

Do you know what caused the soft brick?
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] wheelsofsteel:
The same thing; I also tried with the Windows Odin software; the phone reports that message and the software's log gives no details other than "FAILED"

No, the phone came second hand but its previous owner didn't strike me as someone who would be experimenting with custom ROMs or anything like that; for them the phone stopped working and a new one was needed. It doesn't have its knox bit triggered.

Thanks
[YotaPhone] fcarlosjr:
I've read some reviewers complaining about this problem in some reviews of the Yotaphone 2 around the web, but couldn't find anything related in this forum, so...

Is anyone here having problems with the keyboard lagging while typing text? As if the device didn't have enough power to process the character hittings and ends up queuing and eventually missing some of them. I've been using the default Google Keyboard, but this problem is regardless of the keyboard application I use, and is just driving me crazy.

I'm still on Kitkat as it is my favorite Android, but it's so frustrating typing on this device I am really thinking of upgrading just to see this issue gone. Has anyone already experienced these lags? Can anyone confirm that this has been addressed on Lollipop?
[YotaPhone] casaprocida:
The problem is RAM related. Chheck wich application use more RAM in your device and try uninstalling them.