yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] Appetisaac:
stock kernel.flash what you will.
[Nexus 7 Original Development] k29er:
This is my favorite ROM. Its perfect. No bloat. Please don't change anything for the nexus 7 setup. I like that everything looks smaller. I get more info and icons on the screen, perfect for its size. Everyone looks like they are working towards making there ROMs more like a tablet ui but I would still like the phone ui option.

Thanks for making this ROM.
[Nexus 7 Original Development] Vangelis13:
+100, what a fantastic rom, thank you!!
[Nexus 7 Original Development] Nebucatnetzer:
**** run out of thanks so consider yourself thanked.

You to.
[Nexus 7 Original Development] Vangelis13:
:D You know that you get 8 on the website & 8 through the app, right? Just saying..

This is my stable toy, it'll stay on slim. N4 is the tinker machine. ;)
[Nexus 7 Original Development] tdizzle404:
And as many as you want with tapatalk ;)
[Nexus 7 Original Development] Vangelis13:
:eek::eek::eek::eek::eek::eek:

(Bought!)
[Nexus 7 Original Development] cale42:
Full wipe install of beta 2. Having play store issues. Updates and new downloads all just hang when trying to download. Wiped cache and data with no luck? Thoughts or ideas?
[Nexus 7 Original Development] chrolmesq:
Re: [ROM][4.2.1]SlimBean -grouper- Beta 2 [06/01/13]

Is it possible to change the lockscreen slider icon?

Sent from my HTC Sensation

---------- Post added at 10:20 PM ---------- Previous post was at 10:18 PM ----------

Change the dpi top stock. Make sure you follow the instructions in the ROM.

Or

Back up with titanium/nandroid and do a fresh install.

Sent from my HTC Sensation
[Nexus 7 Original Development] cale42:
Re: [ROM][4.2.1]SlimBean -grouper- Beta 2 [06/01/13]

Thanks.. I was kind of thinking it was dpi related. Just wanted to double check.
[Nexus 7 Original Development] arse87zx:
Re: [ROM][4.2.1]SlimBean -grouper- Beta 2 [06/01/13]

If you check the faq on the slim website there is a way to do that...if I remember correctly.
[Nexus 7 Original Development] Robpollard:
To those using a custom kernel:

Which one do you use and why? (and with which settings?)

My n7 feels rather slow and sluggish, so I'm keen to try something new.
[Nexus 7 Original Development] Shmi117:
Franco for battery and speed (best IMO).

Faux for pure performance.
[Nexus 7 Original Development] coolek33:
If the rom is not booting get back to recovery and fix permissions. The U can wipe cach and dalvick and it Should boot. Thats how i did.

One bug on 7 and weeklies : dashclock as screensaver when charging or docking gives FC.

Galaxy Nexus, nexus 7, Galaxy Nexus S, Galaxy S +, Galaxy S2... All SLIMBEANED!
[Nexus 7 Original Development] Nebucatnetzer:
Confirmed.
[Nexus 7 Original Development] mslatter:
So I tried reinstalling 7 last night but couldn't get ADB to work at home....more to come below. But last night I went through the entire wipe process, and installed 7 with the 7 gapps. Booted fine. Installed Titanium, and rebooted fine. Restored a couple of apps, rebooted fine. Restored a couple more apps, rebooted fine. Restored most of my apps, rebooted fine. Configured some of the interface but stayed away from PIE. Did a CWM backup "A1"...booted fine. Changed the background image, and set up PIE, reboot failed...boot loop. Tried to restore backup "A1", boot loop. Not making any sense to me. So I wiped everything and restored "A1"...still boot looped.

So I wiped everything again, and restored my dirty flashed 7... all good.

So today at work (where ADB works), I hooked it up and made sure that adb logcat>mytext.txt did generate data. I rebooted dirty 7 and could see when it started logging on the boot up. So started ADB again and booted into Recovery. Restored backup "A1" and booted back up....in hopes ADB would catch something. It didn't ....waited for about 5 mins - just had the slim icon on the screen as it was in boot loop and mytext.txt was empty.

Not the perfect test, but if you want me to start with a fresh install I will - just think the boot loop is occurring before the adb server is started.
[Nexus 7 Original Development] :
Why is Build 7 scoring significantly lower in benchmarks compared to Build 6? In Quadrant for example Build 7 is only scoring 4500-5000 while Build 6 scored up to 6000.
[Nexus 7 Original Development] efan3719:
Slim isnt about getting high benchmarks. and benchmarks are mostly silly. all that matters is real world performance.
[Nexus 7 Original Development] :
That does not answer my question.
[Nexus 7 Original Development] efan3719:
oh well... i tried.
[Nexus 7 Original Development] annoyingduck:
Was on build 6, just clean flashed build 7 with Aio gapps, stuck on splash screen (won't boot). Fastbooted into recovery, wiped again, installed again, wiped caches again, fixed permissions, same result. Rom and gapps downloads have correctly verified sha1 sums. What else can I do to get this to boot?
[Nexus 7 Original Development] efan3719:
damn. that's everything i did and it booted. this problem seems to be pretty hit and miss. you can try dirty flashing over a your last stable install.
[Nexus 7 Original Development] annoyingduck:
Just tried that, no go. So weird. I've never had bootloop issues on this device. Was just reading about the same issue in the liquidsmooth threads on their current 2.8 build. They came up with some interesting solutions for achieving boot. What the hell is going on with all the new builds for this device?

I'm back on my build 6 nandroid, but not done playing quite yet...
[Nexus 7 Original Development] efan3719:
good luck to you. hopefully someone from the team can help you out. there has to be something causing this that can be fixed. if you can get a logcat, if you feel like it, during the bootloop that'd probably help the devs out.
[Nexus 7 Original Development] eduardo_b:
I have flashed every official build on five devices without issue until Build 7, which wouldn't get past boot logo on N7, and then after clearing cache and dalvik wouldn't get past starting apps. I tried all kinds of combinations, even Build 6 with Gapps 7, which booted fine. Finally, I tried fixing permissions even though I have never had to do this on any device, and finally Build 7 booted fine. Some change in it causes a permission issue with at least some N7s. Hope this encourages those having issues to use all the options before giving up.
[Nexus 7 Original Development] shayne77:
Still getting bootloop on fresh install with Slim ver.7.

Process I went through.....

wipe data

wipe cache

wipe dalvik

format /system

install Slim ver.7

install AIO Aroma gapps ver.7

reboot

boot... sits on logo forever.

forced hardware reboot in recovery again.

fix permissions.

boot... sits on logo forever.

then I went.....

wipe data

wipe cache

wipe dalvik

format /system

install Slim ver.6.5

install AIO Aroma gapps ver. 7

reboot

boot... booted fine

reboot in recovery

wipe cache

wipe dalvik

install Slim ver.7

boot... booted fine

So you can't fresh install Slim from ver.6.5 onwards on our grouper devices.

Bit of problem if you're coming from another ROM.

I assume other devices are fine? (Anyone know of complaints on other forums?) I would try my mako (N4) device but I don't think I could pry my wife away from her phone for more than 10mins.

Also, I tried adb logcat > NoBoot.txt while it was sitting on boot logo and CMD sat there saying, "-waiting for device-" so I assume its not getting into the boot process enough for it to create a log?

Strange you can dirty flash ver.7 but not fresh install? It's like something is missing from ver.7 that gets installed on ver.6.5 and back but is still "workable" on ver.7? If it were a commit from ver.6.5 onwards you would think even a dirty flash would fail?
[Nexus 7 Original Development] Shmi117:
I fresh installed and it worked fine. I wiped everything but internal storage, then installed SBv7 + AIOv7 and it worked fine. After setting everything up I installed Franco Kernel and its running nice and smooth.
[Nexus 7 Original Development] youdug:
Im running 7 right now and just wanted to say battery life is incredible.

I used this earlier for 29 minutes and left if off the charger..

Went to use it just now and its at 93%...

Thats after being used for 30 minutes and sitting off the charger for 14 hours..

Amazing.

Great work on this slim team :beer::cool:

Edit: i just fckin noticed my girls daughter cut the damn screen with something..
[Nexus 7 Original Development] efan3719:
I was able to get 7 to install like normal, but I had issues on build 6.8 I think. Dirty flash was all I could do to get it to boot back then. I think there is a way to get a log even if you can't boot far enough. I think it's monitor instead of adb. I found a guide. But idk where I found it. Searching for boot loop gives infinite nonsense. I should have bookmarked it.
[Nexus 7 Original Development] shayne77:
I checked sha1 of both files, they match

I redownloaded again anyway via pc and checked sha1 before transferring to N7.

I now have full wiped again, installed ver.7 and its been sitting on the bootlogo for at least 10mins now (far too long anyway)

Not sure how I (and many others above) get problems when others don't?

Couldn't find anything in regard to getting a logcat while at bootlogo?
[Nexus 7 Original Development] Robpollard:
I've tried them both and messed with them for a while,

Now I'm staying with francos kernel; much smoother and snappier overall (than stock and faux), i guess this one's a keeper. Thanks for the quick response.
[Nexus 7 Original Development] mslatter:
I checked my files and SHA matched as well. Maybe it's something about our hardware. When N7 was initially released I bought the bigger one... So I think it's 16Gig. I'm using CWM for recovery. Don't have my bootloader version handy, but assume it's fine since I was able to install 6 with no problems. Also, I used the double validation by Google.... So my password alone won't let me access my Google account, I have to enter a random second code. Other than that, can't think of what could be related to this problem that not everybody is having. For those that 7 installed fine, what recovery are you using, and if not too difficult, what bootloader? Are you using the 8, 16 or 32Gb one?
[Nexus 7 Original Development] PoedelPCS:
Strange. My grouper got that same bootloop! Working perfectly on Manta and i93oo.
[Nexus 7 Original Development] eduardo_b:
I'm running CWM Touch 6.0.3.1 on 16 GB N7 with 4.18 bootloader. I don't use lockscreens. Flashing SB7, GA7 and Franco r65 caused loading to stop at boot logo...but not the first time when rebooting back to system. Because the system reboot went well, I powered off the N7. Later, when restarting the tablet, booting was an issue. Have no idea why.

I wiped cache and dalvik, getting me past boot logo but stopping at starting apps. Reflashing without Franco didn't get me past starting apps. When I tried SB6 with GA7 but no Franco, it booted without problem, so I reflashed back to SB7 with GA7 and fixed permissions, which was pretty much my final option other than resetting tablet, which wasn't going to happen. Booting went fine. I flashed Franco and booting was still fine.

I don't know if any of this will help you pinpoint the source of the issue. I hope it does. Frankly, I was ready to stay on SB6, as there are no issues for me with it and I don't really use the N7 all that much.
[Nexus 7 Original Development] annoyingduck:
Yeah, the farthest I was able to get was to the starting apps screen on build 7. I tried everything. Back on build 6 without issue, except that the upgrade from build 6 to 7 gapps add-on did not take to well. The home screen had to many app fc notices, had to nandroid back to a complete build 6 set up. I really want build 7, as I'm loving it on my s3!
[Nexus 7 Original Development] krarvind:
We can't reproduce this. 3 in our team has grouper and 2 of them clean flashed and I dirty flashed. No issues. Can you try dirty flash?
[Nexus 7 Original Development] annoyingduck:
Tried multiple dirty flashes on top of 6, some with gapps some without, some with cache wipes, fixing permissions, etc. I tried everything. I'm gonna redownload and try again. The only thing I didn't try was to flash a nightly, but that shouldn't matter, as build 7 should but fine coming from 6, especially if installed clean. This is an absolute first for me with this device....Completely dumbfounded.
[Nexus 7 Original Development] mslatter:
Must be frustrating for you too kravind, not being able to reproduce it. I installed 7 again today (didn't have logcat connection) and knowing I'm doing all the wipes between, couldn't get it to boot with gapps7. So did Aroma, and voila...it booted. So installed Titanium and having done nothing else (no gui adjustments, no restores or anything) rebooted...and it boot looped. So I tried reflashing again, and again, doing exactly the same thing each time and I couldn't get it to boot at all.

What I found interesting is that I then wiped everything before restoring back to dirty7. Before booting after the restore though, I wiped Cache and Dalvik....and it boot looped. So I returned to Recovery, wiped everything again, and restored the same dirty7...except this time I didn't wipe Cache and Dalvik, and it booted just fine.

It's not like I have nothing better to do, and dirty7 really is working brilliantly....I'm just trying to help isolate the issue for moving forward.... thanks for your time!

Oh, and thanks to eduardo_b for the feedback. I too am on 4.18 boot loader, don't use a lock screen - so very similar setup, although I'm not installing any custom kernel - only stock :good:
[Nexus 7 Original Development] :
I've been using Build 7 since yesterday after Build 6 got corrupted on me. I make daily Titanium Backups and use MultiRom so it wasn't a big deal. Initially had difficulty booting which got resolved by wiping cache and dalvik cache after install before first boot. Occasionally when it would get stuck booting up, I reboot into recovery and wipe cache then it would start up no problem.
[Nexus 7 Original Development] youdug:
1 day, 11 hours off charger.

4 hours, 35 minutes screen on time.

30% battery remaining.

Watched a movie, tapatalked, browsed websites, gf used pinterest, gfs daughter played games, etc...

Zero lag, zero problems at all.

Incredible work on this.
[Nexus 7 Original Development] creep138:
I'm getting different battery results. I've tried kernels and all, still it drains. Where pa gave me like 70℅ at the end of the day, I get 30℅ on this ROM. I like this ROM to much to go back Lol. No lag, nothing. Good work, maybe I'll figure it out one day.
[Nexus 7 Original Development] Nebucatnetzer:
Check your wakelocks with better battery stats.
[Nexus 7 Original Development] creep138:
Well, just under battery use media sever kills 48℅ and under data usage (WiFi only) my browser alone took almost 15 gigs in one month, youtube about 10. Would it happen to be a virus app somewhere? I have all the same apps from pa, so idk. I know I don't use all this data Lol. I just don't wanna give up this ROM, ran it for almost a month with no hassle like others.
[Nexus 7 Original Development] Nebucatnetzer:
Media Server could be a broken picture or so.

Because of the data are you using build 6? We had a bug there which showed the wrong size.
[Nexus 7 Original Development] coolek33:
Heh. Im using twrp on all of my devices which is the Best in my opinion. And clean install + fix permissions and wipe caches after not booting helps. After that any reboot is fine.
[Nexus 7 Original Development] Nebucatnetzer:
I like what they are doing but the backup function failed for me a couple of times since then I had to switch back to CWM.
[Nexus 7 Original Development] brfsa:
I've been using OpenPdroid since quite a while on SlimRom. Now with Privacy Guard, can I run both? any conflicts between patching with openpdroid and running Privacy Guard?

cheers.
[Nexus 7 Original Development] Nebucatnetzer:
I don't know I've no experience with opendroid.
[Nexus 7 Original Development] brfsa:
it's quite awesome and it works perfectly with SlimRom. It does not cause problems to apps, unless you remove some permission that the app will require to run.

All you have to do it clone the git repo, run ./batch.sh (repeat each time you pull), then create a cwm zip flash from the rom.

./auto_patcher ../Slim-galaxysmtd-4.2.2.build.7-OFFICIAL.zip openpdroid

It will create update-aosp-grouper-20130705-openpdroid.zip, you flash it on CWM,

As well you need to install Pdroid Manager, it's free on Play store.

git clone https://github.com/mateor/auto-patcher
cd auto-patcher
./batch.sh
./auto_patcher path_to_rom.zip openpdroid
adb push update-aosp-romcode-XXXXX-openpdroid.zip /sdcard/
adb reboot recovery

anything goes wrong, just re-flash your Rom on top.
[Nexus 7 Original Development] brfsa:
here I upload OpenPdroid patch for this SlimRom 4.2.2-build7 for Nexus 7

then install pdroid manager https://play.google.com/store/apps/details?id=net.digitalfeed.pdroidalternative

Flash at your risk.
[Nexus 7 Original Development] Nebucatnetzer:
Thanks I'll check it out.
[Nexus 7 Original Development] creep138:
I just dirty flashed build 7 over 6, I'll do a clean install and see if battery still drains. I do know bricked kernel doesn't play well, I thought I was having hardware problems till I went back to stock. Its not really a downer at least. Could be worse like some other ROMs. I hate it when my music goes into a seizure at work lol
[Nexus 7 Original Development] kbeezie:
USB-OTG no longer seems to work on my Nexus 7 since 7.0-Official. Upon plugging in the USB Drive I always use with it (for nandroid and TiB backups) I get this in the logcat.

W/ContextImpl( 506): Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1084 com.android.server.usb.UsbSettingsManager.deviceAttached:619 com.android.server.usb.UsbHostManager.usbDeviceAdded:156 com.android.server.usb.UsbHostManager.monitorUsbHostBus:-2 com.android.server.usb.UsbHostManager.access$000:38

It's not a hardware issue, because the same cable/thumbdrive still works as expected in TWRP 2.5.0.0
[Nexus 7 Original Development] Nebucatnetzer:
We removed OTG support to bring grouper back to the state of build 6 which was working for all.
[Nexus 7 Original Development] kbeezie:
Oh :/ Didn't see that in the change log.

Is it going back in, or do I need to go back to stickmount?
[Nexus 7 Original Development] Nebucatnetzer:
Hard to say atm. We think it might be the cause for the boot loops. At least partially.
[Nexus 7 Original Development] kbeezie:
SlimBean restarted on me in the middle of playing FieldRunners 2 (first time this happened to me).

Running 7.0-Official

last_kmsg attached.

PS: I've been unable to re-produce the problem thus far.
[Nexus 7 Original Development] Lar5:
Weekly build 7.2 is out :victory:

http://www.slimroms.net/index.php/downloads/all/viewcategory/624-grouper

Edit: Damn! My device just don't want to play nice. A fresh install of build 7.2 bootloops after a few reboots.

Logcat after 30 mins. at the boot logo.

I'll try to install some of the older releases to find a stable one... or just never reboot 'cause the ROM itself is the best i've tried :silly:
[Nexus 7 Original Development] jmcdonald58:
Installed fine here did dirty flash over build 7 rebooted 3 times so far so good
[Nexus 7 Original Development] PoedelPCS:
here as well b00tl00pz with fresh and drity 7.2

something about different GB models? got 16GB version.
[Nexus 7 Original Development] mslatter:
I tried clean install of 7.2 with Aroma, to see if it would boot. Never passed the Slim logo. Restored dirty7, flashed 7.2 on top, and all good.
[Nexus 7 Original Development] Nebucatnetzer:
Did everybody who experiences reboot flash with Aroma?
[Nexus 7 Original Development] annoyingduck:
I used the Aio, not aroma. Could not get build 7 to boot, still on 6. Have yet to try 7.2.
[Nexus 7 Original Development] Nebucatnetzer:
Could you try just the ROM zip after a full wipe (factory reset + /system)?
[Nexus 7 Original Development] annoyingduck:
I'll try that as soon as I get home.
[Nexus 7 Original Development] formicae:
Got a call from a friend last night who let her N7's battery die while on Build 7 and was stuck on the pulsing Slim screen after charging and turning it back on. Walking her through the steps to get to recovery over the phone and try to fix permissions and wipe caches, I ran into it too. We both finally got back up after 2-3 trips to recovery and another fix permissions, but I don't know that FP helped at all, might have just been coincidence. The interesting thing is that our setups are completely different.

Hers: New grouper from last week, totally wiped, then a clean Build 7 install with AIO (non-Aroma), kernel from Build 7.

Mine: December unit, dirty flashed over Build 6 (which may have been dirty flashed over Build 5, I don't remember), Osmodded r65 Franco kernel.

Both have no issues once they actually finish booting; it's just getting there that's the problem.
[Nexus 7 Original Development] infatality:
Nope.. Slim gapps, dirty flash over version 7, bootloop stuck at silm boot img.. Resolved by full wipe and clean installed with 7.2 and slim gapps.
[Nexus 7 Original Development] mslatter:
Odd, because my experience has been the opposite. Dirty flash always works fine, clean install boot loops. I'll try a clean install with Gapps this afternoon and let you know how it goes. I've been using Aroma just because that's what worked for me the last time I actually got it to boot.
[Nexus 7 Original Development] PoedelPCS:
nice, did you reboot after that again?

that's where I got stuck. The first boot after dirty flash works perfectly.

After the next reboot it got stuck again in a bootloop.
[Nexus 7 Original Development] mslatter:
Ok, when I went to download Gapps, I noticed the modified date had changed since when I downloaded the 7.0 versions...so I downloaded the 'new' Gapps and the Aroma from 7/15. Then full wipe, cache wipe, dalvik cache wipe, System format, full wipe again for good measure, fixed permissions and installed 7.2 ROM and Gapps 7.x. Waited 10 mins on Slim boot logo and gave up.

Followed the same wipe process, installed 7.2 ROM and Aroma. Waited 10 mins on Slim boot logo and gave up. Can't figure out what's going on here... When I did the logcat attempt last week, it didn't register anything - so believe it's happening before the logging process starts. If I have time, I'll try the logcat thing again, and see if it's changed at all.

To answer PoedelPCS - Yes, I've rebooted multiple times and comes back up fine. I wonder if you dirty flashed over a ROM version that was already unstable, and now that it's boot looping, it "appears" it's from the dirty flash... I started having these problems when I installed 6.2....all versions before then worked like a champ. I was able to get 6.2 to work by flashing Aroma instead of my "normal' Gapps only...but I'd suggest to you, that you install 6.0 or 6.2 - make sure it's stable...by rebooting a few times, and making sure it comes up fine. Then dirty flash 7.2. Good luck!
[Nexus 7 Original Development] PoedelPCS:
if I restore then only b00t and system without data I got my clock crashing after boot. If I call the wake function from clock in the app drawer it crashes again. Maybe there is something wrong? Got no idea. I hoped 7.2 would have solved that strange behaviour :(