yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] taitony:
Finally same as slimport, miracast (WiFi Display) is working on the latest SlimBeam ROM with my TV box (NetGear PTV3000). It never work on CM 10.2 official or Kangs. Thank PO for your efforts.

Sent from my TapaTalk 2 on Nexus 7 2013
[Nexus 7 (2013) Original Android Development] Wanya79:
I'm still havin hickups with Build 5 , that means spontaneous reboots. can't find out,why? anyone?
[Nexus 7 (2013) Original Android Development] bumbernut:
The only random TV reboot I have had is well using Facebook beta. Assumed it was an app issue.
[Nexus 7 (2013) Original Android Development] juried:
Working perfectly here, no help :( Perhaps you could try capturing a log.
[Nexus 7 (2013) Original Android Development] oohaylima:
Now both my Nexus and Galaxy S4 are running my favorite ROM. Sweet!!!!!
[Nexus 7 (2013) Original Android Development] pogi1100:
Anyone having problems with Netflix? When I click on a movie, the screen greys but the popup isn't there. Was working fine on stock.

EDIT: Issue went away after switching to 240 DPI
[Nexus 7 (2013) Original Android Development] JAY28W:
New SlimBean (beta 5) user here, and I like it a lot. Smooth, nice touches on the dark theme and other design touches that I've seen so far. I just switched over my Flo to SlimBean from PA3.

And, IMO, a big gigantic plus is the clarity of communications with the slimroms.net site.

Good job to everyone involved, including the users who give feedback and suggestions.

jay
[Nexus 7 (2013) Original Android Development] vng10:
dont know if anyone else is experiencing this, but whenever i uninstall an app, tablet reboots. I came from a clean install as well.

Also, for anyone that uses OfficeSuite Pro, are you guys experiencing "app unexpectedly closed"??
[Nexus 7 (2013) Original Android Development] z31s1g:
Unistalling works, but OSP force closes.
[Nexus 7 (2013) Original Android Development] harise100:
Same here. On my S4 too. Both running beta 5.

Kingsoft Office works.
[Nexus 7 (2013) Original Android Development] simplon:
I am experiencing this too on beta 3 flo..
[Nexus 7 (2013) Original Android Development] bumbernut:
Yes me too.
[Nexus 7 (2013) Original Android Development] kufikugel:
guys...without logs we cannot do much ;)

grap a logcat when an issue appears and provide it in the thread here
[Nexus 7 (2013) Original Android Development] yellowdie:
Hey guys, Beta 1-4 was totally stable for me, but Beta 5 has had repeated reboots. If it's something on my end, I will deal with it, but I didn't know if these logs would show you guys anything beneficial. I'm on the Beta 5 stock kernel, no OC or UV. It happens a lot when the tablet is sitting idle. Sometimes it happens 5-6 times per day, sometimes a little less than that. Thoughts?

___________________________________

Also, dating back to Aug, I asked about Multi user and Neb said it's not ready yet. By any chance, is it a planned feature for Stable 1? Or will it still come later?

Thanks!

:):D:laugh::good:
[Nexus 7 (2013) Original Android Development] Nebucatnetzer:
Multiuser works so far that you can add a second user.

However the Slim features aren't available for the second user.
[Nexus 7 (2013) Original Android Development] yellowdie:
That's what I meant. Will the Slim features be coming for the second user?
[Nexus 7 (2013) Original Android Development] Nebucatnetzer:
Let me rephrase my post.

Multiuser works so far that you can add a second user.

However the Slim features aren't available for the second user in stable build 1.
[Nexus 7 (2013) Original Android Development] yellowdie:
That's exactly what I needed to know. Thanks! :D

(For the record, I'm asking for an ETA, I was inquiring about a status check). :)
[Nexus 7 (2013) Original Android Development] rubaboo:
link to stable 1?

Where is the link to download SlimBean 4.3 Build 1 WIP? I only see the news article...
[Nexus 7 (2013) Original Android Development] DroidIt!:
Just wondering, is there gonna be a weekly release this week or issues being worked on? Just curious. :rolleyes:
[Nexus 7 (2013) Original Android Development] Nebucatnetzer:
It's Work In Progress.

No weekly this time. But it's planned that we release the first stable build.

---------- Post added at 06:47 PM ---------- Previous post was at 06:01 PM ----------

Hey guys,

The first 4.3 based stable build is available.

When your coming from a 4.2 based ROM I recommend that you start from scratch and restore with TiBu only the most necessary things.

Beside that read the changelog and have fun.

http://slimroms.net/index.php/changelog/377-4-3-build-1
[Nexus 7 (2013) Original Android Development] harise100:
Dirty flashed over Beta 5. Working Great! :D

... but why is the invisible, but always present menu button gone?
[Nexus 7 (2013) Original Android Development] housepabldroid:
this fantastic rom gave more problem with gmd Auto Hide Softkey. this apk reply the message that the n7 is not supported, but it'snt.
[Nexus 7 (2013) Original Android Development] ktkr:
I saw someone saying slimbean has some change since beta5 which caused some compatibility issues with some custom kernels, will this happen to flo too?
[Nexus 7 (2013) Original Android Development] yellowdie:
No, that was only a problem with the Nexus 4. Mako has different kernel sources, but our flo is fine.

_________________

Uh, why was the Menu button removed from the Navbar button options? The three dot option is still there, but that looks like crap and totally throws off the synergy of having the three line button balance out and center the Navbar. :(

Also, no kernel changes since Beta1? :(
[Nexus 7 (2013) Original Android Development] thecdn:
Working great so far but one thing has come up. Under "Choose longpress action:" for buttons there is no longer an option for 'menu' I always set up my Recents long press with that. Was it decided to get rid of that or was it overlooked this time around?
[Nexus 7 (2013) Original Android Development] z31s1g:
Agreed.
[Nexus 7 (2013) Original Android Development] thahackr:
Dude it doesn't matter its 3 dots so what at least it works when u press it YAAAA finally a stable release I been waiting for this over a month already....:):cyclops:;):o:victory::laugh::good::fingers-crossed:
[Nexus 7 (2013) Original Android Development] Olivierica:
no tablet

This room doesn't have a tablet interface. Kinda lame for my nexus 7. I'll stick with PA3+ for now
[Nexus 7 (2013) Original Android Development] hyperxguy:
Still no latest GPS firmware yet.

Just flashed stable1 and lost GPS locks. I think Slim has never had the new GPS firmware fix (released with JSS15Q) implemented (I've been on every Slim releases).

As usual I still use sfhub's GPS patch to solve the problem:

http://xdaforums.com/showthread.php?t=2421373

And as usual, I still love Slim,
[Nexus 7 (2013) Original Android Development] npainter7:
It never ceases to amaze me that people complain about certain features that aren't available or may be missing. I think some people forget that it's a free ROM and that you should be grateful and thankful that these Developers put a lot of effort and time into getting these out to all of us. If you do not like the ROM then use a different one. Or if there is something that you would like in the ROM, maybe you could give a suggestion instead of just complaining about what's not available. Thanks for all the hard work devs, everything is working flawless on my device and I have no complaints whatsoever
[Nexus 7 (2013) Original Android Development] efan3719:
So glad you said this. This is a place to contribute. I understand not all of us can code, but we can at least report bugs/suggest features. Just coming in and complaining then proclaiming you'll use a different ROM as though the developers will get scared like you're a lost customer is ridiculous.

I've yet to get this device but I'm running Slim on my Nexus 4 and old 7 and this will be the first thing I put on my new tablet. Many thanks and keep up the great work everyone. :thumbup:
[Nexus 7 (2013) Original Android Development] thahackr:
Is anyone missing the camera app or is it included with gapps.?
[Nexus 7 (2013) Original Android Development] yellowdie:
I completely agree. I sing the praises of SlimRom all the time. And coming from someone who does code and knows in depth what I'm talking about (I used to put out my own ROM all by myself), there is a LOT of work that goes into doing what these guys do. But one of the things I love most about Slim is they're very community-minded and they take feedback from users well. And most of the time that I've seen features disappear, it's either been on accident or it was something intentional and there's an explanation to go with it. In the case of the Navbar buttons, I'm willing to bet it was accidental (unless there's some reason I'm not aware of); so if there's an accidental mistake, how will the devs ever know unless the users speak up and let them know? So there is a huge difference between reporting things and complaining about stuff. Whining and complaining should never be in a Development thread (although it's always going to happen--which is actually one of the reasons why I killed my ROM and gave it up), but a Development thread also can't exist without feedback and reports.

So again, like I end almost all of my post, thanks again, team, for the awesome work. :)

I've been on Slim since early this year, and I haven't bothered trying anything else (except for the few painful days that I had my Flo before Slim made a 4.3 ROM for it. Those were hard, hard days...) ;) :p
[Nexus 7 (2013) Original Android Development] Nebucatnetzer:
The reason why the menu button got removed is that we wanted to make it's behaviour more similar to AOSP.

That's why Pie has now as well a dynamic menu button.

In addition many apps are up to date and use the three dots which makes the normal menu key obsolete.

However we're currently discussing what we're going to do with it.
[Nexus 7 (2013) Original Android Development] yellowdie:
Good to know, thanks. See, I just wasn't sure if it was intentional or not. My take is that AOSP only has back/home/recents, but Android is about options--and that's always been the heart of the open source. I think there's a reason Samsung's kept the physical menu button all along--it's very beneficial. Especially because although a lot of apps have added a menu button, they all add it in different places.

Just my two cents, but personally I'd love to have the three lines back as an option. But I'm glad to have a solid answer now. Thanks! :)
[Nexus 7 (2013) Original Android Development] scurley1898:
I'm trying to find something, anything to complain about but I can't. Oh well.
[Nexus 7 (2013) Original Android Development] Nebucatnetzer:
Samsung added the menu button because they are selfish pricks and only do what benefits them.

Means they do it so that all there devices work similar even the ones without Android.

The menu button should be in the top right or bottom right. However top right is the more common variant.

http://developer.android.com/design/patterns/actionbar.html
[Nexus 7 (2013) Original Android Development] harise100:
"should be " is the problem. But it isn't!

Not on the xda app for example.

Furthermore it is much more convenient to have the menu key on the bottom, when you hold a 7'' device in portrait mode.

So please Slim team, bring it back as it were before.
[Nexus 7 (2013) Original Android Development] Sanchez_13:
Google now

I love slimbean, I have it on my phone too but for some reason on my nexus 7 google now doesn't work, it goes straight to the search function but doesn't allow me to opt in to google now. any suggestions?
[Nexus 7 (2013) Original Android Development] Nebucatnetzer:
Things you could try:

-Wipe app data/cache

-reflash Gapps

-delete the search apk in the /system folder and install it from the playstore.
[Nexus 7 (2013) Original Android Development] Sanchez_13:
Thanks a lot for your reply. I've tried everything but still no dice.
[Nexus 7 (2013) Original Android Development] Natakranta:
I've reed in other slimbean thread or on slimbean.net that you need to uninstall Google app, reboot phone (important step), then reboot to recovery and reflash gaaps. It worked for me on my Nexus 4 when I was on slim beta 4 or 5, I don't remember now.
[Nexus 7 (2013) Original Android Development] v01rider:
thanks OP for bring this rom to the flo. i just got mine last night. charged it over night and rooted it this morning. just installed slim. best rom imho. i use it on my cell also!

question though. i am using the flo at college and was wondering about encryption. ive never used it on my phone, but thought it might be best for the flo in case it walks off! :silly: if i encrypt and then an update for the rom comes out, how does encryption work with updating? i know for laptop using bitlocker, you have to decrypt, which takes at least 18hrs, before backing up and re-installing. could someone explain encryption for the flo or rather any tablet?

edit to add, what kernel are peeps using?

thanks
[Nexus 7 (2013) Original Android Development] Nebucatnetzer:
Pew I've honestly no experience with encryption on mobile devices (phones, tablets). I only have an encrypted Linux laptop.
[Nexus 7 (2013) Original Android Development] shreddintyres:
Has anyone else noticed that there doesn't seem to be a toggle for profiles on flo? I want to make sure that it's just me experiencing this before I do a complete wipe and reinstall.

I'd appreciate it if someone could check for me. Thank you in advance.

- cheers

FLO'd from my fingertips
[Nexus 7 (2013) Original Android Development] Nebucatnetzer:
Happens here as well. Thanks for spotting it.
[Nexus 7 (2013) Original Android Development] yellowdie:
Hey, out of curiosity will the next build be based on JSS15

R

(android-4.3_r2.3) or still JSS15

Q

(android-4.3_r2.2)?

There's also the JLS36C (android-4.3_r3) and JLS36G (android-4.3_r3.1), I'm pretty sure those are Deb (LTE) only, but why would Google have different branches for them? Especially naming them r3 vs r2. Will Flo ever be on that branch? The original Nexus 7 Wifi and Mobile models had the same branch.

Google just wanted to make it as confusing as possible this time around. lol. Especially seeing as all of the other Nexi are on J

W

R. :)
[Nexus 7 (2013) Original Android Development] Nebucatnetzer:
The next build will be JLS36C.
[Nexus 7 (2013) Original Android Development] shreddintyres:
If you have downloaded the latest weekly DO NOT FLASH according to slim Roms website they found a critical bug and the latest weekly build should NOT be installed. (build 1 weekly 990)

Just fyi
[Nexus 7 (2013) Original Android Development] yellowdie:
Okay, sweet! So we can go the JL way! :D So why C instead of G? And why is Google putting out a thousand builds instead of just pushing a 4.3.1?! (That was slightly rhetorical).

:) :D :laugh::good:
[Nexus 7 (2013) Original Android Development] Nebucatnetzer:
Google knows :)
[Nexus 7 (2013) Original Android Development] patou75:
Don't know if it's a knowing issue but when i m in landscape mode, sometimes I can't see tiles for quickstetting. (I set black with 50% transparent for background on notification drawer)

Envoyé depuis mon Nexus 7 avec Tapatalk 4
[Nexus 7 (2013) Original Android Development] Chronzy:
Like stated in the OP, this is an alpha build and there are certainly some issues here. But first off, thanks for your efforts...

-Power down reboots into system

-Reboot recovery reboots into system

-Nova FC's, didn't get Apex installed

-Scrolling (menus, etc) is pretty janky

-Doesn't show up in windows (MTP). Yes I have correct drivers installed, but a simple reinstall might fix that.

-Lost root.

I'm sure there's more in addition to the bugs in the OP, but at that point I nandroided by to stock. I'm sure all this will be worked out in due time and once again, thanks for the preview!
[Nexus 7 (2013) Original Android Development] dysolv:
For the most part everything seems to be running great. The only issue, other than than the reported themes, and janky graphics, would be the SwiftKey Keyboard seems to FC everytime it tries to open.

Thanks for the hard work!
[Nexus 7 (2013) Original Android Development] paulhoop:
Looking forward to seeing this on the Nexus 7 2013, I run the SlimBean (unofficial) port on my HTC DNA. Love it there.

I lost root after flashing, tried several things to reestablish. Reflashed supersu.zip, reinstalled supersu. probably me since i was trying it at 4:30 AM. Nothing seemed to work. Just reporting in case others see the same.

Restored backup. Will take another run at it tonight.
[Nexus 7 (2013) Original Android Development] Nebucatnetzer:
Try to set to "apps and adb" in the dev options.
[Nexus 7 (2013) Original Android Development] Nexus11:
Not everything is working so I'll hold off and see what the next update brings.

Glad to see work is being done
[Nexus 7 (2013) Original Android Development] paulhoop:
Yup, did the trick.
[Nexus 7 (2013) Original Android Development] dysolv:
Actually it seems to be any keyboard, other than Stock AOSP. Still rocking it though. Feels like home, since this is what I have been running on my Galaxy Nexus!
[Nexus 7 (2013) Original Android Development] gmillz:
Its been fixed and will be in the next build :)
[Nexus 7 (2013) Original Android Development] paulhoop:
Swiping on stock ASOP Keyboard FC's for me.
[Nexus 7 (2013) Original Android Development] gmillz:
Sorry. Known issue and brink looked into
[Nexus 7 (2013) Original Android Development] android88:
Did you read the bugs list in the OP or even one post above yours ;)?

Its a known bug and being looked into...
[Nexus 7 (2013) Original Android Development] paulhoop:
:confused:

lol, known bug confirmed then, but not mentioned in OP and post above mine is about swiftkey not stock.
[Nexus 7 (2013) Original Android Development] dysolv:
Excellent. Thanks again for everything you guys are doing!
[Nexus 7 (2013) Original Android Development] Riddlah:
Has anyone had their device freeze when trying to reboot? I've had this happen using the power menu and while trying to change the dpi.
[Nexus 7 (2013) Original Android Development] paulhoop:
Just FYI, TIB will boot into recovery, I never like doing the power, vol - method... :crying:
[Nexus 7 (2013) Original Android Development] gmillz:
New build in OP
[Nexus 7 (2013) Original Android Development] yellowdie:
Thank you! I can't wait to get this installed! :D

Just fyi, my Chrome (on Win7) thinks the zip from darkspadez.com is malicious... :eek: The Devhost mirror wasn't flagged, but it took forever to download. And I assume the Gapps will stay Build 1 for awhile, right?
[Nexus 7 (2013) Original Android Development] prstorero:
Chrome likes to flag things a lot sometimes. I just ignore it when I know the file is fine :P

prshosting.org
[Nexus 7 (2013) Original Android Development] thecdn:
I didn't flash alpha 1, waited for alpha 2. After it flashed I had no root. Wasn't sure what to do so I flashed the update su zip I had from the unlocking process. That didn't do anything. I have since restored my stock nandroid backup as I didn't know how to proceed and saw nothing reported here.

Am I the only one who had this issue? Is there something I could have done while in the rom to get root back? Will see what those smarter than me have to say. I want to get my favourite rom on my new N7 :laugh:

(After that failure I flashed PA. It had root working but TB wouldn't restore anything - just paused at 0% when I started it. Then I gave up and went back to stock)
[Nexus 7 (2013) Original Android Development] kayone73:
These are known issues with other ASAP custom roms as well.

1. To get root to work, you just go to settings - developer options - root options - select Apps+ADB then your tablet will recognize root

2. Ti Backup - this is more complicated, perhaps someone else can type this out in a step by step explanation, im on a mobile device and it'll take too long to type out.
[Nexus 7 (2013) Original Android Development] shreddintyres:
I've had this before but only after a reboot, rotating to portrait and then back to landscape with quick settings open has always fixed it for me

FLO'd from my fingertips
[Nexus 7 (2013) Original Android Development] runner77:
Just came across a new weekly build(1.2) up on the SlimBean site! Downloading now.
[Nexus 7 (2013) Original Android Development] klaust58:
I have the same problem with titanium backup (and maybe more) with weekly-build-1.2 as with the broken weekly from yesterday. Anyone else?
[Nexus 7 (2013) Original Android Development] Natakranta:
Try changing titanium folder from legacy back to 0. Somebody on mako or maguro slim thread wrote it solved the problem.
[Nexus 7 (2013) Original Android Development] shreddintyres:
Did you flash build 990 then flash 1027 over it? Or are your problems after a clean flash?

Build 990 was the broken one

FLO'd from my fingertips
[Nexus 7 (2013) Original Android Development] klaust58:
i flashed dirty over official-902. later i will try a clean flash...

thanks.
[Nexus 7 (2013) Original Android Development] hyperxguy:
The old bootloader is still probably OK. But can anyone confirm the latest bootloader (from JSS15R) is OK with latest slimbean ?

Thanks.
[Nexus 7 (2013) Original Android Development] looney2388:
Im on build 1-902. About to dirty flash build 1.2-1027 JLS36C. I came across this from factory images website:

Factory Images "razor" for Nexus 7 [2013] (Wi-Fi)

Version

4.3 (JSS15Q)

4.3 (JSS15R)

Factory Images "razorg" for Nexus 7 [2013] (Mobile) [LTE?]

Version 4.3 (JLS36C)

So by this having JLS36C which seems like the LTE version, if I flash it on my wifi-only tablet will it still work fine and does it contain the fixes that wifi-JSS15R has? which are still some of the touch issues reported.
[Nexus 7 (2013) Original Android Development] DroidIt!:
Actually meant to ask about this myself. On the N7 are we SUPPOSED to manually update the bootloader ourselves or are they built into the roms and flashed with a rom like the boot.img. First nexus device so just not sure about this one :confused:
[Nexus 7 (2013) Original Android Development] Nebucatnetzer:
Nexus ROMs usually don't mess with the bootloader or the radio.
[Nexus 7 (2013) Original Android Development] v01rider:
Is this expected battery life? Just running slim no kernel.
[Nexus 7 (2013) Original Android Development] DroidIt!:
OK, was just wondering because I saw in Android Development that scrosler put out a stock deodexed JSS15R ROM and in that thread he included a twrp flashable bootloader update. Just wondering if that needed/should be flashed or no?
[Nexus 7 (2013) Original Android Development] hyperxguy:
Similar to my 2012 N7, Google updates (quite often) come with a bootloader update. But customedROMs don't provide such update -->

it's up to the user to upgrade the bootloader themselves.

Quite many people indicated no issue with old bootloader. But ...but... Google update them for some reasons, right ?

I normally have the latest bootloader. I've had not a single issue with my Tabs (while others are having unexplainable issues ...maybe the old bootloader ? who knows.)
[Nexus 7 (2013) Original Android Development] vagelis:
I flashed the new bootloader about a week ago when jcrosler posted it on his thread. No problems running the 1020 weekly or the stable build earlier on.
[Nexus 7 (2013) Original Android Development] bumbernut:
I did a reboot, and lost many settings, accounts, and some apps. Running the stable build.
[Nexus 7 (2013) Original Android Development] klaust58:
This morning, i did a reboot and it won't came up! The actual weekly.

No wipe cache/dalvic helps and reflashing the ROM also not.

FullWipe....:rolleyes:
[Nexus 7 (2013) Original Android Development] ep0ch2:
Is it possible to make the Navigation bar look like the following screenshot with Slim? I.e. with nav buttons and time,battery and wifi icons within the Nav bar thus removing the need for the status bar? Or is there another Rom which can do this? Thanks
[Nexus 7 (2013) Original Android Development] Nebucatnetzer:
Not by default and your second question belongs to the Q&A section.
[Nexus 7 (2013) Original Android Development] v01rider:
I'm gonna try it