yashsingh1/xdaforums huggingface dataset:
[Android Apps and Games] Aleksandra.XMS:
Hi all,

My name is Aleksandra and I am a community manager at eBuddy XMS.

I would like to introduce you and tell you more about new application that we have recently launched: eBuddy XMS.

Moreover, I would be happy to hear your feedback and thoughts about the application. If you have any questions, suggestions or issues that came up during use of the application, leave a comment in this thread, I will be here to answer.

So, what’s eBuddy XMS all about?

- Group messaging for Android and iPhone: send group messaging to up to 40 friends at once!

- Video sending for Android and iPhone: share videos in a matter of seconds.

- WebXMS: access XMS from your computer’s keyboard.

- eBuddy XMS for Blackberry is live as well! Tell your friends who have Blackberry that eBuddy XMS is now live. They can download it by going to eBuddy XMS - Do more than SMS from Blackberry browser.

We are looking forward to hearing your feedback on XMS. I will be here to answer all your questions. You can also drop a support request at www (dot) ebuddyxms (dot) zendesk (dot) com

Want to be the first one to test new features? Join our Beta community by going to eBuddy XMS Facebook page and choosing "Beta community" link on the left tab.

Happy XMSing,

Aleksandra

eBuddy XMS - Do more than SMS
[Android Apps and Games] hossam.salah:
Not pad

But

Bad support

I add my mail to taste that app on my wp7

no one answer tell now
[Android Apps and Games] saigetshu:
thank for sharing, I already used and nice app...
[Android Apps and Games] Aleksandra.XMS:
Hi there,

Can you please give me your Windows Live ID and contact e-mail?

We'll send you a Beta e-mail as soon as possible.

Best regards,

Aleksandra
[Motorola Droid and Milestone Q&A, Help & Troublesh] dand930:
Hey XDA, I was a bit of a lurker on here for a while, and learned a huge amount about everything from getting root to theme-ing and set up my phone how I thought I wanted it - CM 7.0.3, a lot of ZipThemer and MetaMorph changes, etc.

Anyways, I have seen the majority of stuff on this site about this phone and am wondering what ROMs, kernels, setups, and themes and whatnot you guys think are the best out of all the options you have tried. MIUI definitely is not for me, and I love CM but have been afraid to flash any other kind of ROM, especially after a bootloop issue.

I'm just sick of having to set up everything on my phone again when i change ROMs - (changed to 7.1.0 two weeks ago) - just wondering if there was an easier way, or a lesser known ROM/kernel combo that has great battery life and performance.

Features I really enjoy currently:

ChevyNo1 kernels

just about every CM customization option

RZRecovery

Black and White themes for ThemeChooser, ADW, and Zipthemer/Metamorph

Thanks!
[Motorola Droid and Milestone Q&A, Help & Troublesh] taptaptouch:
Liquid GB with chevyno ulv .8ghz kernal on interactive governer and your golden
[Motorola Droid and Milestone Q&A, Help & Troublesh] dand930:
sweet! thanks! - what exactly do you recommend about each? and why interactive instead of smartass or on demand?
[Galaxy S Plus I9001 Android Development] manveru0:
Hei there.

The idea of this thread is to develop a better kernel for the I9001 in the community. I have compiled my own one for using it in the cwm recovery mod. I've only changed the following so far:

Patched pm2.c file in the samsung kernel sources, see here for the patch:

https://github.com/PabloPL/android_...mmit/46e96915a7e0459dc6b3aec04aa47329371fff44

through menuconfig I've changed the default cpu governor from performance to ondemand.

What we should implement first is init.d support.

I've uploaded my boot.img file for further use here:

http://www.mediafire.com/?6p91s5knka0e0py

It also contains the CWM Recovery
[Galaxy S Plus I9001 Android Development] yogi_best:
This is great idea bro. Its great to have you here.

Thanks again!!!
[Galaxy S Plus I9001 Android Development] joostvhoek:
I would love to see a overclock able kernel! Great idea!

Joost
[Galaxy S Plus I9001 Android Development] eidelen:
overclocking module

Hi guys,

coolbho3000 posted source of an overclocking module for HTC Vision. As far I know, it can be used with the SetCPU App together.

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

Since S+ has a similar Qualcomm chip, it should work as well.

I compiled the overclocking module with the S+ Kernel and packed it into the zImage. The device doesn't boot. Maybe it would be better to follow what coolbho3000 says and adapt the settings :-)

ädu

PS: it needs definitively some adaptions.
[Galaxy S Plus I9001 Android Development] abbradar:
Shouldn't we create our own github/bitbucket repositories for kernel and CWM? I'm trying to get my feet wet in generic Android kernel development now, it would be cool to have repository to sync with.
[Galaxy S Plus I9001 Android Development] manveru0:
yep of course. I've already opened an account on github. But right now I ain't got time to read the instructions on how to upload repos because I'm busy with applying some changes to FeaMod Recovery and testing them.

I would be happy if a lot of kernel developers would join us!

Edit: The sources for FeaMod recovery 1.1 are on github:

https://github.com/manveru0/FeaMod-Recovery--based-on-CWM-Recovery-

Samsung kernel sources with patched pm2.c:

https://github.com/manveru0/kernel_I9001_samsung
[Galaxy S Plus I9001 Android Development] abbradar:
Later I'll try to add "run-parts /system/etc/init.d/" to init.rc, but I'm highly confused from examining ramdisk, because I couldn't find any bash-scripts interpreter (possibly embedded into init executable?) and don't have enough time to continue examining init.rc now. I think, we can add busybox to system image and call it from there. Also, please, modify these lines in default.prop in your future builds:

ro.secure=0
ro.debuggable=1

As far as I understood, these allow us to use "adb root".

Also, thanks for your awesome work!
[Galaxy S Plus I9001 Android Development] manveru0:
sounds good. I haven't seen a script interpreter either and I'm not quite sure if there is one included in the init. I think it's better we include busybox. Take a look at this thread by the way:

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

I'll try to do that testwise.

Here's the adress for my uploaded boot.img-ramdisk without the samsung pictures (we can easily add them again when building a new boot.img):

https://github.com/manveru0/bootimage_ramdisk_I9001

I've already included the changes in default.prop

EDIT: some useful links

http://www.kandroid.org/online-pdk/guide/bring_up.html

http://www.androidenea.com/2009/08/init-process-and-initrc.html
[Galaxy S Plus I9001 Android Development] abbradar:
After some init.rd learning I've inserted a service here which should get the job's done, but I have no idea how to test it. Anyway, here is the diff from the normal one:

[abbradar@abbradarbook boot]$ diff -u3 init.rc ../boot_mod/init.rc
--- init.rc	2011-11-05 22:35:33.194680288 +0400
+++ ../boot_mod/init.rc	2011-11-05 22:24:40.000000000 +0400
@@ -566,7 +566,7 @@

# ihryu 2010.07.19
setprop ro.rfkilldisabled 0
- class_start default
+ #class_start default
# +++++++++++++++++++++++++++++++++++++++++++

# for silent reset
@@ -714,6 +714,10 @@
onrestart restart netd
onrestart restart sensor-daemon

+service initd /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
+ oneshot
+
service media /system/bin/mediaserver
user media
group system audio camera graphics inet net_bt net_bt_admin net_raw radio qcom_oncrpc
[abbradar@abbradarbook boot]$

Have also commented "class_start default" which runs twice for some reason. To have this working in theory, you should have busybox installed in /system/xbin with run-parts support. For me, it boots at least ^_^

P.S. It also works if I call command line from adb. Also, adb root works after changing default.prop, good.

P.P.S. You can also remove "charging.rle" from repo, as it is image, too, but why not just keep all the files in repo? git is loyal to binary files as long as you don't try to create a patch. ~_^ Also, you can use .gitignore to exclude some files from git's view at all.
[Galaxy S Plus I9001 Android Development] abbradar:
Found excellent reference on init.rd:

http://www.kandroid.org/online-pdk/guide/bring_up.html

Fixed previous post (removed "disabled"), so it should really work now. Going to test it, but not really sure if my test are correct (I'll try to write something to sdcard, but is it mounted r/w at the moment of script running?)

Test failed, thinking of some other, more accurate tests now.

Tried to create file in /cache, and it worked! Here is boot.img with working init.rd and adb root. Flash it via dd (dd if=boot.img of=/dev/block/mmcblk0p8). You should have busybox installed into /system/xbin for this to work.
[Galaxy S Plus I9001 Android Development] manveru0:
thx for your commit, I'm testing it as well with the adrenaline shot. If init.d support works you should see the changed values.

I do have a working busybox in /system/xbin with run-parts support, so that shouldn't be the issue as my tests didn't work so far.

Okay, gonna delete disable as well.

concerning the images i wasn't so sure about law problems since they include original samsung stuff.

update:

success :D You did it! Init support works. Though I have to retest it since I've also added user root to the init.rc. Honestly I'm not quite sure if that entry is needed
[Galaxy S Plus I9001 Android Development] abbradar:
"user root" is not needed since user is root by default, already tested without it (edited my posts above).
[Galaxy S Plus I9001 Android Development] manveru0:
okay then, i will change the init.rc file and commit it to github. I will name you in the comment to the change. Which name should I use? Is that okay for you?
[Galaxy S Plus I9001 Android Development] abbradar:
Oh, you can use either "abbradar" or "YardE", I don't mind. ^_^ Thank you for credits and again for your work. Gonna experiment a bit with CWM now since init.d is working.
[Galaxy S Plus I9001 Android Development] manveru0:
I have to thank you for your work as well, mate :) It's cool working as a team since we are better, faster and should see more bugs than working alone ;)

Edit:

Hmm, we should include busybox in the boot ramdisk, since not every user has busybox installed.

P.S: funny thing is, I've installed adrenaline shotv13 but only part of it works. For example the sdcard tweak works, the sysctl tweaks don't.

P.P.S: i've installed bash on my device, it's much more easier with it to navigate in the adb shell
[Galaxy S Plus I9001 Android Development] abbradar:
What is the max size limit in our device for ramdisk? Also, should we really do so? It will be hard to update in comparison and maybe will be stripped due to size limit, and users basically'll have two versions of busybox - our embedded into boot.img and their own - in /system. (I'm looking on CM and other init.d implementations as an example) But on the other hand, it is really nearly critical level app (although sh is not in boot.img, for example)

They also trying to write some values into non-existent /sys nodes, looks like they are meant for other kernel scheduler, like BFQ (should we also try it?)

---------- Post added at 01:25 AM ---------- Previous post was at 01:25 AM ----------

Good advice, thank you ^_^.
[Galaxy S Plus I9001 Android Development] manveru0:
the maximum size of both recovery and boot.img is 7864320 Bytes. Riversource once found that out. It's also in the BoardConfig.mk So we would have enough space for including busybox. But you're right, it would only lead to 2 busyboxes on the device which is not the best idea.

CM uses the BFQ scheduler as far as I know so yeah, we should give it a try
[Galaxy S Plus I9001 Android Development] abbradar:
AFAIK, BFS patch nearly fully removes original kernel schedulers, so some work of comparing with original Linux kernel will be needed to do. Although, it may not be true for Android kernel sources or my experience may be wrong, so we should just try it as is before continuing.
[Galaxy S Plus I9001 Android Development] manveru0:
yep, I've looked at the changes the patches make and they remove alot of the CFQ related functions. Fortunately the makefile is patched as well so no work here.

I've have downloaded the patches for kernel 2.6.35 here:

http://algo.ing.unimo.it/people/paolo/disk_sched/sources.php

I applied them to my sources, compiled em and flashed my FeaMod pack with the new kernel and your changes to the boot ramdisk.

So far everything is working on my device :-) I'm gonna upload the patches to github.

Edit: Had to change the .config as well since bfq is not the default I/O scheduler. It is now, I've also activated the hierarchical scheduler support.
[Galaxy S Plus I9001 Android Development] abbradar:
Concerning ramdisk git repo: maybe we should move all the code into some folder, for example, "ramdisk", and move README out from there to avoid it being placed into final image? Also, we should point which files are missing from ramdisk in README.
[Galaxy S Plus I9001 Android Development] manveru0:
Good idea, I'll do that.
[Galaxy S Plus I9001 Android Development] abbradar:
While testing my kernel with modified pm2.c got that WLAN bug you've got before. Strange, I've not modified anything except of pm2.c. What have you made to fix that?
[Galaxy S Plus I9001 Android Development] manveru0:
Hmm I think the bug is due to the dhd.ko module which has to be recompiled against the new kernel. I've found out that whenever you try to change the kernels name in general setup you'll get that bug. So in order to avoid it you would have to recompile it and copy the new module onto the device as well
[Galaxy S Plus I9001 Android Development] abbradar:
Hmmm, I haven't really modified kernel name, but I'll try to recompile it. But there is the problem - do we have sources for it at all? Looks like it's proprietary broadcom module linked against libc's LGPL kernel headers, and thus closed source.
[Galaxy S Plus I9001 Android Development] manveru0:
Ok, as far as I've looked at it the wlan bug only appeared after changing the name. Honestly I got no idea, since I never looked at the headers (I am fairly new into compiling kernels so I guess you are much better in it). Well it seems reasonable that those modules are closed source. But why does it work then? I

By the way: I'm using the toolchain which samsung names in their readme
[Galaxy S Plus I9001 Android Development] abbradar:
Oh, that may be the issue. I've used my own compiled toolchain (GCC 4.6.2/x86_64/Arch Linux). I'll try to use official one and see what happens.
[Galaxy S Plus I9001 Android Development] abbradar:
The problem was in kernel "setlocalversion" script autoappending "+" sign to kernel because of it being in git repo in HEAD branch. Got working Wi-Fi with patched script even with my self-compiled toolchain, pushed changes to git repo.
[Galaxy S Plus I9001 Android Development] manveru0:
thx, i've merged my repository and am testing the changes right now. What about including BFS as well?

Edit: tried to compiled the kernel again with your changes to setlocalversion, but the wlan error is still there, what I am doing wrong? Im using the toolchain mentioned in the Samsung readme
[Galaxy S Plus I9001 Android Development] abbradar:
Hmmm, strange. For me, after changing name to samsungs's (2.6.35.7-perf) it worked. I'm reflashing phone with XXKPJ right now, will check WLAN work after completance.

---------- Post added at 09:19 AM ---------- Previous post was at 09:08 AM ----------

It will be problematic to include both BFS and BFQ into kernel, because of BFS wiping nearly all about schedulers except itself. Also, we can try compare performance of them and choice the best one.
[Galaxy S Plus I9001 Android Development] eidelen:
module problems

you can get rid of the module loading problem by enabling forced module loading in the Kernel configs.

"Enable loadable module support" > "Forced module loading"
[Galaxy S Plus I9001 Android Development] abbradar:
Can you build it with that and with different local version and check WLAN? I will try that once I get home.
[Galaxy S Plus I9001 Android Development] eidelen:
pack + install script

I made a little script, which packs the boot image and writes it to the device. Adapt the ram-disk name and run it from the kernel dir.

www.eidelen.ch/android/install_kernel_splus.sh

---------- Post added at 10:12 AM ---------- Previous post was at 09:57 AM ----------

It's a known build setting for linux kernels and I tried it my self with the Xperia Arc. Once my S+ is alive again, I'll check it.

Added:

Ok, I was wrong. Forcing works for different kernel versions "2.6.35.7-abcd" & "2.5.01.01-abcd" but not for different local versions "2.6.35.7-abcd" & "2.6.35.7-dcba". On the Arc we had just different versions; it wouldn't come to my mind that the version string isn't checked as a whole. From the insmod manual: "This only overrides the kernel version check, it has no effect on symbol name checks."

I'm going to find out how that works.
[Galaxy S Plus I9001 Android Development] abbradar:
Just checked it out, too, it really does not work ;_;.

From development progress - I've rebuilded kernel with small modifications in config. (removed some unnecesary strings and changed something else, not much really) Also, removed "recovery" from ramdisk - really could not understand why should it be in boot.img, checked init.rc, and saw only one reference to recovery, which points out to non-existent script in /system. So I removed it and saw no regressions in things like rebooting, factory reset from system or something else - now we don't have to update binary on each recovery rebuild. Also, found interesting bug - if I'm flashing our boot and recovery together with stock firmware via one-package Odin, the system doesn't do /data and /cache wipe and hangs up on reboot instead - so I have to pull out battery and wipe these partitions manually via CWM. I tried to insert stock "recovery" binary into boot.img, but that didn't help.
[Galaxy S Plus I9001 Android Development] eidelen:
local version - solution

Ok, here the brute force solution for those, which really want to change the "local version" :))

Modify the load_module function in /kernel/module.c

Replace

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

else if (!same_magic(modmagic, vermagic, versindex))

{

printk(KERN_ERR "%s: version magic '%s' should be '%s'\n", mod->name, modmagic, vermagic);

err = -ENOEXEC;

goto free_hdr;

}

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

by

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

else if (!same_magic(modmagic, vermagic, versindex))

{

printk(KERN_ERR "%s: version magic '%s' should be '%s'\n", mod->name, modmagic, vermagic);

printk( "But I dont care" );

}

-----------------------------------------------------
[Galaxy S Plus I9001 Android Development] abbradar:
^_^ Funny patch. Thank you, I'll apply it and test. (though I cannot say that I have any desire to change localversion, really)
[Galaxy S Plus I9001 Android Development] eidelen:
I wouldn't call it patch ;-)

Well, I'll like to change "local version" and that's usually not a problem, since modules can be built by your self, like for HTC devices.
[Galaxy S Plus I9001 Android Development] abbradar:
Checked that "patch" (probably more like "workaround" ^_^) and it works like a charm. Pushed changes to repo.
[Galaxy S Plus I9001 Android Development] abbradar:
Was busy now checking Skype bug with front camera - I can confirm it, camera works properly with stock kernel. (but with modified ramdisk) I'll grok code a bit, but I have no idea what can cause this. (the bug is obviously in kernel or in some kernel module which fails to load properly)
[Galaxy S Plus I9001 Android Development] abbradar:
I tried to compile vanilla kernel sources with Samsung's configs and such, and bug is still present. I have no idea now how to fix this. Here is workaround build of boot.img with stock kernel and modified ramdisk - Skype will work properly with this, but you'll have to stick with stock kernel (although things like init.d should work)
[Galaxy S Plus I9001 Android Development] manveru0:
uh yeah guys, you're quite into developing things for kernel now :) As soon as I got time I'm gonna try to follow all those changes
[Galaxy S Plus I9001 Android Development] abbradar:
Another bug/feature we have there - range of selectable frequencies, for example, in CPU Master, is smaller approximately 2 times than on stock (kernel/ramdisk?) one.
[Galaxy S Plus I9001 Android Development] manveru0:
yep, that was the one bug which gave me a brainfuck for some days and held on the development of my Mod. I can't find any explanation for it :(

About the recovery binary in the boot.img. I totally agree with you then, I had it only in the boot img to be as close to the original image as possible in order to avoid any instabilitys. I'm gonna remove it from now on in the future versions of FeaMod
[Galaxy S Plus I9001 Android Development] manveru0:
you may attach the device to your pc and watch the debug informations in eclipse with logcat. For example you see the error warning when a module fails to load. but I'm sure you already did that :)

Edit: I have antutu cpu master free installed and it allows me to choose the following frequencys:

122.88 MHz

245.76 MHz

368.64 MHz

768 MHz

1400 MHz
[Galaxy S Plus I9001 Android Development] abbradar:
In stock we have, for example, 1000 Mhz. Not sure is this is a kernel change or something else.
[Galaxy S Plus I9001 Android Development] sakindia123:
hey manver0,can u plz upload the toolchain u r using and ur makefile?i cant get it to work!

i wantto help u!
[Galaxy S Plus I9001 Android Development] abbradar:
You can use official Samsung manuals to compile it, just symlink FeaCore_config to .config instead of "make aries_rev00_defconfig". Toolchain can be found there:

http://www.codesourcery.com/sgpp/li...09-51-arm-none-eabi-i686-pc-linux-gnu.tar.bz2

But nothing stops you from using newer toolchain, I compile it soccessfully on GCC 4.6.2, for example:

https://sourcery.mentor.com/sgpp/li...03-42-arm-none-eabi-i686-pc-linux-gnu.tar.bz2

Don't forget to specify path to toolchain in Makefile. (CROSS_COMPILE variable)
[Galaxy S Plus I9001 Android Development] vitaliy_y:
Hi, is it possible to implement those changes here in the kernel: Battery Life eXtender (BLX) version 1 and Power saving state DEEP IDLE version 2

as was done for the core from Nexus S http://xdaforums.com/showthread.php?t=1336529

Sorry for my english.
[Galaxy S Plus I9001 Android Development] sakindia123:
i have some queries:

i want to set some new cpu governors and do some undervolting......which files do i check out ?i suspect cpu.c and voltage.c..........

edit------------------------------------------------------------------------------------------------------

ok so let me start:

ARCH ?= arm
CROSS_COMPILE ?=/home/sarthak/Downloads/arm-2011.03/bin/arm-eabi-

this is the cross_compile variable in the makefile in the kernel source...

now ,when i type

make

i get this error

sarthak@sarthak-ThinkPad-R51:~/Downloads/i9003/Kernel$ sudo make
[sudo] password for sarthak:
make: /home/sarthak/Downloads/arm-2011.03/bin/arm-eabi-gcc: Command not found
CHK include/linux/version.h
CHK include/generated/utsrelease.h
make[1]: `include/generated/mach-types.h' is up to date.
CC kernel/bounds.s
/bin/sh: /home/sarthak/Downloads/arm-2011.03/bin/arm-eabi-gcc: not found
make[1]: *** [kernel/bounds.s] Error 127
make: *** [prepare0] Error 2

plz help! here is the screenshot of the bin folder of the toolchain i m using:

http://attachments.xda-developers.com/attachment.php?attachmentid=778120&d=1320913934

Thanks!
[Galaxy S Plus I9001 Android Development] abbradar:
Dude, just fix prefix of compilers, you have "arm-eabi-none" in bin dir but "arm-eabi" in Makefile ~_^
[Galaxy S Plus I9001 Android Development] manveru0:
:D I'm gonna apply the bfs patch to test it out since BFS is for the CPU while BFQ is for I/O
[Galaxy S Plus I9001 Android Development] abbradar:
Hey, you are basically thinking the same thoughts - I wanted to try it this evening. ^_^