yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] Goku80:
Guys anything I can do about this wakelock please. I honestly don't get why it's this high
[Nexus 4 Original Android Development] shayne77:
SMS notification in your status bar? Sat there for a long time? Read reports? Ummm... A none default setting? I have 0.3s for my SMS app.

sent from my Slim'd Nex4
[Nexus 4 Original Android Development] Goku80:
Oh never thought that would cause a wakelock
[Nexus 4 Original Android Development] chrolmesq:
House often does this happen? For me oily t only happens when I'm in low data areas and I send an m mms.
[Nexus 4 Original Android Development] Flak:
That unofficial beta1.2 has been working great. Haven't experienced any deadlock's, at least not that I've noticed. And the rom in general is extremely fast and smooth when compared to official beta 1.
[Nexus 4 Original Android Development] Goku80:
Don't know mate to be honest seems to be all the time
[Nexus 4 Original Android Development] Kurre:
I think I saw someone mentioning that it's cause by something of rogue mms message (?) But I don't have any facts about this issue.

Have you guys noticed this after sending a mms instead of sms?
[Nexus 4 Original Android Development] Goku80:
i do not send mms as it costs to much were i am from
[Nexus 4 Original Android Development] RunRa:
file Gapps name "Slim_Gapps.4.3build.beta.1.zip(Size 42.5MB)" What increse form GApps_Core_4.3.zip (Size 16.8MB) ?
[Nexus 4 Original Android Development] damngood98:
gmail, music, youtube, etc....gapps core from banks doesn't include anything that can be found in the market....slim uses a different dpi, is themed so some of the extras are included
[Nexus 4 Original Android Development] yethz:
Yeah ive seen that on RoundR app also..
[Nexus 4 Original Android Development] chrolmesq:
Did they fix the lockscreen? With the new beta.
[Nexus 4 Original Android Development] JNewms:
What do you mean? I wasn't aware of anything being broken...
[Nexus 4 Original Android Development] chrolmesq:
The inability to initiate apps through the lockscreen. Like Google now from the nav bar.
[Nexus 4 Original Android Development] leiros:
Gotten this twice, but it was when on wifi and I had an incomming mms on the way. data off. it would wakelock untill I turned on data..

For now I have turned off auto-recieve MMS messages, and it seems it has fixed the issue for now

Also; regarding the snapchat rebooting issue. After I adjusted my voltages it seems it has been fixed for now. Had it UVed by 100mv, and after I fixed some of the upper values it seems its been resolved for a while.
[Nexus 4 Original Android Development] qu3becker:
Nope. Only Google now is affected by this issue AFAIK,

--

Report on the new beta. I don't text a lot so it didn't happen on the first beta but it did happen once when writing a post with Tapatalk with 1.2. The phone froze for 5 seconds and the keyboard closed itself and came back soon after.
[Nexus 4 Original Android Development] alexkno:
Yes, thats the known freeze on 4.3 ROMs...
[Nexus 4 Original Android Development] qu3becker:
Yup, on Mako only it seems.

I stated that because the new test beta 1.2 was supposed to fix this. Otherwise I'm not really affected by that bug that I couldn't care less but I sent my feedback anyway to help the team.
[Nexus 4 Original Android Development] alexkno:
Ah OK, you mean the test build...yea then its important that you provided the feedback as that's what kofikugel asked for :thumbup:

Sad to see that the fixes seem not to help. Seems to be digged quiet deep

Tapatalked from my Nexus7
[Nexus 4 Original Android Development] A2Eric:
Insufficient storage available error

I get this error 'Insufficient storage available' error when trying to download random apps from the Play store. The latest was the Google Play Music app. Started happening after I flashed this 4.3 ROM. Anyone else experience this one or know of a fix? I currently have over 6GB of storage on my N4 so not sure why it thinks I'm out of storage.

I also cannot restore apps from Titanium Backup, it just hangs when trying to restore and I have to manually stop the process.
[Nexus 4 Original Android Development] Flak:
For the Google Play issue, does this happen when downloading via wireless? Ever since the update to 4.3.10 of the play store I'm running into lots of various errors and issue when trying to use the Play store over WiFi. But if I use it over cellular data everything works fine.

For Titanium Backup, did you change it to use the legacy folder? Titanium Backup > Menu > Preference > Backup folder location > Detect > Whole Device and choose legacy. By default it uses /storage/emulated/0/titanium backup.
[Nexus 4 Original Android Development] A2Eric:
Thanks for the response, it happens when using regular data also.

I just changed to the legacy folder but it said 0 of 1100 files moved. So I guess it didn't work? Is this a new thing in 4.3 because I've never had to do this before?
[Nexus 4 Original Android Development] Flak:
It doesn't move any files (at least not that I've noticed), just changes the sym link. Trying restoring your back-up now.
[Nexus 4 Original Android Development] A2Eric:
Still hangs and won't finish. I think I figured out why though, it's a system app from a previous ROM so probably not compatible with Slimbean. I'm all screwed up since going to 4.3. I'm locked out of Dropbox account because I can't restore my data from the Google Authenticator app that generates my Dropbox verification codes and my backup phone number with Dropbox is an old TMobile that's no longer active. My fault for not updating my info but still a pain in the ass!
[Nexus 4 Original Android Development] perfoliate:
Freeze in text input on test build here as well. Just reporting for test data.
[Nexus 4 Original Android Development] AbuYazeedUK:
I can't launch Google Now through the lock screen either, beta 1
[Nexus 4 Original Android Development] mendozaram:
I got a couple of freezes with beta 1.2. Obviously less than beta 1.

I keeping testing
[Nexus 4 Original Android Development] senses!:
Me too. A lot of freezes in settings with 1.2.

Enviado desde mi Nexus 4 usando Tapatalk 4
[Nexus 4 Original Android Development] yethz:
Got no freezes on 1.2 test build since yesterday..

And seems stable enough for me ;)

Thanks Slim Team.
[Nexus 4 Original Android Development] playya:
I second that test build 0 issues
[Nexus 4 Original Android Development] ElliSkyline:
I got a few deadlocks on Beta 1.2 this afternoon but other than that its smooth

A lot better than Beta 1, not as much freezes with this build compare to previous
[Nexus 4 Original Android Development] brian88:
Would you mind explaining me what happens when a deadlock appears? I've heard about it lately but dont know what it's :(

Sent from my Nexus⁴
[Nexus 4 Original Android Development] ElliSkyline:
Really? Deadlocks is when your device Freezes up and you can't do anything at all but wait until your device starts working normal again
[Nexus 4 Original Android Development] reicute789:
I just installed beta 1.2, gapps and extras with full wipe a couple of times. Right after first boot i downloaded root checker but it says my device isnt rooted.

I apologize in advance for i dont know how to do a thread search on xda app.

Thanks
[Nexus 4 Original Android Development] dorqus:
Settings -> developer options -> root enabled select apps and adb
[Nexus 4 Original Android Development] gallardo5:
Everything looks better with density on 268, but you can always change it in settings>interface>LCD density

I was worried the same, so I downloaded it and opened, it seems to be a ROM for some device, as it includes all the files that are in ROM for N4, I'm not sure what device is it for tho
[Nexus 4 Original Android Development] qu3becker:
The flo is the new nexus 7 so don't flash it on your nexus 4 (obviously).
[Nexus 4 Original Android Development] rokK0:
Great work slim Team....

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] JNewms:
I just got on this ROM like about an hour or so and set it all up. I have to say, this thing is just flat out beast. Can't believe I waited this long to try it. Great work guys!
[Nexus 4 Original Android Development] randyspants:
I dirty flashed over 4.2, aosp keyboard crashes now.

I know I should just wipe but was wondering if there was a easy fix?

Also back does not seem to be working for me on pie.
[Nexus 4 Original Android Development] JNewms:
Yes, do a full wipe
[Nexus 4 Original Android Development] BxingFetus:
This is fantastic work!! I've had 3.1 running for a couple of hours and battery is great, very fluid. Using stock kernel. Everything I use works just fine, no root issues whatsoever. Thanks slim team for the continued development.
[Nexus 4 Original Android Development] a63548:
Just wanted to say thank you for the amazingly smooth 3.1 alpha release to everyone involved with SlimBean. You are all seriously awesome! :)

Also I wanted to ask, as I noticed that on 4.2.2 SlimBean the days of the week and month are not abbreviated like shown, while I think in stock as well as 4.3 alpha both are abbreviated. Just a tiny request if it could be changed back or if it is possible on 4.3 to show the non abbreviated days of week or month. ;)

Thank you for everything!
[Nexus 4 Original Android Development] desmoloch:
Battery life is very impressive!!
[Nexus 4 Original Android Development] leiros:
3.5h isnt exactly what I would call impressive SOT
[Nexus 4 Original Android Development] Pete_79:
Great work Slim team.

But i cant find Superuser :/ Trying to start Franco updater and it says i dont have superuser access.

I found superuser, but i cant give any apps SU access, and i dont get a promt that the app wants SU.

Thanks

Pete
[Nexus 4 Original Android Development] BxingFetus:
Check under advanced in settings.

Sent from a slimmed up nexus
[Nexus 4 Original Android Development] Pete_79:
Thanks, edited my last post that i found it, but i still have the same problem, apps that needs root doesn't ask for it, or at least i do not get a promt.
[Nexus 4 Original Android Development] desmoloch:
Sure it is. Depends on what you are doing while screen is on!

I played plants vs Zombies 2 hours...
[Nexus 4 Original Android Development] leiros:
Kill and restart the app.

They might not ask for it if you've opened it before enabling root

---------- Post added at 10:13 AM ---------- Previous post was at 09:45 AM ----------

Anyone got an idea why titanium wont restore when coming to 4.3? clean install.
[Nexus 4 Original Android Development] shayne77:
I don't get comments like this... You've modified the base Slim ROM to your personal tastes and expect the Slim devs to fix YOUR problem your having with those other mods? Wouldn't it make sense to go to those devs instead? Even TB is not a problem of Slims, it's a setting change for ALL 4.3 ROMs isn't it?
[Nexus 4 Original Android Development] BxingFetus:
You need to change the backup/restore to legacy instead of emulated in preferences.

Sent from a slimmed up nexus
[Nexus 4 Original Android Development] leiros:
I already tried 3 times. what seemed to fix it was restoring a nandroid, and backing it up with an updated version of TB. then doing a clean flash and restoring from legacy.
[Nexus 4 Original Android Development] Pete_79:
In preferences where?

I do not use Titanium Backup, actually i dident do any backup at all except for Nova launcher.
[Nexus 4 Original Android Development] BxingFetus:
Scroll down to backup folder location, then press detect, press whole device then you'll see two options come up, the emulated path and the legacy path, after that press use current folder that will finish the selection and after that all should be good. But if you don't use tibu then no problem.

Sent from a slimmed up nexus
[Nexus 4 Original Android Development] reicute789:
Thanks man. I just saw it too. Was about to edit my post but you beat me to it. :D
[Nexus 4 Original Android Development] brian88:
Ahh, thank you, man. If deadlocks're like you said, I got it sometimes both on b1 and b1.2, espeacially with FB app, other apps I've not gotten yet. It freezes up in about 4-5s and then everything works normal

Sent from my Nexus⁴
[Nexus 4 Original Android Development] jtwlbz:
I started experiencing freeze on 1.2.
[Nexus 4 Original Android Development] Beerad875:
Why isn't there a g+ community?
[Nexus 4 Original Android Development] android88:
There is: https://plus.google.com/communities/104509876514579429216
[Nexus 4 Original Android Development] ElliSkyline:
I hate it too! Yeah same issue here FB app, Chrome and Typing is mostly where I experience it.

Parananoid I think had fixed it but I'm staying with Slim!

I've been a loyal Slim user from day one I got my N4 and also used Slim for the Galaxy S2.

I just hope Google pushes out a fix for this or Slim team figures it out.
[Nexus 4 Original Android Development] shayne77:
Try clearing Play data (settings/apps) and see what happens.
[Nexus 4 Original Android Development] reicute789:
Reporting freezing on viber. Using beta 1.2 and the kernel that comes with it. I juat opened viber then bam. Freeze.
[Nexus 4 Original Android Development] shayne77:
Sounds like CM are building nightlies.

Edit: already done for Mako :)

sent from my Slim'd Nex4

---------- Post added at 05:16 PM ---------- Previous post was at 05:12 PM ----------

Elaborating on this a bit more, i can't see "NTP_SERVER" in etc/gps.conf

Is that why apps setting this value fail? Has something changed in 4.3 regarding GPS? (NTP servers)

sent from my Slim'd Nex4
[Nexus 4 Original Android Development] H-Body:
Hey guys, i allready used the search function, but i didnt found an answer (Only used tapatalk, so perhaps there is allready an answer in this thread, then dont be too angry with me).

I want to try the stock slim kernel for the first time (always used Franco). Is it possible to not only control the RGB settings but also gamma, saturation and all other values i need to apply pa's halfbreed settings via trickster mod?

THX for your answers!
[Nexus 4 Original Android Development] ElliSkyline:
Yes you can set it through trickster mod, after it's set turn your screen off and when you turn your screen back on it should be applied.
[Nexus 4 Original Android Development] kufikugel:
Hey guys,

thanks for testing. As I see the deadlock is at least a bit reduced (that the rom is fast is because of other patches we applied :p).

A general note from us about the JSS deadlock issue.

1. We support a lot devices not only mako. Currently only mako is effected by this random deadlock. As well flo was effected which was solved some days ago with the new blobs google pushed (JBQ story). All other devices do not have this issue. Tbh to tell JSS is borked and not good as a general statement which some are doing....I do not comment it. Just not the truth

2. At least we know that the main issue comes from the qcom display repo. Reverting it to jw would solve it.....but would break any compatibility to any kernel which has JSS (terrible screen tearing etc etc) and will break eg flo at all.

3. thats the reason why we do not lable it as stable :p Reverting back is IMO just not a fix and no magic at all. That mainly the qcom display updates are the cause is now longer clear....reverting to jw is just we do not know it better let us do it like that and say we fixed it lol.

4. summary....of course we hope that google will fix it....but as well we are looking at it....I am sure (need to check it out) that the powerfull caf team has maybe a solution or cm which is working a lot with caf. When we lable it as stable you can blame us...till then we try to fix it. And I am sure we are not that far away. Just hard for a small team like us to do blob and repo work on all devices at the same time :D

so stay tuned and enjoy hopefully all other things we are doing on SlimBean and be sure we are constantly working on any issues we have ;)

just a general statement I wanted to do....I know that most of our users are already really happy with current state just I cannot read it anymore (not related to this thread!!! ;) ) especially on a lot other threads and g+ hehe

and last

thanks again for testing, reporting and all the support from you guys!!!! Next test build will follow for sure :D then lets go into the next round :)

cheers

kufi
[Nexus 4 Original Android Development] eng.stk:
IN fact beta 1.2 is working pretty nice, much less deadlocks that beta 1 ( I mostly have them when typing SMS).

One strange thing I noticied: when my phone is with screen facing down, my alarm didn't rang (everyday alarm at 8.00h, using quiet hours from 00.00h to 07.55h, flip, shake and volume buttons actions set to none).

Keep up the awesome work :good:
[Nexus 4 Original Android Development] shayne77:
OK I'm getting deadlocks all relating to the keyboard.

I was typing an SMS and the screen froze for about 10sec. I was still tapping the keyboard though and I could still feel haptic feedback... Sure enough, after the screen "unfroze" the word I kept typing was there.

I then went into catlog app straight away and saved a text file. I went in to edit that text file to remove I could see was way too old and not related and sure enough as I was deleting text (holding down the backspace) it deadlocked again and repeated above (I could still feel haptic feedback)

Running beta1.2 with Franco 174 unofficial jss.

Other than that, running great and honestly the first time I've experienced the deadlock problem

sent from my Slim'd Nex4
[Nexus 4 Original Android Development] molesarecoming:
i mean no disrespect but we all made a call to use an instable, experimental branch and that's what we got, instead of the stable, official release branch to which you do not wish to "revert just to say you fixed it". you know XDA and you know that less informed users will carry this high on a flag pole if you make this into a thing. JSS vs JWR. using the actual stable branch is a valid fix, google checks in clashing stuff in their experimental branches all the time, you know that. we just never ran into it so blindly before.

there is nothing in these 3 tiny kernel commits in JSS that warrants a broken experience, they're not faster or better. kernel developers can easily follow suit and some already built JWR from the start like franco, because he knew this was gonna happen.

i would have not written this if this didn't sound very strange to me, almost like as if some of it hinted at cataclysm and us.
[Nexus 4 Original Android Development] A2Eric:
Logcat attached.

That didn't work either. I even tried installing a different version of the Play store. The consistent error message I'm getting is 'Insufficient storage space" but I have plenty of space. Even Titanium backup is set to do backups at 2am and it couldn't finish, same error.

Also, I'm unable to install the latest binaries from the latest Superuser update. The only option it gives is the install by 'recovery' method which I choose, then it boots to recovery and flashes something on screen that I can't read then main recovery menu.
[Nexus 4 Original Android Development] shayne77:
I find this part amusing... Your saying it seems Google have borked this branch of Android OS for their own flagship phone? Lol all other devices don't have a problem. We should go back to 4.2.2? :)

sent from my Slim'd Nex4
[Nexus 4 Original Android Development] Lewythefly:
I actually thought that he was saying the opposite? Grammar wasn't great so hard to tell
[Nexus 4 Original Android Development] kufikugel:
lol yes sorry my english is not always the best

[MENTION=4491046]molesarecoming[/MENTION] just to be clear that was absolutly no offence against PA or your work. It was more offence about 1000000 emails I get every day from devs or user that jss15 is a big disaster for all devices....which is of course mainly caused of that xda community and the that a lot cannot differenciate why PA did that and other not and which devices are effected etc. You know that I really respect all the work PA is doing as well the other which are doing real development (like CM, AOKP

, Team EOS or SlimBean). And of course especially for PA it is a valid fix due that you officially support the nexus line. But we support over 30 devices and the only one now which suffers of this problem is mako. And I am really tired of answering emails that JSS is borked or all.

As I saw right now that PA is labled as stable...so reverting to jw is for mako a valid way...I agree. But we did not mark Slim for a reason as stable. First one is that we still have to do some base work and changes for our other devices which can effect mako as well. Second one is the deadlock issue. In the moment we go stable we have for sure a solution...and of course in worst case go back for mako to JW.

summary.....my statement was just to point out clear that the JSS branch is a problem only for mako (and was for flo) and that I am tired of answering every day the same. Not more and not less. Hope you can understand it a bit...and I think you are as well tired of this whole JSS **** the last 2 weeks

[MENTION=3889797]shayne77[/MENTION] to say it short....the official JW repo from google did not even boot on the new Nexus 7 2013.....that was the reason for google to do fast work and push JSS to have a working flo device. But the sad thing on that they forget to update qcom display and kernel stuff on mako properly. Thats at least the problem. So it is now our turn to fix it. Tbh I do not think that google will come out with a fix that fast. At least the official pushed repo from google for mako is working. So we can maybe hope that they will be pleased to the custom roms and push out a fix. Otherwise we all are on our own.

hope I cleared it a bit up and again [MENTION=4491046]molesarecoming[/MENTION] in no way this was offence against PA

cheers
[Nexus 4 Original Android Development] duramas:
Just want to say the beta has been nearly flawless for me. No deadlocks or anything like that, the closest is on rare occasions my phone reboots after updating an app, but that's happened to me in every version of Slimbean I've used. Even on my vibrant.

But I don't use the stock keyboard, I use Swype. Also, I delete all the gapps from the update zip that are available on the play store before flashing. Other than that I don't make changes such as kernel.

Great job guys, keep up the good work.

Also the JSS build supposedly has Wi-Fi fixes for notification delays when using some routers that JWR doesn't. Fixed the issue for me which I've had an issue with since I got the phone. Used to have to flash a configuration file that that set mcast and bcast to persist through sleep. A little hit to the battery but not a big deal.

Here's the Wi-Fi thread:

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

So thanks again slim team.
[Nexus 4 Original Android Development] nadiros:
Myself included, no dead locks at all and using an alternative keyboard and basic gapps pack.

Thanks a TON for all the hard work Slim dudes :thumbup:
[Nexus 4 Original Android Development] a g bell:
OK could someone possibly help me to get in touch with someone who knows what was fixed in alpha 3.1 to stop games like temple run 2 ?
[Nexus 4 Original Android Development] manpildo:
Hello guys. I'm new to Slim so don't hate me too much for what I think are questions with obvious answers, but in my defence, I couldn't find an answer after skimming through search.

Anyway, my questions is: Is it a known issue at this stage that the phone's screen doesn't turn back on after ending a call? It seems that the proximity sensor doesn't react for one reason or another. Oh, and what is this Beta 1.2 everybody keeps talking about? The OP refers only to Beta 1 as far as I can tell.

And kudos for making Touch Control work when it's not supposed to work on 4.3 at all. That's some piece of magic by you guys, the main reason why I migrated :)