yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] They Drew First Blood:
Devil, Voodoo Sound. Battery behavior.

I haven't had much time on Slim or Hellybean so I can't report back about those ROMs specifically, but I have been on the Devil Kernel for a good length of time, with various other ROMs, and I use Voodoo Sound without issue. Have you tried clearing the app data?

---------- Post added at 10:48 AM ---------- Previous post was at 10:37 AM ----------

Askpcguy, regarding the new battery behavior- I wonder if some settings went back to defaults or whatever, when you upgraded the kernel to 1.1.3. I assume you checked your Devil config, and if you use NStools you checked that as well? Most of my Devil settings have stuck after flashing a newer version but typically my CPU freq maxes out. And I do recall issues that shadowcaster mentioned affecting my phone since I went to ICS. I double checked last night and I still get this behavior of charging the phone when it is powered off: the battery charge image comes up on the screen, but a while later after the screen has turned off the phone is unresponsive. I have to long press the power button to get the screen alive again. However in my case it still appears to have charged, but I would need to look at that further to verify. I use the phone as a USB tether so often that I have stopped paying attention to the charging, to be honest. It spends many hours plugged in to the PC and rarely falls below a half charge, even with my BLX (battery life extender) set to 90%.
[Captivate Android Development] dchawk81:
I have had the same charging issue on ICS for awhile now regardless of the kernel or its settings.

I also lost access to the Galaxy S settings (they're all greyed out) at some point but I don't know when that was as I rarely accessed them.
[Captivate Android Development] jecsah:
I was having frequent, random reboots with .60 I've been running the .56 that you posted this morning without a single hiccup or reboot. Seems to be quite stable with liveOC too, my phone is exceptionally picky about that.
[Captivate Android Development] brianray14:
Bizarre.. Still running .6 without issue. My phone has never run this well with any ICS

Sent by billions of neurons firing simultaneously
[Captivate Android Development] DerTeufel1980:
Maybe your phone is chuck Norris :D

But of course I am glad that it is running well for you :)

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Captivate Android Development] kevinnol:
Same here no problems :D

but i miss the wifi and fsync thing on 0.60 :P

0.56 running quite well though
[Captivate Android Development] Nick0703:
Yeah, same here. Didn't get any problems with .6. I'm been running on it since last week.
[Captivate Android Development] DerTeufel1980:
Next one is having it, and even more :)

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Captivate Android Development] Austin Ag06:
Can we use the 90callvolume script with Devil kernel?
[Captivate Android Development] tallsilver:
Same here. With Docs 11. Great battery life as well.......
[Captivate Android Development] mindphaser2k9:
That would be very very cool, because Captivate voice volume is too low. But this is supported only with Glitch, so let's be patient ;)
[Captivate Android Development] Austin Ag06:
Thanks I didn't know that was proprietary to glitch.
[Captivate Android Development] dongfangri:
Just want to increase the speaker volume in handsfree mode of a phone call.
[Captivate Android Development] s0ul_ali:
Battery life is extremely better then glitch & semaphore. I'm loving it, but sound it bit low.
[Captivate Android Development] DerTeufel1980:
well, there have been no issues, with both of my test kernels from yesterday? great :)
[Captivate Android Development] prbassplayer:
I'm about to flash the B kernel now and use it for the rest of the day. Will see if anything changes first one locked on me once but I blame NSTool.
[Captivate Android Development] DerTeufel1980:
I am already running the "next" release since yesterday. No issues till now. But I am only one tester ;)

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Captivate Android Development] Monfro:
Today i tested both of them and had no issues at all.

Seems like B version is a little bit smoother, but on 3.0.8 version seems like you can overclock in a stable way a little more.

I did not performed professional test, but liveOC on 3.0.8 maybe is a little more stable than 3.31.

Anyway 3.31 is smoother on its own...
[Captivate Android Development] The_Wolf91:
Hi thank's for this Kernel (I was waiting it), I'm on last CM9 Nightly and I'm having random reboots with ALL Kernel's versions posted here. Never had a random reboots with Glitch Kernel, so here it is my "last_kmsg" after a random reboot with Devil Kernel.
[Captivate Android Development] nicholishen:
I am running myui and was formally running weui ROM. I have noticed that listening to music is fine, but as soon as I take a call with headphones in, I get some background static noise. It does not do it through the handset on a call...only when headphones plugged in on a call. I had the same issue with with glitch and semaphore. Any ideas? Does anyone else have this issue? Sorry if this is the wrong place for this question...I just assume that it is a kernel issue. ..I could be wrong, I usually am :)
[Captivate Android Development] martinomac:
+1

10chars
[Captivate Android Development] s0ul_ali:
I'm on 2_0.55 since last night great job buddy. My room is WiUI 1.0 over all kernel is very smooth But some wired issues with clock , twice I have relaunched desktop clock widget and now status bar clock is stuck.
[Captivate Android Development] jdogg21:
I have no charging issues running RemIcs with Devil 3_1.1.0
[Captivate Android Development] They Drew First Blood:
Galaxy S settings

Maybe you flashed a _VC version of the kernel rather than a _CMC? (Take a quick peak in Settings -> About Phone -> Kernel version)

Galaxy S Settings would only apply to the CyanogenMod Color version of the kernel, and not the Voodoo Color version. I'm on the VC version and Galaxy S is greyed out for me too. I'm liking Voodoo Color because it is tuned pretty nicely by default, and I just have to switch it to Punchy gamma settings to get the colors to where I prefer. I had to fool around with the CM Color a bit too much and by default it was jacked all the way up.
[Captivate Android Development] dchawk81:
I definitely flashed a VC version. I didn't realize that would do it. My bigger concern is not being able to control the radio like I used to...ie HDPA/3G/2G. It's not a huge deal, but sometimes it's helpful to force the slower connections.
[Captivate Android Development] They Drew First Blood:
3G 2G

I thought that was ROM-specific, but I have been wrong in the past... or maybe supported by whichever modem is currently flashed? Have you been able to control that through another kernel?
[Captivate Android Development] dchawk81:
I used to control it with the same ROM but I don't remember which kernel it was. I was thinking it was an early Devil.
[Captivate Android Development] DerTeufel1980:
You still should be able to control it. Vc kernel does not affect this... Please try deleting app data
[Captivate Android Development] dchawk81:
I did that before and it didn't work. Tried it again and still nada. Now I do have mDNIe Mode, Backlight Timeout, and TV System but everything else is greyed...Color Tuning, Radio, and TV Out.
[Captivate Android Development] DerTeufel1980:
Have you removed Samsungservicemode.apk?
[Captivate Android Development] They Drew First Blood:
Galaxy S Radio

Hmm, on both HellyBean (JB) and F4k (ICS), both with Devil VC kernels, I still have access to the Radio entry in the Galaxy S settings. Only setting greyed out is the Color Tuning. (Well, TV Out is grey but I'm assuming it is like tethering in that once a cable is connected it will be available.)
[Captivate Android Development] dchawk81:
Well I didn't but I just looked and it seems the developer did. D'oh! It must have been a previous version of the ROM that let me do the settings. It's all kind of a blur anymore.
[Captivate Android Development] tkjeeper:
Which devil version can I use with the new cm10 release? Thanks
[Captivate Android Development] prbassplayer:
None as of now.
[Captivate Android Development] RootTheMachine:
Obviously not the ICS ones, but why not the JB kernels that don't have /datadata?
[Captivate Android Development] tkjeeper:
That's what I tried, the latest jb was 1.1.3. I understood it was for cm10, but I was wrong. Lol.
[Captivate Android Development] mindphaser2k9:
It was for earlier cm10 but not since 0817.
[Captivate Android Development] prbassplayer:
You are right. Pawitp changed the partition layout of CM10 (and supposedly fixed slow NAND lag) so none of DerTeufel's kernel will work until he builds from the new layout.
[Captivate Android Development] They Drew First Blood:
JB kernel 1.2.1

There is a new Jellybean kernel up:

http://rootaxbox.no-ip.org/derteufel/jellybean/

I don't know whether this would work for CM10...

Edit: Thanks melvinaury

*facepalm*
[Captivate Android Development] melvinaury:
Just go to the jb thread, and yiu foubd the answer.
[Captivate Android Development] They Drew First Blood:
Devil3_1.4.1_ICS released Sept. 6, 2012

Nice to see another ICS version released:

http://rootaxbox.no-ip.org/derteufel/ICS/Cappy/141/

Thanks yet again DerTeufel for giving us ICS users an update to play around with.
[Captivate Android Development] DerTeufel1980:
New version is hopefully coming soon :) there always are too many things to do...

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Captivate Android Development] uhm:
Hello, I loaded LANIGHTV.6.0 rom on my i897(Captivate). After installing it successfully, the screen becomes predominantly blue after the boot animation...almost as if all the screen colors are mixed with dark blue. It is like having a dark blue back light instead of white. I found a video on youtube that someone made after loading CM10 on their Captivate. This problem seems to exist on i9000 as well.

http://www.youtube.com/watch?v=wwMqqMJK7cM

I read somewhere that this problem is related to using Nexus S Framebuffer. It was stated that for some devices, the color calibration data is invalid and that causes this blue color problem. I don't know how far it is true but I'm just stating it here thinking that it might be useful information.

Hope this issue will be fixed soon. Or if there is a work around, please let me know. It would be greatly appreciated.

Thanks a lot in advance!
[Captivate Android Development] DerTeufel1980:
I am sorry, but I can't help you with it. Pawitp wanted to fix it some time back, but maybe he forgot it, or did not have enough time.

Have you tried the voodoo color kernel, and playing with the values?

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Captivate Android Development] uhm:
Thanks for your reply. I tried the voodoo app. It helps a bit but the screen doesn't look good with those colors unfortunately. If and when Pawitp fixes the problem with Nexus S Framebuffer, will it be integrated in this Kernel also? I thought he maintained the Kernel that is used with CM.

I have found that this problem exists for all the kernels that I tried (devil, glitch and semaphore) for JB and ICS rom's. I wish the use of Nexus S Framebuffer was optional.
[Captivate Android Development] DerTeufel1980:
All those kernel are using the nexus framebuffer, cause pawitp implemented it. If he could fix it, stratosk and me also will implement it

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Captivate Android Development] uhm:
Thank you for your reply. Since I'm a newbie here I don't know how to make a request to pawitp to consider doing that fix. I sure would love to have him fix it. You're right perhaps he might have forgotten about it.

May I request some thing? If it's not too much to ask, would you be kind enough to provide an option to fallback on the framebuffer that was used before the Nexus S Framebuffer implementation via settings? I'm sorry if it's an unreasonable request. I'm sure many people like me would appreciate it very much if that option was available.

Thanks again for doing such wonderful work.
[Captivate Android Development] DerTeufel1980:
About the request to pawitp, you could write to his thread first, and tell him about the issue. You also could use the cm10 bugtracker, for submitting it.

It's not possible to change the framebuffer after compiling it

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Captivate Android Development] uhm:
Per your suggestion, I wrote about that issue for CM10 and CM9 both. Haven't received any response yet. I read somewhere that pawitp was going to be busy for a foreseeable future. Therefore I'm not sure if the fix for this issue would become available or not.

If it's not an unreasonable request, would you please consider compiling a kernel version without nexus framebuffer? That would allow people like me to enjoy hellybean/slimbean rom. Thanks a lot.
[Captivate Android Development] DerTeufel1980:
I am not sure, if this can be done easily, as there have been other important changes, which probably base of this one (things like vsync could... Then it wouldn't work anymore). I am sorry, but I try looking at it.

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Captivate Android Development] uhm:
I really appreciate your willingness to look into things and I really am impressed by your such quick replies. You always respond so quickly. Thanks a lot for that. Whether or not this is done, I still would like to thank you sincerely for your willingness to try and help others. I was hesitant to make that request to you because I wouldn't want to burden you with something that can't be easily done.
[Captivate Android Development] uhm:
I was just wondering if you had a chance to assess if this can be done easily or not. Not trying to be pushy, just curious. Sorry!
[Captivate Android Development] DerTeufel1980:
No, I am sorry. I am always hoping to find some time, to try some things, but in the end, I didn't...
[Defy Q&A, Help & Troubleshooting] the-xda-guy:
Hello guys I'am new on xda and i want to know how to translate a rom in french.:confused:
[Desire General] bubu.:
hey there,

when i deactivate the air plane mode, there's simply no pin input dialogue being opened... so i always got to reboot my phone :(

any ideas? im using latest gingerbread...

thanks
[Desire General] MatDrOiD:
Did you root, S-OFFed, etc. your phone? Or using official Gingerbread by HTC?
[Desire General] bubu.:
root, s-off, using oxygen :) but also was the same before rooting...
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] Sarathdna:
Hi Guys,

I need a help out here with HD2 Pdaimatejam Rom Wp7.5 Tango 7.10.8773.68 v8. After installing the rom the Audio/Sounds/Ringtones having Noisy sound. Plaease help me to fix this issue if sumone is able to....

Rom is awsome n i want to b in this...

Thanks in advance....

Sarath
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] dxdy:
sounds work fine for me...
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] hjhjhj:
try reflashing again or hard reset. you should also post your rom specific question in the particular rom thread instead of general thread. you'll get more feedback.
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] Sarathdna:
Hi

I tried refashing n hard reset. but few ringtones r still same. like Nokia tones n all.

And what is this SOUNDS-FIXS.cab for???
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] hjhjhj:
again...go read up on soundfix.cab and post your question on the rom's thread not here. you'll get more feedback.
[Desire General] bubu.:
hey,

sometimes the desire juts doesnt switch from wifi to mobile connection when i was connected to a wlan/wifi... when i reboot the phone, it's directly connecting to the mobile data connection.

heard of others facing the same problem, is there a solution?

thanks a lot
[Desire General] erklat:
Both issues too important to be asked in the same thread?
[Desire General] bubu.:
most boards want to separate subjects to make it searchable better... so i thought this would also be the case at xda..
[Desire General] erklat:
Thinking out loud - that would be a lot of YAUTAI subjects if it was your way :eek: :D
[Xperia Play Q&A, Help & Troubleshooting] dragondarchy:
Hi ,complete "noob"here so really hoping soeone can help me!

Problem is i have an xperia play (

tried to flashboot it ,it always stopped @14% .

now since i have tried this my mobile is playing up,turn on ,its ok,then soon white lines appear across the screen and i cannot operate the mobile,turn off ok for a while again.

what i have tried to do to solve this ,is phone repair through sony pcsuite,no joy.

Its the xperia play r800i

android version 2.3.4

please i hope someone can help,and remember i am a noob so please put it simply :) Many many thanks
[Xperia Play Q&A, Help & Troubleshooting] CTU_Loscombe:
Flash the original 2.3.4 firmware back on using Flashtool.

www.xperiagamer.com has the firmware update somewhere
[Xperia Play Q&A, Help & Troubleshooting] dragondarchy:
hi, many thanks for your advice ,just before i download the stock f/w ,which one do i choose?

2.3.4 xperia play r800i software tft file version 0.283

2.3.4 xperia play r800i software tft file version 0.42

2.3.4 xperia play r800i software tft file version 0.58

2.3.4 xperia play r800i software tft file version 0.62
[Xperia Play Q&A, Help & Troubleshooting] dragondarchy:
flash tool says device

connected with usb debug mode off

when evenyually flashmode ,choose ftf file ,start ,flash cancelled ,what am i doing wrong!thanks for your time
[Xperia Play Q&A, Help & Troubleshooting] CTU_Loscombe:
Go into settings and turn USB debugging on. It's under applications, development options.
[Defy Q&A, Help & Troubleshooting] jalal-jap:
Can I Use Defy + Battery For Defy Green Lens?
[Defy Q&A, Help & Troubleshooting] lestercoloso:
sure
[Defy Q&A, Help & Troubleshooting] jalal-jap:
and defy+ battery charge with defy green?
[Nook Touch General] Fuda163:
Hello everybody. I need a help with next situation.

I bought my nook like month ago and rooted it with TouchNooter after a couple of days. Everything worked fine for me - coolreader + goldendict, wi-fi, everything. One thing that did not satisfy me was energy drain, so i tried to install another ROM with "minimalistic" package on board. Before i switched i did factory reset and factory restore - my nook has 1.1.0 stock version on board. Unfortunately i discovered that "minimalistic" ROM does not contain android market - so i would not be able to install GoldenDict properly (because programme askes for license check). So i decided to revert back to TouchNooter (with factory reset and restore ofc).

Since then my nook keeps freezing all the time - whatever i do - its just freezes.

If Im trying to read a book with both default reader/coolreader - its freezes after couple of pages. If Im trying to press settings - its freezes again. And it wont boot up without power supply - i need to plug my nook via usb to my PC or to jack.

With energy supply it works fine without any random freezes, reboots etc.

I made a conclusion that its not about ROM (i tried like 30 times factory reset/restore. I tried both versions of n2T Recovery. I tried to use Touch-Formatter.) My device keeps freezing even totally unrooted -i have to plug my device into PC in order to complete registraion process - otherwise it will freeze before my attempt to connect. My nook cant work on its own - it should be plugged in into power source.

So i tried to charge my nook more than it requires - i left it charging for a day with jack. after i unplugged it battery stats shown me 100%. I started to read. Notably that i spend half day reading and using goldendict without any problems, but when my battery drained to 93% my nook started to freezing again.

I just dont understand what is the problem. Why does my nook work fine with cable and cant live without it? One thing i did not do yet is to disassemble my nook and trying to unplug/plug battery - i dont know how it can help but i dont have any options left...

I hope you guys can help me coz i've tried to find same problem and haven't succeeded. Thank you!
[Nook Touch General] Nova5:
Most battery systems require calibration. To do this you need to charge it to full, drain it to low power.. around 10%. 3-4 times is the usual number needed. It sounds like you are having some sort of battery problem and calibration may make the meter read properly. Otherwise it might be time to try for a warranty replacement.

Every time you change roms you need to allow for the calibration period again.
[Nook Touch General] Renate:
I doubt that the battery calibration is that far out, but you can try:

am start -n com.android.settings/.BatteryInfo

That will give you all the numbers on your battery.

Voltage goes from a high of 4.200 to about 3.800 as dead.
[Nook Touch General] Fuda163:
Thank you Renate, but how do i perfrom this and what should i do with all this numbers?

To Nova - i cant charge/recharge my battery several times in order to re-calibrate it - because as i said it simply freezes once been plugged off
[Nook Touch General] Renate:
That was a command you type in a shell on the Nook, normally over ADB.

You do have ADB working?

It sounds like your battery has simply had an early failure.

I'd try restoring it to stock and returning it under warranty.
[Nook Touch General] Fuda163:
This teleir

I think i'll just return it...but im afraid that other device will have same issue...hope its not that regular
[Nook Touch General] Ret-mc:
mine too

I'm also experiencing freezes with my NST (rooted 1.1.2). It has 1 1/2 year with light use (approx 30 mins per day).

Whenever the battery reaches 95-80% my nook would start to freeze.

I've tried using "Battery Calibration" app to restart the battery counter but it didn't help.

I know it's a battery related problem but I wouldn't say it's a hardware problem because it doesn't show the "too low to power on" message. Show I unroot my Nook?

Any suggestions?
[Nook Touch General] ladykayaker:
Did you try looking at your battery info - as Renate shows in post #3

in adb shell :

am start -n com.android.settings/.BatteryInfo

Voltage goes from a high of 4.200 to about 3.800 as dead.
[Nook Touch General] Ret-mc:
I'm checking with Battery Calibration app. It now shows 96% and 4033mV

I'll recheck it on the next freeze.
[Nook Touch General] Renate:
Well, clearly that's wrong as 4.0 volts is not 96%

Can you charge the thing to around 4.200 volts?

Run the battery calibrator reset only when it's at 100% (or so they say).

Does the battery health indicator say good?
[Nook Touch General] Ret-mc:
Yes, the battery health reads good. I reset the battery calibrator when the actual led light turned to green (my nook was showing 100% a lot before that).

Today the battery was showing 93% and 4014mV.

I maybe onto something. I experienced something weird. I kept reading using the official nook app and checking from time to time the battery app. It was always somewhere 92-93% and 4014-4012mV. Seconds after I highlighted a word the nook froze. I rebooted and immediately I read the battery app. I read 92% 3895mV. I waited a moment and then it went back up to 4010mV.

It seems there something going on on CPU intensive tasks. I wonder if the battery is acting weird or there is some task that misreads the battery status ands freezes the device.

What do you think?
[Nook Touch General] Ret-mc:
I've found this suggestion in Mobileread forum

http://www.mobileread.com/forums/showpost.php?p=2186779&postcount=103

I opened my nook, disconnected the battery and put all things back. So far it seems the freezes are gone. I'll report any problems!
[Nook Touch General] ztryfe:
I've doing this for a couple of months now (once every 2), no freezes anymore.

Perhaps the NST power handling firmware has a bug? Been seeing this issue fixed by that on several forums.