yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] SHABBYLEA:
Not really... I think this type of "real world" testing is actually better than "in house" testing....

A few years back I was involved in a software project, and was overseeing QC & user acceptance testing, and my issue with the project was that the people we had testing the software were very tech savvy...they instinctively worked around problems that may have caused less proficient users to struggle...

Anyway, just my opinion....
[Nexus 7 (2013) Android Development] maigre:
That's my experience, too. Besides, different people use software differently and therefore, will encounter different bugs, be it thorough different usage or different sequences of actions. A small group of testers is rarely going to find everything. Though it would seem that these installation issues would be more widespread and easier to reproduce. But apparently, they're not.

Should invoking an update from the Updates screen reboot flo into the updater or into custom recovery where the user instigates the update? My experience has so exclusively been the latter that I just assumed that was how it should be. But some of the comments here make me wonder. This ROM is feature heavy, so maybe that's a factor in the inconsistency between users given the preponderance of options that can be set, along with all the other things Nexus users might introduce.

[MENTION=6207927]713brianp27[/MENTION] will get to the bottom of it in time, I'm sure.
[Nexus 7 (2013) Android Development] blambo:
Ummm. Well? Dirtied both Flo and Deb, latest 09/17. No problems at all with the installation of either one.
[Nexus 7 (2013) Android Development] blambo:
Flo
[Nexus 7 (2013) Android Development] SHABBYLEA:
Well put...as to the updater issue, as just your average user, if I hit the update button, I expect an update... no twrp, no recovery no flashing etc..

Edit: You are absolutely right.. BrianP will get it sorted...
[Nexus 7 (2013) Android Development] blueyes:
Just upstreamed. Will build soon. Got one building now
[Nexus 7 (2013) Android Development] blueyes:
I had an issue with updater on flo, just sent me to twrp. I disabled the open recovery and re-enabled it. Oddly it worked. Deb just works.

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

I do always test before pushing updates. There are just so many variables between users , mods, etc that I can't predict. I made a few changes , I hope it resolves the issues! Thanks for the understanding
[Nexus 7 (2013) Android Development] maigre:
Trying to update from the 9-17 build to the 9-18 on flo:

9-17 still reboots from the Updater screen to TWRP. Then, after flashing 9-18, the device still goes into a bootloop unless I flash the kernel. The stuff that echoes on the output in TWRP says that boot.img is installing. I realize it's scripted to say that, but I'm not seeing any errors. As has been the case, flashing ElementalX gets things back on track again.
[Nexus 7 (2013) Android Development] quickdraw86:
You won't see errors in the recovery output if the package itself installs correctly. The source of the bootloops is the included kernel, or the way it was included more specifically, and errors in the init/boot process will be in the output of last_kmsg.
[Nexus 7 (2013) Android Development] maigre:
Thanks. Fortunately, this is a minor obstacle. It's easy enough to flash the kernel.
[Nexus 7 (2013) Android Development] quickdraw86:
Yeah, hope the issue gets sorted out, I like to clean flash in recovery or via ADB, but Brian p is a good guy, and likely working on it, and it's usable the way it is with EX 4.03.
[Nexus 7 (2013) Android Development] SHABBYLEA:
I know...there are so many variables...

Anyway, I think I speak for everyone when I say you are doing a belting job...
[Nexus 7 (2013) Android Development] ganggreen30:
Amazed theres no fix yet
[Nexus 7 (2013) Android Development] quickdraw86:
He's doing his best. TBH, it's bootable with an extra step at this point. I've seen CM official nightlies broken for weeks on several devices before. Even the almighty slim had devices where data didn't work on slimbean, and data for those devices was never fixed until KK. AOSPA had numerous kitkat devices without working GPS... Never fixed, and support for most of those devices dropped. All of those projects are far larger than bliss, and, he is clearly working on it, give him time.
[Nexus 7 (2013) Android Development] SHABBYLEA:
Well said...
[Nexus 7 (2013) Android Development] blueyes:
What is your issue. What build are you on? What is your update process? Any mods or variables? With so many its hard to fix an issue I can't duplicate. I've been using updater for weeks with no problems. Just ROM,no kernel or mods. I've tried to replicate but can't. I'll do whatever I can but imagine fixing something you can't duplicate and don't have happening yourself. Like flying blind. Like I said I'll do whatever. I've recently upstreamed, changed tc back.
[Nexus 7 (2013) Android Development] blueyes:
MODERATOR EDIT - Quote Removed

https://github.com/TeamBliss-Devices/android_device_asus_flo

Take a look at how many changes I've made to make this a better rom.. Just trying to give everyone the best. Some of our devices are still on 3.8. Lol

---------- Post added at 10:01 PM ---------- Previous post was at 09:53 PM ----------

I'm assuming everyone is on the newest bootloader and radio (deb).
[Nexus 7 (2013) Android Development] quickdraw86:
There's no need for you to justify the status of the ROM, you're obviously doing your best. If everyone that complained tried offering feedback, details, etc. You'd be that much closer to possibly finding a common thread between those with boot issues. Carry on the good work bud.
[Nexus 7 (2013) Android Development] beany>:
Don't bite Brian; it's a slippery slope. Build for you, because you want to. You can't keep all the people happy all the time and there is definitely no reason to justify yourself.

Keep up the good work bud :)
[Nexus 7 (2013) Android Development] blueyes:
Your right Ian. I just wish I could fix every issue. [MENTION=269830]Beany[/MENTION]
[Nexus 7 (2013) Android Development] Stryke_the_Orc:
Thread cleaned. Let's keep things civil here huh?
[Nexus 7 (2013) Android Development] SHABBYLEA:
Yeah, absolutely... Apologies if I caused any offence...
[Nexus 7 (2013) Android Development] ganggreen30:
I am grateful for all the hard work don't get me wrong at all
[Nexus 7 (2013) Android Development] Martin_Devil:
Previously, when I pressed the button for a long time the last application, I showed the app, open it up automatically. And now it is removed. Why is that?
[Nexus 7 (2013) Android Development] blueyes:
I hope the 4.0.2 update helps..
[Nexus 7 (2013) Android Development] SHABBYLEA:
Thanks..really appreciate your efforts... KUTGW....
[Nexus 7 (2013) Android Development] infamouzwt:
Keeps bootlooping even after clean install
[Nexus 7 (2013) Android Development] sgs9:
you must flash with extra kernel 3.4.0-ElementalX-N7-4.03-cm!!
[Nexus 7 (2013) Android Development] quickdraw86:
And, there's only about 5 pages worth of explanation on that too lol.
[Nexus 7 (2013) Android Development] blueyes:
I'm actually just flashing rom, using updater and not having any trouble.

---------- Post added at 09:01 AM ---------- Previous post was at 08:59 AM ----------
[Nexus 7 (2013) Android Development] blueyes:
Quiet here! Everything OK?
[Nexus 7 (2013) Android Development] SHABBYLEA:
Far as I'm concerned everything's fine... Just snached 26/09 and about to flash...

Thanks BP...
[Nexus 7 (2013) Android Development] blueyes:
Has anyone with bootlooping tried installing the ROM only? Like I've sad before I'm updating with no problems. I even tried to fresh install the latest version using multirom and worked. So I am baffled.

---------- Post added at 08:12 PM ---------- Previous post was at 08:07 PM ----------

A few devices are in a similar boat, so my be cm source related. I'll keep digging until everyone is doing well. You can now use any kernel you like, quantum is another good one. Be sure to make it permissive as ROM is base permissive.
[Nexus 7 (2013) Android Development] klaust58:
No Problems, no bootloops :)

Clean install as secondary rom in multirom. First, only the rom, later gapps. Everything(*) works fine. Thank you!

(*) minor problem, the AppBar stops working after a while...

Overclocking (1.6...1.7GHz) for the default kernel would be nice!

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 (2013) Android Development] blueyes:
You can change that in kernel auditor. Once you've got it running good just use multirom and copy secondary to primary.. Man I'm glad to hear this. Lol.
[Nexus 7 (2013) Android Development] blueyes:
Anyone still looping? I don't think twrp truly formats the system. Proven by a successful install using multirom. Either use mr then swap secondary to primary or flash idk cm then wipe and reinstall my ROM. I know I'm grasping at straws but somethings gotta give.
[Nexus 7 (2013) Android Development] etere1964:
With 0927 version (the date on ROM is wrong .... 0926 , please 713brianp27 correct in next one) , infact after installation it will give an update message ...) if I install only ROM and Gapps I've bootloop : if I install ROM + GApps + ElentalX Kernel all OK.

I've Deb

:eek:
[Nexus 7 (2013) Android Development] sgs9:
Same here.

Bootlooping only without 3.4.0-ElementalX-N7-4.03-cm Kernel.

@713brianp27 , I read has 4.02?? Link Thats the fault?

Screenshot_2015-09-29-17-07-58.png
[Nexus 7 (2013) Android Development] etere1964:
Same here.

Bootlooping only without 3.4.0-ElementalX-N7-4.03-cm Kernel.

Also with 0928 Version (last) - Update 21:12 ...FC Trebuchet .... Clean Flash :(

I've Deb

:confused:
[Nexus 7 (2013) Android Development] quickdraw86:
I don't mean any disrespect by this, but honestly, if you don't know what's causing some users to bootloop, then just say you don't know. The past two official versions of TWRP successfully install and boot just about every ROM besides yours, so without any real evidence of inconsistent formatting by TWRP, I'd say the problem is still on the ROM side. Don't try to pass the buck to TWRP.
[Nexus 7 (2013) Android Development] blueyes:
I DONT KNOW! AND NEITHER DOES PAT OR SHAUN OUR HEAD DEVELOPERS. HAPPY?

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

Its a bliss issue. Not just flo. And I was just mentioning twrp to rule out possibilities! Not pass buck. Use another ROM if your not happy. I'm sorry. We are doing our best to fix it. In our spare time, neglecting family. For free. Lol Amazing.

---------- Post added at 03:13 AM ---------- Previous post was at 03:10 AM ----------

Sure works for me? Have any suggestions I'm open but do not insult me.

---------- Post added at 03:14 AM ---------- Previous post was at 03:13 AM ----------

Sorry guys, shouldn't of went off like that.

---------- Post added at 03:16 AM ---------- Previous post was at 03:14 AM ----------

I'll build one now. We have made more changes to try to fix issues. Flo, deb, shamu, lg. Its a mess
[Nexus 7 (2013) Android Development] DroidmanDan:
And Bliss is such a sweet lover!
[Nexus 7 (2013) Android Development] AnkeshReborn:
I don't dare to ask for updates or ETAs ever,but what I wanted to say our maintainer is busy looks like or having other problems hence why updates are not coming and hence saying we are not getting any bliss love.

Hit a thumbs up If I helped you,I am here for increasing my thumbs up count!Don't be lazy its free!
[Nexus 7 (2013) Android Development] nprev420:
Looks like Pimp Shaun hasn't built for FLO in a while. I am building an update for you guys now. Soon as it is done I will upload it.
[Nexus 7 (2013) Android Development] beany>:
Cool. Thanks in advance!
[Nexus 7 (2013) Android Development] SHABBYLEA:
Cheers...
[Nexus 7 (2013) Android Development] AnkeshReborn:
[MENTION=5052522]nprev420[/MENTION]

Keep it going till Shaun isn't here!

Cheers!
[Nexus 7 (2013) Android Development] nprev420:
New build is ready. BlissPop v2.0 Official 02-14-15
[Nexus 7 (2013) Android Development] AnkeshReborn:
Am I blind or what,I can't get the link!

Where's it hiding from me?
[Nexus 7 (2013) Android Development] nprev420:
Its in the OP, its all builds. You'd see it if you actually looked

Yours is here

http://downloads.blissroms.com/BlissPop/Official/flo/
[Nexus 7 (2013) Android Development] AnkeshReborn:
I thought you were doing unofficial builds,well its a good one!
[Nexus 7 (2013) Android Development] travster119:
I can't find the smart pulldown option, search for it in settings then it takes me to the status bar page but nothings there to disable it, any ideas?
[Nexus 7 (2013) Android Development] nprev420:
Why would a member of TeamBliss build unofficial?

---------- Post added at 01:29 PM ---------- Previous post was at 01:27 PM ----------

System settings, bliss interface , notification drawer
[Nexus 7 (2013) Android Development] beany>:
Just a little feedback for you. So far, everything good and no bugs found - not that I really expected any!

One thing I did notice was it took quite a lot longer to charge than normal (was using Vanir-Exodus). It's been just over an hour since charged so early days but battery usage seems close to normal, so it's just the charge time so far.

Thanks again for the build!
[Nexus 7 (2013) Android Development] SHABBYLEA:
Thanks again. Very good work...
[Nexus 7 (2013) Android Development] AnkeshReborn:
I didn't knew he's official!

Sent from my Resurrected flo powered by elemental x and kanged by by Xposed.
[Nexus 7 (2013) Android Development] blambo:
For Bliss 2.0, I'm using the ElementalX-N7-3.03-cm kernel and find that it charges very quickly. Functions superbly.
[Nexus 7 (2013) Android Development] beany>:
Thanks for the feedback. Looks like something on my end then. Let the search begin!
[Nexus 7 (2013) Android Development] travster119:
You should update the title of the thread and great work by the way good to see this ROM back in development ?
[Nexus 7 (2013) Android Development] beany>:
I believe only the op can do that.
[Nexus 7 (2013) Android Development] SHABBYLEA:
[MENTION=2490658]pimpmaneaton[/MENTION] Thanks for the nightles...Top work....
[Nexus 7 (2013) Android Development] ! .ĐΛЄMØИ. !:
So it's not necessarily a kernel issue? Could you perhaps just compile with the default CM kernel for testing on that part? Majority of CM roms use the default kernel and anybody else flashes what kernel they want, I flash custom kernel no matter what rom I use.
[Nexus 7 (2013) Android Development] blueyes:
Really wouldn't matter what kernel I use. It's a bliss issue. Core code. But for some reason it doesn't effect everyone. I'm running flo and deb. No issues. I'm running shamu. No issues but I know 4-5 devs who are bootlooping on it.

---------- Post added at 12:38 PM ---------- Previous post was at 12:36 PM ----------

And changing kernels isn't just a click. Whole process which could cause more issues. Toolchain comparability, compiling.
[Nexus 7 (2013) Android Development] quickdraw86:
FWIW, I don't see any insult towards you in my previous post, though now that I read back your post before it, i see that you said you were grabbing at straws after your remark about the TWRP...

I don't want to argue/derail/offend, so agree to disagree.

Anyway, since you said you were open to suggestions, perhaps compiling a build with the toolchain you used previously, or with CM's flo kernel would be worth a try. As you said, bootloop is generally kernel related, but, in this case, where the issue is present for some, but not others, hard to pin down.
[Nexus 7 (2013) Android Development] Dark_Eyes_:
New build with CM tree and kernel

Hi guys,

I'm the hammerhead maintainer at Team Bliss and I thought I would give my friend Brian a hand. So I re-forked the CM device tree and kernel to build a new experimental BlissPop for flo. I don't own the device so I can't test it myself but it should be good to go. Hopefully that will fix the issues some of you were having. If it indeed works well I'll push my modification to our official repo so all new builds will be built with CM tree and kernel. Since it's not an official build I uploaded it to my personal AFH account. Please provide feedback.

https://www.androidfilehost.com/?w=files&flid=37029

Enjoy !!!

__________________________________

Official Team Bliss Hammerhead Maintainer

Please consider a donation if you want to support my efforts !!!
[Nexus 7 (2013) Android Development] SHABBYLEA:
Many thanks to all involved in this ROM...the commitment to iron out the [sometime] difficulties with Bliss is exceptional....

Gonna flash this tomorrow...wlyk how it goes...

Many thanks...
[Nexus 7 (2013) Android Development] blueyes:
I'm at work and can confirm my buddy Jeans build boots. Let us know how it works for you guys and like he said we will change trees.

---------- Post added at 09:36 PM ---------- Previous post was at 09:35 PM ----------

Thanks Jean. My French Compadre'
[Nexus 7 (2013) Android Development] ganggreen30:
Oh my I came back to this thread after posting this issue when it 1st happened weeks ago it seems I can't believe it's still not fixed but I will give this new one a try thanks dark eyes if it does work
[Nexus 7 (2013) Android Development] quickdraw86:
Your test build boots and generally works perfectly. No issues at all, and I was one of the few that had issues booting normally.
[Nexus 7 (2013) Android Development] Dark_Eyes_:
Let me be clear about something. I'm not targeting anyone personally, but I've been scanning the thread and it's been going long enough. Fixing bugs takes time. It is a lengthy process, especially when your maintainer can't reproduce the issue. I saw no one providing useful "debugging" information, so how do you expect your maintainer to fix a bug he doesn't have?

From my experience most of those "bugs" are caused by the users themselves, either not following the proper directives or misunderstanding what those directives are. I'm not saying it's the case here, but the threads on xda are loaded with "fix this bug" when there is no such issue.

That being said, I also wanted to remind you all how lucky you are to have a dedicated maintainer that actually cares about fixing issues. Brian has been doing a fine job here, on his own free time. He doesn't owe anyone, and if he quits you will be left with nothing. So let's keep that in mind guys.

Rant over. Now let's get down to business and fix that problem lol! I believe we made a step in the right direction, let's see where that takes us.
[Nexus 7 (2013) Android Development] Pfeffernuss:
This build works fine. Dirty flashed and booted straight up, opposed to all previous latest versions.

Great stuff, thanks :good:
[Nexus 7 (2013) Android Development] blueyes:
So I guess I'll rebase the ROM and kernel. If its working for you guys. I'll get it done as quickly as I can. Now! Keep in mind, Bliss is about to go through some major transitions as soon as "M" is officially released. So more changes will then come. As we go from BlissPop to Bliss? M? We haven't settled on name yet, hence question marks. So enjoy the ride. And New rule... No log then it didn't happen. Lol thank guys
[Nexus 7 (2013) Android Development] tashik19:
Please fix it!

Usb OTG is not working in latest build. I am using ElementalX kernel.
[Nexus 7 (2013) Android Development] ganggreen30:
Blissfully Marshmellow or Marshmellow Bliss !!!!
[Nexus 7 (2013) Android Development] blueyes:
Gonna be AOSP. Not CM based too. Hmmm
[Nexus 7 (2013) Android Development] SHABBYLEA:
OK, flashed exp bliss & can confirm is bootable, stable and even runs on a different kernel [quanta 4], everything great so far...the only issue I had was I flashed the wrong gapps...

Thanks for all the effort chaps...
[Nexus 7 (2013) Android Development] blueyes:
Can you upload your build.prop?

---------- Post added at 07:41 PM ---------- Previous post was at 07:29 PM ----------

You should see persist.sys.isUsbOtgEnabled=1

In your build.prop.

---------- Post added at 08:04 PM ---------- Previous post was at 07:41 PM ----------

Hey. Check USB otg suport

---------- Post added at 08:09 PM ---------- Previous post was at 08:04 PM ----------

Jeans the great coder is fixing the otg support. Simple permission issue. Workaround.. Open terminal, type su

Grant su, then type "chmod 777 usbdisk" make sure you have a flash drive in before opening terminal.
[Nexus 7 (2013) Android Development] SHABBYLEA:
Unfortunately can't check that.. sorry.
[Nexus 7 (2013) Android Development] conqueror_25:
The latest experimental build. Will it work on Deb? Sorry for being impatient to wait for the Deb version.. ? Lte Mobile Data is not important to me.
[Nexus 7 (2013) Android Development] blueyes:
No. It will not flash.
[Nexus 7 (2013) Android Development] conqueror_25:
Hey Brian. Thank you for your prompt response. Will stop downloading now and wait for your release. Thank you Man!
[Nexus 7 (2013) Android Development] blueyes:
Im at work but I think jean updated my buildbox. I'll build one and see if it updated. I'll be able to tell after I repo sync
[Nexus 7 (2013) Android Development] Dark_Eyes_:
New builds are underway

Guys,

I pushed all the changes I made yesterday about rebasing to CM (both tree and kernel) to our official repo and I changed toolchains to UberTC 5.2. I also added back ViPER4Android and Doze (Ambient display). I started some fresh new official builds with those changes and I'll upload them on the BlissRoms website when they are ready. All future builds will be synced to that new repo and contain the changes I made.

Hope you guys enjoy it !!! I'll leave you in the good hands of Brian now :)

__________________________________

Official Team Bliss Hammerhead Maintainer

Please consider a donation if you want to support my efforts!!!
[Nexus 7 (2013) Android Development] blueyes:
Just pushed flo, deb is building now

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

No Problem. Another 20 min. I'll hit you up her to let you know I pushed deb

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

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

Deb is pushed!

Official Team Bliss Flo/Deb Maintainer
[Nexus 7 (2013) Android Development] conqueror_25:
Woah! That was fast.. Can you provide a link.. Please..

Thank you Very much Team Bliss. ?
[Nexus 7 (2013) Android Development] beany>:
:good: Good move.

Good to see you guys making progressing. Thanks to brian and [MENTION=5445418]Dark_Eyes_[/MENTION]
[Nexus 7 (2013) Android Development] blueyes:
Use your updater

---------- Post added at 12:11 AM ---------- Previous post was at 12:11 AM ----------

Or blissroms.com

---------- Post added at 12:14 AM ---------- Previous post was at 12:11 AM ----------

http://downloads.blissroms.com/BlissPop/Official/deb/BlissPop-v4.0.3-deb-OFFICIAL-20151001-2047.zip

Official Team Bliss Flo/Deb Maintainer
[Nexus 7 (2013) Android Development] hamma:
I just switched from CM 12.1 to bliss and am really impressed. It´s so much smoother. Thanks to all the team for such a great rom.
[Nexus 7 (2013) Android Development] blueyes:
Hope you enjoy it!

Official Team Bliss Flo/Deb Maintainer

---------- Post added at 01:18 AM ---------- Previous post was at 01:16 AM ----------

Yeah. Jean is too modest to admit it but he's taught me a lot. He's an amazing coder!
[Nexus 7 (2013) Android Development] tashik19:
Hey, still usb otg is not working! I have followed all of your steps. :confused:
[Nexus 7 (2013) Android Development] sgs9:
Thanks to all dev's :)

Last Version work fine, no bootloop :D