yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] sconrad308:
I'm running stock 4.2.2, I tried to do a battery pull it wouldn't reboot, got stuck on the nexus boot screen. I had to use Odin to get it back up and working. No, the phone was on charge in the dock when it died. I just happened to wake up and it was daylight out. The phone was stuck at 4:08AM. I didn't do anything else to it except flash the kernel through the app. I will re-root and will do it again with the new kernel.
[Samsung Galaxy Nexus] Milleniumlance:
omg v-g-nex bfq, interactive clocked at 1.7ghz with rendering done with gpu...this phone is screaming fast thx franco!!!
[Samsung Galaxy Nexus] Spoderman:
Isn't that a bit too much? (OC 1.7Ghz..)
[Samsung Galaxy Nexus] Milleniumlance:
it only clocks to 1.7ghz when the cpu load is over 60% the interactive hispeed is 729mhz, it only clocks to over 1ghz when the cpu load is at 35-45%... its a stepped up ramp
[Samsung Galaxy Nexus] Sik-1:
Would you mind posting screenshots of your cpu setup???
[Samsung Galaxy Nexus] Milleniumlance:
im using muzzys lastest french vanilla rom and latest franco 376

https://www.dropbox.com/s/6qwnld8mg53svz0/2013-04-23 16.00.44.png

https://www.dropbox.com/s/yxwt1plh34ene5p/2013-04-23 16.02.59.png
[Samsung Galaxy Nexus] Spoderman:
I know it isn't locked at 1.7...but for playing games, or web browsing, it'll ramp up to 1,7 pretty quickly, thus making your device hotter and god knows what more.
[Samsung Galaxy Nexus] J-Hop2o6:
Interactive, 1.5GHz max (384MHz min / 729MHz max screen off) here with no problems. Plus using the great CFQ scheduler. I do have my hispeed_freq at 1.2GHz. And my highspeed_load and target_loads is 90/80. So these settings keeps regular phone usage at nice smooth speed, and ramps up to 1.5GHz under heavier load (games, web browsing, Play Store installs/updates).

Why can't I post normally? (EDIT: found out you can't use the "at" symbol/sign) (EDIT2: Guess it has to do with the recent XDA "at" update: http://www.xda-developers.com/announcements/new-feature-for-the-forums-mention-and-quote-tracking/)
[Samsung Galaxy Nexus] timbck2:
But don't you want people to use it and post logs when they have problems to help you figure out where the bug(s) are? Or do you have enough to go on for now?

Sent from my grouper or toro
[Samsung Galaxy Nexus] Khrushy:
Basically it's just a hassle saving thing. If you're happy to use bfq, get the occasional crash, and post a log then fantastic - that's a massive help and please please do it.

Most people just come into the thread and say "crashing with bfq" then don't answer any questions for detail, which is really frustrating for Franco.
[Samsung Galaxy Nexus] Gafanhotz:
I've did some tests now and came to this conclusion:

If you let your phone deep sleep with bluetooth turned on: Deadlock!

Tested AK Kernel: No problems.

Lean Kernel: No problems.

CyanogenMod Kernel: No problems.

Franco Kernel: Deadlock.

Note: It's on CyanogenMod 10.1, it would be nice to test with other roms, but I can't do that right now.

Note 2: Sometimes vibrations, notifications, everything, still working, but display is f***** up. Only pulling battery out to bet phone back.

KMSG: http://pastebin.com/XppNpMcy

Wondering why the hell everytime time bluetooth is turned off and on again it connects as a new AVRCP device. (It started as input7 and now I'm tryting to deadlock it again it's on device11!)

Oh these weird things Android have... I love it. -N
[Samsung Galaxy Nexus] Khrushy:
Had another reboot using bfq, with another good kmsg with crazy **** at the end.

Yesterday's + today's ksmgs are linked:

https://www.dropbox.com/s/g1pvq41egajor9l/last_kmsg 23-04-2013.txt

https://www.dropbox.com/s/gp3xl83gktf3lyr/last_kmsg 24-04-2013.txt

The second ksmg is 1.5MBs, just for a heads up.

Cheers
[Samsung Galaxy Nexus] malaroth:
My phone deepsleeps just fine with Bluetooth. I'm running shiny rom and I'd have to check what version but it was mid March. I also know that I never had an issue with jbsourcery.
[Samsung Galaxy Nexus] Gafanhotz:
I've got the the same deadlock right now on Xylon, but this time, even the logs it didn't recorded. The phone really got "dead".

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

Second KMSG, this was all I got:

http://pastebin.com/F3LCnGbn

After that last log, the phone "deadlocked" again.

Update: Got an logcat. http://pastebin.com/iF4hk7Gn

The amount of weird things with the bluetooth are scaring the **** out of me.

Update 2: Fourth deadlock in a row, without a ******* log! -.-'
[Samsung Galaxy Nexus] Khrushy:
I don't usually run with BT on, but I've turned it on and had the phone sleeping for the last 30 minutes with no issues here on AOKP. I'll keep BT on for the rest of the day to see if I can replicate your problem.
[Samsung Galaxy Nexus] osm0sis:
Do you have any devices connected? Or is BT just enabled and waiting? I don't have any other BT devices but I'll enable on stock and see. Governor and scheduler?
[Samsung Galaxy Nexus] wasdf:
Tested with bluetooth GPS and no problem...

Edit: Oops.. wait a second.. r376? so fast.... just updated to r375 few days ago, now updating to r376 and will test again

Edit2: just tested r736 without any problem too.
[Samsung Galaxy Nexus] malaroth:
2 Bluetooth earpiece and headset and GPS. No issues. If it's bfq you're running then switch and see if it's still a problem. We haven't started tweaking bfq yet so I dunno but I don't see an io scheduler being the issue. Rom issue?
[Samsung Galaxy Nexus] Gafanhotz:
No devices connected, just my car sound system paired with it, it searches for it for a while but deactivates as soon as it sees it's not on it's range. Then, BT is just enabled and waiting for something.

Governor: Interactive

Scheduler: deadline

I'll test with row to see what results do I get.

Deadlock on row too. (damn!)

Well, no devices connected on it. Just idling. And i'm using deadline. I don't like (to be sure I hate) bfq and cfq. And I tested Xylon and CM 10.1 and got the same deadlock on them both.

Edit: Got a deadlock more faster with the phone connected to my PC through BT. I'm starting to fix that "google's fix to solve bluetooth problems on jelly bean" is an huge bullsh**! If anyone experience this please report. I'll test AGAIN with all other kernels.
[Samsung Galaxy Nexus] Culex316:
Hi guys, I just flashed r376 and was trying out the new BFQ tunables and for a while it worked fine (opening Facebook, Twitter, etc) but when I opened the Flipboard app, it suddenly started to freeze/act slowly then the screen got yellowish followed by a crackling sound from the speaker and my phone reset.

Here is the last_kmsg,

I am running it on interactive with min 384mhz max 1420mhz, stock JB 4.2.2. ROM,
[Samsung Galaxy Nexus] Milleniumlance:
thats odd, is flipboard HTML 5?
[Samsung Galaxy Nexus] lordofazeroth:
One question to franco kernel:

When booting the phone has 1.2 GHz, right?

When are the higher frequencies set?

Is it possible to deactivate certain frequencies without using trickster mod or setcpu or another app?
[Samsung Galaxy Nexus] osm0sis:
To set things on boot without an app you need to use init.d sysfs commands. Search the thread for posts by me mentioning that. Or you can find it linked in the Odds & Ends thread on my sig.
[Samsung Galaxy Nexus] The Gingerbread Man:
[MENTION=4249301]Gafanhotz[/MENTION] try with stock rom, I've been on plenty journeys with my car connected to gnex with Bluetooth and never had anything like your describing.
[Samsung Galaxy Nexus] Culex316:
I'm not saying it's the app itself the phone just started acting weird and freezing and I'm hoping with the last_kmsg someone would know what caused it.
[Samsung Galaxy Nexus] duduzinho15:
If you're using bfq its the problem!
[Samsung Galaxy Nexus] osm0sis:
Same error as Khrushy.

[ 464.175659] Unable to handle kernel NULL pointer dereference at virtual address 00000038

BFQv6 is a lot of fun so far. :rolleyes::p
[Samsung Galaxy Nexus] Culex316:
I figured it was BFQ. Oh well. CFQ is working nicely at least without any random reboots.
[Samsung Galaxy Nexus] osm0sis:
Yeah, if Francisco can't do anything about that NPE in the short-term then he'll likely need to revert to BFQv5 for the milestone, so that it's nice and stable across the board.
[Samsung Galaxy Nexus] alangrig:
Have been running BFQv6 with max CPU 1.7ghz for 4 hours already. All rest is stock.

No issues at all. Will report later. Now working in Movie Studio. Project is 30 minutes long 1080p and gonna export project later. So the real test is coming up.
[Samsung Galaxy Nexus] Fenvarien:
BFQv6 is running stable here for more than 6 hours :confused: Max CPU @1,3GHz.
[Samsung Galaxy Nexus] Midomad:
Nice kernel awesome Devs.

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] whitedragonz83:
Those doing well with BFQ. Double check your uptime. I found it rebooting while in my pocket at least once. After a second reboot I had to go back to ROW or CFQ.
[Samsung Galaxy Nexus] wasdf:
Actually why everyone seems sticking at BFQ? ROW should better then BFQ because just it is Read Over Write, unless you are downloading torrent or updating lots of app on play store, Read speed is a really important key to make system running smooth. Please correct me if my idea is wrong :D
[Samsung Galaxy Nexus] Khrushy:
Your idea is fine.

Yes, favouring reads over writes is vitally important for the smooth operation of the phone, but that doesn't just blanket mean RoW is better. There is almost always *some* small writing going on in the background and favouring reads *too* much leads to hiccups when these writes either get delayed (which then delay further reads that are waiting on them), or delays when the writes all pile up in the queue and then are serviced at once. Of course, that's not a problem with the tuned RoW settings on Franco.

That said, your advice is valid - I'm also not sure why everyone is sticking on BFQ with the knowledge that it's causing reboots - if they want smooth fair IO operations then both the CFQ and RoW settings are excellent - and are probably better than the current, untuned, BFQ settings (with the added bonus they don't cause reboots).

BFQ technically should be an excellent scheduler, it has all the fairness advantages of CFQ (and it's that fairness with how it handles multiple threads that makes CFQ feel so smooth) with added goodness to handle heavy IO situations better, but I'm not sure it's worth random reboots for most people.
[Samsung Galaxy Nexus] Milleniumlance:
i have to switch to CFQ i was getting reboots when i ran Onecast podcast while at work
[Samsung Galaxy Nexus] 93fuelslut:
A bit confused. Do I go by my ROMs version or stock ROM version? I believe my stock version is 4.1.1 but my ROM (jb sourcery) is 4.2.2.

My battery is horrible with stockkernel so I wanna try something new. Im a motorola guy so i dont know abt kernels.

Just download the kernel, and reboot and if i dont like it, i can just restore my nandroid?
[Samsung Galaxy Nexus] wasdf:
True :good:
[Samsung Galaxy Nexus] Milleniumlance:
you go by your rom version, your rom is the current version your using if its jb ssourcery 4.2.2 you use r376 (which is AWESOME!!!)
[Samsung Galaxy Nexus] Efrenjr15:
R376+codex ROM is the best combo ever!!!

Quick question ,I seen someone mentioned there clocked at 1.7 but is not locked in at that speed only until the demand is needed, what governor or I/O is needed for that?

From what I understand the CPU won't go as high until ex.games,browser, etc are being used.

Tia
[Samsung Galaxy Nexus] chugger93:
Anyone else have issues with their batteries just getting rapped for not doing much of anything? (Surfing/text etc)
[Samsung Galaxy Nexus] bigknowz:
build.prop

Anyone have any thoughts on this build.prop tweak to enhance smoothness?
[Samsung Galaxy Nexus] Kyle C:
Every damn day with this phone. Haha. No matter the ROM/Kernel.

But to answer your question more seriously; no, nothing seems out of the norm on my particular device.
[Samsung Galaxy Nexus] osm0sis:
Interesting find! Good looking out! We'll be looking into vm settings next so we'll definitely check it out.
[Samsung Galaxy Nexus] Charmacas:
You and every other who contribute so much to the community have my respect! It's great what you're doing! :)

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] bigknowz:
build.prop

Have to give credit to Goofball over at the Shiny ROM thread, was his find.
[Samsung Galaxy Nexus] irminsul:
Testing those setting presented on the site.

Gonna report later, on first note nothing is different.

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] Charmacas:
I did a restart because I read somewhere that this is important to get the tunings in the build.prop to work. Is that right?

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] albedebbi:
I have the correct values :

View attachment 1911303

So, this is why I never had problem about lag or memory leak.

I'm running Rasbeanjelly by Rascarlo :)

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] irminsul:
You gotta reboot, yes!

Vanilla version of rasbean had other values, was quite sluggish even with systemui restarting.

Scrolling in tapatalk is way smoother.

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] Sik-1:
No, its supposed to be 64m instead of 96m and I personally change the 256m to 192m, much smoother for me even on lower cpu freqs
[Samsung Galaxy Nexus] albedebbi:
:crying:

pardon
[Samsung Galaxy Nexus] Charmacas:
The values I read about where 64 and 384. I am running them right now and it's running fine so far. But after a reboot everything works fine for a while. I have to wait at least 24 h. :)

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] Sik-1:
What didnt you get????
[Samsung Galaxy Nexus] Zadeis:
I think he was more so referring to the fact that defaults for 4.1 are 64 and 256. If you go down the google thread a bit more someone mentions it is 256 not 384.
[Samsung Galaxy Nexus] 93fuelslut:
My battery is still getting raped. Any idea's to help or a battery app (preferrible free) to see what's up?

I got one battery app but I don't know what I'm looking at
[Samsung Galaxy Nexus] Charmacas:
Yes, you're right. I read this a few hours ago and these posts were not there. :)

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] irminsul:
Look at better battery status, the xda edition is free. Install the app, advanced settings put root features on, charge phone in the evening and let it idle for a night. You can check wakelocks, and post a log here and in the app thread. People will help you understand ;) therefore this is called a community.

Verstuurd van mijn Galaxy Nexus met Tapatalk

---------- Post added at 08:59 PM ---------- Previous post was at 08:58 PM ----------

Running 64/256, so far so smooth. Post back in a day because people report that the lag returns.

Verstuurd van mijn Galaxy Nexus met Tapatalk

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

Running 64/256, so far so smooth. Post back in a day because people report that the lag returns.

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] JBNex:
So there's 384 and 256. What's the best value for the max value? :P
[Samsung Galaxy Nexus] Charmacas:
384 = Nexus 7

256 = GNex

Edit:

But I do not understand that. Thought it may be regarding the RAM but both devices got 1 GB. Maybe someone could explain it more technically!?

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] irminsul:
The available ram on gnex is only +-690mb, in nexus 7 it's more but don't know exavtly how much.

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] bunnahabhain:
974MB
[Samsung Galaxy Nexus] xI mEzMeRiZe Ix:
I posted a question about this on reddit a few weeks ago and everyone seemed to agree it had to do with the cellular radio occupying the RAM.
[Samsung Galaxy Nexus] lippol94:
I'm not sure if it's the same with Galaxy nexus, but on my old I900 (Samsung Galaxy S), altough it was shipped with 512MB of RAM, only more or less 300 MB were available to user. That was due to a defined amount of RAM destined to, for example, HD decoding/encoding while recording or playing a HD video.

Probabily it's the same on Galaxy Nexus.

On the other hand, on Nexus 7, which doesn't have a rear camera, it doesn't have to process huge images (frames taken by rear cameras) in order to create an HD file.

So here's why Asus didn't take a lot of RAM away from the built in one.

This is just a supposition. But it might be true.
[Samsung Galaxy Nexus] Fenvarien:
Yes, that is probably the case. Current custom kernels like Semaphore for the SGS provide 397/409 MB RAM (with HD video recording / without) by working around many memory limitations.
[Samsung Galaxy Nexus] ak:
Holy word! :fingers-crossed:
[Samsung Galaxy Nexus] Khrushy:
That post was awesome, but I'm actually commenting to declare my love for the quote in your sig. That. Is. Fantastic.
[Samsung Galaxy Nexus] J-Hop2o6:
Well I guess this is goodbye. Went ahead and bought the HTC One from Tmobile. Very good phone all around (design, material, performance, screen, speakers, etc). Franco.Kernel was the main and only kernel I used with my short time (6-8 months) with the GNex, and it was great tweaking every last bit of performance out of this very old SoC (CPU+GPU) including scheduler tweaks. Thanks for tweaks and testing you guys (Franco & Company), and hopefully I'll see you over on the HTC One side, or even the next Nexus (5?) this fall/winter (if its great enough all around).

EDIT: I'm sure i'll be back to test out Android KLP/5.0 + Franco.Kernel r4xx ;)
[Samsung Galaxy Nexus] thegtfusion:
Good! Tell me when you start to dislike sense ;) :beer:

Sent from my Nexus Prime
[Samsung Galaxy Nexus] J-Hop2o6:
Its actually not bad. Elegant looking and not bloated feeling. Smooth and doesn't slowdown or stutter. But I do keep switching back and forth between Sense Launcher and Nova Prime Launcher. Keep missing my gestures and other tweaks in Nova.
[Samsung Galaxy Nexus] shawnaye:
Wonder if there are as many people that dislike sense as there are touchwiz & motoblur.

Stock is just so much more meaningful.
[Samsung Galaxy Nexus] J-Hop2o6:
I enjoy Stock also (been with it since 1.5/2.1). But it does miss a few extras that Skins and Play Store Launchers have. But Google is getting there. Sense has came a long way since previous versions, but Sense 5.0 is fine. Looks wayy better than that kiddish Touchwiz skin. But hey, Nova Prime FTW!
[Samsung Galaxy Nexus] shawnaye:
Touchwiz, probably the primary reason I will never get a Samsung again.

I mean, it's great hardware, but when the hell can their software team properly understand what people want.
[Samsung Galaxy Nexus] osm0sis:
Yeah they've still got that hideous color scheme from Gingerbread on there, and blech. I was actually playing with the HTC One at a cell kiosk the other day, and gotta say I was pretty impressed with how far Sense has come.
[Samsung Galaxy Nexus] Khrushy:
THIS. I live in Seoul, home of Samsung, and seriously, given that everyone cloaks their phone is some obnoxious case and the touchwiz UI hasn't changed in 25 years or so, it makes it ridiculously hard to differentiate their products.

I glanced at a guys phone in the elevator this morning and thought it was an original Galaxy S. At second glance I realised the screen size and that it was an SIII.

Just so ugly. You're doing something wrong when a self-affirmed phone nerd can mistake your recent hardware for stuff from 3 years ago.
[Samsung Galaxy Nexus] hdoraemonk:
Since r374, sometime device freeze, then must pull battery. I use default config (row, cubic...) :(
[Samsung Galaxy Nexus] osm0sis:
Follow the f.Ku Emergency Reset Zip link in my sig. Flash it in recovery and see if that helps.
[Samsung Galaxy Nexus] 93fuelslut:
Can someone please help me

I have the app better battery stat, but idk how to use it or know what I'm looking at. When I wake up, where in the app do I go to see my log and then post it? I flashed this kernel but my battery is still the same and someone said they got better battery from this kernel. So can someone please give me step by step directions on the app to post my log
[Samsung Galaxy Nexus] osm0sis:
1) Go to the Better Battery Stats xda thread.

2) Ask them.

;)

It's not a hard app to figure out but you need to learn to search and read before you post, not just expect things spoon fed to you.
[Samsung Galaxy Nexus] 93fuelslut:
Thanks but I did
[Samsung Galaxy Nexus] shawnaye:
Tell me about it... I was using GB on my S2 last time, and when ICS came out, the whole S2 community basically flamed Samsung for their crappy design choices.

Hah, you can only imagine how hard it'll be to differentiate the S3 & 4 now.
[Samsung Galaxy Nexus] chugger93:
I don't get how my battery sux with this kernel. I literally took my phone off the charger 1 hr ago exactly..and I'm down to 92%. I havnt picked it up once or turned on the screen since I took it off the charger. How is this possible??

I'm even at 384/1024 or whatever. I have my max clock down to a gigahertz for Chris sakes. Nothing running in the background. What the sh*t gives!!
[Samsung Galaxy Nexus] whitedragonz83:
Look at your battery window. See what processes are using more battery then the screen.

Look at your graph and see how bad your mobile connection is.

"Nothing running in the background" is wrong. There are always apps running constantly. One likely is screwed up. Oftentimes I found my GPS to be the fault as seen by high Google Maps. A reboot fixed. So more information please, even though this is not kernel related.
[Samsung Galaxy Nexus] chugger93:
Umm.. My battery window only has the android processes and the screen. That's it. Phone idle, android is, cell standby.

Its not.mobile data Cuz I'm connected to wifi

---------- Post added at 10:15 AM ---------- Previous post was at 10:12 AM ----------

The only apps running that I see in apps -- currently running are:: Facebook, mino golf, Google voice, light flow and power amp
[Samsung Galaxy Nexus] Angelakaro:
Give a look at your CPU usage, maybe some apps like social networks constantly update and may wake up your device.

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] bigknowz:
Battery

First hour is the worst. My last discharge went the same way. Unplugged at 8pm, Lost 8% in 1st hour, woke up 6:30 with 82% Ended up going almost 36 hours with standard battery.
[Samsung Galaxy Nexus] whitedragonz83:
Do a reboot, full charge phone, disconnect it. See what happens in an hour. It really could just be that android was syncing a lot of things that hour and you got exceptionally high drain. Or maybe Google Services was a "grey bar" when you turned it on, indicating it was disconnected from Google a bit and didn't know what to do except stay awake.
[Samsung Galaxy Nexus] chugger93:
Thanks for the responses folks. Ya I dunno. I froze lightflow and my golf game just to test in the meantime with titanium as starting points. Maybe my battery just sux these days and I should get a new one?

If I'm in the franco app under system monitor --> apps, android system climbs to the top CPU wise like every other second or so. Franco app does too, but that's because its running. So what Android system consists of, I have no idea
[Samsung Galaxy Nexus] whitedragonz83:
Chugger, I use LightFlow without noticable (significant?) battery drain.

Android App will be constantly running at the top in the CPU monitor under Franco's App because it is the core of the phone.

Take a screenshot of your Battery Window, click the graph and screenshot that, and also click the "screen" entry and screenshot that. These are the basic 3 screenshots needed to even begin to help. Preferably, fully charged and after it was allowed to discharge 1-3 hours without turning the screen on.
[Samsung Galaxy Nexus] The Gingerbread Man:
Facebook app for android is the culprit, use browser for using it.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Raijin:
Now that there is the talk, do you know if LightFlow and WhatsApp take battery/performance?