yashsingh1/xdaforums huggingface dataset:
[Nexus 9 Android Development] TotallyAnxious:
Well the thing is that sometimes it works and sometimes it doesn't. I was having a streak of crashes so I was able to grab a log. It's working fine now. Double tapping quickly isn't causing a crash.
[Nexus 9 Android Development] buffal0b1ll:
Something to do with this bug maybe? http://www.androidpolice.com/2014/1...ws-random-cards-after-youve-cleared-them-all/
[Nexus 9 Android Development] wantowan2:
A page or so back you mentioned that you "dirty flashed" a gapps package or something with, no issues? lol

I've been compiling several Roms for some time now. Not that that is anything other than that in that time I have never done it, recommended it or seen it ultimately result in anything other then grief. Some youngster will come along, see all the flaming on the board around reading and get to that bit about how dirty flashing fixed something.

Trust me. You might get away with something for a day, two or five. It never lasts.

Just last month I snagged a kernel source from an excellent top respected Dev. Previously unposted but heavily developed. It compiled like a dream with just a couple of the conventional hooks for my n5. I did it twice (well, more but two finals) , boot.IMG and inline with the DU44 I usually do. Flashed the ROM package and was blown away. Way out paced his regular kernel and couldn't understand what was holding him up from posting a version.

All was well and I went with it as is for 5 or 6 days, no change to anything. Nothing. Really slowly. An fc. Then 2. Weird, almost like a virus it started wiping out all over the place. Because it was so slow and with no change's it took me a while to realize that I just had to hard reset and start over.

I guess there is no end to me reacting to you dirty flashers. That's easy to find on here... lol.

If the package you used was anything close to an official one, it probably did the wiping anyway. ?

Besides, what is gained by not wiping cache and dalvik or whatever and then flashing? Maybe a minute with this CPU. It means, however, you come back here with useless feedback. Fact.
[Nexus 9 Android Development] buffal0b1ll:
Of course I wiped cache and dalvik. That goes without saying.

By dirty I mean I didn't wipe system or data before pushing the 11/17 Gapps over the 11/15 Gapps.

I guess I should have just said I had no problems flashing the new Gapps over top of the 11/15 setup. Wiped cache and dalvik and all's peachy.
[Nexus 9 Android Development] Max128:
Hi, Thanks is a great rom, waiting for CM12.

I found a bug when i installing the ROM with TWRP. The installation of the ROM does not launch because is said for flounder,

I was forced to changed the updater-script and replace the flounder with volantis this:

( getprop("ro.product.device") == "volantis" || abort("This package is for "volantis" devices; )

And is working after..
[Nexus 9 Android Development] chefb:
Still peeping in to see who used TWRP to flash the rom and gapps? Thanks
[Nexus 9 Android Development] craigacgomez:
Yes, I can see that. And that is wrong in TWRP. ro.product.device=flounder, not volantis. ro.product.name=volantis. Maybe [MENTION=912474]Dees_Troy[/MENTION] can answer that!
[Nexus 9 Android Development] Max128:
Exactly! Ok so is the TWRP the problem, For now changed the name in updater-script in the rom is enough for installed.

By the way .. why it has two code names? the difference between flounder and volantis is?
[Nexus 9 Android Development] Win_Wizard:
I think one codename is htc's internal codename and the other is googles codename for the device
[Nexus 9 Android Development] ilatimer1:
Is it just me or does this build run better that Google's official build?
[Nexus 9 Android Development] Max128:
Google has not yet fixed the bug when the charger is connected the screen lights up and extends to two seconds after a short time .. That happening it on all nexus devices with Lollilop.

I specify only with the french canada language..

craigacgomez: Can you look this?
[Nexus 9 Android Development] buffal0b1ll:
Day 3 using this ROM. Loving it immensely. Thanks [MENTION=2322613]craigacgomez[/MENTION] !
[Nexus 9 Android Development] USBhost:
+1 Aye there
[Nexus 9 Android Development] D-m-x:
Me too, but I'd like to ask again, is anyone's Vibration working in 3rd Party Apps? Vibration works for me only if it's triggered by the system, not in Games or 3rd Party Keyboards e. g.
[Nexus 9 Android Development] stratman71:
This rom is working great, it even fixed the compatibility issue with XCOM:Enemy Enkown, which was driving me nuts. (not sure if it was the rom or turning off encryption that fixed it!?!)
[Nexus 9 Android Development] ilatimer1:
Just wondering if there is any update to this build or is one even needed?
[Nexus 9 Android Development] cmplaya:
installing

Can we flash in twrp instead of the aosp recovery?
[Nexus 9 Android Development] buffal0b1ll:
I don't see why you couldn't. Try it and let us know:)
[Nexus 9 Android Development] oRAirwolf:
I just tried flashing this ROM using TWRP. It says that this ROM is for Flounder devices and wont work on my Volantis.

Gonna try the fastboot method now...

TWRP logs:

And everything is F'd now....I will report back
[Nexus 9 Android Development] djslyda87:
Same thing happened to me, i couldnt get it to flash via TWRP, fastboot or flashify.......

the fix: you need to open the Rom zip and open the META INF folder, open COM folder, open GOOGLE folder, open ANDROID folder and then open the updater script with notepad, you need to change a few of the entries (look back a page or 2 to find out but basically all youre going to do is change the words from flounder to volantis) and then go to FILE, SAVE, if it asks you to update the archive blah blah blah then click YES.

Try flashing the zip you have just edited and it should work correctly, on first boot i got a bootloop so i rebooted into recovery and flashed again BUT this time after it had flashed i wiped DALVIK/CACHE. Lollipopalooza booted up fine this time.

Hope this helps as it took me a couple of hours of pulling my hair out to get this slick rom to work :)
[Nexus 9 Android Development] buffal0b1ll:
Read back a few pages. A user reported this and a workaround.
[Nexus 9 Android Development] tyvar1:
Here is the answer :)
[Nexus 9 Android Development] oRAirwolf:
Thanks for the reply. I decompressed the zip, changed the updater script, and then re-zipped the image. I then got the error "Error flashing zip" and then the path to the file. Do I need to make this change through a ROM kitchen? I am pretty well versed with Android/Fastboot/ADB/etc, but I have never actually modified a ROM before. If I do need to re-do this through a Kitchen or whatever it is called, can somebody point me to the best/most supported one? I will try and figure it out on my own.
[Nexus 9 Android Development] mpmilestogo:
I believe that [MENTION=5501864]USBhost[/MENTION] created a modified twrp in the recovery thread that fixed the issue with twrp. May want to check there. I have not tried it but I flashed it using flashify. Been busy of late with stuff.
[Nexus 9 Android Development] oRAirwolf:
I ended up just flashing the ROM with the adb sideload method in the OP...which I should have just done all along.

Here is a link to the [MENTION=5501864]USBhost[/MENTION] version of TWRP that you mentioned for anybody else here http://xdaforums.com/showpost.php?p=56894821&postcount=87
[Nexus 9 Android Development] Max128:
Actually, do not decompressed the zip because it removes the signature. Just drag your new updater script in the zip and is working. As I said above.
[Nexus 9 Android Development] craigacgomez:
I've been a bit busy the last week and did not get time to do much other than push all my changes to GitHub. I hope to be able to spend time this week. I am aware of the TWRP issue (yes, it's not an issue with my ROM), but I will have a modified installer script with the next release to circumvent this issue.

EDIT: Just to be clear about this whole flounder/volantis naming confusion...

1. The board name and device name is flounder (for both the WiFi and LTE models)

2. The product name for the WiFi model is volantis or volantisf. I don't know the product name for the LTE model yet. And I don't know how volantisf differs from volantis.

3. Device name check in the installer script is, and should be flounder, but the identifiers in TWRP are looking for volantis, so it fails.
[Nexus 9 Android Development] USBhost:
Just remove that check completely
[Nexus 9 Android Development] craigacgomez:
I would rather not. It's a good safeguard against accidental cross-device flashing.
[Nexus 9 Android Development] USBhost:
you are right

looks like i need to edit TWRP again lol

to say volantis now
[Nexus 9 Android Development] craigacgomez:
Nope. I will make the installer script assert work with both flounder and volantis.
[Nexus 9 Android Development] USBhost:
O nice
[Nexus 9 Android Development] nmalready:
Encryption

I'm having a heck of a time removing encryption on this rom. I recovery says it's removing encryption but when I go to security in settings it always says encrypted.

I have successfully done this on stock but can't seem to get it on this rom. I'm running twrp 2.8.1.0 and have tried fire and ice kernel.
[Nexus 9 Android Development] USBhost:
Do a factory reset from fastboot

Also

Can you give me your

fstab.flounder

Or just format data to ext4 then back to f2fs
[Nexus 9 Android Development] nmalready:
Ok, working on that and on accident I wiped system:crying: I will try and one last time and give you fstab.flounder thanks!
[Nexus 9 Android Development] USBhost:
Make sure you flash my kernel

Then give me your fstab.flounder

Trying to figure out what's going on
[Nexus 9 Android Development] nmalready:
here's fstab, still not working. thanks again!
[Nexus 9 Android Development] USBhost:
Give me the output of

su

cat /proc/version

Are you sure you flashed FIRE-ICE

If you did give me the recovery log of then you flashed it
[Nexus 9 Android Development] nmalready:
Sorry this takes me so long, I'm new to this
[Nexus 9 Android Development] USBhost:
Ok

So the kernel did flash ok thats good

Now can you do this too

And give me the output

su

cat fstab.flounder
[Nexus 9 Android Development] nmalready:
recovery log
[Nexus 9 Android Development] USBhost:
Ty but thats not the log but np

Can you give me the output

Of

su

cat fstab.flounder
[Nexus 9 Android Development] nmalready:
Here you go.
[Nexus 9 Android Development] USBhost:
Got some good news

Every thing looks good

Now just do a factory reset

And you should be unencrypted
[Nexus 9 Android Development] nmalready:
OK! resetting now!
[Nexus 9 Android Development] USBhost:
Just a reset nothing else
[Nexus 9 Android Development] auggie246:
I am wondering why is this LRX21T, isn't LRX21T for nexus 4, and 21R is for nexus 9
[Nexus 9 Android Development] nmalready:
Ok, so I did a factory reset from fastboot, it booted into twrp no problem, no errors, said it's message about decrypting, ect.

Booted into rom, went to settings and no dice, still says encrypted. Tried factory reset from setting and straight from twrp, same thing...
[Nexus 9 Android Development] USBhost:
ok flash this TWRP recovery

hopefully fixed the format problem that always encrypts data as doing a reset

and its running the FIRE-ICE kernel R10 cheers lol

https://s.basketbuild.com/devs/USBhost/Nexus 9/recovery/
[Nexus 9 Android Development] nmalready:
Finally!!:highfive: Fixed. Thank you!
[Nexus 9 Android Development] auggie246:
1 feature request if possible. Battery %
[Nexus 9 Android Development] joshndroid:
nice rom, after fixing the assert check in updater script (should have read thread before hand, atleast i know twrp backup works and usb otg in twrp lol) flashed fine. Haven't run into any dramas as yet. 1+ on adding the ability to get battery percentage.
[Nexus 9 Android Development] craigacgomez:
Hopefully by the weekend... if I don't get caught up with real work issue during the Thanksgiving weekend (story of my life as a software architect)

I do plan to add this... hopefully with the next release.
[Nexus 9 Android Development] oRAirwolf:
Thanks again for making this ROM available to us. I understand from your OP that you made this ROM for yourself and you are being kind enough to let the rest of us use it as well. I genuinely appreciate that.
[Nexus 9 Android Development] _Infamous_:
Here is a app to enable battery % https://play.google.com/store/apps/details?id=net.edavid93.kitkat_battery_percentage
[Nexus 9 Android Development] Skid71:
Disable Encryption

To disable encryption:

After flashing Lollipopalooza, before booting system, while still in recovery:

Factory reset

Then reboot system

Just confirming before my first Nexus device arrives tomorrow.

Thank you
[Nexus 9 Android Development] joshndroid:
I get system ui fc when hitting the clear all recents button in the recents section... No big deal just feedback
[Nexus 9 Android Development] USBhost:
I wonder why I don't get that
[Nexus 9 Android Development] joshndroid:
Seems to be intermittently... I'll try to get a log next time it occurs... It has happened 3 times... After a reboot and try again it does not fc
[Nexus 9 Android Development] craigacgomez:
I do know about the "occasional" SystemUI FC... hopefully fixed, but not yet sure...
[Nexus 9 Android Development] CaspaTheGhost:
I'm sure its directly related to this LP bug.

http://www.androidpolice.com/2014/1...ws-random-cards-after-youve-cleared-them-all/

Sent from my Nexus 9
[Nexus 9 Android Development] craigacgomez:
Woohoo!! New version with some nice features... (A lot of credit to rascarlo, SlimRoms and CyanogenMod)

And the ThunderKat exclusive feature is now here in Lollipopalooza... Movable navigation bar buttons... You can align the navigation bar buttons to the left, right or centre... particularly useful in landscape mode.... Completely rewritten in a much better way!!

Hopefully, the clear all recents bug is fixed as well...
[Nexus 9 Android Development] pantmunu:
Hot damn !!!
[Nexus 9 Android Development] USBhost:
Cheers man will flash soon!!!

And ntfs awesome
[Nexus 9 Android Development] D-m-x:
Has anyone flashed it yet, i tried but TWRP wouldn't flash it (kept stuck forever while flashing) and rendered my /system completely useless, even TWRP reformatting didn't work so i had to flash the Factory Image and Recovery to get it working again. I'm just wondering if anyone has run into the same Problem (MD5 checked of course, everything fine). Came from the last Version btw.

Also [MENTION=2322613]craigacgomez[/MENTION]: Are you going to provide an Updated SuperSU ARM 64 or should we use the Play Store Version?
[Nexus 9 Android Development] craigacgomez:
Play Store version is fine... or the official recovery version recommended
[Nexus 9 Android Development] USBhost:
Just give it time it will flash

But lol in about 5-10min

[MENTION=2322613]craigacgomez[/MENTION]

Can you just use busybox to mount system

Also how you mounted system made flashing long just fyi
[Nexus 9 Android Development] D-m-x:
Thanks, i think i was too hasty. It seemed like TWRP had frozen cause the bar stopped moving after a few minutes so i assumed it had hung up. I'll try it again ...
[Nexus 9 Android Development] ilatimer1:
I'm having the same problem flashing this update. TWRP reports that the e signature does not match. I also tried to flash via adb sideload and it fails as well. I have done a factory reset, complete wipe in TWRP and even erased via fastboot.
[Nexus 9 Android Development] zanoli99:
I tried to install. did full wipe and flashed successfully but wouldnt boot. Let boot for 20 minutes but never got past android logo. THanks, cannot wait to try.
[Nexus 9 Android Development] D-m-x:
ADB Sideload told me the same, Signature mismatch. Second try flashing with TWRP suceeded but it took about 10 minutes like USBHost said!
[Nexus 9 Android Development] USBhost:
ROM running awesome

Does the new version have supersu ?
[Nexus 9 Android Development] craigacgomez:
This is how AOSP edify generator works now. I know it takes a few minutes to flash the ROM, and I have yet to look at ways of optimising this.

Turn of signature check in TWRP (TWRP settings, uncheck Zip file signature verification)

It will never have SuperSU bundled because SuperSU is not open-source. Once koush's open-source Superuser is updated to work with Lollipop, that will be bundled.
[Nexus 9 Android Development] ilatimer1:
Now I am getting a failed to mount /dev/block/platform/sdhci-tegra.3/by-name/APP at system: Device or resource busy symlink: some symlinks failed
[Nexus 9 Android Development] USBhost:
O ok ty

Then can you make the rom not install stock recovery

Or it wont?
[Nexus 9 Android Development] craigacgomez:
It won't flash the stock recovery.
[Nexus 9 Android Development] USBhost:
Awesome
[Shield Tablet Q&A, Help & Troubleshooting] kukuthejak:
In the introduction of the Sheild tablet on the page where all the specs are mentioned, it says 1900x1080p. but the correct display is 1900x1200. Am i right?
[Shield Tablet Q&A, Help & Troubleshooting] donutman1324:
Yes. It is 1920 by 1200.
[Shield Tablet Q&A, Help & Troubleshooting] NicoC72:
1920x1200 is the 16:10 version of 1080p. In marketing terms, this tablet is 1080p Full HD because the average consumer doesn't really know about 16:10 and 1080p is pretty universal. Rest assured that the Shield tablet is 1920x1200.
[XDA Assist] Anonymous_Sayan:
My tablet stucked after asus logo animation... Plz help me fix it..
[XDA Assist] prboy1969:
Hello. A quick search did not come up with much for your device. I would advice posting up in the link below. Best of luck.

Android Q&A, Help & Troubleshooting
[Galaxy Note 4 Q&A, Help & Troubleshooting] bat0nas:
How long usually it takes Samsung to adopt the new Android version?
[Galaxy Note 4 Q&A, Help & Troubleshooting] polish_pat:
in my experience, it could be months. As in Q2 2015
[Galaxy Note 4 Q&A, Help & Troubleshooting] ozaghloul:
Knowing Samsung it might not be till end of summer 2015 (if you are lucky).
[Galaxy Note 4 Q&A, Help & Troubleshooting] bat0nas:
Hrrr
[Galaxy Note 4 Q&A, Help & Troubleshooting] iridaki:
There have already been two preview builds for the S5, both shown by Sammobile on YouTube. Which means they are working on it and they're almost there. I would expect an update closer to the end of the year or at the beginning of the next.

iR¡D@k!* from i9505 via Tapatalk 4
[Galaxy Note 4 Q&A, Help & Troubleshooting] ozaghloul:
Meanwhile, the good people at LG are releasing Lollipop for the LG G3 this week. Samsung is always way too slow with updates, for no acceptable reason.
[Galaxy Note 4 Q&A, Help & Troubleshooting] Lodix:
G3 won't get Android 5.0 this week.
[Galaxy Note 4 Q&A, Help & Troubleshooting] bat0nas:
Android in G3 is not so heavily modified than in Samsung phones. Maybe that's the reason.
[Galaxy Note 4 Q&A, Help & Troubleshooting] ozaghloul:
Yes they will get it this week, in fact people already have it.

http://phandroid.com/2014/11/08/lg-g3-lollipop-update-official/

And motorola already released it for the Moto X.
[Galaxy Note 4 Q&A, Help & Troubleshooting] Lodix:
I don't see any word of LG supporting what you say.
[Galaxy Note 4 Q&A, Help & Troubleshooting] ozaghloul:
http://www.lgnewsroom.com/newsroom/contents/64765

Enough proof for you?
[Galaxy Note 4 Q&A, Help & Troubleshooting] SAVVAS.:
I am pretty confident/optimistic that we will have the update during Nov-Dec, 1-2 months from now:o

So far we have seen 2 leaks of Lollipop for S5, 1 leak of S4, so imagine at what level the newest flagship of Samsung is;)

Even more, all companies are promoting fiercely their update plans, so Samsung should be at least worried and thus speed up their game.

Lastly, last year we had the same case as with Note 3, it was released with 4.3 Jellybean and it received the 4.4 Kitkat update in early January.
[Galaxy Note 4 Q&A, Help & Troubleshooting] flyhighx:
The best news relateed to this is that Chainfire was able to root Lollipop on the Nexus 9. It is encouraging that if you have an unlocked bootloader, it seems likely that there will be root for Android 5.
[Galaxy Note 4 Q&A, Help & Troubleshooting] Lodix:
Yes, thanks :P
[Galaxy Note 4 Q&A, Help & Troubleshooting] mrnovanova:
According to this article it's late November early December.

http://www.techtimes.com/articles/1...e-note-3-galaxy-s5-and-s4-release-details.htm

But I wouldn't hold my breath.
[Galaxy Note 4 Q&A, Help & Troubleshooting] polish_pat:
As I mentioned, don't expect anything before a few months. I estimate q2 2015 but this article seems to say February 2015

http://m.christianpost.com/news/and...samsung-galaxy-s5-scheduled-for-2015--129316/
[Galaxy Note 4 Q&A, Help & Troubleshooting] iridaki:
Are you joking? There are builds for the S5 and the S4, the latter being almost 2 years old now! There is no way the the Note 4 will get an update in "Q2 2015". And the article you linked to has no substantial evidence or insight. On the other hand, we know Note 3 was released with 4.3 and got an update to 4.4 in January, so it's not far fetched to think the Note 4 will be treated the same way.

iR¡D@k!* from i9505 via Tapatalk 4
[Galaxy Note 4 Q&A, Help & Troubleshooting] ozaghloul:
I hope you are right, but I highly doubt we will get it before end of Q1-2015. Yes there are builds for many phones, but Samsung tends to take their sweet time coming up with a final draft. I suffered plenty with the Note 2 and Note 3 (still on 4.4.2 until now). Maybe the fact that almost every manufacturer other than samsung will have Lollipop before end of the month might make Samsung move faster (but I doubt it, because they know that most of their end users aren't on XDA and don't know lollipop from lollygag).
[Galaxy Note 4 Q&A, Help & Troubleshooting] iridaki:
What's really funny -and to be frank, quite sad- is how we use words like "suffer" when we explain how we feel about waiting for an update. It's a phone. :cool: Save your capacity to suffer for things that actually matter.
[Galaxy Note 4 Q&A, Help & Troubleshooting] polish_pat:
Maybe Samsung will see this and we'll get the update this week........or in Q4 15[emoji13]