yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] rene_r:
You can download the 172 from here:

http://xdaforums.com/showthread.php?t=1367341&page=1738

br

rene_r
[Samsung Galaxy Nexus] ranasrule:
are gamma setting also fixed in this build ?

---------- Post added at 11:27 AM ---------- Previous post was at 11:26 AM ----------

this is a known issue....dev is working to fix it in next nightly
[Samsung Galaxy Nexus] jnr21:
I don't think so, but i'm not sure, there's no changelog as this is just test kernel.
[Samsung Galaxy Nexus] rene_r:
No, has not been fixed in this build.
[Samsung Galaxy Nexus] do0b:
newb here and i got some questions:

- i just updated my franco app, now with different power modes, will i put it on full-power, the app crashes. anyone else getting that?

- does CPU 1 go offline when screen is off with the new update?
[Samsung Galaxy Nexus] drawde40599:
I hate the coloring of this.screen no matter what i do, but after months of messing with this is what looks best to me

200

200

200

-4

0

5

Manually change gamma to 4 ( root explorer)

Then blue setting on voodoo color at 75% brightness what i run all day
[Samsung Galaxy Nexus] johno168:
Well thats pretty much franco's recommended set up. I'm guessing you dont have the app.
[Samsung Galaxy Nexus] Lambetts:
Hey

Its all good man, chill! Haha.

I've bought your app and was just conversing with others that have the same ideas/thoughts etc. :-)

Ezekel must just have a magic wand huh?

Haha.
[Samsung Galaxy Nexus] ranasrule:
great settings....just tried them
[Samsung Galaxy Nexus] ke_be:
512MHz gpu is safe? I need it if I don't play games? Is there a noticeable difference between 512 and 384 for battery?
[Samsung Galaxy Nexus] drawde40599:
The question should be do u have the app cause there not pretty much his settings?? And ya actually I bought it 2x; ) thanks!!
[Samsung Galaxy Nexus] ch33kybutt:
It's practically impossible to fix a problem which you can't see for yourself, so what might help franco is if those who experience signal drops monitor their radio buffer logcat, i.e. run aLogcat > settings > preferences > buffer > radio.

Look for specific errors which occur when signal is lost.
[Samsung Galaxy Nexus] metalspring:
Or simply

su

logcat-b radio > radio.log

should work, right? (Can't tell since I have logcat disabled, I know its something like that though)
[Samsung Galaxy Nexus] frigidazzi:
Same question. Does CPU 1 go off with screen off always now since there's no more generic hot plug setting regardless of governor?

Mine crashes with power mode too, but settings are still applied.
[Samsung Galaxy Nexus] jackie_jagger:
quick question, first time flashing this kernel - I am on Android Revolution ROM and I'll be flashing this kernel in a while - latest milestone and I'll be flashing it in CWM, right?

Another question, the settings everyone is talking about - how exactly do you use them? is there a GUI or something (I am guessing it can only be done with the franco kernel updater app)

and lastly, thank you everyone who ever has put in the effort to make our phones better.

Cheers
[Samsung Galaxy Nexus] metalspring:
Easiest way is via the app, but all the settings (besides the built in power mode profiles and "non kernel" tweaks like sqlite defragmenting) do have an actual file path but you'd need to make an init.d script to have them stick on boot
[Samsung Galaxy Nexus] ch33kybutt:
Yep, that's right. But there's a space between logcat & -b

$ su
# logcat -b radio > /sdcard/radio.log
[Samsung Galaxy Nexus] jackie_jagger:
Sadly I can't access the app right now - I am out of country in a place where I cannot buy apps. So I reckon I have to flash via CWM right?
[Samsung Galaxy Nexus] drawde40599:
If u have the app u can download and install from the app, if u don't have the app u can download kernel from page 1 of this thread , and install threw recovery or clockwork ...if u have never used this kernel I'd recommend not touching ANY settings ( besides color: ) ) just run stock for few days get the feel so u have something to compare to when you do start tweaking it ....GPU maybe what u mean? There are 2 experimental builds called nightlys they have a GPU over clock of 384 or 512 if u try them I'd recommend 384 first, agn so u have something to compare to .

I've been using this kernel since be4 Franco even had the phone and stock has always got me best results
[Samsung Galaxy Nexus] Antob125:
Test build Franco released

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Basian Mile:
Where can find the File that i need to change it manually?
[Samsung Galaxy Nexus] metalspring:
Even the app on Android pit?
[Samsung Galaxy Nexus] zenzip:
r169 on AOKP b37 with XXLA2

- some datadrop

- OMAP4 Gamma interface doesn't work

- Colors Multipliers reset on boot
[Samsung Galaxy Nexus] chrispo:
I have the feeling some people reporting datadrops do not know what it is anyway (as do I btw) . It is not simply the bars going gray, is it? Can someone describe how to spot those?

Chris
[Samsung Galaxy Nexus] schizophrenia:
ok, for anyone who does not know what is "Data drop"

as explained earlier

http://xdaforums.com/showpost.php?p=26634974&postcount=17234
[Samsung Galaxy Nexus] Dave778:
Hi Franco, ever since like 2 or 3 nightlies ago I have been losing network. Eg if I go into an underground parking lot & then come out the signal doesn't come back 25 percent of the time. Getting datadrops. Have to toggle airplane mode or reboot to get network back. Am loving this kernel otherwise.

Am using AOKP B37 w 169-384 Kernel & UGLC1 radio.
[Samsung Galaxy Nexus] navodwickra:
did you try the test kernel which was posted few pages back?
[Samsung Galaxy Nexus] chrispo:
Detecting data drops

My question was more like: "How can I see if there has been data drops". Should I check the battery graph (more specifically: phone signal bar not being green?) or are there other ways to detect data drops?

Chris
[Samsung Galaxy Nexus] jnr21:
I've made tasker script which alerts and notify if there is signal drop, it also set airplane mode on and then off and then you have signal again. It also write all alerts to log file.

But it works only if whole network disconnect, not only data connection.
[Samsung Galaxy Nexus] rene_r:
You can also use the free app no signal alert. Br
[Samsung Galaxy Nexus] schizophrenia:
data drop? then you lose the 3G, H+, 2G whatever icons. simple as that
[Samsung Galaxy Nexus] rene_r:
@Franco:

Testing your unofficial 172 build for about 9 hours and hadn't any data/signal drop.

Using XXLA2(rom) and matching RIL.

Hopefully I won't get an data/signal drop as soon as I post this ;)

Will report back as soon as drop occurs or in 2-3 days if everything is working fine!

Franco could you tell me what you have changed in your kernel(regarding data/signal) drop I'm interested in the technical part.

br

rene_r
[Samsung Galaxy Nexus] jnr21:
I previously used it but it doesn't return signal, only alerts if signal dropped.
[Samsung Galaxy Nexus] Hanny:
he will tell when the testing is complete ;) this is to prevent any placebo but literally honest reports from testers

by the way i have a short report here:

i flashed 172 about 10 hours ago

had no drops at my home (which has ~2 drops per day before)

then i went out, my journey was

HOME->TRAVEL->SPOT A->SPOT B->SPOT A->TRAVEL->HOME

on the whole journey i had NO drops EXCEPT SPOT A. yes - both going there and coming back i had 2 SIGNAL (whole bar gone with an X) drops when i arrived spot A for 2 times. (both auto reconnects in 20sec)

i seriously dont know whether this is a coincidence or not, otherwise it would be my regional reception problem.

however:

the accuracy of SPOT A is 10m x 10m (thats exactly the same turn right corner of a road :eek:) is an open outdoor area, not mall not lift not indoor, and can see the sky clearly

which i makes me feel sad that it may because of other factors instead of reception/carrier.

thanks to the member whom reminded us about logcat and surely i will focus on that immediately and send it to franco if it seems useful.

thank you for your time reading! was trying to tell every single observation i have :)
[Samsung Galaxy Nexus] rene_r:
Maybe it helps Franco if you append your logcat file (1. open shell, type su press enter, type logcat -b radio > /sdcard/radio.log and press enter)

br

rene_r
[Samsung Galaxy Nexus] zellroot:
Stock rom M3 never data drops.........AOKP M5 Franco M3 never data drops.......maybe guys need to use the developers stable mods and grade those instead of flashing 3 kernels and 4 roms per week......I personally prefer stability and you?
[Samsung Galaxy Nexus] apratomo:
All about chase for perfection my good sir.
[Samsung Galaxy Nexus] metalspring:
Great idea except if everyone did that then there would be no further development, there would be no aokp m6 and no Franco kernel m4, for that matter there never would have even been an aokp m5 or franco m3, we'd all still be on aokp m1 and franco m1...staying only on the "stable" builds of everything would cause all development to stagnate and die...

I personally prefer progress rather than 100% stable and stagnant...
[Samsung Galaxy Nexus] randommmm:
a misspell at OP, I wonder why nobody found it before, should be

"/v1_offset"

without the S in the very end:D
[Samsung Galaxy Nexus] BigBake88:
Yes, the system shuts down a core, if it feels it can do it safely. So, there is no reason to have a generic hotplug.
[Samsung Galaxy Nexus] franciscofranco:
r173

* OMAP Gamma settings works again

* Color Multiplier won't turn the screen green if we set all the entries to >240 anymore

* voltage.h: increase VDDMIN from 800mV to stock 830mV to reduce the chance of data loss

* opp4xxx_data.c: add a new OPP core entry for OPP25 to fight the recent surge of data losses. Also increase 192mhz slot nominal voltage to 900mV from 820mV. Smartreflex still calibrates it to 840mV, but at least we're sure the data losses are not due to extreme nominal undervolt
[Samsung Galaxy Nexus] Flukester69:
Instantly using 173, haven't had a data drop yet. Still advise people get and use getRIL app and make sure your radio etc is working properly.
[Samsung Galaxy Nexus] gparmar76:
Never did I think I would be anticipating new kernel releases as much as I do for Franco's nightlies....great work and it just keeps getting better...I read that the audio volume bug was fixed...I can't wait to install the new one because that was the one thing that I have been waiting for...I'm always rocking away on the Westone 3s with volume jacked further to +3 and a text message or email would always ruin it :(

Also, I read that for others the multipliers are sticking after rebooting?? I have always had to redo the multipliers and OMAP gamma...lately I've just been using Android Revolution...is this a ROM issue?

Anyway, great work Franco...I'm very appreciative and am thinking your getting close to another milestone release ;)
[Samsung Galaxy Nexus] franciscofranco:
Yep, couldn't agree more.
[Samsung Galaxy Nexus] spaceman860:
Is this the same as 172

Sent from my Gnex {GSM}
[Samsung Galaxy Nexus] franciscofranco:
No, on r172 it didn't have Gamma and Color ****s fixed.
[Samsung Galaxy Nexus] Flukester69:
Thanks by the way! :D
[Samsung Galaxy Nexus] vomer:
Thanks franco.

Edit: connection drop happened again on this. Gonna try get you a log but gotta search for the terminal command first.
[Samsung Galaxy Nexus] franciscofranco:
Yes definitely. Milestone 4 will have a surprise though. Since we can run 384mhz GPU in the same OPP as 307mhz (the issue Colin Cross talked about was the higher battery usage when using OPP3 for higher GPU clocks than stock 307mhz) I'd rather have people happy with the extra 77mhz while still running in the same "power trail".

You're the first one to encounter data loss with this kernel (r172 already had the same voltage/OPP fixes as r173). Get GetRil and check for mismatch.
[Samsung Galaxy Nexus] rene_r:
Also got a drop with r172, after 9 hours usage. No baseband mismatch!! Min CPU 729, Max CPU 1228, interactive governor, sr enabled, nothing else changed. Btw using your app
[Samsung Galaxy Nexus] Bram77:
I've had connection problems with my Gnex since the day I have it. I'm pretty sure it has to do with the location I live (in a small village) but I've never had this problem with my previous phone (a Desire HD).

Is there any option in de Franco app that I can ajust to improve the signal strength, even if it's costs extra battery? Losing the connection halfway a conversation is driving me crazy!
[Samsung Galaxy Nexus] leos0000:
Work nice on Xperia Rom :D so fast r173
[Samsung Galaxy Nexus] franciscofranco:
Sorry theres nothing else I can do. We all know Google is aware of this problem, so we have to wait until they fix it for real. As for me, I don't have anything else I can add/change to fix the bug.
[Samsung Galaxy Nexus] Bram77:
Thanks for clarifying Francisco :)
[Samsung Galaxy Nexus] wingsiw:
A little question about getRIL. I'm using AOPK 37 + Franco 173 + UGLA4 baseband / RIL of XXLA2. getRIL notified of the mismatch. When select & download the RIL for UGLA4... I got the message installed successful. But when I reload getRIL, it still tell me I got a mismatch... the RIL still the one for XXLA2??? The only way for me to have match baseband/RIL is to flash my phone with the XXLA2 baseband. But UGLA4 give me a better signal! It's possible to keep UGLA4 and apply to good RIL to it? Thank you in advanced!

And btw, FRANCO is the King! Best Kernel ever! It completely change/boost my Gnex performance!!! Thank you again!
[Samsung Galaxy Nexus] duowing:
I actually use the UGLC1 radio, but I also have the mismatch that says to use XXLA2. I believe the UGLA/LC radios are developed to work off that RIL, but they are just made for different regions. I think getRIL is just saying that they are mismatched simply because of the name. I don't think there's actually any problem with that radio/RIL combo. If there was I would think you'd be having a lot more problems
[Samsung Galaxy Nexus] vomer:
I have this same problem. I am running UGLC1 BaseBand and it says I have XXLA2 RIL. I have never flashed that baseband before so not sure why? They do not have a UGLC1 RIL listed and I tried installing the UGLA4 RIL but it does nothing even though it says installed.
[Samsung Galaxy Nexus] iGoogleNexus:
=] no problems here .. no data drops

:D happeh

- Google
[Samsung Galaxy Nexus] nikulogical:
Went from r166 to r173 and just got a data drop.hopefully its just a fluke.
[Samsung Galaxy Nexus] wingsiw:
Thanks for the answer! The reason why I asked how to match my baseband/RIL is because many users & Franco said that may be the cause for data drop. And I encountered few data drops since kernel 165.
[Samsung Galaxy Nexus] sparkdroid:
My phone has been very stable in the past with no data drops. I have been using LiquidSmooth as my only ROM from 1.25 all the way to 1.4. I have also been only using the Franco Kernel updating with each nightly build and running 512 GPU with no issues.

I had my first data drop this past Saturday. I think I was on r166 and rebooting fixed the problem. Then I noticed my second data drop this morning when I woke up at 8am (it happened some time after 1am). I tried rebooting and this did not fix it. I tried toggling data and airplane mode to no avail. I flashed back to r162-512 and this did not fix it. I flashed r166-512 and this did not fix it. I returned to r169-512 since previous versions were not fixing the problem. Data came back shortly after 9am when I was on my way to work (I don't know if switching cell towers triggered the data to re-activate or not).

I saved logcat files using the app "Catlog" while I was on r162. Then again once I booted to r166 and once more when booted into r169. I have attached them in the hopes there is something useful in them. If there is any way to provide more useful output for you to investigate, let me know.

I also have Getril which shows I have a mismatch however, there is no matching RIL for my baseband (UGLC1). Several days ago, I tried flashing UGLA4 hoping that Getril would download and install the matching RIL but it wouldn't. It always seems to recommend XXLA2. It wouldn't even install the UGLA4 RIL when I had that baseband installed and chose the matching RIL from the dropdown box. Since I couldn't get a matching configuration, I returned to the configuration shown in the screenshot.

I hope there is something useful in all this. I am currently trying r173-512 as of about 10am this morning so I'll let you know if I experience any more drops.
[Samsung Galaxy Nexus] vomer:
Update: after that initial data drop things seem to be back to normal for now. It was very strange as I had no data connection even after a restart but it came back to life after I left the phone alone for a bit.

Let's hope things are fixed! :p
[Samsung Galaxy Nexus] iGoogleNexus:
=] guessing I'm good

- Google
[Samsung Galaxy Nexus] swaser18t:
I too have lc1 and I installed the ril it recommended and right away after I turned the screen back on I have signal loss
[Samsung Galaxy Nexus] nikulogical:
Who's getting data drops and have their radio/rils matched?
[Samsung Galaxy Nexus] rogersnm:
I'm on AOKP M5, Kernel r169, Baseband XXLA2 with matching RIL.

I've used every single official r16* (384) build and haven't had a single data drop on any of them, maybe I'm just lucky? :confused:

Anyway, cheers for your great work - I'm getting much better battery life :D
[Samsung Galaxy Nexus] BigBake88:
Have any CDMA guys had data drops? I have not had one.
[Samsung Galaxy Nexus] wingsiw:
The only way for me to have a matched radio/ril is to have xxla2/xxla2 installed. But I have a better reception with a mismatched ugla4/xxla2 (unable to install the ril for ugla4). Let hope r173 solved my data drop problem even with a mismatch radio/ril. Cause xxla2 is very bad for me.
[Samsung Galaxy Nexus] DarkGruf:
Never experienced any datadrops with Franco's kernel. Still I checked with getRIL and had to dl a new ril according to the application. Since then I never more had blue bars on 3G... Coming back to "non proper" ril solved the problem... So be cautious with getRIL and never fix something that works :)
[Samsung Galaxy Nexus] Hanny:
I used 3 hours to do researches about my rare SC04DOMKKD radio and found that it is causing some problems (some 900mhz radio band thing is not supported) with my carrier. I hope after I switch to XXLA2 (and they match now) will give me and you good news :)

thank you franco for your support to our data issues. thanks a lot.
[Samsung Galaxy Nexus] jnr21:
I think that 172/173 fixed signal drop issue. With 166/169 i was getting several drops/day.
[Samsung Galaxy Nexus] Benji1983:
like i say : never change a running system

i dont know what a data drop is i never got one

i installed getril (hmmm)

i got the SC04DOMKKD

with the UGLA4 ril

and this all here in tyrol (austria)

and i got 5mb down and 1 mb up the fastes so far here in the mountains

i checked and installed all radio ril combinations that seem plausible to me

guys not everytime the suggested radio in a country is the best i got the best recieption ( dont know how to write lol) with the japanese radio ^^

maybe i could helped you

greetz benji
[Samsung Galaxy Nexus] odin13:
Same here..i only got datadrops on Bugless Beast from april 6.

Since i'm running BB from the 9th i encounter no problems :cool:

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] leos0000:
I dont have data drops...r173 its the best.... Work perfect on xperia rom .... Radio kk6 eu....
[Samsung Galaxy Nexus] Zflash:
Never had data drops until I installed 169 and 173. Stock ROM. It happens when i wake up the phone. On 166 i never had this problem.
[Samsung Galaxy Nexus] wayne850:
can you guys please share your colour settings?everytime i play with my settings it get really ugly :D
[Samsung Galaxy Nexus] renna1992:
my phone also handels 172 better by far. had one single data drop since yesterday, usually i would get 2 or 3 per hour.

thanks franco, i really appreciate your work :)
[Samsung Galaxy Nexus] leos0000:
Yo bro where i can download r172 :D can u upload on dropbox
[Samsung Galaxy Nexus] kid1da:
I had data drops when I tried to match the radio and rils. My phone was working perfect without them matching. I guess I shouldn't have tried to fix what wasn't broken.
[Samsung Galaxy Nexus] Bonvaz:
Mine: 165,175,210

-4,0,5

Gamma omap 1.4(or 1.2)
[Samsung Galaxy Nexus] renna1992:
it was just a boot.img franco shared yesterday. everything that changed in 172 also changed in 173 + the color fixes so just give 173 a try, should have the same result :)
[Samsung Galaxy Nexus] The Gingerbread Man:
I had a data drop on 173 after using wifi and moving out of range from the router. Am using paranoidandroid 0.9b xxla2 radio with matching ril. I understand not much can be done as Franco said earlier but just posting my findings so far. Great to have gamma control working again now.

Sent from my Paranoid Nexus
[Samsung Galaxy Nexus] jnr21:
http://db.tt/Fp3GFfIU
[Samsung Galaxy Nexus] willl03:
Just had my signal loss on 173 after an hour... back on 160, damn I enjoyed the performance
[Samsung Galaxy Nexus] nikosrs4:
anyone having data drops, what governor do you use?

I had several drops with Lazy governor but none with Interactive and I'm using Interactive all the time but I switched to Lazy for some hours and only then I had them.
[Samsung Galaxy Nexus] craz6r:
I've seen a some people asking for sets on setting frequency's for governors, this should help understand what different governors do and how to set them. I know this is for the S2 but, it should help. There's a lot to read but, a good read.

http://xdaforums.com/showthread.php?t=1369817
[Samsung Galaxy Nexus] billouetaudrey:
I use lazy on screen off and don't have data drop...

Edit : bad information. Sorry, I use conservative on screen off...
[Samsung Galaxy Nexus] leos0000:
Thanks man ;) ... How i can flash img
[Samsung Galaxy Nexus] renna1992:
fastboot flash boot boot.img :)
[Samsung Galaxy Nexus] willl03:
Interactive 384-1344
[Samsung Galaxy Nexus] Flukester69:
I haven't had a data drop all day so far. Usually at this time of day I'd have 4 or 5.
[Samsung Galaxy Nexus] vomer:
Every time I launch Chrome and hit the search key and start to type the app freezes. Only happens on nightly not M3.

Closing the app fully and reopening makes the issue go away.

Using power save mode. Maybe a bug?
[Samsung Galaxy Nexus] schukje:
I have a noob question :) what type off franco is better the 512 or 384? And what is the difference en yes i know that the numbers are different :);)

Grtz from Holland
[Samsung Galaxy Nexus] Razer(x):
Do you set the screen off governor via setcpu?
[Samsung Galaxy Nexus] Razer(x):
Gpu overclock. My device can't handle 512 for example
[Samsung Galaxy Nexus] Theshawty:
The overclock is different. The performance isn't that much better, contrary to what most seem to think. The FPS in most games is roughly 3-5.

We cannot say what runs best for your GPU chip as all are different from each other. Some can take the massive overclock while for others they show signs of screen tear or the like.

Try them both and make up your own mind.
[Samsung Galaxy Nexus] Flukester69:
Just go 384, really makes no difference in anything. I tried 512 for many kernels, then I went 384 last 3 or 4 kernels or so and noticed absolutely nothing different but I didn't take stats, just visually, running games and apps I saw no difference.
[Samsung Galaxy Nexus] justme1988:
For some reason since the latest app update. The set CPU settings on boot and set power settings on boot won't stick....

Send from my Galaxy Nexus using Tapatalk
[Samsung Galaxy Nexus] lynxboy:
+1

I used to always go for 512, but recently switched to the 384 kernels and notice no difference in speed/performance apart from slightly improved battery life on the 384.

Regards.