yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] sordna:
I would only let titanium restore non-system apps & data after flashing a completely different ROM.

Otherwise, it's almost the same as dirty flashing in the first place, which can cause problems between different ROMs, right?
[Nexus 4 Original Android Development] wildestpixel:
very correct - never use titanium for system apps unless you have specific needs.
[Nexus 4 Original Android Development] CoolApps:
The only good sides of Android 4.3 is major performance improvements and the updated apps.

The major disappointment is SELinux, let's hope Google removes it. :s
[Nexus 4 Original Android Development] franciscofranco:
Forget about that AOSP rom, its old.

What is the problem with SELinux?
[Nexus 4 Original Android Development] CoolApps:
The problem is that it is causing permission issues and such which makes it harder to do stuff and also can cause problems with other stuff.
[Nexus 4 Original Android Development] wildestpixel:
Go on - elaborate on "stuff" ;)
[Nexus 4 Original Android Development] Andre_Vitto:
too much stuff?
[Nexus 4 Original Android Development] wildestpixel:
likely all the stuff cleared up by Super SU 1.51 and greater.
[Nexus 4 Original Android Development] Funnnny:
Those are problems with nosuid mount, not SELinux. SELinux in Android is very passive, it's not like the SELinux in RHEL we hate.

So, next time don't spread false information based on something you don't even know.
[Nexus 4 Original Android Development] franciscofranco:
I don't want to crash the party, but this is from Chainfire:

:)
[Nexus 4 Original Android Development] Funnnny:
Well, it isn't the big reason su went daemon, but it's the initial reason. After nosuid breaks current root process, they stop and look back, improvised the situation. And the new daemon worked better in many ways, like when two app nount/remount /system

Nosuid is indeed why we had 1.51,but that doesn't mean if we can remove nosuid, we can remove the daemon.
[Nexus 4 Original Android Development] nexusmaniac:
Ok, I can't wait till 4.4 hits, then I'll stay with the stock ROM and not bother with cm or pa or any other ROM, they both just have to many features that I don't need :/
[Nexus 4 Original Android Development] wildestpixel:
For the average user and even more su as dameon / proxy fixed everything that "they" needed. If you are working on something like cracking MobileIron as a measure of testing security on say a local government rollout then things like Samsung SAFE and 4.3's SELinux whilst two very different things are whilst great hurdles, great hurdles sic.

Implementing a nosuid workaround when we have a fully functional dameon is not necessary unless you want to get at the OS encrypted data in an unconventional manner given that Chainfire has done his thing.
[Nexus 4 Original Android Development] Funnnny:
What does it have anything to do with SELinux like you said several post ago?
[Nexus 4 Original Android Development] wildestpixel:
Nothing - this is about what was done to work around getting over all of things introduced by 4.3.

I didn't intend for a shooting match here, just stating that for average user there is no 4.3 permissions problem. If we can end it here before we change the topic to looking at various improvements in mobile linux security!

Thanks.
[Nexus 4 Original Android Development] Pipusz:
Sorry to interrupt, but have you developed ROMs for any device? Your name looks familiar.
[Nexus 4 Original Android Development] CoolApps:
The point is that SELinux is making stuff a bit more harder (which is the whole point :p) so you have to do extra stuff like for example you need to enter a chown (change owner) command so Titanium Backup restores and changing the path to an other one (which got fixed since PA 3.99.1 RC2).
[Nexus 4 Original Android Development] wildestpixel:
Yes I had Pixelrom on Nexus S last year until I moved to Galaxy note and had nightmares with bad EMMC and kernels / wipe.

Elaborate on that I had 2 bricks on Note which halted my public dev work. Lots went on between xda members and Samsung staff even in face to face meetings on that EMMC issue.
[Nexus 4 Original Android Development] blankit:
Is deep sleep similar to what my laptop does when I put it in sleep mode?
[Nexus 4 Original Android Development] Pipusz:
Deep sleep is when the screen is off and you don't interact with it.
[Nexus 4 Original Android Development] sir_fz:
How can I revert to the stable app from the dev version? I already unsubscribed as a tester but play is still installing project pringles
[Nexus 4 Original Android Development] franciscofranco:
Nope, its different.

You gotta wait, or reboot.
[Nexus 4 Original Android Development] bongostl:
Which kernel do I use for a jls rom?
[Nexus 4 Original Android Development] Bill Gamble:
JSS
[Nexus 4 Original Android Development] bongostl:
Thanks! Do you know if this is true for carbon, too?
[Nexus 4 Original Android Development] Mercado_Negro:
No, you need a JWR kernel for Carbon.
[Nexus 4 Original Android Development] David9519:
Nice battery life with 4 active cores on touch

4 hours of SoT with 2 hours playing candy crush saga.

Candy crush saga 37%

Display 29%

---------- Post added at 09:43 PM ---------- Previous post was at 09:28 PM ----------

Nice battery life with 4 active cores on touch

4 hours of SoT with 2 hours playing candy crush saga.

Candy crush saga 37%

Display 29%

---------- Post added at 09:44 PM ---------- Previous post was at 09:43 PM ----------

Nice battery life with 4 active cores on touch

4 hours of SoT with 2 hours playing candy crush saga.

Candy crush saga 37%

Display 29%

---------- Post added at 09:45 PM ---------- Previous post was at 09:44 PM ----------

Nice battery life with 4 active cores on touch

4 hours of SoT with 2 hours playing candy crush saga.

Candy crush saga 37%

Display 29%
[Nexus 4 Original Android Development] galza:
installed original kernel...black screen and rom didnt boot up.. installed jss kernel boot up with inverted colors how to fix?

cheers

---------- Post added at 08:51 PM ---------- Previous post was at 08:50 PM ----------

tried to install jss kernel got inverted colors..how to fix it please?

---------- Post added at 08:52 PM ---------- Previous post was at 08:51 PM ----------

tried to install jss kernel got inverted colors..how to fix it please?

---------- Post added at 08:53 PM ---------- Previous post was at 08:52 PM ----------

tried to install jss kernel got inverted colors..how to fix it please?

---------- Post added at 08:54 PM ---------- Previous post was at 08:53 PM ----------

tried to install jss kernel got inverted colors..how to fix it please?
[Nexus 4 Original Android Development] fozzie:
Ditch CM for a decent ROM. It doesn't support third party kernels anymore.

(Or for a temporary solution, and mentioned loads of times in this thread, search for colorfix.zip in this thread.)
[Nexus 4 Original Android Development] galza:
tried to install jss kernel got inverted colors..how to fix it please?
[Nexus 4 Original Android Development] fozzie:
You already asked that above.
[Nexus 4 Original Android Development] galza:
ok i found color fix now its fine...im using vanir AOSP and its really good dont think ill ditch it soon:good:

---------- Post added at 09:05 PM ---------- Previous post was at 08:59 PM ----------

yeah sorry my browser got stucked and i thought that the reply was not send

:good: thanks mate
[Nexus 4 Original Android Development] sysak:
1026MHz and yes quite heavily. It seems like with r188 the music is stuttering more rarely than it used to but still happens once in a while.
[Nexus 4 Original Android Development] SneakyGuyDavid:
Here's A Direct Link for the Color Fix !

Link:http://www.mediafire.com/download/g82or3inoagqi2a/color_fix.zip

people seemed to have trouble finding it, i sure did, i had to go all the way to the AOKP page and jump through loops to find this so i figured i would upload it again but on mediafire, by the way it works great on CM 10.2 just remember to flash JSS tagged.
[Nexus 4 Original Android Development] Raphael17:
How do I get rid of this wake lock has it been solved yet?
[Nexus 4 Original Android Development] Toronadian:
Apologies if this has been asked, but will you continue pushing out new kernels for the N4 once the N5 comes out?

Had it since January and love using it and I usually don't switch phones until 2-3 years...but if the N5 does come out pretty cheap, gotta say I'm tempted.
[Nexus 4 Original Android Development] ziddey:
power manager wakelock is the result of userspace activity

whatever it is is requiring data and resulting in hsic host wakelock.

nothing to do with the kernel.
[Nexus 4 Original Android Development] franciscofranco:
How to solve the msm_hsic wakelock -> take out your sim card.

How to solve the PowerManager wakelock thingy -> don't use any apps that wakelock your device.

I'll still push Kernels for the N4, but in slower rate.
[Nexus 4 Original Android Development] CDeviant:
Exactly when do I flash the color fix? I've tried searching, but all I can find are links to the colorfix.zip.

I'm going to update to the latest pac nightly.

Do I flash the fix before I flash the new ROM, or after?

Or do I flash it after gapps and before the kernel. Or after the kernel?

I've been using r184 and pac 10/06..
[Nexus 4 Original Android Development] arlenwoot:
Doesn't really matter as long as you flash colorfix after you flash the rom because its replacing a file. I usually flash rom gapps colorfix kernel.
[Nexus 4 Original Android Development] peikojose:
[MENTION=3292224]franciscofranco[/MENTION] I sent you an email ! Best regards.
[Nexus 4 Original Android Development] santeana:
Congrats [MENTION=3292224]franciscofranco[/MENTION] on 5000 pages for the Nexus 4 FK thread!!
[Nexus 4 Original Android Development] franciscofranco:
Wow!
[Nexus 4 Original Android Development] jawz101:
FKU Per App Power Mode has always seemed finnicky. The 2nd tab seems redundant to the main frequencies/voltage menu screen. The only reason I use the default system power mode tab is to throw some settings in it so I can finish up setting up my per app 'power' profiles without them reverting to my more conservative default system power setting because, in the time it takes to set an app up once, it reverts back to the system defaults by the time you want to apply it to another app.

Also, it does not save every setting- ex: input touch boost seems to get left out 9 out of 10 times.

Also, if adding another per-app power mode to an additional app don't trust the values displayed. it'll display one value for something but when you click to adjust it it will be on another value previously used.

Can't you just get rid of all of this and just have the regular frequency/voltage settings, and the per-app pwr mode screen would be a process of

1) create a power profile

2) associate apps with a profile

As it stands there is a disconnect between the 1st and 2nd tab. I really don't know what the 2nd tab is for except to confuse me since I set my default freq/governor settings on the frequency/voltage menu screen.
[Nexus 4 Original Android Development] franciscofranco:
All true, all agreed :)
[Nexus 4 Original Android Development] jmudrick:
Was so happy with battery life on r183 I gave subsequent releases a pass but r191 is so friggin responsive. Haven't had an all wifi session to compare with r183 but almost 5hr SOT in a mixed wifi and 3G session looks promising. Good WORK Franco. No issues thus far. Cataclysm ROM.
[Nexus 4 Original Android Development] Dave778:
I just noticed that compared to 188+189 that 191 is a battery hog!

I will admit its so much more responsive though.

Franco ? :good:
[Nexus 4 Original Android Development] 1ceb0x:
You just flashed it. Give it a few days or so to settle down.
[Nexus 4 Original Android Development] Dave778:
Really? kernels need time to settle ?

Never heard of that 1... :eek:
[Nexus 4 Original Android Development] 1ceb0x:
Not the kernel. But your phone does.
[Nexus 4 Original Android Development] sordna:
50,000 posts!

Congrats on 50,000 posts too!
[Nexus 4 Original Android Development] Dave778:
Just saying that on 188 I would get home after a 8 hour day at work with heavy heavy voice, txt & data usage & I would have 40% battery left.

W 191 I've been at work for 4 hours & only used very light voice usage & I'm already at 25% battery remaining
[Nexus 4 Original Android Development] 1ceb0x:
How much time did you had 188 installed? 2-3 days? You can't say the kernel has bad battery life after 1 day of use. Give it a few charge cycles.
[Nexus 4 Original Android Development] Andre_Vitto:
you sure you did not install any apps in between your casual tests that hogs battery? because 191 is giving me nearly the same battery signature as the previous ones..
[Nexus 4 Original Android Development] Dave778:
no I havent installed any apps. Just updated from 188 to 191 & BOOM! no battery.

I had 188 installed since it came out
[Nexus 4 Original Android Development] Mercado_Negro:
Why does it need a few charge cycles? Please explain this to me because I really want to understand why something based on 0's and 1's will behave differently after a few days.
[Nexus 4 Original Android Development] Luigiesin:
Make sure you cleaned FK data as few times...

My phone takes one cycle to get his shht together.. After that it's all buttery again...
[Nexus 4 Original Android Development] Dave778:
I cleared app data once, I'll try it again & see if its better after a couple of cycles

thanks
[Nexus 4 Original Android Development] jimbohurt:
You need to wait a few days in order to rule out any other variables that could be effecting your phone and make it so there is only one variable (that being the new kernel)

I have days where my battery sucks but I hadn't just flashed anything new, but it was because I was out of a lot of service or because I was using location settings, ect. So what if i had one of those crappy battery days but I had just flashed a new kernel? Well then I would blame the kernel but if I waited a few days I would see that it was indeed not the kernel, but another reason.

So if you wait a few days you can get more of the big picture with a kernel and not just one small view of it when there are many other possible variables effecting your phone.
[Nexus 4 Original Android Development] Mercado_Negro:
Now that makes sense. I thought it was something related to that "let it settle, it's alive" myth which I've always seen like "ok, use your phone for a while and compare later" but people like to make it sound like the kernel needs to adapt itself :D
[Nexus 4 Original Android Development] LibiSC:
The three laws man... The three laws ;)

Enviado desde mi Nexus 4 usando Tapatalk
[Nexus 4 Original Android Development] jimbohurt:
Haha yeah totally, I think I've seen posts like that too. Pretty silly. Now that I think of it, he may have meant that (the guy you quoted in the first place) but whatever :P
[Nexus 4 Original Android Development] Mercado_Negro:
Born (compile), live (flash) and die (post battery stats pics)? :p
[Nexus 4 Original Android Development] LibiSC:
Was a reference to I, robot... I guess nobody really liked that one lol

Enviado desde mi Nexus 4 usando Tapatalk
[Nexus 4 Original Android Development] arief347:
Compile (born) *expecting good result* flash (teenager) *excitement* got error crash (real life) :D *sad,confuse,etc*
[Nexus 4 Original Android Development] Mercado_Negro:
Yeah, that's the first thing that came to my mind but I took the chance to make a bad joke :p

I love that movie, btw.

1. Can't hurt human beings

2. Obey the first law

3. Protect human beings

:D

---------- Post added at 01:25 AM ---------- Previous post was at 01:19 AM ----------

Yeah, the screen tearing pain caused by an evil JSS/JWR Kernel Conspiracy :p
[Nexus 4 Original Android Development] fozzie:
http://xdaforums.com/showpost.php?p=41029765
[Nexus 4 Original Android Development] psyren:
Does anyone have any recommendations on a non-retarded ROM (non-CAF) that I can use this kernel with?
[Nexus 4 Original Android Development] Pipusz:
Stock 4.3, Purity, PA, Rasbean, etc.
[Nexus 4 Original Android Development] psyren:
I'll investigate.

I should've been a bit more specific with my post: I'd like a ROM that has a dark toggle, speed optimisations, general UI customisations... basically, the feature set of most custom ROMs without the CAF crap.
[Nexus 4 Original Android Development] nadavar:
I'm using Carbon with it and it works really great. It has all the features you wanted. Previously I used PA, also fits your bill (without dark toggle), but carbon is more feature packed (except hybrid).

Both go with the JWR version of the kernel
[Nexus 4 Original Android Development] uglavnom_bezopasni:
deleted
[Nexus 4 Original Android Development] Andre_Vitto:
Carbon and purity are the most feature filled rom these days thats stable..PAC too has features but its too unstable..
[Nexus 4 Original Android Development] Luigiesin:
Im on Cataclysm and after trying almost all of them this one is problem free! No nighlies every two days.. Just works! And it brings a few cool features without bloating your system.. Pretty much stock and super light.

Franco friendly ;)
[Nexus 4 Original Android Development] ctfrommn:
Ok, but it doesnt boot or stay at 384/1513. Is that by design? It is booting at stock freqs of 1026/1242. Or did I do something wrong? I am using a rooted stock Rom for this.
[Nexus 4 Original Android Development] _Opiate_:
Awesome! Will be flashing this to my nexus 4 soon. The fact the nexus 4 ramps up so much upon touch might be another reason it can't match Optimus G battery life with same hardware.
[Nexus 4 Original Android Development] franciscofranco:
Means I comply with the GPL. Email me about the app.

It boots with max 1513 and min 384. If that doesnt happen with you then you have something wrong setting up your frequencies.
[Nexus 4 Original Android Development] JNewms:
Can this be flashed on my phone through my recovery? I tried flashing the boot image using my n4 toolkit but it went back to stock kernel after a reboot
[Nexus 4 Original Android Development] franciscofranco:
Because the toolkit used probably fastboot boot boot.img. Just go to the bootloader and type the command in the OP. CWM flashable zips will come in its own time.
[Nexus 4 Original Android Development] javacody:
Franco, you're patience with newbs who clearly haven't read your prior posts is pretty amazing!
[Nexus 4 Original Android Development] JNewms:
I've read everything. But yes I'm a noob. This is my first nexus so a lot of this is new to me. I'm not sure how to type things into the boot loader. Can anyone point me in the direction of something that would explain it to me?
[Nexus 4 Original Android Development] Ranguvar:
This really isn't the place for that discussion.

Ask in the Q&A forums, but Googling fastboot commands will get you far.
[Nexus 4 Original Android Development] elliot.newnham:
You can try the stickies.. Massive guides are out there and details with the differrence between ADB, Fastboot, bootloader, kernel, Rom etc...
[Nexus 4 Original Android Development] ragnarokx:
internet <------
[Nexus 4 Original Android Development] andrewjrr:
Mine has the same problem.. didn't boot with it. Any idea of how to fix this? Clear or wipe something?
[Nexus 4 Original Android Development] franciscofranco:
Dunno, mine boots at stock 384/1513 just fine.
[Nexus 4 Original Android Development] javacody:
Mine is working fine, too.
[Nexus 4 Original Android Development] richteralan:
Does that mean you got your N4?
[Nexus 4 Original Android Development] andrewjrr:
Yeah it seems like I can't get any changes to stick. I thought it was just my one app so I downloaded another and same problem, they go back to default after restarting app
[Nexus 4 Original Android Development] franciscofranco:
No, I'm using one that Andy Rubin got for us few days ago. I dunno if they going to give it to me or its just borrowed.

Can you be more specific? What do you mean by changes to stick? Its pretty simple, just remove any frequencies set on boot function that you are using in any app or some rom built in menu, reboot the device and it will be using 384 min and 1513 max all the time. If you try to change frequencies again it will revert to stock behaviour until you reboot again. Maybe I'm speaking Chinese here, but thats how it works so far, it works for me, for minooch, and for a large number of people.
[Nexus 4 Original Android Development] andrewjrr:
You're right, all it took was a reboot.. thanks
[Nexus 4 Original Android Development] Serious_Beans:
You working at Google or something now? O_o
[Nexus 4 Original Android Development] leets4uc3:
Not sure how this kernel thing works but is it hard to make beta7 usable with cm? Im really liking jellybro. If not Ima Gunna switch to a different ROM tonight.
[Nexus 4 Original Android Development] JNewms:
Well guys thanks for the motivation. Finally learned how to fastboot this kernel. Now that i have that accomplished I'll finally get to try out this legendary kernel.
[Nexus 4 Original Android Development] Taxiback:
Can you not make those images a little bigger, I'm struggling to see them. :)
[Nexus 4 Original Android Development] sidhaarthm:
Sorry - just copy/pasted direct image links from Imageshack - and opted for no resizing over there.. :-/ Any thoughts on the battery calibration issue?
[Nexus 4 Original Android Development] jarjar124:
bigger? they're already big!!
[Nexus 4 Original Android Development] kenkiller:
Sarcasm is obviously not apparent to you. :D
[Nexus 4 Original Android Development] springy:
It has a case on it.. And I feel a bit stupid now as I worked it out and it isn't the Kernel.. :) NFC - Sorry guys for wasting your time... :(
[Nexus 4 Original Android Development] ssauger:
Its the sound from NFC, maybe the phone read something inside the letter (any kind of nfc tag). If you don't use nfc u can disable it in the settings.
[Nexus 4 Original Android Development] simondadiamond:
3 and a half days!!! Holy crap! :D lol, although those results are quite biased, 1h VS 4h of screen time, im quite impressed for stock...
[Nexus 4 Original Android Development] fetto666:
r28 is great, best battery i have ever had on this phone.
[Nexus 4 Original Android Development] Nebucatnetzer:
Battery calibration is a myth.

Your 10% drop comes from flashing the kernel. It seems that the recovery doesn't update the batterystats that's why it goes down in a straight line.
[Nexus 4 Original Android Development] Taxiback:
Even though your phone does it automatically after a full charge. ;)
[Nexus 4 Original Android Development] Nebucatnetzer:
That's just wiping the batterystats file. It doesn't affect the charge of the battery.
[Nexus 4 Original Android Development] ben_pyett:
don't comment/complain/joke about the size and then quote them, we knew the ones you were referring to as we all saw them the first time!

I've also found that a reboot/restart on this device can be quite costly, often consuming >5% of battery. But let's not go off topic and talk about bleeding battery calibration, not again please..:crying:
[Nexus 4 Original Android Development] mobilehavoc:
Maybe because while booting its probably pegged all 4 cores at full.
[Nexus 4 Original Android Development] ObihoernchenDE:
Have used 28 for about 10h on 3g now.

No data drops! Everything is working fine.

With 24-27 I had about 1 data drop every hour.
[Nexus 4 Original Android Development] luckylui:
I use stock myself :)

Using AOKP Mr1. I rarely use my phone so this is how i roll. 8)
[Nexus 4 Original Android Development] dannyyung:
Tried r27/r28, both have data connection issues.

Go back to r23, data/internet working fine again.
[Nexus 4 Original Android Development] zaki67:
I am on r28 and also have data problems on stock rooted.
[Nexus 4 Original Android Development] eRajesh:
No data issues on r28.
[Nexus 4 Original Android Development] Taxiback:
What exactly are these data problems?

I'm on stock 4.2.1 and r28 and it's fine.
[Nexus 4 Original Android Development] mosd:
Apps don't load data, takes like 10 seconds for the app to start to download info. Even thought it's full signal