yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] nadiros:
Thank you, thank you!

You guys fixed the brutal sceen banding on system backgrounds that this device has been plagued with from day one. I have ranted about this before. How this ever was alowed to happen AND continue with every release since from google just baffles me.

Slim is quality, performance, and attention to detail. And all three are usually not on par even in the best ROMs here on xda.

Your time and willingness to share are appreciated. Donating ;)

*Edit - Donated -
[Nexus 7 Original Development] androidkid311:
Has everyone missed the information on slim site. It bootloops due to a lock screen bug. Lock screen has to be enabled. I haven't had a bootloop since. I didn't even wipe cache updating to beta 4 from 3.
[Nexus 7 Original Development] minifig:
I've had this thing bugging me when I first installed slimbean. It took me a few reinstall before I figured it out myself. That'll teach me to read every line twice.
[Nexus 7 Original Development] MasterJ87:
This is the one thing that is currently bugging me. I don't use a lockscreen since I already have a flip cover case on my N7. Opening it and unlocking it is one step too many for me. Hope for a fix soon.
[Nexus 7 Original Development] ricardowec:
Is this bug device specific or system wide.

I ask this because I am thinking on switching to SB in another device that as the previous post don't use the lock screen.

Sent from The Beast + using Tapatalk 8 beta
[Nexus 7 Original Development] MasterJ87:
It's device specific. There are several other device specific bugs as well.

Device specific issues

grouper/tilapia: on a fresh install or when you have disabled lockscreen you can run into a bootloop....wipe dalvik/cache after the bootloop resolves it. Keep lockscreen activated for now

Captivate & I9000: Camera FC after unlock of lockscreen

Skyrocket & Hercules: Panorama will FC app.
[Nexus 7 Original Development] nadiros:
I do not use lockscreen and have no boot loops!

What may work is to change lockscreen security to a pattern lock, confirm that it locks/unlocks correctly and then disable locksceen within settings. I only say this because that's what I did and have had no issues.

Ofcourse have a backup handy just in case. The only other variable that might have an affect is I did not use dashclock on the lockscreen either before disabling it altogether. Hope this helps somebody as I too find it a pain on a tablet.
[Nexus 7 Original Development] coolek33:
U can always set the delay after lockscreen to 30mins. Its handy if U often turn the screen on.
[Nexus 7 Original Development] DigitalJedi:
Here's my question: does the TRIM support in 4.3 really make the big difference in the this ROM (and other 4.3 based ROMs) like I've read it should? I'm on Slim build 8 4.2.2 and I've noticed that it is like lightning at first and slows down over time becoming unbearable after a month-ish. That's what I've read the TRIM support is supposed to resolve, but I've got no personal experience to go off. I generally don't flash ROMs until they are in "stable" status, but since there aren't anymore Slim 4.2.2 builds coming out I've actually resorted to re-flashing build 8 to get performance back for a while. I've become frustrated with my N7. If the TRIM support is really making a big difference I'll jump ship now and check out then beta builds.
[Nexus 7 Original Development] android88:
There haven't been many reports (if any) of unbearable lag so i guess it is working...

And about this being labeled not as a stable - it is very stable, we just like to make sure that 100% of things work and there are no issues before we release a "stable" build.
[Nexus 7 Original Development] nadiros:
AFAIK trim makes a difference if your internal storage is low. Now that this function is built in 4.3 we shouldn't even know it's there. I'd recomend grabbing a good cache cleaning app

https://play.google.com/store/apps/details?id=com.isnowstudio.cachecleaner

And you could also reflash your ROM, (gapps,kernel) after wiping system in recovery.

I find things to feel snappier after that.
[Nexus 7 Original Development] annoyingduck:
On 4.2 I used the fsrtim app and could clearly notice a difference. So far on 4.3 there hasn't been a need.
[Nexus 7 Original Development] android88:
beta.5 released. Check slimroms.net for downloads and changelog
[Nexus 7 Original Development] Vyrus69:
Anyone else having an insane battery drain? On 4.2.2 I could get 3 or 4 days of battery not touching my tablet and this rom I get barely 2
[Nexus 7 Original Development] MasterJ87:
My battery life has been great so far. Haven't needed to flash a custom kernel either. Get 2 days as well but with minimum 4 hours screen on time.
[Nexus 7 Original Development] ricardowec:
No problem in dirty flash over beta 4. Great ROM.

Sent from The Beast + using Tapatalk 8 beta
[Nexus 7 Original Development] ~wolverine~:
Anybody else getting this. The center dock icon is off to the right in both portrait or landscape. It's like this with both apex and nova launchers. It wasn't off in beta 4.

Slimbean beta 5
[Nexus 7 Original Development] coolek33:
For those who want clean install b5 without bootloop: power off via recovery after a clean install and then just power on. Check it.
[Nexus 7 Original Development] android88:
That's because the app drawer isn't in your dock - its just a normal app icon/shortcut on your homescreen ;) if you try moving it around you'll see what I mean
[Nexus 7 Original Development] ~wolverine~:
OK I see what you mean. I must have had a brain fart. Thanks
[Nexus 7 Original Development] waz675:
What beta? Since beta5 was announced 1 hour before your post, I'd recommend flashing latest and giving it 1 or 2 charge cycles. Aldo betterbatterystats can be a godsend.
[Nexus 7 Original Development] ricardowec:
Dirty flashed Beta 5 and AIO Gapps. Getting FC on GOOGLE SEARCH. Anyone_?

Sent from The Beast + using Tapatalk 8 beta
[Nexus 7 Original Development] :
Most popular answer will be...........clean flash, then post your issues. ;)

Sent from my cellular telephone
[Nexus 7 Original Development] waz675:
Did you even read the download page for slimgapps? It has:

Slim_AIO_gapps.4.3.build.beta.5

Attention:

This package you need for a fresh SlimBean install. If you are on latest SlimBean version allready you can use the upgrade packages in Download Addons Upgrade section.

AIO package (All In One) includes all google apps

*

NOTE: If you get a FC with Google Now this is caused by old data and a security change by google on dirty flashes. To solve it uninstall Google Now.....reboot one time......reboot into recovery and just flash AIO_gapps again and you are fine to go
[Nexus 7 Original Development] coolek33:
5 posts higher i wrote how to clean install without bootloop. Check when U will be doing that.
[Nexus 7 Original Development] :
Reading is hard!! :)

Sent from my cellular telephone
[Nexus 7 Original Development] waz675:
Haha, I did a similar post the other day as a p1ss take. 'Reading is for suckers' with context to someone not bothering to read OP as their question was directly mentioned and answered in it ha ha ha :p
[Nexus 7 Original Development] mrdevil_25:
i tried to uninstall google+ and google search but neither will uninstalled due to system app. then i tried to convert to user app using TB but error comes back that i cannot convert =(

looks like clean flash is the only way for me?
[Nexus 7 Original Development] coolek33:
Did U try slimsizer from SlimCenter to Uninstall this App?
[Nexus 7 Original Development] minifig:
Well, try using wakelock detector to see what's happening. I found out that there were a lot of location requests from apps. So I turned off GPS as I don't use it on a tablet. Now I hardly loose battery power over night or when not using it.
[Nexus 7 Original Development] ricardowec:
No I didn't. I read one full page of changelog.

FIRST I expect important stuff, changes in installation instructions and warnings be posted by the maintainer to help users and testers avoid this type of errors. If I where to read the OP and installation instructions EVERY time I flash a ROM, I would spend countless hours in doing so and reading the fine print. I work for living Sir.

FINALLY, this warning was posted long after the announcement that the new build was up and I downloaded the rom and Gapps minutes after such announcement.

Be kind and respectful. Just a suggestion

Sent from The Beast + using Tapatalk 8 beta
[Nexus 7 Original Development] :
It takes hours to read the OP? LOL

Wow!

Then don't read the OP's....and when something important gets written there....you'll miss it. And if you're lucky, you won't end up bricking your phone.

Also....just read the OP....took 38 seconds. ;)

Sent from my cellular telephone

---------- Post added at 04:41 PM ---------- Previous post was at 04:35 PM ----------

Also....you are going against the usual complaint. Some devs don't update the OP, and just post all the important stuff in the thread. So then you gotta go back countless pages to find updates and other info. Most prefer the OP be updated regularly so we can find new info quickly. And not have to comb through 1000's of posts potentially.

My friendly advice....seriously ....if seconds out of your life to read the OP is too much, then flashing must really screw your day up....that can take lots of time. So....my advice.....flash stock and call it a day. Or....maybe an iPhone?? ;)

Anyway.....I've now wasted more seconds of your busy day. I apologize.

:)

Sent from my cellular telephone
[Nexus 7 Original Development] ricardowec:
Did I mention this ROM OP??( it doesn't say much) . Then read well and come to conclusions. Also.. I clearly mention EVERY Time, again, read well, also mentioned that the warning was not there when the update was posted, again, read the full post.. It takes 5seconds.

Sent from The Beast + using Tapatalk 8 beta
[Nexus 7 Original Development] :
Not reading or learning before you mess with an android.....will one day lead to brick. Guarenteed.

Sent from my cellular telephone
[Nexus 7 Original Development] nadiros:
Ricardowec frequents these threads and I'm sure would have responded to you better if you folks had the same issue or problem. There's somthing about just being nice that's helpful enough. We worry that dev threads fill with useless questions...how about filling with flames instead?

The only mistake he made was flashing the build and accompanying packages on the cutting edge. Jeesh!

Anyhoo [MENTION=233732]slim[/MENTION] devs, thanks for sharing another build. Just setting up my mako then I'll be back to flash and report ;)
[Nexus 7 Original Development] tdizzle404:
Anyone stuck on the boot screen?
[Nexus 7 Original Development] nadiros:
Last few pages has an answer, as well as grouper specific notes on Slims page.
[Nexus 7 Original Development] tdizzle404:
Yeah I read all that and followed the steps in the op but still can't boot PA flashes fine for what its worth, dunno wiped and flashed a few times
[Nexus 7 Original Development] DigitalJedi:
Today I used adb fastboot to flash the new bootloader, booted into recovery, wiped everything but internal storage, flashed, wiped cahces, and rebooted. I had no problems whatsoever. Smoothest ROM upgrade I've ever done. It is running a good bit faster than the Slim 4.2.2 was running for me. Thanks for this ROM! I'm enjoying my N7 again.
[Nexus 7 Original Development] lagoskon:
If you find this quick, just flash the latest bricked kernel to see real speed.

102-1600, 520 GPU oc, 620gmode. Rest as proposed, zram on.

Also with these settings there is very good sleep battery life

Στάλθηκε από το Nexus 7 μου χρησιμοποιώντας Tapatalk 2
[Nexus 7 Original Development] coolek33:
Try this: wipe cache, dalvick, data and system. Flash rom and gapps. Power off. And then power on. If this not work then after stuck on boot go back to recovery and flash again without wipes.
[Nexus 7 Original Development] scottx .:
For some weird reason it's not booting for me. Fresh from full data wipe. Pushed everything via adb and flashed the weekly and the minimal gapps. Didn't boot twice. Flashed franco.Kernel hoping it might fix it and nope.

scottx@edge:~$ adb logcat

/sbin/sh: exec: line 1: logcat: not found
[Nexus 7 Original Development] coolek33:
Tried my method and the one from OP?
[Nexus 7 Original Development] D_Viper:
install rom, gapps, reboot give bootloop, reboot to recovery install rom, it starts...

In my opinion flashing gapps is the problem, trying to flash first gapps and then rom.....!!!

Mybe some apps present in rom and even in gapps (calendar?) give bootloop

EDIT: I can confirm that gapps have some problems... The Perfect solution is:

Flashing first GAPPS and then ROM

(So if there is some duplicated apps (present in rom and in gapps too) grouper will use the rom's apps ;))
[Nexus 7 Original Development] nadiros:
Uh, AFAIK this method would only work on a dirty flash. I won't claim to understand the details of how partitions function, however flashing gapps first would be redundant if this install allows for saving gapps when system is updated, and would fail if there is no system for gapps to install to?

I'd be curious to know how this works.

*Edit - yes I know its a question more then an answer lol. But if it works for you then cheers man ;)
[Nexus 7 Original Development] lmulli:
Dirty Flashed over CM10.2 with no problems whatsoever, credits to the devs for this!! Have gone back to CM10.2 simply because I don't like the default DPI setting of this rom and couldn't be bothered changing it.(nothing more than a couple of clicks I know!). Why the Devs have chosen such a DPI when it makes the icons far too small for the device and the text at normal size font unreadable I can only guess.

But anyway, the main crux of this message was to say that dirty flashing the latest rom with the AIO Gapps and LeanKernel 2.2 resulted in a rock solid rom with no issues (apart from the DPI!) at all.
[Nexus 7 Original Development] tobiasth:
no problems here, flashing beta 5 over beta 3 with format system ... all runs great!
[Nexus 7 Original Development] adrman:
I also had a bear of a time doing a clean install of beta 5 on my wife's N7. I tried all of the previous suggestions in this thread, but couldn't boot into the rom. I had no problems doing my own N7 last Friday, but that was a dirty flash over beta 4. That gave me the idea of clean installing beta 4 first, then dirty installing 5 and eventually, it worked. However, the first flash of beta 4 also boot looped, so I, did a clean wipe again, reflashed it, then powered down in recovery and powered back up. That got me into beta 4 and the dirty flash of 5 went off perfectly. Hopefully, updating to the stable release will be a smoother transition. :D
[Nexus 7 Original Development] dirtygoldfish:
I really hope everyone having trouble with bootloops have actually read the instructions and tried them, or tried the method previously suggested by [MENTION=4741244]coolek33[/MENTION]. Because if not...you're just creating more trouble for yourself than necessary. :p
[Nexus 7 Original Development] adrman:
Read and tried.
[Nexus 7 Original Development] dirtygoldfish:
Ah that's unfortunate then. I flashed betas 3 and 4 and got everything up/and running once I wiped cache and dalvik cache after a bootloop. :eek:
[Nexus 7 Original Development] nadiros:
Ok so I feel like a dummy lol.

Last week I raved about you guys (Slim Team) fixing the default holo background sh*tty gradient that google/asus left us with.... well it seems that it must have been the kernel I was on (m-kernel) that apparently has improved dithering affects.

Soo... I'd like to request this please :D

I believe since ICS certain devices have had issues with the system backrounds

(Gnex) and the N7 has disgusting banding/rainbow effects in the gradient that can

supposedly be fixed by deleating a few .xmls and adding background .png's instead

within the framwork.

Anybody else agree? Since I haven't heard much about it recently is it only me?

(am I crazy? are they coming to get me?)

Its a cosmetic disaster!

Seriously, if you have and use your N7 how could you miss it?

/end rant.
[Nexus 7 Original Development] bullfrog527:
Just dirty flashed over my 4.3 harmony set up and everything is working great! Switched the DPI back to stock and looking good.

Thanks, now on to getting my HTC one on slimbean
[Nexus 7 Original Development] annoyingduck:
Anyone know how to choose the white system icons for home screen apps?
[Nexus 7 Original Development] android88:
Change the icon pack. I use the holler! wht pack (yes spelled that way). They are cool white icons. Take a look ;) there's also a holler! blk icon pack that is just black instead of white
[Nexus 7 Original Development] annoyingduck:
Yeah, I downloaded about ten white packs, none of them had that true stock white look except for the "tiny" series, but that was missing fine basic icons that I needed.

Where are the system icons stored? Can I extract them to the gallery?
[Nexus 7 Original Development] android88:
System icons? You can probably pull them from the launcher apk (from 3rd party launchers. The system icons) or from the individual system apks
[Nexus 7 Original Development] MasterJ87:
Anyone tried playing Breach and Clear? After installing the game, it always FCs. And after uninstalling, my N7 always reboots. I don't think it's the game, because reviews on the Play Store are good. So is it incompatible with the ROM for some reason?
[Nexus 7 Original Development] misterk267:
Rom runs great, but flashing a custom kernel seems to break connection to play services. WiFi bars are grey, play store won't connect. All other internet related things work fine.
[Nexus 7 Original Development] coolek33:
No problems with m kernel or bricked one here.
[Nexus 7 Original Development] misterk267:
M kernel and oxydo both cause it over here.
[Nexus 7 Original Development] coolek33:
Try fixing permissions, maybe this will help.
[Nexus 7 Original Development] nafdroid:
simplex themes. i like them both very much.

http://xdaforums.com/showthread.php?t=2293257
[Nexus 7 Original Development] android88:
build.1 weekly (not stable) released! Check slimroms.net for more info
[Nexus 7 Original Development] MasterJ87:
So grouper still has the bootloop issue, but is it caused by the lockscreen issue? I noticed there was no mention of disabling the lockscreen causing a bootloop in the device specific issues section. Does that mean it's safe to disable lockscreen?
[Nexus 7 Original Development] annoyingduck:
Yup, disabling it is perfectly fine. No bootloop issues in regards to the lockscreen.
[Nexus 7 Original Development] ~wolverine~:
Nice job Slim team. Very slick and smooth. Thanks to all involved.
[Nexus 7 Original Development] ricardowec:
Sorry, can't find the gapps. Are they up?

Sent from The Beast + using Tapatalk 8 beta
[Nexus 7 Original Development] efan3719:
Yes. http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/383-addons/downloads/dlsearch
[Nexus 7 Original Development] annoyingduck:
Ughh, office suite is still not working...there was some discussion about this in g+, but no clear answers. The logs I provided are apparently not showing the crash.
[Nexus 7 Original Development] efan3719:
When I use it the app crashes but keeps working. I get the pop up that says it has stopped working but it hasn't. I dismiss the pop up and continue on. So at least on my end it's not actually crashing. It just thinks it is. Don't know if that will be of any help.
[Nexus 7 Original Development] annoyingduck:
Not on my end. If I I'm in Google drive and try to open any type of document (with office suite set as the default program to open with), the app crashes and returns me to drive. If I try opening office suite directly and choosing a file, it opens the file then immediately crashes. There's no ability to bypass the toast message, it's a full on crash.
[Nexus 7 Original Development] efan3719:
Guess I spoke too soon. Just did what you described and got the same results.
[Nexus 7 Original Development] android88:
New weekly up on the site ;)
[Nexus 7 Original Development] ricardowec:
Can't find any updates at this time.

Edit : can see it's been taken down

Sent from The Beast + using Tapatalk 8 beta
[Nexus 7 Original Development] Steph310:
New update? :confused:

Sorry but I only see Slim-grouper-4.3.beta.5-WEEKLY-676 (2013-09-06 ) and nothing newer...
[Nexus 7 Original Development] Gothic4:
Yeah. Where is the new version?

Wysłane z mojego Nexus 7 przy użyciu Tapatalk 4
[Nexus 7 Original Development] dillis:
i think they took it down,might have needed a quick fix or something
[Nexus 7 Original Development] Jimi Mack:
I see it is up as of now.
[Nexus 7 Original Development] android88:
They were taken down for now to fix a bug
[Nexus 7 Original Development] runner77:
Looks like the new weekly (1.2) is back up for downloading! Thanks SlimBean team!!

Update: Can't get it to boot. Did a full wipe.

Update 2: Recovered previous build, wiped caches and flashed the new weekly. Everything seems to be working good now.
[Nexus 7 Original Development] Archaic1881:
I just switched from cm to slim, but i lose superuser every time i flash. Is slim not rooted out of the box or do i have an issue?
[Nexus 7 Original Development] minifig:
Read the homepage of slimroms. At the bottom is says what to do.
[Nexus 7 Original Development] pyroguysf:
Unless I mis-remembered what I read, I thought the initial boot hang was reported as fixed. I tried multiple clean flashes (full wipe + system + even all data the first time), trying all 3 types of gapps packages, but I still have to reboot to recovery, wipe dalvik/cache before it boots. I used to disable the lockscreen, but I've kept it enabled ever since it's been known to cause problems. FWIW, I'm on the newest TWRP 2.6.3.0.

Not that it's a big deal, I just wanted to report it since I don't see anything for grouper specific issues anymore. I have a problem crack flashing anything that looks possibly interesting, but I always end up coming right back to Slim, particularly for the minimalism, even unofficially on my DNA. :good:

Also, if I may, I'd like to suggest 3 small feature requests for consideration:

Camera QS Tile

Network Speed in status bar

Ability to delete a screenshot from it's notification

For reference, they're all in Cristiano Matos' crDroid. Keep up the good work!
[Nexus 7 Original Development] efan3719:
If remember right they didn't put grouper into stable since that issue wasn't fixed. That's why it was still considered a weekly.
[Nexus 7 Original Development] Cliniclyinsane:
Weekly? It hasnt been stable ina month. Been waiting to try this on grouper for a while now. Someone needs to fix this
[Nexus 7 Original Development] pyroguysf:
I haven't noticed anything else since beta 2. It's been "stable" - they've stated they just don't want to give it a stable title because of the one initial boot hang which has a really simple workaround. Source (Note 2). I was simply indicating it was still an issue since I no longer saw it listed under device specific issues for 1.2.
[Nexus 7 Original Development] efan3719:
Yup. They may have just forgot to put it in or figured people knew about it. But other than that it is very stable.

Not really. I'm sure they are working on it. If you want it fixed so badly then contribute something useful. It's a really simple fix to get it to work. And then everything is 100%. So nothing is stopping you from trying this ROM.
[Nexus 7 Original Development] Cliniclyinsane:
That simple fix that the team cant simply fix? I get bootloops that are not fixed by clearing cach. So a non booting rom is stable? Weird
[Nexus 7 Original Development] efan3719:
I'm not a dev so I have no idea how hard it is to fix the issue. If you have a boot loop problem that isn't fixed by the instructions they have then provide a log and follow the bug reporting steps and maybe they can help.
[Nexus 7 Original Development] coolek33:
Try this: wipe cache, dalvick, data and system. Flash rom and gapps. Power off from recovery. And then just boot.