yashsingh1/xdaforums huggingface dataset:
[Galaxy 3 Android Development] FadeFx:
If battery life is good, then why not, btw if u lower the 'up threashold' value in ondemand to lets say 70 or lower you have probably a similar effect but with the difference that it does not stay on high freq for so long. Meaning you could get even better battery stats and also no lags.

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

tapatalked
[Galaxy 3 Android Development] pratikmore:
My battery is fully charged at 9am...now 6.30 pm here in india.from last 1 hour im using 2g data network..only surfing it falls to 50%.im on dutchmod rom with 1.9g3 mod lite kernel...plz help me
[Galaxy 3 Android Development] D@rekills4:
Try calibrating the battery.....

It worked for me before and now I am gonna do it again.... :)
[Galaxy 3 Android Development] hillbeast:
Yes, but I have hardly ever seen a file become corrupt by just sitting on an SD card, and considering how many hash fails I've gotten on perfectly fine files with CWM, it's better just to turn it off.

I got a hash fail once because it didn't generate the MD5 in the first place. As a result, my entire backup was pointless.

That battery life isn't too bad. It should just need a calibration.
[Galaxy 3 Android Development] DaBigFreak:
Now here is another thing with the setting the 100% to 4,0 volts.

This is my third time I charge the battery with g3mod 1.9 and now it realy slows down the charging above 3,89 volts.

Before that, the slow charging begun over 4,15 volts!!!

So please, how can I set it back to 4,2 volts, and please set it in any further kernel back to 4,2.

The other thing is, that now with 0% at 3,5 volts is that I dont get a real warning that I need to charge. So it happened that with 3,55 volts the phone just shut down and I couldnt boot, first to plug in usb.

The most bad thing for a battery of any kind, is to be undercharged! Under a certan voltage, the battery begins to destroy itself, not with an explosion :-) but with chemical decomposition.
[Galaxy 3 Android Development] fuxmen:
I know from my friend who knows A LOT on electronics that to damage this battery You need to discharge it <3V or even lover... Soo if You dont put it out and attach to it light with wires then this couldn;t be done :D
[Galaxy 3 Android Development] LarryMetal:
The only thing that looks nice with 100%@4000mV is that it shows for long time 100% and many people think that they have better battery duration. The correct 100% is @~4150mV, because while charging can reach ~4.2V but it falls really fast.
[Galaxy 3 Android Development] DaBigFreak:
Light is coming through the clouds :D

Thanks a lot mates!
[Galaxy 3 Android Development] vivekmishra:
Thanks a lot(used the button) ;)

Pardon me for it is thread for the froyo kernel, Are there any ETAs for g3mod v2.0?

Plus, taking my chances here,, are there are different version of swype for froyo and cm7? If yes can you plz help me out getting that? :)

And, yes.. can i multiboot cm6.2 and cm7? If yes how?

Pleeease :)

Galaxy3 Apollo Cyanogenmod7 alpha6
[Galaxy 3 Android Development] bautrupp:
Why don't we throw away that percentage-thing and simply write the voltage into the panel.

Perhaps it could be colored yellow under 3700mV and red under 3600mV.
[Galaxy 3 Android Development] mankokoma:
My problem with draining was solved with WIPE DALVIC CACHE (remember: booting then will take it's time... be patient), but in the same procedure I did WIPE CACHE & WIPE BATTERY STATS. Which one of the three was the solution I can't say, but now I had amazing good results in battery life. Really better than ever before! Even with GPS, G3 or WIFI.

When I see the charging process going to tranquilize I pull off the plug and plug it in after a few seconds.

To me that helps.

But I'm also afraid, that it's better to buy another second battery, vacuumize it into foil and put it into the deep freezer coz of this my behavior :D:D:D

I think in general it's the best, to keep Li-ions between 45 and 90some Percent - In the case with the new kernel of course 100% ;)

BTW I don't mind that percentage display - look always at the Voltage!
[Galaxy 3 Android Development] bizjoya:
Was never able to reach 4200mv while on kyrillos 7.1 g3mod 1.9 .. just flashed JP6 stock to check .. and immediately it reached 4200mv.. chkd from batt info ... is anything happening wrong with my phone?? quite clueless with batt thing ...
[Galaxy 3 Android Development] Inovator:
Applied 1.9 extreme and lost WiFi MAC adress :/
[Galaxy 3 Android Development] Pinak.ahuja:
I agree the full voltage should be atleast set to ~ 4100mV
[Galaxy 3 Android Development] vleutmans:
compcache

Hi designers and all followers,

I'm really following g3mod 1.9.1 disabled compcache ;-)

I just saw the development on github, where the ramzswap service was mentioned.

I'm not a designer, but recognized this ramzswap from fugumod 2.2 where it also was mentioned and you could "enable" it in that case .

At the moment I'm on g3mod 1.4 without compcache and I already can state that disabling compache solves (part of) lag, especially when you don't set the minfree parameters a little higher than default. Could it be then when you set minfree values too low, that compcache gets a conflict (lag)with the reserved portion of ram (16/32mb?) that is being compressed, when 'memory free' gets below 32 mb ?

My experiences with lag (I mean the lags in game "dragon fly", there are many types of lag)) were caused by different kind of interrupts :

1) compcache

2) A2SD

3) minfree

4) cpu freq

5) swap file

solutions that seem to work (by trial and error):

1) use kernel with compcache disabled (g3mod 1.4 kernel or lower.. or 1.9.1)

2) use link2SD instead of A2SD (not offending any designer). Change your existing ext4 partition to fat32 (a2sd auto disabled!).

3) set minfree to moderate settings 6,8,16,20,24,40

lowmemorykiller/parameters 0,1,2,4,6,15 = 1536,2048,4096,5120,8192,10240

Juwe ramscript is a little aggressive in these minfree settings.

4) overclock to 1000 mhz, with performance kernel.

5) disable swap by removing the swap partition.

If you have a spare i5800 and or you're bored, then you could try these things too :-)

enjoy !!
[Galaxy 3 Android Development] radek.god:
Hi,

I did not tried Dragon You play, but I am sure your problem is at A2SD script.

Of course it should be something elese or more thing, BUT A2SD is really bad.It loosk like good, but with more and more apps installed You will find it is a CRAP.

I get so many restarts, lags or even reboot during call even with stiock deodexed/( non deodexed too ) JPS ROM.All problems disappeared when I used LINK2SD.

So from my side, start use permanently LINK2SD instead of A2SD.Then You can try next steps.

To 4) - I can use fugumod Kernel 1366 at 1366 MHz and my stability test will pass 12+ hours.

I see what scripts You have.I used RAM script + swap too

For example by this http://xdaforums.com/showthread.php?t=1247273&page=16

Your phone should be fasterand boot up time will be much faster!, but When You

will install 0.2.0 then You should have so many problems.What Am I trying to say is "sometimes less mean more" :cool: and with more and more things you cant know what exactly makes problem ...

I wish You good luck with solve your problems :-)
[Galaxy 3 Android Development] djmaxis:
Thats right in advanced restore
[Galaxy 3 Android Development] Sergiales:
Back to jps samsung deox rom... Faster and smother that any other rom (but cm 6.2, i have some problems with it though) after a clean some apps, changed launcher and customized my settings...
[Galaxy 3 Android Development] dpthakar:
Thanks for the great kernel.

I was waiting for cwm recovery.

This one is great
[Galaxy 3 Android Development] hillbeast:
I believe a lot of the instabilities that arise in a lot of custom ROMs are caused by themes and such being changed. The frameworks are surprisingly delicate and messing with them can cause a lot of problems.

And I'm not defending Kyorarom because I know CMbins has issues which cause Kyorarom to be a little unstable. Unfortunately I am unable to replicate these issues that people report.
[Galaxy 3 Android Development] kyrillos13:
I think that 100% must be set at 4170mV... Thats the full. The battery goes up to 4200mV but to reach it you must plug & unplug the charger 4-5 times...
[Galaxy 3 Android Development] cop1976:
Well, my battery reached 4200 ever time without unplugging, but I think that set up at 4170 it is a good idea.

Sent from my ultra fast Galaxy 3
[Galaxy 3 Android Development] dpthakar:
I am using I5801DDJP6 with g3mod_froyo_v1.9_lite.

All seems working fine, except while restoring backup using cwm I am getting following error.

/dev/block/stl7 file exists

Even manually mount / umount of data / cache partition does not work once above error appears.

I also repartitioned sdcard with cwm, just to ensure no issue with reading from sdcard via cwm.

Edit:

I am using Link2sd
[Galaxy 3 Android Development] LarryMetal:
To be fully charged, battery must go a little bit higher than 100%. For our batteries 100% is ~4150mV and to be fully charged Must go to 4180-4200mV. That is why when you unplug it falls almost emediatly to 4150mV and then is stabilized.
[Galaxy 3 Android Development] Inovator:
Does anyone know (dev's maybe?) why is MAC adress lost after flashing g3mod 1.9? Tried under Kyrillos 7.1 and Dutchmod 3.2, same thing...

10x
[Galaxy 3 Android Development] benzyniarz1:
I've noticed a bug... I don't even know if someone else has the same problem...

When battery is lower than 20%, I get the message on the lockscreen - "The SIM card is locked". But I can make calls, receive messages. When I plug the charger, the text disappears.

What's more, battety life is about 12-15h less on the 1.9 Performance than 1.8 Extreme...
[Galaxy 3 Android Development] mankokoma:
To me helped WIPE DALVIK CACHE, WIPE CACHE & WIPE BATTERY STATS in same case. Since then Battery life is much better than with every other G3mod-kernel
[Galaxy 3 Android Development] benzyniarz1:
Thanks, I'll try and then check :)
[Galaxy 3 Android Development] hillbeast:
4200mV is the default Samsung charging level. We never set that up. All we have adjusted is where it sets 100%.
[Galaxy 3 Android Development] satyamsit:
I want to use Jp6 with g3mod 1.9 . can I partition my sdcard from cwm as we do in kyrillos??
[Galaxy 3 Android Development] mankokoma:
I also think, you should put UP the 100% mark. When you charge it to more than 4,1 V, the %-display is going to stay for at least one day on 100%. Result for me is just to ignore the %ige in display. However - I don't care too much on this issue ;)
[Galaxy 3 Android Development] Dharam_Maniar:
Yes you can
[Galaxy 3 Android Development] satyamsit:
cant find /system/etc/init.d/ ......... through root explorer .. i mean no init.d inside /etc ..

using stock rom .. thr wasnt any init.d directory .. after flashing g3mod performance 1.9 .. still there isnt any... :O

have already partitioned..
[Galaxy 3 Android Development] FadeFx:
Create it if u need it

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

tapatalked
[Galaxy 3 Android Development] satyamsit:
will it supprort g3mod lite 1.9 or stock kernel in that case?
[Galaxy 3 Android Development] FadeFx:
stock kernel will not be supported, lite i think yes...
[Galaxy 3 Android Development] dhirend_6d:
Haha. What a video. Good insults. :D :D

"XXXdevelopers.com". :P :P
[Galaxy 3 Android Development] benzyniarz1:
Unfortunately, I must say that battery life hasn't improved. It's still max 20h..
[Galaxy 3 Android Development] LarryMetal:
You are doing something wrong. I have 50h avg.
[Galaxy 3 Android Development] benzyniarz1:
I really don't know what I am doing wrong... Cache, dalvik-cache, battery stats have been cleaned, battery calibrated.. On the 1.8 Extreme, my battery life was min 40h....
[Galaxy 3 Android Development] mankokoma:
I'm sorry... had the same problem and that was the only thing that helped. (I'm using g3mod-rom & performance kernel). check apps in background & services. have you set advanced setcpu settings suggested in this thread? otherwise I've to admit no idea than flashing all new :(

any other?

sent from the desert
[Galaxy 3 Android Development] LarryMetal:
The problem is the apps you use and how you've set them up. And also if you are constantly touching the screen you'll never get better battery life.
[Galaxy 3 Android Development] benzyniarz1:
No, I was using the same app with the same frequfency. Maybe the problem is wi-fi.. I've noticed that sometimes the data packets are not turned off while wi-fi is connected.
[Galaxy 3 Android Development] hillbeast:
Alright guys, let's try to compile a list of all the things we want to do with G3MOD v2.0.

Also, try not to ask about improving battery life because batteries are a tricky thing to diagnose as it happens on some phones but not others and because of this we can't isolate where the issue lies.
[Galaxy 3 Android Development] Criminal23:
Want CM7 Support ;-)
[Galaxy 3 Android Development] hillbeast:
Working on it :)
[Galaxy 3 Android Development] FadeFx:
What about 1.9.1 Version with corrected battery gauge and compcache enabled/disabled version to compare... then a 1.9.2 with 500/300hz?

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

tapatalked
[Galaxy 3 Android Development] mankokoma:
+1

& wanted to remind, that I still 'only' can use performance due to..... you all meant it's about too low VOLTAGE....
[Galaxy 3 Android Development] hillbeast:
500Hz doesn't cause instabilities like people suspect. The instabilities in v1.9 stem from the new 100MHz steps and incorrect voltages.

We will however still be doing 2.0 with 500Hz though, no more 1000Hz, and not because of instabilities, rather because it puts enormous strain on the CPU.

The kernel Hz just defines the frequency the interrupts interact with the CPU. If this is higher, then the CPU will check the interrupts more frequently per second, ie 256 times, or 500 times per second. As you increase this, it will cause the system to respond quicker but as a side effect it means the CPU has to do a lot more work per second and it can drain the battery quicker, or even begin to cause a negative effect on the performance as the CPU is checking interrupts when it could be working on something important.

It has nothing to do with bus speeds or clocks or anything like people are assuming.
[Galaxy 3 Android Development] FadeFx:
It however would be of interest if 300hz could possibly extend battery life a tad...

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

tapatalked
[Galaxy 3 Android Development] mankokoma:
That's already clear. I'm just begging to fix it anyhow, as you can see, my poooooor lamb of phone seems to be very pretty tender sensitve on low voltages from the beginning on :D

However, 1.9 performance is perfect to me and the best until now. So do what you want and I still will be satisfied with this version!
[Galaxy 3 Android Development] KSLevel11:
+1.

I want to see how it works without compcache.
[Galaxy 3 Android Development] DaBigFreak:
OK, so now, after 4 days checking 1.9, I got zwo times the same issue.

In the morning, my alarmdroid works, get me to wake up. But than after some snoozes, nothing happens any more. Just the unlockscreen, then nothing. Beside that, mobile gets realy hot, cause I mentioned the freeze just after an hour.

So, after the first one, I wiped all the stuff (not the data/wipe :-P ), but now it happened just the same way again.

So for now, I go realy back to fugumod 1366, here I got awesome battery backup, 100% is 4,175volts, it ends with 3,6 there I get an warning to charge my battery at 15%, with this I can use it half a day.

Here in g3mod, to go to bed with just 40-50% will result in NO BATTERY at morning...wtf? No warning, just draining till death...

I realy hope that this will be somekind fixed by 2.0, but as many of you dont have these problems, guess it will remain. Maybe I set Kyrillos ROM completely new up, but this takes time I dont have these days.

In my mind, it should be possible to make this kernel run with my installed Kyrillos, cause flashing the same ROM again, wont change anything, will it? Just one thought came to me...what if the g3mod kernel needs different partition filesystems? Cause I am stuck to the Kyrillos filesystems, maybe the problem is that g3mod need some partition in another filesystem? ext2 -> ext4 ???

The other one would be, that g3mod kernel is realy messing up with the conservative governour...some times phone gets realy laggy, I go to setcpu, voila, fixed to 100MHz...

Using the kernel at 100-1000MHz, but 1400 works just fine too :-)
[Galaxy 3 Android Development] criminal_007:
I have one query regarding battery drivers

It shows 95% in information but when switched off the bar is almost about 60%

what's the problem? :confused:
[Galaxy 3 Android Development] DaBigFreak:
For me the hole battery thing is absolute messed up. I read the voltage and than I know how long it will last, till my drain comes up again, than its imidatly off...
[Galaxy 3 Android Development] bautrupp:
I'm still using 1.6_performance. Everything regarding the battery is fine with this kernel.

But i repeat my proposal:

Skip the percentage-calculation and simply get the voltage written into the panel, or perhaps it could be made configurable (g3mod-app?). For those who don't want or trust the percent notification it's a waste of space.

But there would be problems with some SetCPU profiles.
[Galaxy 3 Android Development] radek.god:
As I used my phone at home, nearly 95% of time AC/USB powered I though Fugumod 1366 is better, now I discovered this.

Fugumod 1366 is much stable, at stability G3MOD extreme is useless and G3MOD ultimate is not so stable.BUT Fugumod 1366 has MEGA Battery drain.Battery is empty within 2 hours even not at 1366 MHz :-(

So I hope there will be soon 2.0 with 300/500 Hz max.If non stability is not because of kernel HZ but because of low voltage, I hope G3MOD team will look at voltage too :cool:

I think Fugumod has 1.525 V for 1366 MHz ?

at G3MOD performance I see 1.400 V as max for 1000 MHz.

Problem is we can lowe rvoltage only, but we cant raise it.So maybe if voltages will be higher, we can reduce it manually to make battery drain lower and CPU cooler if we will find stable voltage.
[Galaxy 3 Android Development] DaBigFreak:
On 1400MHz g3mod goes to 1525mV too. So quit no difference.

For me, its the same opposite! With fugumod I have at least 2 days of battery, WITH wifi on. With g3mod wifi on, just one day, max.

Maybe, the batterystat.bin realy needs to be made up, so for quick switching kernels, no way. That whole thing needs time...current answer to all my questions, cause so many of you having quit no probs, but me a lot... :-(
[Galaxy 3 Android Development] radek.god:
You are not alone , I have problems too :

Extreme 1.7-1.9 unusable, phone hangs within 1-5 mins, specially at 1400 MHz

Ultimate 1.7-1.9 not so stable like Fugumod 1366 MHz, I get restarts sometimes

When some CM6.2 files used by Froyo (some cmbins) , then 1.9 went unusable.

Performance - just testing - I get "startup" sound during call and I expected phone restart, but I finished call and no restart, no program close - weird

- When Ondemand set to 100-1000 or 800-1000, phone NEVER use 900 or 1000 MHz , even I play game.

Btw it is weird You have 2 days with Fugumod battery life, My phone died after 2 hours , tested last 2 days when I used my phone without permamnent AC adapter in.
[Galaxy 3 Android Development] hillbeast:
Okay guys, today I'm gonna take a good look at both the battery drivers and the CPU frequency drivers to see what can be done about getting the battery to be read correctly.
[Galaxy 3 Android Development] (•.•):
you should really look into fugumod and g3mod and compare them where they have the main difference.. especially on the battery settings.
[Galaxy 3 Android Development] hillbeast:
The differences between G3MOD and Fugumod are so great that it's not worth it. Fugumod AFAIK has an unmodified battery driver, whereas G3MOD has a heavily modified driver in order to give a more linear drop as people complained that battery life was unpredictable. But now that we have changed it, people are complaining that the battery life is unreliable, so we just can't get it right no matter what we do.
[Galaxy 3 Android Development] TheCreat:
I think fugumod had the original battery driver.

I like the idea of trying to get the battery drain more linear than what Samsung managed, but I think adjusting the limits A was a mistake. Like many others (and like I have already reported) my G3 stays at 100% for 12 hours, another 6 on 99%. Battery posts nicely for about 2.5 to 3 days. Yet it diss so quickly in the end I either never get a message to plug it in, or it immediately shuts down upon showing me that message. Nothing linear about that...

Swyped on my Galaxy 3
[Galaxy 3 Android Development] hillbeast:
I am looking for 4 or 5 people to do an alpha test of the current kernel I am running. I have adjusted quite a few things and I need opinions from general public.

PM me if you are interested.

Also, the kernel is Ultimate @ 500Hz , so if you don't like that then don't PM me :)
[Galaxy 3 Android Development] harkan89:
This one works with CM7?
[Galaxy 3 Android Development] hillbeast:
No. CM7 is still not supported as the modem is non-functional. CM6 and Froyo are the only supported by this test kernel.

EDIT: I'll also mention, the people that PM me, I'd prefer you aren't experiencing issues with your phone already, ie crashing or battery drain. If you test it and you have crashing and then report you are getting crashes, I can't fix it because I don't know if the problem is with something I have done or if it's something else on your phone.
[Galaxy 3 Android Development] radek.god:
battery drain like hell

OK, I tested 1.9 Performance and my battery went from 100% 4.176 Volts to 0% within 1 hours only ! I had wi-fi only enabled :(

I am trying 1.6 Performance as somebody reccomended :o

good luck to mod battery and overclock/voltage/stability drivers/settings to have 2.0 soon :cool:
[Galaxy 3 Android Development] hillbeast:
Well we don't know what Kyrillos used to root the system but he used Superuser.apk and su. It doesn't matter what method he uses though to do it as they all work pretty much the same. I use SuperOneClickRoot for my ROM.
[Galaxy 3 Android Development] DaBigFreak:
Could you please add "how to install the newer kernels"? Cause I got a bit confused, to install the kernel via recovery, not to flash with Odin^^

And for the guys that now update their kernel the first time, have no chance^^

EDIT: Oh my goodness...just saw you have the *.tar files in the downloads...so sorry man!
[Galaxy 3 Android Development] Dharam_Maniar:
yes, sure will be added... :)
[Galaxy 3 Android Development] DaBigFreak:
Hey, another thing. Again the voltages^^ Sorry to bother you...but:

Till now I used fugumod 1366 the inofficial one. There MHz goes from 1xx to 1366, up to 800MHz the default voltages as in stock rom.

You start right from 200MHz with 1200mV, is it because you have higher kernel frequency? Do the 300MHz kernel speed need the much more voltage?

The thing is, if I push the voltages down to fugumods values, I got a freeze in no sec. First thing I think is there is a huge need, that the voltage is increasing near linear, that means a high voltage jump imidiatly freezes.

So its kind of hard to make a near linear increasing voltage from 1.0 V to 1.5 V, to 800MHz not above 1,2V.
[Galaxy 3 Android Development] hillbeast:
It's a lot easier than it sounds. Just pop the zip on your SD card, reboot into recovery, go to Update, go to Select zip from SD, and choose your kernel zip.
[Galaxy 3 Android Development] hillbeast:
This is because Fugumod sticks to the stock clock speeds whereas in G3MOD we have gone for 'just make it stable'. Fugumod doesn't undervolt correctly anyways. It only undervolts on the max frequency.
[Galaxy 3 Android Development] D@rekills4:
Which root is better then?

The ADB Root or the SuperOneClick Root?
[Galaxy 3 Android Development] Dharam_Maniar:
the adb root, is for the root in terminal emulator or when you connect via adb to the PC.

SuperOneClick is for the apps...the SuperUser one...