yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] RayGarden:
Ok...i try again.

Re: Screencast App not working on Tegra 2/3 Device (like Gnex)

===============================================

---->>>>> off-topic

I just read a comment from someone who was explaining why anyone is capable to make "Screencast" work on a Tegra 2/3 Devices (like Gnex).

Now in this comment (see below), the person was referring to the Kernel. As you are the Kernel Whizkid here, maybe you understand the problem and maybe can solve this? Or you acknowledge the problem and confirm that there is no way to find a solution here.

************************************************** ************************************************** ************************************************** ****************

The OMAP4 has built in hardware DRM which makes the framebuffer inaccessible from software running in user space. The challenge to fix

Screencast for the GNex means breaking the hardware protection on the framebuffer (read: very difficult). We even hired OMAP consultants and

they all threw their hands up in the air. Without HEAVY kernel modifications, Screencasting on the GNex is impossible.

************************************************** ************************************************** ************************************************** ****************

Never asked, Allways missed. So maybe you have a challenge?

Thanks
[Samsung Galaxy Nexus] mikarbach:
I am on CNA-3.6 with r283 and use the default settings from Franco. Battery is very good. No problem at all.

Gesendet von meinem Nexus 7 mit Tapatalk 2
[Samsung Galaxy Nexus] franciscofranco:
CM10? Pfft...

I have no idea about that to be honest and I really don't want to waste my already limited time trying to break that DRM thing. Sorry!
[Samsung Galaxy Nexus] yellowdie:
Chances are your phone was not calibrated properly and your phone said "Hey, we have 70% battery left! yay!" And your battery said "Um, no, we only have 60% left, retard." And your phone said "oh crap, okay, droppin' my numbers like a rock to match the battery's numbers."

That's why numbers can fluctuate so much so quickly. But draining your battery all the way down, then charging it all the way up, will get the phone and battery talking on the same page, and wa la! Your battery magically lasts uber long the second time around.

:):D:laugh::good:
[Samsung Galaxy Nexus] franciscofranco:
+1000000000000000000000000000000000000000
[Samsung Galaxy Nexus] mpokwsths:
Exactly the same ROM and kernel version:

64% battery left

1h 40m screen time

All these with Interactive tuned for fairly high responsiveness: Hi_freq_speed 1.22Ghz (when over 99% load). That way all the cpu states are populated, and when needed full speed.
[Samsung Galaxy Nexus] CaspaTheGhost:
Nope, I'm part of the 729 club. Better performance and no tangible effect on battery.

This! +1

And THIS! Said it earlier in the thread when someone posted a shot of their battery going up, works both ways!

+1

It irritates me when I see those 5 min test posts. People need to realise that the biggest drains on battery are screen and signal strength and the latter is such a massive variable its means those reports are worthless.

I can only do full measured testing at the weekend when I'm at home all day with as little variants as possible.

Franco, haven't flashed the 284 test but is the change WiFi related? I had my WiFi 'stick' yesterday, as in it was on but didn't connect when I got home. Turning it on and off had no effect, it was like it was stuck in some way. Worked fine after a reboot.

I also noticed at work that my drain appeared higher than before, its switching from WiFi to mobile as I go between offices and out of range. I've actually been testing today by having WiFi off in the office.

Currently at 3% with the below shots...

View attachment 1391291

View attachment 1391293

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Neo3D:
Look here, it all depends on if you are LTE or GSM. LTE is fast but a known battery hog. My coworker got the iphone 5 and it drains worse than our phones!

http://xdaforums.com/showthread.php?t=1834634
[Samsung Galaxy Nexus] Schneewitzchen:
Got 50% battery left...till now 2h 11min screen on time, 1st battery cycle with r283

I'm on mincov4...great rom and kernel btw!
[Samsung Galaxy Nexus] Intelmaster90:
Hey Franco, your kernel works like a charm... you're a good kernel developer... I have on Question... in the OC/UV Tab There's the scaling govenor. Whats the different between interactive and dynamicInteractive. I thought that all scaling govenors are dynamically...
[Samsung Galaxy Nexus] TEK112:
That was very funny. However, I only agree with half of your post. It has been proven that completely discharging a lithium-ion battery will reduce its life. Even if you only do it a few times. That being said, the best way to calibrate the battery is to charge to 100% and then reboot to recovery and wipe battery stats.

Or conversely, you can go back to the old practice of charging up to 100% and only flashing ROMs while at 100% and on the charger.
[Samsung Galaxy Nexus] osm0sis:
While the guy talking in the comment might know what he's talking about, I believe you've misinterpretted him for the rest of his thread since a GNex is not a Tegra device in any way shape or form. And his comment was more to the point of how "it's impossible" than "anyone is capable".
[Samsung Galaxy Nexus] eug89:
A question about the app:

Is it a common issue that setting a green gamma lower than zero the screen goes all green as if the gamma was set at the highest value? I've already searched this thread about it and I've only found another user that reported the same problem setting it lower than -4. Nobody answered to him though.
[Samsung Galaxy Nexus] Empty Hand:
Ok, so I just downloaded better battery stats. Are there any settings/options that should be adjusted, or just use it as installed and it may reveal the mystery of my mediocre battery life?

BTW, I don't think it has to do with the kernel at all. I've had the same battery life from pre-rooting days until now.
[Samsung Galaxy Nexus] c_86:
I'm using a maguro. So gsm.
[Samsung Galaxy Nexus] --__LoRiS__--:
what rom, kernel and settings?
[Samsung Galaxy Nexus] Culex316:
I am on stock Jelly Bean 4.1.1. Interactive governor, 384 min, 1420mhz max, hispeed freq 1228mhz, input boost 1036mhz, go high speed load at 50%

oh yeah, I forgot to mention I have an extended battery too, but I still notice battery consumption usage improvements nonetheless
[Samsung Galaxy Nexus] Neo3D:
OMG, can we please put this myth to rest? Here is it, straight from the Google Engineer who works on that feature:

https://plus.google.com/u/0/105051985738280261832/posts/FV3LVtdVxPT

Wiping battery stats does not help your phone "calibrate" your battery.

Wiping battery stats does not improve battery life.

Wiping battery stats does not help you grow more hair on your head.
[Samsung Galaxy Nexus] TEK112:
Just install and open it. Then close it and don't look at it again until, you go to recharge it. By default it wipes all the good stats when you plug it back into the charger. You really want to look at a whole day as a few minutes or an hour can have you chasing ghosts.
[Samsung Galaxy Nexus] SUTHRNFRIED:
I was one of those having excessive drain on 283 but after 2 full cycles and now my second day of testing all seems great again. No more drain. 9.5 hrs with a little over 1 hr screen time and I'm at 74 percent. I take more calls during the day BC of work. So doing 2 full battery charges worked for me. Not so sure if I'll need to flash 284 test.
[Samsung Galaxy Nexus] TEK112:
Easy killer... I didn't mean it the way you thought I did.

Calibrate as in calibrate with the device, not calibrate the battery itself. I know of no way to calibrate a battery without special equipment.

I do know an incorrect batterystats.bin will cause incorrect reporting under the battery usage tab and in some rare cases cause certain apps to misbehave that rely on that data to adjust performance (ie. some battery saver apps).
[Samsung Galaxy Nexus] gaich:
I do not use it because of poweramp
[Samsung Galaxy Nexus] SIGUEL:
I use it, and no prob with poweramp playing with screen either on or off.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] sruel3216:
man whatever you did to 284 franco is great. this thing is fast and my micro lag in settings is very very minimal. please dont change
[Samsung Galaxy Nexus] franciscofranco:
Don't worry, r284 + a little change = Milestone 6.
[Samsung Galaxy Nexus] itsalexaye90:
can't wait for milestone 6! best kernel ever.
[Samsung Galaxy Nexus] RoscoeDpG:
?284? :confused:
[Samsung Galaxy Nexus] derPianist:
Some unofficial test kernel

via Google Galaxy Nexus

Pianist ain't Weasel though you've been SPANK'd
[Samsung Galaxy Nexus] RoscoeDpG:
oh i didnt even see 284 test link up i always like to give those a run
[Samsung Galaxy Nexus] osm0sis:
THE BEST unofficial test kernel ;) :laugh:
[Samsung Galaxy Nexus] mssam:
Just out of curiosity, let me pose a general question to whom ever. Do you stay with a nightly (such as r283) until you have problems or do you just update to the next nightly because it's available? Not trying to criticize, just asking a question...
[Samsung Galaxy Nexus] RoscoeDpG:
i usually test them all but if i find one that works better i stick with it untill another takes it out .....i have gone back to 281 because that one gave me great performance and amazing batt life with the reg use i do. Im gonna test out 284 now see if i can get same results seems everyone is happy
[Samsung Galaxy Nexus] sk8oldschool74:
We're is 284. I can't find it on my update app or the site?
[Samsung Galaxy Nexus] CMNein:
In the experiments folder on the nightlies DL page.
[Samsung Galaxy Nexus] klasszsrac:
Here

Gnex ~JB~ Aokp
[Samsung Galaxy Nexus] yellowdie:
I'm a flash junkie. I gotta live on the bleedin' edge!

I write code myself, so I know that when you make a change and release a new version, that change is for the better (sure sometimes it causes problems, but you work through them that way), and with every new release, you are slowly (sometimes quickly) getting it better and better and better. So, me personally, I don't want to sit on an old kernel (even a few hours old!) because I know Franco has changed something in the new version that is for my benefit. Sure some people find staying on older nightlies (or even an old Milestone) to be more stable, and I don't blame them--that's good if that's what you want. But me? I want new. And better. And smoother. And faster. That's why I'm on Franco. I know Boss Man will take care of us. And if you're on old stuff, then his new work isn't benefiting you!

There's my two cents!

:):D:laugh::good:
[Samsung Galaxy Nexus] schizophrenia:
what have you changed from r283 to r284?

It was just 1:30 testing time but the battery consumption seemed to have improved from r283

again, I am on no wifi no Data and the phone has zero/little wakelocks
[Samsung Galaxy Nexus] kyokeun1234:
Franco made 284r to help stop the battery drain that people were reporting.
[Samsung Galaxy Nexus] schizophrenia:
Thanks and yes I know.

that's why I was testing it and curious what has been changed because there is improvement.
[Samsung Galaxy Nexus] franciscofranco:
Doesn't matter what I changed, but its all good now :) Now I changed my sim to the GN, closed the SGS3 on my drawer and will test Milestone 6 until I think its the right time for release. M6 is everything until r284 + 4.1.2 changes.
[Samsung Galaxy Nexus] scarmon25:
Nice. Interested in seeing that when it's released
[Samsung Galaxy Nexus] ChazzMatt:
I went back to 276 a few times. It was very good.

I started on Milestone 5 in mid-September, then started flashing nightlies somewhere in the r240s. I kept flashing every one, only reverting a couple of times if there were problems. But Franco soon sorted things out.

However, 276 was excellent and I've gone back to that a few times. I kept my wife's Nexus on that one, not bothering to update hers further than that. I flashed 283 but have now gone back again to r276.

I've suggested that r276 be Milestone 6 -- then go on from there. :) Let 276 be the new "baseline". :victory:
[Samsung Galaxy Nexus] murdah204:
I'm pretty sure he'll test milestone 6 until MiNCO v5 comes out
[Samsung Galaxy Nexus] franciscofranco:
Nice one Mr. Sherlock Holmes.

Might come sooner than that though, but thats what I'm aiming for.
[Samsung Galaxy Nexus] Antob125:
So i want to make the switch to Interactive from Wheatley. i like running 729min 1305max. Can anyone recommend settings for Governor Control? I searched keyword Interactive and so on but not getting the answers im looking for. I want it to run as smooth as wheatley. and i wanted to test the difference in battery between the two governors. Can anyone tell me the settings to get the most out of 729-1305?
[Samsung Galaxy Nexus] Dr Byte:
The case I posted about was very unusual; I can normally go for days without charging - as little as 20% per day. I have NOT installed the 284-test version because I'm trying to reproduce the same condition, but catch it early-on in case there is something in the logs.

The previous post was already analysed to death, rather than posting raw graphs... but here is a JuicePlotter graph showing "normal" and "unusual" behaviours... the "dive" is where the graph is centred (0900-1500). To summarize: virtually no wakelock activity, no OS-reported app usage, phone in deep sleep for almost the entire duration. Bizzare, I know.

So far, nothing unusual on this charge... but I should mention that I overrode the "overnight" power mode last night, so 3g/wifi/sync were enabled all night. I plan to try recreating the scenario while I'm awake and watching.

Bixie's deodexed JB ROM. http://xdaforums.com/showthread.php?t=1737849

Update: the first attempt to reproduce this sequence of events had no effect. Ditto the second. Trying one more time.

Result: After multiple attempts, I can't reproduce the issue by reproducing the circumstances. Wifi Sleep policy: always, Wifi PM_FAST: off.

Added two extra screndumps

Conclusion: a one-off infarct in the battery reporting electrochemistry, triggered by a sudden wakeup from a cold, deep sleep. If this is anything to do with the kernel, it must be a 'perfect storm' of preconditions that cause it.

I'll keep an eye on developments, see if it happens again.
[Samsung Galaxy Nexus] sruel3216:
ok if you want smooth then copy me... :p

interactive

1228max

729min

go_hispeed_load 50

hispeed_freq 1228

min_sample_time 40000

timer_rate 20000

input_boost_freq 1036

enjoy :D
[Samsung Galaxy Nexus] tyraelasd:
Just installed the 283 nightly and it's quite amazing its been a while since I felt my Nexus this fast. Looking forward to m6, hope it give us good battery life as well.
[Samsung Galaxy Nexus] RoscoeDpG:
not huge deal but sometimes when i connect my phone to computer it will say missing ID? i have to click off debug mode so i can transfer over the files i want and then put debug mode back on. Has anyone seen or have a fix? but doesnt do it all the time, it could just be my computer being stupid too but thought id ask...........oh and 284 running smoooooooooth gonna give it the full day run tomorrow :good:
[Samsung Galaxy Nexus] Antob125:
What about boost and above Highspeed_delay

And the settings above are for a smooth experience with games and ui?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] sruel3216:
lets say i am all about going FAST with my phone. i hate any lag at all. i will gladly sacrifice battery for a smooth experience. i dont play games but im certain it will perform well

above hi speed is 80000 (some use 40000)

boost is enable by default on francos

if you mean input_boost i have it at 1036
[Samsung Galaxy Nexus] THE_KINGDOM:
I know it's older but I'm on r276 and found this to be overall the least laggy compared to the other nightlies, although I haven't tried 283 yet... wondering if I should give 283 a shot..?

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

Agreed, I'm exactly the same way, I can't stand lag. I would rather sacrifice battery life to have a smoother experience.
[Samsung Galaxy Nexus] RoscoeDpG:
y not give it a ride........u can always just go back :D
[Samsung Galaxy Nexus] gianton:
r284 with CNA 1006 nightly, lost 6% (70% to 64%) in 8h overnight all disabled.
[Samsung Galaxy Nexus] shawnaye:
nice to see you fully concentrated on our gnexes, feels great that other phones aren't getting the attention. haha.

anyway gs3 already has gokhan there, they should be fine, STAY HERE FRANCO!
[Samsung Galaxy Nexus] leets4uc3:
What are your wake lock?
[Samsung Galaxy Nexus] IgnorantNerd:
Any radio you would recommend?
[Samsung Galaxy Nexus] osm0sis:
There is lots of love for the UGLH1 radio currently. It's also the newest by build date. Click the links in my sig for both the radio and the corresponding RIL (radio interface layer).

And before you ask it, UILE1 is from a newer OTA, but is not a newer radio than UGLH1 (LE comes before LH alphabetically; first 2 letters are the region code). That's just how josteink orders them.
[Samsung Galaxy Nexus] Savant:
Damn tapatalk won't let me click your signature... :banghead:
[Samsung Galaxy Nexus] gianton:
Why you think this is high?

With my set up this is what I get with Trinity, Lean and AK kernels too.
[Samsung Galaxy Nexus] tzyn:
Boost is off by default for me. I'm running r276 (back from r277 and r28x, because it's fastest for me).

What is "boost" doing?

My current settings:

min 384

max 1305

max screen off 729

input_boost_freq 1036

hispeed_freq 1036

lmk tweak

other settings r276 default
[Samsung Galaxy Nexus] debp:
what difference : Nightlies vs Milestone 5?
[Samsung Galaxy Nexus] Culex316:
Nightlies are experimental kernels that often have new features or tweaks and are released for mass testing and feedback to see how the community likes it but it may (occasionally) cause things to go awry like random reboots, shutdowns or give you herpes.

Milestones are releases that have been thoroughly tested, verified, and blessed by franco to be stable and reliable enough for everyday use.
[Samsung Galaxy Nexus] despard:
You are not gonna believe it. I have tried many kernels out their, they give me reboot, then I thought I need a full wipe maybe. But after I flashed your kernel, the annoying reboots are gone, my phone is running smooth and fast now:D:D:D
[Samsung Galaxy Nexus] sruel3216:
After running a full cycle on 284. Haven't 1m 4sec of screen on time lolol.

We will see round two. But f u c k its smooth
[Samsung Galaxy Nexus] osm0sis:
Looks good to me, but if you want it even better and can live without it, disable the automatic location settings in Maps/Latitude, its creating 18min of wakelocks.
[Samsung Galaxy Nexus] sruel3216:
Whoops here is pic...

i had full wifi the whole time, i just disconnected to leave my house
[Samsung Galaxy Nexus] --__LoRiS__--:
Can anyone tell me what is SD tweak that you use and lmk tweak? I'm feeling noob XD...
[Samsung Galaxy Nexus] leets4uc3:
I fkn hate how maps randomly has wake lock problems. Go into app info. Wipe cache and data then uninstall and reinstall. That worked for me earlier this week. Also if you are able to set your location to be fixed rather than search for your location.

Hopefully his helps
[Samsung Galaxy Nexus] CaspaTheGhost:
Use the same, previously had 1305 as the top end but been testing this recently.

If you're a heavy gamer then you might want to bump it up but in haven't seen a major impact personally.

Generally looks fine, the top one is just where all the partial ones are recorded so is to be expected (explained if you click on the info link). Over 15hrs that looks normal.

+1

Yeah, as Os says. Turn it off as it still works fine without being on auto, picks up your location when you go into Maps or anything else that uses GPS.

Just relates to Latitude which is known for being a battery hog. Sure you used to be able to log out of Latitude specifically, but can't seem to find it now, just the ability to turn off auto reporting.

284 WiFi strength seems stronger. Still connected to the work signal in an area that it didn't on 283.

Looks good Franco!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] th3s7riker:
Hi guys :) A little question... How do you set these values?
[Samsung Galaxy Nexus] --__LoRiS__--:
Franco kernel updater app or trickster mod app!
[Samsung Galaxy Nexus] 11768:
Purchase franco app from play store to support him or download trickster mod for free at the same place. :good:
[Samsung Galaxy Nexus] Crwolv:
Stock SD read/ write speed is a poultry 128kbs... 1028 and higher makes for much smoother performance on Android. Franco, ROM toolbox and many more apk's on the play store can change this setting and of setting is in CNA:) little ole me advizes ya do it:)
[Samsung Galaxy Nexus] gianton:
Thanks will try this.

BTW what's your usual battery drain overnight?
[Samsung Galaxy Nexus] --__LoRiS__--:
I can't find this setting in Franco app.. where is?
[Samsung Galaxy Nexus] nemotheblue:
I feel like I'm late to the party!

Having read through the last 30/40 pages, is the vfs_cache_pressure conversation put to bed? r283 comes with a default of 1000, right? I know Franco and others have said it feels less laggy with a high setting like this, but I'd be very curious to hear how you justify this is Linux/Android terms. Is it not just keeping more and more RAM free/unused?
[Samsung Galaxy Nexus] Fenvarien:
R284-test is really impressive - a great combination of performance, smoothness and battery life. With MiNCOv4 and interactive gov., 384/1305 I get 5 1/4 hours of screen time.

GNex with franco.Kernel / MiNCO ROM
[Samsung Galaxy Nexus] stoske:
What is the brightness settings? Auto or fixed?
[Samsung Galaxy Nexus] --__LoRiS__--:
Franco i noticed a battery life improvement on 284 over 283 (1h and 52m with 39% battery left) But I'm impressed of other users battery life like 5h and a half on screen O.O.... it depends of ROM? I'm on AOKP build 4...
[Samsung Galaxy Nexus] gm007:
Download lux auto brightness from playstore and customize the light to minimum visible screen.

I am on AOKP 50% left.
[Samsung Galaxy Nexus] fuske:
Using CM10 jellybro latest nightly and franco's kernel.

I still get random times with a lot of mipi_link kernel wakelocks that drains my battery :(

I googled and searched XDA but no answers find. Only it has something to do with the camera and Google talk / + . When I don't use the camera I still get this wakelock. The google talk and + I dont use...
[Samsung Galaxy Nexus] gm007:
Delete gtalk and g+ from system/app if you don't use them.
[Samsung Galaxy Nexus] Antob125:
Does this look like the settings you recommended? Btw the boost I was talking about is the second one that reads 0

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] fuske:
deleted Talk.apk but where is the g+ apk?
[Samsung Galaxy Nexus] mpokwsths:
I believe these partial wakelocks are normal (I have them with every rom and every kernel) and they are not draining your battery.

Same ROM with r283 (which is great by the way, good job Franco!)

Auto brightness with custom values (a lot higher at low ambient lighting).
[Samsung Galaxy Nexus] CaspaTheGhost:
Not a system app so its in /data/app

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] fuske:
Well, i'm pretty sure that its draning my battery!

Couple a days ago my battery wont drain anymore, me very happy, and indeed there was no mipi_link on top. The next day it was on top again and my batterylife went bad..
[Samsung Galaxy Nexus] omron2010:
logcat spammed with boostpulse messages

@franco:

My logcat is still being spammed with:

E/Tuna PowerHAL ( 322): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device

Using nightly r283 and Bigxie 4.1.1 stock rom (busybox, root, insecure boot). Please advice.
[Samsung Galaxy Nexus] safendi:
the kernel milestone 5 work fine with 4.1.2?