yashsingh1/xdaforums huggingface dataset:
[EVO 4G Q&A, Help & Troubleshooting] Systemfraud:
I've searched far and wide, and can't seem to find anything on the issue I'm having. Or maybe I'm not looking in the right places, but it's been about a straight hour know that I'm looking and can't find the answer I'm looking for.

My problem: When I send a SMS as ONE text it sends perfectly, but once the text reaches 2 texts and I try to send it does not work, it says "sending..." for literally 10 minutes then I get a notification saying the message cannot be sent. I have no idea what I could possibly do to fix this. Someone help, please? :( :confused:
[EVO 4G Q&A, Help & Troubleshooting] criccio:
My suggestion is picking up the phone and calling them.. clearly you have alot to say. :p

(its late... you'll have to excuse me... lol)
[EVO 4G Q&A, Help & Troubleshooting] Systemfraud:
Yeah, I was expecting something like that from this time at night..lol. I did laugh.
[EVO 4G Q&A, Help & Troubleshooting] glock23c:
I think the problem is that the message you're trying to send is over 160 characters, and since SMS messages can't be over 160 characters, and the messages app isn't breaking the text into two texts, it can't send and just times out. Try using chompSMS or Handcent as an alternative, as they have auto-160 breakout features.
[EVO 4G Q&A, Help & Troubleshooting] martyzidek:
A known problem with that Rom. Can't send texts over 160. Why I tries fresh Rom. Can't stand that and don't like the sms in the market. If I can find out to put froyo sms on the Rom id switch back to pick. Bit that's a downfall to me personally.
[EVO 4G Q&A, Help & Troubleshooting] Systemfraud:
I really must agree with you. The rom is awesome, but that's a major issue for me. :( ah well, guess I'll go back to Virus or someone else.
[EVO 4G Q&A, Help & Troubleshooting] martyzidek:
I should spell check before sending. Amyways, on cm6 my sms never had the letter counter so could never tell if over or not. I thought it was the kernel I installed. Then went to the Rom topic and people had the same problem. If I can find out how to pull the sms apk from froyo and push it to cm6 is say I have a perfect Rom.
[EVO 4G Q&A, Help & Troubleshooting] nolageek:
Removed...
[EVO 4G Q&A, Help & Troubleshooting] Saturn2K:
Yeah, this is a real issue. CM6 was originally for GSM networks, which don't have problems with extra large SMS messages. They haven't tweaked the AOSP messenger for CDMA networks yet (by splitting messages).

Here's the issue on the bug tracker. http://code.google.com/p/cyanogenmod/issues/detail?id=1942

Be sure to go there, reply and star the issue.
[EVO 4G Q&A, Help & Troubleshooting] Systemfraud:
That makes perfect sense. That's pretty game-breaking if you ask me. I'm sure I'm not the only one who finds that to be a huge problem. I'll definitely go to the link you provided and take it from there. Thanks everyone for your responses.
[Touch Diamond, MDA Compact IV General] xukca:
Hello!Since 4 days i am owner of HTC Diamond.I really like it but this morning i woke up and got the phone and it told me "Tap screen to launch TouchFLO" i tapped everywhere but the phone was freezed and TouchFLO doesn't start.After soft reset the phone booted normally.Thank you in advance!Sorry for my ENGLISH!
[Droid Incredible General] tmettler5:
I tried searching, and didn't really find anything...today my home button just started caused a screen flash, and nothing else. The search button does not work either. Any suggestions? I have tried power cycling, pulling the battery, pulling the battery and then pushing the power button to drain any power in the circuits...nothing. Any help?
[Droid Incredible General] cooksalot:
Sounds to me like it had a short. One of the reasons I wanted to make sure I had insurance. Unless someone else has another idea.
[Droid Incredible General] tmettler5:
Looks like lockbot was causing it. I uninstalled it, and haven't had a problem since.
[Desire Q&A, Help & Troubleshooting] mazeli:
Hey all,

i have a simple question about the umts network options on the desire.

Is it possible to activate 3G automatically when it is needed by a application and then deactivate it automatically when the application is done with using it?

best regards

mazeli
[Captivate Android Development] SetiroN:
I really appreciate you looking into this and hope you get a handle on it so that we could be able to indifferently use any firmware/kernel with just a few modifications, enable HSUPA and use different 3G bands without losing GPS functionality or auto-rotate.

Cheers.
[Captivate Android Development] madjsp:
This would be helpful for Eugene since he's having some issues with GPS on his rom.

I wonder, can you use this method to look inside the modem.bin for both? See what is different.

Or did I miss it in your wall of text?
[Captivate Android Development] Zilch25:
modem.bin isn't in there, it's not part of the source :)

But there *is* something in the kernel compilation that "checks" your modem.bin to see if it's an ATT one, if it fails that test you still get HSUPA but you lose audio on your voice calls (You just hear hissing). There's GOT to be something in there, I've been completely unsuccessful so far figuring out what though =/
[Captivate Android Development] pongothemagnificent:
I was hoping for someone to this, thanks alot mate.
[Captivate Android Development] Zilch25:
God lord hahaha the CM differences. This does give me a bit of a starting point for pruning through some of the files in search of the HSUPA fail though. Still... that's a lot of crap to go through!
[Captivate Android Development] Unhelpful:
I build my kernels from the T959 source. If compatibility with a different modem.bin differs it is either due to one of the board config options or something in the initramfs - remember that initramfs contains files that set properties and control startup.
[Captivate Android Development] Dani897:
Lol you guy seem close to all the info needed to build the ultimate rom for these phones maybe just a matter of weeks, just in time for froyo to get you guys started on something else.
[Captivate Android Development] TMC_Sherpa:
Samsung just released new versions of the I897, T959 the source for the D700(Epic) and I'm checking the I9000 now. Ignore the previous information until I have a few passes at the new stuff.

I really need to reorganize my posts.

Sherpa

Just so this isn't a totally useless post, here are the differences between the new Captivate old Captivate .config

NEW I897 CONFIG_KEPLER_AUDIO_A1026=y

NEW I897 CONFIG_BLK_DEV_INITRD=y

NEW I897 CONFIG_INITRAMFS_SOURCE=""

NEW I897 CONFIG_ARIES_VER_B2=y

OLD I897 CONFIG_ARIES_VER_B3=y

NEW I897 CONFIG_KEPLER_VER_B2=y

OLD I897 CONFIG_KEPLER_VER_B0=y

NEW I897 CONFIG_KEYPAD_MELFAS_TOUCH=y

OLD I897 CONFIG_KEYPAD_CYPRESS_TOUCH=y

OLD I897 CONFIG_VIDEO_S5KA3DFX=y

NEW I897 CONFIG_AUDIO_HW_Rev02=y

The changes between the old version and the Sep 6th Version

Files ./I897/kernel/build_kernel.sh and ./OldI897/kernel/build_kernel.sh differ

Only in ./I897/kernel/linux-2.6.29/.config

Only in ./I897/kernel/linux-2.6.29/arch/arm/configs/kepler_rev02_defconfig

Only in ./I897/kernel/linux-2.6.29/drivers/input/keyboard/MMH_ST959_R01_V07_bin.c

Only in ./I897/kernel/linux-2.6.29/drivers/input/keyboard/VTW0014_R00_V08_bin.c

Only in ./I897/kernel/linux-2.6.29/drivers/input/keyboard/VTW0014_R00_V10_bin.c

Only in ./I897/kernel/linux-2.6.29/drivers/input/keyboard/VTW0014_R00_V12_bin.c

Only in ./I897/kernel/linux-2.6.29/drivers/input/keyboard/VTW0014_R00_V14_bin.c

Only in ./I897/kernel/linux-2.6.29/drivers/input/keyboard/VTW0014_R00_V15_bin.c

Only in ./I897/kernel/linux-2.6.29/include/linux/utsrelease.h

Only in ./I897/kernel/linux-2.6.29/include/linux/version.h

Only in ./I897/kernel/linux-2.6.29/scripts/basic/docproc

Only in ./I897/kernel/linux-2.6.29/scripts/basic/fixdep

Only in ./I897/kernel/linux-2.6.29/scripts/basic/hash

Only in ./I897/kernel/linux-2.6.29/scripts/conmakehash

Only in ./I897/kernel/linux-2.6.29/scripts/ihex2fw

Only in ./I897/kernel/linux-2.6.29/scripts/kallsyms

Only in ./I897/kernel/linux-2.6.29/scripts/kconfig/conf

Only in ./I897/kernel/linux-2.6.29/scripts/kconfig/lex.zconf.c

Only in ./I897/kernel/linux-2.6.29/scripts/kconfig/zconf.hash.c

Only in ./I897/kernel/linux-2.6.29/scripts/kconfig/zconf.tab.c

Only in ./I897/kernel/linux-2.6.29/scripts/mod/elfconfig.h

Only in ./I897/kernel/linux-2.6.29/scripts/mod/mk_elfconfig

Only in ./I897/kernel/linux-2.6.29/scripts/mod/modpost
[Captivate Android Development] SetiroN:
I'll take a wild guess: one of those AUDIO .config differences must be the culprit for the voice not working with a non-ATT modem.bin.

Wouldn't it be relatively easy to just replace the files and .config references with the vibrant/i9000 ones and end up with a Captivate kernel with working audio along with HSUPA support from an i9000 modem.bin?

The again, would you be so kind to build a few kernels, each with a different configuration for the various audio related differences, for people to test and conclude what causes the incompatibility? :)
[Captivate Android Development] TMC_Sherpa:
I'm just an idea guy trying to put out as much information as I can although I'm pretty sure Zilch would try just about anything I or anyone else compiles :) I have a new theory about screen rotation but I need the new sources at work to check the CONFIG tags in the /drivers/sensor/compass/yamaha.c file. I figure the download should be done in a few days or so.

Sherpa

Or I could scroll up and see them from the list I already made.....
[Captivate Android Development] Zilch25:
Guilty :o Just don't mess with the power regulation or anything else terrifying and we've got a deal!
[Captivate Android Development] SetiroN:
:D

thanks man!
[Captivate Android Development] TMC_Sherpa:
Well at least the rest of us will know how good a job Samsung is doing with their wear leveling. I'm surprised designer posted the Odin one-click software and not you :P
[Captivate Android Development] Zilch25:
I'll have you know I haven't flashed my phone once today... as for how many times I've done so this month... eh I'd rather not say :D
[Captivate Android Development] TMC_Sherpa:
Fun things about the Yamaha compass. This would be much easier if Samsung called the file something other than yamaha.c or put anything in the header other than Samsung 2006-2015 but Yamaha does make compass/accelerometer chips and this is the only file in the /drivers/sensors directory that includes our CONFIG information to build it differently depending on the phone.

This is only a guess at this point although I would love to see someone mess with these values and check the orientation.

Hey hey, what do you know, it does work. Thanks to xcaliburinhand for building a I9000 kernel with our rotation in it.

I9000 garray #define YAMAHA_GSENSOR_TRANSFORMATION \

{ { -1, 0, 0}, \

{ 0, -1, 0}, \

{ 0, 0, -1} }

I897 garray #define YAMAHA_GSENSOR_TRANSFORMATION_KEPLER \

{ { 0, 1, 0}, \

{ -1, 0, 0}, \

{ 0, 0, -1} }

T959 garray #define YAMAHA_GSENSOR_TRANSFORMATION_KEPLER \

{ { -1, 0, 0}, \

{ 0, -1, 0}, \

{ 0, 0, -1} }

I9000 marray #define YAMAHA_MSENSOR_TRANSFORMATION \

{ { -1, 0, 0}, \

{ 0, 1, 0}, \

{ 0 , 0 , -1} }

I897 marray #define YAMAHA_MSENSOR_TRANSFORMATION_KEPLER \

{ { 0, -1, 0}, \

{ -1, 0, 0}, \

{ 0 , 0 , -1} }

T959 marray #define YAMAHA_MSENSOR_TRANSFORMATION_KEPLER \

{ { -1, 0, 0}, \

{ 0, 1, 0}, \

{ 0 , 0 , -1} }

*No idea what these are for or why they need to be there*

I9000 marray_00 #define YAMAHA_MSENSOR_TRANSFORMATION_00 \

{ { 0, -1, 0}, \

{ -1, 0, 0}, \

{ 0 , 0 , -1} }

I897 marray_B5 #define YAMAHA_MSENSOR_TRANSFORMATION_KEPLER_B5 \

{ { 0, 1, 0}, \

{ -1, 0, 0}, \

{ 0 , 0 , 1} }

I9000 garray_emul #define YAMAHA_GSENSOR_TRANSFORMATION_EMUL \

{ { -1, 0, 0}, \

{ 0, 1, 0}, \

{ 0, 0, 1} }

I9000 marray_emul #define YAMAHA_MSENSOR_TRANSFORMATION_EMUL \

{ { 1, 0, 0}, \

{ 0, 1, 0}, \

{ 0 , 0 , 1} }

For some reason our marray and garray are different to the Vibrant and I9000 and I'm guessing that the chip is oriented differently on our boards for some reason.

This all seems kinda ridiculous, there are files for AK8973b which is a 3-axis compass and an accel directory for a SMB380 which is a 3-axis accelerometer. Leftovers or junk for future phones? *shrug*

Someone (not Zilch, we need his phone alive and well...or alive anyway) needs to crack their phone open and take some better pics. We need to look for the triple tuning fork or any other chippies that look interesting.
[Captivate Android Development] TMC_Sherpa:
As long as I'm doing slightly annoying Captivate vs Vibrant stuff

melfas-touchkey.c & cypress-touchkey.c

#define DEVICE_NAME "melfas-touchkey"

#if defined(CONFIG_S5PC110_T959_BOARD)

static int touchkey_keycode[] = {NULL, KEY_BACK, KEY_ENTER, KEY_MENU, KEY_END}; // BEHOLD3

#else

static int touchkey_keycode[5] = {NULL, KEY_BACK, KEY_MENU, KEY_ENTER, KEY_END};

#endif

is why the keys are backwards

If only I could figure out how

static DEVICE_ATTR(brightness, S_IRUGO | S_IWUSR | S_IWOTH | S_IXOTH, NULL, touch_led_control);
static ssize_t touch_led_control(struct device *dev, struct device_attribute *attr, const char *buf, size_t size)
{
unsigned char data;
if(sscanf(buf, "%d\n", &data) == 1) {
printk("touch_led_control: %d \n", data);
i2c_touchkey_write(&data, 1);
touchkey_led_status = data;
}
else
printk("touch_led_control Error\n");

return size;
}

if (device_create_file(touchkey_update_device.this_device, &dev_attr_brightness) < 0)
{
printk("%s device_create_file fail dev_attr_touch_update\n",__FUNCTION__);
pr_err("Failed to create device file(%s)!\n", dev_attr_brightness.attr.name);
}

works someone could get the message notification project going again.
[Captivate Android Development] asrrin29:
This stuff here is linear algebra stuff. Looks like matrix transformations having to do with x, y, z orientation. If these matrices are different between the I-9000 and Captivate kernels, they are most definitely responsible for the orientation problems.
[Captivate Android Development] TMC_Sherpa:
I figured it was something like that. The confusing part is the _EMUL _00 and _B5

And thanks, I can always use more brains.

Sherpa
[Captivate Android Development] asrrin29:
I'm guessing gsensor is the accelerometer and msensor could be motion sensor. emul is emulation, and could be related to array emulation, something people do when the language they program in doesn't have native arrays. 00 and B5 are hex values. That's all I can really say without seeing more of the source. Maybe I'll download it and take a peek. I'm not the best programmer in the world, but two heads are better than one.
[Captivate Android Development] TMC_Sherpa:
The I9000 is the only version that uses the _EMUL and _00 arrays and the Captivate uses _B5.

Everything else KEPLER in the source is Captivate specific and I'm still not sure what FLEMING is

I've attached the yamaha.c file
[Captivate Android Development] asrrin29:
Kepler_Board and Flemming_board might be references to hardware calls to do with circuit board hardware. They could be internal codenames Samsung uses. Johannes Kepler was an astronomer that discovered gravitational rules of planetary motion, and John Ambrose Flemming was an electrical engineer who invented the "right hand" rule used in physics and mathematics. Could be homages to them? Still looking through the rest of the code
[Captivate Android Development] xcaliburinhand:
Quick glance last night showed some differences between the captivate and I9000 source in the drivers/usb section.

I didn't dig too deep into them yet, but they appear to be usb tethering related.

Sherpa found some interesting things in the drivers/mmc area. There is a mutex in the I897 source that does not appear in the I9000 source. Also a few extra bits regarding I959 power control for the SD.
[Captivate Android Development] xcaliburinhand:
External SD card in the captivate comes down to two additional sections in arch/arm/mach-s5pc110/setup-sdhci.c

< #if 1 // Behold3 and Kepler

<	return card_status ? 0 : 1;

< #else

and

< #if 1 // Behold3 and Kepler

<	s3c_gpio_setpull(S5PC11X_GPH3(4), S3C_GPIO_PULL_UP);

< #else
[Captivate Android Development] TMC_Sherpa:
You da man X. I should be done moving in a few days. Then I can get back to working on this stuff again.

Next stop is a list of all the function calls that have differences between the sources.

Sherpa
[Captivate Android Development] Zilch25:
I think we now need diffs between the I897 and a Nokia 5700... GET ON IT!
[Captivate Android Development] TMC_Sherpa:
Huh, I thought the Samsung tablet would be more important than some Nokia. If the rumors are true and it's coming out on all the big carriers seeing the source will be very interesting. Or maddening. Or both.

Sherpa

Cthulhu is my master.
[Captivate Android Development] Zilch25:
Well fine, do the tablets, but I want my nokia >=(
[Captivate Android Development] xcaliburinhand:
Most likely maddening, but here's hoping the P1000 source has a few I897 if statements littered throughout.
[Captivate Android Development] Zilch25:
Is there any source release for the I987? That's the one that's supposed to be for AT&T
[Captivate Android Development] TMC_Sherpa:
*sigh* fine

IN I897 ONLY *

IN 5700 ONLY *

:D

The P1000 source should be a sign for how Sammy is going to handle 2.2 on our phones. The good news is they will have to try pretty hard to make it worse than what we've already got. The bad news is I wouldn't put it past them.

Sherpa
[Captivate Android Development] TMC_Sherpa:
Turns out I'm not the only one with a diff project.

*Shakes fist at the XDA gods for setting up all the subdirectories*

miki4242 is working on SGS vs stock 2.1 android.

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

Now I don't have to. yay?

Sherpa
[Captivate Android Development] Zilch25:
Slacker :p
[Captivate Android Development] TMC_Sherpa:
Yeah, your right, everyone else is doing duplicate work why should I think I'm somehow above it :D

Sherpa

Lazy and willing to work very hard to stay that way.
[XPERIA X1 Themes and Apps] mayyhem84:
Hello!

I know, I know - it was already.. ;) But.. it does not work :(

Can somebody please tell me how the hell it suppose to be done to work properly? I am traveling a lot by car, and I really would appreciate this function.. and any help with it!!

I did found a thread in which it was written that it should work.. but I've failed..

1) I've readed that I should have hands-free config. I've installed it - trial version - 30 days. I did marked the Voice dialling

BTW - is there any way to do it without this program? I would need sth that is.. pernament :)

2) cyberon speed dial. I have..

3) I installed the path for speed dial.

and.. In buttons settings I have a button that sould launch voice speed dial (button5).

But when I press buttons on my bluetooth I can - with one button holded longer - dial last number, with the second holded longer - phon extension (for dialing a number) is launching.. no speed dial at all !! :(

P.S. I can not use MS VOICE!!! I am polish and i just can not communicate with that program! :o The best way would be to lauch cyberon program - I can teach it and it can uderstand everything I say.. :)
[XPERIA X1 Themes and Apps] mayyhem84:
nobody.. ? ;( ;(
[XPERIA X1 Themes and Apps] vp1:
I´ll try to traduce this:

***://***.htcmania.com/showthread.php?t=40652

First install VSD(Voice Speed Dial). Softreset

(***p://***.4shared.com/file/55482593...rified=2948f2e)

Then install VSD patch. softreset

Then install JetWare Hands Free Bluetooth Extension.

(***p://***.4shared.com/file/48603300...HFExt-131.html)

Then in Jetware mark Voice dialing in advanced options.

I hope it works for you...;)

Sorry for my bad english.:(
[XPERIA X1 Themes and Apps] mayyhem84:
hello!

Thank You very much for that reply!! :) Actually.. I was doing this at the first time.. but it did not worked :(

But now, after the hard reset, I did that, but in a way described here:

http://xdaforums.com/showpost.php?p=3237913&postcount=7

and suppoerted by

knowing the key in registry - in OEM there is sth like voice dialing with the path in it value. all of that, after the hard reset did the job!!

So now it is all fine and cool :D

Weard - it was not before the hard reset o_0

thank's again!!
[XPERIA X1 Themes and Apps] Gab1288:
its funny that sony sold it and said it would work when its not..
[Android Q&A, Help & Troubleshooting] cucuong:
Does anyone have unlocking code for Nokia T459

Please post, thank you.
[Captivate Q&A, Help & Troubleshooting] mr.jaguar:
I'm having weirdness, running stock rom, rooted -bloatware and I installed launcher pro, since then, I can't connect with kies/mtp unless twlauncher is running. is this normal?
[Captivate Q&A, Help & Troubleshooting] Dave the Knave:
Yupp. It's normal. Kies/MTP only work with the TWLauncher running.
[Captivate Q&A, Help & Troubleshooting] mr.jaguar:
BAH! I hate proprietary crap like that
[EVO 4G Q&A, Help & Troubleshooting] brad2287:
I recently began to encounter an error when attempting to install apps from my SD card while using programs such as root exporer or android home. I get this error when attempting to install any non market .apk using any file management program. I have no problem installing apps from the market. The error reads-

"Parse error

There is a problem parsing the package"

I was wondering if anyone had any knowledge as to how to solve this so I can install non market apps? So far everything I have tried has failed (wiping and reinstalling ROM and also trying different file management programs.
[EVO 4G Q&A, Help & Troubleshooting] blackroseMD1:
Yeah, I have this error too, and it's really starting to get annoying. Anyone have any ideas?

I'm running CM6 Final with it's stock kernel.
[EVO 4G Q&A, Help & Troubleshooting] deeznutzone:
I have also been experiencing this error. i have an HD2 runnning a chuckydroid rom with FroyoStone with HTC Sense V2
[EVO 4G Q&A, Help & Troubleshooting] Sw1pe:
I'm getting this error too on my HD2 with Hyperdroid & Enegy Leo rom
[EVO 4G Q&A, Help & Troubleshooting] RTC88:
From my experience, the parse error only occurs with bad/incomplete downloads.
[EVO 4G Q&A, Help & Troubleshooting] xHausx:
Have you tried running the fix_permissions script yet? Its included in most ROMs. I would try that along with clearing your cache & dalvik
[EVO 4G Q&A, Help & Troubleshooting] CapinWinky:
has anyone tried making an update.zip to see if it will instal that way?
[EVO 4G Q&A, Help & Troubleshooting] bianava:
I had that error when it is an unlocker apk or an upgrade version of an app.
[EVO 4G Q&A, Help & Troubleshooting] cordell12:
Is the script included in cm7? If so where, thanks
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] jamesbond_28_007:
Apologies, that's the best way to discribe it.

I have searched the forums for this but it's difficult to find someone that has the same scenario as me. Am using lates Darkstone build with NRG light rom. Radio is 20.12 and I have the media folder (with all contents in the root of my SD card).

The problem is, is that I get sound - for a while, then it goes. When this happens and I make a call, there is no sound ringing sound the other end but it does ring apparently. They answer but obviously they dont hear and I am hearing nothing. This also happens with Mattc build.

I've tried radio rom 20.10 but the same issue happens.

Does anyone know of this issue and it's resolution. It is obviously rendering the build useless to me.

Thanks :)
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] wilwilwel:
have you tried to switch the zImage?
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] jamesbond_28_007:
Thanks for responding. I dont really understamd the whole kernal zimage thing. I just trust what ever's in the Adroid folder. But I'll try anything!

How do I decide which zimage to try? And do I just copy and paste it over the one in the folder (obviously reinstalling Android again after)?

Thanks.
[Desire General] tommo123:
there are times i only really want to use the desire for net access etc and would like to cut off the phone ability to save power. airplane mode would do but it cuts off 3g/wifi as well - and bluetooth.

is there a way to disable phone mode and leave the rest on?