yashsingh1/xdaforums huggingface dataset:
[Windows Phone 7 General] ChrisKringel:
Hello guys,

ah another one waiting for the Omnia W :D I'm currently sporting my old but well-functioning HTC Elf. And I think I'll keep it as navigation system in my car when it gets replaced. And although it gets the job down I can feel it becoming older and slower from day to day. So i decided to jump to WP7. However I'm still waiting for affordable devices. As a student, my budget is limited and i want to spent around 300-400 € for my new mobile phone. At the moment there are the HTC Radar and the Omnia W more or less announced around this price. But the Radar seems ugly and I'm not really convinced by its specs. However I've heard quite some praise for the Omnia 7 so I'm assuming that the W will have a comparable build-quality. However 8GB is not much and I'm hoping that Nokia will announce their devices really soon. But at the moment I'm going for the Omnia W :-)

Regards

Chris
[Motorola Droid 3] MrJudylicious:
Ok Im on .890, rooted, debloated. I create a playlist in the stock music app. Add songs to it and finally save it. When I reboot the playlist shows in the list, but when i try to play it it says its empty. Anyone else having this problem? Any ideas?
[Motorola Droid 3] eXecuter.bin:
The stock music app is horrible, and I've experianced the same issue before. Use a third party player such as POWERAMP.
[Motorola Droid 3] redsox985:
I second the vote for PowerAmp. I love having an equalizer with custom profiles. 1 profile for my car, 1 for listening, and 1 for working out.
[Motorola Droid 3] wootizzle:
Player pro is where its at.
[Motorola Droid 3] MrJudylicious:
what about free apps?
[Motorola Droid 3] binlalo:
I also have that problem! Did you solve it?
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] dpaun1:
I have a problem with my Samsung Galaxy Tab 10.1 (GT-P7500). My stock Album show picture in wrong order. i mean can i change the order of pictures in stock Album?? i have some albums inside and the first pic i took is at the end right, so if i want to see the picture i need to go to last picture then start looking to begining. now i use a QuickPic. what is the best Photo Album viewer for that tab? thanks....
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] Tivo7:
"Just Pictures" is a great gallery app. I use it for my DroidX and my Gtab7510
[Android Q&A, Help & Troubleshooting] caretaker01:
Recentlly Graphisoft anounced an app for iphone and ipad called BIMx wich allows the user to explore a building model

Is there any way to port it to an android device because they say that its not available for android platform (yet)

Any way to doo it without haveing to buy an Ipad?
[Galaxy S II Q&A, Help & Troubleshooting] manoeke:
Hello,

I am having some trouble with a chinese s2,

I read alot on this forum, and I was able to flash my own s2.

But mine is bought where I live, in belgium. My dad bought one in china.

I tried to put on a belgian firmware, but he won't accept it.

I used odin, but it stops when he tries to upload the firmware:

NAND write start

write operation failed

I've been searching the whole day by now, but I can't get it fixed.

Can anyone help me out please? I have got only 3 days of android experience.

*UPDATE*

I was able to flash a kernel to the device.

before that, I couldnt start up the phone, now I can start it up again.

But I still can't flash a matching firmware...

Thanks in advance.
[Galaxy S II Q&A, Help & Troubleshooting] lucifaru:
do you have the soft brick icon now? (the one with a small triangle between the cell and a computer). I tried exactly that flashing other country's rom and I have a failed write. Just try to flash it back to HK or asian rom and see if it boots your phone. for some reasons it should allow you to flash back your old stock rom
[Galaxy S II Q&A, Help & Troubleshooting] manoeke:
Yes I had that triangle, but now the phone functions normal again...

If I upload a new kernel the phone works, if I trie to upload a new firmware it wil fail and the phone won't start up again.
[Galaxy S II Q&A, Help & Troubleshooting] manoeke:
I cant get it solved....

Does anyone know how I can at least get the market to work on it?

I installed market apk on it, but when I trie to open it, it asks for my google account and then crashes.
[Galaxy S II General] xak944:
I really appreciate all the effort you've put into researching this!

While I certainly do believe this, what leads you to believe it is a driver issue? And what particular driver have you found is the culprit?

I know that the 2.3.4 update for the original GX2 was supposed to have fixed this exact bug. You're saying that it is not in fact fixed? Shouldn't Samsung be alerted to this blunder? :confused:

So you're saying it was just dumb luck and you happened to not trigger the bug? So this could account for people finding "solutions," but they were only coincidental of the bug randomly not manifesting itself?
[Galaxy S II General] Molitro:
Very weell explained.

As far as the first SGS, I can confirm that the bug was solved from the first 2.3.4.

I was experiencing a fantastic battery life with my SGS, and I was quite shocked when I had to watch helpless as Android OS went up on the S2.
[Galaxy S II General] Jebus99:
That was a fantastic explanation. It does explain the vast difference in AOS between my Nexus S and SGSII. Hope this thread gets pinned to help put away the vast number of AOS threads present. And hopefully it'll help get more people to star the issue and get it the attention it badly needs!
[Galaxy S II General] AndreiLux:
It's been confirmed by a Samsung person on the original Galaxy S where it had the very same issue. Which driver exactly it is, I don't know. Supposedly it was the Wifi-driver but the bug also happens to some extent without Wifi, so I don't know. If you want you're welcome to go through 120MB of kernel source code to find the issue and change it.

Look. There's Android, and then there's a complete phone firmware. People tend to call firmware versions by the Android version they're on. Android version itself is completely meaningless and it's not Google's job to fix this, the manufacturers are the ones who deliver the drivers and everything that makes Android run on the phone. There's been for example about 8 leaked firmware versions for 2.3.4 on the Galaxy S2.

Yes. Go wave a dead chicken over the phone and practice voodoo magic on it and you'll be just as successful at changing the behavior. The issue goes way too deep for the user to have any reproducible impact on it.
[Galaxy S II General] SiSL:
Thanks for great explanation and having a bit more light on the issue. I'm going to star those as soon as it goes off maintenance.
[Galaxy S II General] Matriak31:
Good post thanks for your research.
[Galaxy S II General] xak944:
Was this in a support case you opened with Samsung? A forum? Where and how?

Then why are we flagging the issues on the Android project? Shouldn't we be hammering on Samsung support channels for a fix if the problem is located in their proprietary drivers?
[Galaxy S II General] AndreiLux:
Galaxy S XDA thread ; post in question ; response by Todd who is a Google employee.

You're more than welcome to show me the proper non-Korean Samsung channels. You're the one who said in big bold red letters to flag it to Google. :p In any way, Google forwards big issues directly to the manufacturers themselves.
[Galaxy S II General] xak944:
Oh good grief. We've really gone full circle now. That entire thread claims it was fixed in 2.3.4! :eek:

Yeah, you're right. I should've done my own research and not assumed you knew what you were talking about.

http://www.samsung.com/us/SUPPORT/

http://twitter.com/SamsungSupport

http://facebook.com/SamsungSupport
[Galaxy S II General] jonny68:
Very good post probably the best on the subject to date.

Personally running 2.3.5 i don't find it as bad but there can be no denying the problem is still there and until Samsung sort it out it will continue to be there.
[Galaxy S II General] AndreiLux:
It was... for the Galaxy S, we're on another phone. XXJVP fixed it, not 2.3.4. I said it earlier, firmware version != Android version.

Well I'm not that stupid and have been that far myself. The US site doesn't even let me select my model because it doesn't officially exist there, and the international site where I'm rerouted to doesn't even have a report feature and the only contact is a phone number. And I'm not going to start FB'ing or Twittering about driver issues to a mega-conglomerate coorporation, I'll leave others to do that. Hardly a "proper" tech support channel as Google Code. Only the Korean site has that, but sadly, I can't speak Korean.
[Galaxy S II General] spridell:
Thanks for the research.

Lets all star this so we cant get it to Samsung and they can fix this ASAP.
[Galaxy S II General] claimui:
Great post. Lots of people are talking about battery life but without understanding how the stats work and how to interpret them.

The battery usage screenshot is funny though. Yeah, I understand it shouldn't have those steep fall-offs. But still, must be pretty nice to have 40% battery left after 2.5 days!
[Galaxy S II General] marcadam:
Thanks for your explanation, I often wondered what the android os bug was and now I know. I'm quite fortunate by the sound of things my android os is usually around 15%. Is this issue likely to be resolved with ICS?
[Galaxy S II General] Shafty:
Here's what I don't get. I've had the phone since week one back in may and from may to September - no os bug. So why now? Have I done something to trigger it? Can we isolate the cause to prevent others getting it? I can list what I've done different recently to previous months if it helps?

And if it's drivers then why doesn't it access the CPU when the charger is plugged in?

I share everyone's frustration over all this.
[Galaxy S II General] Pheno.menon:
We have the same problem on the US Galaxy S II/Sprint Epic 4G Touch :\
[Galaxy S II General] m2smoe:
This thread should be stickied!
[Galaxy S II General] AndreiLux:
I have no idea.

I've tried it on half a dozen ROMs, wiped everything clear, removed every app to the point of the ROM being pretty naked, and still didn't get to change it. There's a lot of people like you who say they don't have the bug and suddenly have it. It may be a hardware fault that doesn't trigger until some certain circumstances are fulfilled. Maybe it's just some stupid bug in the drivers and it's some synchronization problem between registers. It may be cosmic rays who change a bit in the memory. Who the **** knows.

All I know is that nobody has been able to isolate it to any common cause, and I sure haven't managed in the last 3 months, and I've had it since July myself. At the same time you ask yourself why there's such a wide variety of devices having the same issue, but different hardware. If I would be paid full time to look through the source code and find the bug then I'd do it. But until then, I just wanted to share it with everybody and just tell them to stop wasting their time.

Because when the device is plugged in then a wakelock is active and the device doesn't go to deep sleep at all. Since the going to deep sleep process is what is bugging, then wakelocking it prevents it from bugging out. I mentioned this already in the post. Since you have MIUI, you can for example tell it in the battery setting to not go to deep sleep at all (there's a checkbox), and see the results for yourself.
[Galaxy S II General] shotta35:
I'll just say i got my SGS2 recently and it came with 2.3.4 - there was no AOS bug at first then oneday started noticing it. I upgraded to 2.3.5 via XXKI3 and it's better as it's "only" 11% now rather than 29-40%.

Guess i should check with CPUspy to see if the phone is actually deep sleeping - I would however assume so as it's been getting better battery life since i upgrading to 2.3.5.
[Galaxy S II General] Capp5050:
You're correct, and I apologize; In my frustration I didn't even respond to your question. So you understand, my real frustration is spending hours pouring through these threads for a solution, only to find 1/3 of the posts being from people trying to 'explain' to others that they really don't have a problem. Not only is that counter-productive, but dissuades any 'lurkers' from Samsung/Sprint, or wherever, from recognizing the issue exists. OK, 'nuff said there - to your questions:

I have a Galaxy S2 Epic 4G of the Sprint variety (SPH-D710)

Until yesterday, I was running Android 2.3.4, and Kernel: 2.6.35.7-SPH-D710.EG30-CL435734 (stock/came with phone)

Out of little more than despondence, yesterday I rooted the phone and now I have Kernel: "2.6.35.7-g130e817-dirty"

With the root and the revised kernel, surprisingly, the phone now seems to be able to enter 'deep sleep', but the battery drain is still huge, the AlarmManager errors are still many, and the 'Suspend-Event/0' still appear numerous.

Thanks for the suggestion regarding 'dumpsys Alert', but when I try this, I get a 'permission denied' error (I tried a couple emulators and same result). I'm new to Android, and unfamiliar with its architecture, how permissions works, etc. I'm guessing this is a 'protected' file that can be dumped if one knows what they're doing, but clearly I don't.

If you have some advice, I'd appreciate it, and so as not to cause to much of a digression from this thread (i.e., if others aren't having the same symptoms), feel free to respond via PM.

Best,

Andy Capp
[Galaxy S II General] crypticc:
Siyah kernel 1.8 from Android development (not original) freeze ALL SNS* apps and AP weather and AP News. Finally wipe data in settings applications for....both calendar apps and calendar widget (you can re sync).

Don't register for Samsung at all..(use Cerberus from market which uses push for security triggers rather than constant polling like Samsung)

oh and if you get zero deep sleep on siyah trigger reinstall of su.

Figure out if your network does fast dormancy. In UK O2 and 3UK based networks do. Ki8 has correct nwk_info.db settings for most (off time means is enabled for some reason).

If you have Facebook app open chat then "go offline" (you are online by default).

Finally battery calibration

Virtually zero wake locks for me with >five hours of screen on time over one and a half days. Finally I had to run a few Quadrant tests just to get the battery to conk out so I could recharge it.

TV.out it's mentioned in wake locks but only because everything else its measured in one second or two.

I have a gmail, snow storm weather widget, and feedr rss feeds.

Good luck.
[Galaxy S II General] s2d4:
its all good, we r here to learn anyways. I should have mentioned that it needs to be run as super user to have access. U may also need to install superuser app from market , So try this:

su

It should prompt u to run emulator as super user, allow it. Then type the following.

dumpsys alarm > /sdcard/alarm.txt

U can read as text if u use root explorer.

Hope this helps...
[Galaxy S II General] zippyijk:
Well my AOS seems to have fixed itself?

As in my previous posts I was struggling to get to 12 hours with the 2000mAh battery in.

I was also getting the issue with the usb port thinking it was connected to cardock/charger randomly wouldn't connect to charger or PC at times.

I was fixing the usb, by using the old "cocktail stick and a bottle of isopropyl-alcohol" and cleaned then pins inside the usb port.

I removed the battery, sim card, and sdcard beforehand and cleaned the pins on them too (not the sd cause you can't reach them).

When I powered her back up, the unofficial firmware count had reset to 0 SWEET :D no idea how that managed to happen, I had the battery out when I cleaned the port and made sure it was dry when I turned it back on. The little triangle on bootup is gone too. Still rooted, still running KI8 with siyah kernel.

Then this morning I noticed my battery stats, AOS is at 2%, I'm now on 23hrs without a charge and I've still got 47% battery left :D Thats been with normal usage, a few phonecalls, approx 1.5 hrs internet, push gmail, some Elmo videos for 20mins for my son. Very very happy so hopefully it stays the same.

I've no rootcause and there is no reason why what I did should fix it but somehow it has. I'm an manufacturing engineer by trade so I know how to troubleshoot devices well and I never listen to the "I did x/y/z and spun round 3 times and changed the battery and powered it on while it was upside down...." ;) but as I said something I did obviously fixed it :confused:

Maybe I've just stopped the issue and it will come back. I'll monitor it and post how its going in a day or two.
[Galaxy S II General] aqualeris:
Honestly think the AOS bug either isn't really draining the battery or Siyah has somehow managed to make it stop reporting on battery stats and not really fixed it.

Said this because I reverted to SpeedMod after testing out Siyah and even with my high AOS % back in battery stats, my battery life is very much comparable to what I got in Siyah. And of course I was undervolted in Siyah and even underclocked while I'm completely setCPU-free on speedmod now. Kind of wondering if the 'improved battery life' because of Siyah is just a placebo effect.

Of course I am by no means intending any offence to any supporters of the Siyah kernel or the dev of it himself. I may also be wrong, so if I am please correct me. Its just what I feel after using both kernels so hope I don't get flamed for this. I still love Siyahkernel to bits as much as I love speedmod. Both are great kernels, so I really don't think there is any loss if you use either.
[Galaxy S II General] Entropy512:
Oh, and I finally figured out how to try and duplicate your likely good-signal conditions. While I can't break the laws of physics, I do have a bit of a cheat that lets me effectively reduce RF path loss, reducing the load on the phone's power amp significantly by letting another device do the work:

http://www.amazon.com/gp/product/B0011GI94Q - I have one of these installed in my car. My car unfortunately has a switched outlet, however I do have a 100AH deep cycle lead-acid battery I use for camping (which is how I don't violate conservation of energy while reducing the RF path loss the phone perceives). So in a few nights I might be able to do a strong-signal test run. Right now I feel like crap due to this damn sinus infection though, and that battery is heavy as hell.

Edit: One little tidbit, from the dmesgs I've looked at so far. Our phone DOES take quite a while to wake up out of suspend - 650-660 msec as opposed to 90-150 for the Infuse, suspend entry is almost identical for both phones at around 80-110 msec. That's probably the reason people complain about screen-turnon lag.

In the .14 kernels, it doesn't seem to be entering the ultra-deep suspend state nearly as often based on the dmesg - but yet drain is still pretty good and whatever state it's entering is still considered by CPUSpy to be deep sleep. It may be sensibly using a sleep state that is slightly less power efficient but much quicker to resume from when it knows a wakeup is occurring reasonably soon, but not sure - it could be just that some printk()s were removed to avoid race conditions. Need a lot more time to investigate.
[Galaxy S II General] Molitro:
Entropy512, I'm not going to enter on all of that, but just one thing: You're going on and on on the signal strengh, and I just don't now why.

No one (or no one in he's right mind) is saying tha the signal strengh doesn't affect the battery drain.

This bug isn't related, that's what's being said.

And, other thing:

I must be reading this incorrectly, but if you are saying that is false that there are cases of AOS climing to the roof and evets/0 and suspend taking a lot of CPU time, then you are one off two things:

1 - blind

2 - a troll

because there are plenty of pics showing that behaviour.

On the god-phone thing, hardly we are asking for the phone to brake the laws of physics, when the first SGS actually has the battery behaviour we're asking for the S2.

If without any tweaking at all, with stock kernel, my first S managed 1% every 2 hours with plenty of services on, and the S2, with the same config, barerly makes it to 1% per hour, it's obviously something wrong.

Edit: Actually I have the S2 with a less power consuming configuration, so there you go.

Finally, you are doing yourself a crappy favor with the coments on the lack of proper testing, to then pick a single phone as proper testing.

I'm suffering right now because of my inability to express myself properly in english.
[Galaxy S II General] AndreiLux:
This single sentence invalidates everything you've ever said and simply implies that you're not suffering from the issue, as many have before. More on that a bit later when I write a worthy lengthy reply and show you my dmesg logs.
[Galaxy S II General] aceofclubs:
Im not suffering from the AOS problem on ANY firmware I've used.

There are enough reports on xda for me to conclude that there is a problem somewhere. Just where, no one has convinced me.

If you want to get to the root of the problem someone needs to take control and find the common denominator on each device that's experiencing the AOS problem.

There will be one and it will have nothing to do with any ones ego.

Maybe the op could design a spreadsheet that users could fill out with their setup and send back to him. Pretty sure a pattern will form. Hardware combo, software combo or hardware software combo pattern ???

I'd be surprised if this post even gets seen amongst the pissing contest this thread has turned into.
[Galaxy S II General] Entropy512:
It may happen sometimes, but claiming that all high AOS usage cases is a bug when clearly in many cases it's falsely reporting way high and completely inconsistent with all other evidence is masking what real problems may occur.

Pulling dmesgs and logcats are basic Android debugging skills, anyone flashing custom ROMs or kernels and then whining about bugs without any dmesgs or logcats shouldn't be here, and it's exceptionally sad when someone manages to make the front page and get such a following talking about a "kernel bug" when they haven't even performed the most basic of kernel debugging techniques (dmesg).

If you get high drain, you look for wakelocks. If you don't see wakelocks, then you try to find out why, like I did, and discover that the app you're using hides a lot of ****.

And when debugging, you never trust apps that are either clearly documented by their author as giving inaccurate data, or are closed-source and known to have display bugs.

Not a single I777 user has yet encountered any of the bugs you claim despite our hardware being nearly identical. Every time they've had drain, and an actual proper investigation has been performed, and it has proven in every case to be:

Broken Exchange servers and Exchange email accounts set up

A well-known Hotmail calendar sync problem

A rogue app (Words With Friends seems to be the most common battery hog these days)

They had not yet removed the notorious battery-draining AT&T bloat

It might be some evidence that there's something in our sources that fixes a bunch of the drain situations you've had, but still causes AOS to report high despite low drain unless patching to .14.

Edit: Anyone who is complaining of high drain and using BLN should do the following:

Turn off BLN

Reset CPUSpy counters

Turn screen off for a few minutes

Check deep sleep to make sure you're OK

Then reset CPUSpy again

Turn on BLN

Activate the test notification

Turn off the screen

Wait a few minutes

Check deep sleep statistics - After reading through the code multiple times, I'm more and more convinced that the bug I've had isn't something I introduced in porting and may also apply to I9100 BLN implementations. In short, an active BLN notification inhibits deep sleep and doesn't show in BBS wakelock stats, but will show in /proc/wakelocks
[Galaxy S II General] m2smoe:
Interesting stuff in this topic! Hopefully all this procrastinating and back & forth will let us discover a solution.