yashsingh1/xdaforums huggingface dataset:
[Galaxy 3 Android Development] DaBigFreak:
OK, so I tried undervolting with SetCPU, but it seems that my input has no change! I realy dropped the voltage, but nothing seems to happen. How do you undervolt? Handle the cpu?
[Galaxy 3 Android Development] D@rekills4:
Ok thanks....
[Galaxy 3 Android Development] fuxmen:
I have on every clock from 200-1000mhz undervolt -100mV with pimp my cpu, everything works fine, no freezes, because my phone can handle this. But when this kernel was making, the most inportant thing was that It would work on every phone stable. Because of that there is no UV even on 200mhz on stock

One more thing, don't set UV on all freq and then clic applly mosty this cousing freezes, I have that. When i set one UV in one freq then click apply and doing this one step after another until go to 1000MHZ everything is ok and phone works ok :)

Maybe i helped sth with this
[Galaxy 3 Android Development] hillbeast:
None is better than the other. In practice you want both as they both unlock different things.

You might not have actually used the clock speed you changed the voltage for. Check what clock speeds your phone is running with CPU Spy.
[Galaxy 3 Android Development] bizjoya:
just calibrated my phone 7 hrs before.. no phone calls and it was stable at 99% .. but after one hour of gaming it suddenly dropped to 63% percent .. quite shocked .. was playing simple fruit ninja..

g3mod 1.8 performance.. 200-1000MHz indemand.. kyrillos 7.0.

whats wrong with my phone?
[Galaxy 3 Android Development] Sergiales:
I feel the same... is like the first 8 hours the battery shows 99% but after that it drains very fast...
[Galaxy 3 Android Development] fuxmen:
Its stuck on 100% because 100% for this kernel is on 4V soo from ~4.2 to 3.990 is 100% and then drops down. But for me, battery hang for a long time in between 3.9-3.7 soo wait for it. And it Turn off around 3.55V not like when it have samsung battery driver 4.65..
[Galaxy 3 Android Development] bizjoya:
Hope someone can help us out .. otherwise will be going back to stock ROM with g3mod kernel ..permanently .. too much of experiments .. but leading us to almost nowhere except for the speed.. :(
[Galaxy 3 Android Development] bizjoya:
so we have to it every time??
[Galaxy 3 Android Development] fuxmen:
The % indicator anoying me like hell, then now with CM 6.2 i have oryginal green android indicator with 6 steps and I'm not thinking is ther 70 or 80 %. Just see that battery is almost full almost down or half, and my nerves is come now ;) But every person like another way of reading bat lvl
[Galaxy 3 Android Development] fuxmen:
Yes every time phone will be stuck on 100% for a couple of hours, But some batteries drop down from 4.2 to 4V in minutes, because of that i think dharam coded this like that...
[Galaxy 3 Android Development] Dharam_Maniar:
yes, that is the only reason why i did it like that...
[Galaxy 3 Android Development] kyrillos13:
It ain't possible! Did you wiped battery stats?
[Galaxy 3 Android Development] DaBigFreak:
Hey guys, at some point, dont know for what reason, my phone hangs and freezes, than its getting realy hot!

So if the phone only lives one hour, take a look at temperature, if should be realy hot, cause otherwise, battery energy isnt going somewehre without heat!

In the end, some thing must go crazy and take a bunch of CPU use, maybe the phone isnt realy freezed, but is staying on 100MHz and is working on one gone crazy app, so it seems as a freeze.

Weird thing about all that, if I go back to fugumod, instantly, all is fine again. (yes, I cleaned SetCPU for sure, deleted data, deinstall, install fresh)
[Galaxy 3 Android Development] kyrillos13:
I did advanced backup (only system) and i cannot restore it. It hasnt created an md5 and it says that md5 dismatch! I made one but it keeps saying it. What should i do? SOS !
[Galaxy 3 Android Development] Dharam_Maniar:
hmm, add it to some multiboot folder and restore it...

we will solve in next version....
[Galaxy 3 Android Development] kyrillos13:
Hm okay. Thanks Dharam :P
[Galaxy 3 Android Development] hillbeast:
MD5 hash check is disabled in v2. If you want, I can link you a test version and you can use that to restore your data.
[Galaxy 3 Android Development] kyrillos13:
I will do what dharam said:P But i would like to try it. What are the changes until now?
[Galaxy 3 Android Development] hillbeast:
This is a sneak peak at only SOME of the huge list of features we are adding to version 2.0 of G3MOD kernel

Hybrid kernel (supports CM and Samsung)

Adjusted battery driver

Compcache disabled by default (can be enabled easily)

InteractiveX CPU frequency mode

SIO scheduler

MD5 hash disabled

App2SD, Data2SD, Custom App2SD, Hybrid App2SD, Hybrid Data2SD

There are so many more features we are adding to version 2, so be excited about it.
[Galaxy 3 Android Development] debaj:
Maybe it would be the simplest to purchase a new battery, these issues you have are far from normal.
[Galaxy 3 Android Development] Smonic:
When wiping the battery stats from cwm recovery you don't need to use any other battery calibration app and only wipe the battery stats when the battery is full. I would recommend you buy a new battery. It's not that expensive and should solve all your problems. Another solution you could try is not overclocking your phone so much maybe up to 800 MHz or use use g3mod lite kernel. You should be able to live without oc
[Galaxy 3 Android Development] benzyniarz1:
Hmmm I've also problems with freezes.. I need to clean up memory via Task Manager every 2 h, because after 2-3h of messaging phone just freezes and only the on way to get it to work is pulling the battery.

I'll flash tomorrow 1.8 Extreme or Performance.. I hope freezes and battery drain will disappear. If not, there is sth wrong with my device.
[Galaxy 3 Android Development] Smonic:
Extreme is unstable for many people
[Galaxy 3 Android Development] LarryMetal:
That's why it's called "Extreme"!
[Galaxy 3 Android Development] Smonic:
I'm just saying it because many people decide to use extreme then moan about instability lags and battery drain...
[Galaxy 3 Android Development] radek.god:
But there is definitelly something wrong with extreme ( voltage or Kernel Hz + battery driver), because my phone cant get 1400 MHz - OK, but phone die within 5 mins even at 1300 MHz.When fugumod 1366 MHz kernel used at 1366 MHz I can pass 12+ hours at stability test ...

It means problem is not at my phone but at G3MOD kernel ... :mad:

---------- Post added at 11:28 PM ---------- Previous post was at 11:19 PM ----------

I will buy new battery.Weird, I though Voltage should lower to 4.0 or less Volts at full charge to be market as "bad" (Ive expected same efect like at Ni-Mh or Ni Cd or any other battery when I cant reach maximum voltage of new battery ... )

As I had phone nearly always connected to USB, I am sure I never wiped battery stats at less than 9x % , maybe always at 100% battery stast was wiped ... ) ...

Now I have 1.6 Performance, but I did not set SETCPU yet, so there is no reason to have battery drain :confused:

There is a HUGE difference between 667 and 1000 and between 1000 and 1366

I can live at 1000 MHz , but I cant live at 667, phone is totally gayed then :eek:

I am thinking about buying car 12 V adapter, I hope 800 mA will be non deadly for mobile as Samsung original car adapter CAD300U has 700 mA ...

:mad::mad::eek:After 10 mins of NDRIVE 11 + GPS on , battery went from 100% to 46% ... :mad::eek::mad::eek:

Update : battery went from 100% to 0% within 20 mins ! :-(
[Galaxy 3 Android Development] mankokoma:
my impression is: most people here don't hardly know what they are doing but complaining bout the kernel. sorry for this un necessary comment.

sent from the desert
[Galaxy 3 Android Development] TheCreat:
@radek.god: can you please be clearer about your issues when you describe a problem? It's quite hard to read, you even seem to contradict yourself. Read again what you wrote before submitting it, it's often just not really clear what happens in which circumstances...

First of all: if your battery is OK, you can't possibly drain it from completely full to completely empty in one hour! The CPU isn't that powerful and just can't draw that much power in that amount of time that it shuts off after an hour or even less. If that is the case, the battery is broken. The WiFi is also unlikely to draw so much power that this becomes a possibility, but you only said it's on, not if you used it or not, if it was connected or not, or maybe it was only just in range of a known network so it constantly reconnected over and over again?

then please clarify, do you have the same problem with fugumod 1366 or not?

first you said:

then a few posts later:

Which is it? Do you have the same power drain with basically any kernel so that you can't use the phone for more than a couple of hours at best? Or was that 12h test a long time ago? Or was the phone connected to a charger/usb?

Also you are misinformed about batteries and what was changed about the battery driver, please read more than just a few posts of the thread, this has been explained by a dev already!

I tried to the best of my abilities to decipher what you wrote in that post, you suggest that not charging the battery above 4.0 V might be bad for it, right? First of all, that doesn't (really) apply to LiIon batteries, it did apply to NiCd and to some extend NiMh.

More importantly though: the only change in the kernel affects how voltages are interpreted and/or displayed. Currently 4.0V means 100%, yes. But this has nothing to do with how far the battery is actually charged (which is still 4.2V as defined by Samsung), as hillbeast explained here.

EDIT: forgot one thing, I know you have almost absurd amounts of apps installed, can you please install Watchdog Task Manager Lite? It's free, and monitors if any apps that you aren't actively using strain your CPU. Just install it and launch it once, it will then inform you via a notification whenever some app (that isn't in the foreground) causes excessive CPU load.

Even if some app is misbehaving on your phone it doesn't explain the battery dying within an hour, but this might make an already existing problem (like a broken battery) more severe...
[Galaxy 3 Android Development] hillbeast:
No, the problem is not with G3MOD kernel. The problem is that at 1300MHz, you are running the phone at TWICE its rated clock speed. When Samsung made this phone, they expected it to run from 83-667 MHz. They never expected someone to run it at this level of speed.

Most people with even more expensive phones like the Nokia N900 don't even have their phones up that high. My phone at 800MHz experience NO lag whatsoever. Games run smooth, the UI is smooth, and the systemis very responsive. At 1300/1366/1400MHz, you have essentially killed both your CPU and your battery. I'm sorry to be giving you this news but that's how it is.

I wouldn't even run my Core i7 at a 200% overclock, and that thing is made for overclocking.

That's impossible for our phone in 100% battery condition to drain the battery that rapidly. Our phone is a 1500mAh battery, and your phone lasted 1/3rd of an hour. That means for 20 solid minutes, your phone was using 4500mA (I believe my calculations are correct). If your phone drained that quickly, your battery and phone would be EXTREMELY hot, and most likely would have caught fire.
[Galaxy 3 Android Development] TheCreat:
Well, 20 minutes are a third of an hour, as an hour still has 60 minutes and not 100. That still brings the usage to an just as impossible 4500 mA, so all other statements in you're post are just as valid (even though the calculations were not quite as correct as previously thought :D )

Swyped on my Galaxy 3
[Galaxy 3 Android Development] hillbeast:
lol I was thinking 1 hour = 100 minutes for some reason. I had only just woken up though so let's blame it on that.

4500mA is still around the amount of power an Intel Atom uses on its own, disregarding the VRMs, RAM, hard drive etc. That's a hefty chunk of power for a phone to be using.
[Galaxy 3 Android Development] harkan89:
Hey guys.. I don't mean to be pushy.. But is there any ETA for v2.0? Reeeeally waiting for it :D :D
[Galaxy 3 Android Development] hillbeast:
It'll be released when we get every features we want to add working 100% and we have tested it thoroughly enough to where be believe it is safe to release to the public. Reason we are taking our time on this one is because there are so many changes that it means a lot of testing for each feature needs done, and we are adding quite a few breakthrough features.
[Galaxy 3 Android Development] dhirend_6d:
I really really hope you get through the all in one kernel project you are doing. :) Very nice work you guys are doing. :)
[Galaxy 3 Android Development] mankokoma:
wrong place

EDIT: wrong place
[Galaxy 3 Android Development] hillbeast:
This information should have been PMed to me as this is information about the test kernel :P

But yes, Compcache can be enabled or disabled by placing a file at /sdcard/Android/g3mod/compcache. Just a blank file called compcache in the g3mod folder is all you need to enable it if you wish. The other two lines are there to show the results of the hybrid kernel. It's all just debugging from me.

Also the battery driver is modified. That is the first purpose of this test kernel. The other is to check the stability of the 100MHz steps.
[Galaxy 3 Android Development] radek.god:
Ok, my english is very very gay, so sorry for that ... :p

Now I have same battery drain with Fugumod 1366 and G3MOD kernel too.With GPS used by NDRIVE with wi-fi OFF and no DATA , then battery is empty after 20 mins - ok, I will order new battery.I had no idea my battery is broken before I tested G3MOD too.As I wrote 95 % of time is my phone plugged to AC/USB ...

12+ hours at stability test was ofcourse with USB/AC power adapter.I am mostly at home, so my phone is nearly always connected to USB/AC power adapter.I do not expect phone can pass 12+ hours at stability test and specially not at 1366 MHz with battery only ! :D:D:D

4-6 hours with fugumod set to 1366 MHz it was 2 months ago when I listened some MP3 at bike trip I used GPS only for 20 mins ... I had no G3MOD at this time ...

I suggest nothing about charging.I was thinking battery performance should be up to 60 mins only when battery is too old and Ive expected this can be prooved, when maximum voltage of battery is not 4.2 Volts as defined by Samsung, but changed permanently only 4.0 Volts or less even you charged it many hours ... I know this effect from Ni-MH ,Ni-CD 1.2 volt or non rechargable 1.5 V AA batteries.But I did not see this effect at phone battery, so I though my battery should be good.I was definitevely wrong about that and will buy new battery.

When I wrote wifi is ON, I mean I am connected to my router.Sometimes I am downloading/uploading , sometimes I have wifi on (mean connected to router) and I dont care if some apps are using it or not.For me there is no reason set wifi to OFF when I am home and My phone is connected to USB/AC

I will try app you suggest, thanks for tip :-)

I will leave Fugumod 1366 and G3MOD Ultimate and stay rather with G3MOD Performance :cool:

Hope 2.0 will be tested and released soooooooooooooooooooooon :D
[Galaxy 3 Android Development] hillbeast:
Your battery has been worn out from constant heavy use, hence why it lasts only 20 minutes. It is impossible, even with the worst programming possible, to drain the battery in 20 minutes, especially when it is such a large battery as it is in our phone. The overcurrent protection would trip. You'd most likely blow out the VRM circuitry before your phone could possibly do that.

Refer to my thread Important Information About Overclocking and you will see that at high overclocks, the CPU draws over 3 times as much power. This would have ruined your battery very quickly and most likely has caused negative long-term side effects for both your CPU and surrounding components including VRM circuitry.
[Galaxy 3 Android Development] radek.god:
What You wrote about G3MOD at 1300 MHz it does not add up (I mean it cant be true) How can You explain this : I can pass 12+ hours at 1366 MHz with fugumod kernel set to 1366 MHz and I cant pass even 5 minutes with any G3MOD set to 1300 MHz, becuse phone restart or mostly hang ???? :cool: It means there are some differences what make phone unstable = G3MOD kernel problem.

Of course I agree with you about CPU and battery lifetime with 1300+ MHz :( ...

About the battery drain, I understood Your calculations, and drain looks like impossible.But It can be possible if battery is at bad condition or battery has not 1500 mA yet even fully charged.Same effect like old Ni-Mh/Ni-Cd AA batteries.

It can be tested by multimeter.Good one can give 5-7 or little bit more Amps.Worst can give 3-5 Amps and realy bad battery cant do even 3 Amps.They all looks +/- same, only the bad ones can have maximum voltage under 1.2 volts.

200-1000 ondemand, screen 98 % off, poweramp with mp3 play on background (no headphones, speaker volume muted) and battery went from 100% to 83% within 55 mins.

But if I turn GPS on + NDRIVE + display permanently on, then 20 minutes and phone died because of battery 0% ....

at 83% I set phone wifi to on (mean connected and used by market and voila - 1 minutes and phone shutdown byself - for a 1 sec I saw red battery EMPTY icon just before that.

Same effect like I put my OLD fully charged AA battery to Fujifilm finepix s7000 and digital camera will shut down within 1-5 mins or even not start ! ...
[Galaxy 3 Android Development] hillbeast:
The reason it will react differently is because of different methods for overclocking. Fugumod uses synchronous clocks (all the clock speeds are divisible by the bus of 166) whereas G3MOD uses asynchronous clocks. This will react differently to phones that have had their CPU weakened over time.

I am not saying it's impossible for a battery to drain that quickly, I am saying it's impossible for software to cause drain like that. The only way to drain a battery that quickly is with a resister across the two terminals on the battery.

And the battery is a Lithium Ion, not a Ni-Cd or Ni-Mh battery. They react differently. It's like comparing a standard Energiser battery to the one in a car. They work completely differently. Ni-* batteries can't retain voltage as well after time, whereas Lithium* batteries can retain voltage, but can't retain the charge.

Also putting a multimeter across batteries in current mode can make the battery explode. It's not a good idea.
[Galaxy 3 Android Development] radek.god:
I know :cool: I am testing Ni-MH batteries for measure max AMPs they can hit only for 1-3 sec :cool:

I alraedy tried charge NON RECHARGEABLE 1.5 V batteries with 32 Volts AC :D:D:D

I was not able make them cool down so fast and they realy exploded :D I had batteries garbage all over my room :D:D:D:D:D

I know I had luck and I am not making those stupidity anymore

I went to 230 V instead :-)
[Galaxy 3 Android Development] dhirend_6d:
Wow man.:eek::eek: That was really stupid. :D:D. Anyways, it is an expierence.
[Galaxy 3 Android Development] FadeFx:
Hehe when i was young a friend used to charge non recargable batteries using a 12v car battery and that went well actually...

----------------------------------------

tapatalked
[Galaxy 3 Android Development] FadeFx:
I have an idea on how to possibly remove some lag from data2sd enabled systems, i think it could be usefull to leave the /data/data folder on original data partition which is onenand and thus faster than sd ext4 partition. Unfortunately i have no idea how to acchieve this, but as you guys are the pros here, i guess u have an idea how this could work. Id suggest to mount stl7 as /datadata/ and move /data/data/ there and symlink it.

----------------------------------------

tapatalked
[Galaxy 3 Android Development] hillbeast:
I'm making a hybrid Data2SD which will allow the user to select each folder he wants on SD or on internal: a fully customisable Data2SD. This will do what you're thinking.

---------- Post added 19th September 2011 at 12:06 AM ---------- Previous post was 18th September 2011 at 11:51 PM ----------

Thanks to marcellusbe, we now have CM7 working on G3MOD! Now I just need to make them all work together in a single kernel!

Go over to marcellusbes CM7 thread and click thanks on all his posts in order to thank him.
[Galaxy 3 Android Development] dhirend_6d:
Yes yes yes yes.;):)
[Galaxy 3 Android Development] FadeFx:
Sounds perfect, only thing i worry about is, i think only one data partition can be monitored by the system, so if the other one gets full we will expirience a fc-orgasm and all hell breaks loose, as we get it on cm7-sgs where we have a seperate datadata partition.

----------------------------------------

tapatalked
[Galaxy 3 Android Development] hillbeast:
Don't worry, I've thought of all this. It's hard to explain what I'm doing, but it'll work wonders.
[Galaxy 3 Android Development] FadeFx:
Ok, i stand by and wait what u come up with...

Btw, did u think about this before i came up with the idea, or u had a concept so fast?

----------------------------------------

tapatalked
[Galaxy 3 Android Development] toms95:
:eek: - that's all I can say about G3MOD kernels, but maybe you could add OC bus (maybe some kind option in CWM to turn it on/off) or maybe upload 2 kernels- 1 with and 1 without OC bus.
[Galaxy 3 Android Development] vivekmishra:
I'm facing the same problem, and what about the new directories, i have no idea what you are talking about. I'm on cm7 alpha6 can i multiboot using the g3mod froyo or g3mod 6.2 kernel if yes how..

just wanted to grab ur attention :P
[Galaxy 3 Android Development] dympy:
No, not yet.

The CM7, CM6, FROYO Multiboot would be availavble in V2.0 of the kernel (if I'm right).

Dympy.
[Galaxy 3 Android Development] NishantM:
Sorry for interrupting such an interesting discusion. I'm getting freezes on 1.9 ultimate on 100-800 ondemand. It happens occassionally when i press the home button. Back to 1.8 which doesnt have this issue.

Just wanted to let you know.
[Galaxy 3 Android Development] mankokoma:
seems you have the same problem as me - it's about voltages in the 100Hz steps.

when you don't go about 800 MHz anyway, then change to the performance kernel and you won't face these freezes anymore...
[Galaxy 3 Android Development] hillbeast:
There is something odd with 100/200MHz. I'm not sure which but as soon as I get hybrid working, and hybrid Data2SD I'll work on it.
[Galaxy 3 Android Development] radek.god:
I think this is a good idea.As my battery "died" probably because of high OC ( battery today went from full state to 0% withnin 20 mins :( , even small usage or within 2.5 hours with MP3 and display off ), I wanna rather to have kernel with such low kernel Hz as possible with 100-1400 MHz.

I saw this as someone sent as reply to my post http://xdaforums.com/showthread.php?t=1266712

I cant believe my eyes what I read about power consumption increase from 667 to 1366 as I used daily with Fugumod :eek: ... I can confirm nine months and my battery is unusable :mad:.

So I hope there will be 2.0 with kernel 256/300 Hz only and with 100-1400 ability

(100-800 for daily use, 100-1000 for battery 90-100% of charge only and 100-1400 with charging only ... ) :cool:
[Galaxy 3 Android Development] vleutmans:
I see some improvement in 3d performance

when using g3mod performance 1.3 @950 mhz with

190 mhz bus speed.It outperforms other kernels

which have non oc bus and 1200mhz especially in 3d

games.
[Galaxy 3 Android Development] hillbeast:
I want to get OC bus working again, but the way to switch it on and off is quite awkward and we are trying to minimise the amount of kernels we have to release from here on. If we get the chance after implementing everything for G3MOD 2.0 then we might release an OC bus version. I won't promise anything though.
[Galaxy 3 Android Development] ale_bot:
thanks :)

i really want a oc bus because with games like nfs or gangstar is slow even at 1200 MHz. with g3mod 1.3 and fugu ultra I played well at everything

good work