yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Shadow Death:
I look through these threads and somethings just don't change.
[Samsung Galaxy Nexus] domenci:
No, a few builds ago the lens blur stopped rendering, and with the 7/5 build a new bug showed up in which the camera UI kept rotating even with the phone staying still (making it next to impossible to snap a picture), plus the lens blur issue remained, also random reboots. I tried wiping and a clean install but no luck. Anyways I'm on shiny now and all is well. Thanks again
[Samsung Galaxy Nexus] MWisBest:
...that's because you were using Google Camera. The stock Camera app works fine.
[Samsung Galaxy Nexus] domenci:
Should I also have been using the stock browser and not chrome? An older version of the play store? Not really sure your point... Google camera works fine (and is stock) on other ROMs and you have no disclaimers saying there are problems with the new camera app.
[Samsung Galaxy Nexus] MWisBest:
There's no disclaimer about Google Camera not working because this is the first I've heard of it not working. I don't quite understand how I'm expected to fix something I don't know about.
[Samsung Galaxy Nexus] domenci:
Sorry to upset you, I've personally mentioned it three times in this thread, at least one of which you responded to.Good luck on a fix, I doubt people want to stick with the olde camera any longer than they have to.
[Samsung Galaxy Nexus] MWisBest:
I'm sorry, I overreacted. I think I probably mistook what you were saying for it being a bug with the regular camera. I did get a logcat of what's going on with Google Camera and I have a couple ideas of what might be causing it, hopefully I can get it fixed for the next build.
[Samsung Galaxy Nexus] ilgimmy:
deleted
[Samsung Galaxy Nexus] Rushead:
In the future, please be specific when you're talking about issues. Google Camera is NOT Camera. You may have mentioned Google in a previous post that I missed or don't recall, but no one can be helpful if we don't have accurate information.
[Samsung Galaxy Nexus] domenci:
be that as it may, google camera is the new stock (gapps not AOSP, which this rom is not) camera and has been since at least 4.4.3. I'm not sure why there is a discrepancy in this ROM that requires gapps that don't have the new camera. That being said the stock camera doesn't have features like photoshphere and lens blur, so when I pointed out a problem with those features, it was pretty obvious what I was talking about. Sorry if I confused your understandination I'll try to be more specific in the future.
[Samsung Galaxy Nexus] Rushead:
There's a new one.
[Samsung Galaxy Nexus] MWisBest:
Release Candidate build: omni-4.4.4-20140726-toro-FML.zip (159.68 MB)

I reverted the LTO stuff to libc/libdl (bionic) and ART, as it just wasn't stable enough. As a compromise I added some tested, proven optimizations to bionic, courtesy of the awesome people from Linaro.

Chromecast streaming/mirroring is working, as well as other WFDs (WiFi Displays) I think. Screen recording should work 100%, beit command line or the app/shortcut, and it should use the device audio rather than microphone audio now as well.

If the Chromecast stream/mirror thing works OK (don't expect 100% performance, this is nearly a 3 year old device, it can be decent however if the Chromecast or the Galaxy Nexus drop just a single packet it can cause a large stutter and, RARELY, disconnect the entire thing), I plan on getting it merged directly into OmniROM then.

The kernel is still kinda barebones, that'll be the last thing I mess with before getting an official update to FML up. I have so many ideas bouncing around in my head, eventually I just have to stop or I'd never get new builds out at all! :eek:

In the past week alone I've done at least 3 builds a day!

This ROM is AOSP-based. That's basically AOSP, the entire underlying thing is more or less the same. Look at the name of the keyboard: AOSP KEYBOARD.

The first post mentioning GApps says to use the mini modular version. It's very annoying when the full packages decide to remove the stock apps, which I presume is what happens to the stock Camera then.

Google Camera is installable through the Play Store and it should just be gotten through there. What the hell happened to the days when GApps were one-size-fits-all, flash-away and no-problems. This has reiterated the need for me to create a GApps package just for FML, so I'm going to create a tentative plan for them:

"Essential" Package:

- Google Services, etc.
- Google Search
- Google TTS
- Google Play Store
- Face Unlock

"Play" Package:

- Google Play Books
- Google Play Games
- Google Play Movies & TV
- Google Play Music
- Google Play Newsstand
- Sound Search for Google Play

"Actually Useful" Package:

- Calendar
- Drive
- Gmail
- Google+
- Hangouts
- Maps
- Street View
- YouTube

"Community" Package:

- You
- Tell
- Me
[Samsung Galaxy Nexus] JoJoDaClown:
Personnaly, I don't want any of the apk's in the Play package. The others I use 90% of. I don't really use Google+ or Drive, but understand that many people do.
[Samsung Galaxy Nexus] MWisBest:
Like I said, it's tentative. The idea with the different packages is:

1. If there's an update to one of the apps, I only have to update the package that it's in, rather than one huge zip.

2. It lets people only flash what they want, such as in your case you could skip on the "Play" package then.

So rather than having a bunch of packages which duplicate themselves (in the case of the currently-recommended PA GApps, with their micro, mini, full, etc.), people can just piece together what they want. Seriously, how does it make any sense for the PA GApps to do it like that? They could instead do the micro package, then the mini package, but only have the mini package contain the differences between the micro and mini packages (etc.)!
[Samsung Galaxy Nexus] JoJoDaClown:
For some reason I can't install the ROM. I'm using FML TWRP from first page, the linked ROM (7/26) and the 7/25 mini modular Gapps. I'm doing a clean install (wipe cache, dalvik, system). I get stuck on the Google boot screen.

Anyone have success installing?
[Samsung Galaxy Nexus] MWisBest:
Only thing I can suggest is to try flashing it again, and worst-case scenario try to redownload it.
[Samsung Galaxy Nexus] JoJoDaClown:
In the process of re downloading. I've tried to reinstall a few times. Is the new rom F2FS compatible? that would be my only other issue.

UPDATE: Still won't install. I've re-downloaded and even gone so far as to completely wipe the phone and push the files.
[Samsung Galaxy Nexus] terminal13:
So I installed the rom it runs fine, but my play store resource images are wrecked... I did a manual update to the newest version might that be it? It was fine before I flashed, may this be a bug?

Radiation from my 4.4.4 gnex
[Samsung Galaxy Nexus] MWisBest:
It is still F2FS compatible. I don't understand what is causing this, I just went over everything I've done since the last build. Only thing I can suggest is this:

1. Make sure you leave it on the Google screen for a while rather than giving up right away. There was a rare instance where the eMMC didn't initialize properly on first boot, waiting 30 seconds made it try again and that fixed it.

2. See if it responds to adb and if so try and get a logcat of what's going on.

That's a bug from compiling with GCC 4.9. I'm certainly not going to ignore it, I AM trying to fix it, however I'm not going to let that stop me from releasing a new official build either. Corrupted images in Google Play, versus the performance of using GCC 4.9... I'm going to go with GCC 4.9 and bad images in Google Play.
[Samsung Galaxy Nexus] JoJoDaClown:
I've moved all of the filestructure to ext4 and still no dice. I'm trying to dump a logcat, but adb just says waiting for device. I'm able to push files but logcat function isn't working. I've never used the logcat function, so not sure if I'm missing something.

I've always waited on the google screen for a good 10 mins before pulling the battery.
[Samsung Galaxy Nexus] terminal13:
Did you try to flash an older version then reflash?

Radiation from my 4.4.4 gnex
[Samsung Galaxy Nexus] JoJoDaClown:
I've used both the phone and a PC to download the file, both times md5 checks out and neither works. I've wiped and installed 7/5 and that installed fine. Tried to dirty flash 7/26 and it won't work. I've clean flashed numerous times, numerous ways, numerous downloads of the file, and never been able to get it to install. I'll just have to wait.
[Samsung Galaxy Nexus] terminal13:
Weird bro.....

Radiation from my 4.4.4 gnex
[Samsung Galaxy Nexus] MWisBest:
Can you by chance see if this build works?: omni-4.4.4-20140716-toro-FML.zip (159.09 MB)

If not, can you tell me what the file "/sys/board_properties/revision" contains on a working build?
[Samsung Galaxy Nexus] Clarke33:
ROM is running great with the exception of camera and torch. Anyone else?
[Samsung Galaxy Nexus] terminal13:
This is in the Release candidate build if it happens to be helpful.....

Radiation from my 4.4.4 gnex
[Samsung Galaxy Nexus] MWisBest:
Same hardware revision I have, which is the newest possible one as far as I can tell. I'm hoping to narrow down which hardware revisions the new kernel work on, then I can maybe find whatever quirks there are between the non-working ones and the working ones.
[Samsung Galaxy Nexus] terminal13:
Maybe in my random drop ins I missed something, but don't you have a more aosp-ish build going and some omni builds, which are cm based which ultimately have to be sourced from google? So doesn't this all come to a full circle aosp issue or am I just swimming with sharks?

Radiation from my 4.4.4 gnex
[Samsung Galaxy Nexus] midnightdevil66:
7/26 running like a champ for me. Thanks!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] D1BB:
I too couldn't get past "Google" with a clean flash. Thought it might be the kernel so I flashed one I had on my sd and it booted right up. Seems to be running fine so far, still setting everything up. I'm still on ext4 and using philz touch, but you can give it a shot.

Edit: sorry guys, I was falling asleep and didn't realize it was already determined to be kernel. Disregard my above post.
[Samsung Galaxy Nexus] Rushead:
Toro 8-1th Sample (0x19)

7-16 is running great for me so far.

EDIT: Can't hang with the minimal kernel, tho.
[Samsung Galaxy Nexus] MWisBest:
Everybody who is trying the recent test build:

Try using the stock FML kernel with it (meaning don't flash a different kernel) first.

If it boots, tell me what the /sys/board_properties/revision file contains and that it boots OK.

If it doesn't boot, either flash a different kernel or go back to the 07/05 FML build and then tell me what the contents of the /sys/board_properties/revision, as well as that the test build doesn't boot with the FML kernel.

I really need all the help I can get!

Originally when KitKat came out I was basing FML on AOSP. Eventually I started basing it on Cyanogen Inc. like I had been doing with the 4.3 builds of FML. In late December or early January I switched from basing FML on Cyanogen Inc. to basing it on OmniROM.

OmniROM isn't really based on Cyanogen Inc...

Please see the message I wrote above!

Please see the message I wrote above!

Thanks for the feedback! I am working on getting the kernel more up to speed, but if I can't figure out the not booting thing I'm going to have to revert to the previous kernel. :(
[Samsung Galaxy Nexus] D1BB:
Toro 8-1th Sample (0x19)

Would not boot with stock kernel, tried multiple times. Had to flash another.
[Samsung Galaxy Nexus] JoJoDaClown:
Toro 8-1th Sample (0x19)
[Samsung Galaxy Nexus] mastertech007:
How do I find that info you need?
[Samsung Galaxy Nexus] Rushead:
You need a root file explorer. Navigate to /sys/board_properties/ and open revision as a text file.
[Samsung Galaxy Nexus] mastertech007:
Did not boot 7-26 with stock or Dirty V kernel (latest). Stuck at GOOGLE. Restored 7-5 with stock kernel.

Toro 16GB 8-1th Sample (0x1a)
[Samsung Galaxy Nexus] Rushead:
Google boot freeze on 7-26

Toro 8-1th Sample (0x19)
[Samsung Galaxy Nexus] dbt816:
No boot with 7-26... loaded SmittyV kernel and it boots fine. Revision file is "Toro unknown(0x1a)"
[Samsung Galaxy Nexus] MongolPup:
7-26 doesn't boot with included kernel, Toro 8-1th Sample (0x19)
[Samsung Galaxy Nexus] MongolPup:
Also is anyone else having terrible 3G/4G hand offs with the last two beta builds? I waited a while to see if it was usage conditions but now I know for me the build from the 5th is the last one that didn't have the problems I'm having.
[Samsung Galaxy Nexus] Rushead:
No problems on 7-16
[Samsung Galaxy Nexus] midnightdevil66:
No issues here on 7/26.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] MWisBest:
Hey guys, have some news...

I'm going on a vacation with my father and I won't have any sort of access to technology for about a week or so. We're going up to the Boundary Waters, basically a canoe trip in the middle of nowhere for about a week.

I was hoping I'd have a new FML release out before this, but unfortunately I ran short on time. I don't even have time to reply to questions and stuff in the FML thread(s), I'm leaving in -1 hour!
[Samsung Galaxy Nexus] MongolPup:
Alright, thanks guys.
[Samsung Galaxy Nexus] rice923:
Dads before bros?! Blasphemy
[Verizon HTC One (M7)] TechSavvy2:
Like the title says, I have my HTCDev Unlocked VZW One listed on Swappa. Love the phone, love roms, etc etc, but like many others I'm disappointed with the shutdown of unlocking the bootloaders. And FYI, yes, I bought the phone with the knowledge of them being unlockable (checked 5 minutes before I bought), then they got locked down, and I was gonna return it because of that, but I know many people would be upset me with taking back "one of the six" unlocked phones to Verizon. Just doesn't seem right, it could be in a developers hands.

In any event, I didn't necessarily wanna start a debate of f-this phone or that, but I'm looking to go in the direction of the most developer friendly phone, current or upcoming (preferably upcoming). At the moment, I'm leaning Moto-X Dev Edition. I am happy they did Dev Editions and am a strong supporter of them. What I'm wondering is if it will get the dev support on our carrier it should, with only having dev editions vs all of em being unlocked. LG G2 - bootloader status unknown (past devices) as well as past-time hating LG devices, as well as hating touchwiz (yes, I made that reference on purpose). However, I'm also considering the Note 3 (still hating touchwiz) dev edition. As much as I disliked touchwiz, the Note 2 was probably my favorite device to date.

In any event, like most of the users on here, just wanting to get some feedback on dev-friendly devices that VZW will be seeing. AND NO, I'M NOT SWITCHING CARRIERS.
[Verizon HTC One (M7)] cstrife999:
Get a GNEX that's about it.
[Verizon HTC One (M7)] jntdroid:
A lot of S4s still come with mdk out of the box. Even though ME7 is locked tighter than fort knox, if you get one on mdk, I think that's about as dev friendly as it gets on Verizon right now.

To be totally honest, you might want to be patient and wait a bit. The One is one of, if not THE most popular phone in the world, with crazy dev support on other carriers. I'm not sure how popular the X will be, especially since its getting mixed to good reviews so far and not nearly as widely available as the One and S4 are. If the One gets unlocked or S-off, it could very well be the most dev supported phone on Verizon very quickly. But maybe it's that "if" part you're tired of dealing with.

Sent from my phone
[Verizon HTC One (M7)] rmaccamr:
It's only a matter of time. Every device, to my knowledge, has eventually had an exploit or workaround. Might have to wait until Verizon pushes an OTA but it will eventually happen. And again, to my knowledge, I believe the One is the only quad-core on Verizon at the moment, so even if it leads the pack in that respect, it will be a while until it's matched and bettered in terms of raw processing capability. If you get a quadrant on it, it's into the 13,000's, it'll make you feel better about holding onto it.
[Verizon HTC One (M7)] jntdroid:
I hate making assumptions like that, but that's my hope as well. And the S4 is quad core, same processory, clocked higher than the One.
[Verizon HTC One (M7)] 91ludesit:
Are the really only 6 that got unlocked? I'd have thought it was more than that.

I was at Verizon when they opened to purchase mine and went right back to work and unlocked it.
[Verizon HTC One (M7)] Vidfreek:
So its been out for a week or so tops and you cant wait to see what happens? While I enjoyed my Galaxy S3, the One is a far superior phone in build quality and even though the S4 is a tad bit better in specs, its still crappy plastic and feels cheap. I can see if you still have a chance to take it back and exchange it free and clear, I still have a week myself, I'd like to wait and see what happens with this phone. Honestly there is nothing else for me to go to, I dont care about the MotoX even in Dev form because I dont see it as being any better than what I got, same with the Droid line in general, they are all locked down as well and have been for some time. If I would think about the S4, there is no chance I would get one that I could do anything with and its back to vanilla unrooted again anyways. The LG-G2 looks really nice but their reputation for phones isnt all that great.

So I think I'm just going to stick it out and see what happens, if I had an already unlocked One there would be no way I'd be switching at this point.
[Verizon HTC One (M7)] josh995:
There were more than 6. I'm not sure what OP means by that :P
[Verizon HTC One (M7)] cstrife999:
It's a joke from the other thread. I'm one of the illustrious 6 I guess lol.
[Verizon HTC One (M7)] chip.hughes:
Just bought your phone, can't wait to get it!
[Verizon HTC One (M7)] thepolishguy:
There are 20 people on the unlocked list here...

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

And I am sure there were more who didn't see it or didn't bother posting in it.

As far as the OP as concerned - I guess it would depend on your android preferences. In the last 6 months I went from...

1. Gnex - absolutely loved it - but dat battery life and after owning 18 months I just wanted a new phone :/

2. Note2 - way to big (obligatory "that's what she said), the screen looked washed out to me. I think 720p at that size not so good maybe, hated touchwiz.

3. GS4 - beautiful screen - ridiculously awesome screen, awesome battery life. If I hadn't have taken the update (stupid, stupid, stupid me) maybe would have kept it. But again - I hate touchwiz. TouchWiz really is a train wreck. I mean 4 tabs in the settings page? And I HATE physical buttons!

4. HTC One - build quality was out of this world, screen is awesome. Speakers awesome (but I always connect to bluetooth sound so...) Battery meh, Sense 5 meh. Better than TouchWiz but not as good (for me) as vanilla Android). Camera meh (in my opinion), I don't care what you call your pixels if there's only 4 of them - meh. PHYSICAL BUTTONS - why?

I was Dev Unlocked on the One - but what does it matter if no one else is? I don't have the skills to pay the bills. So the One is on its way to NYC via Swappa.

5. MotoX - love it. Will sell it and buy the Developer Edition when it releases. I just love vanilla android. The phone feels good in your hand - like the One. Even though it is plastic - it doesn't feel like Samsung plastic (hard to explain). But I would say if the build quality of the One was a ten then the X would be a 7 in comparison. Great size. Good size screen in a smaller package because of bezel elimination. Camera meh. Battery. So far so good. But I haven't had it 24 hours so we'll see. Development though is meh right now as well. But I can live with less Development on the MX because it comes pretty much the way I want it whereas the with the One I was hoping for an AOSP build. Oh - and no physical buttons!

So yeah. That's my ramblings.
[Verizon HTC One (M7)] TechSavvy2:
Haha, yeah, that's what I'm thinking right now too. Probably gonna shoot for Moto X Dev Edition, was gonna do exactly what you did, but I had a backup GNex laying around and figured I could crack flash in it for a while till Dev edition releases.

I'm a phone freak....I've got a problem, I admit. I've seriously had 20 phones over maybe the 2 years. Only 1 at a time, and even bought same phone at different times. I gotta quit this, haha.

And yeah, the "6 of us" thing was a joke from cm10.2 thread. Didn't even see that other thread about actually unlocked people.
[Verizon HTC One (M7)] jntdroid:
You can take me off that list... had to replace it b/c of a bad volume rocker... :(
[Verizon HTC One (M7)] TechSavvy2:
:good::good::good::good:

Can't ship till Tuesday cuz of the holiday obviously.

Feel free to pm me if you need help with anything on it. I'm on here a lot.

EDIT - This message brought to you from......your phone........lolz. Gonna reactivate the GNex now though, no worries, haha
[Verizon HTC One (M7)] thepolishguy:
Your listing reminded me that I needed to email my buyer his unlock code. Completely forgot about that.

I gave my Dad my Gnex or I would have done what you did. And yea - I have got the same problem as you do. I am (in all seriousness) actually getting tired of being so tech addicted. I am going to TRY and just get this Dev Edition X and call it quits for at least 18 months (famous last words). Unless Verizon actual gets another Nexus which will probably never happen.
[Verizon HTC One (M7)] jntdroid:
If you were really trying to ditch the tech addiction, you should get the locked X, not the dev edition. ;)

Sent from my phone
[Verizon HTC One (M7)] Hand76:
Sooo I am waiting to see if this device gets rooted and a black one becomes available through Verizon.

But at this point as much as it pains me to do so I will probably wait till all the fall phones cards are on the table and make a decision come October what phone I should get. Htc One? Developers Edition Moto x? Or (the way I think I am currently leaning) a Nexus 5?
[Verizon HTC One (M7)] thepolishguy:
Good point. I already have the locked X though. But I won't be able to pass on the Dev Edition. Just in case. Especially since I paid retail for the locked X. I am going to Swappa it and fund my Dev Edition.
[Verizon HTC One (M7)] jntdroid:
Gotcha - how are you liking it vs the One? And is it Verizon?

Sent from my phone
[Verizon HTC One (M7)] thepolishguy:
Yes - on Verizon.

I'll tell you - after coming from the GS4 and the One I was really worried that the screen would bother me. But I seriously don't notice any difference. But here's the thing. I am not super picky about some things. I am mostly picky about software (vanilla versus OEM skins). I love vanilla Android and I love on screen buttons.

I also decided (and everyone will have their own opinion on this which is fine) that as far as a pocket-able device; I don't want a really big device. I have a Nexus72013 to cover that. The One is not bad at all. But it is a little on the tall side. But like the Note2 and Note3 - I just don't need that size. What's nice about the MX is that it kept a pretty good screen size but eliminated a lot of bezel.

So for me - I love the MX
[Verizon HTC One (M7)] jntdroid:
Good to know. Been trying out the Maxx for the past week alongside the One. Finally sold the S4, but loved it as well. Love the Maxx battery life, but the bigger screen makes the resolution difference more noticeable, and it's a beast size wise - would definitely be nice to have a phone that is more ergonomic. If I can get used to the camera, I'll be sold, and probably get an X as long as it has better battery life than the S4 or One.

Edit: what color is the one you're selling?

Sent from my phone
[Verizon HTC One (M7)] thepolishguy:
Ill be selling a black on black version. But I don't think the battery life is going to be as good as the GS4. Could be wrong. I think the MX battery will be better than the HTC One (which was only decent for me).

But mine won't be available until the Dev Edition drops and who knows when that will be.