yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Q&A, Help & Troubleshooting] samersh72:
it doesnt depend on your location or what is the "official variant" in your country. it depends on what is the product code of your phone (csc)

for example i live in Lebanon and i have India firmware on my phone, and i can still receive ota update when it comes to India ;)
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] seriouskilla:
Hi folks, I changed provider from t-mobile to o2, but I`d like to keep my mdaIII, but with the functions of the xdaIII (homezone, etc.).

I figured, if the rom / extended rom is changed, everything should work out.

Has somebody already done this or knows how to do it?
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] martinmove:
I have the same Problem. Where can we download the original o2 ROM Datas?? please help !! Thanks
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] LumpiStefan:
Try this:

ftp://xda:xda@ftp.xda-developers.co.../Version_GER/O2_XDAIII_Ext_ROM_131137_GER.rar

Extended ROM should be enough......

Stefan
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] martinmove:
Stfan: Many Many Thanks :-)))))
[Nexus 7 (2013) Q&A] micromarty:
I recently got tasked with making an androdid app at my job and want to run my app on my new Nexus 7 and not in the emulator. I have the latest SDK installed and have adb installed and working. But no matter what I do, when I type adb devices in the terminal it says offline.

I am running OSX 10.8.

Any ideas?

Thanks for the help!
[Nexus 7 (2013) Q&A] sfhub:
Do you get the popup prompt on your phone asking you to accept the RSA identification of your computer?
[Nexus 7 (2013) Q&A] nhidog:
You need adb 1.0.31, you probably running 1.0.29, took me awhile to figure it out.
[Nexus 7 (2013) Q&A] wingzero1:
You've probably already checked this...but do you have usb debugging checked on tablet? If not, then turn on, and make sure to accept RSA.
[Nexus 7 (2013) Q&A] micromarty:
Edit: Upgraded to latest ADB worked!
[HTC EVO 3D] mrg666:
How to build

If you are going to distribute your builds, please don't build your binaries with the same name (i.e. MiRaGe) and distribute in this thread. I would recommend you to start an alternative thread. Otherwise the problem reports will be too confusing for everyone.

First requirement is an ARM toolchain for cross compiling, i.e. using an X86 computer to generate ARM binary. I use Linaro tool chain for cross compiling like many others since Linaro specifically develops tool chains that produce optimized code for ARM architecture.

Linaro toolchains can be downloaded from Linaro binary page. The Linaro-12.03-gcc-4.6 toolchain is very stable/reliable and I recommend starting the development with this toolchain. After the kernel build is successfully done and tested, you can switch to later versions. The toolchain can also be built from the source code available at Linaro website. Cristpoher83 distributes binary packages built from source and I use his 4.7.4 package. It is very reliable. I don't use the experimental gcc-4.8 based toolchains (as of July 2013) since they don't build reliable kernels for me yet.

The binary Linaro toolchain package needs to be expanded in a certain directory, probably inside the home directory. The source code for kernel is available in my Github repo, You can either download the kernel source as a compressed package or you can git-clone it with the following command (you will need git installed in your Linux computer)

git clone https://github.com/mrg666/android_kernel_shooter.git

The kernel source can again be in a specific home directory.

After the source and toolchain are prepared, copy the configuration file for shooteru, arch/arm/configs/shooter_u_config, as .config to the root of the kernel source and use the following command to build the kernel

make ARCH=arm CROSS_COMPILE=~/android/android-toolchain-eabi_46/bin/arm-linux-gnueabi- zImage modules -j6

Replace j6 in the above command according to the number of cpus you have on your computer.

Also set CROSS_COMPILE based on the directory you have expanded the binary toolchain package in your home directory.

I use Xubuntu 13.04 x64 (currently) on my Linux workstation that has a Phenom II X6 CPU (960T unlocked to 6 cores and overclocked to 3.4 GHz), 8 GB RAM, 500 GB HD. The compile time is about 1m32.824s for me using all 6 cores. I have been using Ubuntu since version 10.04 to build Gingerbread, Jellybean, and Linux kernel and updated the OS to each and every new version, all of them worked just fine. There is no magic version of Ubuntu. The build problems arise from the package requirements not the OS version.

The flash package is easy. Just use what I distribute as a template and replace zImage and modules inside the package with your build.

Now that you have source and can build the kernel, you can add all the features you want to the kernel ;)
[HTC EVO 3D] phantom5:
Mirror:

http://superuser.cu.cc/kernels/MiRAGE/
[HTC EVO 3D] mrg666:
4ext is ideal with s-off. Don't forget nandroid backup!
[HTC EVO 3D] phantom5:
Relevant Part:

Starting TWRP 2.5.0.0 on Tue Jul 30 16:05:48 2013

I:Set page: 'install'
I:Set page: 'flash_confirm'
I:Set page: 'flash_zip'
I:Set page: 'flash_zip'
Installing '/sdcard/Download/MiRaGe_shooter_test_kernel_881_gsm.zip'...
Checking for MD5 file...
I:Cannot find file /sdcard/Download/MiRaGe_shooter_test_kernel_881_gsm.zip.md5
Skipping MD5 check: no MD5 file found.
Copying files to /tmp...
minzip: Extracted file "/tmp/dump_image"
minzip: Extracted file "/tmp/mkbootimg"
minzip: Extracted file "/tmp/mkbootimg.sh"
minzip: Extracted file "/tmp/unpackbootimg"
minzip: Extracted file "/tmp/zImage"
Dumping boot image to /tmp...
about to run program [/tmp/dump_image] with 3 args
about to run program [/tmp/unpackbootimg] with 3 args
Updating kernel and making new boot image...
run_program: child terminated by signal 11
about to run program [/tmp/mkbootimg.sh] with 1 args
cat: can't open '/tmp/boot.img-cmdline': No such file or directory
cat: can't open '/tmp/boot.img-base': No such file or directory
Segmentation fault
run_program: child exited with status 139
script aborted: assert failed: write_raw_image("/tmp/newboot.img", "boot")
Flashing new boot image...
assert failed: write_raw_image("/tmp/newboot.img", "boot")
E:Error executing updater binary in zip '/sdcard/Download/MiRaGe_shooter_test_kernel_881_gsm.zip'
Error flashing zip '/sdcard/Download/MiRaGe_shooter_test_kernel_881_gsm.zip'
Updating partition details...
I:Unable to mount '/sd-ext'
I:Actual block device: '', current file system: 'ext4'
I:Set page: 'flash_done'
I:Set page: 'clear_vars'
I:Set page: 'install'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
I:Copying file /tmp/recovery.log to /sdcard/recovery.log
[HTC EVO 3D] phantom5:
oops, yes...

(But cross-recovery-compatibility wouldn't be a bad feature)

-- about 20 mins...
[HTC EVO 3D] howpathetic:
Testing the Kernel

I flashed the kernel via EXT4(smartflash) on my Evo 3D GSM S-ON.

Everything is working (except wifi). I will be testing it now :)

Thanks for the kernel and welcome to the Evo 3D GSM world :)

I will update this post.
[HTC EVO 3D] mrg666:
Thanks for the welcome.

Smartflash is sometimes unreliable. I recommend using Flash Image GUI if you are S-ON. See the MiRaGe thread in CDMA forum for details. I will update the OP with full post after the initial tests.

Thanks also for the initial feedback.
[HTC EVO 3D] phantom5:
COnfirmed, everything but wifi works.

S-off.
[HTC EVO 3D] mrg666:
Thank you!

Can you post a dmesg for the wifi error? You are using the stock ROM, right?

Can you also confirm if the camera works?
[HTC EVO 3D] howpathetic:
Get Wifi working :P but Camera aint working
[HTC EVO 3D] mrg666:
I will check the camera. If you can post a logcat for camera error it would be great.
[HTC EVO 3D] phantom5:
I'll send you a PM.
[HTC EVO 3D] mrg666:
Can you tell more about wifi problem and fix?
[HTC EVO 3D] howpathetic:
Just flashed it via Flash Image GUI, EXT4 doesn't flash the kernel properly.

Try to add

"set_perm_recursive(0, 0, 0755, 0644, "/system/lib/modules");"

to your updater script :)
[HTC EVO 3D] mrg666:
I added the permissions line as you suggested in the updater script. It has not been a problem before ... but it makes sense since the problem looked like failing to load the wifi module. It is hopefully fixed now. I have also applied a fix for the camera. I would appreciate if you can test again. The newer 882 build is in the OP.
[HTC EVO 3D] weirdsciencex:
Getting invalid key error while trying to download.
[HTC EVO 3D] phantom5:
I only have the 881 version, unfortunately
[HTC EVO 3D] mrg666:
Thanks to howpathetic, I fixed the build script problem for WiFi. I am working on camera now. Hopefully that will also be fixed soon. The download is available in the OP again. Please report if you find any other problems. Thank you all for your help :)
[HTC EVO 3D] cenex:
hi,can you add sweep2wake function? thank you :D
[HTC EVO 3D] Z O X:
And again ...

Anyway, I have noticed some strange behaviour with battery (4.0.3 ROM):

deleting battery stats file and rebooting phone causes addidtional charging that can't be done with charge bump.

It gives additional 10 - 12h of usage but only until next charge. In stats aren't deleted, battery life is back to cca 36 hours.

A week of training the battery has not changed anything. Clearing stats again gives much better life.

It was tested on two different batteries with three kernel versions.

Back on 2.3.4 ROM and situation is similar (clearing gives about 6 - 8 hours).

Any1 else experiencing this?
[HTC EVO 3D] mahg:
Is already included in Johnnyslt kernel: http://xdaforums.com/showpost.php?p=45851760&postcount=265 which is based on MiRaGe so I guess it's 'easy' to add it.

I'm playing with it without problems although at the begining it didn't respond very quickly and a reboot was needed after enable this feature.
[HTC EVO 3D] sdeft:
I didn't bother you any more cause I knew you were busy on the JB and your new phone! I was able to fix the errors myself. For the prior to your new ondemand commit the error was in cpufreq_ondemand.c. A parenthesis was missing in the below line

idle_time = (cur_wall_time - busy_time);

Also there is a warning for defined(CONFIG_ARM_UNWIND) in arch/arm/kernel/return_address.c. I fixed it by below line

#if 0 // defined(CONFIG_ARM_UNWIND)

Managed to build a kernel with sweep2wake from btoast's kernel. I can include here the changed files for anyone interested.
[HTC EVO 3D] mrg666:
I had disabled the old ondemand since it was not working well. I recommend using the updated ondemand in my repo instead of making the old one compile.

There is no warning in my build with arch/arm/kernel/return_address.c. That should be because of your changes.

Anyway, have fun! I know, it is a great to have your own kernel/ROM on your phone.
[HTC EVO 3D] helicopter88:
There has to be a warning in that file because it's triggered by the file itself,using #warning

If you do not have it then either you #if 0'd the warning or you disabled stack unwinding in kernel defconfig
[HTC EVO 3D] mrg666:
Oh, it is this one!

#if defined(CONFIG_ARM_UNWIND)
#warning "TODO: return_address should use unwind tables"
#endif

Yeah, it is there but it is not a warning issued by compiler itself. Code instructs the preprocessor to print that warning.

Whatever, thanks!
[HTC EVO 3D] mrg666:
I have updated the MiRaGe builds. Please see the OP for downloads and my repo for changes.
[HTC EVO 3D] Arbelzapf:
Is there a link to the JB kernel in the OP? I only see a link to HTC/Sense ICS ROM (09292013).

If yes, did you update the JB kernel as well?
[HTC EVO 3D] mrg666:
Yes there is a link in the OP to another post where the download link is :cyclops:

http://xdaforums.com/showpost.php?p=45696923&postcount=113
[HTC EVO 3D] Arbelzapf:
I guess it didn't jump in my face enough. Thank you very much, will flash immediately

EDIT: The new Wifi driver seems to have a problem. Here's a log of me trying to enable it a couple of times.

I'm still on LiquidSmooth and have no Wifi at all
[HTC EVO 3D] mrg666:
I have updated the wifi module. Can you please try again and let me know? Thanks!
[HTC EVO 3D] Arbelzapf:
It's working now, thank you :highfive:
[HTC EVO 3D] sdeft:
mrg I tried to patch your kernel to 98 and is failing at

patching file drivers/net/usb/cdc_ether.c

Hunk #1 FAILED at 615.

I compared this file with other evo3d kernels and I noticed that there are some other things missing too (some devices I figured).

So I have a general question. Your kernel is not based on the stock one ? Have you "trimmed" some files on purpose ?

I am not complaining...just learning...!!!
[HTC EVO 3D] mrg666:
I have updated the JB kernel with usb/gadget and bluetooth updates from Johnnyslt. ICS kernel is also updated but only with Linux 3.0.98 and 3.0.99 patches. See the download link in the OP. Thanks to Johnnyslt.

MiRaGe is far from both stock Linux and HTC stock kernel. So the patches for stock kernel sometimes need modifications.
[HTC EVO 3D] mrg666:
Android1234567 (sultanxda@github) graciously donated a brilliant patch for the shooter kernel that increases the RAM available for Android to 876MB (from 798MB) by more efficiently allocating the memory used by the kernel. I have merged the patch and tested briefly. Everything seems to be working fine. The only caveat is that HDMI output has been disabled which is not working in AOSP anyway. The test kernel for AOSP/JB is below.

http://www.mediafire.com/download/v676v6vmlv99lab/MiRaGe_shooter_u_test_kernel_992_jb.zip

Please test and let me know if you find any problems since this is a very critical patch.

Also, please go to Android1234567's thread and give him a thank you. He truly deserves a kudos for this.

I have not tried this patch with the ICS/Sense kernel yet since I am not sure if it is okay with everyone to lose the HDMI output capability. Let me know if you have any objections/comments so that I can decide what to do with ICS/Sense kernel.
[HTC EVO 3D] Sultanxda:
A few additions: leave your phone on as long as possible with this test kernel in order to check for random reboots. The surfaceflinger allocation is smaller than before so it is crucial that you test the long-term stability of the kernel. If there are random reboots being caused by surfaceflinger being too small then they can be fixed at a price of 5MB of RAM. If there is a Sense ROM with HDMI working then HDMI functionality can be kept in the ICS kernel with the new memory map at a price of 10MB of RAM.
[HTC EVO 3D] SebRut:
For me, HDMI isn't, I actually never used it;)
[HTC EVO 3D] fxjumper:
Hi mrg666

Could you implement Fastcharge in your kernel?

Thanks

FX
[HTC EVO 3D] Arbelzapf:
I have been running the new kernel for one day with zero problems.

Everything seems fine. Thank you very much

To be quite honest, I'd prefer if the Sense kernel would be kept 100% functional. I have used HDMIout exactly once - for the sake of having used it once. But When I flash a Sense rom, I'd like to be sure that everything works. In my opinion, "gaining 10mb less" is a small price to pay to keep things the way they are.

That's just my 2 cents. As I said, I pretty much never use that feature myself, so I could absolutely live without as well.
[HTC EVO 3D] mrg666:
I agree. I will not disable HDMI (or any other feature) in the stock ICS ROM.

Hi, I don't like the idea of pushing a cheap charger (or USB port) beyond its load limit. And fastcharge hack doesn't make a good charger faster. A good charger is not that expensive.
[HTC EVO 3D] gigsaw:
If my memory is good, some time ago you were trying to port 3.4 kernel to Evo 3D..Have you continued this hard project?
[HTC EVO 3D] mrg666:
I haven't completed it. It needed much more time than I thought initially.
[HTC EVO 3D] gigsaw:
[YOUTUBE][/YOUTUBE]

Yeah, I think that kernel-related work is always the hardest part, so I can understand. Have you totally abandoned and definetly stopped that project or are you slowly working on it and maybe in some future we will see it?

Anyway I think that your kernel is the best one for evo 3D, compliments :)
[HTC EVO 3D] mrg666:
Porting a device to a different kernel is almost like a black art. There are so many ways to do it and switching from PMEM to ION is definitely not simplifying the task. I have left the 3.4 shooter kernel undone after recently switching to Nexus 4 and started working on the mako kernel. A Nexus 7 (grouper) kernel is waiting to be next. Another Samsung Galaxy Reverb (icon) kernel was going parallel with the shooter and I want to do a kernel for Sprint SGS3 (d2spr) as well. I am still keeping the EVO3D and I might go back but I want to work on the mako and grouper kernels before that.
[HTC EVO 3D] mrg666:
Everyone, I think we are done with testing the 992 experimental build. There were several crashes/reboots reported with the new memory map. I have deleted the experimental build and will upload the next build after fixing the problem. Sultan is working on it. Please go back to stable 991 build until that time. Thanks for all the feedback.
[HTC EVO 3D] THC Butterz:
mgr666, your kernel is awesome, and i truly believe you produce the best kernels to date for the 3vo, (not that there are too meny kernel devs left for the 3vo)... but i digress, i am and have been atempting to port sense 5 and sense 4+ Jellybeanz to our outdated novlty devices...lol, have you experimented with mayby trying to port a jb sense kernel to our phones? maybe from the htc one s c2... if so any luck? if not any advice?
[HTC EVO 3D] mrg666:
Thanks to Sultan, here is his second iteration of kernel memory allocation mod which should fix reboots.

http://www.mediafire.com/download/u40itzfp0yacfal/MiRaGe_shooter_u_test_kernel_993_jb.zip

Please test and let us know.
[HTC EVO 3D] mrg666:
Yes, actually. Mobstergunz (@ androidforums) and I had given it a shot. The main problem is that the suitable JB Sense ROMs (such as villec2) for porting to shooter require ION 3.4 kernel. AFAIK, there are no Sense 3.4 kernels for shooter and I wasn't able to complete my part to do the kernel. You can have a look at Evervolv AOSP kernel which is ION and 3.4.
[HTC EVO 3D] Sultanxda:
Those Sense JB ROMs don't require a 3.4 kernel; all they need are a proper porting and an ION kernel. Getting camera working with the current PMEM libs will be impossible and getting audio working with PMEM will be extremely difficult.
[HTC EVO 3D] gigsaw:
Yeah of course you're right, ION instead of PMEM is the point..but I don't know if it's useful compiling a 3.0.xx ION sense kernel, I mean..if someone will ever accept the challenge (SENSEJB on Evo 3D), probably is convenient making a bigger effort once (3.4 and ION) than trying to compile a ION kernel 3.0.x which is quite outdated..of course I am definetly not a Kernel developer, I'm just trying to understand. Of course, as everybody know, for htc sensation SebastianFM succeeded in porting 3.4 ION kernel for SenseJB, probably this could be an help if sensation and evo are similar(?)

Finally yeah, if this kernel will ever come on Evo, IT would be possibile to porta a Sense 4+ ROM, but I don't think that sense 5 is possibile because I heard that HTC blamed Qualcomm to have abandoned the S3 family (lack of drivers and so on), and on ville c2 there's a petition for that..but I don't think it will change anything. It's all on developer's hands, ad usual with HTC..now HTC complains because can't sell enough new phones even if they have a premium quality built and so on, they blame lack of advertising..I think that one big problem is that there are many users with s3 phones that were abandoned with updates and they got angry with HTC, so probably they wouldn't buy HTC no more because they are angry, IMHO at least..
[HTC EVO 3D] Sultanxda:
Sense 5 with Android 4.1.2 can work. A 3.4 kernel is very very very very difficult to port, and it will not fix the camera or audio on a Sense JB ROM. Porting ION to the 3.0 kernel is a piece of cake and probably would only take 1 hour; a 3.4 kernel is 100x harder and could take weeks or months, and even then it isn't guaranteed that it'll boot.
[HTC EVO 3D] ngochuy:
The easiest way to port 3.4 is to change the text to 3.4. I mean fake number, lol
[HTC EVO 3D] helicopter88:
I already have a 3.4 with ION booting and working not fully and a 3.0 with ion(everything but camera working)
[HTC EVO 3D] Z O X:
Can you, please, give us mempatch version kernel for ICS?

I understand concerns about stock rom but I'm back to gb precisely because it gives more ram. HDMI out is totally unimportant for me but 80 megs od ram is night and day situation ...

--

over 'droid
[HTC EVO 3D] mrg666:
We tested the mem allocation patch with android1234567 for the ICS kernel. The 3D camera and viewing functions also were failing in addition to HDMI. Since 3D is not functional in AOSP ROMs, it didn't matter but stock ROM has working 3D. BTW, although 69MB extra RAM is very nice to have, it really doesn't make that much difference to call it "night and day". Because the amount of RAM in EVO3D is large enough for ICS. But I will post the kernel as soon as 3D functionality is restored with a modified mempatch.
[HTC EVO 3D] Z O X:
Thank you very much!

As for RAM, I have to disagree. ICS roms leave less free ram and with zeppelinrox time killer patch some app I use regularly drop out.

Night and day for me means that on a phone with 1GB of RAM I want to have all my apps alive and switch instantly.

It's not possible on ICS (with swap yes, but I was using your great kernel) with my usage pattern (no games).

Never had free RAM above cca 450 - 500 MB on ICS.

On GB, one can have 600+ MB free and no worries about dropping apps.
[HTC EVO 3D] mrg666:
There were still several reboots with the second iteration of new memory map. Android1234567 kindly did another modification to fix those reboots. Here is the third iteration that will hopefully be last.

http://www.mediafire.com/download/zc4j1kakp277pr3/MiRaGe_shooter_u_test_kernel_1001_jb.zip
[HTC EVO 3D] jcsy:
Regarding ram, I notice it doesn't really matter how much

As long as u set the OOM settings to kill processes, such as 256 MB, it will keep killing every non useful thing that is open

And it seems 256 is the highest it can go

I do notice the things that always restart and run again are widget related things

Attached is a screen shot of my ram manager, it seems to be all the apps which are some sort of widget on home screen only. The rest are not open...

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

Tapatalked from my HTC EVO 3D GSM

CM10.2 | 5Oct2013

Mirage kernel | CFQ

-----------------------------------------------------
[HTC EVO 3D] mrg666:
The extra ~70MB RAM helps with reaching the OOM limits later than sooner for the lowmemorykiller. So lowmemorykiller will be working less and there will space for one or two more apps in the memory. Since 1GB RAM of EVO3D is not causing any serious shortage of memory for JB, 70MB extra RAM doesn't show a drastic improvement. But there is an improvement, at least in battery life, since lowmemorykiller works less. Thanks for the feedback.
[HTC EVO 3D] gigsaw:
But why nobody has ever ported ION on 3.0XX kernel if it's so easy? Sorry if I'm wrong but I knew that porting ION will break some functions, like camera, microphone, bluetooth and it's not easy to fix them..I'm not a kernel developer, I'm only trying to understand with my poor knowledge, sorry.

Of course Domenico, you have an enormous knowledge, but I know that you wil never work on closed source-sense roms, and it's a pity because you would be the right person for this heavy work ;) anyway thank you and good work for your AOSP kernels :good:
[HTC EVO 3D] helicopter88:
Porting ION is extremely easy, and using it in AOSP roms is also easy

Using it on a closed source rom might be tricky,tho
[HTC EVO 3D] Sultanxda:
Nobody has ported ION because the camera won't work (our camera libs, specifically liboemcamera, use PMEM). Audio can work on AOSP by allocating audio with PMEM, but audio will be very difficult or impossible to get working on a Sense 4+ ROM (HTC removed support for the TPA2051D chip, so unless the Shooter uses a different chip...).