yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] ! .ĐΛЄMØИ. !:
Ok mate thanks I will try it, BTW what kernel is that? Just modified Elementalx or Blissful?

Thanks.
[Nexus 7 (2013) Android Development] blueyes:
X from my earlier test build on deb. Just not 5.1 tc. Its a 4.9 tc.

---------- Post added at 10:43 PM ---------- Previous post was at 10:41 PM ----------

Blissful is only on Shamu. Flash mine or elementalx and you'll do fine.

---------- Post added at 10:44 PM ---------- Previous post was at 10:43 PM ----------

Blissful is only on Shamu. Flash mine or elementalx and you'll do fine.
[Nexus 7 (2013) Android Development] ! .ĐΛЄMØИ. !:
Ok I flashed your boot.img and got boot loop like 0830 build. :(

I wiped all (except internal) then flashed BlissPop, Slim Gapps. And then boot.img via ADB. Is flashing boot via ADB ok? I think I did it right.
[Nexus 7 (2013) Android Development] blueyes:
Should be. Can you download elementalx cm 4.03 and flash in twrp? Use a usb-otg

---------- Post added at 11:01 PM ---------- Previous post was at 11:00 PM ----------

Or any kernel. I'll have to work on toolchain.

---------- Post added at 11:04 PM ---------- Previous post was at 11:01 PM ----------

Its a kernel issue. Sorry. For now you'll have to flash a kernel after rom
[Nexus 7 (2013) Android Development] ! .ĐΛЄMØИ. !:
Just flashed that and I'm booting OK now.

EDIT:

Lol thanks for help anyways mate, this must be a headache for you. :(
[Nexus 7 (2013) Android Development] blueyes:
Re wipe. Flash ROM , gapps then kernel (elementalx 4.03cm).

---------- Post added at 11:11 PM ---------- Previous post was at 11:06 PM ----------

Becoming. Lol

---------- Post added at 11:14 PM ---------- Previous post was at 11:11 PM ----------

What process did you do?

---------- Post added at 11:15 PM ---------- Previous post was at 11:14 PM ----------

BTW you guys are SO much more understanding than the Shamu thread.
[Nexus 7 (2013) Android Development] ! .ĐΛЄMØИ. !:
Heh apply ice to head if necessary. :D

And thanks again for the builds.
[Nexus 7 (2013) Android Development] quickdraw86:
Okay, 8-27 to version 4.0 through twrp after wiping cache and dalvik is stuck at google splash.

Clean flash of 4.0 through TWRP doesn't boot either.

Clean flash of 4.0 with the boot.img you supplied is a bootloop.

Clean flash of 4.0 with elemental x 4.03cm DOES BOOT, and seems to run okay. Bliss 4.0 is nice.

Thank you for trying so hard to fix the kernel issue, and for your work on Bliss in general, really like your builds, I'm sure you'll figure this out.
[Nexus 7 (2013) Android Development] blueyes:
Thank you
[Nexus 7 (2013) Android Development] sgs9:
Dirty flash

Thank you :)

Dirty Flash over 2015-08-25 work too.
[Nexus 7 (2013) Android Development] sabbeer:
Got bootlop on n7 deb...stuck on google screen....
[Nexus 7 (2013) Android Development] sgs9:
You read some of this thread near your comment?
[Nexus 7 (2013) Android Development] blueyes:
on what build? I didnt push a deb 4.0 yet because of the kernel issues. I can but you'll HAVE to flash cm4.03 elementalx after gapps until I fix the toolchain. The 7 isnt liking the tc jump...
[Nexus 7 (2013) Android Development] blambo:
Dirty flashed Deb 4.0. Flashed EX 4.03cm as usual. Booted OK but slow, then had bad Google play loops and gmail frozen. Rebooted, flashed tk-micro modular gapps 5.1.1 20150824. All good.
[Nexus 7 (2013) Android Development] HippoMan:
Questions about flashing 4.0

I'm soon going to try flashing 4.0, and I have a couple questions:

1. If I flash the kernel supplied here, should I flash it before or after installing the 4.0 ROM?

2. If I decide to flash ElementalX, is it the AOSP or CAF version.

Please forgive me if one or both of these questions have been already answered here. I'm getting a little lost in all of the recent postings.

Thank you very much.

.​
[Nexus 7 (2013) Android Development] sgs9:
ROM. Gapps. CM Kernel 4.03
[Nexus 7 (2013) Android Development] HippoMan:
Thank you. And if I dirty-flash, I assume that I don't need to redo the Gapps, correct?

.​
[Nexus 7 (2013) Android Development] sgs9:
Flash again gapps and "Wipe Dalvik Cache" und "Wipe Cache"

Its here somewhere in the thread ;)

For me it work in this style, and the ROM is now very smooth and quick.
[Nexus 7 (2013) Android Development] HippoMan:
Thanks. I'll redo Gapps. And I always wipe those two things when dirty flashing something new.

I'm sure all of this is buried in the thread, somewhere. Sorry ... it's just hard for me to keep up with all this today.

One more question: does anyone have any thoughts about what might be different between the kernel that's supplied here and that ElementalX kernel ... in terms of features, performance, etc.? Or is it just "six of one, half-dozen of the other"?

.​
[Nexus 7 (2013) Android Development] sgs9:
In the moment only elementalX work with flo 4.0.

sorry about my english.
[Nexus 7 (2013) Android Development] HippoMan:
Oh, OK. Thank you.

Your English is fine!

---------- Post added at 18:21 ---------- Previous post was at 18:18 ----------

... and one last question: if I install xposed, should I do it before or after the kernel?

.​
[Nexus 7 (2013) Android Development] sgs9:
first reboot, then xposed with twrp
[Nexus 7 (2013) Android Development] HippoMan:
Well, I just decided to dive in and try everything. Here's what I did, and it all worked.

Starting point: 08-31 3.9 ROM.

1. Download 4.0 ROM, ElementalX, proper Gapps to my desktop machine.

2. Go into TWRP on my flo device.

3. Go to Advanced->ADB Sideload.

4. Wipe dalvik and cache.

5. Flash the 4.0 ROM.

6. Back in sideload, flash these Gapps: Slim_zero_gapps.BETA.5.1.build.0.x-20150901.zip

7. (optional) Back in sideload, flash this Gapps add-on (to manage DPI changes): Slim_ADD-ON-5.1-MULTI_DPI-20150901.zip

8. Back in sideload, flash the ElementalX 4.03 CM kernel and answer all the setup questions.

9. (optional ... xposed is not needed) Back in sideload, flash the latest xposed, This is rovo89's latest version: xposed-v72-sdk22-arm.zip

10. Reboot

Everything came up fine. Apparently, I didn't need to load xposed after an interim reboot.

.​
[Nexus 7 (2013) Android Development] blueyes:
OK. That's my test build. Didn't know I pushed it.
[Nexus 7 (2013) Android Development] sgs9:
I am not so cool ;) , Most of the time I Make a nandroid From the running System before I Flash Xposed to be care it work well. Some times before it give Problems.

My tablet like big letters :D
[Nexus 7 (2013) Android Development] blueyes:
Thanks for helping out! We've been working on shamu all day. Its 4.0 has several of us brain fried. I finally got it on my phone.
[Nexus 7 (2013) Android Development] sgs9:
Same procedure like yersterday for this ROM with elementalX Kernel?
[Nexus 7 (2013) Android Development] blueyes:
No difference in elementalx, I merged his kernel into ROM. Just having trouble with the coding and going from 4.9 toolchain to 5.1 is a jump itself. That's what's causing boot issues. Make file, toolchain upgrade, a lot of 4.0 commits. Just a lot to mix so to speak. Guess I should of waited on kernel. I'm building now with some cherry-pick that hopefully help. But don't feel bad it took several of us to get shamu to not bootloop on 4.0. I just got mine set. Its just me and Jean (hammerhead maintainer) working flo. I am very thankful for his assistance.
[Nexus 7 (2013) Android Development] blambo:
BlissRom Deb and Flo latest (today): Dirty flash. EX kernel 4.03cm. Gapps install required, this time used Banks (5.x.x-8-18-15). No issues, very nice. Thank you!
[Nexus 7 (2013) Android Development] blueyes:
There is an issue with backup script so if you want to flash update you must 1 wipe caches 2 flash rom 3 flash gapps (issue with script, sorry working on that too its on all devices) 4 flash kernel. You can backup your current kernel in twrp and restore it after gapps instead of reflashing kernel zip. Your choice.... Regards Brian

---------- Post added at 01:10 AM ---------- Previous post was at 01:07 AM ----------

Yes but must reflash gapps because we are losing play services etc.. for some reason, you can restore a backup kernel if you have or do a backup of current kernel....

---------- Post added at 01:12 AM ---------- Previous post was at 01:10 AM ----------

Ahh, you have both devices as well.. Nice Well I have deb and my daughter has flo. Poor thing with my testing on it has her flo..
[Nexus 7 (2013) Android Development] Nic2112:
If I do a clean install of today's build, will that work? (Wipe, install today's daily, flash GAPPS, flash ElementalX CM 4.03 ?

Edit : Works, just a few FCs at first boot.
[Nexus 7 (2013) Android Development] R4e:
I can not get to boot loader
[Nexus 7 (2013) Android Development] blueyes:
hold power and volume down may take a few but it should go to bl

---------- Post added at 08:41 PM ---------- Previous post was at 08:40 PM ----------

Pushing update now, flo is ready and deb is building now. Good news you can use updater and no need to flash kernel. If you use twrp just wipe caches and flash rom then reboot. Dirty should work. I just tested it and running great...
[Nexus 7 (2013) Android Development] blueyes:
https://drive.google.com/file/d/0B5P8eROFCrBLb2laUDlld3AwOUk/view?usp=docslist_api

Just a boot animation I made. Install like a regular app. Activate in themer-boot animation
[Nexus 7 (2013) Android Development] blueyes:
What's the word on last night's build? Good bad OK?
[Nexus 7 (2013) Android Development] Nic2112:
Nothing major to report other than a couple FCs. I don't go nuts with customization so I can't speak for all the settings BlissPop offers but so far absolutely no problems.
[Nexus 7 (2013) Android Development] maigre:
I can't install this latest 4.0 build successfully. First, I downloaded it via the ROM's updater and dirty flashed it as I do with lots of nightlies. On reboot, I got stuck at the black Google logo screen with the unlocked padlock. It stayed like that for 20+ minutes. I wiped the caches and rebooted a couple times with no change. So I wiped system and reverted to the last 3.9. That brought me back to a working device. So I tried it again, this time, flashing Gapps along with 4.0. This after wiping the caches and system. That booted back into another half hour of the Google logo screen. That's where I am now. I may just revert back again. Or maybe I'll even wipe data.. Based on the recent note in #487, I didn't flash a kernel. Maybe that's the issue?
[Nexus 7 (2013) Android Development] HippoMan:
Yes, you apparently need to flash a kernel along with 4.0. Also, it seems to work best when flashed via recovery, not via the updater.

I got 4.0 to work via the following procedure:

http://xdaforums.com/showpost.php?p=62623241&postcount=477

.​
[Nexus 7 (2013) Android Development] maigre:
I'd seen that post. What you did is what I did, except that I didn't sideload the files, I flashed the .zips from TWRP. But I didn't flash the kernel, largely because 713brianp27 later said it wasn't necessary.

I just flashed the kernel and it's booting now. I'm on the BlissPop loader screen, a good sign. :)
[Nexus 7 (2013) Android Development] HippoMan:
Yes, indeed a good sign! The kernel is apparently needed, and I'm glad that made the difference for you.

.​
[Nexus 7 (2013) Android Development] maigre:
I had flashed Minimal Gapps, which was giving me errors, so I flashed Banks Gapps. I was still getting some play store errors, so I clean flashed and started over again. It's all looking good now.
[Nexus 7 (2013) Android Development] quickdraw86:
This is part of a known issue with the backup script... It's being worked on...

http://xdaforums.com/showthread.php?p=62627581
[Nexus 7 (2013) Android Development] blambo:
Latest Deb, 09/10: Hotspot and tethering settings still not accessible.
[Nexus 7 (2013) Android Development] maigre:
Is Live Display a recent addition? I never noticed it until the current nightly, or maybe the one from 9-7-15. I like the color temperature adjustment. Makes the whites look a lot better. I don't think I've seen the ability to tweak color temperature recently on kernels or other ROMs for this or other Nexus devices. Big thumbs up.
[Nexus 7 (2013) Android Development] SHABBYLEA:
Just checking in (10/09 release)...

So far so good, no problems whatsoever, excellent work...

Is this release still tied to EX kernel? (I ask because when I originally flashed I forgot to install EX, so ended up in a bootloop).

Reading back my post, I think I have answered my own question...?
[Nexus 7 (2013) Android Development] conqueror_25:
Can somebody please post a link on the latest build. I'm unable to download it via the OTA Update. Thank you..
[Nexus 7 (2013) Android Development] sgs9:
http://downloads.blissroms.com/BlissPop/Official/flo/BlissPop-v4.0-flo-OFFICIAL-20150910-0907.zip
[Nexus 7 (2013) Android Development] conqueror_25:
I forgot to include on my post. I'm using a Deb N7. I'm sorry. ?

Thank you for your prompt response [MENTION=3165459]sgs9[/MENTION]
[Nexus 7 (2013) Android Development] quickdraw86:
downloads.blissroms.com/BlissPop/Official/deb/

They're ordered, the latest is at the bottom with its MD5 file. Second up from the bottom.
[Nexus 7 (2013) Android Development] conqueror_25:
Thank you very much.. Really appreciate it Mate..
[Nexus 7 (2013) Android Development] sgs9:
My tablet Do not refresh the Website, :D

http://downloads.blissroms.com/BlissPop/Official/deb/BlissPop-v4.0-deb-OFFICIAL-20150910-1719.zip ;)
[Nexus 7 (2013) Android Development] etere1964:
Thanks for the procedure ... al ok except Gapps ... with Slim error about no space in system ... flash Banks 0818 -> OK

Any idea about this issue ???

:good::good:
[Nexus 7 (2013) Android Development] HippoMan:
Glad it mostly worked for you. I can only guess that the out-of-space issue with those Slim Gapps is due to the fact that you may not have much free space on your device, and that the Banks 0818 Gapps are just smaller than the Sim version.

There are a number of different Gapps packages, so the choice of Gapps packages is not critical, as long as you have one that works.

.​
[Nexus 7 (2013) Android Development] ganggreen30:
Why is the 9/14 build from the website boot looping and not working
[Nexus 7 (2013) Android Development] blueyes:
[MENTION=4471805]quickdraw86[/MENTION] , thanks for all your help. New builds are 4.0.1 now. I dirty flashed flo and used open recovery on deb, both worked fine.

---------- Post added at 01:05 AM ---------- Previous post was at 01:01 AM ----------

Which build/device? I flashed both with no issues. Verifying they worked before pushing. So I don't know why you would be looping.
[Nexus 7 (2013) Android Development] blambo:
Confirm: Latest version 09/14 NO boot on deb. Doesn't even get into boot animation sequence. Trying flo next.
[Nexus 7 (2013) Android Development] ganggreen30:
I clean flashed flo newest version. Shoulda just dirty flashed but I was coming from 3.9 8/15 build
[Nexus 7 (2013) Android Development] sgs9:
ups, sorry, "replay" error.

With EX kernel (flo) no problem here.
[Nexus 7 (2013) Android Development] etere1964:
Thanks for the answer : but I think that the problem is not real for space .... with Banks every time is OK , also with last Banks version , instead of Slim (mini or zero) that the issue of space is always displayed .... but there is no problem ... I use Banks :)

Bye :good:
[Nexus 7 (2013) Android Development] ganggreen30:
Any word on why 9/14 flo build won't boot on clean install?????
[Nexus 7 (2013) Android Development] etere1964:
New version 4.0.1 all OK - Dirty flash from TWRP on Deb

1) Wipe Dalvik - cache

2) Install Rom 4.0.1

3) Install Banks Gapps

4) Install EX kernel

5) Wipe Dalvik - cache

6) Reboot

Work like a charm !!!!!

:laugh::laugh::laugh::good::good::good:
[Nexus 7 (2013) Android Development] quickdraw86:
Clean flash on flo for the 9-14 build bootloops. Here's a last_kmsg for the bootloop:

pastebin.com/c2wMh430

9-14 (flo) does boot successfully with elemental x 4.03, just not with the included kernel.

Also, on 9-14 (flo) it seems that network provided time values are not being read correctly.

I live in an area where the time zone is central daylight time, or GMT-5:00, and had to manually select my time zone in date and time settings. Minute issue, but thought of point it out.

Thanks for continuing to work on this, other than the issues I reported, 9-14 works fine.
[Nexus 7 (2013) Android Development] blueyes:
No need to flash elementalx anymore, its already in the ROM and preoptimized for it. Next update just use updater. Updater works great on deb for me but my daughters flo just goes to twrp, so I dirty flashed last nightly. Didn't wipe anything, just flashed. It's running like a charm.
[Nexus 7 (2013) Android Development] ganggreen30:
Still not BOOTING 4/15 flo whatz the deal I even tried dirty flash
[Nexus 7 (2013) Android Development] zynexiz:
I use AllStream to cast my music to dlna speakers, and it worked really well until I upgraded to 5.1.1 and tried this rom. According to the developer, this rom doesn't support "Remote Submix". I also tried AirAudio, without success. Can anyone else confirm this?

Also there's something odd when using screen casting, the screen is casted to the TV, but not the audio. I tried it on the hotel TV, and it worked here before (WiFi casting).
[Nexus 7 (2013) Android Development] sgs9:
[MENTION=6207927]713brianp27[/MENTION]

Please where is the download file from Updates? In the directory "Updates"???

In the directory "Updates" was an old file, Updates program wrote downloaded file from 2015-09-15, and is matched.

Updates program start also only TWRP, I think, while it was every time like this, its normal.

For computer dummy, like me ;) a "Help" in the Updates how it work was fine.

Also the path to the "Updates" was "easy" to find ;) I search first time in "Bliss settings" / "Bliss downloads", right path is Settings / "Over the Tablet" / "Aktualisierungen" in german.

In settings, from Updates, OpenRecoveryScript activ yes, wipe dalvik and cache, do not update from 2015080602 checked on.

Need a special TWRP? Is the same TWRP on daughters and yours?

I love Bliss on my Flo, do not misunderstood, I will only tell, how normal user feel :D

Sorry, this is my best English ;)
[Nexus 7 (2013) Android Development] blueyes:
Settings/about tablet/updates. Use a file manager and remove any old builds in sdcard/Updates folder

---------- Post added at 02:44 PM ---------- Previous post was at 02:42 PM ----------

Use twrp. Updater script was fixed around the time of the 6-2
[Nexus 7 (2013) Android Development] sgs9:
But only if I delete the last downloaded ROM file in the "Updates" it will work in automatic style? :o

I delete , and it went also only in TWRP. No self install? I fail?
[Nexus 7 (2013) Android Development] ganggreen30:
DOES noone care that im saying builds don't boot !!??? Great thanks for the insight and help moderator!!!!!
[Nexus 7 (2013) Android Development] quickdraw86:
The last few pages have outlined at least 3 ways to get flo to boot successfully.

1. Use the updater to get to the latest version from a booting prior version. The updater script has been fixed and is working nicely.

2. Dirty flash the latest onto a booting prior version.

3. I posted that the included EX kernel goes into kernel panic (I.e. bootloop) if you clean flash the ROM, but found that flashing EX kernel separately after ROM installation boots the ROM.

I'll admit that it's somewhat disappointing that the past few versions can't be clean flashed in recovery successfully. IMHO, all ROMs should be able to do that, but there are clearly ways to boot the flo version if you read through the thread... Hope that helps.
[Nexus 7 (2013) Android Development] ganggreen30:
[MENTION=4471805]quickdraw86[/MENTION] I tried all those before I messaged here since I have been doing this stuff since the days of the g1!! 1. Doesn't work it says null update 2.doesn't work for me at all!!! Yikes what's up with the developers????
[Nexus 7 (2013) Android Development] quickdraw86:
9/15, the latest for flo, can be booted. Updater to TWRP results in a bootloop, and dirty flash from 9/14 to 9/15 is also a bootloop.
[Nexus 7 (2013) Android Development] blueyes:
I'll do whatever I can, I apologize for not being able to get to your issue sooner, had some medical issues to deal with.
[Nexus 7 (2013) Android Development] quickdraw86:
I hope you're okay bud. Your health takes precedence over anything else.
[Nexus 7 (2013) Android Development] ganggreen30:
Definitely
[Nexus 7 (2013) Android Development] blueyes:
I did just clean flash flo with no issues. Just rom then gapps.
[Nexus 7 (2013) Android Development] quickdraw86:
I definitely can't clean flash 9-15 flo. I get a boot loop from clean flash, dirty flash, and also if I use the updater to download, check md5, and reach TWRP. The only way I can successfully boot 9-14 or 9-15 is to install elemental x 4.03 CM after I flash the ROM and gapps.

Recovery log:

pastebin.com/hENH0Eiv

Last_kmsg:

pastebin.com/N2tg28Yd
[Nexus 7 (2013) Android Development] ganggreen30:
This looks to be common for most but a few OK for!! Strange.

---------- Post added at 10:51 PM ---------- Previous post was at 10:50 PM ----------

I'm just wanting to see difference from 3.9 to 4.01
[Nexus 7 (2013) Android Development] etere1964:
Installation of last build : KO with OpenRecovery , OK with TWRP but ....

Hello

This is my experience , i have deb :

With last build (20150917-1848) I try to use OpenRecovery (Download and Install directly from Updates) but I've boot loop on Google Logo .

After I go in TWRP and I install ROM (from Updates Dir) + BanKs GAPPS + ELEMENTALX , problem with Google Play Service !!!!

Finally , I've restored a Nandroid (20150910) , and after , from TWRP , I install ROM 20150917-1848 + BanKs GAPPS + ELEMENTALX , all work perfect !!!

Bye

:p:p:p
[Nexus 7 (2013) Android Development] maigre:
I have to flash ElementalX after dirty flashing the ROM, too. I also had to flash it after clean flashing the first, or one of the first 4.0 versions of BlissPop.

On the Updates screen, when there's a new nightly, it used to incorrectly state that the nightly had already been downloaded. That appears to be fixed now. Thanks.
[Nexus 7 (2013) Android Development] blueyes:
I will look it over to see what may be causing issues. I'm just confused as to why I'm not having any.

---------- Post added at 02:20 PM ---------- Previous post was at 01:43 PM ----------

Go into updates/open recovery and disable it then re-enable. Then use updater for next nightly. Also be sure nothing is in your flash after folder

---------- Post added at 02:24 PM ---------- Previous post was at 02:20 PM ----------

I'm going to try something so wait for next update. Sorry guys
[Nexus 7 (2013) Android Development] quickdraw86:
Thanks a lot for the support. I will do as you suggest for the next nightly. I'm certain there was nothing in my flash after folder, and only the nightly I installed in the /updates folder, but I understand why you'd mention that, as it's strange you were able to install without difficulty.

Edit: I see that 9-17 is up, will give it a shot and report back.
[Nexus 7 (2013) Android Development] quickdraw86:
9-17 flo is another bootloop. I made sure I had nothing in /updates/install after. I downloaded 9-17 FLO, checked MD5, and rebooted to TWRP through the updater, I dirty flashed over 9-15, bootloop.

Last_kmsg: pastebin.com/B1XYnsW1

I then did a full wipe and attempted to clean flash 9-17, bootloop.

Last_kmsg: pastebin.com/G3eDWNUD
[Nexus 7 (2013) Android Development] SHABBYLEA:
Can confirm...
[Nexus 7 (2013) Android Development] blambo:
To me this means that TeamBliss inc. are pumping these ROMs out thoroughly untried and untested.

Installs hit or miss at best? User/operator workarounds required... daily.