yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] asprofridis:
let me ask something cause I am new with 4.3 . I ve just installed latest stable slimrom 4.3 and after downloaling latest franko I have stuttering issues. Propably I have to install other version of franko kernel but my question is: which version is downloaded by default? jwr or jss? And How I can set up franko auto updater so as to recognise which version is needed?
[Nexus 4 Original Android Development] Arstoien:
It does that automatically now. You must have the correct version.
[Nexus 4 Original Android Development] :
Look at the title of Slim rom it clearly says JWR kernel!

It might not boot cause there's a ramdisk issue still to be sorted
[Nexus 4 Original Android Development] farris:
How can you guys get a SOT of 4-5 hours? I only have 2-3 hours, don't know how to get it higher. I lose 30-40% per hour. Maybe I'm going to try 4.2 ROM again because I had a much better SOT before the 4.3 update.

Before the N4 I had a Desire Z, and there was the culprit of having the wrong radio (US baseband and I live in Europe). Does the N4 have the same? Different radios for different countries? Because I only use my Nexus 4 on HSDPA, and not on wifi, so maybe I can get the SOT higher with a better radio (battery friendly, haha).

The only wakelock I have is 'mediaserver' with AudioOut_2 for about an hour a day. When I use the command 'lsof | grep mediaserv' I see a lot of lines with files in use by the mediaserver. Is there any log I can check what happens? In logcat there isn't anything to see unfortunately.
[Nexus 4 Original Android Development] orangestrawberry:
faris - What ROM are you on?

---------- Post added at 01:03 PM ---------- Previous post was at 01:02 PM ----------

What ROM are you on?

---------- Post added at 01:04 PM ---------- Previous post was at 01:03 PM ----------

What ROM are you on?
[Nexus 4 Original Android Development] farris:
First stock 4.3, but because of the bad SOT I switched to Cataclysm + franco, however, still this 'problem'. I need to take my charger with me everywhere I go :P
[Nexus 4 Original Android Development] orangestrawberry:
I'm on Purity with Franco v183 and its simply the best combo I've ever had. The battery drain is fantastic.
[Nexus 4 Original Android Development] pkelly517:
I'm glad they are enabled, too.

I've already found a 2 hour kernel wakelock that I'd never seen before. And a quick Google search knocked it down to minutes.

Thanks Franco.

---------- Post added at 07:17 AM ---------- Previous post was at 07:16 AM ----------

And then ask questions in the BBS thread.

Those folks really know their wakelocks.
[Nexus 4 Original Android Development] MuertoKo:
I achieved my record yesterday, 6.5h Sot an almost 18h On... Which is completely insane! I usually get around 2-3 h Sot and 15h On...

How did it happen?

I was at home, all day. Only difference! Most drain comes from net switching and so, try easy, plane mode and use your phone xD

Enviado desde mi Nexus 4 usando Tapatalk
[Nexus 4 Original Android Development] pkelly517:
And then ask your questions in the BBS thread. Those guys know their stuff.
[Nexus 4 Original Android Development] zephiK:
For those who prefers Chrome over AOSP browser or whatever, http://www.androidpolice.com/2013/0...ce-reboots-but-a-fix-is-already-in-the-works/ just dont do that and it wont reboot ;)
[Nexus 4 Original Android Development] limeaide:
Those of you that was having the su toast notification and could not figure it out. Try this, make a copy of any data you want to keep in the franco kernel updater folder. Now Goto the app find the option to clear app data when flashing automaticly, make sure itis checked now go and restore the most recent kernel you have. Once the phone reboots using a file explorer again navigate to the franco folder and delete everything including the folder. It will be recreated on the next boot dont worry. You should have also created a backup if you wanted.

Now reboot the phone and once it boots up wait about fifteen minutes. Then use the phone like you normally would but do not change the franco settings yet. Use the phone like this for a while and see if that toast pops up again. If not that means you had a per app power mode and it was not playing nice with your phone. Now copy the contents from the backup you made but do not copy the stuff from the folder inside franco folder named power_modes.

If this did not solve your issue then you need to run a log cat and post it for francisco.

I have been a diehard franco kernel user since Feb. I did test other kernels but ultimately came back. But since about a week or so ago Ive had horrible battery life. It started on Cataclysm so I tried Cyankang. For a day or so battery was nice. But then bam I was lucky to make it from 8am to 5 pm before needing to charge. Nothing changed other then I updated the kernel and app updates that "shouldn't" affect battery. Checking the battery stats it will show android OS as the main source of battery usage. I know that is userspace and not kernel. But I could never figure out what it was. I flashed a nightly build of Cyankang that uses hells-core kernel and forgot to flash franco after I booted up. The next day my phone lasted me all day and I had a lot of battery left at midnight when I went to sleep. I ran that kernel for a couple days. Never seen android OS as the main user of battery until I flashed 182 and then 183. No change in anything no app updates or anything just changed kernels. I completely charged the phone each time AFTER flashing the kernel so I know it wasnt a misreading of battery.

I cant figure this out. I know it should not be the kernel but I know for a fact I changed nothing other than kernels. I also used the phone a lot more on hells-core kernel then franco so theoretically it should have used more battery and not gave me better battery, right?
[Nexus 4 Original Android Development] trek85002010:
Is the 183 compatible with T(ouch)C(ontrol)?. I have this kernel, and this message:

"I was unable to load modules,sorry...."

I'm root
[Nexus 4 Original Android Development] yethz:
That question been asked already million times.

Ask it on TC thread (or the developer)...

________________________

Device: Google Nexus 4 (LG-E960)

ROM: SlimBean 4.3 Beta Build 5

Kernel: Slim-4.3-JWR_RC-1.0+

Recovery: PhilZ Touch (CWM) Recovery v5.11.2
[Nexus 4 Original Android Development] trek85002010:
I think the problem is due to my ROM, because with the stock kernel TC thread also continues out the same message.
[Nexus 4 Original Android Development] scream4cheese:
Yeah, you have to search it through the threads. I assume it doesn't get added unless it's an official release.
[Nexus 4 Original Android Development] albundy2010:
I get around 3500 with a max clock of 1026ghz. As somebody else stated you sure it isn't underclocked?
[Nexus 4 Original Android Development] scream4cheese:
I dislike how every device behaves differently when the same kernel is applied to the same device as everybody else's.

I'm currently on r26. My cell reception has been very low. Back when I had r23, reception was normal. I had 3-4 bars and even full bars when I'm at home in my room. Now I get none to 1 bar.

I guess it has some sort of reverse effect. For people with signal issues' r26 seems to fix their problem and for those who have decent signal will get poor signal (?).

I left my phone on overnight (12hrs +) and I only lost 5 percent of battery power. Wakelock hsic was on for 15 minutes or so and WiFi was on all night.

I hope the next official build or test build will fix my signal issue.
[Nexus 4 Original Android Development] Hrithan2020:
You had tried r24 or r25? People who were having problems with r24,r25 may likely have issues with r26? [Although some are not having, as franco has cherry picked only a few patches/fixes from r24-test and r25.
[Nexus 4 Original Android Development] jak3z:
Everything else is stock.
[Nexus 4 Original Android Development] ragnarokx:
Obviously you "put stock" into benchmarks or you wouldn't care - you just say you don't to avoid flaming, but you still are trying to get people to tell you how to improve your benchmark score. That's like saying you don't believe in black magic, but you are trying to find out why one Witch Doctor says Franco's kernel has worse joo-joo than Motley's kernel.

Sent from my Nexus 4
[Nexus 4 Original Android Development] capcanuck:
I've had this phone since November, haven't ran a single benchmark... Probably never will
[Nexus 4 Original Android Development] franciscofranco:
I know some patches are wrecking everything up. I just merged Ricardo's latest commit which reverts a bunch of those patches - if he says its fixed now I'll take his word for it, he's one of the best Android developers in the world.
[Nexus 4 Original Android Development] franciscofranco:
Ok r27 is out:

r27:

This should be the latest version before the first Milestone labeled release is out

* This release is based on test releases r24-test, r25-test and r26-test which include:

- Interactive governor fixes from Google

- Improvements to the Hotplug driver for bettery battery without sacrificing performance

- Make the thermal control a little more aggressive to prevent heat

- Qualcomm patches which include improvements to the msm_hsic_wakelock etc

Everyone should update to this one, has the change from CM's kernel to fix the instability on the connectivities.
[Nexus 4 Original Android Development] schizophrenia:
lucky

i was just about to flash r26. haaa

thanks for the great work man
[Nexus 4 Original Android Development] irishrally:
[informed] Opinions on the Seeder app?
[Nexus 4 Original Android Development] richteralan:
*Waits for the first milestone release*

:good:

---------- Post added at 03:11 PM ---------- Previous post was at 03:10 PM ----------

Frankly, sad to see people trying to make a few bucks on hype.

And even sadder to see people are buying into the hype.
[Nexus 4 Original Android Development] Treatcon:
Thius is Franco kernel thread, not placebo thread.
[Nexus 4 Original Android Development] drawde40599:
now were going see a bunch of noobs buying this app , then come here " your kernel causing this Franco" never mention they have it installed . personally i haven't had a lag stock or custom kernel since my captivate a billion years ago
[Nexus 4 Original Android Development] imsuperjp:
ok i'll admit I am a noob and I have tried to read the past 100 pages and ddint see an answer to this. I've installed the kernel and it works great for me. What all does the Franco App do and would it be of use to a noob?
[Nexus 4 Original Android Development] ReD_AvEnGeR:
dont know what some people here are testing. Do they only check that the menu animation is smooth or something ?
[Nexus 4 Original Android Development] Hrithan2020:
Well, franco kernel is an excellent kernel which can be used as is and doesn't need any changes in settings to work well, as you have pointed out.

Apart from the color modification [required if you genuinely feel the color calibration of the display is poor] , I don't think there is anything you need to play with. But the best thing is that it enables you to automatically flash a new kernel when it comes, so you don't need to check the thread repeatedly for any updates ;)
[Nexus 4 Original Android Development] stankyou:
Well according to the app description...

Nexus 4:

(most options depend on the kernel features, if X or Y feature isn't present in the kernel the interface in the app won't show up)

* franco.Kernel's auto-flash

* Detailed franco.Kernel changelogs

* Kernels backup/restore on the go interface

* CPU clocks interface

* Governor Control

* Color Control

* Power modes

* All the kernel settings (disable logging, changing IO scheduler, TCP Congestion algorithm etc)

* CPU's online/offline live feed

* Lots more
[Nexus 4 Original Android Development] Marreboy:
Short answer is yes even a noob will have benefits from Franco's app.

Through the app you will have access to backup / restore of kernel, frequency settings, color settings and much more. Well worth the money.

Tapatalked from my Nexus 7
[Nexus 4 Original Android Development] imsuperjp:
Thanks. i dont know what most of that means but I think i will just purchase just to support his work.
[Nexus 4 Original Android Development] yethz:
Off topic already, but try to load other modules, like;

Franco Nightly #178 module in TC..

Sorry for off topic. Just trying to help.

________________________

Device: Google Nexus 4 (LG-E960)

ROM: SlimBean 4.3 Beta Build 5

Kernel: Slim-4.3-JWR_RC-1.0+

Recovery: PhilZ Touch (CWM) Recovery v5.11.2
[Nexus 4 Original Android Development] ranasrule:
is there any fix for the storage issues with franco183 on PA 3.99.1-RC1 ?
[Nexus 4 Original Android Development] snacs:
Me too. But now I moved to AK kernel and everything working normally. I use JSS version :confused:
[Nexus 4 Original Android Development] Bill Gamble:
Apparently, the Linaro version of Franco r183 doesn't have this issue.
[Nexus 4 Original Android Development] ciano865:
Chrome BETA

Google has reproduced issue of Chrome BETA/reboots and working on fix it, so is not a kernel/custom ROM problem:

http://www.androidpolice.com/2013/0...ce-reboots-but-a-fix-is-already-in-the-works/
[Nexus 4 Original Android Development] fozzie:
That was already posted 10 posts ago. Please read the thread before posting duplicate information. Thanks.
[Nexus 4 Original Android Development] Mercado_Negro:
The amount of policemen, bodyguards and zealots in this thread is so big that we should really consider building a security agency. The "hollier than thou" crowd is also really nice.
[Nexus 4 Original Android Development] jak3z:
Try calling the internet police and see what happens.
[Nexus 4 Original Android Development] bruce7373:
Lol. Actually I'm starting to find it all somewhat entertaining.
[Nexus 4 Original Android Development] drawde40599:
Use wifi , shut off sync, dim your screen so u can't c it, no Google now, . Turn down your max freq, use 2g, all or combo of that is what there doing . i get 2.5-4 with everything on, i shut everything off one day baby sit the phone like crazy and got 7 hours , . But who wants to do that :P
[Nexus 4 Original Android Development] mr xombie:
Nope, tried it.

Still got the force close on storage settings.
[Nexus 4 Original Android Development] NPuter:
You have to use the fixed version here: http://xdaforums.com/showpost.php?p=45592370&postcount=952
[Nexus 4 Original Android Development] red0307:
1700 MHz removed?

is the 1700 MHz CPU frequency removed by Franco in r183? limit is 1512 MHz when selecting frequency. tried searching for answer in the thread.

EDIT: tried searching. google gived me no OC yet in 4.3 is it true?
[Nexus 4 Original Android Development] mr xombie:
It works!.

Thx man.. :D
[Nexus 4 Original Android Development] zephiK:
No over clock on Franco 4.3 series. Use another kernel if you desire over clock. Overclock not even needed, this kernel is too fast
[Nexus 4 Original Android Development] franciscofranco:
This - exactly. Thanks for posting that! A userspace app giving random hard reboots means their JNI (java native interface) are probably pretty fúcked. GG Google.
[Nexus 4 Original Android Development] franciscofranco:
http://productforums.google.com/forum/#!topic/nexus/coHv92FP5RA

Android OS high percentage is a recurring issue since 4.3. I'm pretty sure its caused by Google Services.

No, I asked PA to fix their shít and they are going to do so.
[Nexus 4 Original Android Development] drawde40599:
O= No such thing as to fast, crank it up!! :P
[Nexus 4 Original Android Development] khanhtrinh:
I'm currenty on r182. Do I have to clear FKU data before flashing r183?. In which case should we do it before flashing new releases?

Nexus 4 | Cataclysm | Franco | Viper4Android
[Nexus 4 Original Android Development] fozzie:
Some people will say you should, others not.

I've always cleared the app's data before flashing a new kernel & never had any problems when updating. It also ensures you're running with the kernel defaults (in case they've changed). It only takes me 30 secs to load my settings.
[Nexus 4 Original Android Development] frozst:
Ok, I am not going to be rude with you guys as it's obvious that you were misinforming, next time don't reply if you are not sure.

[MENTION=2819760]jak3z[/MENTION] Ditto. Think twice before post. Thanks.

Thanks [MENTION=3292224]franciscofranco[/MENTION] . I just wiped the app data and now is behaving as usual: it is only requesting SU permissions when I open the app, before that it was requesting them like 5 times per minute without any apparently reason, even in the background. I don't have the logcat as I fixed this yesterday, but I hope that someone else can send it to you as it is quite usual.

Seems that a lot of people is experiencing the same after updating the app, and I think that a lot of people here think that this is a normal behavior...

I'm not using the per app settings, only color correction, undervoltage and headset gain. However, I am not sure if this problem appeared after updating the app or the kernel as both happened nearly at the same time...

Thanks!
[Nexus 4 Original Android Development] jsmasterx:
Artifacts on screen while swiping

You can disable H/W Overlays in the developpers settings. Found that it solved that infamous issue in r183.
[Nexus 4 Original Android Development] whitedragonz83:
Infamous r183 issue, or Infamous Chrome Beta issue? I'm confused...

Has Franco acknowledged a real issue with r183 or is everything still inconclusive?
[Nexus 4 Original Android Development] jsmasterx:
Well it's seems there is something with the refresh rates or the Hardware overlay.

On other kernels, if the hardware overlay is on, there is no artifacts on screen. On this kernel, there is artifacts and the only way to solve the issue is to turn it off, using the software overlay,

Made a clean install on the kernel, erased boot before and install it using fastboot erase boot and fastboot flash boot

EDIT : BTW the bug only apply to JSS
[Nexus 4 Original Android Development] Drmol:
Aight so I'm having the superuser issue again but I'm completely new to logcats and everything so this might not be of any use but I tried to take one anyway

http://pastie.org/8330994
[Nexus 4 Original Android Development] scandalousk:
You do realize that you probably flashed the wrong version of the kernel on whatever particular rom you're using right.

The artifacts you're describing happens when you flash a JWR version of this kernel on a JSS ROM or Vice versa. Meaning you that's what probably caused the artifacts you're talking about.
[Nexus 4 Original Android Development] franciscofranco:
I need a log running for at least 20 seconds and in those 20 seconds there needs to show the granted SU request, otherwise I cannot check or reproduce! :)
[Nexus 4 Original Android Development] Drmol:
It was running for over a minute and the granted SU request was shown 4 times iirc, so I don't know what I'm doing wrong :D using CatLog app btw

It definitely has something to do with the perapp settings though, if I disable them from within the app, those SU notifications are gone
[Nexus 4 Original Android Development] whitedragonz83:
This JWR vs JSS is getting really complicated to sort our what is a "bug" with r183 and what is a "bug" with JSS and these "hybrid ROMs".

Honestly, Franco is a saint for putting up with JSS-anything and any non AOSP/Stock ROM.
[Nexus 4 Original Android Development] jsmasterx:
It was the JSS kernel.

If you put the JWR kernel on it, you will have a lot of FC and the NFC wont work and will keep FC.

I am always double-checking before flashing and I flashed boot-r183-JSS on top of AOSP
[Nexus 4 Original Android Development] drawde40599:
What rom? I don't have to disable anything on any rom as long as im using correct kernel.... They run flawless besides jss deadlock, i don't have issues u do, and Truthfully i don't think anyone else dose either with correct kernel , what rom?
[Nexus 4 Original Android Development] Arstoien:
Franco, have you had the chance to work on implementing the thread migration, you spoke before about, to interactive? Wondering how is that going?

Sent from my Nexus 4
[Nexus 4 Original Android Development] jsmasterx:
SlimRom 4.3 build 1
[Nexus 4 Original Android Development] HarbingerIV:
I also had this issue randomly show up after flashing a ROM or FK but, that doesn't matter cause that is not what is causing the issue. I noticed in Wake Lock Detector that there were two NLP wakelocks under Google Services keeping my CPU awake and after searching Google and XDA I solved the issue.

Go to App Drawer > Google Settings Icon > Location > and turn off "Location Reporting" and "Location History". Doing so should not affect functionality of Gapps but, I have Google Now disabled so I can't say if it will affect that.

Hope this helps as I now regularly get 4 - 5hrs and up of SoT (I us Greenify for Chrome and Facbook too). If not, let me know as I may have another tip for you! Cheers.:cowboy:
[Nexus 4 Original Android Development] drawde40599:
I don't use that rom but right in the title of that rom it says use jwr kernel. Your post says your using jss kernel ?
[Nexus 4 Original Android Development] jsmasterx:
Iit must be jss i think
[Nexus 4 Original Android Development] HarbingerIV:
This is straight from the Slim ROM website: "Note: mako user who use a 3rd party kernel need to flash a JWR kernel to avoid the JSS deadlocks on mako, even though the complete rom is JSS base. This is only for mako!!!!!"

You can view the website here: http://slimroms.net/

Cheers!:cowboy:
[Nexus 4 Original Android Development] franciscofranco:
Not yet, been SUPER busy with FKU and now the new N7. The amount of coding is slowing down now, so I'll have some time soon!
[Nexus 4 Original Android Development] limeaide:
Francisco I understand that Google services is being stupid however I don't understand why it happens only once I flash your kernel?

I appreciate the suggestions on how to "stop" this. But I bought the phone to use it like a smartphone not gimp it's features. I just want to understand why this is happening only with Franco kernel. I'm wondering if the per app modes is derping or it is just a fluke.

Sent from my Nexus 4
[Nexus 4 Original Android Development] drawde40599:
U sure its just this kernel? , i c people talking bout this in all custom rom 4.3 threads , My google services is 8% after 13 hours , purity rom and 183, ALL google sync and now features turned on . I don't have battery issues but is 8% alot.? Ive never looked at it before :P
[Nexus 4 Original Android Development] Redneck Trash:
Hmm... Just saw an update for fKu.
[Nexus 4 Original Android Development] limeaide:
I used the kernel that comes with cyankang and it lasted longer than Franco with more use. Android os was at the bottom of the list. That is why I'm asking. I don't understand why this happening. I'm going to use 183 tomorrow and see if it still happening. I flashed clean just to rule out a ninja app being derpy.

Sent from my Nexus 4
[Nexus 4 Original Android Development] drawde40599:
i wouldn't judge by order on a list id judge by percentage of use , but also what is normal or 2 high?
[Nexus 4 Original Android Development] franciscofranco:
I doubt its correlated with PerAppSettings, but you can disable the service and test for a while to see what happens. Let me know.

Yeah, merely bug fixings :)
[Nexus 4 Original Android Development] drawde40599:
I actually disabled your update refresh service and google services went down from 8 to 3 since my last post? coincidence? I don't have battery issues or even look at that stuff so i have no clue what's normal, but whiling to test **** for others...
[Nexus 4 Original Android Development] leader288:
Uninstalled it already. Phone rebooted while trying to place a call today.

http://www.mediafire.com/view/?uz6sx46v14l2x7z
[Nexus 4 Original Android Development] zephiK:
http://xdaforums.com/showpost.php?p=45641676&postcount=47219

read
[Nexus 4 Original Android Development] Andre_Vitto:
lol. l2r.. he says he uninstalled already..