yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] ricardowec:
Sorry skinner but this is a Development From, not. Q_&A. You might check in the General thread.

Cheers

Sent from The Beast using Tapatalk 2
[Nexus 7 Original Development] simms22:
we here like to help our users/friends, we dont tell them to go search someplace else. if you cant help, someone else will. no need to send someone away.

main device settings, users http://www.expertreviews.co.uk/software/1296415/android-4-2
[Nexus 7 Original Development] stunndd:
This is what makes the Trinity and Rasbean threads the best. Always willing to help, esp simms22
[Nexus 7 Original Development] ricardowec:
Rascarlo,/Uber

Sorry to ask a question that probably has been asked\answered before but I am searching and don't find anything related.

Why is phone apk needed in this rom? ( It bears Rascarlo sig)

It suddenly started to FC (from boot - -. >up) with Uber's theme.

I have re flashed, fixed permissions, with same result. I'd does not happen with BM's theme nor without any theme.

Cheers

Sent from The Beast using Tapatalk 2
[Nexus 7 Original Development] ridearoundsolo:
This problem I came across is very minor but I'm curious as to why ROM toolbox makes this ROM reboot, I open the app and I get a reboot, doesn't happen on other 4.2 Roms again its very minor
[Nexus 7 Original Development] simms22:
delete the app data via the devices main setting, apps. then check if it still gives you issues.
[Nexus 7 Original Development] ridearoundsolo:
What's weird is that its not rebooting anymore lol but thanks though
[Nexus 7 Original Development] VanillaG0rilla:
After installing ubers theme, when i open rom toolbox, my n7 reboots. It worked fine before the theme. Its weird it would that.
[Nexus 7 Original Development] rascarlo:
new build is up.

GAPPS HAVE BEEN REMOVED.

changelog:

- Frameworks:

.fix notification icons not animating till ticker is updated

.use holo alert drawables

.remove GB alert drawable from reboot menu

.improve tethering notification icons

.performance increase in thumbnail handling

.audioService: don't adjust volume when vol-downing to vibrate or silent

.clear all button on recent apps

.tiles

.changed behaviour of the volume wake
[Nexus 7 Original Development] simms22:
gapps :) http://fitsnugly.euroskank.com/?rom=rasbeanjelly&device=gapps
[Nexus 7 Original Development] airmaxx23:
Thank you very much, downloading now.
[Nexus 7 Original Development] ÜBER™:
Woohoo, get to build today. :D

Sent from my Galaxy Nexus
[Nexus 7 Original Development] airmaxx23:
I just got a SOD on the new build while the device was on the charger, I tried pulling the last.kmsg but it wouldn't let me upload it. I dirty flashed from the previous build to the new build.

Edit: I'm going to do a full wipe and see what happens.
[Nexus 7 Original Development] ncvikingx97:
Can't wait to try it out. Good job

Sent from an AOSP , Rasbean'd Nexus 7
[Nexus 7 Original Development] simms22:
sods are a known issue with 4.2.X kernels, even stock and aosp(rooted and non).
[Nexus 7 Original Development] ÜBER™:
You know I've never experienced an SOD, well once but that was due to low voltage. Never have I had it JUST happen. :cool:

Sent from my Nexus 7
[Nexus 7 Original Development] airmaxx23:
OK, this is also the first one I've ever had on 4.2.
[Nexus 7 Original Development] smartpr1v4t3:
Thanks for this smooth rom.

I have a small pro blem and i dont know its rom related.

I use the version 5.1 with franco .82v and usb otg is not working. Any idea?
[Nexus 7 Original Development] gogol:
Yesterday was terrible :(

So, as I have predicted, like other ROM, after long time usage, the lag will come. And it did come. I tried reboot, it cured a bit.

Then ... because I read in other posts, we can greatly reduce this lag if we wipe the cache / dalvik cache.

Ok, I went to the Recovery and did just that, wiped the cache and the dalvik cache.

Booted to system (Android) ...

Guess what? It stuck on Google logo!!!! I waited almost 30 minutes. Tried second time, third time, same stuck.

I could go back to the Recovery though. And stupid me, I don't have nandroid backup of this ROM setup.

I flashed the franco kernel again ... same stuck ...

I reformatted the /system to f2fs and restored Xenon-HD ROM all-f2fs, it booted up to Android, but some apps didn't work properly (Facebook, Miniclip 8 ball), mostly cannot properly connect to the wifi.

I ended up flashing from scratch again, this ROM, the gapps, franco kernel, SuperSU.

It went back to normal again, still need to reinstall my apps (this is OK, I don't have much apps).

But still, how can this happen? Wiping cache and dalvik cache caused stuck on Google logo!
[Nexus 7 Original Development] atefi:
What about tilapia?
[Nexus 7 Original Development] DreadApex:
if you are using TWRP?

The latest versions have some quirks. scripts don't run correctly and formating (wiping) doesn't work as intended sometimes, especially with F2FS.

I had many issues with corrupted partitions and failed scripts.

If you are on the latest TWRP on your nexus, this is probably your issue.

I had to roll back to 2.8.3.0 for it to function properly again with scripts and formating.
[Nexus 7 Original Development] sldier11:
I tried your suggestion by installing TWRP 2.8.3.0 on a fresh install of rastapop with no luck. What happened was after I restored my nexus successfully and tested a rebooting into recovery TWRP 2.8.3.0 just hanged and I couldn't boot into rastapop anymore either. I even tried to reflash 2.8.6.0 and boot into recovery with no luck, still got a bootloop. I had to unlock my bootloader and re-flash 2.8.6.0 to get back into recovery. Still not sure if this corruption that keeps happening is a kernel issue or twrp. The TWRP thread claims it's the Franco Kernel and a new M Kernel was released yesterday for 5.1 but also causes a bootloop with this rom when the app start-up begins.

If anyone has a working fix I would love to hear it. This is a great rom with nothing but headaches since I started using it. I factory reset about 8 times since I started to try and figure out what has been causing the 'Unable to stat' issue in recovery leading to an unable to boot issue sometimes later on.
[Nexus 7 Original Development] anzi2001:
yeeeessss man this rom is awesome! any chance of getting a custom kernel of yours in addition to this rom?
[Nexus 7 Original Development] DreadApex:
I too was having these issues, as well as "unable to stat"

this was caused by TWRP 2.8.6.0. (for me)

This is how i solved it:

1.) full recover to 4.4.4 stock

2.) install twrp 2.8.3.0

3.) format system/data/cache using THAT recovery to ext4

4.) reformat to f2fs using that recovery. (to fix any corruption caused to the partitions before)

5.) full wipe (just to be sure)

6.) install rastapop, supersu, and franco

I had zero issues after this.

I have since gone back to kitkat, simply because i can't live without xposed so i'm going to wait until that is straightened out.

(I'm still hoping someone can provide a mirror to rascarlo's 4.4.4 vanilla rom by the way)

Another thing....m-kernel will NOT install with 2.8.6.0... it's a known issue (script errors, but they don't show in TWRP, they fail silently) and again requires 2.8.3.0.

The grouper is one of several devices that have issues with the new twrp releases, not sure if/when it will be fixed.

Until then the slightly older version works fine for me and i have not has any issues with corruption and scripts failing since. YMMV

I'd suggest trying again following the procedure i listed above and see if you have better luck.
[Nexus 7 Original Development] sldier11:
Thanks for the useful info. I currently ended up using TWRP 2.8.6 to format my cache and data to f2fs and then installed rastapop, franco kernel and gapps. I then booted into the bootloader and flashed the clockwork recovery.

Not sure how much this will help or at all really. I know clockwork mod doesn't seem to support f2fs like TWRP does.

I'm wishing I formatted now with TWRP 2.8.3 like you suggested but does this mean if I use this ROM I can't have a proper f2fs recovery? Are there other decent custom recoveries beyond clockwork and TWRP?

Rastapop is running fine right now without issue. I am thinking the corruption issue was TWRP and not the Franco Kernel regardless what I read on this thread.

Update: Clockwork does say it can't mount or open cache

Is this because it's formatted to f2fs and it doesn't support it?
[Nexus 7 Original Development] DreadApex:
Yes. if your cache is still f2fs and the CWM you have installed does not support f2fs then it won't be able to mount it.

You should be able to install TWRP from your current point without issues. (again i'd suggest 2.8.3)

This *shouldn't* affect your rastapop install at all and would allow you to format your partitions again, without having to start again from scratch.
[Nexus 7 Original Development] sldier11:
If I can say thanks, is this the 4.4.4 ROM you're looking for?
[Nexus 7 Original Development] DreadApex:
Thanks for the effort, but unfortunately no, that is not it.

That is a modified version and what i am currently running on my nexus. (with m-kernel)

It runs extremely well but I was hoping to get the untouched AOSP img originally posted in this thread.

However... it seems to have vanished from the interwebs.
[Nexus 7 Original Development] gogol:
Well, it happened again. After recovered from that, I don't know why, it stuck again at Google Logo.

And it even worse, it cannot go to the recovery, stuck at TWRP logo.

I don't know why, I just deleted some folders inside /sdcard, rebooted and got that problem.

So, panicked because I cannot go to the Recovery.

Lucky, fastboot still available.

Downloaded the official Android 4.3, did flash-all and everything went normal again with stock 4.3. Apparently that process also did all the necessary file system conversion, back to all EXT4.

All wiped though, including the /sdcard partition, all data gone. Not a problem, I didn't have important data.

Then I installed the latest TWRP and now it's back again, but without F2FS.

I will try for a while and see how it performs with EXT4. Otherwise, I can go back again with F2FS.

Anyone ever compared EXT4 vs F2FS? Does F2FS help significantly?

Thanks.

PS: Thanks, next time I will downgrade to the TWRP 2.8.3.0 :)
[Nexus 7 Original Development] DreadApex:
yes, f2fs makes quite a difference, it's very noticeable.

Mostly with write speeds, which prevents stutters and speeds up caching.

formating system to f2fs does almost nothing, but f2fs on data and cache is a large boost.

if you went back to 4.3, make sure your bootloader is up to date if you try again.

be sure to grab the newly posted images from google, the older bootloader has issues and does affect flashing.

if you are using an older image, it more than likely includes the old wonky bootloader.

get the new images from here: https://developers.google.com/android/nexus/images

Even if it is the same version you already have saved, the bootloaders have been updated in all nexus 7 image files.

so be sure to grab the new one and flash it (i suggest 4.4.4) before attempting a new recovery and rom again.

You can even extract the bootloader from the archive and flash only that, if you are comfortable with that.

good luck!
[Nexus 7 Original Development] gogol:
Ok, thanks for the info, I will do this then:

- Do flash-all using the official Android 4.4.4 image

This should wipe everything and also got updated boot.img

- Flash TWRP 2.8.3.0 (not the latest one)

- Using TWRP, format the /data and /cache to F2FS

- Install Rastapop 5.1, gapps, franco kernel, SuperSU

- Profit? :)
[Nexus 7 Original Development] DreadApex:
sounds perfect! the only thing different i did was flash super su before the kernel, but i doubt that makes any difference since i do all 4 in one swipe.
[Nexus 7 Original Development] gogol:
Strange ... Everything went perfect ... Used the device all night.

This morning, I decided to make a nandroid backup.

Hold power, choose boot to Recovery ...

Boot-looped!!!

Then it cannot go to Recovery ...

Rebooted ... boot-looped :(

Now, I am flash-all again stock 4.4.4

Yesterday, after I finished flashed the ROM, etc. it asked me to wipe the cache & dalvik.

I did, but I saw the cache was formatted as ext4 by TWRP. Why? I changed it to f2fs for sure. Then I changed the cache back to f2fs ... booted to Android, used it ... And boom this problem. Might this be related?

UPDATE: Reading TWRP and Franco threads, it looks like this might be caused by franco kernel with f2fs combination. Sounds plausible ... When I was with all ext4, no problem at all.

So, I am doing it again now, but with Lean Kernel ....

UPDATE2: Damn, Lean Kernel doesn't support Android 5.1 yet :( What now? M-Kernel?

UPDATE3: F*ck, M-Kernel boot-looped ... lol

Oh well, going to all ext4 now
[Nexus 7 Original Development] DreadApex:
Honestly, those partitions shouldn't make your recovery unreachable... neither should the kernel..

you said you held power and chose boot to recovery... what method did you use to get this option?

Xposed mod? something else?
[Nexus 7 Original Development] gogol:
From Android ... I meant, you know, the normal way to shutdown. But with rastapop, we have more option, such as boot to recovery.

I don't install any other fancy app like Xposed.

Except "Disable Service" to disable some Google Play services (wearable & analytic).

When I booted to TWRP, it boot looped. It cannot go to the TWRP menu.

What is your setup btw?
[Nexus 7 Original Development] elwood:
I am using the latest TWRP with r82 franco kernel, cache and data formatted to f2fs only difference is im running Chroma and having no issues. Only thing I could suggest is maybe after formatting to f2fs flash cwm recovery and flash RASTAPOP, gapps su and franco, then boot up, set up, reboot and flash back to twrp since only twrp supports the change of ext4 to f2fs. Just a thought?

April is Autism Awareness Month. Sent from my Sprint Galaxy S5
[Nexus 7 Original Development] gogol:
Back to all EXT4 ... rasta, franco ...
[Nexus 7 Original Development] rascarlo:
new build is up

CHANGELOG:

MERGE BUILD 5.1.0_r5 - LMY47O
[Nexus 7 Original Development] asim0:
Thanks! I guess you mean r5...
[Nexus 7 Original Development] rascarlo:
thank you. edited
[Nexus 7 Original Development] pjcanales:
Could someone do a review of this Rom with current Rom build so others like myself can see it in action :)
[Nexus 7 Original Development] sldier11:
Success

Thanks! Successfully updated to this r5 ROM with TWRP 2.8.6.0 and the r82 Franco Kernel.

So far so good, and following previous instructions I did start off with TWRP 2.8.3.0 to format my cache and data to F2FS and then flashed r1 Rastapop, r82 Franco Kernel and Gapps.

I then updated to TWRP 2.8.6.0 to flash this ROM and so far no issue's with 'Unable to stat' errors.

Thanks for everyone's hard work.
[Nexus 7 Original Development] DreadApex:
I'm glad to see this has been updated.

I'd love to join in on all the lollipop goodness again but i just can't function without xposed working properly, as i have become too accustomed to it being a part of my android experience.

does this new build finally squash the notorious memory leaks?

Xposed for 5.1 is making slow but steady advances and it shouldn't be too long before it is ready for primetime, i can't wait to hop on board again.
[Nexus 7 Original Development] ZeroDs111:
[MENTION=3124065]rascarlo[/MENTION] I am in Previous release, how i can Update? I need to flash all again?

Thanks
[Nexus 7 Original Development] Treboeth:
Just follow the instructions in the OP it's all there .
[Nexus 7 Original Development] ichigo_kurosaki:
sorry for quoting you bro. i just have a couple of questions:

on my first install of this rom, i encountered an error and tried to revert to stock. well that error i belive was due to my own foolishness..i mistakenly restored a system related app via titanium backup. so i did a reflasha dn a factory reset via TWRP using multirom TWRP btw). well my problem was when i tried to revert back to stock, restoration of my stock nandroid backup fails halfway through /system patition restore as though my backup is corrupted. my fired, who uses this same ROM also encountered the same.

on flashing an update, we know we can dirty flash this over the previous build. so if i flash this new build, will i need to also reflash everything (superSU, Gapps, etc)?
[Nexus 7 Original Development] smartpr1v4t3:
I only wanna tell you that i have the exact same problem. Flashed already the rom and r82 4 times. Its ending every time in the same way.

TWRP 2.8.3.0 - Install Rom - Gapps - Kernel

Format Cache and Data to f2fs

-> Everything is fine and i setup the device

After some reboots the device -> everything is fine

some times i reboot the device into recovery -> boom broken

Cant start recovery or rom. It doesnt help to flash recovery or system again. Tried with Nexus Toolkit. The only thing that restored my nexus was a Stock installation with Nexus Toolkit.

Edit:

I will try it now with m-kernel a75 and the new gapps version from rastapop 4-16-15

Edit2:

Ok i dont try m-kernel^^ to many bootloops in the thread

Edit3:

will stay with ext4 atm ^^
[Nexus 7 Original Development] Harpratap:
Which kernel are you using for f2fs?

If it's franco, then I think its a problem in the kernel and not the file system. Can you try bricked kernel or carcosa kernel and post the results?
[Nexus 7 Original Development] smartpr1v4t3:
Thanks for answer.

Will try it now with bricked ;) Report in some hours

Edit:

So my problem is now that the device is not booting with bricked. I think its because the missing ramdisk? Or did i something wrong. I'm not really understanding the thing about the ramdisk.

Flashed Rom - Gapps - Bricked Kernel

Format Data and Cache to F2FS

When i start the device i only see the rastapop logo.

All EXT4 the device is starting with bricked kernel
[Nexus 7 Original Development] five²squared:
1000 + "Thank you's" to Mister Rascarlo

I got my "grouper" on an impulse buy when it was on sale because the LTE version had just come out. I thought, ”7-month old Nexus tablet for $100? Why not?" Took it home, soft-bricked it about 127 times, and rooted it. The very first ROM I flashed was Euroskank-mostly because I dated a couple and the name cracked me up. Loved the ROM but I had a new toy so I went through most of the others (PA,CM,AOKP,SLIM,CARBON, blah, blah). Before long, I had new toys; HTC One m8, a gaming PC build, and a Cintiq graphics monitor to play with. The now WAY-outdated N7 went in a drawer until lollipop came out. Everyone knows how well that worked out so back in the drawer. Yesterday, I was Googling something and happened to see the word Rastapop and I recognized that word from somewhere. So I read the post and thought, "why not?" Dusted the N7 off, flashed 5.0.2., TWRP 2.8.6, Banks gapps, and your work of art, no pun intended, and all I can say is, ”Holy sh**......no, freakin', way.."

My NEW tablet runs cleaner and much faster than it ever did. First time I've seen what lollipop might be capable of - I've been experimenting all day to see what I can flash it with, install, etc-on a device I thought was hopeless. Can't imagine the hard work that goes into these ROMs, and then to share it. So thanks a million and I apologize for this book I posted.

From Euroskank to Rastapop.... Still makes me chuckle..
[Nexus 7 Original Development] sldier11:
Seeder App

For those of you or everyone really who still finds lag in any ROM even after formatting to f2fs try out this app. It works great on ext4 and f2fs partitions. I found rastapop lagging after some time like most of you have and this app makes a big difference in keeping your n7 responsive.

Seeder
[Nexus 7 Original Development] five²squared:
Thanks sldier11..Didn't have time to read that whole thread.. Is that the Seeder I can pick up in the Store or a modified APK I need to flash?
[Nexus 7 Original Development] smartpr1v4t3:
What Kernel are you using with 5.1 and f2fs?
[Nexus 7 Original Development] albysprx:
i'm using franco kernel and i not have any problems with f2fs o.O
[Nexus 7 Original Development] nycelitemaster:
Can someone tell me if their camera works? I installed rastapop 5.1 r5, with data and cache f2fs with Franco kernel.
[Nexus 7 Original Development] DreadApex:
give this one a try, it should work fine.

https://play.google.com/store/apps/details?id=com.magix.camera_mx&hl=en
[Nexus 7 Original Development] five²squared:
Never used the camera on the Nexus 7 but I just tried it on Rastapop with the CameraMX app and it seems to work fine.
[Nexus 7 Original Development] nycelitemaster:
Cool thx. BTW would formatting system help?

Sent from my Nexus 4
[Nexus 7 Original Development] five²squared:
I let the latest TWRP take care of that and it seems to be running smoothly. I'm sticking with the "if it ain't broke..." mindset with this ROM for now..
[Nexus 7 Original Development] sancamcal:
Any all F2Fs version for 5.1??
[Nexus 7 Original Development] Leonhan:
You can actually format data and cache to f2fs and flash this rom (along with a compatible 5.1 kernel). Formatting system to F2FS leaves you with no noticeable improvement.
[Nexus 7 Original Development] !crazy:
Anyone tried Legola's Convert2f2fs app on this ROM?
[Nexus 7 Original Development] five²squared:
I've been considering trying Torlaschi's Convert to f2fs app.. Trying to decide the safest ROM to convert. Prolly going to convert the XenonHD I was running before I flashed Lollipop. It's about the skinniest ROM I used with 4.4.4. Then again, maybe Slim.. Who the he'll knows..
[Nexus 7 Original Development] nycelitemaster:
Has anyone tried ram expander for n7 with rastapop and Franco kernel?
[Nexus 7 Original Development] five²squared:
I have plenty of RAM on my N7 (have the 32 Gb) Don't see the need yet. Devs? LOVE the toast that pops up after long-pressingback..... "app killed. Happy Now?" I appreciate attention to little details like that. {or I'm just easily amused}.

- trying not to be frivolous but need 10 posts so I can unlock posting screenshot and links-
[Nexus 7 Original Development] rascarlo:
new build is up

CHANGELOG

PLATFORM_VERSION=5.1.1_r1

BUILD_ID=LMY47V

MERGE BUILD 5.1._r1 - LMY47V
[Nexus 7 Original Development] stunned:
Any new features in the future? Hoping for extended desktop.
[Nexus 7 Original Development] five²squared:
Seems to be working fine on mine..
[Nexus 7 Original Development] abdulhamid1978:
I have been using this ROM for a while now, best and most stable for me. Does anyone know how to add centre clock and circle battery mod? Is there a flashable zip available for this?

Keep up the good work Rascarlo:good::good:
[Nexus 7 Original Development] five²squared:
There's a flashable zip I found for a center clock mod, it's at t

---------- Post added at 11:45 PM ---------- Previous post was at 11:43 PM ----------

Oops.. now I lost it, hang tight for a few.

---------- Post added at 11:50 PM ---------- Previous post was at 11:45 PM ----------

Don't know if it will work (I'm just running Nova Prime for customization, for now) but try this - - https://www.google.com/url sa=t&source=web&rct=j&ei=8YA5VZG6CPj7sATH6YHADg&url=http://nexus5.wonderhowto.com/how-to/center-status-bar-clock-android-lollipop-0158908/&ved=0CCgQFjAB&usg=AFQjCNGHthCLGD3T8dGp9ZZVjrmihqejVQ&sig2=_ItZqeI5pDWUQotf68G70A
[Nexus 7 Original Development] limaunion:
I've been using Slimkat for a long time, till a month ago when switched to this ROM. I like it very much but find it so slow when it wakes up after a long period (couple of hours). The first 5 minutes are really almost unusable, I've to wait for any application to start running. Is anyone experiencing something like this?. This has never happened with Slimkat. I'm using ext4, as with Slimkat. I'm currently using a release from March but will update to the latest version released today soon. Hope to notice an improvement with the general responsiveness. Thanks.
[Nexus 7 Original Development] five²squared:
I've been using Rastapop for the past week.. flashed initially last Saturday and updated today. My n7 starts very fast and doesn't show any lag until I have 7 or 8 tabs open.