yashsingh1/xdaforums huggingface dataset:
[Samsung Captivate Glide] dman3285:
As the title says.. AOSP.. only for CM10, CM9, AOCP, AOKP, PAC-man, ect, ect... ONLY AOSP roms
[Samsung Captivate Glide] lorddavid:
aaa ok, thanks :)
[Samsung Captivate Glide] VinayS:
oh, Time to change back..i am on stock ICS..

In Stock ICS,

Not able to pass lockscreen from second boot onwards..

phone gets struck and hangs.. also does not charge..
[Samsung Captivate Glide] dman3285:
That's because this is Only for AOSP ROMs.. clearly stated in title and OP..
[Samsung Captivate Glide] taiber2000:
so this really a teaser for upcoming update to the cm10/10.1 and aosp roms :)
[Samsung Captivate Glide] seniar:
What do you mean by "wakelock enabled" in the op?
[Samsung Captivate Glide] dman3285:
If I need to explain it you don't need to flash it.

Means you can enable wake lock in settings if supported..
[Samsung Captivate Glide] dbrannon79:
Just a quick question! overclocked to 1400mhz? is that safe? I was having trouble with litekernel clocked to 1.28!! and heat issues while running google maps. and how does that affect the battery life?
[Samsung Captivate Glide] dman3285:
Its completely stable.. been running it at 1400 with smartassV2 and has been flawless .. not even gotten warm...
[Samsung Captivate Glide] dbrannon79:
I wish I could use it in Ice Pop rom too! But it's a modified stock rom!
[Samsung Captivate Glide] dman3285:
This was just a quick run on quadrant OC at 1400, UV at 750
[Samsung Captivate Glide] Adam77Root:
Do you mean these wakelocks? If yes, I doubt that there is any Android release having such an option. If you disable wakelocks, almost nothing will work on the system.
[Samsung Captivate Glide] seniar:
I am not a noob at this I've been flashing roms for a long time and I've never seen the tweak wake lock enabled and I've only seen wake lock referred to as apps or other things keeping your phone awake and killing battery

I'm not trying to be rude i was just curious
[Samsung Captivate Glide] Evil Alex:
Looks awesome! Is that 750mv at 1400Mhz? I cannot imagine that would be possible, the lowest voltage at the highest frequency. If it is, then the covenant really does work miracles! :D
[Samsung Captivate Glide] magicninja:
What are you using to oc? I am using antutu but can't seem to find 750 Anywhere
[Samsung Captivate Glide] dman3285:
In the cm settings...
[Samsung Captivate Glide] magicninja:
What about the under volt?
[Samsung Captivate Glide] dman3285:
Voltage control
[Samsung Captivate Glide] magicninja:
Ok thanks I have never really messed with under volting before guess I can figure it out
[Samsung Captivate Glide] thescot33:
Just wanted to see what cpu options people are running for best batt life and performance? What governor and I/O scheduler? CPU freq? I use my phone all day so my batt gets charged twice a day just want to get the most out of it

Cheers!

Sent from my i927 PACman JB
[Samsung Captivate Glide] :
I usually like to set CPU clock at 800MHz, and with Interactive governor (SmartassV2 isn't bad), with voltage low enough to support the continuing CPU operation (Voltage Control is already smart enough to know the limit).

And, I ran my phone at 1.4 gigahertzs briefly (I only do my actual overclocking easy and start with voltage and duration even on my own PC's Phenom II CPU). But still, it was mind-blowing.

Sent from the jar of Jelly Beans
[Samsung Captivate Glide] :
I forgot to mention that the IO scheduler do affect the battery runtime, apparently. I tried Deadline, and it cost me a bit runtime. So, I switched back to SIO.

Sent from the jar of Jelly Beans
[Samsung Captivate Glide] :
I personally think Tegra 2's Cortex A9 CPU cores might be able to run at 1.6 GHz (done on several hacked Android tablets), but not higher as it's made on 40nm SOI process, maybe with crystalline Carbon low-k gate layer similar to those of later Phenom II (Thuban).

If this SOC was to be made on 32 - 28nm SOI+ HkMG process, it could be capable of running past 2 GHz, with reduced runtime being the price.

All in all, 1.4 GHz seems to be a safe speed (200MHz above official 1.2 GHz as advertised by NVIDIA).

Sent from the jar of Jelly Beans
[Samsung Captivate Glide] :
I decided to overclock my phone and let it at NBench benchmark (this benchmark is kinda BS, but I don't know which can solidly prove MIPS / MFLOPS, I hate scoring system). I set two runs, at stock clock of 1 GHz, and OC 1.4 GHz, with IO scheduler on NOOP, and governor on ONDEMAND. It will kill battery that well, but I decided to burn through the charge for giggle and sh*t. And, I can confirm dman3285 was right, it ran cool at 1.4 GHz (voltage was tuned all the way down).

1.0 GHz run benchmark screenshot

Sent from the jar of Jelly Beans
[Samsung Captivate Glide] :
1.4 GHz run benchmark screenshot

Sent from the jar of Jelly Beans
[Samsung Captivate Glide] dman3285:
Covenant Kernel V2 update in OP with Voice search fix.. Enjoy..
[Samsung Captivate Glide] :
AndroSensor returned valid microphone values this time. :thumbup:

Sent from the jar of Jelly Beans
[Samsung Captivate Glide] dman3285:
I will be running a new CM10 build with updated keyboard fixes and voice fixes to include the covenant kernel..
[Samsung Captivate Glide] :
Sweet! :D

Sent from the jar of Jelly Beans
[Samsung Captivate Glide] dbrannon79:
Can someone please post a breakdown of the many governors in the kernel, what the differences are and the best to use for the different situations!

Thanks
[Samsung Captivate Glide] bobbinthreadbare:
My microphone works now with the new kernel but something else went wonky..if anyone elses uses wifi calling, give it a try. Music and everything sounds fine but when I make a call, people sound very distorted. Almost like one of those movies where the bad guy is using a voice changer, its kinda funny..I'll try a different client later but it was fine on the old kernel yesterday (just no one could hear me on my end) and my other devices using the same setup still work/sound fine.
[Samsung Captivate Glide] :
Governor and IO scheduler:

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

"ye who asked, ye shall receive"

And on a side note, someone suggested that the stability of CPU can be held long enough with thermal paste - it doesn't work here, too far apart in the SGH-I927 but I have the transistor thermal sheet (gray-blue rubbery sheet), and cut it up to fit the RAM on top of CPU and put it on keyboard case and put everything back together. Will be testing it out.

EDIT: The transistor thermal sheet did the trick. Again, dman3285 was correct. It's barely warm (kept my hand on the keyboard). I think CPU would be okay with 1.4 GHz without any cooling.

Sent from the jar of Jelly Beans
[Samsung Captivate Glide] smutta:
Does the led work now?
[Samsung Captivate Glide] dman3285:
Does the op state that led works? Negative
[Samsung Captivate Glide] :
LED do work but not the way it's supposed to, so it's correct to say it's broken. I already reported this bug.

Sent from the jar of Jelly Beans
[Samsung Captivate Glide] dman3285:
I'm working on fixing BLN at the moment.
[Samsung Captivate Glide] :
I am wondering if there may be an option to for the EXTn (EXT 2 - 4) FS automounter to be able to support the microSDXC cards (the hardware in SGH-I927 already support that new SD format but there is a need to mount the SDXC without 4GB limitations, sans EXFAT which is proprietary). Just wondering.

Sent from the jar of Jelly Beans
[Samsung Captivate Glide] :
Finally dared myself to run my phone at 1.4 GHz long enough (at the time of this post, an hour have passed since turning up the CPU speed and still operating at 1.4 GHz). No problem - even battery drain was kinda normal (IO: SIO / CPU: Interactive) except when I am connected to internet via EDGE link. Still cool to the touch. No problem-o.

EDIT: 5 minutes after the above post, I decided to up the ante - set the governor at Performance, which is naturally dangerous, I left it at 1.4 GHz at 100% of the times for ten minutes. This phone's seriously tough.

Sent from the jar of Jelly Beans
[Samsung Captivate Glide] bobbinthreadbare:
I messed with some governers and stuff last night too, managed a 79xx on Antutu at 1.4 with performance. 1ghz is perfectly fine for me but damn 1.4 is fast.
[Samsung Captivate Glide] :
Nice. And, I like the 1.4 GHz speed. It was definitely maintainable long enough.

Sent from the jar of Jelly Beans
[Samsung Captivate Glide] :
Decided to set it at 1.4 GHz as default speed for maybe 6 hours - I lost track of time anyways. :P

And the battery life is still good enough - the CPU have been spending half of the time at full speed. Think I will leave it at this speed for good.

Sent from the jar of Jelly Beans
[Samsung Captivate Glide] dman3285:
For those running PACman flash the last kernel download named Covenant-Kernel-V3-pacman-cam and camera will work.. enjoy ..
[Samsung Captivate Glide] :
I flashed V3 onto older CM10 Beta 2 and camera works wonder. :D It's just like a Christmas present. Thanks, dman3285 and roothorick!

EDIT: camera shutter's so fast that it only took lgCamera app 300 - 500ms to save the picture after shutter is "depressed". That's real nice thing to be seen from both of your efforts.

Sent from the jar of Jelly Beans
[Samsung Captivate Glide] santimaster2000:
So, we need to use the LG Camera app in order to get the camera working or we can just use the stock camera app ?
[Samsung Captivate Glide] dbrannon79:
Stock camera app!
[Samsung Captivate Glide] thescot33:
Thanks dman...everything works great so far! Even the panorama pictures! U da man! XD

Sent from my i927 JB PACman
[Samsung Captivate Glide] :
Santimaster2000, you can use stock camera, it works fine. However, any camera apps from Play Store works.

dbrannon79, yea but not just stock one, however as above.

The lgCamera from RubberBigPepper on Play Store allows me to adjust the camcorder codec and quick way to adjust the picture settings - everyone have their preference anyhow.

Sent from the jar of Jelly Beans
[Samsung Captivate Glide] :
CPU voltage settings I used in 25 millivolts step as set in SetCPU:

1.4 GHz - 975mV

1.3 GHz - 950mV

1.2 GHz - 925mV

1.0 GHz - 900mV

912 GHz - 875mV

816 MHz - 850mV

760 MHz - 825mV

608 MHz - 800mV

456 MHz - 775mV

312 MHz - 750mV

216 MHz - 725mV

Tested this voltage settings whilst stressing the CPU for any sign of instability. Still works quite well.

Sent from the jar of Jelly Beans
[Samsung Captivate Glide] roothorick:
Oh shush, all I really did is twiddle one text file :P It wasn't even my idea, really, I basically just did the lifting.

By the by, are you stress testing your OC/undervolts? I'd like to UV my Glide a bit to get a little more battery and make it run cooler (even at 1.0 it's getting a bit warm) but I need this thing to be reliable so I'd have to test it somehow.
[Samsung Captivate Glide] thegreatergood:
have you had any freezing/rebooting while testing voltages at all?
[Samsung Captivate Glide] :
Nope. I have been stressing it out for a while, but I personally would recommend testing it on your phone first just to take variables in 40nm low-k SOI process used to produce this Tegra 2 CPU into account. I have had no problem with it on Performance governor at 1.4 GHz. I recently showed my brother that it is scary fast (zero lags).

EDIT: it may have something to do with kernel's CPU scheduler and multicore supports. It may work for Jelly Beans, but not sure about ICS. Still it warrant a try.

And yes, roothorick, I have been leaving it this way ever since two days, but switched to SetCPU yesterday to make sure voltage sticks (and yes, I will give SetCPU developers some cash as soon as I get paid, the version is Donate and it's doing great job). And to answer the CPU temperature question; barely warm. It's left at 1.4 GHz as it's better than 1 GHz in a big way.

Sent from the jar of Jelly Beans
[Samsung Captivate Glide] roothorick:
How did you get the voltages to apply? Even after reboot it's still using the stock voltages.
[Samsung Captivate Glide] :
I used SetCPU (and you have to select Set at Boot, and it works every time). Maybe the kernel have fail-safe mechanism, just depending on how it's provoked.

Sent from the jar of Jelly Beans
[Samsung Captivate Glide] :
Like in the screenshot here.

Sent from the jar of Jelly Beans
[Samsung Captivate Glide] roothorick:
See, I interpreted that screen as "this is what you want (saved), and this is what you're getting (current)". I set 1200 to 600mV, forced that clock, and ran a stress test, the fact that it didn't seem to find any problem at all with such a severe UV strongly suggests to me it's not actually being applied.
[Samsung Captivate Glide] thegreatergood:
precisely... these voltages are impossibly low...
[Samsung Captivate Glide] :
Um. Interesting. Maybe dman3285 would have to pop in voltage daemon into the kernel, but still, it's no cakewalk in the park, due to the protection mechanism inside kernel (that's to prevent the CPU from dropping out).

EDIT: I now doubt voltage daemon is installed for some reason because I tried Daemon Controller, and applied voltage - the app crashed.

Sent from the jar of Jelly Beans
[Samsung Captivate Glide] :
Guess this screenshot of IncrediControl explains it all.

Sent from the jar of Jelly Beans
[Samsung Captivate Glide] Rawr0w0:
I'm running PAC v18 and Covenant Kernel v3 with cam fix without adjusting anything...

been running 11hr 16m 50s+ and only at 59%
[Samsung Captivate Glide] :
roothorick and thegreatergood, I finally managed to freeze my phone at 1,100mV at 1.4 GHz, so guess I succeed in finding the limit. I used 3c's CPU Tweaker to try and drive the CPU into ground.

EDIT: Froze again at 1.4GHz at 1.125V and I am progressing slowly until I see no problem. You can try 3c's CPU tweaker and see if you can get the CPU to crash at that voltage, just so I can be sure I am not seeing things.

SECOND EDIT: 1.150 V for 1.3 GHz and 1.175 V for 1.4 GHz's the stable voltage (without crashing from sleep). I will do for the slower frequency then finally put up the best voltage graph as far as CPU tweaker's concerned.

Sent from the jar of Jelly Beans
[Samsung Captivate Glide] roothorick:
Are ARM CPUs somehow different from x86 in the undervolting thing? Because in PC processors, every single chip is different, and for any two chips that sat right next to each other on the assembly line, there's a good chance that only one is stable at a given OC or UV. I would assume that cellphone CPUs are the same.

All I'm saying is, what works on your phone is probably not all that useful to us :P
[Samsung Captivate Glide] :
Not that different from x86 (you can try it if you have AMD CPU - I have), and it strictly depends on two things: temperature and frequency. And "what works on yours won't works on mine" is exactly what I meant; a variable in chip making (for example - some peoples are lucky to run their Phenom II 940 at 4 GHz or faster on air cooling alone whilst I am not) thus your argument "the computer processors are different even if they are the same model" is valid.

The maximum voltage Tegra 2 can handle is 1.225 V (default for 1.3 - 1.4 GHz in the kernel). 1.200 V may work - either you are lucky or you are not.

Sent from the jar of Jelly Beans
[Samsung Captivate Glide] roothorick:
Is that just the kernel-imposed limit? I'd fully expect the chip to take quite a bit more than that if you manage to keep it cold (arc threshold for 40nm is what, 5V?), and even on stock cooling should be able to push above 1225 for many Glides.

I think 1.6 should be attainable for most, about half should be able to go as far as 1.8 and a lucky few to the big 2.0. But I'm just speculating.
[Samsung Captivate Glide] thegreatergood:
That's a kernel imposed limit yes ... I'm fairly certain it can take at least up to around 1400mv....
[Samsung Captivate Glide] :
The kernel-imposed limit is for the protection of the hardware it's operating on.

Keeping it cool? Meh, RAM is on the top of SoC die. FCBGA version (non-package on package favor) might be better for this. I have done it as a test, it was alright as well - PoP doesn't help with cooling at all. But, I am glad it runs cool at 1.4 GHz for me.

EDIT: This is the Tegra 2 module (for the mini-ITX motherboard); http://www.secoqseven.com/en/item/quadmo747-x_t20-/ and I will definitely go crazy with the idea of overclocking it to a nice and big numbers (2.5 GHz maybe, or faster with TEC peltier).

Sent from the jar of Jelly Beans
[Samsung Captivate Glide] :
1.225 V is actually a good idea as my phone finally froze at 1.175V - that voltage's to give us some leeway at 1.3 and 1.4GHz. 1.225 V may cost us bit runtime, but hey we have to give the tradeoff a careful consideration.

Nevertheless, I definitely give this kernel a thumb-up.

Sent from the jar of Jelly Beans
[Samsung Captivate Glide] Evil Alex:
Mine's running great on 1175mV for 1.4Ghz. But it does freeze when I go lower than that. I'm using the C.A.M.P.+ ROM, which comes with the Covenant kernel, apparently V2.(But the camera does work...?)

Battery life has been awesome, I've had it on my phone for a little over 2 days now! :)
[Samsung Captivate Glide] :
That's good. :D And Version 3 of Covenant kernel have fixed camera.

Sent from the jar of Jelly Beans
[Samsung Captivate Glide] AzraelsKiss:
V3 shows up as V2 in about phone.
[Samsung Captivate Glide] yohan4ws:
Can anybody else confirm using covenant v3 that volume can't be adjusted while in a call if the screen is blank ?

I've noticed I need to pull the phone from my ear for the sensor to unlock the screen in order to adjust the in-call volume.
[Samsung Captivate Glide] kick buttowski:
ondemand governor doesn't seem right, devices gets all laggy and doesn't look like it's ramping up and down properly.
[Samsung Captivate Glide] dman3285:
Just a heads up.. do not try and flash any of these kernels on CM 10.1. The ramdisks are different and it will not boot. I already included a modified covenant kernel in cm10.1.
[Samsung Captivate Glide] roothorick:
I've noticed the governors seem goofy in general. Anything besides performance or interactive makes the phone act goofy. Also it seems to randomly get set to userspace for no reason.
[Samsung Captivate Glide] dman3285:
Sounds like your phone is goofy.. I've ran this kernel since day 1 on every governor. No goofiness here..

And the only governor that was added was smartassv2. All others are stock in the kernel..
[Samsung Captivate Glide] jayjayjoker2:
Great job flashed this phone runs way smoother
[Samsung Captivate Glide] yohan4ws:
I've also noticed when using different governors that the phone lags and reverts back to userspace as well. I started using smartassv2 (cm10 with covenant kernel v3) and then used covenant v3 again with pacman ... it's still my daily driver. I'm using interactive for the governor now and the phone seems to be running really good on battery like 5% in an hour vs. 10% per hour like I was getting before... i also disabled cobalt theme which had animations in the notification area sooo its likely the issues were combined on battery.

,

For lag, however, to put myself back on topic - I had lag, really bad lag. Switching apps, scrolling especially was jittery using conservative , on demand, powersave. Even when increasing the minimum frequency to 312 it still lagged. It didn't happen right away, usually after half day or some hours of the phone sitting on idle it would happen.

This is on i927(r) Rogers branded, Virgin Mobile (Bell) network in Canada.
[Samsung Captivate Glide] bobbinthreadbare:
I had some random lag the other night when I was just playing some games and stuff. Same as you mentioned - scrolling through apps, switching etc. A quick reboot and it was back to normal.
[Samsung Captivate Glide] Evil Alex:
Mine stays on interactive all the time. ONLY after a reboot I find it set to userspace sometimes. I then set it back to interactive and all is good again! I'm unsure what the source of this problem is, could it also be the app used for OC/UV?

I'm using System Tuner Pro(which doesn't show any voltages for the two lowest frequencies, BTW). I seem to recall dman uses cpu control? So perhaps it's not the kernel? I'm just thinking out loud, here. What app for OC/UV are you guys using?

Sent from my SGH-I927
[Samsung Captivate Glide] dman3285:
I use the performance settings that's provided by cm 10 in the OS. Works better than any app. And it resets to userspace because that's the default governor.
[Samsung Captivate Glide] kick buttowski:
I was using system tuner and got this goofy behavior, using performance options in settings all seems good.
[Samsung Captivate Glide] :
Sorry if I pulled this thread from the grave - dman3285, I wanted to ask you a question - do your kernel default to 1.3 GHz upon reset / reboot?

I am curious as I kinda want 1.4 GHz speed to stick, along with the remembered voltage settings.

I have been running this kernel for a few weeks now, and it's still quite good. :thumbup:

EDIT: I decided to actually use what's in CM10 performance settings. All's jolly now.

Sent from the jar of Jelly Beans
[Samsung Captivate Glide] dman3285:
I GHz if not specified to set on boot
[Samsung Captivate Glide] kick buttowski:
Dman, you think you can add some voodoo goodness to this kernel ?
[Samsung Captivate Glide] :
Ah. Alright. I see - same with stock kernel. For funny reason some OC apps revert back to 1.3 GHz, so I had to stop using CPU Tweaks' OC daemon because of its unusual habit of dropping 100 MHz lower than I would like it to run at - every reboots. Went back to CM10's own OC daemon because it sticks every time I reboot - used 3c's app instead for voltage control.

Sent from the jar of Jelly Beans
[Samsung Captivate Glide] kick buttowski:
Would love to see a 4.2 version of this :)
[Samsung Captivate Glide] greeneyez15o:
Does it work on .9 literom
[Samsung Captivate Glide] yohan4ws:
I'm going to assume yes, but some functions in literom may not be carried through such as the keyboard lights etc.

This kernel works great on CM10 and Pacman and Paranoid based on JB 4.1 ... still have issues with bluetooth, microphone (skype) and is pretty hungry on battery.
[HTC One X+] lafite66:
My head is spinning on trying to figure out if I can unlock the bootloader with my device. I've been to HTCdev to find my device and it's not listed.

Could someone please direct me to the directions to do so?

thank you!
[HTC One X+] Synseer:
On the htcdev website selecyt the option that says something like all ornery devices at the bottom of the list. And then follow the instructions.

Also check ohtt thew thread in the development section for the unlock and root tool kit
[Samsung Galaxy Player 4.0, 5.0] iKosmos:
I have a GP 4.2 and want to know how I can change the Internet App on the Homescreen below the dots for changing screen pages?

I am really liking my first android more than my itouch but I DDID like changing the default homescreen apps on the iTouch. I changed the default Media Players and Web browser on it.

I would like to change the default Internet icon to launch a better web browser. For that matter I would change the Video player to launch something else as well.

Thanks.
[Samsung Galaxy Player 4.0, 5.0] augiem94:
Open your app drawer press menu -> edit and drag and drop icons to your dock and rearrange your app drawer how you wish
[Samsung Galaxy Player 4.0, 5.0] iKosmos:
Thanks. That was easy! Can you recommend a good "Beginners book that might cover things like this (It was NOT in the docs that came with my unit.)

Now my last complaint with Android is finding a good replacement for the Audio player that has navigation similar to an iphone wher eI can navigate albums in and out like folders instead of everything being in just a really looooooong list!

Thanks again.

:cowboy:
[Samsung Galaxy Player 4.0, 5.0] augiem94:
Personally i have my 2500+ song uploaded to google play music, its a great cloud music player. And i dont know of an in- depth guide to android mainly because i just figured it out as i went, i bricked my player within the first 2 days of having it so i had to get good, fast. Just lurk a bit, youll get the hang of it.