yashsingh1/xdaforums huggingface dataset:
[Nexus One General] jboxer:
Changing the apk contained in this thread did not work for me. The pinch and zoom was still broken.
[T-Mobile LG G2x] Deleted member 2653512:
so now that MIUI 1.9.23 is out for the optimus 2x... are there any devs feeling froggy enough to get it on our g2x? :)

EDIT: found it on RootzWiki. doh!
[Touch HD General] swoo:
Hi, reading all these posts has confused me - Can Android be installed and run from internal phone memory?

I have 2 SD cards, but none of them is working, unfortunately.

Other issue - how can I format SD and split it in 4 parts? I have no port on my PC to put there microSD (which blackstone has), so it seems impossible for me to format my SD.

I have tried to install Android for numerous times, but the instructions are so hard to understand, I haven't managed :(

Is there any youtube video showing step by step (and describing) process (including what files should be downloaded and used)???

I have flashed my phone with WIN6.5 like a million times, that is easy, everything is understandable, but Android is like chinese alphabet :)

Thanks in advance
[Touch HD General] arrrghhh:
1. Android cannot be installed to run from internal memory at this point in time. There's people working on it, but until HaRET (running off SD card) is stable, it won't be stable running from internal memory either...

2. You can attempt to add some lines to your startup.txt that *could* help your SD card issues:

msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave

3. I might be biased here (yea, definitely biased :p) but my build (FRX07.1) does not require partitioning of your card. One partition is all you need ;).

However, there are some advantages to partitioning the card, and I wouldn't want to completely discourage you from using other builds - if you're on Windows, there's a great utility called 'Mini Partition Wizard' or something to that effect. Works well.

There are some videos on how to partition, but they're not up to date. I would start with my build, since it doesn't require partitioning. Once you get sick of it, come back and partition your card and give the other builds a whirl. ThaiDai's app helps with that.
[Fascinate Android Development] comradesven:
INFORMATION REGARDING OC/UV VALUES

The default values in the Samsung source are as follows:

1000MHz arm_volt=1275mV int_volt=1100mV

800MHz arm_volt=1200mV int_volt=1100mV

400MHz arm_volt=1050mV int_volt=1100mV

200MHz arm_volt=950mV int_volt=1100mV

100MHz arm_volt=950mV int_volt=1000mV

arm_volt_max=1350mV int_volt_max=1250mV

Of these the values that everyone talks about are the arm_volt values. arm_volt is what is modified by Voltage Control, Pimp My CPU, etc. int_volt is a secondary line that is not reported or directly adjustable by the user. The Glitch kernel plays around with int_volt for their different "leakage" versions, demonstrating that int_volt, too, plays a significant role in max overclock, but this isn't a concern of mine at the moment.

arm_volt_max is set to 1350mV which would then be the theoretical "overvolting limit". In this example you could overvolt 1000MHz by up to +75mV before running into driver limits.

Here are the default values in TKS.

1700MHz arm_volt=1500mV int_volt=1250mV

1600MHz arm_volt=1500mV int_volt=1250mV

1500MHz arm_volt=1500mV int_volt=1225mV

1440MHz arm_volt=1500mV int_volt=1200mV

1400MHz arm_volt=1450mV int_volt=1175mV

1300MHz arm_volt=1400mV int_volt=1150mV

1200MHz arm_volt=1350mV int_volt=1125mV

1000MHz arm_volt=1250mV int_volt=1100mV

800MHz arm_volt=1200mV int_volt=1050mV

400MHz arm_volt=1050mV int_volt=1050mV

200MHz arm_volt=950mV int_volt=1050mV

100MHz arm_volt=950mV int_volt=1050mV

arm_volt_max=1500mV int_volt_max=1250mV

Let's look at 100-1000MHz first. At 1000MHz there is a slight -25mV arm_volt undervolt (or just plain old undervolt) as well as a -50mV drop in int_volt for all frequencies <1000MHz. In other words, for stock frequencies there is already an undervolt built right in that you should take into account.

At higher clock settings the values are essentially best guesses at the proper settings for that speed, refined by community experience, so talking about a "proper" undervolt level is a little bit inaccurate. Note that voltage is maxed out at 1440MHz and above, but the secondary int_volt values keep increasing. The effect is a ramping up of total power supplied with increasing clockspeed, as it should be.

So I wouldn't be at all surprised to see 100-1000MHz benefitting from a couple +25mV boosts compared to "the settings I used to use on my old kernel" here and there and I'd pay attention to differences between the default voltages, especially 1200MHz+, of the old and new kernels. With different defaults, seemingly different undervolt settings could translate into the exact same amount of mV supplied.
[Fascinate Android Development] nitsuj17:
awesome man...great to see eh09 finally getting some kernel love :o

hopefully once imoseyen gets his i500 from someone sending it, u can get some more help as well :)

(if u bet bln working ill reactive my fascinate for awhile lol)
[Fascinate Android Development] skynet11:
I can give feedback about what DOES work despite being in alpha stage:

Voodoo color is working (personally, I like to go "punchy" on gamma hack)

OC is stable at least to 1400 for me with default noop/interactive, and with 100mhz state disabled (I could only go up to 1200 on MIUI without immediate instability on Glitch)

My phone is quite stable (so far) on this kernel, more so than what you'd expect on an alpha release

I'm glad you posted your own thread for this kernel comeradesven :D

Another Fascinating post by my XDA app...
[Fascinate Android Development] ssignature:
This kernel is what I've been looking for

With a battery fix and in-call volume fix, I think I'll have a permanent GB solution! I'm hard of hearing and most of these GB kernels just don't cut it for me. CM7 (MTD) works, but Slacker caching doesn't work because of the file system. Slacker says tough s**t, we're not supporting it. So here we are. I'll put this on my spare Fassy and test it out today.
[Fascinate Android Development] skynet11:
I'm also hard of hearing, but in-call isn't too, too bad for me on speakerphone... Media volume, on the other hand... IDK if media volume has anything to do with this kernel or if it's an EH09 issue...

Another Fascinating post by my XDA app...
[Fascinate Android Development] FDro:
Does this kernel use the Nexus S color source like on Glitch's kernel?
[Fascinate Android Development] comradesven:
If you're talking about mDNIe values, then no. I tried adding some new values earlier and it didn't work. It does have a ported Nexus S framebuffer driver like all Voodoo Color kernels AFAIK.
[Fascinate Android Development] droidstyle:
Awsome work sir!!
[Fascinate Android Development] ekowanz:
which one is better... voltage control or pimpmycpu?

now i use voltage control oc up to 1400 with uv 50 all way down. so far run smooth.

i use noop and ondemand, if i use conservative then phone get lag
[Fascinate Android Development] djblu:
I purchased SetCPU originally, can I use it instead?
[Fascinate Android Development] comradesven:
IIRC the answer to that for this variety of overclock code is as follows.

Short answer: No

Long answer: Maybe but you might/probably will have problems
[Fascinate Android Development] mgrimmenator:
will this eventually have a -100uv kernel. i've the best battery life using pbj kernels with that setup. hope this gets it too. will switch kernels once all the kinks get worked out.

thx for your efforts.
[Fascinate Android Development] s44:
Voltage Control = roll your own undervolt

The only real missing feature is BLN.
[Fascinate Android Development] kuronosan:
Can't seem to get it to download on my fiancee's phone.
[Fascinate Android Development] laureanop:
Just flashed 9-27 through cwm and flashlight confirmed working. Awesome job

sent from my SCH-I500 PWGB 2. 0b3 voodoo , shot v7
[Fascinate Android Development] JJHunterx:
Does this kernel support non OEM batteries?
[Fascinate Android Development] skynet11:
Idea: RAM optimization, if feasible :)

Another Fascinating post by my XDA app...
[Fascinate Android Development] splashattack:
So far this kernel is working out great for me. Loving voodoo color. Makes me wish I waited on buying that Thunderbolt off eBay. The cwm file didnt work for me (probably a bad download, stayed on bootanimation for WAY too long, lagging the animation) so I used the Odin version instead. Booted instantly. Many thanks for putting this together.
[Fascinate Android Development] djblu:
Thanks for the clarification. next question:

how do keep from getting stuck in boot loop? Do I need to reflash my recovery immediately after flashinging the kernal?
[Fascinate Android Development] Dj-Dubster_TN:
I've been using auto killer for awhile and I've been using settings similar to what @laurenop put up a few posts back, 15360,10240,12800.

But I changed to what u put up lauren and its running great now,I also use the advanced tweaks to,remount partitions with noatime,battery tweaks,ui optimization,and I'm experiencing no lag at all

Tsm -ressurection,tksgb10/12,shot xix
[Fascinate Android Development] AtropineNa:
What settings are you referring to? I only found his 15360,10240,12800 settings... which i'm running right now
[Fascinate Android Development] laureanop:
The same as 40, 50, 60 in mb

PWGB,TKSGB10-14, adren shot xix, honeycomb2.03, ec09 radio.
[Fascinate Android Development] droidstyle:
I got rid of my lag by disabling lagfix...seems alot easier than running these extra programs to fix the lag.
[Fascinate Android Development] skiddingus:
Volume is now perfect on my phone. Thank you.

Update: Any idea why version 1014 is so much larger than 1012? I just had my phone reboot during a call. I called back and the phone locked on the blank screen when I tried to hang up and then it rebooted again. It has never done this until 1014.
[Fascinate Android Development] skiddingus:
rebooting when using phone

I think there may be something wrong with the 1014 update. I installed it tonight on both mine and my wife's Fascinate and both of them lock and reboot when making phone calls. (about half the time) They each did it several times before I flashed back to the 1012 version on both phones and everything is fine now. Is anyone else having this problem?
[Fascinate Android Development] pahick:
Im on 1012 and had mine reboot twice. Been fine for a couple hours. But again, im on 1012 and it has happened.
[Fascinate Android Development] laureanop:
Interesting, I had mine reboot for no reason once on 1014 and another time on 1012. If it happens again I'm going back to 1006(I had no volume issues to begin with)

PWGB,TKSGB10-14, adren shot xix, honeycomb2.03, ec09 radio.
[Fascinate Android Development] skiddingus:
Was is during a call or when you tried to hang up? It weird that both of my phones started doing it as soon as I updated them. I just made several calls back and forth between them and neither rebooted. The problem seems to be gone on 1012 for me.
[Fascinate Android Development] laureanop:
Unplugging in from the charger the first time, and on screen off the second time

PWGB,TKSGB10-14, adren shot xix, honeycomb2.03, ec09 radio.
[Fascinate Android Development] droidstyle:
This part of the reason I tried disabling lagfix... random reboots and lag. So far no reboots on 1012 and super smooth. Makes no sense because on pwed05 I noticed a huge difference with voodoo lagfix. Try it once and tell me what you think? Maybe it's just placebo effect lol.
[Fascinate Android Development] laureanop:
I can't right now I'm at work driving and I can't risk going into a boot loop. I'll disable lag fix when I get back home later on tonight and will post my impressions late afternoon tomorrow.

PWGB,TKSGB10-14, adren shot xix, honeycomb2.03, ec09 radio.
[Fascinate Android Development] skiddingus:
As soon as I had a couple reboots on 1014 I tried disabling lagfix. The very first phone call gave me another random reboot. So I flashed back to 1012 and it has been fine since. I have not reenabled lagfix yet. My wifes phone did the same thing on 1014 so I just flashed it back to 1012 but left the lagfix enabled. So far, neither has crashed on 1012.
[Fascinate Android Development] AtropineNa:
So you're running this TKS kernel but disabling lagfix? Or you're flashing the stock kernel therefore disabling lagfix? Thanks, I'm going to try what you're doing and hope the lag gets fixed
[Fascinate Android Development] droidstyle:
I disabled lagfix on the tks kernal.
[Fascinate Android Development] the entity:
Sad to say that I'm getting reboots during calls. Yesterday it was after the battery went to ~%10 , but today had about 80% and rebooted, then once it came back up, I called the person back, and in the mid of my apology, it happened again lol.

*on 10/10
[Fascinate Android Development] droidstyle:
try the tks kernal with lagfix disabled...seem to fix reboots and lag for me. May not work for everybody tho, being the fascinates track record lol.
[Fascinate Android Development] skiddingus:
I'm still back on 1012 with both of my phones and have not had a reboot since flashing back from 1014. One phone is voodooed and the other I converted back when troubleshooting. Here are a couple interesting things since the phones are otherwise identical. (both are overcloced to 1200mhz) The Antutu benchmarks are nearly the same. The Quadrant benchmarks are completely opposite. The voodooed phone is WAY faster. They must be completely different tests.

I laid the phones side by side and ran them both through the paces. I ran all kinds of apps, and did everything I could to try to see a speed difference. There is nothing I can see anywhere. If the quadrant benchmark was anywhere near accurate, one phone should be much slower than the other. I may just disable voodoo on the other phone because I just can't see any advantage so far.
[Fascinate Android Development] jcurley:
I notice on my 10/12, I start to get reboots once the battery drops below 10. Ever one percent, the phone reboots. That has never happened before.

Edit: ran bluetooth in the car last night and it was perfect. Ran at 200. Good work Comrade.
[Fascinate Android Development] Wolfkmann:
You can ignore my previous post. My phone is functional again, after 6hrs of panic.

I had to use the pit file and the stock edo5 kernel. For whatever reason, I cannot get it to function with any other kernel, this one included. Even after I resurrected it, I tried to odin this again, and it was a brick. Re-odin stock ed05 kernel and it's alive. So currently I have GeeWhiz 2.1 on the stock kernel and am now reloading everything.
[Fascinate Android Development] laureanop:
Are you under volted and by how much ?

PWGB,TKSGB10-14, adren shot xix, honeycomb2.03, ec09 radio.
[Fascinate Android Development] comradesven:
OK, since you guys have been getting random reboots on 1014 I have reverted a couple of the changes between 1012 and 1014. Perhaps it was the compiler optimizations (in 1014 it is no longer optimized for size, therefore the entire kernel is bigger and has more compiler tricks in it, which may be worse for stability). I hope it's sufficient as I can't track down every bug. It isn't as though the kernel is the only variable changing. In fact I had to reodin everything two days ago on 1012 because of failed boots upon trying to reenable V6 Supercharger, when I hadn't had any problems toggling it previously. I'm keeping this install free of Supercharger or Adrenaline Shot or similar to see how it runs by itself.

There's some more stuff I want to try before another "official" release but I'll upload another "unofficial" one with zram in a bit.
[Fascinate Android Development] darkmage1991:
this may not be possible, but not sure if this is controlled by the kernel or rom, but is there any chance of adding the required bluetooth protocols for wiimote controller and sixaxis controller?

heres the dev's websight for the sixaxis controller if someone needs to ask what protocol is needed http://www.dancingpixelstudios.com/sixaxiscontroller/about.html
[Fascinate Android Development] jcurley:
200-400 -75

800-1200 - 50

But it has not rebooted tonight and I just dropped below 8. So it is a random thing. I have my heap at 48 and running optimizer optimal setting with ui and partition. Nothing this time.

Maybe my optimizer corrected the problem.

Not sure. It is random though.

Does not reboot during when charged.
[Fascinate Android Development] laureanop:
My guess is that if you're under volted by 75 + whatever Uv is built-in the kernel at any battery level below 10-15 percent there' s just not enough current to support certain functions thus the re boots.

I have to say that my phone has re booted just once since I installed 1014

PWGB,TKSGB10-14, adren shot xix, honeycomb2.03, ec09 radio.
[Fascinate Android Development] jcurley:
Just rebooted.

Ok, adjusted that to 50-across the board.

So far so good.

Thank you.

Pwgb

Tks

Adrenaline XIX

mem optimizer

W

Vm heap 48
[Fascinate Android Development] laureanop:
My battery' s never been that low, can't test it

PWGB,TKSGB10-14, adren shot xix, honeycomb2.03, ec09 radio.
[Fascinate Android Development] comradesven:
Hi guys, sorry about the late unofficial release. I managed to lose data with git which is pretty hard to do and I had to redo some work while losing some. Anyway I was able to integrate zram into the kernel and you may find it interesting to play around with that. What is zram, you ask? Well, it's swap space, except on a compressed ramdisk. The LZO compression involved is pretty fast.

Odin tar.md5 http://www.mediafire.com/?8yemqilhlqiluq2

CWM zip http://www.mediafire.com/?cbk1w4bd65xke6c

To run the zram script just type "zram" into a terminal and run, it's pretty self-explanatory after that. To tweak sizes (the script uses by default 12.5% of available RAM) edit /system/etc/init.d/05zram, where the size is stored in bytes (do your own calculations) and reboot. imoseyon's original implementation used ~10%, and the CyanogenMod wiki, referring to compcache (pretty much the same thing) says about 25% is common. I have no idea how all this fits together with the other tweaks so give it a whirl if you're feeling adventurous.

Call volumes are the same as on 1014. From the discussion I can see that low voltage seems to have something to do with random reboots (this isn't unexpected) but if it looks like there's a real problem with stability on 1015 as opposed to 1012 and 1014 I'll look into it some more.

I also sent an e-mail to the guy behind the sixaxis controller app to ask what I can do to enable support for sixaxis in my kernel. If it isn't too much of a hassle I'll do that.
[Fascinate Android Development] AtropineNa:
If we disable lagfix on this kernel, will we still have wifi-tether protection removed? Thought about doing this cause should help fix lag... Thanks
[Fascinate Android Development] comradesven:
Yes, whatever hotspot monitoring Verizon was doing in the kernel has been removed. It's been removed from before I even started working on it.

I'm getting very little lag on a fresh install of TSM Resurrection with my kernel, Voodoo lagfix, and no additional tweaks, keeping in mind that what made my install break earlier was trying to reinstall V6 supercharger. Ah well, it's still early days yet.
[Fascinate Android Development] darkmage1991:
awesome :)
[Fascinate Android Development] laureanop:
@comradesven. I just installed 1015. I have the latest busy box. So I go to Terminal Emulator and I type in:

$su

#zram enable

Then it tell me that it's enabled and it gives me a value, and then phone re boots immediately without giving me a chance to do anything.

PWGB,TKSGB10-14, adren shot xix, honeycomb2.03, ec09 radio.
[Fascinate Android Development] comradesven:
I suggest running it immediately after boot. It does require about 46MB of free RAM to set up the ramdisk, after all...
[Fascinate Android Development] Bawb3:
I've only had two random reboots, both were during calls. Also both on 1012, haven't tried the newer ones yet.

Uv is 75 across the board, 100 at 200mhz, and 50 at 1200.

I may have to dial that back.
[Fascinate Android Development] laureanop:
Cleared enough ram and tried it again. Unfixeable bootloop. Cannot mount /system to restore nandroid. Back to square one
[Fascinate Android Development] comradesven:
:mad: Man I really wish random computer failure didn't happen like that. I mean seriously there's nothing I changed that I can think of that should cause such hilarity as what just happened to you, especially the part where you can't mount /system, which makes absolutely no sense whatsoever if you look at the script and what it does. Or my own experience with having to reodin everything a couple days ago.

Oh well, it is "alpha" for a reason I suppose.

Edit: The only "maybe" I can think of is if the partition needed a fsck.ext4. That should be included in the blue CWM that I'm pretty sure people are using but a) I'm not sure if it is b) I'm not sure if ext4 will refuse to mount if it needs a fsck c) You can hardly expect people to know to go into recovery with adb, find the binary and execute the correct sequence of commands all by themselves even if it is
[Fascinate Android Development] laureanop:
I'm back on PWGB and about to re flash 1015. No zram for now though. Wife upset

PWGB,TKSGB10-05, adren shot xv, honeycomb2.03, ec09 radio.
[Fascinate Android Development] jcurley:
Just loaded 10/15. Got an immediate reboot, but now seems stable. Well try to load the adrenaline now.

Edit: able to run adrenaline. Running great, listening to nfl and running tapatalk.

Perfect.

Pwgb

Tks 1012

Adrenaline XIX

mem optimizer

Vm heap 48
[Fascinate Android Development] pahick:
Im on 10-15 right now for the last hour. Seems alright. Something weird is, Ive never been able to go above 1300 with voltage control. With 10-15 im on 1400. Not sure why.
[Fascinate Android Development] darkmage1991:
weird i get those reboots also, i have no idea why it does it. it does it with no uv or with it uv to its max.
[Fascinate Android Development] Bawb3:
Yeah, I'm pretty sure it did it once with no uv or oc too. It doesnt happen often, but it can be annoying.
[Fascinate Android Development] droidstyle:
again, Try disabling lagfix on the tks kernal and see if you reboots and lag go away. Thats what fixed it for me... if you do please report back your results. Im curious if it was a fix for just my phone or its actually a fix across the board!

Laurenop, I never seen you post back about disabling lagfix? Did you try it by chance??
[Fascinate Android Development] HuskerDad3:
I've disabled lag-fix too and have not had any reboots. I had data loss problems when I did the voodoo conversion, so that's why I didn't do it when I came to TKSGB.
[Fascinate Android Development] laureanop:
Sorry man, I was trying to restore from the boot loop that the zram thing put me in. My wife is gonna kill me if I play with my phone today

PWGB,TKSGB10-05, adren shot xv, honeycomb2.03, ec09 radio.
[Fascinate Android Development] skiddingus:
So far 1015 has seemed to fix the reboot problem for my wife and I. None so far today with lagfix enabled on both and overclocked to 1200. If I do get another reboot, I'll try disabling lagfix on both and see if it happens again. 1014 made both phones reboot during half the phone calls.

Update....2 days and no reboots on 2 different phones. 1015 seems stable for me.