yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] allgsmnetwork:
I use only 2g and 3g when I can not find wifi signal away from home so I have to use the 3g but with # 358 this does not happen too excessive heating so for me in # 361 there is something that does not work well...in #358 i not used UV.
[Samsung Galaxy Nexus] Angelakaro:
Android system is a set of services by google,android operating system is something different but i think they're almost the same thing

Inviato dal mio Galaxy Nexus usando xda premium

---------- Post added at 11:36 AM ---------- Previous post was at 11:22 AM ----------

Maybe cause r361 introduced more smoothness and so quite more heating is normal..i don't know

Inviato dal mio Galaxy Nexus usando xda premium
[Samsung Galaxy Nexus] aimcr7:
I guess its android system and android OS, its normal
[Samsung Galaxy Nexus] osm0sis:
How hot? Give us a number.

Have you tried toggling it in settings to make sure it's set correctly? Change it to off when in deep sleep then back to always on.
[Samsung Galaxy Nexus] The Gingerbread Man:
I bet 37 degrees haha About that WiFi turning off and on, isn't that to do with how the built in WiFi optimisation works?
[Samsung Galaxy Nexus] itasoulas:
Anyone still thinks that 348 is the best of all nightlies so far for 4.2?
[Samsung Galaxy Nexus] osm0sis:
Not really how it's supposed to work.. Or at least it doesn't for me and I have it enabled. Either way messing with that option would be my next step if toggling didn't work. :good:

r361 is the new lightning fast 'reference' kernel.
[Samsung Galaxy Nexus] vlc_marcos:
people could you tell me what speeds are you using and gov.
[Samsung Galaxy Nexus] The Gingerbread Man:
I had it happen a few times my self but just figured that's how it was meant to be when the WiFi driver dropped to low power mode. I took your advice any way on both my gnex and n7 so will see how it plays out :):thumbup:
[Samsung Galaxy Nexus] Angelakaro:
Again ,thanked instead of quote,sorry for that. (I'm using xda app)

However,you can check my signature,i have a text file on dropbox with all my settings

Inviato dal mio Galaxy Nexus usando xda premium

---------- Post added at 02:22 PM ---------- Previous post was at 02:15 PM ----------

I think who's maintaining the xda app have to introduce a confirmation before thanks someone lol i promise i'll pay attention next time :angel:

Inviato dal mio Galaxy Nexus usando xda premium
[Samsung Galaxy Nexus] --__LoRiS__--:
Good battery life here on 361! Thanks franco! I'm using Westwood and row with facebook notification disabled
[Samsung Galaxy Nexus] Khrushy:
I keep switching back between row and deadline. Both are great, but in different ways. Deadline seems to be the better all-rounder though. Row seems good for media consumption and definitely makes scrolling in some apps smoother for me.

Re: contacts. I don't have any lag like that. What ROM?
[Samsung Galaxy Nexus] Sveke:
Been rocking 361 for about 3 or 4 days now.

I have absolutely zero issues, rock solid, stable, fast as ****, epic.

ROW is the new standard.

For all that are having issues, its your fault, the kernel is amazing.
[Samsung Galaxy Nexus] siealex:
This behavior also depends on production date. Phones manufactured Aug. 2012 and later have different hardware.
[Samsung Galaxy Nexus] vrehenriqu:
Hi!

I’m not crazy about benchmarks but I’m finding an issue that led me to run some tests.

I’ve tested this behavior in two different roms (Xylon 15 and Slim Bean 4.2.1 Beta 2) and happen on both.

I use a small bench apk called Benchmark & Tuning as a fast speed assessment. Runned also Quadrant to double check and results are the same

1. Running Franco r361 on Slim Bean 4.2.1 beta 2

2. 1st time it boots the phone flies. Under Fku, just setup Max freq to 1305Mhz. All other settings remain stock. The frequency value sticks on the screen. All ok

3. Runned benchmarks that scored around 25000 on Bench & tuning and 3300 on quadrant

4. Reboot phone

5. Under Fku, just setup Max freq to 1305Mhz. All other settings remain stock. The frequency value won’t stick on the screen… which is strange

6. Running benchmarks it scores around 17000 on Bench & tuning and 2750 on quadrant

7. From quadrant bench results breakdown I can see I/O performance cut by half

The only way I find to have the phone with the original/correct performance is to clear fku cache/data and reboot.

Could it be something wrong with fku apk or even the r361 kernel?

Other than that, everything great! This kernel rocks!

PS: didn’t try with other kernel version
[Samsung Galaxy Nexus] dandyqb:
hope this will run on franco kernel when released next month :)

http://www.theinquirer.net/inquirer/news/2235310/ces-ubuntu-coming-to-the-samsung-galaxy-nexus-next-month
[Samsung Galaxy Nexus] allgsmnetwork:
Rom for you is due to the high temperatures?
[Samsung Galaxy Nexus] Lostpick:
+1, I had no problems with r358

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] siealex:
Try to test 1305 MHz at +16°C or less, 1420 MHz at 0°C.
[Samsung Galaxy Nexus] joaquinf:
I don't know but, I have no clue about what these guys are talking about. Just saying
[Samsung Galaxy Nexus] asder00:
I've got problem with bluetooth connecting to my car with the latest release.

When connected to the car for the first time everything is ok but when I go away and return to the car the bluetooth doesn't connect and when i try to deactivate it stuck on deactivation and i have to restart the phone....

Didnt try with previous release..... Franco can you investigate????

Everything else is very good many thx for your work!!!

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] Fenvarien:
+1

The ignore list is a handy utility - or take it as the comedian part of xda and don't even try to understand their conversation... ;)
[Samsung Galaxy Nexus] The Gingerbread Man:
Which country would you suggest to achieve this temperatures?':rolleyes:

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] cschmitt:
Personally, I do all of my CPU benchmarking at -273.15°C...
[Samsung Galaxy Nexus] siealex:
Ukraine ;)
[Samsung Galaxy Nexus] Sveke:
Anyone not on 361 is crazy. Row scheduler alone is so worth it.

Trust.
[Samsung Galaxy Nexus] vrehenriqu:
deleted
[Samsung Galaxy Nexus] joaquinf:
The bluetooth on 4.2.x is crap. I had to revert to 4.1 on my nexus 7 to get decent bluetooth audio playback. Some issues has been reported for mako and maguro running 4.2.x too.

Let's wait and see if franco can give us a light on this. Blame google not the kernel
[Samsung Galaxy Nexus] The Gingerbread Man:
Which time of day, humity and period of the lunar cycle give best results?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Empty Hand:
Wait, does that make a difference?!? ;)
[Samsung Galaxy Nexus] The Gingerbread Man:
More so then doing the rain dance naked but wearing a cat mask in the garden in the snow at night twice clock wise then thrise anti clock wise.

I was able to under volt 192mhz to 6mv this was at 40 degrees amibient heat

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] yellowdie:
LOL. Freakin' XDA won't let me thank your post thrise.
[Samsung Galaxy Nexus] joaquinf:
LMFAO

No worries, got you covered ;)
[Samsung Galaxy Nexus] The Gingerbread Man:
Inspired by chainsfire or chainsdd, the quoted post in Francos sig with my on twist on it ;)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] yellowdie:
Yep, I actually recognized the base of it as that. That's what made me laugh so hard. That, and the truth behind it. :p
[Samsung Galaxy Nexus] UK_Wildcats_Fans:
+1 I often have to turn bt off and back on every time I use them in order to get some devices to connect. I agree that it isn't the kernel
[Samsung Galaxy Nexus] sparkdroid:
These quotes were from October 20, 2012:

Has OTG charging already been merged into the latest nightly?

I have an OTG Y-cable on order at the moment (otherwise I would just try it)

Awesome kernel... I'm having no issues at all!
[Samsung Galaxy Nexus] neo-X:
Same problem here. Extremely annoying. ******* Google

Galaxy Nexus MiNCO
[Samsung Galaxy Nexus] whitedragonz83:
I like ROW a lot, but on a few apps when scrolling deadline is vastly better. I think I will just keep deadline overall.
[Samsung Galaxy Nexus] Vikram Menon:
Small question

Hi, How can we find the production date of the phone then?
[Samsung Galaxy Nexus] garuhhh:
I'm running 361 currently, and am very impressed with its smoothness! smoother than stock kernel definitely! I'm running all stock ROM, and default fKU settings, no UV.

But one concern I have is that after running a few days (3 days maybe), I needed to restart the phone, or else almost everything starts to get killed, even the Launcher gets killed after putting 2 apps in foreground. I'm not sure though if this is kernel related, but I don't remember this happening on previous kernel versions. But even if this is happening, the phone is still over all smooth! problem starts when switching to other apps, they need to be refreshed or restarted (again, including Launcher).

I have a few apps always running in the background (skype, whatsapp, yahoomail, g+, facebook, hd widgets, gTalk). One thing I haven't tried is running a memory manager app, and killing all apps after experiencing the "automatic killing of apps". I'll update once I experience this again. I just restarted my phone yesterday.

Anyone having similar issues?
[Samsung Galaxy Nexus] Schneewitzchen:
Hi everyone,

does someone uses wifi on 5ghz band with a galaxy nexus without troubles?

my phone connects to my wifi network without trouble but the data rate is really worse. Also the site loading speed is really bad. It seems that the connection pauses 5 - 10 seconds and then the website is loaded. This happens every time when you open a link or a new website.

On the 2.4ghz band there's no problem but there are to many interferring networks around mine so that the n-standard is reduced to a g-standard.
[Samsung Galaxy Nexus] sam razzy:
Hey fransisco I'm one of your greatest fan in this world.. I just loved your kernel when I was using optimus p500 .. I just miss it.. cos I sold ma optimus.. now I miss u guys also..

Now I'm using HTC HD 2 fone.. Thanks a lot for your great contribution and effort toward us...

I will include u in my prayer for your success in your life.. hope you will do a great day... Thank you once again
[Samsung Galaxy Nexus] akellar:
It is if he ever actually wants to use maps.
[Samsung Galaxy Nexus] Vangelis13:
Post of the year! ;-)
[Samsung Galaxy Nexus] Vangelis13:
This is off topic anyway, but, I find it quite easy to freeze / unfreeze things. I prefer 5-6 clicks than an issue.
[Samsung Galaxy Nexus] sishgupta:
lol sorry I was in a rush and on the mobile app

Here's the end of my last kmsg hopefully it will help with determining the cause of my kernel panic.

http://db.tt/K9lqQ5Yu
[Samsung Galaxy Nexus] ellesshoo:
I can assure those with init.d issues that it's not a kernel issue. Just put your properly formatted script in the init.d folder and although I haven't checked if there are certain file naming requirements just stick with the convention of the scripts that already exist (number, followed by all lowercase with no spaces or strange characters). Probably want to set the permissions the same as well, which is user: read/write/execute... group: read/execute... other: read/execute... which is chmod 755.

This is my CPU script (named "90cpu"):

#!/system/bin/sh

echo 350 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq

echo 1200 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

echo interactive > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

Fyi, I'm on AOKP milestone 2 and Franco kernel #13.
[Samsung Galaxy Nexus] eriksengh:
It´s working

Hi Franco. Turned out to be ROM problem indeed. Flashed AOKP Milestone 2 and it now works flawless (Kernel update app that is) :D

Again thank you for developing this amazing kernel for us all.

Might add that I formatted data, cache and dalvik before flashing new ROM.
[Samsung Galaxy Nexus] Felixpau86:
Don't know if this is a rom or kernel issue but when the screen turns off my streaming radio stutters... its fine when I turn on my screen but goes back to stuttering when its off. Any settings to help me out?
[Samsung Galaxy Nexus] pa.pn2:
absolutly lol
[Samsung Galaxy Nexus] bradm23:
Franco, are u planning on releasing a 13.1 or 14 with the omap fixes you found for battery? :-)
[Samsung Galaxy Nexus] Stretlow:
Same...............
[Samsung Galaxy Nexus] slg60:
Please in next Kernel a bulit in GPU OC possibility by your App! This would make the Kernel perfect!
[Samsung Galaxy Nexus] minooch:
The current OC for the GPU provides no improvements to performance - no point at the moment - just eats more battery for no gain
[Samsung Galaxy Nexus] AdrianE46:
I can't, for the life of me, figure this out. I've tried aokp milestone 2 with franco #12 and aokp 19 with franco #12 and #13, the best I could get was 9 hours battery time of which 3 hours are screen time. Did a full wipe before each flash, too. I was expecting more standby time, even with 3 hours of screen time. Am I expecting too much or is something wrong? I've also noticed a lot of activity from something called kworker (about 5 of them) in better battery stats. Can someone please enlighten me?
[Samsung Galaxy Nexus] leshake:
That actually sounds reasonable. Do you mean the phone powers off after that length or you get a battery warning. I'm using the latest kernel with AOKP milestone 2 holding at 63% with 8+hrs battery life and 1hr6min screen time. Take into account the last 45 mins of screen on time has been constant as I just got off work. With the screen on a full 3 hrs used throughout the day I'd say that is very reasonable.
[Samsung Galaxy Nexus] sluflyer06:
3 hours of screen on is crazy high usuage. No work or school? :p Even when I'm playing constantly on my phone all day I usually top out around 1.5-2 at most. Try a day with more average use like 1h-1.5 and see what happens. Also how much are you losing when the phone is sleeping, like overnight?

Couple of factors that are huge.

A. Are you on a LTE GN?

B. If your hanging out somewhere where signal is low you'll blow thru battery at a high rate

C. Are you playing alot of games? Games just annihilate the battery.
[Samsung Galaxy Nexus] ChongoDroid:
Im getting about 16- 18 hours of up time with 4 of those having the screen on at about 30%

sent from my googletron
[Samsung Galaxy Nexus] sishgupta:
You are definitely hitting the near limit at 3 hours of screen on. I get about 4 tops.
[Samsung Galaxy Nexus] MarcLandis:
The kworker threads are from K9-Email.

Marc
[Samsung Galaxy Nexus] AdrianE46:
Well, i actually don't have a home pc atm and i use my phone as a subsitute for that + i use my phone for collage a lot because of a very usefull app.

So 5-6 hours of standby in addition to the 3 hours screen time is normal? I was expecting more, maybe along the lines of 10, especially since i have a gsm phone with auto brightness and do pretty much no gaming whatsoever, just stuff that requires internet access. Also i have the power saver option of aokp enabled and set to keep only 2g on while screen is off. I also undervolted by 50v in each cattegory.

I get a drain of about 14-16% over 6-7 hours of standby over night.
[Samsung Galaxy Nexus] Khizar:
you could have searched, there is a thread in the general section... here is a link

http://xdaforums.com/showthread.php?t=1519606
[Samsung Galaxy Nexus] rohan.binny.arora:
Thanks for the reply.

Hmmm...i'm also planning to do that for more extensive testing. Will report results here - qualitative of course. Is there any way to quantify the performance that the two deliver? I'll be happy to run those and help out in the little way i can... :cyclops:

About the lag - i'm on stock 4.2.1 but have seen the lag ever since ICS. See if you can replicate it this way - reboot the phone (or just close the phone app if its open), open the phone app and swipe to the right-most page (which has the favorite contacts) - The photos take a couple of seconds to load. I first see the grey, generic icon which is subsequently replaced by the photo. Of course i have hi-res photos synced so you'll need to do that as well.

---------- Post added at 03:39 PM ---------- Previous post was at 03:15 PM ----------

+1... have been facing bluetooth connection issues ever since 4.2 OTA. Went over to the radios thread and there people said that it was an issue with how the kernel controls it (which is how i discovered this thread and have r361 now :victory:)

Anyways, searched around a bit for this issue and found this... http://xdaforums.com/showthread.php?t=2065962

I checked the file on my /system/ and the permissions originally were exactly how the OP mentions they should be and yet i was having issues with frequent disconnections. So, in a nutshell, didnt work for me but has for some others. You can try this - maybe it'll work for you.
[Samsung Galaxy Nexus] siealex:
5 GHz on nexus is not recommended at all - the wifi chip often burns itself on this band.
[Samsung Galaxy Nexus] razvanultra:
I had no problem with 5GHz band, the router it's in the same room with the phone :) but i'm not using at this frequency, only for testing.
[Samsung Galaxy Nexus] whitedragonz83:
Screenshot of something you should like Franco.

Feels great!
[Samsung Galaxy Nexus] malaroth:
Search play store for eMMC and download the brick bug checker. It will tell you your phone manufacture

JBSourcery 4.1 Franco 361 FTW! Keep the Magic alive!

---------- Post added at 01:24 PM ---------- Previous post was at 01:20 PM ----------

By the way... I've noticed several posts stating that they are not UV.... it is not possible to UV on 361, the voltages are hardcoded and therefore NOT changeable. It's cut down on a lot of complaints about reboot SOD and other silly stuff

JBSourcery 4.1 Franco 361 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] nuwan32:
Uhh no.. a nexus is supposed to and can handle 5ghz easily. I've used it extensively with no problems whatsoever.

And to the person that said it's slower, it's definitely your router or your phone because on my phone using 5ghz vs 2.4ghz is much faster due to no interference as I live in a pretty crowded area l. Just try restarting your router and/or phone and maybe even flashing a different modem?
[Samsung Galaxy Nexus] osm0sis:
We'll see how much was dumbassed UVing if Franco lets us UV again in the future. We definitely know these new fixed Interactive patches from Todd at Google are solid as hell though, since Todd was finally able to reproduce the slow-down + SOD with his own device and correct his earlier patches. :good:
[Samsung Galaxy Nexus] yellowdie:
Yep. Patched patches are great! And speakin' of unbreaking broken junk, looks like Franco's inside source is right: http://www.engadget.com/2013/01/11/android-4-2-2-supposedly-shipping-with-new-nexus-4-units. Let's just hope Google gives Franco and the other Devs some good solid stuff to work with!

:):D:laugh::good:
[Samsung Galaxy Nexus] UK_Wildcats_Fans:
What is the source of this? I have been using the 5G on my Gnex since it was first released without any problems. I believe that the Gnex uses the BCM4330 wifi chipset that is capable with 5G and used in the SGS2 and iPhone 4S.

Datasheet

https://www.bluetooth.org/tpg/RefNotes/4330-PB10X-R1.pdf
[Samsung Galaxy Nexus] malaroth:
This would be a pretty good time to fix stuff but something tells me we won't see a major change till the world mobile conference in March...

And I would have caught that article but having an AOL app on my phone just creeps me out :P :laugh:

JBSourcery 4.1 Franco 361 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] Williamsss:
I just flashed the latest nightly 361 I think, on Toro, On Jellybeer (CM10 Base) and after flashing I could not conect to Data or Wifi no matter what I tried. I wiped everything and reflashed and even when i relfashed a different kernel I could not connect. I had to Completely wipe and reflash the Rom. Is there anyway to get franco kernel working with the internet?
[Samsung Galaxy Nexus] joaquinf:
CM10 is based on android 4.1 if i'm not mistaken. You'll need a cm 10.1 ROM because the kernel you are trying to flash is made for 4.2.x ROM's
[Samsung Galaxy Nexus] Williamsss:
Yea hahaha your right CM10.1 Sorry. Still The wifi and data work on every other kernel, expect this one. Is there a known solution for this issue?
[Samsung Galaxy Nexus] joaquinf:
So, are you flashing a 4.1.x or a 4.2.x rom? my wifi and data are working just fine
[Samsung Galaxy Nexus] malaroth:
Certain privileged people are testing different densities of tinfoil hats with copper wiring circling into an antenna....

JBSourcery 4.1 Franco 361 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] creeve4:
What's up with input_boost in r361? Has it been hardcoded or temporarily disabled?
[Samsung Galaxy Nexus] Williamsss:
Hahaha you guys are funny. I am on 4.2.1. I flashed the kernel with the franco updater app then when i found out the data wasnt working I flashed back to Zen. Then data still wasnt working so I put franco kernel boot.img in the Rom and I wiped and flashed the rom with franco in it. Data still wasnt working so I wiped again and flashed the normal rom with the CM10.1 kernel. Data was working fine after that, but I didnt have the franco kernel.

And by data I mean it would say it was "connected" but when i went to the browser or any app that used the internet, I wouldnt be able to connect to the internet, whether on wifi or data. And the bars up top would not turn blue, (they only stayed grey)
[Samsung Galaxy Nexus] malaroth:
Usually the bars not turning blue is a gapps issue not syncing but you should still be able to get data

JBSourcery 4.1 Franco 361 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] UK_Wildcats_Fans:
I had a similar problem, but it turned out to be an issue with the gapps that I flashed to get initially working. If I have this problem after it had been working, I can usually turn Wifi Off, leave off for about 30-60 seconds, and turn it back on. In rare cases, I have to reboot to get it working (maybe multiple times).
[Samsung Galaxy Nexus] Empty Hand:
I decided to try a new rom and when going to set up my colors through Osm0sis's init.d method, I noticed I have no more init.d folder in system/etc. Should I just create a new one, or is this a sign of a problem? Thanks!
[Samsung Galaxy Nexus] joaquinf:
It should be under /etc/ not /system/etc/ If you don't have it you can just create it and put whatever script you want to run
[Samsung Galaxy Nexus] creeve4:
I ask because the option to change input_boost_freq in the app is greyed out...
[Samsung Galaxy Nexus] siealex:
Usually /etc is a sym-link to /system/etc.
[Samsung Galaxy Nexus] joaquinf:
And what does it says under input_boost?
[Samsung Galaxy Nexus] yellowdie:
Yes, it is temporarily disabled. Franco's workin' on stuff and wanted to take that variable out of the equation.
[Samsung Galaxy Nexus] Empty Hand:
One more question. Should the init.d folder I create have any particular permissions? I know the permissions for the color setting file. Thank you again!
[Samsung Galaxy Nexus] joaquinf:
Give it 755 (drwxr-xr-x) and should be fine
[Samsung Galaxy Nexus] malaroth:
Wow! I didn't believe it would make that big of a difference but I changed osm0sis's initi.d color script to Franco colors and it's waaay more crisp and sharp. Nice one osm0sis!

JBSourcery 4.1 Franco 361 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] neo-X:
Where can i find osmosis init.d file?

Better yet, could you PM your file?
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -> 4.2 | r300 -> 4.1

Right here

http://xdaforums.com/showpost.php?p=34951507

If you look in your init.d script you'll see 01blah 02blah on up each one setting the sequence to be run at. Hence setting the file to 900colorsettings so it runs at the end of the init.d but before total boot

This is what it looks like (for those who don't already know)

JBSourcery 4.1 Franco 361 FTW! Keep the Magic alive!