yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] DiRT_360:
Thanks Novic, for your awesome work.

Battery life is perfect.

1 day and a half, still 75% of battery.

Rom: PixelRom 1.60

Kernel: Beta 3

CPU: 1440 + 105 liveoc = 1512

Volt: Default

Use: Regular, some calls, game, sms, etc.

Screen on attach.

Now i will try Beta 4.
[Nexus S Android Development] S_Dot:
Thanks for the update, is the default 50 or 60FPS refresh rate? I mean, what did your previous kernels use?
[Nexus S Android Development] y3mita:
flashed beta 4 and when charging with other governor than default it powers off.
[Nexus S Android Development] thegtfusion:
:o how the hellll do you get such battery life at 1.5 ghz?????? :eek:
[Nexus S Android Development] y3mita:
also with default governor not changing nothing phone powers off when charging to wall.

---------- Post added at 02:10 AM ---------- Previous post was at 02:01 AM ----------

I had to remove battery in order for phone to boot up... I am now charging my phone powered off.

Anyone with this same problems? Is there a solution?
[Nexus S Android Development] navillos:
Yup beta 4 has the sleep of death. Have to do a battery pull when the screen powers off.

Also for SnG I was using the 50hz version.
[Nexus S Android Development] simms22:
sounds typical of a little too much undervolting. some phones might handle it alright, while others sod.:
[Nexus S Android Development] y3mita:
Default values though, and I checked the voltages and they are not UV at least they looked the same as Air_Kernel and I run that kernel just fine.

I hope once the phone is charged I'm able to turn phone on and I don't get the SoD it'd be a shame.
[Nexus S Android Development] DiRT_360:
Same thing there, every time screen is of, i have to pull off the battery. i think it's SoD.
[Nexus S Android Development] y3mita:
I went back to Air Kernel, will wait for this one to get stable.
[Nexus S Android Development] :
Beta 4 benched!

http://xdaforums.com/showthread.php?p=23597641

Has sleep of death issue at the moment. Do not flash!

novic_dev, do you preserve ro.secure=0 from Eugene's source?
[Nexus S Android Development] novic_dev:
Hi for all!

Thanks for testing!! The results of testing are very useful for me!!!

Sleep Of Death is proved on Beta 4 :(

Will correct stability issue today!
[Nexus S Android Development] novic_dev:
"ro.secure" is setting during the boot time, by default it is enabled (=1)
[Nexus S Android Development] novic_dev:
Ok, I'll try to fix all stability issues today evening...

I'm also working on rebasing the AniDroid-Hardened kernel on the latest Linaro Linux 3.3 RC3 Source.. So, hope to see the results very soon! :p
[Nexus S Android Development] lolokman:
WOW, beta4 is exactly what I want. I have been waiting for a kernel with 50Hz or even lower reflash rate for long long time.:p:D

Hoping there will be 45Hz and 40Hz versions.
[Nexus S Android Development] novic_dev:
Thanks! I'll try whet the Kernel will be stable with all other features included ;)
[Nexus S Android Development] tjackbjorn:
Make it stable as hell at ~1300mhz and put in deep idle! It would be a perfect kernel!:D
[Nexus S Android Development] novic_dev:
Hi for all!!!

Please try Beta 5, it's very stable for me now.

This Beta includes also an 45 FPS and 65 FPS versions that allow us to compare the performance and battery life differences between them, thoose the best.

The previous versions of AniDroid (till Beta 4) uses 60 Hz screen frequency.
[Nexus S Android Development] y3mita:
Are these undervolted? I flashed both and I can't boot phone up. I had to remove battery!!

But you say it is working fine?

Anyone else managed successfully?
[Nexus S Android Development] novic_dev:
Beta 5 uses Stock voltage values, both versions boot and work without any problems for me :confused:
[Nexus S Android Development] y3mita:
Really weird been flashing kernels forever but no luck with beta 4 & 5!!

I'll wait for other reports
[Nexus S Android Development] RcrdBrt:
Why don't include blx? With blx it will be simply perfect. I think you can call stable the last release you did.

Inviato dal mio Nexus S usando Tapatalk
[EVO 4G Q&A, Help & Troubleshooting] epena2:
I cannot do anything with my phone. It freezes and locks up and sends me force closure messages with any application and with the launcher. I don't know what to do. I didn't root my phone (a friend did it for me about a year ago) and never updated anything. I need help. Thanks
[EVO 4G Q&A, Help & Troubleshooting] moreno4xl:
If you provide more info it'll be easier to find out what the problem is...
[EVO 4G Q&A, Help & Troubleshooting] -EViL-KoNCEPTz-:
Since you are rooted try going to recovery and wiping cache and dalvik cache 3x each if that doesnt work you may need to flash a new rom stock rooted if you like stock or a custom rom if u choose to go with something a little different for custom roms id suggest the classic by tommytomatoe if u like sense 1.0 or mikg v3.0 or v3.1 uf you want to try sense 2.1 with 3.0 elements like the lock ring both have good support and lots of themes addons tweaks and customization
[EVO 4G Q&A, Help & Troubleshooting] marcusva79:
Fixing permissions via rom manager or recovery (other, uid mismatches) helps fix fc's
[EVO 4G Q&A, Help & Troubleshooting] epena2:
Whenever I try to enter recovery it fastboots. How do I turn that off?
[EVO 4G Q&A, Help & Troubleshooting] plainjane:
Pull the battery first.
[EVO 4G Q&A, Help & Troubleshooting] marcusva79:
Pull out battery and volume down and power at same time. It will take you to bootlaoder and the choose recovery. Should help ya.
[EVO 4G Q&A, Help & Troubleshooting] ihugyou:
Hopefully you did an Android backup. If not you can just use USB through amon ra in recovery and download a stable from.
[EVO 4G Q&A, Help & Troubleshooting] epena2:
Whenever I enter Hboot it gives me the following options:

Fastboot

Recovery

Clear Storage

Simlock

Hboot USB

When I try to enter recovery it gives me these options:

Bootloader

Reboot

Reboot Bootloader

Power down

Any suggestions?
[Motorola Droid Bionic] Penguinrocker:
My computer wont install the drivers I need to connect my phone, any one had this problem
[Motorola Droid Bionic] Bfitz26:
What happens when when you try to install them??
[Motorola Droid Bionic] Penguinrocker:
Come back with error %public% \desktop\
[Motorola Droid Bionic] Bfitz26:
hmm. i know on my laptop i had huge issues different cables different.. ports wiped phone went to stock etc.. at that point restore my computer to "stock" and that was the problem best of luck...
[Motorola Droid Bionic] sgschwend:
My laptop does not recognize the Bionic. The drivers installed fine. I even installed the previous version of the driver still no go; the driver did find the newer version and ask me to start an update.

I also have an older tower running XP and it does find the Bionic. However, this tower is so outdated that other problems occur, so using it is not an option.
[Motorola Droid Bionic] Penguinrocker:
Thanks ill keep playing with it till it works
[Motorola Droid Bionic] priddyma:
Did you try downloading the drivers from Motorola instead of letting your PC find them?

If you're running 32 bit windows - http://developer.motorola.com/docstools/USB_Drivers/Handset_USB_Driver/

64 bit: http://developer.motorola.com/docstools/USB_Drivers/Handset_USB_Driver_64/
[Motorola Droid Bionic] Penguinrocker:
Yeah comes up with the same window during installation, can not locate %PUBLIC%\Desktop\,
[Motorola Droid Bionic] sgschwend:
I tried a different laptop but the same model number running Vista instead of Win7. No happiness here. My drivers downloaded fine, but the PC does not recognize the Bionic.

Nothing shows up in the device manager.

As I said before my old Dell using XP does recognize the phone.
[Motorola Droid Bionic] cruiser86:
motorola drivers

having same problem with moto drivers in windows 7 computer. downloaded drivers from moto 64bit & the computer said I already had them installed but in devices I have the "!" mark on the mot driver. can't re-root without these.
[Galaxy S II Q&A, Help & Troubleshooting] ASKnASK:
It is a common belief that SAMOLED has no backlight, which is true. However, the screen IS powered and hence there is SOME energy that generates a teeny tiny amount of light.

This can be checked by using the *#0*# and doing the Vibration test where the screen goes totally black.

I'm talking about a VERY VERY faint and very uniform glow from the screen.

Try waving it in front of your face if you don't see it.

Report back.
[Galaxy S II Q&A, Help & Troubleshooting] ndnesh:
Hi,

Yes. Even I have noticed this when I am using the cell in night and in a completely dark room. I am not sure about the SGS 1'S screen, but in the S2 I have seen a very faint glow which is present in the backs even when there are other elements colors present on the screen. It's my opinion that there is some amount of backlight that is being used for the black.
[Galaxy S II Q&A, Help & Troubleshooting] roughavoc:
Both the i9000 and i9100 have a faint glow when nothing is being shown on the screen
[Galaxy S II Q&A, Help & Troubleshooting] Gambler_3:
I havent seen any glow just how "teeny tiny" are we talking about here?? If you keep reasonable distance from the screen then it is perfectly black. Watching a video with black bars in a completely dark room the blacks are literally indistinguishable from the bezel.
[Galaxy S II Q&A, Help & Troubleshooting] ayhamx360:
so far i had 3 galaxy sII devices the last one was the white color

all of them had the same thing ur talking about in complete darkness
[Galaxy S II Q&A, Help & Troubleshooting] jeroensk:
Yes both the i9000 and the i9100 I own have this, you can also spot it while just turning on the phone before the boot screen, but I only notice while in a dark room or at night.
[Galaxy S II Q&A, Help & Troubleshooting] mengsuan:
The faint glow is there because the pixels do not totally power down when displaying black. The screen is designed this way to give better response rate. No one wants a screen that ghosts isn't it :o
[Galaxy S II Q&A, Help & Troubleshooting] Archer:
You only see it on a fully black screen. As soon as there is anything on the screen your eyes compensate for the light and you lose sight of the black. Try it as the OP suggested and you'll see it.
[Galaxy S II Q&A, Help & Troubleshooting] Gambler_3:
Okay so we are talking fully black screen.

So while watching videos, playing games or having a black wallpaper(with obvious widgets or icons on top) the eyes would perceive it as pure black as I have experienced.

So for all practical purposes the contrast is infinite. OP you shouldnt worry about some glow on a fully black screen. I can tell you for sure that even in totally dark room lets say you are in the ICS app drawer you will not be able to see any glow between the icons, it would seem like the icons are flying in the air. The magic of SAMOLED. :)
[Galaxy S II Q&A, Help & Troubleshooting] electropineapple:
Yes, there is a faint glow. But its only noticeable when you're in a completely dark room and your screen is showing only black.

However that does not in any way mean that SAMOLED+ doesn't have perfect blacks.

The glow is there only because the pixels aren't actually powered off (at least that's what I think)

The contrast ratio is still infinity.
[Galaxy S II Q&A, Help & Troubleshooting] hussainmushahid:
The OP made this thread to prove a point, just checked and YES there is a faint glow in complete darkness.
[Desire General] MetinKale38:
Hey,

My desire shutsdown itself at 13%. The Desire HD of my brother shutdown at 0-2%.

Ive tried to reset batterystats but it doesnt help.

What can i do?
[Desire General] erklat:
Gee, I can't tell.

How about googling about it first?
[Desire General] MetinKale38:
It was Same on stock rom as i bought it newly (before 1year), it cant be because its old, and Ive calibrated it too, more Tipps i cant find there,
[Desire General] thesavagedonkey:
It is a problem with the battery stats. HOWEVER. I've read somewhere (cant remember where ) that even though its an annoying problem. Re-setting the battery stats will not improve battery life. It will give you a more accurate representation but the battery life will stay the same.

Instead of messing around ressetting stats just remember that 13% = dead battery.

just my 2c
[Desire General] MatDrOiD:
Some batteries shut down with 13%, some with 20%, some with 1% and others with something between. As long as you did not notice a strange battery drain, I would just stick with 13% = dead battery (as already mentioned).
[Desire General] MetinKale38:
Ok, i asked because i thought it isnt normal. Thank its ok.

Thank you
[Desire General] daniel_pt:
I guess it depends on the battery. I have one that goes almost until 0% and I have another one that holds only until about 11% or so... 13 is not that bad!
[Desire General] john479:
My desire did this, except it shut down at around 20%. I just bought a new battery, not even an official HTC one at this fixed it. Now it shuts down at 0-1%.

So basically, its just the battery imo. My battery was about 1 1/2 years old and had seen better days.
[Desire General] masterdam79:
Used to have this problem

When I used CM7.0.3 I had this problem, now running LeeDrOiD HD 3.3.3 with Sense 3 and it only shuts down at 2% or less.
[Desire General] forenheith:
i have same problem too
[Desire General] pechano:
same here

Mine used to do this aswell. Reboot to recovery and clear battery stats? Then full charge and full discharge.

Worked for me at least.
[Desire General] erklat:
Mythbusters to the rescue.
[Desire General] Tarinder:
Like every desire user am having this problem too. I often switch between roms. Even after resetting battery stats my desire dies at 15% battery.:confused:
[Desire General] dan281082:
http://forum.oxygen.im/viewtopic.php?id=723

calibrate the battery ****s down at 0% then
[Desire General] in1400:
I think, you have to reset the Battery Stats. For me it helps!
[Desire General] erklat:
Lol.

It is not a problem any longer since theGanymedes published his great guide.

Notice how he never mentioned wiping battery stats? :D
[Desire General] _snIP3r_:
same here

... buit how can i fully discharge the battery if it shuts down at 13 or 20%? even if i restart the phone, it shuts down again :confused:
[Desire General] Gr4v3:
Mine just shut down between 45% - 48%.

Ordered a new one
[Desire General] Vous.Thal:
Same here @ 18%, going to test some methods and inform you
[Desire General] Tsjoklat:
You need to recalibrate the registers in the battery. There is a special program that does that.

Use this howto and it will be fixed.

http://forum.oxygen.im/viewtopic.php?id=723

BTW, you need to have Cyanogenmod or Oxygen installed for this to work or a distro with a kernel that supports it.
[Desire General] pwatk:
I've just done this to my phone and I can confirm it works as it now shutsdown at 0% instead of 13%.

This post pretty much sums up everything that was learnt by theGanymedes (and others) in the entire thread.

Here's my advise:

1. Don't use a sense rom as the power drain is too high and you'll find the phone will cut out before it starts charging (even after you've plugged in the cable). Use Cyanogenmod (or Oxygen) and this app. You can work around this but it's a pain in the neck.

2. Read carefully the section entitled Make the calibration permanent (thx to user "theGanymedes") as this is the bit that will solve the problem.

3. I did read somewhere that once you have set the new Full40 value it is a good idea to discharge and recharge the battery again but in reality you only need to drop to 80% and then charge back up. This may not matter at all but I thought I'd mention it.

4. When you do finally discharge the battery to empty (or charge whilst the phone is off) your battery's age (Batt Age %) will increase to 94% again (the default) but you can safely ignore this so-long-as you've set your Full40 value correctly above.

5.

Do

enable the advanced options in the app's settings else you wont see the option to send values to setreg in the LearnPrep tab. This may be self evident but I've seen a few people caught out by it (including me :o).

Hope this helps.
[Desire General] baschelik:
This is really helpful, great job, man....
[Desire General] Shmarkus:
13% == 0%

;)
[Desire General] facade:
Try checking the battery health by dialing *#*#4636#*#*
[LG Optimus Black] Huexxx:
Hi all!

Let's begin thanking to dxdiag32 all the efforts to get the original lockscreen to our blackies...

This mod is SO SIMPLE.

You have you edit your build.prop, and replace the line...

user.feature.lock_sui=true

... with this one ...

user.feature.lock_andy=true

That's all folks!!!

It will work with all versions of Gingerbread, and hopefully with all versions of Froyo.

Regards!!!
[LG Optimus Black] gabwerkz:
Wow good find...
[LG Optimus Black] Huexxx:
All the problems with Zeus finally worth for something...
[LG Optimus Black] t0g3:
very very simple :eek:

nice find :D
[LG Optimus Black] gabwerkz:
Yeah man. Hope all be fixed. Want to help but I'm on my own ROM ATM. With my experience, just a sudden freeze with zeus.

All I can do for now is... With the V20N ROM I'm using, I don't have any. Even comparable to your performance.

What I can tell you is, I don't have .ko's, patches (libsqlite), only themed apk's, untouched .jar's. init.rc is tweaked, init.omap.post_boot is heavily tweaked.

Before I touched boot.img, I used init.d, it generated me automatic 00something and another one. I placed scripts and they work. Removed some and placed them in init.omap.post_boot.

Hmm, aight... I'll flash V4.X and edit it. And will let you know the results. I will remove what I think is the cause and that includes .ko's and orig files (gps, apk's, .jar's) etc.

Regards!
[LG Optimus Black] Felsar:
Indeed it works, but text is messy when reciving a sms, look at this....

hey, I'm not complaining... just telling you and want to know if there is a way to move text down is it will be more visible??
[LG Optimus Black] Huexxx:
Ops, maybe LG guys abandoned andy lockscreen and it have bugs... I'll look into it in my own ROM...

Thanks for the tip.

And Gabwerkz, thanks for the tips, I'm tasting the begin to begin procedure... right know I NEED to know where the problem is...

I would come back...
[LG Optimus Black] achyut:
dunno what actually is the problem,but i have used ZEUS from day 1 till today(i.e., 4.02b). i never ever have faced ANY problem. it's as stable as the stock GB rom, but a hell lot faster.

maybe am an offshoot lucky??:confused: :confused:

any views???
[LG Optimus Black] Huexxx:
Yeah, you must be lucky... I've had one or two issues, people with lots... and the best... trying to catch the problem, I've made two ROMS from scratch with almost nothing added and the people have problems!!!! I don't know if cut my veins or leave them long...

Regards.
[LG Optimus Black] achyut:
LOLZZ :D :D :D....i'll count on my luck then :D :D
[LG Optimus Black] N00BY0815:
Add me to the lucky ones. Only had one in Zeus 4.02b, but dunno where it came from, but after that nothing more. Must have been a buggy install, since I always customize your ROM a bit according to my taste and first then flash them ;) :D
[LG Optimus Black] Felsar:
uhmm guys why are you talking about if there is [or not] a problem with zeus?? there is a thread for that already isn't it?... anyway the text issue I post before is gone, don't know why since I did nothing, but here is fixed [don't ask me I didn't do it, it fix itself somehow]
[LG Optimus Black] Huexxx:
It happens with alarm and charging related info...
[LG Optimus Black] dxdiag32:
ha,i tried this with a little difference so i failed,i just changed the 'true' to 'false',and i face a bug that can not unlock.

your method works great!thanks! :D
[LG Optimus Black] mauka:
I have so far is 2.2.2. There is no such line, but there is a line:

user.feature.flex = true

user.feature.lgdrm = true

user.feature.lgresource = true

user.feature.lgpoweroff = true

user.feature.ls_event = true

user.feature.ls_normal = true

user.feature.sui = true

Try in the last replaced by sui andy, not a rental.

Is there a way to replace the screen lock 2.2.2 from LG on Android?
[LG Optimus Black] Ncyde47:
+1

I also have 2.2 froyo but there isnt even the lines that mauka wrote, theres nothing with "user.feauture.xxxxx"
[LG Optimus Black] zyfkurmom:
what about the ics lockscreen ?
[Kindle Fire General] airmaxx23:
http://www.xda-developers.com/android/beats-audio-now-available-on-any-gingerbread-rom/

I flashed the zip in CM7 and it definitely made a difference in sound quality.

Edit: PM me if you want the file.
[Kindle Fire General] Jessical:
That is sweet! Can't wait for an ICS version. :D
[Kindle Fire General] will25u:
Do you think it will work on stock Rom since its bbased on gingerbread?
[Kindle Fire General] airmaxx23:
Just make a backup and try it, if something isn't right afterward just restore your backup.
[Kindle Fire General] BluesHawk:
Thanks for the link, I flashed it and do notice some improvement :)
[Kindle Fire General] xolanir:
Tried to flash this on my stock 6.2.2 KF and was unsuccessful. Is it only compatible with cooked gingerbread ROMs? Thx for your help in advance.
[Kindle Fire General] kundancool:
can't access to link

Can anyone provide me a link to that thread or update.zip file

can't access it says

http://xdaforums.com/showthread.php?t=1523760
[Kindle Fire General] xolanir:
All threads have been closed and links removed due to people disputing the MOD's function. So basically a lot of people *****ing. :p
[Kindle Fire General] airmaxx23:
If anyone wants the file PM me and I will send you a link to download it.
[Kindle Fire General] cruel91:
I flash this into my ICS and it works. But really it is so hard to find the difference. If you want, you can give it a shot

http://xdaforums.com/showthread.php?t=1525226

Update: I used the download link from 3/2/2012
[Kindle Fire General] mugabuga:
Sounds interesting. I always thought it was a marketing gimmick. Did it work on ICS too?
[Kindle Fire General] xolanir:
Not sure how people are making this work for KF. Tried several times through twrp and it didn't install. Did the manual push, which lead to my device getting bricked. I think I'm gonna stay away for now till the kinks get ironed out unless anyone with a KF can help me successfully install.
[Kindle Fire General] smirkis:
installs fine on my cm7

which cm7 are you using?
[Kindle Fire General] BluesHawk:
What error did you get through TWRP?
[Kindle Fire General] xolanir:
It tries to mount/open the file but then says it can't read it. Plus I'm on stock KF firmware, would that make a difference?
[Kindle Fire General] JustROLLIN:
Yes. I believe the thread said it was for Gingerbread only, but some ICS folks had luck. I do not think there was any talk of the stock KF firmware, nor was it designed to install correctly on that firmware.

On a side note, it does not really install correctly on anything, must people just thought they heard a difference unless they went through the manual installation process.
[Kindle Fire General] xolanir:
Yeah when I read the original thread, it just listed GB ROMs as compatible and so it installed fine on my infuse 4G. Since I already was running voodoo sound on my infuse, couldn't be sure on whether the sound is really all the way different, but some songs and their bass sound a little clearer than before.