yashsingh1/xdaforums huggingface dataset:
[HTC One X] Wilks3y:
Can any1 link me to some good Senheiser earphones that arent IN EAR.

I have small ears and they never stay in, I want a good pair of earphones that are the ones that sort of cup your ear like this: Click Here
[HTC One X] BenPope:
"I cant agree with you more" means maximum agreement. Unable to be more in agreement.
[HTC One X] BlueSingA:
Thanks for translating from english to english Pope. He must be thinking "what kind of inception is this?!" :P
[HTC One X] SgtIcetea:
Just try other headplugs, the originals are not really good they're aweful to listen to music so get ypurself other m8 :)
[HTC One X] forster:
Type in the google sennheiser cx300 best in ear headphones out there, for bout 30$, unfortunately they haven't got a mic. if you need headphones with mic, your choice widens up. i would recommend one of those:

Nocs NS400 or NS200. a-Jays one +, RHA MA450i, Sennheiser cx275s all arround 60$.

I myself went for sony mw600 together with sennheiser cx 300, will buy Nocs or RHA with next opportunity.
[Samsung Epic 4G Touch] Smurphjw:
Is there a proper order of operations when flashing a rom, kernel and modem at the same time? if it matters im currently running FL16 rom and modem. im going back to FF18. I know to use a safe recovery. Odin on PC is not an option. Thanks in advance.
[Samsung Epic 4G Touch] garwynn:
Kernel/Recovery, Modem, ROM in my opinion. You can do the first one in Mobile Odin Free to avoid any issues - one of Agat's repacks (any up to FI27 will do) - then just get a ROM & Modem.

If you're willing to pay for Mobile Odin Pro it can do a one click minus the modem. That can be done easily afterwards by doing Agat's repack in Mobile Odin and then flashing the modem.

If you're going back to ICS I recommend going back to FI27 though.
[Sony Ericsson Xperia Neo, Pro] DarkStryder:
hi i have a xperia neo v and i sent it off for repair about 5 months ago because the internet data never loaded it was always sending data never receiving. they replaced a chip and then it worked fine. but now when i turn on data it doesn't come on! if u turn on plane mode on then of. it works, also if i switch to 2g network it comes on fine!! i have recently flashed cm10 on my phone and after that i got the problem! but dont know if its the rom of the phone? please help! thanks!
[Sony Ericsson Xperia Neo, Pro] Ghostfreak NB:
Did you face with any previous Rom?
[Sony Ericsson Xperia Neo, Pro] DarkStryder:
No it didnt. But sometimes when u turn of data the 3g icon where the signal is used to stay there a while as if it was stuck!
[Nexus 7 General] maglog1:
Hello I tried installing whatsapp but to no vail. Can someone guide the process as i tried all the bluestacks process..

Also i installed app guard and did try those stuff but when i launch whatsapp and go to call verification which is the last step.

It gives me an error " It looks like your client has been modifed. Kindly download the latest version from whatsapp.com/andriod."

So any tips would be welcome..
[Nexus 7 General] davisac:
You followed the steps listed here: http://xdaforums.com/showthread.php?t=2061176
[Nexus 7 General] maglog1:
Hey davisac, i tried those steps. It didn't work.
[Nexus 7 General] davisac:
I tried to install it myself but I only have a Mac right now and couldn't seem to get an .apk to install on Bluestacks.
[Nexus 7 General] kao_u20i:
I successfully got whatsapp working on my nexus by doing the following;

1 - Backed up whatsapp on my phone using titanium backup

2 - Copied the backup file from it's location on my phone (sdcard/TitaniumBackup) to it's corresponding location on the nexus

3 - Opened Titanium on the nexus and restored app DATA only using the restore feature.

4 - Ran Whatsapp with wifi on, it says it needs to verify your number. Input number, await txt on phone with a security code and input this into whatsapp on the tablet.

5 - Hey presto you now have free messaging over wifi :)

Requirements on both devices;

Whatsapp, Titanium Backup, File Explorer such as ES File Explorer.

Optional: I used airdroid to transfer the backup file between devices, this can be done via cables and laptop if you prefer

You can also use this method to restore data for saved games such as angry birds....
[Nexus 7 General] ucubz:
What whatsapp version do you use? I'm getting notice that mw whatsapp ver is older ver and need to be updated.

Exit: got it working now. Just send app and data manually. At first I sent it with tb option "send backup to" and not working.
[Nexus 7 General] kao_u20i:
Yeah I've always done a manual transfer of the backup file to the titanium folder and never had an issue, I didn't even notice there was a 'send backup to' option :D

When restoring I use the 'data only' option and never have any cross-version compatibility issues
[Nexus 7 General] trandithao:
Hey davisac, i tried those steps. It didn't work.

you can shoot your scence and up photo , we will help u
[Sprint Samsung Galaxy Note II] garwynn:
Well, now that it's up and running it's time to properly set this thread up.

The idea of this thread is to provide a kernel repo that most can use to build their own.

I'll be building and posting the builds from this without modification.

May 29, 2014 Update: I have added the NE2 Kitkat kernel and built but it will remain untested.

I'll try to see if someone can test but it doesn't look like much has changed from MK4.

Project Repositories:

NE2 (4.4) (Initial Setup Only)

https://github.com/garwynn/L900_NE2_Kernel

MK4 (4.3) (WIP):

https://github.com/sleshepic/l900_MK4_Kernel (Thanks to sleshepic for his work on this!)

MC2:

https://github.com/garwynn/L900_MC2_Kernel

Older Versions (Development has stopped)

MA7 | LJC

Project Status:

NE2:

I've used the same as MK4 to make a test kernel. Untested though without a N2.

MK4:

Still trying to get a full boot.img together, stay tuned.

MC2 Status:

Kernel patched to current Linux 3.0.x (.71 at time of update)

Stock governors enabled, 6 additional ones added.

Project Downloads (Built Kernels):

My kernels are currently housed by rwilco12's Android Stock Repo. (All versions)

To compile on your own you need:

1) Linux Box - I'm using Ubuntu 14.04 and all prerequisites for building AOSP.

2) Android SDK with toolchains - I used arm-eabi-4.4.3 all the way through NE2.

3) Cloned repo from above.

Just modify the toolchain location in ./build_n2.sh and execute ./build_n2.sh.

Rest should go on its own.

On some cases I had to also change the toolchain location in main makefile.

Releasing/Posting your Kernels:

Folks are encouraged to try building the kernel and posting it if they want to.

Any posts should refer to using the kernel as their base.

If you modify the code further outside of this you should include a link to your repo for others to see those changes.

Anyone interested in chipping into this is more than welcome!

Thank you in advance for your time!
[Sprint Samsung Galaxy Note II] cbucz24:
I've been playing, digging, etc for about a year now. Ive been attempting my first rom build and I think im really close. Its a 4.2 rom, so its been a challenge.

But I would love to participate in this too if its open to everyone.
[Sprint Samsung Galaxy Note II] garwynn:
That's the goal! It slowed down on the E4GT but it's hopefully going to heat up again soon.

The more people that get involved, the better the kernel should end up - and the more that fellow XDAers learn and share knowledge!
[Sprint Samsung Galaxy Note II] btbamzao:
Talk to sleshepic. He built a kernel for his rom.
[Sprint Samsung Galaxy Note II] thewadegeek:
Self-plug below. It should get you started on kernels.

http://xdaforums.com/showthread.php?t=1748297
[Sprint Samsung Galaxy Note II] garwynn:
Agat63 showed him and also is willing to show me but catching him will be tough for the next 3 weeks.

So that's what I'll go with if we can't get something cobbled together before then.
[Sprint Samsung Galaxy Note II] sleshepic:
Agat was def helpful as always. The way I ended up doing it was slightly dif than the way he does it on the S3, really similar though. im really busy for a couple days but when I get to my comp with some time ill type up what I do.

My git wouldn't be a good source to clone from just cus my first commit had a few changes already, but it def would be helpful to get a working repo together with the Cypress touch drivers already placed in source - did they forget them or what lol. Could try getting that together too.
[Sprint Samsung Galaxy Note II] garwynn:
Thanks for the assist!

I'll try to commit a fresh LJC repo over the weekend then and we can go from there.

Hope I don't mess that up. I'll ask if I have any ??s.
[Sprint Samsung Galaxy Note II] garwynn:
Well, I made a repo here:

https://github.com/garwynn/L900_LJC_Kernel

...and followed the kernel readme instructions. Looks like it's compiling.

*Edit* ...and failed. arm-eabi-nm missing in toolchain I'm using.

(Wait, it's right there!)

/root/Kernel/L900_LJC_Kernel/scripts/mksysmap: line 44: ~/Kernel/toolchain/prebuilt/arm-eabi-4.4.3/bin/arm-eabi-nm: No such file or directory
make: *** [vmlinux] Error 1
[Sprint Samsung Galaxy Note II] VeNuMuS:
How about a Modem Repo? Like on the Epic Touch
[Sprint Samsung Galaxy Note II] garwynn:
Rwilco12 - when he has time - is going to set up a Kernel/ROM/Modem Repo... at least time I talked to him.
[Sprint Samsung Galaxy Note II] VeNuMuS:
Cool.
[Sprint Samsung Galaxy Note II] sleshepic:
Here is what my build looks like, in general. I have my toolchain referenced in the first export (which could also be easily put in the makefile so its not needed each time)

$ export CROSS_COMPILE=/media/Android/Kernel/toolchain/prebuilt/arm-eabi-4.4.3/bin/arm-eabi-

$ make t0spr_04_defconfig

$ make menuconfig (this is not necessary, and possibly not recommended unless you know what your changing etc, or could be manually edited in the file)

$ make modules

$ make -j5 (the -j5 is optional, I have a quad core processor so this just speeds things up, if you believe your comp is capable of faster than standard builds put the number of cores plus 1 for the number after "-j" )

Then that will build the zImage into the /arch/arm/boot directory.

Which we then bundle with the ramdisk to create the boot.img.

On the Epic Touch all we needed was the zImage for the kernel since the initramfs were bundled differently, but it's dif on our Note 2's. you'll need the ramdisk and zimage to make your boot.img. I pulled the ramdisk from the stock kernel.

I use

$ ./unpack-bootimg.pl boot.img

to pull the "ramdisk-contents" from the stock kernel, I renamed that folder "initramfs" and threw it in a folder along with my mkbootimg binary, and my zImage I just compiled. you can put this anywhere, I just put it in my working kernel folder so it's easy to navigate to

I put the newly created modules from zImage build in my initramfs/libs/modules with

$ find -name '*.ko' -exec cp -av {} [path to desired folder] \;

I navigate to the initramfs folder and

$ find .|cpio -o -H newc > ../ramdisk

$ cd ..

$ gzip ramdisk

$ ./mkbootimg --kernel ./zImage --ramdisk ./ramdisk.gz --board smdk4x12 --base 0x10000000 --pagesize 2048 --ramdiskaddr 0x11000000 -o boot.img

That last part is what bundles the zimage and ramdisk into the boot,img. sorry I had to rush it, hope i didn't miss much, can fill in the blanks as needed, just I'd get up whatever I could when I found a moment, open to help in any way I can.

Edit: Also, checked out the repo put up, Nice work so quick! this is the folder I mentioned that needs to be added or else the capacative touch keys won't work, unbelievable that that was missed in the source drop. I mean, isn't it supposed to be a buildable working version for it to meet open source standards? guess not. anyway, this "cypress" folder needs to be added to the source prior to build for the two touch keys to work. first time I finally got mine booting and all I was so psyched only to find out my touch keys didnt work, so frustrating. Just have to pull it from other source, or you can grab it from mine

https://github.com/sleshepic/Note_2_l900/tree/master/drivers/input/keyboard/cypress

Big thanks to agat63 and Andreilux for help along the way
[Sprint Samsung Galaxy Note II] slick_rick:
Nice stuff here, will be following this thread. Here is another repo with fresh LJC kernel source with cypress drivers included https://github.com/slickrick/L900_Kernel
[Sprint Samsung Galaxy Note II] garwynn:
Mind if include this in OP revision after Phase 1 is finished?

Also thanks for the quick responses... will try to get to it this weekend but will probably be Monday. Sucks but that's the way it will be a few more weeks.
[Sprint Samsung Galaxy Note II] rwilco12:
Working on it as we speak! I was able to finish the week with only 10 hours of overtime and had some free time to work on some projects. :)

Got one or two little things to sort out in the PHP but here's a sneak peek of what I've got coming! It's a complete rework of my original Repo for the E4GT with more devices and more goodies!

If there are any PHP gurus (or web design in general) and you're willing to help hit me up and maybe I can get over this last hurdle and make the New Repo public!

View attachment 1639626
[Sprint Samsung Galaxy Note II] thewadegeek:
Nope feel free.
[Sprint Samsung Galaxy Note II] garwynn:
Well.. work on this may be pushed back a day or two, new source for the E4GT. Gotta look at it first.
[Sprint Samsung Galaxy Note II] agat63:
Hi everyone.

I'm here by invitation :p and will try to participate as much as I can.

Hopefully with combined knowledge and power we can make this

project move faster.
[Sprint Samsung Galaxy Note II] garwynn:
Okay... here's where I still stand.

Added Cypress and pushed a commit to Github.

Make still is good up until VMLinux and fails.

Didn't know I can just skip to here so here's the command and output:

root@build:~/Kernel/L900_LJC_Kernel# make vmlinux
CHK include/linux/version.h
CHK include/generated/utsrelease.h
make[1]: `include/generated/mach-types.h' is up to date.
CALL scripts/checksyscalls.sh
CHK include/generated/compile.h
LD vmlinux
SYSMAP System.map
/root/Kernel/L900_LJC_Kernel/scripts/mksysmap: line 44: ~/Kernel/toolchain/prebuilt/arm-eabi-4.4.3/bin/arm-eabi-nm: No such file or directory
make: *** [vmlinux] Error 1

Where should the vmlinux object be? It's trying to create system.map so I suspect that vmlinux is not being created properly.

I dumped a debug output from this make but it's 115MB.
[Sprint Samsung Galaxy Note II] agat63:
It shows arm-eabi-nm error.

Did you check your toolchain/bin folder?

is there a arm-eabi-nm in there?
[Sprint Samsung Galaxy Note II] garwynn:
It's there... but toolchain wasn't from Google, possible something missing.

I'm pulling the prebuilt repo now and will point to that one instead. Hope that fixes it.

*Update* Pulled Google toolchain again and no change.

I still think it's having a problem making the VMlinux (which if I read correctly is one of the last steps)

Not sure what would differences would exist between the E4GT and GN2 to cause this...

..going to re-extract kernel source and make sure nothing is missing.

4:00 pm (CST) Update:

I'll be danged. Something must have been missing as this time it worked.

Did make clean, make mrproper, make distclean and pushing to Github. Should be a working repo.

I'll compile one more time after that to verify.
[Sprint Samsung Galaxy Note II] agat63:
I'll pull repo as soon as I get home from work and give it a try.

Why couldn't this source drop yesterday? I did check sammies site about 7 pm last night.

:mad:

Edit: Since note uses boot.img as does the GS3 I'll try my GS3 setup/tools/script to run the build.

If it goes thru I'll PM results to you. I don't have Note so I can't test the kernel itself. If boot.img build successfully I'll pm it to you as well for testing.
[Sprint Samsung Galaxy Note II] garwynn:
This is old source, so no hurry. Just trying to understand and set up repos for both E4GT and GN2 that people can easily use to make kernels.
[Sprint Samsung Galaxy Note II] cbucz24:
When I get home tonight I'll switch my manifest to this so I can test an build it too.

I had previously used perseus kernel an I couldn't get it to boot even though it compiled fully?

Please be patient with me guys as development is new for me.

Few questions about kernels. Is there anything in a kernel about a dev ttyUSB0?

Lastly about the files in general, when a repo is "100% synced" and should be fine. Is there any real way to know if there are files missing? Other than a single directory side by side comparison?
[Sprint Samsung Galaxy Note II] garwynn:
Compiling - as sleshepic mentioned - is only part of the process. You still have to combine the ramdisk/initramfs. Now that we have a stable repo next on my list would be a script to do most of that for you. I've got the E4GT one that I'm thinking about using but waiting to see what Agat is using for GS3 and see if that's closer.

As for comparing local with remote repo:

http://stackoverflow.com/questions/5162800/git-diff-between-cloned-and-original-remote-repository

...Or just delete the folder and do a git clone again.

Again, sorry if it feels like I'm neglecting this thread, want to get FL24 for E4GT moving now that it's an official build.
[Sprint Samsung Galaxy Note II] agat63:
Once I'm done with merging with FI27 tweaks into FL24 source I'll run my GS3 srcipt on this and see if it works.

If build goes thru and boot.img boots I'll share my script with Garwynn to expedite the process.
[Sprint Samsung Galaxy Note II] garwynn:
Just an update:

Copied cypress and compiled LJC. Completed the ramdisk steps, looked good.

Flashed, booted, capacitive keys not working. Dang! :(

Will have to look again. Does anything need to be done except adding the folder to /drivers/input/keyboard?

*Edit*

Think I found it... https://github.com/sleshepic/Note_2_l900/blob/master/drivers/input/keyboard/Kconfig

(Had to refer to it at the bottom to include. Makes sense to me)

Recompiling but probably won't be able to test until tomorrow.

*Edit #2*

Added, recompiled, reflashed - still no capacitive keys.

Think I'm still missing something to pull it in.

Repo updated to reflect adding line from above.

*Edit #3*

Found another missing change: https://github.com/sleshepic/Note_2_l900/blob/master/drivers/input/keyboard/Makefile

Will add tomorrow and see if it fixes.
[Sprint Samsung Galaxy Note II] sleshepic:
Re: Community Kernel Project

Sorry, just saw this now. Yeah that last edit you put in is crucial in the makefile, and adding that last line in kconfig, after adding those, and enabling cypress in your config (manually or in menuconfig etc) you should be good to go. I had the same thing, was flashing dif versions for a while before I figured it out.
[Sprint Samsung Galaxy Note II] garwynn:
After adding one more line to the defconfig the touch keys are back in business.

Overnight Agat also provided an alt (and scripted!) method to combine the ramdisk.

Booting to regular system okay but booting to recovery caused hang on GN2 splash screen and battery pull.

We're getting there but not 100% yet. (If you read earlier version Phase 1 is not complete.)

*Update #2*

Flashed back LK8 kernel and recovery still froze. Odd.

Flashing fresh copy of TWRP fixed it.

So was it my kernel test? Let's try it again....

*Update #3*

Reflashed kernel, went to TWRP without issues. Guess there was something else at play there.

But wi-fi not working now. Investigating.
[Sprint Samsung Galaxy Note II] garwynn:
Wi-fi Logcat:

I/WifiManager( 2903): setWifiEnabled : true
E/WifiHW ( 2488): ##################### set firmware type 0 ###################
##
D/WifiStateMachine( 2488): setWifiEnabled : WifiNative.setFwType(0)
D/STATUSBAR-WifiQuickSettingButton( 2903): Wifi onClick(true)
D/WifiService( 2488): setWifiEnabled: true pid=2903, uid=1000
D/STATUSBAR-QuickSettingButton( 2903): Button DIM
I/WifiHW ( 2488): module is semco SH
E/WifiHW ( 2488): ==========[WIFI] Station firmware load ===========
I/WifiHW ( 2488): Start Check B2 #######
I/WifiHW ( 2488): wifi_trigger_poke : Found 4334B3
I/WifiHW ( 2488): ==========[WIFI] SEMCO SH MODULE ===========
E/WifiStateMachine( 2488): Failed to load driver!
D/WfdService( 2488): intent recieved android.net.wifi.WIFI_STATE_CHANGED
D/STATUSBAR-NetworkController( 2903): onReceive() - RSSI_CHANGED_ACTION, WIFI_ST
ATE, NETWORK_STATE
D/STATUSBAR-WifiQuickSettingButton( 2903): Wifi onReceive(2)
D/STATUSBAR-QuickSettingButton( 2903): Button DIM
E/WifiStateMachine( 2488): DriverFailedState
D/WfdService( 2488): intent recieved android.net.wifi.WIFI_STATE_CHANGED
D/STATUSBAR-NetworkController( 2903): onReceive() - RSSI_CHANGED_ACTION, WIFI_ST
ATE, NETWORK_STATE
D/STATUSBAR-WifiQuickSettingButton( 2903): Wifi onReceive(4)
D/STATUSBAR-QuickSettingButton( 2903): Button OFF
[Sprint Samsung Galaxy Note II] sleshepic:
Re: Community Kernel Project

Was dhd.ko included with your modules? That would need to get transferred from build location to your mkboot folder (wherever your making your boot.img from ramdisk etc)
[Sprint Samsung Galaxy Note II] agat63:
If you didn't load dhd.ko with boot.img or flashed to /system/lib/modules folder your wifi won't work.

I had same problem with GS3 kernel.

You should load modules that were build with kernel otherwise certain things won't work.

I did modified the build script yesterday to include the newly build modules into ramdisk before it get packed into boot.img but didn't change script I pushed to your box. Wanted to test new boot.img first.

I'll send you new boot.img with modules included in /lib/modules folder and if it works I'll revise your script as well.
[Sprint Samsung Galaxy Note II] garwynn:
Think I know what I missed. Adding and trying again.
[Sprint Samsung Galaxy Note II] garwynn:
OK, modules added, wi-fi works.

I also changed the ramdisk mappings to sleshepic's values.

System ROM seems to be working without issue.

Back to recovery side. Booting to recovery still freezes.

Flash TWRP and it will work but then put system boot into bootloop.

Have to clear by flashing stock kernel and TWRP again.

Any thoughts/ideas? Maybe I'll change the ramdisk addresses back to Agat's values and see if it fixes.
[Sprint Samsung Galaxy Note II] agat63:
In Note2 recovery is outside of boot.img and I don't understand why flashing recovery will cause a boot loop.

I can imagine not to be able to boot to recovery but the system is booted/loaded by kernel (boot.img) and recovery should not

affect it in any way. :confused:

And Garwynn you should edit your defconfig to take that "dirty" from kernel build description.

Find the line:

LOCALE_VERSION_AUTO=y (or something similar). and change it to

# LOCALE_VERSION_AUTO is not set.

You will have a clean kernel :D
[Sprint Samsung Galaxy Note II] garwynn:
Found it - CONFIG_LOCALVERSION_AUTO. Will take screenie of next test - probably Monday.

And when I flash the kernel it doesn't boot to recovery - it hangs.

Flash TWRP after that and then boots to recovery OK but system gets stuck.

It's obviously something in the test kernel since stock kernels are fine.

Now just need to isolate what's causing this....

Thanks again for all the help! Think if we get this solved we can consider Phase 1 complete!
[Sprint Samsung Galaxy Note II] agat63:
First test build I made did boot to system according to Rwilco.

Since he flashed boot.img without any modules few things were broke but it did boot.

I'll run 2 builds tonight with different settings for modules and upload it to my dev-host for testing.

Hopefully you or Rwilco will be online tonight and can test both versions.
[Sprint Samsung Galaxy Note II] garwynn:
Here's the fixed screenie.. thanks!

Here's my current test plan:

1) Flash kernel. Automatically boots to system.

2) Try basic functions on system, see if anything stands out.

After wi-fi was fixed seems good here.

3) Reboot to recovery to see if it's fixed. (Using ADB reboot recovery)

This is where I get stuck and started tinkering with flashing TWRP and then kernel to get back to start point.

The test plan is safe enough, just need to find a way to figure out where the problem is.

I probably won't be able to do much over the weekend but will see if I can.