yashsingh1/xdaforums huggingface dataset:
[Streak 5 General] jnovello:
I've had my audible selection box checked since the first day, but last night everything seems to have gotten much louder. Typing on the keyboard was always a welcomed sound, but it is out of control annoying now. I didn't change anything. The only thing that changes it is to either put the ringer down to vibrate or shut it off in the setting all together. Is anyone aware of how to control the volume for these functions?:confused:
[Desire General] JoseF:
Hi,

I m running rooted desire with froyo.

When I play certain videos (stream via lan) I see this triangel in the middle of the video.

any ideas what to do to get rid of it?

Regards

http://picasaweb.google.com/lh/photo/JzADFciSHd_sXRJJuhBGiQ?feat=directlink
[Desire General] Flaggie:
What program are you using for that?

Maybe you are using a lite version and only the paid version gets rid of that play icon.
[Desire General] JoseF:
Hi thanks Flaggie for taking your time,

I m using AndrostreamPro bought via the market.

Tryed with ORB same issue.

Regards

JoseF
[Desire General] waebi:
put simply, the modded ones have way more functions than the official ones, contain newer kernels, are often faster and may also look quite a bit different regarding the user interface.

edit: just have a look at the Desire Development Section and check out the with [ROM] prefixed threads, you'll often see a list of features.
[G1 Q&A, Help & Troubleshooting] qwerty3656:
I need a phone and the primary objective is best call quality while I am at work. I had a G1 and am a big android fan. I currently have a cheap temporary samsung while I figure out which phone to get.

Talked to technical support at T-Mobile and they said that the smart phones do have stronger frequencies (so that is why my cheap temporary phone is not as good in terms of signal strength as G1). However, tech guy said for my situation I should consider a Blackberry (specifically BOLD). Reason being is that I have WIFI at work and Blackberry's are the only phones designed to make calls over wifi. I told him I tried Vonage with the G1 (and wasn't happy) he said no the Blackberry technology is much better.

I really like android, but again I need best voice quality (I use my cell phone as my work phone - no land line) - data/bells & whistles is a distant second.

Any fatal flaws with Blackberry that I am overlooking before I go and sign a 2-year contract?
[G1 Q&A, Help & Troubleshooting] lbcoder:
Oh, and as for this "stronger frequencies" thing... nonsense. The output strength of a phone is limited by the FCC, not by whether it is smart or dumb. You can have the dumbest phone in the world and it is free to output a signal with the same maximum intensity as the strongest smartphone.
[G1 Q&A, Help & Troubleshooting] ilostchild:
that was some good enough, i jus felt as if i was in school bout Phones and what not Lol
[Galaxy S I9000 Q&A, Help & Troubleshooting] m3talm0rph:
I have seen that my Galaxy S has a maximum output for my Sennheiser CX-300 II a lot lower than my Cowon S9, is there a way to turn the volume up without distortions?
[Galaxy S I9000 Q&A, Help & Troubleshooting] }{Alienz}{:
Not that I know of. However, you can use the audio quality fix provided here to improve the quality of music.

http://xdaforums.com/showthread.php?t=735918&page=1
[Desire Q&A, Help & Troubleshooting] nitrox1:
Hi all,

Sorry if this questions been answered already.

But why is everyone saying that the new HBOOT is unable to be rooted.

Is it locked down, and how?

Or just it hasn't been done yet?

Thanks for all info, and explanations :confused:
[Desire Q&A, Help & Troubleshooting] bigdan35:
http://xdaforums.com/showthread.php?t=745903

It can be now, via downgrading to 0.80 :)
[Desire Q&A, Help & Troubleshooting] nitrox1:
Ok it can be downgraded, but why can't the newest one be rooted?
[Desire Q&A, Help & Troubleshooting] nitrox1:
Is this an unanswerable question?
[Desire Q&A, Help & Troubleshooting] nrosier:
Cause the exploit that was used in the older hboot was fixed and no-one has found a new one yet. Be our guest if you want to find one :D
[Desire Q&A, Help & Troubleshooting] nitrox1:
Well as a slight noob, it's way over my head, but you know, "the only stupid question is the one not asked".

And I guess the answer from that its it just hasn't been done yet.

Thank you
[Desire General] rottunix:
Hi,

I updated my Desire like most of you during the weekend. And ofcourse moved some apps to the sdcard.

To my suprise today, some apps disappeared! I looked and it's the ones sent to the sdcard.

Even in the market they are showed as not installed. I had to redownload them and reinstall them again.

Anybody else experienced this issue? Got any solution/recommendation?

Regards,

Rayen

Update: had to reboot phone.

Sdcard was showing as empty.
[Captivate Android Development] blackjackboy:
OK guys, thanks to AJerman and many others who have posted in this thread, we have had success in compiling, loading and running a bug free kernel. The wakeup lag is there, but is highly reduced. Also, if someone could figure out how to compile a boot.img so that we can simply flash the kernel through recovery (I have no idea how), we would really be grateful, for all of us with either Linux or Mac. Anyway, here is the link, flash it through Odin3. http://www.multiupload.com/8UM79T8VNE . Bug reports are welcome, as are logcats. Please download SetCPU from the market, or for free from an xda thread (I forgot where it is, I think it's in the G1 section). Set to OnDemand to reduce wakeup, set lowest possible value for min, and highest for max (1.2 GHz). Of course, you can also use profiles if you are an advanced SetCPU user. Thanks for reading, here we go!

We now have a successfully compiled kernel for the Captivate that overclocks the phone to 1.2 GHz. The link is coming soon. Also, many are complaining about garbled audio on custom kernels, even compiling directly from source. Either way, that is now fixed:

The Hummingbird processor inside all Galaxy S models can theoretically be overclocked to 1.6 GHz [stable], and potentially past, if a genius can do that. Please, devs, post a link compiled kernel so that I can put it in the OP and people can start hacking their phones, I'll give full credit to the dev.
[Captivate Android Development] rob989_69:
AHHH, between froyo, the lag fix, and this, I'm tempted to return the captivate and buy a Galaxy S>...... Too bad they're $700.....
[Captivate Android Development] hansmrtn:
I will look at it and see what I can do. I will attempt to port it and make it a flashable zip. I cant guarantee anything :D
[Captivate Android Development] rob989_69:
You Sir would be my new hero.....
[Captivate Android Development] bedwa:
I'm going to look at it over the weekend as well since I've got the source for the kernel at home. I've got a friend that I can possibly get to be my tester as I only have an n1. We'll find a way guys.
[Captivate Android Development] hansmrtn:
Sounds like a plan my friend
[Captivate Android Development] rob989_69:
I'd really like to get involved in the Dev side of things. Problem is I know 0 about Linux. Anyone recommend a good tutorial? I got time and patience.
[Captivate Android Development] dseo80:
Dont port - use your source and follow directions in the main post
[Captivate Android Development] blackjackboy:
Don't port? I guess building from source would work too, but I don't see what's wrong with porting, but I know nothing about kernels, so I'm in the dark.
[Captivate Android Development] dseo80:
porting M110S/i9000 kernel to Vibrant will be very a difficult process.

It would be MUCH easier just to start from Vibrant source and apply changes there.
[Captivate Android Development] designgears:
ok, I have made the changes to the kernel source, just need to figure out how to compile it now :)
[Captivate Android Development] THATTON:
That is awesome to hear. It sucks to see the Vibrant development moving along much quicker than ours! So much so that I tried to flash an update.zip from the Vibrant threads and I can safely say that it doesn't work. ;)
[Captivate Android Development] dseo80:
here is steps i used on M110S (Korean Galaxy S)

1. install codesourcery toolchain (GNU/Linux version i think 202)

2. install initramfs directory and source list for your phone

2. goto linux-2.xxxx directory of source

4. make menuconfig - find and point to your initramfs source list

3. make -j8 HOSTCFLAGS="-g -O2" ARCH=arm CROSS_COMPILE="PATHTOTOOLCHAIN/arm-none-linux-gnueabi-"

4. Kernel: arch/arm/boot/zImage is ready -- if you see this you succeeded, file size should be 6-7MB

5. tar -cvf mykernel.tar arch/arm/boot/zImage

6. Flash using odin
[Captivate Android Development] Anthonok:
this would kick some ace
[Captivate Android Development] dalingrin:
Be aware that the reason for the lack of Captivate kernel development is because the kernel source currently does not work correctly.

The kernel source causes microphone distortion rendering calls worthless. My guess is that the problem is the A1026 voice processor driver can't be compiled as of now.

Check out NukaCola's speed fix thread for more info.
[Captivate Android Development] shaolin95:
I am subscribing to this one...cannot wait to OC :-)
[Captivate Android Development] AJerman:
Be aware that we have yet to be able to compile a kernel that didn't have sound distortion issues. I don't know what changes were made for this mod, but not even a stock kernel is working right after we compile it yet. Look in the speed fix topic for more info.
[Captivate Android Development] AJerman:
Okay, this is very preliminary, I'm not ready to give this to anyone for fear of blowing up people's phones and being blamed. I'm going to review my code changes a little more and test a little more, but this is on stock voltage:

Also, I got a 1540 Quadrant score running at 1.2 GHz along with the data folder on an ext3 partition on SD if anyone is curious. I was getting 1400s or so. I'd say it jumped around 50-100 points in Quadrant. Nothing huge as I expected, but not bad.
[Captivate Android Development] XorZone:
Sounds good. How is your voice quality?

You cood check it using loopback test:

*#*#197328640#*#*

Common-factory test-audio loopback- and both pcm and packet for the handset plz.
[Captivate Android Development] AJerman:
Same as every other kernel I've compiled to date:

http://www.zshare.net/audio/790823995f7a3425/

That's really bothering me. I mean, people can probably understand you, but you have to speak loud and clear for them to even be able to barely hear you. We need to get that figured out ASAP or all our kernel mods are a little less useful.
[Captivate Android Development] Croak:
Anyone savvy enough to see if this method can be applied to the Hummingbird?

http://code.google.com/p/milestone-overclock/

http://code.google.com/p/milestone-overclock/wiki/KernelModule

Doesn't require a kernel flash, and was very handy on my Milestone, easy OC on the fly, and no need for SetCPU and the problems it brings to the table.
[Captivate Android Development] anilkuj:
@AJerman , thanks for the great work !

quick question is there a 1.2 GHZ overclock kernel for the new JH2 Rom /

Thanks

Anil
[Captivate Android Development] flashman2002:
I used the zimage.tar that is in the first post with the JH2 update and seems to be working fine for me.
[Captivate Android Development] IStern:
set 200/1200 as the min/max, wow the phone feels muuuch smoother, especially out of sleep. let's see if i can still get a full day out of the battery...
[Captivate Android Development] TheTodFather:
Ajerman aka ..a german? Very nice? Thanks for the thorough reply. I see why you choose 1.2 ...so you skip from 1 to 1.2 ghz 200 mhz isnt bad at all. I agree. Yeah i saw your name on gizmodo. That **** is so cool. Well good luck with it broskii. I throw up a hail marry for you.

Hoping this rodgers firmware comes though nicely but i talk about that on the hspa thread.
[Captivate Android Development] TheTodFather:
what difference does it make to set it at 200 rather then 100?
[Captivate Android Development] slider2828:
100 causes crashes coming out of wake up... dont use 100.... 200 should be min
[Captivate Android Development] raspdeep:
im able to add steps, see my thread for i9000:

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

if u want to exchange notes, hit me with PM
[Captivate Android Development] Unhelpful:
Any chance we could get a patch for your changes? I wouldn't be surprised to see it apply cleanly to the Captivate sources, and it's by far the easiest way to exchange or explain source code modifications. I'm surprised not to have seen any patches for any of the other kernel work on Captivate either, really. :/
[Captivate Android Development] clown_luv:
Ive been told one thing that makes not want to overclock. People have said it could fry the proccessor. Is this true?
[Captivate Android Development] rob989_69:
Meh, first this specific OC is running at stock voltage, so the likelyhood that you would do any damage to the processor is almost non existant. In general overcloaking will put extra strain on CPU's. Keep in mind though, every single CPU is built the same way. Their then "clocked" during the testing phase to see what speed they will be released at.

Overclocking will most likely NOT result in a "fried" processor, but would shorten the lifespan a little bit. I've been running this since AJerman released it a week or so ago, my phone is solid as a rock and running temps are only slightly higher than normal.
[Captivate Android Development] anilkuj:
hi flashman in the first post of this thread i see only one multiupload link which i think is for JF6 , did you mean another thread?

Thanks
[Captivate Android Development] slider2828:
Not to be a **** but seriously if you don't know what over clocking entails you really shouldn't be in this forum. That is pretty basic knowledge even in computers
[Captivate Android Development] flashman2002:
That is the same one I used when I changed to the JH2. It is working for me with no problem. I have SetCPU and it shows 120000 so I am OC'd
[Captivate Android Development] TheTodFather:
I read that post from here about the oc'ing guy on the i9000 board about adding steps. Maybe this dude can help a few brothers out on this board. :( His kernal oc is not nearly as stable as the captivates 1.2 oc though. :( Well I look forward to overclock to 1.21 giggawatts soooon enough.
[Captivate Android Development] AJerman:
This kernel should work just fine for JH2. I've been using it for a while with no problems.

Absolutely, I'll get in contact with you and see if we can get it figured out. Thanks for the message!

Trust me, I'm not one to try to keep all my work to myself. This is an open source community, and we're all trying to make our phone better, so why not share? In fact, open source says we HAVE to share. The only reason I haven't posted anything yet is the same reason I haven't posted a new thread with a final kernel. It's not completely working yet. Once it's completely working I'll post a new kernel and patches for the code.

Not on stock voltage, which this is running. Your CPU will be fine.
[Captivate Android Development] Fortune090:
Have JH2, ext2 fix, and this overclock, and my phone is running beautifully fast. Got 2559 in Quadrant. Yeah, the wakeup lag is still there, but it's not too big of an issue to me.

I'm satisfied. :D
[Captivate Android Development] anilkuj:
Thanks Flashman
[Captivate Android Development] TheTodFather:
Holly sheeet mon! I had changed the min. from setcpu from 100mhz to 200mhz and no i have no lag what so ever!! Thanks for the suggestion. It immediately unlocks regardless of how deep it is in sleep. Damn! LIke the McDonalds jinggle goes da Da da da daaa I'm lovin' it!:)

I am also running JH2, BuglessBeast root, Lag fix 2.3 ext 2. 90% of the time i hitting 2500 quadrants. Very NICe...sexy time!
[Captivate Android Development] Fortune090:
I'm not sure how relevant this is to the wakeup lag, but I've noticed if I get a text, the unlock screen pops up instantly. Maybe just the way the unlock is triggered is the cause?

Pressing unlock button: ~3 sec lag.

Application-triggered unlock: No lag.

:confused:
[Captivate Android Development] TheTodFather:
ok i lied i had my usb hooked up and i was tethering while using pdanet and somehow having usb in. The phone would sleep but wake up instantly. I jumped the gun a little bit. Perhaps it never went into a deep sleep.
[Captivate Android Development] Fortune090:
Haha, yeah, that's what I figured, because mine was like that too. Really doesn't make much sense to me why this happens. Really hoping someone gets a fix for this on the Captivate soon! Would make so many things for this phone flawless... :D
[Captivate Android Development] BoostedSR20:
Subscribing... (just to catch when the fix comes for the stupid screen lag)

Just flashed the new samsung ROM, then this kernal. The phone has never run better.... until I try to turn it on. :o
[Captivate Android Development] THATTON:
So I was running some "experiments today" with the kernel and I decided to uninstall SetCPU since it doesn't seem to be optimized for our devices and I installed Overclock widget. Guess what- THE WAKE UP LAG HAS DISAPPEARED!!! For me at least. Check it out and report back. Someone needs to make a kernel that can ramp up and down at MUCH SMALLER intervals also, 200mHz is way to much imho...
[Captivate Android Development] BoostedSR20:
Just tried this exactly after reading your post. My linpack score went up super slightly, but still got the wakeup lag. It actually worked great one time, but then after that back to the lag.
[Captivate Android Development] THATTON:
Strange, mine is still working great! No wake up lag at all...
[Captivate Android Development] itsjusttim:
Any idea if this will work on my vibrant? And does this use any more volts than 1gh?

Typos/Nonsense due to Swype!

Stock Root + RyanZA LagFix + Captive Camera MOD
[Captivate Android Development] BoostedSR20:
Mine will work fine a few times, then start lagging again. Its weird. Your at 200-1200 right
[Captivate Android Development] slider2828:
I tried 400-1200, it works a little better but it drains the battery man!!
[Captivate Android Development] joedon3:
Anyone think about pushing the Captivate past 1.2? I want to be able to run Gingerbread like a champ!
[Captivate Android Development] mostyle:
Hmm..

At work yesterday listening to Pandora I noticed that as long as Pandora was playing there was no wake lag. I could leave Pandora running but pause the audio and the lag returned.

Any ideas?

I tested it with several apps that streamed data (youtube, etc) and only noticed the lag disappear with Pandora.

:confused:
[Captivate Android Development] BoostedSR20:
I also found with AIM running in the background, there is no screen lag...
[Captivate Android Development] AJerman:
200 MHz steps are what stock does, in fact, it has a 400 MHz step from 400 to 800. I think 200 is just fine, it's when we start getting to 400, 500, or 600 if I try to OC it even more that aren't as good.

If we ever figure out how to get steps added properly, I'll space every step out at 200 MHz difference.

This is a Captivate kernel, so you'll have issues running it on your Vibrant. However, I know there are already similar kernels on the Vibrant.

I have been able to boot it as high as 1.5 GHz, but I had issues. It did run a stress test fine, but it needed more work still. Until I can add steps, I'm not bothering with any higher overclocks because I don't want to be jumping from 800 MHz to 1.5 GHz. That's a big jump and it needs to have steps in between.

If you have something running in the background like that, it will keep the system in an awake enough state to prevent the lag. I don't know what the app has to do to keep it awake though, as you said Pandora only did it for you. Obviously there are apps running in the background all the time, so only certain things keep it awake.
[Captivate Android Development] BoostedSR20:
I'm getting it sometimes where the phone wont even wake up after hitting the power button. Combine that with the 3 second wake up lag, and you have ppl looking at you wondering why your staring at a blank screen like your trying to will it on...

Any way to flash back to the stock kernel? I'm torn, because it does really seem snappier...
[Captivate Android Development] Clienterror:
What is your setcpu profile set to?
[Captivate Android Development] BoostedSR20:
Took Setcpu off and tried the Overclock widget. Also I would say about every 1 out of every 5 or 6 times I turn it on, its instant. (with nothing running in the background, and no notifications)
[Captivate Android Development] Clienterror:
Yea that's weird, I got rid of setcpu as well and went to the overclock widget and it does seem better but not perfect. I haven't had any problems with it not turning on (unlike setcpu), I don't know if that's because I'm using samset 1.9e rom or what. Wish we could figure this out, especially since this is happening for every cappy custom rom I think so it has nothing to do with the cpu steps being to big.
[Captivate Android Development] BoostedSR20:
I went from the stock rom, to the new rom from samsung, and this kernel all at once. Never tried just the new samsung rom. Only other thing I did was to run Unleash the Beast.
[Captivate Android Development] dman1x:
I think that the reason the phone wakes faster when a program like that is running in the background is because its actually using processes. Other programs that run in the background arent always running. Most of the time those programs are in standby waiting for either there sync time or an outside connection like the messaging app and phone app. as long as the cpu and memory are actually being used you may not have wake-up lag.
[Captivate Android Development] IStern:
Now this is *really* interesting...

I had to restore from a fairly old nandroid backup. After a flurry of app installs, i finally got around to setcpu, and as I was about to flash this kernel again, I opened setcpu for fun and what do you know?? It showed 1200 as the max! Best of all, absolutely NO wakeup lag. Is this just a case of setcpu misreading the max, or did I end up with the best of both worlds?

Edit:

And as a side note...this nandroid backup was definitely before I flashed the OC kernel...does this mean clockwork recovery didn't overwrite the kernel?

Edit 2:

Nevermind, sorry for the false hope! Phone was plugged in to the comp...sigh...
[Captivate Android Development] mostyle:
So in essence the device appears in standby even though it isn't completely in standby.

Appreciate the replies.. Thank you.
[Captivate Android Development] _Opiate_:
I've tried this kernel and it works well. The only thing I didnt like about it was you either had to set the max at 1200 or 800, there was no 1000 incase you wanted to clock down to stock for any reason. Once more clock speeds are added I will use this kernel.
[Captivate Android Development] TheTodFather:
LOL

You had it plugged into computer. I did the same thing.
[Captivate Android Development] Unhelpful:
Initial patch for .1/.2/.4/.6/.8/1/1.2GHz

I have tested each frequency for a few minutes in SetCPU stress test, and 1.2GHz for over six minutes with zero errors. Clocks and voltages are the same as for raspdeep's i9000 1.2GHz kernel, and while they work nicely on my device, they may not on yours, may cause crashes that damage your data, and may even damage your hardware.

The kernel starts with the maximum frequency at 1GHz - if you want to use 1.2GHz you will need to use SetCPU or some other utility. This is so that users who find the 1.2GHz speed does not function on their device can still safely boot the kernel (hopefully) to reach recovery mode.

The binary includes ext2/3/4 and nilfs2 filesystems, and my user_init hack which allows for the safe unmount/remount of /data before system startup.

For those interested, I got 1039 in Quadrant with this and without any lagfix (It's disabled until I get an installable package for internal nilfs2).

Again, this is preliminary, things may break, your results may vary from mine. Good luck. :)