yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Q&A, Help & Troubleshooting] aguadilu:
Hi, I think it has happened in most of the roms I've tried. I have the battery completely charged 100% and then just as I unplug the phone it jumps to 99%!

Somebody know why this is happening? How could avoid it?

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] onslaught86:
It is absolutely normal behaviour. There are explanations for this all over the Internet. Please search before posting, and please don't post non- development threads in the development forum.
[Galaxy S III Q&A, Help & Troubleshooting] D_Magic:
Can't avoid it cause it's a feature...you also posted this in the wrong thread!!

All questions have to be asked in the Q & A thread
[Galaxy S III Q&A, Help & Troubleshooting] sstanton86:
Ok please don't take this offensively, but how dumb do you seriously need to be to post this in the 'development' forum and not the 'Questions' forum????

:eek:
[Galaxy S III Q&A, Help & Troubleshooting] aguadilu:
I'm sorry I misunderstood some Tapatalk feature, please don't jump on me. Feel free to erase this thread.

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] fallenwout:
It is probly 99.9% but showing the first 2 digits.
[HTC Sensation] mickh:
can i connect a sensation to a iphone connector,i have a dension 500 in my car with a iphone connector, is there a way of connecting so i can play music thro it,anybody help,thanks mickh:confused:
[HTC Sensation] Sindroid:
I dont think so..

Beamed from my Senny..
[HTC Sensation] realsis:
I don't think so either.... Sorry
[Samsung Galaxy Mini] M1hai:
Can someone please upload the latest version of Kies Air?? On Google Play it is: 2.1.206011 but our Galaxy mini is not compatible...so they say at least because i think it is fully compatible and I ask to upload it...please!:D:D
[Sony Xperia P, U, Sola, Go] rolex0815:
Is it possible to establish several own forums for the other models of the Xperia NXT series?

For me, the "Android Development Thread" of the Xperia S has nearly become

unreadable

because of many other threads belonging to Xperia P,U,Sola etc.
[Sony Xperia P, U, Sola, Go] krabappel2548:
I know, there have been more discussions about it, but no.seperate forums yet.. And I'm sorry for all the development threads I have there :D
[Sony Xperia P, U, Sola, Go] poo-tang:
Agreed its a joke this forum why bother calling it xperia s mite as well call it just Sony general. The mods are kidding themselves if they thing it's clean (mod closed last thread like this and said that exact statement) maybe xda can't cope? server issues? What ever it is that's stopping them from making them. Just hope they sort it out soon :mad:
[Sony Xperia P, U, Sola, Go] iridaki:
You need to make a request here.

And yes, I do have to close this thread down, because this is not the place to make requests.

Mainly because the people involved in those kind of decisions will most likely not see it here.

Not every phone can have a home in XDA

.

There are many factors affecting the decision, one of them being interesting and continuous development, this is xda-developers after all.

P,U and sola are relatively new devices, borderline low-end, middle-end at best, so it could go either way.

You need to be patient and in the meantime, try to make the accomodation of more than one phones under the same section bearable.

It is your responsibility to post in the correct sub-section, provide clear and to-the-point thread titles ("HEEEEEEEELP :(" "OMG wtf happened to my phone" "???" etc, are NOT acceptable) with tags ([P],

, [Sola],

) so that the forums are as clean and helpful as possible.

Thanks!
[Nexus S Android Development] bedalus:
Download latest marmite: this post

Download marmite for old versions e.g. Jellybean: version matrix

Marmite once made me more sick than I'd ever been before or since.

But I still love it. #truefact

This kernel is based on the stock jb kernel. I have kept, added or tweaked the features I approve of:

- CFQ I/O scheduler (best performing)

- Ondemand, tweaked values

- BLN (no blinking), BLD and Fast-Charge

- more free RAM

- Bluetooth fixed and PM_FAST (keeps fast wifi even with screen off)

- Voodoo sound and colours with my settings for a stable whitepoint at all brightnesses.

- Zcache: compressed cache stored in ram, improves performance by retrieving cached pages from ram rather than flash

- MTP (explanation below the links)

- custom OC available

Voltage and OC quoted from a chip designer with 14 years industry experience: here.

What is ORD?: here.

Facebook by leap_ahead:

here

What you need to know about Custom OverClocking [OC]: here.

Interesting discussion of gamma and RGB setting (voodoo): here.

My kernel doesn't wipe your cache or dalvic, so you can flash and reboot in less than a minute. Read this.

What is MTP?

Firstly, huge props to krfoy for making this work with the any-kernel script. Great work!

Microsoft's Media Transfer Protocol. It allows for dramatically faster transfers too the phone, so it is really good when you are copying over films or mp3 folders. What's really good is that you can continue to use your apps while these transfers happen. Faster? More functional? You bet! The limitations are that it is relatively unsupported on non-Windows platforms. However, you can investigate these possibilities: Ubuntu: here. --- --- Mac: here.

How to Select MTP/PTP

Go to Settings>Storage>(Hit capacitive menu button)>USB Computer Connection to select.

If your ROM doesn't have the switch there then check this tip from pigsan! or use the command line.

* * *

Big thanks: ...to the community! So many people supported my research that it's impossible to thank them all individually. Particular thanks to tchaari and Harbb. Credit goes to: _thalamus for getting me started with git, correcting my misconceptions about merging; KalimochoAz for CM; ezekeel for the incredible variety of mods; mathkid95 for ondemand tweaks; steve.garon for help with scripting; morfic for his advice and permission to use his colour settings; and supercurio for voodoo. Big thanks to krarvind for MTP, legend! Congrats to krfoy for enabling MTP via the any-kernel script. Nice work! Thanks to caliban2 for his consistent and unbiased feedback. Thanks to brainmaster, when I originally joined the forums for being so helpful. Hopefully I treat newcomers just as kindly.

Old versions: http://goo.gl/B0p8Z

TOOLCHAIN: Linaro a8 optimised by [MENTION=4825437]Christopher83[/MENTION] here

SOURCE: http://github.com/bedalus/marmite
[Nexus S Android Development] stempox:
bedalus Hello, I can add this kernel to the list I made on the kernel and rom?
[Nexus S Android Development] bedalus:
Yes, but be sure to give credit to the right people.

I've decided to attempt to build my own version of thalamus' kernel with some mods.

If I'm not too retarded, hopefully i can achieve this in the next few days.

As a result of learning to manage git and c, I'll have less time for forum posts.
[Nexus S Android Development] jjhrrsn:
Looking forward to this
[Nexus S Android Development] apatal:
This is good news, Dave. I've been hearing a lot of good things about the new stable release of thalamus in the thread for his kernel that I've been moderating. However, a lot of people including me will be missing BLD and BLN so it's nice to see how it would perform with these mods. With those two plus Voodoo sound that's already cooked in the last release, this may be a kernel to be reckoned with. Cheers! :)

Sent from my Nexus S
[Nexus S Android Development] ironia.:
waiting for bedalus thalamus base plus addons

an interesting benchmark would be bedalus vs thalamus
[Nexus S Android Development] apatal:
Off-Topic: I've been discussing with thalamus about the need for a dalvik wipe before flashing a kernel, and he had some pretty convincing arguments against it. You can read his statement here.

Just wanted to get your opinion on this, if you have time. Thanks, Dave.

Sent from my Nexus S
[Nexus S Android Development] wmdunn:
+1. Me too! Would be nice to have voodoo color included.
[Nexus S Android Development] bedalus:
Thalamus wins,

REMATCH!

Thalamus wins again.

Good news, BLN added. I now know what I'm doing with the code merges, so more features to come soon.

Later on I may start trying to make some original mods, but for now we'll focus on existing ones.

Thanks to thalamus for his help with some extremely noobish questions,

...thalamus' latest but with added BLN and marmite.

To Do

Get organised

Push back to github so changes can be observed

Get some sleep
[Nexus S Android Development] mixtapes08:
Lol at marmite. :)

Sent from my Nexus S®
[Nexus S Android Development] bedalus:
Yeah, i agree with thalamus. I only wipe when switching ROMs.

I modified the script so it doesn't bother wiping cache or dalvic-cache

This makes flashing much more painless.

If anyone has trouble, reboot into recovery and wipe cache.

apatal provides some handy scripts for wiping: http://xdaforums.com/showthread.php?p=19746141
[Nexus S Android Development] _thalamus:
To be completely honest, I wouldn't have been so helpful had I known you intended to release this, specially without saying anything to me about it.

I fully accept that the GPL doesn't require permission but to ask is both the polite and respectful thing to do.

The majority of others have always when they have wanted to release my work with superficial alterations...all it takes is 'I plan on doing this, what do you think?'

I have never had any objection, but to be asked first is just common courtesy, specially when you are asking me for help! You had plenty of chance to mention it whilst I was assisting you with your queries via email.

But hey...
[Nexus S Android Development] DaXmax:
From what i see here... Give him the big daddy credits as you used his sources... ;)
[Nexus S Android Development] bedalus:
Sorry, links pulled.
[Nexus S Android Development] mixtapes08:
Too bad i was diggin the marmite just now lol

Sent from my Nexus S®
[Nexus S Android Development] bedalus:
I feel quite bad now. I don't know what possessed me to release without getting the okay first. Eager to show off i think. :o

I'll get this thread locked as a lesson to myself!
[Nexus S Android Development] mixtapes08:
We're not perfect we have our own mistakes in life :)

Sent from my Nexus S®
[Nexus S Android Development] bedalus:
Actually thalamus is fine for me to release this! Yay. Thanks thalamus.

Links will reappear when the OP is properly organised and credited.
[Nexus S Android Development] :
Here's another link: https://www.box.com/s/470636474d8efe07201f (v0.9.3 experimental)

Okay, I know MTP works with Slim ICS, and I've been told it's working with Cyanogenmod 9, and Remics, which I see is based on Cyanogenmod. So does it work with any Cyanogenmod based rom? Like brainmaster's and markvis'? Does AOKP provide the MTP option?
[Nexus S Android Development] madd0g:
I wonder if MTP can work with a stock ROM ? Like using coming stock JB and your kernel (when it's done for JB) ?
[Nexus S Android Development] :
Maybe, but you need some way to tell the OS which UMS method you want, and I don't think the stock rom has the switch in storage options... so, I think it might need a rom developer to release a mod at the very least.

In other news, I'm trying to bring back franco's ondemand tweak. Since I've had some more sleep, I was able to meld his version with a bit more restraint and consideration, and hopefully this time it'll work. In the cpufreq_ondemand.c file it says:

/*

* Not all CPUs want IO time to be accounted as busy; this dependson how

* efficient idling at a higher frequency/voltage is.

* Pavel Machek says this is not so for various generations of AMD and old

* Intel systems.

* Mike Chan (androidlcom) calis this is also not true for ARM.

* Because of this, whitelist specific known (series) of CPUs by default, and

* leave all others up to the user.

*/

So I think franco has decided that for the tuna board, removing IO accounting is viable. It saves a few cpu cycles in deciding the frequency step, and I think prevents higher IO loads from having direct impact on the CPU frequency.

Caveats: We don't have a tuna board! We have herring. Also, the way I'm reading the above paragraph, it seems to suggest that ARM processors DO want IO accounted as performance critical... Also, is franco crazy??? (j/k :p) But, just in case franco is right, and that paragraph is written a little backwards, I'm taking out the IO accounting too. I'm running a build of it now (v0.9.4) but I'm not releasing this one until it makes it through a day with no crap-outs.
[Nexus S Android Development] caliban2:
Hm, just had a total freeze while listening to music, had to pull batt. No last_kmsg, system never got a chance to save it.
[Nexus S Android Development] madd0g:
Oh right, forgot about that. Hm, maybe a solution would be to make an app dedicated to that and it needed root to switch.
[Nexus S Android Development] :
No. Removing the code for the io_is_busy tunable will do exactly the opposite, that will make the iowait time be accounted as busy. Removing *all* the iowait accounting code will make it act exactly the same as it does by default, ie, the iowaits will not be counted as busy time.

Higher I/O wait times will make the CPU frequency ramp up with said tunable removed. Whether that is a good or bad thing is debatable, I removed the tunable in my bravo kernel and did notice a bit of an improvement to responsiveness immediately after boot, but I/O wait time is technically idle time because the CPU isn't doing anything except for waiting for a blocking I/O operation to complete.

The reason for the addition of iowait accounting is explained here in this commit.
[Nexus S Android Development] :
Is Deep Idle on?
[Nexus S Android Development] :
Thanks for explaining that, and great link... btw how did you know where the patch originated? Is it a nuance of git navigation that has gone over my head again?

I'm benchmarking the kernel both with and without the io wait-time code, under cfq, deadline and noop. 21 times for each scheduler to establish confidence in a normal distribution, then standard deviation to establish the boundary where we'd expect 99.7% of results to be above. That's 126 benchmarks! It's going to take all day I expect.
[Nexus S Android Development] caliban2:
Sure, but if you now want to tell me to disable it - stop right there.
[Nexus S Android Development] Maximilian Mary:
This is why bedalus' kernel will make all others weep. :beer:
[Nexus S Android Development] noobiekins:
In my testing of air kernel, if you turn on deep idle, it might SOD or freeze when screen off. My fix was to increase the INT voltage of 100mhz to fix it, haven't had any problems since. I set my voltage to 1050mv
[Nexus S Android Development] Jamalsid:
You know what this kernel needs...................................a boot animation of a pot of marmite revolving or something.
[Nexus S Android Development] caliban2:
I said stop it! :p

Joking aside, it was caused by cfq. With deadline everything's fine. When it happened the second time, kmsg was created. Bedalus has it.

Will test cfq with different speed settings later, but I'll keep voltage@100 in mind as well.
[Nexus S Android Development] :
Read the OP
[Nexus S Android Development] :
Franco's ondemand tweak.

No significant impact on database IO

CFQ
sd w io	+0%	-20%
sd r io	+22%	+15%
Deadline
sd w io	-37%	-13%
sd r io	+26%	+18%
Noop
sd w io	-14%	+53%
sd r io	-24%	-4%

Percentages represent increase or decrease in performance compared to no-franco-tweak.

The first one is based off a borderline where we can be near-certain the raw benchmark result would always be greater than. The second percentage is just the mean score.

So, not exactly a conclusive result, as thalamus suggested. What I see though is general improvement in reads, but deterioration in writes. Since writing to the disk is one of the main bottlenecks, I think we'll err on the side of caution, and stick with the untweaked ondemand.

There's another conclusion we can take from this, noop is the best for disk reads. But for disk writes, CFQ wins. Deadline seems to be a compromise between the two.

I'll attach the raw data and stats to this post if anyone is interested.
[Nexus S Android Development] :
Okay, so .config is automatically generated. It's taken me this long to realise why I couldn't revert franco's hz tweak, despite a message on the terminal telling me that .config had been written, and the head of the .config file says "This file is automatically generated. DO NOT EDIT."

I just needed to revert the Kconfig file instead. :facepalm:

Source code at github vanished for a while due to my ineptitude with git, and I still haven't worked out how to properly revert something that I've already pushed... (hints anyone?)

...but it's back up now.
[Nexus S Android Development] :
Increasing the HZ won't do any harm other than increasing battery usage a bit and slightly affecting performance due to the CPU spending more time servicing timer interrupts and context switches. But, it's fairly pointless unless you have a specific reason for doing it, such as BFS, but even then, 256HZ is sufficient.

To revert a commit it is: git revert <commit sha1>

You should probably read about git rebase too, which allows you to rewrite git history, and rebase your changes on top of another codebase.
[Nexus S Android Development] :
It's a bit of a hazy memory... but I think what I did was a git hard --reset <sha1> to where I wanted to be, then found I couldn't push it to github... so I forced it, then my branch disappeared from github completely!

I've skimmed over rebase before. I think revert was probably what I should have done.

Also, I think I may have reasoned out what's causing this 200 MHz min step thing. I think what's happening is due to two tweaks

1) the code Kalim introduced to increase the min to 800 MHz if Deep Idle is enabled and the system goes into suspend

2) the 200 MHz min tweak for when the GPU is active.

What happens is if the min has been temporarily raised to 200MHz by (2), then an early suspend is called in (1) it will record the current min of 200 MHz before setting the min to 800 MHz. When returning from suspend it restores the previous min of 200 MHz, but then (2) isn't resetting back to 100 MHz for some reason.

I'll consider how best to hack around this issue.

Caliban has got a testing release, we're still looking for stability too. If he finds it okay, I'll release a new testing version.
[Nexus S Android Development] :
I haven't looked at the code so I don't really know what is going on there. That seems to be an unfortunate bug.

I can guess that it isn't being reset back to 100MHz by the GPU tweak because it thinks it is already at the minimum when it is at 200MHz after a suspend. I suspect they use different methods to set the minimum.

Why does the frequency need to be set to 800MHz if deep idle is enabled and the system suspends? The whole point of deep idle is the apps CPU is power gated, so the frequency is irrelevant.
[Nexus S Android Development] :
I'm not sure, I believe Kalim introduced the code (actually I can't remember where I got the idea he wrote it, I hope it wasn't just an assumption) to improve the stability of DI.

Personally I think it's a good idea because when I measured the amps drawn, the most power efficient state was 800MHz. This was with music playing, so the processor coming from sleep to the DI state to feed the audio buffer.

The method of my test was to fix both min and max at the same frequency. All the battery drain results are here: https://docs.google.com/spreadsheet/ccc?key=0AntDDKv-lS6IdEY4T3dXWVFDWk9lREdJNGFfU2NwRlE

...just do a ctrl-f for deep idle. Different frequencies have different amps drawn.

Just had a little play with rebase. I'll be squashing commits into one before pushing from now on!

---

NEWS: Things are looking good for the stability of the next version!
[Nexus S Android Development] jojoost:
Seems like ondemand/deadline is doing absolutely fine!!
[Nexus S Android Development] :
Just cherry-picked the IDLE2 code, and perhaps I did it wrong, but I'm not seeing any TOP=OFF accumulating. However, I am seeing TOP=ON accumulating while the screen is on, which is thalamus' intended behaviour. This might be good for extra power savings while the screen is on, but the problem is that it lags badly. But I'll double check that I merged the code properly anyway.

If the lag can't be fixed, I'm not going to include it.
[Nexus S Android Development] italia0101:
Sounds interesting .... but definitely a good call about the lag
[Nexus S Android Development] jayzu2512:
When i test phone by antutu benchmark. Max speed cpu is 1200 in info system, but i set 1000. Who could tell me about different that???
[Nexus S Android Development] Imppy:
Android is 20 percent on 4.4.1 hmm
[Nexus S Android Development] :
EXPERIMENTAL IDLE2 version

UPDATE: Here is 4.4.4:

Remember, there is no MTP (conflicts with IDLE2)

-Stock OTA only: http://d-h.st/Brz (4.4.3)

-All other ROMs: http://d-h.st/V54 (4.4.4)

Rules

Do not bother thalamus about this, users posting in his threads seems to bug him, and if he is busy telling people off, he is not working on the code.

Post all issues here, and I'll work out if they are reproducible, and let him know. Thanks! :)

Issues

Bluetooth may die. Someone confirm please? Thanks! :D

Caveats

I've tested this and very little, if any power is saved. This may improve with further testing.

Tips

In a terminal emulator:

cat /sys/kernel/debug/idle2/error_stats

...will tell you how well it's working

Idle States: Equivalent Terminology

Idle	= C1	= State 0
TOP ON	= C2	= State 1
TOP OFF = C3	= State 2
[Nexus S Android Development] italia0101:
Could you make one for stock please would love to try it
[Nexus S Android Development] :
Not until i know it's working well enough.
[Nexus S Android Development] italia0101:
No worries fair dos
[Nexus S Android Development] dimeim:
Awesome kernel, works very well with Codename 3.3.2 but I just can't get BLN to work.. Any help please?
[Nexus S Android Development] caliban2:
You know, all that ambiguity in just one sentence - very, very nice...! :D

It's hard to catch. At first I thought "what lag is he talking about?!" Not bad at all.

Not a typo on your side? "idle2_disabled=1" meaning it's on looks wrong to me.
[Nexus S Android Development] 309041291a:
Haven't got to test battery yet cause I put a new Paranoid on my phone with 50% battery. Going to do a charge cycle today. Then test battery on my new setup.

Nexus S. (GSM i9020a)

Paranoid Epsilon 1.2(1.992 - 4.1.1)

Marmite (4.4 - Bedalus)

Smartassv2 (1000/200)

Deep Idle (On - Deadline)

BLX (98 - Inverted. Apps)

Black Exodus (UnderVolted)
[Nexus S Android Development] CrackerTeg:
Good tip and good to know about the bigmem now included. I went ahead and doused it in alcohol and shoved it back in the cat litter. The only thing not working is the ear speaker at the moment. I'm currently using the wife's s2 in the meantime while she uses her old iPhone. At least she let's me stick with Android when I muck things up. Lol.
[Nexus S Android Development] Blackcrx:
V4.4.1

8.5hr up time

47mins screen time

Android OS: 15mins CPU. 1hr 5mins keep awake.

Still got the bug. Back to V3.5
[Nexus S Android Development] :
I think it must be the ROM. Unless you can run another kernel without any issues?
[Nexus S Android Development] pan1980:
with androxide 3.1.0 and bedalus 3.5

currently i have 3 days 0h 44min uptime

battery at 21%

screen on time 3h 5m

android os cpu time 38min, keep awake 1h 4min.

i havent tried any other version after 3.5 since 3.5 gives excellent perfomance and really good battery life, either with screen on or stand by or combination. http://xdaforums.com/showpost.php?p=30392438&postcount=1580
[Nexus S Android Development] linuxxp:
I did a full wipe again and this is the result (pictures). 10 minutes ago I flash Jellybro and marmite 4.4.2. I'll write about the results. More and more I begin to think it is ROM issue.