yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] TITANote2LTE:
So we are to use JWR kernels now eh.... thats great, downloading now thanks guys.

Is Faux's123 kernel recommended over stock with the addition of intellidemand?
[Nexus 4 Original Android Development] android88:
Stock kernel is always the recommended one ;)
[Nexus 4 Original Android Development] justthefacts:
JS or JW kernel?
[Nexus 4 Original Android Development] prbassplayer:
Read the changelog ;)
[Nexus 4 Original Android Development] ricstone:
So how do we uninstall Google Now?
[Nexus 4 Original Android Development] Mercado_Negro:
I wanted to ask. Where do I have to go to check what was merged and what not? I'd like to know if that sms delay feature made it or not :) (I checked Github but I can barely understand it).

I'll sure do. I must say I'm really impressed with the stock slim kernel, its perfomance is really great. I haven't felt the need to flash franco.Kernel, which is always my preferred kernel.
[Nexus 4 Original Android Development] mi3zu:
Slim center
[Nexus 4 Original Android Development] prbassplayer:
Changelog has a fast list of big changes else check our github :)
[Nexus 4 Original Android Development] rwaempires:
use Titanium Backup...find google search...uninstall
[Nexus 4 Original Android Development] Mercado_Negro:
Thanks, just read the changelog before flashing and didn't find what I was looking for. Maybe it hasn't even been commited yet. I'll check Github again from my computer tomorrow, I'd like to learn how to read and search there.

Cheers... Flashing beta 5!
[Nexus 4 Original Android Development] yethz:
Id rather delete all my JSS kernels backup and download JWR than experiencing deadlocks before ;)

Thanks a lot for making the right choice and bow down to the Slim Dev Team for making Android experience to its un-paralleled level (dont mind what i say, Im just hypernated with the result of using this SlimBean build).

Thanks a lot....

•[ Google Nexus 4 (LG-E960) ]•
[Nexus 4 Original Android Development] elderap:
Edited: resolved
[Nexus 4 Original Android Development] kufikugel:
yeah let us see if it really fixes this issue....PA reverted way more back. We just do not fetch the retire fence from the MPD driver any more and duplicate it like it was before...at least only a change of 2 lines in the complete source + the kernel change of course, If this fixes it then we have it already good isolated and then we can concentrate on this codepart
[Nexus 4 Original Android Development] ensboarder:
Flashed a jwr kernel and bootlop
[Nexus 4 Original Android Development] prbassplayer:
How is this helpful? Mind you the stock kernel is jwr... Fail to see why others won't work...
[Nexus 4 Original Android Development] ensboarder:
Don't know if is helpful or not, I'm just reporting.. Sorry for my English
[Nexus 4 Original Android Development] prbassplayer:
No your not. No logs, no steps to reproduce, you didn't even specify which kernel. Saying "stuff don't work" isn't reporting it's making useless posts :/
[Nexus 4 Original Android Development] playya:
I believe they are try to say if you are going to post errors try and at least post a logcat with it. Posting errors and no documentation makes it hard for developers to reproduce and figure a way to fix the issue. In the future if you have an issue try and post some documentation with it or its kind of useless to most developers...

Thanks
[Nexus 4 Original Android Development] brian88:
I got the same issue :( Franco r182 plus JWR

We got bootlop, how could we report issue by logcat

Sent from my Nexus⁴
[Nexus 4 Original Android Development] rwaempires:
Flash latest faux or semaphore...or stick to stock...
[Nexus 4 Original Android Development] ensboarder:
That's the same kernel I flashed.. Also flashed matr1x but but acting weird when swiping left and right or opening apps drawer, don't know how to explain
[Nexus 4 Original Android Development] playya:
check this site as it may help and my post was not only for the one post you had but as an fyi for any future posts in reference to similar issues.

Here is some more info for you here

So, let's say you're experiencing a boot loop and want to get an idea of what's going on "under the hood". It can't hurt to peek with adb logcat. Even if it just looks like gobbledygook, you can copy and paste the output (usually the errors will be obvious if you sit down and look-- stuff like "ERROR!!!!!" may appear) to a site like pastebin.com (although make sure that you're not pasting personal information such as local network addresses or anything sensitive, which occasionally will appear in the log). That way, you can show people the problem (via a link) for further discussion, debugging, etc.

Anyway, from now on-- instead of just saying "Help! I'm bootlooping!", maybe say "Help! I'm bootlooping, and here's a link to the logcat!"
[Nexus 4 Original Android Development] brian88:
Did you try the official Franco JWR kernel?

Sent from my Nexus⁴
[Nexus 4 Original Android Development] ensboarder:
Yes
[Nexus 4 Original Android Development] brian88:
The same problem?

You mean this http://db.tt/rwyfbp7H?

Sent from my Nexus⁴
[Nexus 4 Original Android Development] prbassplayer:
Nothing I can do about it guys. Franco JWR uses a different ramdisk. I'm not sure why its different or his reasons for it but it seems to not play nice with Slim. Other kernel devs like Stratosk or Faux's kernels should work fine as it injects the zImage in to existing boot.img, tends to play nicer and be compatible with the widest rom selection. So Sorry for bad news but thats how it is (at least from what I saw)
[Nexus 4 Original Android Development] Mercado_Negro:
Bad news indeed but thanks for letting us know, that info is very useful. Like I said before, I've been using the stock kernel and I'm very happy with it. It's just sad that we can't play from time to time with franco.Kernel.
[Nexus 4 Original Android Development] :
So the release post for b5 says:

- under Device Specific>mako

However, it also says:

- under Device specific issues and notes>mako

I'm confused. Is it based off JWR or JSS?

And, have they fixed deadlocks by patching or rebasing (like PA)?

Darn, that's the only kernel I use. :(
[Nexus 4 Original Android Development] prbassplayer:
For kernel purpose it's JWR kernels. We fixed up 1 aosp commit in qcom/display to use jwr code but for everyone else use Jss. The rest of the rom is JSS. Specific commit that allows us to use JWR kernel on JSS rom is https://github.com/SlimRoms/hardware_qcom_display/commit/99d44d266ba02ce2cee74fdde8eaca70ecb14167

As for franco let's keep it off this thread. We won't mess with our ramdisk because of this.

Edit: For this to work needs a device folder commit as well to set the flag and the revert on kernel ;)
[Nexus 4 Original Android Development] gururoop:
Slim has been the best 4.3 rom since the day it was released.. with native support for touch control and tons of useful features unparalleled in any other rom.. I have hardly experienced the so-called deadlocks with slim even though I did experience them with the same setup and same set of apps in other roms.. now with jwr bits, its hard to imagine a rom better than this one...
[Nexus 4 Original Android Development] :
Oh, ok thanks! :)

Hmmm, alright...
[Nexus 4 Original Android Development] yethz:
To those experienced bootloop when flashing JWR kernels, try this; (I also got bootloop)

Wipe cache/dalvik

Flash stock JWR kernel (or faux enhanced stock)

And then flash your JWR kernel of choice

Wipe cache/dalvik

Flash supersu 1.60

Reboot system and wait..

Dont know what exactly was overwritten but it work.

Though i didnt managed to reproduce the bootloop when flashing jwr for the first time..

And i might add; Goodbye deadlock LOL!!

Havent got one yet since flashed B5...

•[ Google Nexus 4 (LG-E960) ]•
[Nexus 4 Original Android Development] brian88:
Now I'm pleasure with b4 + r182 plus about battery life, performance and stability. Hope Slim Team will do something to make their rom compatible with every kernels in next build. Really love this rom anyway :D

Sent from my Nexus⁴
[Nexus 4 Original Android Development] ahepas:
Logcat and kmsg concerning the dead wifi issue...
[Nexus 4 Original Android Development] prbassplayer:
No this is not our problem sorry.

This is on which build?
[Nexus 4 Original Android Development] nokiagye:
First time today my WiFi don't opens I have to reboot the phone to work
[Nexus 4 Original Android Development] ahepas:
on build 4
[Nexus 4 Original Android Development] prbassplayer:
What build?
[Nexus 4 Original Android Development] yethz:
Flashed Purified Kernel #172 (JWR)

•[ Google Nexus 4 (LG-E960) ]•
[Nexus 4 Original Android Development] zorginho:
May maybe it's a stupid question but it's possible to add fauxsound to slim kernel?

Inviato dal mio Nexus 4 usando Tapatalk 4
[Nexus 4 Original Android Development] nokiagye:
4 stock kernel
[Nexus 4 Original Android Development] prbassplayer:
I'm not sure why you guys are having driver initialization problems but try beta 5.i updated Prima.
[Nexus 4 Original Android Development] :
Why is it jwr instead of jss now?
[Nexus 4 Original Android Development] vergilbt:
Because the deadlocks...
[Nexus 4 Original Android Development] 1ceb0x:
Its JSS at its base but the room boots now only with jwr kernels.
[Nexus 4 Original Android Development] zubin111:
Hi, i just flashed b5, factory reset/ format system... Now there are some issues which i never faced in the earlier builds. 1) Wifi somehow does not stick, its like same as we had in 4.2.2 where sleep notifications didnt work, i switched off wifi optimization and all but still it stays that way 2) under camera i am not sure why but the focus seems to be bit haywire, by that i mean it does not focus at the point where i touch it after the initial focus, it only refocuses when phone is moved a little bit here and there 3) What are the kernel options available to tune by trickster, i saw uV implementation, is mpdecision is changed too?
[Nexus 4 Original Android Development] manpildo:
Is it just me or are Camera and Gallery apps missing? Flashed beta 5, minimal gapps and photosphere.
[Nexus 4 Original Android Development] Rohit02:
Guys can some give me a link to gapps.. m not able to get it.. also please provide me with a mirror link as the one in op is not working.. thanks a lot..

how is beta 5? issues if any?

I am on beta 3.
[Nexus 4 Original Android Development] OppiFjell:
ROM!!
[Nexus 4 Original Android Development] vlatkonexus4:
This Rom is really beautifull and smooth

Thanks for this rom developer/s,i have flashed so many roms,but i have found myself the enjoying in slimbean the most

Thank you for hard work on this project,keep up the good work and even in beta stage,really good,so i am waiting for RC release soon:good:
[Nexus 4 Original Android Development] zubin111:
Why the whole OP man??
[Nexus 4 Original Android Development] yethz:
Nope...

___________________________________

•[ Google Nexus 4 (LG-E960-16GB) ]•

ROM: SlimBean 4.3 Beta Build 5

Kernel: Purified Kernel #172 (JWR)

Recovery: PhilZ Touch Recovery v5.11.2
[Nexus 4 Original Android Development] zubin111:
In addition, Just a request can FauxSound and drivers be included in the kernel?? :fingers-crossed:
[Nexus 4 Original Android Development] hooliganx:
good signing! everyone could do so. thereby save those who want to help and all the devs time to ask which version of rom or kernel or modem are using. not need to know who uses Tapatalk or XDA app or know any other details about anything else. is a development thread, so let's save labor and be more direct in what we can be. ;)

Mako*Carbon.09-05*JSS-4.3*UHC-b2*TWRP.2.6*Radio.0.84*(full wipes always!)
[Nexus 4 Original Android Development] shr33kant:
Just using the latest beta, no deadlocks, everything is running nice and smooth! Full clean flash with minimal gapps.
[Nexus 4 Original Android Development] alexkno:
unfortunatly for me on alpha 3,2 and 1 it is not the case...always jumped over after a while to to franco and always lost root (not even always on first boot but at some point it was gone) so needed to flash supersu....I see it affects some users and some not. Maybe it's due to the way of flashing the rom (I always wipe system) or whatever. No big issue and all those who are affected know what to do or can (should...) find a workaround within 2 seconds by doing a search

---------- Post added at 08:51 AM ---------- Previous post was at 08:46 AM ----------

I had this once (kept awake 16h) by google calendar sync...deleting my google account, reboot and recreating it solved the issue and I never saw it again

---------- Post added at 08:56 AM ---------- Previous post was at 08:51 AM ----------

ok, so if you want a persistent notification, then you get it :)

But I guess in the app itself there is an option to replace the temperature with an empty field (widgetsoid had this for example). So even if you loose the space for other notifications, you are not bothered by the temperature.
[Nexus 4 Original Android Development] dark_ente:
App Ops is nice but it can't block the permission the first time the app is used, whereare Privacy Guard will block immediately. So you'll lose data first before you can block the apps, and there's no way around. So at the moment I think it's not a good idea to replace PG yet.
[Nexus 4 Original Android Development] gecko316:
did a full wipe, flashed rom, franco 174, aio apps, and 1.51 su

all seems to work. did initially get stutter when trying to load webpages within chrome. seems like it's gone now, not sure if gaining root access and allowing franco app to tweak things made the difference.

one thing i see is the graphics tearing when scrolling. i do recall this being a problem somewhere, but don't remember if there's a fix yet

slimbean is kicka$$
[Nexus 4 Original Android Development] leiros:
got the graphics tearing while scrolling on an other kernel as well, but not on franco or stock.
[Nexus 4 Original Android Development] randyspants:
You have to use the JSS version of franco to not get the tearing, I would find it but its late and I'm sleepy
[Nexus 4 Original Android Development] a g bell:
Doesn't happen with stock kernel that being jss and all :banghead::)
[Nexus 4 Original Android Development] it_ferret:
First of all thanks for such a smooth 4.3 ROM loving it.

Any chance of the T9 phone apk being implemented? Or am I being thick and missing something?

Thanks in advance.
[Nexus 4 Original Android Development] nextking:
There's an option in call settings called "dial pad auto complete" . Enable that and you should be good
[Nexus 4 Original Android Development] it_ferret:
Hey thanks [MENTION=2568456]nextking[/MENTION] I was looking and looking and clearly missed it. (feel a little embarrassed)

Now this ROM is complete for me.

Excellent ROM and support.
[Nexus 4 Original Android Development] android88:
We've talked about it, but for now we're sticking with PG.
[Nexus 4 Original Android Development] Pete_79:
Actually, i think this is different from user to user. I installed this rom and tried with stock kernel, i still lost root. Sorted it with SuperSu tho.
[Nexus 4 Original Android Development] yellowdie:
I figured out the no root issue that some people are having!

If you have the stock Slim kernel or any JSS kernel (like the unofficial Franco version), then you see this:

If you install any JWR kernels (like the official Franco), then you see this:

The ROOT ACCESS option is missing entirely if you don't have a JSS kernel!

[MENTION=4451743]android88[/MENTION], you and other people (myself included), kept saying "just change root access to 'apps and ADB.'" Which worked for some, but not for others. So if people flash a JWR kernel right away (like I do), then they would need to flash the superSU package as well. If you keep the stock kernel on your first boot, then you can change the root access like it should and the built in superuser should work like normal.

That's why everyone's been complaining about the same issue and no one could hammer down exactly where the problem was. It literally was one way for some people, and another way for others! Gah! I hope the JWR screw up goes away soon!

:):D:laugh::good:

Extra: And for what it's worth: 'USB debugging' is an option when both JWR and JSS kernels are installed, but 'USB debugging notiy' doesn't show up on JWR kernels. Weird... lol
[Nexus 4 Original Android Development] playya:
got to admit that's a great find but my question is why would you flash a jwr kernel on a jss based rom? Its been noted that the wrong kernel creates screen tearing and other issues. Way to keep digging and get to the bottom of stuff though :good:
[Nexus 4 Original Android Development] yellowdie:
When Slim 4.3 first came out, there weren't many JSS kernels, so the devs said you could use JWR if you disabled HW Overlays. I imagine people are still just following that advice.

And for me, I'm friends with Franco personally, so I only use his kernel. :) Which is why I never had the "Root Access" option to begin with--so that's what got me curious and thinking about it. :D
[Nexus 4 Original Android Development] hakim7489:
i've lost my bookmarks on stock browser. how do i get them back? searched the thread and found only 1 user have similar problem, nobody replied him/her.

im using centre clock option with normal case date and small font for am/pm on statusbar. sometimes the clock disappears and i need to turn on/off the real dark slim option to get it back. battery icon totally gone now even i've tried changing different battery styles.

other than that, and combo with unofficial franco r174 for jss, this rom is perfect for me. great work devs!
[Nexus 4 Original Android Development] leiros:
Currently on the first run with the unofficial franco kernel. Some UV and UC to 1100mhz

currently on 16h 15m, 65% remanining, 2h SOT

WiFi on whenever there is something to connect to

5 hours of somewhat bad connection - really bad connection (Both for wifi and phone signal)

on 3g net

This is just great.
[Nexus 4 Original Android Development] alexkno:
one thing: on the first alphas I played a bit and used first a JSS kernel which led to screen tearing and then switched to JWR...as of alpha 3 JSS Kernels work seamless.

I don't know exactly how it works on a N4. Is there maybe something kept somewhere? I remember from my old Samsung SGS2 times, there was a kernel cleaning script needed sometimes in order to get rid of some bins and stuff from other kernels. Maybe here there cold be something similar? Maybe I needed to flash superSu as I previously used JWR kernel and something is still left as i only wipe /system between the alphas?
[Nexus 4 Original Android Development] playya:
Yes I has an S2 and went through that myself at times but I did the same thing here as I did there. When flashing a kernel because of the different developers methods I simply reflash my rom as well. Takes seconds and I know I am starting with a clean slate so to speak... I tried the reset kernel that was posted in here and found that just reflashing rom worked better for me
[Nexus 4 Original Android Development] alexkno:
If you stored them in your google profile then they will be synced back once you enter your google account and enable browser sync in google account settings.

If you didn't sync them, then you may restore them from a previous backup (NANDroid, TiBu, Helium or whatever you backed them up with)
[Nexus 4 Original Android Development] yethz:
Sorry bro didnt get what u mean (sorry not very good in english/grammar)

My 1 word reply "Nope" is to someone who asks if franco kernel works on b5 (he edited/deleted his question before i press reply button, by the way).

And i want to answer more info but cant explain it will ;)

Sorry if my little support in this rom/thread makes it clutter.

Regards

_________________________

•[ Google Nexus 4 (LG-E960-16GB) ]•

ROM: SlimBean 4.3 Beta Build 5

Kernel: Purified Kernel #172 (JWR)

Recovery: PhilZ Touch (CWM) Recovery v5.11.2
[Nexus 4 Original Android Development] happiboi:
So running beta 5 ok so far :D

Wiped, flashed beta 5 rom + gapps ... no issues there, (camera/gallery etc are ok?). Also flashed semaphore 1.6.0 kernel (jwr version) ...running fine as well.

side note: uninstalling app on beta 5 still suffers from random reboot? log attached
[Nexus 4 Original Android Development] hooliganx:
hehehehe. you don't understand. I'm saying that everyone should use the signature (infos in end of post) to give the information about what using. just as you did. I'm not criticizing you. :D

Mako*Carbon.09-05*JSS-4.3*UHC-b2*TWRP.2.6*Radio.0.84*(full wipes always!)
[Nexus 4 Original Android Development] D33PO:
Lol no, as far as I know, he gave you a compliment for your signature, which is neat, actual and detailed. :thumbup:

Sent from space
[Nexus 4 Original Android Development] nokiagye:
Beta 5 is up go for it

Do you read this?

Build 5

mako

Upstream to Linux 3.4.60

Added Stratosk's UV implementation

Updated Prima to CAF release 3.2.3.109

Added Faux123's Intellidemand

Switched to JWR base

Other smaller things

So we need the jwr kernels

Android88 can you make a stock jwr overclocked kernel like the jss test?
[Nexus 4 Original Android Development] 1ceb0x:
What's wrong with the stock kernel? Also, I don't see the word "please" in your request. These devs are doing it in their spare time so a demand approach is not the good way to go around here.
[Nexus 4 Original Android Development] manpildo:
Nevermind, they are back after clean flashing. Something got screwed on first flashing attempt (error 7) and I guess this messed something up and a wipe was needed.
[Nexus 4 Original Android Development] nokiagye:
If he make it he will get a big thanks of me..I can't understand some people inside here...

What is yours problem? You learn us how to talk? other times correct your self
[Nexus 4 Original Android Development] fkloznica:
problem connecting to home wi-fi on beta 5.. my connection is every second out of range even when i am 20 cm in distance.. what to do.. ? :(

i was on beta 4 and didn't have this problem.. did factory reset and then installed beta 5

edit: fix the problem for now.. best rom ever ! :D
[Nexus 4 Original Android Development] Shardzmi:
So we won't be able to use franco with slim ?
[Nexus 4 Original Android Development] hooliganx:
easy guys... :p

I see Slim Team working in things that give us a excellent rom, with excellent tweaks and options in settings, and... excellent stability.

since I started use this rom, see this.

So, let thanks the Team for all this things.

Ask for another things/tweaks is normal. Everyone here wanna have THE BEST NEXUS 4 EVER! :D

And Slim work for it!

But all of us is free to try other things in XDA. So try it, for yourself. Let the Team work in reality relevant points. After this, we have a best rom and the Team, maybe, time to do this other little things ;)

Thank Slim!

N4*Carbon.09.05*JSS.4.3*Hells-Core.b2*TWRP.2.6*Radio.0.84
[Nexus 4 Original Android Development] ilamaan:
I saw few changes on cm's latest DSP Manager but this ROM yet has the older version. I hope the new DSP manager will be added to gapps. Thanks for the great work.
[Nexus 4 Original Android Development] 1ceb0x:
unfortunately no.

LE: it boots with francisco's jss kernel but sutters everywhere.
[Nexus 4 Original Android Development] android88:
Maybe, we'll see. But as [MENTION=2688060]1ceb0x[/MENTION] said, you can remember that we do this for fun, and when we have spare time we work on this. But the overclocking feature probably won't ever come into the kernel in the ROM officially.

There's a patch to add it into our ROM on our gerrit ;)
[Nexus 4 Original Android Development] TaRsY:
Yep glitches everywhere with franco. But stock works well
[Nexus 4 Original Android Development] QUIETLYloud:
Really liking the .25 animations
[Nexus 4 Original Android Development] elderap:
+1
[Nexus 4 Original Android Development] Shardzmi:
Yeah, slim is great but I can't give up on using Franco. It's just too good.
[Nexus 4 Original Android Development] veedubrocks:
Lost root access.... Anyone know how to get it back? Went from B4 to B5 with a clean install
[Nexus 4 Original Android Development] ciprianruse88:
Deleted