yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] malaroth:
Hadn't noticed... same on 357 as 358 now eq doesn't kick in till opening dsp through Google play music (maybe cuz it's blacklisted on auto killer) but then all :good: not experiencing freezes or stops. Not too big of an issue. The volume before eq kicks in is plenty loud on Bluetooth and phone speaker

JBSourcery 4.1 Franco 357 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] momomok:
ROW seems ok for now (just flashed r358 10 minutes ago)

Phone call is still unhearable using wired headset

Sent from my Nexus Prime
[Samsung Galaxy Nexus] haxor:
Just flash 2013 first kernel ;) #358 it seems ROW smoother than deadline but it is in experimental stage so looking forward volume is quite good even on speaker phone :thumbup:
[Samsung Galaxy Nexus] calinoii:
Hey,I'm using r300 on aokp 4.1.2 milestone 1 and I just raised CORE voltages with 50 MHz and the CPU voltages with about 25 MHZ each,is this wrong? I think I have a problem with my chip and the stock voltages were making my phone sluggish
[Samsung Galaxy Nexus] haxor:
Its already cleared by Franco dat don't play with voltage let SR do their work....
[Samsung Galaxy Nexus] bombadier:
Wired headset volume is a lot better on r358, am happy.

Tapatyping from my Nexus
[Samsung Galaxy Nexus] The Gingerbread Man:
I just had a call, I literally couldn't hear any sound from the ear piece speaker I had to take the call on loud speaker. Switching to loud speaker and back didn't work, volume was at 100%.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] joaquinf:
Hi guys!

I just flashed r358 and everything is working fine here as expected. Didn't find any trouble with ROW (i.e bootloops) as some people mentioned. Actually as far as i can tell it feels snappier than deadline, at least doing basic things like browsing through menus and opening apps. Call volume through earpiece is fine too.

I Haven't stressed that much yet. I'll report my internet browsing, gaming and music playing findings later. I'm at work starting a darn busy week/month, sorry for the vague feedback

Thanks for this great frirst kernel of the year :cowboy:
[Samsung Galaxy Nexus] irminsul:
My phone seems to like ROW, but it's hard to see noticeable difference compared with deadline. I don't run benchmarks or stuff like that. For me it seems to be equal, it's not that choppier or smoother than deadline. Apps seem to start and load a little faster, don't know if it's a placebo or not.
[Samsung Galaxy Nexus] prembox:
Yeah...flashed 358 half-hour or so....Phone definitely seems smoother n snappier on ROW. I also noticed that there is no stuttering while scrolling in the Settings Menu.....that's nice as that always used to bother me a lot....
[Samsung Galaxy Nexus] ethanhunt123:
Sound issue where it would stop playing through 3.5" mm port is fixed. thanks franco!
[Samsung Galaxy Nexus] gaich:
I thought it`s 4.2 feature - my volume is 100 % (both ringer and mutimedia), I listen to the music in my headphones, but whe I receive an incoming call - I cannot hear the caller- my volume becomes some 50 %, I have to adjust it manually again...
[Samsung Galaxy Nexus] allgsmnetwork:
Is true the menus flows better with ROW of deadline you had to put more strength do the test scrolling through the menu by touching without force has more thrust or power,only problem audio very high :good:
[Samsung Galaxy Nexus] duduzinho15:
I had 4 reboots in 358 all config in default
[Samsung Galaxy Nexus] peikojose:
I have been testing r358 for about 2 hours... It seems good... I'm still testing but haven't got the cracking sound when receiving a whatsapp notification...
[Samsung Galaxy Nexus] lesp4ul:
r358, 192/1036, interactive, ROW for hours now. No SOD. Notif/ringtone volume is absolutely louder. Thnx Franco :)
[Samsung Galaxy Nexus] cenwesi:
Not TRUE at all. I tried r357 2days ago and thought it might have to do with the cm10.1 nightlies that my BT and 3.5"mm will switch back and forth. Little did i suspect it was francos' kernel. Tried r358 today and the same thing with the lastest cm10.1 nightlies. Then i decided to re-install the nightlies without franco's kernel and NOT one issue with the sound. I have so far gone back to r348 where i am pretty sure worked fine.
[Samsung Galaxy Nexus] aimcr7:
Running 358 for almost 4hours without any issue, using the same settings as 357. Havent got any sound issue yet with franco kernel. :)
[Samsung Galaxy Nexus] The Gingerbread Man:
Is any one else having weird charging issues? I'm sure Franco hasn't changed anything there but before I left for work my phone would not charge using wall charger. I tried two different chargers in two different rooms. I removed the battery, rebooted, pulled out battery plugged charger in the put battery in again and what ever I did it would not charge. All I have done is update to 358 and using ROW :confused: in the end I ran of time and had to leave for work with battery at 60%

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] whitedragonz83:
ROW enabled and I can wall charge. Reboot the phone and try charging again?
[Samsung Galaxy Nexus] itasoulas:
I also confirm that. Music stops for no reason while on headphones/out. I am on stock 4.2.1

345 and 348 all the way!
[Samsung Galaxy Nexus] allgsmnetwork:
try flashing emergency and back again 358
[Samsung Galaxy Nexus] The Gingerbread Man:
Well if you say that then at least it's not kernel related. I did try that if you read what I did to try trouble shooting it.

That's if you get stuck at boot loop for if you set your voltage to low and enabled set on boot. Gonna be about 8 hours before I'm home I hope my battery lasts my shift :eek:

Sent from my Galaxy Nexus

---------- Post added at 03:58 PM ---------- Previous post was at 03:45 PM ----------

Just had another call where I couldn't hear, had to use loud speaker. I think my nexus is getting faulty

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] giugiu:
+1

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] Piemo:
Maybe is a stupid question, but I'm quite a noon about kernel.

Could someone explain me in a simple way why the 3.4 kernel can't be merged for galaxy nexus or (if it's possible) why it isn't done yet?

Not an attack to the great Franco's work, just to understand...

Sent from my AOKP'ed Galaxy Nexus swyping with my nose.
[Samsung Galaxy Nexus] allgsmnetwork:
I think having a franco nexus 4 wants to improve the kernel did today in 358 has entered the shudler ROW like nexus 4 wants to give the best of himself.

But I am very confused about which kernel to use the 348 is that it seemed more stable, others I look the same I do not see a revolution but it will come I'm sure :good:

But Franco does great work he is a master is always pushing to the maximum :good:

Great franco :)
[Samsung Galaxy Nexus] b1337:
because GN is old..
[Samsung Galaxy Nexus] _chanstar_:
ROW feels as smooth as Deadline, just a little faster. When scrolling on Deadline, I couldn't make out anything since it scrolls so fast without stuttering. On ROW, I can't see anything period sometimes since it scrolls so fast without stuttering.
[Samsung Galaxy Nexus] logi43:
E R358 ex used this morning and row / interactive 192/1228 there is sod's not freezing, and all I have seen is that when I listen to music with headphones and volume lock screen descends automatically, this did not happen before with R356 / 7

I use Sound mod with rom Xlouder stable xylon 014

Greetings and thanks for development work
[Samsung Galaxy Nexus] Piemo:
Yeah, I understand what u mean, but aren't the repository and the source of the whole system and the kernel both public?

I see that for now 3.4kernel isn't only for n4, so there's something that people can do to compile it as it was done for the padfone?

Can't understand where the problem exactly is. In the phone that can't support the kernel, or in the kernel that needs something precise to be compiled?

Sent from my AOKP'ed Galaxy Nexus swyping with my nose.
[Samsung Galaxy Nexus] whitedragonz83:
Google did not update their source for the GNex to 3.4. As such, Franco didn't either. If you look here, there is clearly a large amount of work to make 3.4 compatible with the GNex. http://xdaforums.com/showthread.php?t=2071021

Likely, MANY changes to the 3.4 kernel do not even apply for our phone/AndroidOS. I know Franco tried to get the WiFi drivers to work and it broke WEP security so he reverted them. Along with Tethering and other things.
[Samsung Galaxy Nexus] markop90:
Kernel panic with ROW scheduler...cannot upload the last_kmsg with tapatalk, i guess it is similar to the other
[Samsung Galaxy Nexus] fatappel:
r358 interactive/row running fast, stable and with good battery life as far as I can see so far. audio's good too. nice addition. thanks

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Ronaldo Forenucci:
Franco,

I will test r358 later today, with 1/8" / 3.5mm Line Out cable to see if the speaker switching occurs. Thanks for the hard work.

RF
[Samsung Galaxy Nexus] franciscofranco:
Thanks everyone for all the logs and feedback. Todd Poynor from Google just sent me this email regarding the Interactive patches he has been working on:

"Hi Francisco -- Oops, my GN running over the holiday got an RCU stall detected on a spinlock deadlock between a transition notifier and a timer, grabbed logs and will look at it later today."

So glad to be able to help him fix the bugs from the logs I gather from the users. This is open source :)
[Samsung Galaxy Nexus] Kirill31337:
Still music random stops... :((( r357 & r358
[Samsung Galaxy Nexus] The Gingerbread Man:
Lol now my phone refuses to play mp3 on 357 and 358 but some sounds are working like turning up the ringer volume and alarm.

So to some up my day, I can't hear calls, my mp3 are screwed, no sound on video, very low volume on notifications (tested by texting myself with volume at full) and my phone won't charge

Edit

Same on 348. Using minco v6 here btw

Does anyone have any ideas?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] _yaz_:
it seems gnex has some general issues with sound playback. for me, mp3 plays fine (so far !) but some flac files do not. some are playing but some are not even recognized with any obvious reason :confused:
[Samsung Galaxy Nexus] razvanultra:
InCall Sound Volume

Hello,

I have done a real sound test, for in call volume, it's louder in older build#348 than the latest build #358.

The test was done with connecting a stereo jack - jack cable from the telephone output to the sound card of input line (Realtek® ALC892) with the volume set to 80% at the computer and maximum from the telephone.

Here are the files: http://goo.gl/l6YNL

ps: the language used for the recording is romanian.

I have also noticed that are random music stops, using Youtube. I have not tested other things, I observed less battery drain from previous build, but this is just a thought. Because tomorrow I need to have loud in call volume, I'm back to #build348.

Once again, thankyou for your time.
[Samsung Galaxy Nexus] Jerreth:
I going to r358 still have to turn the volume down 2 clicks in order to keep playback going. previous version I had to turn it down 3 clicks hope this helps.
[Samsung Galaxy Nexus] allcity187:
R358 fix the issue with the music stopping, I listen to Pandora for over 2 hours with no issues.
[Samsung Galaxy Nexus] franciscofranco:
Can you try stock or another rom? Maybe something is ****ed with MiNCO. If you reproduce that with another rom, great, its not MiNCO, if its ok with other rom then its MiNCO's fault. Just do a nandroid and flash other rom and test it quickly ;)
[Samsung Galaxy Nexus] The Gingerbread Man:
Will try later if I can, I got not enough memory to nandroid, twrp is being gay about paths so won't allow restore to stock, got 13% left, 4 hours left at work and at home phone wouldn't charge

Edit

The words **** the bed come to mind

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Gd Ahmed:
#build348

first thnx to franco for his hard work

i hear so mush about franco kernel build 348 how great it is

can someone post a link to franco kernel #build348.

thanks
[Samsung Galaxy Nexus] cenwesi:
here you go

http://minooch.com/franciscofranco/Galaxy Nexus/JB/JB-4.2/zips/
[Samsung Galaxy Nexus] osm0sis:
I see the headphone volume interface is hardcoded back to 3 again for r358. Maybe putting it to 2 or 1 would still help some of those with issues remaining while keeping some boost. :)
[Samsung Galaxy Nexus] :
I'm still having music issues, but I had them before cuz if I use the volume boost at all it causes the pausing on all you're kernels for GNex

PS. It's not just your kernel
[Samsung Galaxy Nexus] The Gingerbread Man:
I'm having my issues on 348 ( which is before the boost was reintroduced) and 357 and 358. I think mine is ****ed tbh :(

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] galakanokis:
358 working well for me. Not sold on ROW yet but will continue to use and see if I notice any differences with it compared to deadline. It gives a slightly slower result for i/o reads than does deadline but only a couple of ms.

All volumes seem fine, if anything I find the headphone volume to loud. I run it only a few notches above off for volume. Full volume is way too loud. Tested on headphones, external computer speakers using the headphone jack, amp with mini to RCA and just the built in speaker. No drop outs with Pandora or Google music.

With regards to the low in-call volume are people referring to headsets or just the earpiece on the phone? I tested on earpiece only and it is fine on my end, lots of range on the volume.

G
[Samsung Galaxy Nexus] Gd Ahmed:
thnx

thanks man
[Samsung Galaxy Nexus] cenwesi:
Nope, there is problem with r357/8. I know this because i listen to Audio Books all the time in my car using 3.5"mm and with BT. I even tried turning off the BT and the same problem. Just got done testing it again with r348 and not one switching for over 30mins. With r357/8 it will start switch withing 30 seconds...
[Samsung Galaxy Nexus] Ridho1:
Do you use fast charge oftenly? My GN's USB port was broken. And I believe it is because almost every day I use fast charge, and it happened after I fast charged it.
[Samsung Galaxy Nexus] Khrushy:
Tested RoW again after switching batteries (no linkage between the two, I just emptied one and decided to try RoW again randomly).

I like it so far. Seems very smooth for my usage, which generally involves very few writes. Not an earth shattering change, but ever so so slightly noticeable.

Also not sure what caused RoW to crash the first time.

/scratches head.
[Samsung Galaxy Nexus] galakanokis:
Sorry, nothing happening here, no drop outs or switch overs. Only been 15 mins or so but I will let ride out the day at work here and see what happens. Phone plugged into mini jack to a set of Dell desktop speakers.
[Samsung Galaxy Nexus] Ronaldo Forenucci:
Ok, I just installed r358 and did some testing using the exact same files/scenarios that I had a problem with in r356/r357 - Line Out cable to desktop speakers, volume at max on Android sliders.

First off, using BeyondPod and listening to the BYOB Ep 107 Podcast-

http://homeservershow.com/byob-episode-107.html

I had the speaker switching issue just once for each play of the file. At the beginning of this podcast there is a music intro, and it caused the switch to the internal speaker. BUT, where as on r357, it would constantly switch back and forth, on r358 it just did it once and then played fine through the desktop speakers. Better, but not perfect.

Edit: I want to add that it didn't do it every time though. I stopped and re-played the beginning maybe 6 times, and it switched to the internal speaker maybe 3 or 4 times.

Now for the bad news: I then tried Noozy Music Player. Music would pause with any volume over 12 (Noozy doesn't use the Android sliders, it has its own volume control 0-15).

I then tried everything using just the internal speaker, at max volume, and all was well...so there is a Line Out problem still.

I did not try any Bluetooth headphones or speakers.

RF
[Samsung Galaxy Nexus] Khrushy:
He mentioned his wall charger, so fast charge would have no effect because a wall charger isn't checking if those pins are shorted anyway.

Besides, fast charge shouldn't do anything detrimental anyway (I almost always have FC on)

It's more likely just the unfortunate fact that the GN's USB port is notoriously dodgy.
[Samsung Galaxy Nexus] The Gingerbread Man:
Yup two different chargers in two different rooms but same model as each other. I'm praying I have enough juice to get me home and flash stock rom img. 4% left and two hours left at work. Am using beastlybattery power mode to hope it can make it limp home. I really shouldn't be using my phone so I'll report when I can. Wish me luck cos I really need it!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Paragon_X:
Quick question. I've noticed that when accessing swiftkey keyboard via twitter, facebook anything there is considerable lag in that I can type a full sentence before it even shows it on screen. I was wondering what settings I could play to curb this problem? I'm on AOKP12/27 R358.
[Samsung Galaxy Nexus] rolear8:
No problems here, have you tried with the default keyboard?? Also could be a dirty ROM flash
[Samsung Galaxy Nexus] Paragon_X:
Thanks, I completely overlooked the fact I've been dirty flashing, maybe it is time for a fresh install. Stock keyboard gave same results, not as bad but still there regardless.
[Samsung Galaxy Nexus] Khrushy:
First suspect is dirty flash, as I've had that happen before. Secondly you could try a different i/o scheduler. I found that distinctive keyboard open lag only happened on deadline. With BFQ or CFQ it was never an issue (but performance suffered when multitasking and switching between apps).

Haven't had long enough to test RoW yet to comment really.
[Samsung Galaxy Nexus] asim0:
Feedback on r358

row: a little more snappy to me (will see if it affects battery on the long term).

Sound: I just played Temple Run and there was so many cracks I had to turn the sound off; yes it's that bad, and it was less than 50% volume.
[Samsung Galaxy Nexus] slayr76:
How do you change the speaker volume settings with r358 kernel, I don't notice any difference in speaker volume after flashing it, I have Franco's kernel app an trickster mod but don't see the volume option, by the way Franco kernel updater app v8.2.5 force closes on every reboot on cm10.1 rom
[Samsung Galaxy Nexus] malaroth:
I use fast charge every day and nothing broken

JBSourcery 4.1 Franco 358 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] sframbo:
Also using run358 with iO-scheduler "row". What governor have I got to use best with it? BTW, runs smooth with no SOD on aokp_maguro_unofficial_Jan-01-13.

Gesendet von meinem Nexus 7 mit Tapatalk 2
[Samsung Galaxy Nexus] decarre:
Hi franco your work is amazing i have gnex and nexus10 i hope maybe one day you work on nexus 10 :)

Thanks a lot and Happy new year :)
[Samsung Galaxy Nexus] whitedragonz83:
Interactive defaults. Franco has this tuned great for the nexus.
[Samsung Galaxy Nexus] franciscofranco:
I just ordered a Nexus 10 few minutes ago ;)
[Samsung Galaxy Nexus] RayGarden:
the Nexus 10 is my wish for 2013. It will not be available in the NL so i have to search cross-border. Any suggestions?
[Samsung Galaxy Nexus] warranty45:
Severe Audio Issues

Since the addition of the audio boost I have had Google Music stop as soon as I play. I was able to deal with this by turning down the volume. I updated to 358 today and the issue is still there and I have discovered YouTube videos won't play through the headphone jack. I would really like a way to disable the boost because I've only had problems with it. I don't want to have to switch kernels since I've been with it since I got the GNex and I know it is the best one out there.
[Samsung Galaxy Nexus] sframbo:
Has he not said, dyninteractive was the optimized one?

Gesendet von meinem Nexus 7 mit Tapatalk 2
[Samsung Galaxy Nexus] decarre:
Dude...you rox :) i m waiting for an amazing kernel !! :)
[Samsung Galaxy Nexus] _chanstar_:
Sick!! LOL
[Samsung Galaxy Nexus] osm0sis:
That is JB4.2 and has been that way since it came out. So Google's **** up at least or the game devs' since I also haven't seen that with other games.

He put a bit of work into it, but no, he didn't say that, he just explained what dynint is; interactive which adjusts its own tunables. Unfortunately this process also appears to involve a bit of overhead, so interactive, when he added it back, was much snappier. That's why he made interactive the default again :good::)
[Samsung Galaxy Nexus] yellowdie:
Holy crap! It's finally in stock!!!!!!!!!!! :) :D :D :D :)

Edit: grrrrr.... Now I have to make a decision again... It was an easy choice not to get it--when it was out of stock!! Lol
[Samsung Galaxy Nexus] The Gingerbread Man:
Good news guys my phone is charging again and the video sound/mp3 sound is working again, ear price speaker worked on a test call but not my microphone. I'm so freaking relieved

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] GeekMcLeod:
With 357,as far as I could tell, my music worked fine using power amp. With 358,it stops randomly again. I have to turn my volume down by a couple notches for it to work on 358.

Again,not a huge problem. I'm happy with using songza.
[Samsung Galaxy Nexus] tetrakinitis:
franco.Kernel r357+rasbeanjelly *1305-537. 729 screen off. 1036-729. cfq-westwood. no uv, just smartreflex as Franco said.:thumbup:

And one for rascarlo :thumbup: for the best rom around here. The Army of Two...

Thanks Franco and Happy New Year!

I wish you the best :)

Sent from my SmoothCriminal™
[Samsung Galaxy Nexus] salemsayed:
Running latest nightly 358, music playback is fine using poweramp, however phone calls through headphone is the worst. I can barely hear the other person I'm calling.
[Samsung Galaxy Nexus] sonnydroid:
I'm experiencing the same thing.
[Samsung Galaxy Nexus] DMonster:
Same here but I am on r357. My girlfriend was gonna kill me last night when she spoke very loud over the phone but I could barely hear what she said...:(
[Samsung Galaxy Nexus] tribaleps:
Sound performance

Not sure if I'm really blind, but I noticed that there's no longer an option to tweak sound performance in the app. Anyway, only started hunting for the option recently when the call volume on wired headset was unbearably soft. Flashed leankernel (thanks to the convenience of doing so in the kernel updater app), and reverted back to franco's to get it sorted out. Today's my third time doing so in the past 4 weeks. Running on Roman's AOKP 27/12 build.
[Samsung Galaxy Nexus] osm0sis:
High performance sound was terribly buggy before but became very broken with JB4.2 so is not included anymore. Headphone volume boost is currently what we're testing, but it's hardcoded so there is no option in f.Ku for it. :good:
[Samsung Galaxy Nexus] slayr76:
My phone refuses to wake after receiving a phone call on 358 an just flashes with notification light, might be rom related though, never had that problem before.
[Samsung Galaxy Nexus] tribaleps:
Sound performance

Thanks! Guess I'll have to stick to 'reflashing' kernels in the mean time to sort out call volumes.

Btw, love your color settings...I feel it is the most ideal. :)

https://www.dropbox.com/s/w4fde5ql9503efy/Screenshot_2013-01-03-10-45-52.png
[Samsung Galaxy Nexus] calibachrome:
Phone randomly rebooting and acting as if it is charging while unplugged and not charging while plugged up... Any ideas?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ad astra:
hi, first off thanks for this wonderfull kernel. been using it for quite a while now.

just wanted to report that since since nigthly 356 ive been hearing a static like sound after i press any button (even volume rocker) wich ends with a crackling tone.

its all bearly audible, you have to be in a quiet place with the device near your face.

i just found out that it doesn't happen with the keyboard.

the other thing i found is related to music playback.. when a theme is playing real quiet (u can try lowering the volume) it sounds“ crackly" on my sgs3 earbuds. mp3 quality is allways 320kbps.

hope this helps!!

im running PA 2.99 b9 and nightly 358.