yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab A series Guides, News, & Discus] pottu221:
So i decided to make this new thread to android tab a. here everyone can post their roms and kernels and everything to this nice device. :)

and if someone could help me out with my first kernel. im building it to this device.

i get this error when i try to compile kernel whatever how i change the toolchains and ubuntus and like that. nothing helps

pottu@pottu-HP-Pro-3405-Series:~/akernel$ export ARCH=arm

pottu@pottu-HP-Pro-3405-Series:~/akernel$ export CROSS_COMPILE=/home/pottu/toolchain/bin/arm-eabi-

pottu@pottu-HP-Pro-3405-Series:~/akernel$ make msm8916_sec_gt510lte_eur_defconfig

drivers/misc/Kconfig:414:warning: type of 'TIMA_LOG' redefined from 'boolean' to 'tristate'

drivers/misc/Kconfig:745:warning: choice value used outside its choice group

drivers/misc/Kconfig:747:warning: choice value used outside its choice group

drivers/misc/Kconfig:755:warning: choice value used outside its choice group

drivers/misc/Kconfig:758:warning: choice value used outside its choice group

drivers/misc/Kconfig:760:warning: choice value used outside its choice group

KCONFIG_SELINUX((null))

KCONFIG_LOG_SELINUX((null))

KCONFIG_TIMA((null))

KCONFIG_DMVERITY((null))

KCONFIG_VARIANT((null))

***

*** You must specify VARIANT_DEFCONFIG !

***

/home/pottu/akernel/scripts/kconfig/Makefile:130: recipe for target 'msm8916_sec_gt510lte_eur_defconfig' failed

make[1]: *** [msm8916_sec_gt510lte_eur_defconfig] Error 1

Makefile:508: recipe for target 'msm8916_sec_gt510lte_eur_defconfig' failed

make: *** [msm8916_sec_gt510lte_eur_defconfig] Error 2

pottu@pottu-HP-Pro-3405-Series:~/akernel$ make VARIANT_DEFCONFIG=msm8916_sec_gt510lte_eur_defconfig

scripts/kconfig/conf --silentoldconfig Kconfig

drivers/misc/Kconfig:414:warning: type of 'TIMA_LOG' redefined from 'boolean' to 'tristate'

drivers/misc/Kconfig:745:warning: choice value used outside its choice group

drivers/misc/Kconfig:747:warning: choice value used outside its choice group

drivers/misc/Kconfig:755:warning: choice value used outside its choice group

drivers/misc/Kconfig:758:warning: choice value used outside its choice group

drivers/misc/Kconfig:760:warning: choice value used outside its choice group

***

*** Configuration file ".config" not found!

***

*** Please run some configurator (e.g. "make oldconfig" or

*** "make menuconfig" or "make xconfig").

***

/home/pottu/akernel/scripts/kconfig/Makefile:36: recipe for target 'silentoldconfig' failed

make[2]: *** [silentoldconfig] Error 1

/home/pottu/akernel/Makefile:508: recipe for target 'silentoldconfig' failed

make[1]: *** [silentoldconfig] Error 2

make: *** No rule to make target 'include/config/auto.conf', needed by 'include/config/kernel.release'. Stop.

pottu@pottu-HP-Pro-3405-Series:~/akernel$
[Samsung Galaxy Tab A series Guides, News, & Discus] Chemnitzer:
Any Progress?
[Samsung Galaxy Tab A series Guides, News, & Discus] pottu221:
nope. broke the tablet anyway so im not even trying anymore
[Samsung Galaxy Tab A series Guides, News, & Discus] ashyx:
See here for some ideas of where you're going wrong.

https://github.com/ashyx/Samsung_Galaxy_Tab_A_kernel

http://xdaforums.com/showthread.php?t=3433560
[Samsung Galaxy Tab A series Guides, News, & Discus] jedld:
Integrated kernel building for CM must be properly setup:

In your boardconfig you have to tell CM what kernel config to use. Note that it is usually named after your device, for the SM-T285 which is gtexslte internally it looks like this:

TARGET_KERNEL_SOURCE := kernel/samsung/gtexslte

TARGET_KERNEL_CONFIG := gtexslte_defconfig

TARGET_VARIANT_CONFIG := gtexslte_defconfig

TARGET_SELINUX_CONFIG := gtexslte_defconfig

If you don't what to use integrated kernel building and what to specify a prebuilt, comment those lines above and use something like this:

TARGET_PREBUILT_KERNEL := kernel/samsung/gtexslte/arch/arm/boot/zImage

Point it to your stock kernel image
[E 2015 CDMA Android Development] Sands207:
I made an updated flashable VM fix from V.R2 of Mopedryder's version of the fix http://androidforums.com/threads/vi...rgin-mobile-apn-fix-wip-cm-aosp-4-4-x.840298/. I wrote a new updater-script to accommodate our new apns-conf. This also deletes telephony databases and updates the build.prop somewhat accordingly,carrier brand is also correctly set as VM also. I recommended using this on a clean flash of your ROM or after a factory reset, let me know if you get LTE,text and calls working and which ROM and kernel you are using and we can add or change stuff. This should work with CM 12 & 13 :)

Take a backup first via twrp before using this. I am not responsible for any damage you cause on your end!

How to install:

Download to Ext SD Card

Reboot into recovery

Either Clean Flash with ROM &Gapps

Or

Flash and then

Factory Reset (Dalvik,Cache,Data)

Reboot

LTE should immediately turn on

texts and MMS should now work, textra helps if you get problems sending pics.

https://drive.google.com/file/d/0Bz99NuhE3XwmRnRTWW9SejY2MlE/view?usp=docslist_api

Sent from my Virgin Mobile Moto E via CM 13
[E 2015 CDMA Android Development] soupysoup:
Thanks man, I was actually working on this, used the other thread to manually get everything working, once I saw it worked I was working on a script to do it via flash like this, I just got the device to have a decent phone while my Nexus 6 is getting rma'd, must say I'm super surprised at this little $40 phone
[E 2015 CDMA Android Development] Sands207:
This is my favorite phone I've had so far, I broke the screen on my old one and bought another one because I wanted to see LTE work on the custom ROMs so badly. [MENTION=6755483]Starklyraving[/MENTION] and [MENTION=6430051]hydroman202[/MENTION] have been so awesome working all along to get this fixed. Cheers guys! :)

Sent from my Virgin Mobile Moto E via CM 13
[E 2015 CDMA Android Development] fivefour:
Thanks
[E 2015 CDMA Android Development] deega:
I spent some time this afternoon throwing together an Aroma flashable zip to activate LTE on Boost, FreedomPop, Sprint, Ting, and Virgin Mobile. It's a really simple setup, but I've hit a hangup getting build.prop to edit in recovery mode.

Is your zip actually patching build.prop or is it just acting like it does?

Mind you, I've had LTE running fine with no changes whatsoever to build.prop so I may just cut those patches out.
[E 2015 CDMA Android Development] Sands207:
I double checked the prop.sh file and I made a few edits to fix mms but I'm not finished yet,I'll upload that tomorrow but to answer you the zip also clears the correct databases and replaces the eri and apns_conf file and changes the numeric in build.prop and carrier branding

Sent from my Virgin Mobile Moto E via CM 13
[E 2015 CDMA Android Development] scritch007:
I don't really understand what is the difference with https://github.com/Motorola-Cyanoge...mmit/8a6f577c866c3979d758bbe48d3bb0565fd94a1d

unless at that time the values that were provided were wrong, in the apns-conf.xml and eri.xml were wrong, this patch used to do the same thing. (I actually didn't make the diff for now)

Update the getprop values, copy apns and eri to the right place.

I some of you guys want to send me the fix for all the providers. I'll make it by default in the "CAF" build.

CM13 will most probably won't get the fix.
[E 2015 CDMA Android Development] soupysoup:
I will say I'm super impressed with moto for this device, I mean come on, I paid $40 for this thing, it performs almost as well as my Nexus 5, I just wish it had a little bit bigger screen and some more storage, but I mean for $40 really, I had very low expectations for this phone, it was just something to get me by until me N6 comes back from RMA, but after using it for a week I'm impressed, I'm actually working on 6.0 for it too, bcuz I know it can run it and I think it will improve on an already amazing device, good stuff moto, after my Nexus 6 I wasn't a fan of moto, but this restored my trust in them a great deal....
[E 2015 CDMA Android Development] deega:
The main difference is in apns-conf.xml. eri.xml is purely cosmetic and LTE works perfectly without patching build.prop. I'm currently pulling the build.prop patching from my zip and updating the various apns-conf.xml files with the most current information. I'll upload in a bit.
[E 2015 CDMA Android Development] Sands207:
[MENTION=3445372]scritch007[/MENTION] Thanks, if you could include it that would great. The difference is on lines 23 + 24 of prebuilt/system/etc/cdma/virgin/apns-conf.xml the value for LTE for Virgin Mobile at least in the US I believe is n.ij.ispsn instead of v.vmu.ispsn which is used for 3g data that is there now. I am guessing with the introduction of spark network the value was changed. The prop fix just sets our carrier branding correctly as Virgin Mobile in settings>sim info and in quick settings because by default without the fix we are listed as using Boost Mobile as our carrier and in quick settings it will just read "roaming indicator off" and can only use 3g. I am using the fix in CM 13 right now. The only difference between flashing the fix with CM 12.1 and 13 and probably CAF too is that APN's can be viewed,added,edited etc in CM 12.1 and in CM 13 APN's are not visable but the fix still works by replacing the correct files and prop edits.
[E 2015 CDMA Android Development] deega:
The carrier information in SIM status is taken from eri.xml. I get no difference in functionality between patched and unpatched build.prop files. It may have once been necessary, but I think whatever problems those build.prop patches solved have been resolved.
[E 2015 CDMA Android Development] Sands207:
OK great :)

Sent from my Virgin Mobile Moto E via CM 13
[E 2015 CDMA Android Development] deega:
I just looked a bit deeper into the code you linked. (specifically init_surnia.c) It's setting the CDMA values based on the value of ro.boot.fsg-id, expecting virgin or sprint else it's boost. A getprop ro.boot.fsg-id returns nothing on my CAF 0.10 surnia. getprop ro.cdma.home.operator.numeric returns 311870 (boost). Expected behavior would return the following in my case:

ro.boot.fsg-id=virgin

ro.cdma.home.operator.numeric=311490

If I understand the structure of APN entries correctly, getting this resolved would make it possible to include the APNs in the default apns-conf.xml.

I'm not sure how ro.boot.fsg-id is derived, but adding ro.boot.fsg-id=virgin to build.prop doesn't alter the above behavior.
[E 2015 CDMA Android Development] scritch007:
Yes this is taken from the CDMA test build I made. I had asked people to set the fsg-id to the correct value. This can be done thanks to fastboot:

fastboot oem config fsg-id virgin

This wasn't added into CM.
[E 2015 CDMA Android Development] deega:
Something like that would certainly help! If the CDMA properties were set based on a user-selectable carrier then it would solve a lot of headache with the apns-conf.xml files. We know the appropriate APNs for Boost, Sprint, and Virgin. It would be nice to have them folded into the default apns-conf.xml.
[E 2015 CDMA Android Development] fivefour:
It definitely would. I don't understand why this isn't already fixed in CM 12.1, it also should be listed as an issue in the wiki but it isn't.
[E 2015 CDMA Android Development] deega:
I just tried placing the values from the code [MENTION=3445372]scritch007[/MENTION] linked into build.prop like so:

ro.cdma.home.operator.numeric=311490
ro.cdma.home.operator.alpha=Virgin Mobile US
gsm.sim.operator.numeric=311490
gsm.sim.operator.alpha=Virgin Mobile US
gsm.operator.numeric=311490
gsm.operator.alpha=Virgin Mobile US

Then I tried appropriately tagging the VM APNs with numeric="311490" mcc="311" mnc="490" while including them in a default, huge apns-conf.xml file.

Even with the proper numeric codes set in build.prop, the phone populates its APN database with Sprint (310120) APNs. Getprop yields the following results:

ro.cdma.home.operator.numeric=311490

gsm.sim.operator.numeric=31000

gsm.operator.numeric=310120

I sure hope hardcoding these values into init works better than defining them in build.prop. :) It's clear that the value of gsm.operator.numeric is pretty important. It's also clear that patching build.prop doesn't help us.

Pardon me if this is all old news, but I'm pretty new here.
[MDA III, XDA III, PDA2k, 9090 ROM Development] linuxpete:
Hi @all,

First of all I would like to thank all the xda-developers for their outstanding work, especially to Helmi.

I am thinking about upgrading my VPA III to WM6. It is a VPA III (PH20B2) from Vodafone Germany.

Before I continue in upgrading, could someone please answer me the following questions:

1. Can I use Helmis ROM to upgrade my device?

2. I did a backup of my ROM with the mtty-tool on sd-card. Is it possible to go back to the original ROM by using this sd-card, as far as I do not change the size of my ExtROM, by inserting it into the device and change into bootloader?

3. Is there a possibility to use my qwertz-hardwarekeyboard? (It is, found in the forum http://xdaforums.com/showthread.php?t=326687)

4. Is there a german translation?

5. Can I use my BT-headset to use voicedial by using MS-VoiceCommand 1.6 (did not work under WM2003)?

Thanking you in advance

Peter
[MDA III, XDA III, PDA2k, 9090 ROM Development] linuxpete:
Is there anybody who can answer even one of my questions? The most important one is question numner 2.

Greetings

Peter
[MDA III, XDA III, PDA2k, 9090 ROM Development] borjok536:
...

the answer is yes
[MDA III, XDA III, PDA2k, 9090 ROM Development] linuxpete:
Hi borjok536,

thank you for the answer. Does it mean "Yes" to all my questions or only "Yes" to question number two? I am still afraid of upgrading because the last time I did it I got massive problems with my bluetooth. I had to send my VPA to vodafone.

By the way: In all descriptions (wiki and forum) they all speak about PH20B1 or PH20B or PH20A1 but mine is a PH20B2. Does it make any difference?

Thank you

Peter
[MDA III, XDA III, PDA2k, 9090 ROM Development] stephenw10:
Hi All,

I too have a PH20B2. It's a Vodaphone UK V1620. Vodaphone often refuse to belive it exists when I speak to them!

I'd love to know if this ROM is safe to use with it.

Cheers,

Steve
[MDA III, XDA III, PDA2k, 9090 ROM Development] linuxpete:
Hi stevenw10,

unfortunately so far it is not save. I am thinking of going back to WM2003. I have Problems with WIFI, and GSM. Maybe someones has the same problems and solved it.

Grettings

Peter
[MDA III, XDA III, PDA2k, 9090 ROM Development] xplode:
For short i will answer with yes and no

1. YES

2. YES

3. YES

4. NO

5. I think that the answer is YES but i have not tryed it

regards

xplode
[MDA III, XDA III, PDA2k, 9090 ROM Development] DANDANA:
Vodafone will not support WM6 on your phone; also will not support WM5.

Its safe to use, but isn't perfect; nor isn't WM2003.

@linuxpete

I don't have any of your problems with WiFi or GPS
[MDA III, XDA III, PDA2k, 9090 ROM Development] stephenw10:
I realise that Vodaphone won't support anything other than WM2003/SE.

What I didn't realise, before I bought it, is that they don't really want to support the hardware at all!

I have rung them and told them I have a Vodaphone V1620 and they have said to me 'that phone does not exist'!

Not really what I call good support.

You're running an XDA IIs which is the standard PH20B and not a PH20B2 like me and linuxpete.

Anyone else tried a PH20B2?

Steve
[MDA III, XDA III, PDA2k, 9090 ROM Development] linuxpete:
Yes me. I installed WM6. I will keep it. I still got the problem with BT and Voice Command. I can't hear any announcements form VC through my Headset. Anyway in WM2003 this wasn't (and couldn't) working either. I also got problems with my GSM. I must manually connect to GSM 900 MHZ (Vodafone Germany). With GSM 1800 MHZ everything wokrs fine (I use a dual-sim-adaptor). I can live with it.

Greetings

Peter
[MDA III, XDA III, PDA2k, 9090 ROM Development] stephenw10:
That's great news Peter!

I'm off to try it now.

Steve
[MTCB Android Head Units Q&A] DRidilla:
Hello,

I recently sold my car and no longer have the need for one of these MTCB units. Like an idiot, I forgot to wipe my information from the unit (Eonon / KLD) before uninstalling it.

The unit is made for plug and play with a Mazda 3. Is there something I can do to power it on without the car, so I can erase all of my information / settings and get it ready for resale. Otherwise I'm not going to feel safe selling it. (Even though I could probably revoke the important accounts from the cloud.)

Thanks.
[MTCB Android Head Units Q&A] dazza007:
I used a PC power supply.

You need 3 pins Positive and negative for power and positive for ignition power

Look at the adapter wiring specific for your car and you will figure it out.
[MTCB Android Head Units Q&A] MAJED.y:
No need to a PC power supply, an AC Adapter 12v - 2a is sufficient.

Cut the end if the connector and make 3 wire ( 2x positive - 1x negative ).

1 positive, 1 negative wire to the power pins "normally the thin pins" to power up the unit

1 positive wire to the ignition wire to start the unit.
[MTCB Android Head Units Q&A] Zorba2pi:
I used a PC power supply, the yellow wires are 12V, black are ground. I just put the battery and ignition wires in the yellow wire plug and the ground in a black wire black on a 4-pin Molex connector.

To turn on the power supply, you have to jumper the green wire to a black wire in the 24-pin motherboard connector.

Make sure the power wires can't touch the ground pins. I kept shorting mine out and took me a couple times to figure out what was happening.
[MTCB Android Head Units Q&A] DRidilla:
I'm like an absolutely moron with wiring so this sounds fun!

I guess hacking up the adapter is better than never selling the unit anyway. Thanks everyone for all the help.
[MTCB Android Head Units Q&A] dgcruzing:
youtube is your friend when it comes to this.. plenty of video's on it..

I have made one up myself from youtube videos
[Verizon Samsung Galaxy S III] 6LygoOs3:
Hey everyone, I've been researching for days, trying to figure out how to Unlock my bootloader on a 4.2.2 OS d2vzw(Verizon SGS3) SCH-I535. it seems the only way I can start flashing new roms( specifically CM 12.1) is to install a custom recovery such as TWRP or CWM, but it locks up my recovery and I end up flashing the stock 4.2.2 over and over again. are there alternatives ways to flash roms? is it impossible to unlock my bootloader on a 4.2.2? is there a way I can downgrade my bootloader? help please nothing is working and I can't find current information....Thanks.
[Verizon Samsung Galaxy S III] ShapesBlue:
I'm assuming you mean 4.4.2 or 4.1.2. There is a huge difference between the two.

If you are on 4.4.2 you do not have the option to unlock the bootloader.

However if you are on 4.1.2 you do have the option to unlock the bootloader. There never was a 4.2.2 update for the VZW S3.

Nexus 6 via SSHD/Cataclysm
[Verizon Samsung Galaxy S III] FlashHappy78:
http://www.mobiletechvideos.com/samsung-galaxy-s-iii-s3-bootloader-downgrade-service/ I should start a thread with this LOL. This guy is the only guy I know of that can do it. It's done by soldering a jtag in 3 spots all within millimeters of each other. I've sent a bunch of business his way and never saw a bad review
[Sprint Samsung Galaxy S III] jeeves_m:
I have a S3 (SPH-L710) that has always had hardware issues, but has been usable. Now I need to return it to the stock firmware so I can activate it with Ting under a new number. Can I flash it back to stock firmware using Team Win Recovery? I have grabbed the latest firmware for the phone from the sammobile.com website but am not sure if this file is meant to work with Team Win Recovery.

Normally I would use one of the more traditional methods of restoring stock firmware, but they all fail on this phone:

Kies - Accepts the model number & the MEID, but can't get past a greyed out "Start Upgrade" button.

Heimdall (on the command line Linux) - can't detect the phone.

Odin (on Windows) - fails to detect phone

I have checked the usual suspects for phones that are not detected (usb drivers, bad cable, not being in download mode) but no success.

I am able to successfully flash new ROMs with Team Win Recovery at least, but I have never heard of someone doing this with factory firmware.
[Sprint Samsung Galaxy S III] madbat99:
Nope. Cannot flash a .tar in recovery. It is definitely one of the problems you listed. Odin WILL detect a Samsung phone when its in download mode. One of those is definitely your problem. But you can try the app flashfire by chainfire. I think you have to go to the flashfire website (Google it) before it shows in the play store because its in beta. But it will flash .tar files on the device.
[Galaxy S 4 Q&A, Help & Troubleshooting] Sanji-:
How can i get the Emoji from ios to my Keyboard (Google Keyboard)?

Do i have to flash a zip file?
[Nexus 6P Q&A, Help & Troubleshooting] mdoshi50:
Hi guys,

In my car I have a Kenwood DNX 6990HD system which has a 5V/1A USB outlet built in. I just bought a Nexus 6p and bought a corresponding TechMatte USB type C to type A cable from Amazon.

When I plugged in my phone, I got the pop up asking what I wanted to do and I selected the "charge only" function. However, the phone doesn't seem to actually charge. Is there something I'm missing here or am I doing something wrong? Any help would be greatly appreciated.

Thanks.
[Nexus 6P Q&A, Help & Troubleshooting] LosserKlosser:
I have a USB A to USB C cable and when I plug it in my car charger (you know, the cigarette lighter port) it doesn't charge. I *think* the output charge is too small but I don't know. I'm very interested in the solution to your problem.

Sendt fra min Nexus 6P med Tapatalk
[Nexus 6P Q&A, Help & Troubleshooting] geoff5093:
1A is more than you get from a laptop, so it's enough to slow charge. Of course if you are using your phone at the same time with the screen on or navigating, it's going to drain faster than it can charge. Download the app Ampre (I believe that's how you spell it).
[Sony Xperia ZR] gavranpero:
Hello there! Since I bought this phone I've always had sound problems while using camcorder. I used the first and, probably, the only method to fix it (change number ACDBID 545:2 to ACDBID 528:2), but it wasn't good enough. The sound was too quiet on records, and it wasn't really clear. For a while now I've been trying to fix it and I thought of trying to record sound by using only one microphone. The other microphone is no longer used. As a result, I got video records with clear and loud sound. Here is what I did. I changed this

SectionDevice
Name "Camcorder Stereo"
Comment "Dual MIC recording device"

EnableSequence
'SLIM_0_TX Channels':0:Two
'SLIM TX7 MUX':0:DEC4
'DEC4 MUX':0:ADC3
'DEC4 Volume':1:66
'SLIM TX8 MUX':0:DEC7
'DEC7 MUX':0:ADC1
'DEC7 Volume':1:85
'ADC3 Volume':1:100
'ADC1 Volume':1:100
EndSequence

DisableSequence
'SLIM TX7 MUX':0:ZERO
'DEC7 MUX':0:ZERO
'SLIM TX8 MUX':0:ZERO
'DEC3 MUX':0:ZERO
'ADC3 Volume':1:0
'ADC1 Volume':1:0
EndSequence

ACDBID 545:2

into this

SectionDevice
Name "Camcorder Stereo"
Comment "Dual MIC recording device"

EnableSequence
'SLIM_0_TX Channels':0: One
'SLIM TX7 MUX':0:DEC7
'DEC7 MUX':0:ADC1
'DEC7 Volume':1:85
'ADC1 Volume':1:100
EndSequence

DisableSequence
'SLIM TX7 MUX':0:ZERO
'DEC7 MUX':0:ZERO
'ADC1 Volume':1:0
EndSequence

ACDBID 528:2

For some unknown reason, code line ''''SLIM_0_TX Channels':0: One'' is not displayed correctly inside the wrap code tags. So you need to move the word 'One' one space to the left to get the correct code line.

If you don't want to manually change code lines, you can download the whole file from these links

https://drive.google.com/file/d/0B0fm48_gHjlYTl9FT21ZTGxzZkU/view?usp=sharing

https://mega.nz/#!VwcyyBya!EmkmzPx2w2vWMMldFWNfjO4A4dIPO0U8KIwB7_tHtZU

and replace them with the existing file at the location system/etc/snd_soc_msm.

I hope this has been helpful. :)