yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] Lar5:
Now I've tried wiping and making a clean install of build 5, 5.5, 5.7, 6 and 6.2.

All installed with the matching AIO aroma apps.

All the 5.x - 6 builds starts and works just fine.

Build 6.2 (and forward) gave me problems. First after install reboot stayed at the boot logo.

After wiping dalvik cache I was able to go through the setup process (wifi, gmail...)

Almost all off/on and reboots after that (a few works) will need a wiping of the dalvik cache.

Build 6.2 without any gapps/AIO/aroma at all hangs too.

I tried dirty flashing a working build 6 with build 6.2. It got stuck in the "Upgrading Android" part.

It just stayed at "Starting apps..." (here i took the logcat)

Grouper 32GB, Bootloader 2.18, HW ver.: ER3 <-- Could it mean anything?

TWRP 2.6.0.0 (tried CWM 6.0.3.1 too...)
[Nexus 7 Original Development] Nebucatnetzer:
It's extremely weird that build 7 doesn't work since it we reverted all the grouper relevant stuff.
[Nexus 7 Original Development] Shmi117:
I've been running SlimBean in fear that it would stop working at any second. So far this hasn't happened on my device. I should also point out that my device would usually hang on boot when flashing gapps or flashing the ROM without gapps (both AIO). After flashing a kernel though (Franco) everything is working perfectly. Its strange how it doesn't work on some devices but works perfectly on mine so far.
[Nexus 7 Original Development] tobiasth:
I don't have problems too, flashed 7.0 with aroma and m-kernel....

via nexus7
[Nexus 7 Original Development] coolek33:
Works fine for me. Clean install+slim gapps and Wipe cache, dalvick again before first boot. N7 8gb.

Nexus 7, Galaxy Nexus, galaxy Nexus S, galaxy S+, galaxy S2... All slimbeaned!
[Nexus 7 Original Development] thecdn:
Working fine for me as well. Full wipe, aio (non-aroma) and faux kernel at the moment. Also had success with bricked kernel. N7 16g.
[Nexus 7 Original Development] jlvlawrence:
I dirty flashed the 7.2 over 7, gapps, and Franco kernel. Didn't wipe anything.
[Nexus 7 Original Development] jmcdonald58:
I still good here also no issues 7 to 7.2 wiped caches only reflashed gapps,I never use aroma just Rom ,gapps for me
[Nexus 7 Original Development] creep138:
My problem was user error. I only wiped sys, dalv, and cache. Missed the data before flashing. I never did that cause I thought it would wipe the whole memory. Running better now.
[Nexus 7 Original Development] shayne77:
I use AIO Aroma everytime. Just noticed now its 40mb bigger then non Aroma... I thought packages would be the same just a prettier GUI with Aroma? Is the GUI 40mb?
[Nexus 7 Original Development] formicae:
Unless I'm mistaken, the Aroma version has two sets of Google apps inside (modded and stock).
[Nexus 7 Original Development] kbeezie:
Both sets are modded (and/or dpi hacked as needed), the only difference between toggable and not toggable is the TDRS treatment (The Real Dark Slim). Any modifications aside from that are present in both versions.

The reason the Aroma version is handy, is TRDS doesn't look that nice in gmail, but seems fine in the rest of the google apps, so you could install the apps and just make gmail the only one that's not toggable, so you can enjoy the dark skin on the rest, but not get annoyed by it in apps you don't want the dark treatment on.
[Nexus 7 Original Development] kbeezie:
Ran into an issue where my screen was off on my Nexus 7, but pressing the power button did not wake it at all, there was plenty of activity in the logcat and the system was still running.

So I grabbed a full logcat and dmesg output to a text file and attached it.

Nexus 7

Bricked (06/24/2013) Kernel

SlimBean 7.2-Weekly
[Nexus 7 Original Development] Swissola:
I'm having exactly the same issue (Stuck on Updating Android part) with the 7.2 Weekly build on my Galaxy S3 i9300 running the yank555 kernel.

It's happened twice to me this week already. A massive blow for what is the best ROM I've ever used :crying:
[Nexus 7 Original Development] android88:
New weeklies have started building... Will update OP once grouper weekly is released.
[Nexus 7 Original Development] kbeezie:
Logcats or can't help.
[Nexus 7 Original Development] reverepats:
7.5 running really well for me so far. Haven't come across any issue just yet
[Nexus 7 Original Development] mslatter:
Fresh install or dirty flash?
[Nexus 7 Original Development] reverepats:
Actually that was a dirty flash. Installed the AIO add-ons in the same session. Have hit any road bumps yet. Performance is good also
[Nexus 7 Original Development] mslatter:
I tried a fresh install. Booted up perfectly after install and gaps. Then restored using Titanium and rebooted fine. Changed battery icon and rebooted fine. Turned on PIE and rebooted fine. Changed the lock screen to none, and rebooted badly.. Bootlooped.

Thought I would try a reinstall and try the lock screen deactivation first. Did a full wipe and reinstalled ROM and gaps again but it Bootlooped on the initial boot. Tried to reinstall a second time using the exact same process and it still Bootlooped immediately... I couldn't get it to even boot up to the setup screen.

So gave up and restored a backup. The fact I couldn't get it to install a second time really confuses me. I used the exact same process and it didn't work. Maybe there are still bits being left over after a full wipe. I will try and redo it again later.
[Nexus 7 Original Development] :
Have not had any major problems with 7.5. Similar to Build 7, it seem to occasionally have trouble booting after initial install. Rebooting and/or wiping the cache and dalvik cache fixes it. After a while it seem to stabilize and boots reliably.
[Nexus 7 Original Development] Nebucatnetzer:
That's really strange when you really do a full wipe in between the flashes.
[Nexus 7 Original Development] formicae:
Flashed 7.5 over Build 7, first boot went fine, but the second reboot stuck at the boot logo. I'm kind of getting used to the dance of trying various combinations of cache-wiping and permission fixing, but I'm also really curious as to why this is only a problem for some of us and not others. Once it's up, it runs beautifully, but every boot is a spin of a roulette wheel.
[Nexus 7 Original Development] PoedelPCS:
I got no l0ckscreen either. If I get my device running again I will set the lockscreen to on and try several reboots. If I encountered the same phenomena as you this could be really close to the bug ;)
[Nexus 7 Original Development] efan3719:
stuck at boot trying to flash weekly 7.5. been at boot screen for ten minutes now. doesnt get far enough to start ADB for a logcat. so here's my steps when flashing.

Format Cache

Format Data

Format SD-EXT

Format System

Format Cache

Format System

Wipe Dalvik Cache

Install ROM

Install Kernel (Faux123 b20)

Install AIO Aroma GApps

*Selected core apps, optional apps, stock launcher, all other apps but the non-toggable versions*

Install Universal Lockscreen Handle

Wipe Dalvik Cache

Fix Permissions

Reboot. stuck at boot screen.

i'll try it again just flashing the rom and see what happens...

***wiped everything again to start over. installed only the weekly 7.5. nothing else. ROM only. still stuck at boot screen. can't get far enough to do ADB Logcat.

*****force rebooted after being stuck at bootscreen. after second boot the ROM booted normally.

Alright. after the force reboot and successful boot i rebooted to recovery and installed gapps, kernel, lock screen as mentioned above. didn't wipe anything or fix permissions. and it booted up just fine. it seems like that there is something in that initial boot that is causing problems. i have no idea but here are two logcats i could get. one from the first successful boot and one from after i flashed the other things. not sure if they'll help.
[Nexus 7 Original Development] PoedelPCS:
yep, here the same..

booted now ~10 times new, always installed or set up some apps on my fresh 7.5 build. Rebooted always without getting stuck. Setting screen lock off leads to bootloop again.

We'll catch you, bug :cyclops:
[Nexus 7 Original Development] efan3719:
i'm going to get everything setup and try that no lockscreen bootloop you've been having to try to see if i can catch anything in the logcat. hopefully this can lead to something that the devs can use to figure out this problem.

Well setting lock screen to none doesn't cause a boot loop for me, did you reboot in between to get the boot loop?

***spoke too soon. Disable lock screen, reboot, stuck at boot screen. But, I force rebooted twice and it booted OK again. This is really strange. Something is causing it to get stuck but rebooting a few times let's it get past. I wish I know how to get information when stuck on boot screen....
[Nexus 7 Original Development] Nebucatnetzer:
Thank you for helping to track the bug down guys.
[Nexus 7 Original Development] Lar5:
Setting the the lock screen to none seems to be the trigger.

First reboot after disabling the lock screen all works like it should.

When rebooting

a second time

it hangs.

Confirmed on build 7,5 and 6.2

TWRP 2.6.0.0

Wipe -> Factory Reset (data, cache, dalvik)

Advanced Wipe -> System

Install -> build 7.5

Install -> gapps 7.x

Reboot

Stays at the boot logo.

The "Google Nexus 7 ADB Interface" is visible at the Device Manager, but when typing "adb devices" in a command prompt nothing is listed.

Hard reboot, bootloader, recoverey

Wipe -> Advanced Wipe -> Dalvik Cache

Reboot

Android is upgrading...

Language setup -> English US -> Skip wifi

Google & location -> both on

Enabling Android debugging

Storage -> PTP-mode (now my device is visible in a command prompt)

Reboot

7 x successful reboots

Security -> Screen lock -> None

Reboot

1 x successful reboot

Reboot

Hangs at boot logo

2013-07-21_125753_logcat.txt

Hard reboot -> TWRP

"Back to build 6.2 which was the first build that gave me reboot problems."

Wipe -> Factory Reset (data, cache, dalvik)

Advanced Wipe -> System

Install -> build 6.2

(no gapps this time)

Reboot

"First start up okay. Boots directly into the Nova Launcher. No screen lock?!?! even though it is set to Slide when checking in the Security settings. Maybe the very first start up is meant to be without any lock screen"

Enabling Android debugging

Storage -> PTP-mode (now my device is visible in a command prompt)

Reboot

Starts with Slide lock screen

Reboot

Starts with Slide lock screen

Reboot

Starts with Slide lock screen

Advanced reboot -> Always show

Reboot to recovery

Install AIO Aroma 6.x (core apps)

Reboot

Android is upgrading...

Language setup -> English US -> Skip wifi

Google & location -> both on

Reboot

Connect to Wifi

Google Play -> setup using my google account

Downloading update for Nova

Reboot

Browser: Visiting slimroms.net

Youtube: works too

Settings -> Language -> Dansk

Reboot

5 x successful reboots

Setting lock screen to pattern

Reboot

3 x successful reboots

Setting lock screen to Slide

Reboot

3 x successful reboots

Setting lock screen to None

Reboot

Successful start up

Reboot

Hangs!
[Nexus 7 Original Development] kbeezie:
Have you tried without the faux kernel? (ie: sticking with the slimbean default).

Also I'm confused about the formating SD-EXT option, as there is no SD card in the Nexus 7 (none that you could partition a /sd-ext mount onto). Should only need to format /system /data /cache (though "formatting" /data also wipes /data/media/ aka /sdcard, so I'm assuming you mean "wipe" unless you're installing from a thumbdrive via USB-OTG with TWRP, and actually removing all your /sdcard content each time)

Edit:

Just tried myself, I changed lockscreen to none, turned it off and on several times without a problem.

But.... if I reboot, stuck at boot screen without getting to the point of adbd launching. Holding down power and letting it boot again goes into the rom just fine.

PS: I don't use a custom kernel on my N7 for the purpose of this test, been testing 7.5-Weekly without bricked.
[Nexus 7 Original Development] efan3719:
I did try it without a kernel. I tried it with nothing but slim installed. And the SD ext thing was just me misreading the dialog.
[Nexus 7 Original Development] shayne77:
I think when you wipe data, it formats sd-ext at the same time? (Even tho it may not exist. I know 2 lines come up, can't remember what they are?)
[Nexus 7 Original Development] efan3719:
Yeah that. It says that it tries but skips it because it's not there. So I shouldn't have put it down.
[Nexus 7 Original Development] letroll59:
miracast

Is it possible that you would add the Miracast support? A modder made ​​a patch available at: https://github.com/kensuke/How-to-Miracast-on-AOSP
[Nexus 7 Original Development] coolek33:
Couldn't boot build 7.5 after a clean install so i restored boot image from a backup of previous build with twrp. Now its working flawlessly.

Galaxy Nexus, nexus 7, Galaxy Nexus S, Galaxy S, S +, S2... All SLIMBEANED!
[Nexus 7 Original Development] pyroguysf:
As a minimalist, I've been loving Slim for a on and off for a while now- it's finally calmed my crack flashing; haven't flashed in well over a week, haha. I'm also running unofficial builds (7.2 right now) on my Droid DNA that've been running great. Only problem I've had on the N7 though is in Phablet mode occasionally quick settings tiles all get squished to a few pixels high- I remember reading another report of this but can't find it, however it's only happened twice in the week+ I've been running 7.2, and isn't anything a simple reboot doesn't solve.

I love the minimalism, but would like to make a tiny feature request- can you guys add the ability to set notification styles (e.g. Always/Never Expand, etc.). Not only do I personally like the Always Expanded option, but I feel it provides a better experience for "non-standard" expandable notifications. Particularly for notifications with integrated buttons like some music players I find that with the reduced DPI that comes standard with Slim sometimes causes notifications use their expanded version while at the fixed collapsed height and don't always look quite right, usually with just a tiny bit of the bottom cut off, until manually expanded.

For what it's worth, the unofficial build 7.2 I'm running on my Droid DNA has this as a setting in Interface > Notification Drawer but there isn't an option for that on my N7. Here's the thread for the DNA, but the author doesn't say what, if anything has been changed from your sources (other than using our kernel which is most similar to the HTC One/M7).

Overall I'm very happy with Slim (even the unofficial port), and I'm glad it was able to stop my crack flashing- keep up the good work!
[Nexus 7 Original Development] Nebucatnetzer:
I added the request to the list.

Thank you for the compliments.
[Nexus 7 Original Development] android88:
Looking for some grouper testers. Let me know if you'd like to test.
[Nexus 7 Original Development] Shmi117:
I would be willing to test. I own an 8GB launch day N7.
[Nexus 7 Original Development] annoyingduck:
4.3 testing.... :rolleyes:

I'm in either way. I'm one of the ones that cannot boot any of the build 7 builds, so would probably be helpful.
[Nexus 7 Original Development] k4bbe:
I'd be up for some testing :D
[Nexus 7 Original Development] thecdn:
I'd be in for some testing.
[Nexus 7 Original Development] infatality:
[MENTION=2815753]andriod[/MENTION]88 count me in..
[Nexus 7 Original Development] s33d1ing:
I'd like to test if you're still looking for testers.
[Nexus 7 Original Development] mslatter:
Me too!
[Nexus 7 Original Development] #define:
Same here..

Lemme know if you need more..

ғг๏๓ ҭђє ғเรђ!
[Nexus 7 Original Development] android88:
Woah that's a lot of testers :p - I only need 2-3 though... I'll go with the first few people who answered.. Thanks though guys.
[Nexus 7 Original Development] nimbold:
Kinda addicted to this ROM! that "Real Dark" is really good. everything is good in these 3-4 days of using latest version.

btw it's really slim! 380mb free space of internal :)
[Nexus 7 Original Development] kbeezie:
:P Though I've often wondered what's the point of the free space in /system anyways if you can't use it for normal data? It's a read-only partition, an most system apps you might add are no more than a couple megs (every other data saves to /data).
[Nexus 7 Original Development] annoyingduck:
I'm by no means speaking on definitive knowledge, but I would assume it's a default allowance in Android to allow for manufacturer and carrier bloat. Seeing as most android devices are not running pure android. Touchwiz roms for example are typically 800mb to over a gig on some of the newer devices, compared to 100-300mb for most aosp roms. Majority should logically take precedence for default allowances. Just my assumption...
[Nexus 7 Original Development] kbeezie:
Oh I'm quite aware of that, I'm just saying praising the fact there's so much free space in /system :P doesn't do anything in my opinion, especially when you got people explicitly asking to free up space on /system.

Though I'm sure the person I quoted was just making an observation of how slim it was based on how little it took up in just it's own files.
[Nexus 7 Original Development] coolek33:
If the There is still problem with booting after a clean install the please bring back the USB otg support. I don't want to use any 3rd party apps.

Galaxy Nexus, nexus 7, Galaxy Nexus S, Galaxy S, S +, S2... All SLIMBEANED!
[Nexus 7 Original Development] nimbold:
Actually i love everything "slim" :D

Course Google stock almost has no bloat ware, but it can be more and human is insatiable :D
[Nexus 7 Original Development] Nebucatnetzer:
Hey guys,

The weekly builds for 7.8 have started.

We made some serious changes as a preparation for 4.3.

I insist that everybody reads the changelog otherwise you won't find a single feature (and you would miss my nice flow chart :) ).

http://www.slimroms.net/index.php/changelog/362-weekly-7-9

So that's it for now have fun with the new build when it drops.

Nebucatnetzer
[Nexus 7 Original Development] android88:
You beat me to it ;)

This build has a very different settings layout that we think you guys will enjoy... It removes duplicate features, looks nicer and best of all, works great!
[Nexus 7 Original Development] Nebucatnetzer:
Sorry thought I would post here as well since you said you're busy :)
[Nexus 7 Original Development] android88:
Yeah I was earlier (got home like 20 mins ago...) but its fine man lol ;)
[Nexus 7 Original Development] Pinktank:
What sort of build flags do you use? Linaro, strict aliasing, etc?
[Nexus 7 Original Development] nimbold:
Thank you devs. I won't go for 4.3 till Slimbean goes for it ;)
[Nexus 7 Original Development] mslatter:
Not sure if we're waiting on the testing / correction conclusions or not, but decided to try 7.8. Full wipe, wipe cache, wipe dalvik, format system, then full wipe again for good measure. Installed 7.8 and slim gapps. Boot loop.

Restored dirty 7.2, wiped cache, wiped dalvik, dirty flashed 7.8 and slim gapps....all good! Just a few extra steps to get it running :silly:
[Nexus 7 Original Development] Lar5:
My N7 boot looped too with a clean install of build 7.8.

After a hard reset and booting into TWRP I wiped the dalvik cache.

After that, it works perfecet. This time I won't set lock screen to "none". ;)

Shouldn't the dalvik cache be "empty" on a clean install? Where in the file system can it be found?

I guess I should try a clean install and wiping dalvik before first reboot?

Btw... the new layout of the Slim settings is very nice.

It feels very well thought through - like a natural part of the system :good:
[Nexus 7 Original Development] Nebucatnetzer:
We had quite a discussion about which feature goes where and which section we add and where.
[Nexus 7 Original Development] nimbold:
Just flashed latest version over v7.5 and all thing is ok. It only took wiping cache and dalvik cache.

Playing with new version. Thanks :)

:cheers:
[Nexus 7 Original Development] ferparedes:
Me neither! But I will install 4.3, specially after reading about TRIM.
[Nexus 7 Original Development] Sage:
just installed 7.8 with fresh wipe of everything with new google apps too.. google play updated and when the Dark Slim is activated you cannot read the title of the apps in Google Play.. (black text on black background i assume) anyone notice this bug?

/edit

Google Play version 4.1.10
[Nexus 7 Original Development] annoyingduck:
You didn't install Slims gapps. You must use slim gapps (I recommend the aio packages). Current playstore is already in the package, along with other framework items that regular gapps do not have.
[Nexus 7 Original Development] Sage:
i installed the ROM and Slim_Gapps.4.2.2.build.7.x... do i need a AIO? I thought the ROM and slim gapps was enough?
[Nexus 7 Original Development] Nebucatnetzer:
It is enough but they play store shouldn't get updated by itself.
[Nexus 7 Original Development] Sage:
So I guess we do have a bug.. not a big deal.. i just cant use Dark Slim.. pity cause i do like it :)
[Nexus 7 Original Development] android88:
What do you mean you can't use it?
[Nexus 7 Original Development] nimbold:
If you mean Slim dark for play store, download latest inverted zip file of "Play" app. You can find it on xda/forums/android/inverted bla bla bla
[Nexus 7 Original Development] annoyingduck:
He shouldn't need to install another playstore. I'd recommend 're-downloading the current slim gapps or Aio, verify the sha1 with android file verifier, and flash the rom again (dirty/just caches). I'm not aware of any playstore updates recently, but it shouldn't matter as the app is modified for theming and dpi so it should not ever update unless you manually flash a newer version.

I'm running 7.8 (;) android88) with the current Aio gapps. Playstore is version 4.1.10, no update of any kind happened, dark toggle works as it should. Something is definitely wrong somewhere...but I don't think it's on Slims end.
[Nexus 7 Original Development] Sage:
Just did as you asked and the same thing happened again. Once completed flashing google play has the old white icon. First run is fine.. Though then gets upgraded to the new multicoloured arrow icon.. (same version as you 4.1.10) and i can no longer see the Title of the app. You can see the developer though. (this is only in Dark Slim mode though).

No big deal just worth a mention..
[Nexus 7 Original Development] annoyingduck:
Wtf?... No clue what's happening, I'll reflash later and see if I can replicate what's happening.

Your only solution now may be to call a priest - your device must be possessed!
[Nexus 7 Original Development] reverepats:
Nope me either. My play store hasn't updated either and I always use the latest AIO package. But pushing the latest store should work.