Database Develop

WM6 in all lenguages!! WM6 en cualquier idioma!

SPANISH:
Hola tras mucho buscar y buscar e intentar cocinar una rom ... con resultados desastrosos e encontrodao la manera de poner traducir tu wm6 a cualquier idioma !!! es muy muy facil comenzamos!:
-Comenzamos descargando los siguientes programas:
Real VGA
http://forum.xda-developers.com/attachment.php?attachmentid=50575&d=1189773218
Respack128dpi
http://forum.xda-developers.com/attachment.php?attachmentid=50576&d=1189773643
y por ultimo el paquete de idomas que deses:
Español:
http://forum.xda-developers.com/attachment.php?attachmentid=49497&d=1189070923
Frances:
http://forum.xda-developers.com/attachment.php?attachmentid=49498&d=1189070962
Aleman:
http://forum.xda-developers.com/attachment.php?attachmentid=49500&d=1189070999
Ruso:
http://forum.xda-developers.com/attachment.php?attachmentid=49502&d=1189071063
Noruego:
http://forum.xda-developers.com/attachment.php?attachmentid=49501&d=1189071034
Para comenzar la instalacion instalamos primero el Real VGA seguidamente instalamos el respack128dpi y a continuacion el pack de idiomas que hallamos descargado una vez hallamos instalado todo solo tendremos que ir a START> PROGRAMS>REAL VGA y selecionar el pack 128dpi y el idioma que hallas selecionado y presionar OK! se reseteara y ya tendras tu Treo 750 en castellano casi totalmente!!! excpto el menu de la camara y de llamada!!
Informacion sacada del post de tobias.waldvogel Thanks!!
ENGLISH:
Hello after looking for much and looking for and to try to cook a ROM… with disastrous results and encontrodao the way to put to translate your wm6 to any language! it is very very easy we began:
- We began downloading the following programs:
Real VGA
http://forum.xda-developers.com/attachment.php?attachmentid=50575&d=1189773218
Respack128dpi
http://forum.xda-developers.com/attachment.php?attachmentid=50576&d=1189773643
and finally the deses package of idomas that:
Spanish:
http://forum.xda-developers.com/attachment.php?attachmentid=49497&d=1189070923
French:
http://forum.xda-developers.com/attachment.php?attachmentid=49498&d=1189070962
German:
http://forum.xda-developers.com/attachment.php?attachmentid=49500&d=1189070999
Russian:
http://forum.xda-developers.com/attachment.php?attachmentid=49502&d=1189071063
Norwegian:
http://forum.xda-developers.com/attachment.php?attachmentid=49501&d=1189071034
In order to begin the installation we installed the first Real VGA next we installed respack128dpi and next pack of languages that we found unloaded once we found installed all single one we will have to go to START> PROGRAMS>REAL VGA and to selecionar pack 128dpi and the language that you find selecionado and to press OK! reseteara and already tendras your Treo 750 in Castilian almost totally! excpto the menu of the camera and call!
Information removed from post of tobias.waldvogel Thanks!

English please?

Looks like het found a dictionary for different languages on WM6

The title sounds promissing, but no Dutch...

and italian is not possible????

All languages but not Italian ???

in which firmware version I can use Russian LangPackRUS.ARM.CAB.zip ?

dont do it!!!! because no sound in incoming calls,
if you use this programs, you have to uninstall this programs and a hard reset
i warn you.....

[rom][SPA][01-01-2010] HD fussion peterking edition WM6.5 21887 MANILA 2.5 [fast rom]

(01-01-2010) FUSSION PETERKING ROM EDITION (VERSION RECOMMENDED 100%)
CHANGES:
21,887 SYS XIP
MANILA AND OPTIMIZED BY THE COOK 2.5.19222911.0, XD, unblinking OF DOCUMENTS OR LANDSCAPE.
2.02 LEO ENTERTAINMENT PACKAGES
CLIMATE FASTER
PRESET INSTALLED:
CLEAR RAM
APAGAR FUSSION
JAVA
HD TWEAK
G-CONFIG
Gps TOOL
OBEX INBOX
OPERA MINI 5
POCKET RAR
Ppc PIM BACKUP
REG EDIT
SMART LOOCK
ACCESO WIFI BLUETOOTH
VIA RAPIDA
Cab CIUDADES WEATHER
ANDROKKID
TASKBAR BW
ASSASING CREEAD
COREPLAYER
OPERA MOBILE 10
SHOWCASE RC3
PRESET USING INSTALLER:
1.-capeta copy the software to the sd.
2.-open the folder expand
3.-clicking on Preset Installer
4.-we give below the list until soft .
5.-punctured all that interests us and we give the following configuration 6.-store if we are ready
7.-install and you can also include placing them in extended cabs vuestos \ setups \ folder name \ your soft
(01-01-2010) ROM FUSSION PETERKING EDITION (VERSIÓN RECOMENDADA 100%)
CAMBIOS:
SYS Y XIP 21887
MANILA 2.5.19222911.0 OPTIMIZADO POR EL COCINERO,XD, SIN PESTAÑA DE DOCUMENTOS NI LANDSCAPE.
PAQUETES DE LEO 2.02
ANIMACIONES DEL CLIMA RAPIDAS
DRIVERS ACELERADORES 3D NUEVOS
ELIMINADO Y INSTALABLE POR PRESET INSTALLER:
CLEAR RAM
APAGAR FUSSION
JAVA
HD TWEAK
G-CONFIG
Gps TOOL
OBEX INBOX
OPERA MINI 5
POCKET RAR
Ppc PIM BACKUP
REG EDIT
SMART LOOCK
ACCESO WIFI BLUETOOTH
VIA RAPIDA
Cab CIUDADES WEATHER
ANDROKKID
TASKBAR BW
ASSASING CREEAD
COREPLAYER
OPERA MOBILE 10
SHOWCASE RC3
UTILIZACION DE PRESET INSTALLER:
1.-copiamos la capeta software a la sd.
2.-abrimos la carpeta extendir
3.-pinchamos en Preset Installer
4.-le damos a siguiente hasta que aparezca la lista de soft.
5.-pinchamos todo lo que nos interese y le damos a siguiente
6.-guardamos la configuracion si queremos y a instalar
7.-listo
Tambien podeis incluir vuestos cabs colocandolos en extendir\setups\nombre carpeta\vuestro soft
MAS INFO Y DESCARGA DE LA ROM:
AQUI​

woha great a new chief!
downloading now

thanks, I hope your impressions

peterking said:
thanks, I hope your impressions
Click to expand...
Click to collapse
primero que nada saludos, para mi es muy agradable ver como se expande su cocina te deseo exito en xda felicitacione de la rom te puedo decir que esta a la altura.
first of all greetings to me is very nice to see it expand your kitchen you desire success in the greeting xda rom I can tell you this to height,

Hi Peter, nice to find you here.
Probably the best rom for hd never cookek, fast and solid as a rock.
Thanks for your job.

Really great rom!!!!!!!!!! Congratulations!!!!!!

What is the language of this RoM. Is it in English too, or just Spanish?

Problema con Bluetooth
Tengo un problema con mi dispositivo bluetooh (JABRA). Una vez hecha la sincronizacion el dispositivo fucniona muy bien puedo llamar y todo sonido es reproducido por los parlantes del dispositivo bluetooth. Sin embargo cuando se desconecta y conecta nuevamente, el dispositivo funciona solo para enviar y recibir llamadas, pero la parte de la reporduccion por los parlantes del dispositivo no funciona. Para que funcione debo emparejar de nuevo el dispositivo o desactivar desde el htc los servicios del auricular y llamadas y activarlas de nuevo.
Gracias por su ayuda

Only SPA version, or i can switch to ENG ?

Kernel HUAWEI P8

Buongiorno
Per curiosita sto tentando di compilare il kernel per il dispositivo GRA-L09.
Qui ho preso i sorgenti: h##p://emui.huawei.com/en/plugin.php?id=hwdownload&mod=detail&mid=90
ma riscontro qualche piccola difficolta
1) il comando adb pull /proc/config.z non produce nessun effetto
2) cerco di recuperare il config dal produttore quindi vado in /arch/arm/config ma non trovo o meglio dire non sono in grado di stabilire quale defconfig faccia al mio caso.
qualcuno gentilmente puo darmi un piccolo aiuto???
grazie
saluti
Good Morning
Out of curiosity I'm trying to compile the kernel for the device GRA-L09.
Here I took the source: h ## p: //emui.huawei.com/en/plugin.php? Id = hwdownload & mod = detail & mid = 90
but finding some little difficulty
1) the command adb pull /proc/config.z no effect
2) I try to recover the config from the manufacturer so I go in / arch / arm / config but can not find, or rather, are not able to determine which defconfig face to my case.
can someone kindly give me a little help ???
thank you
Greetings

Hi lello,
did you have any luck compiling the kernel? I'd like to do it too

lello22 said:
Buongiorno
Per curiosita sto tentando di compilare il kernel per il dispositivo GRA-L09.
Qui ho preso i sorgenti: h##p://emui.huawei.com/en/plugin.php?id=hwdownload&mod=detail&mid=90
ma riscontro qualche piccola difficolta
1) il comando adb pull /proc/config.z non produce nessun effetto
2) cerco di recuperare il config dal produttore quindi vado in /arch/arm/config ma non trovo o meglio dire non sono in grado di stabilire quale defconfig faccia al mio caso.
qualcuno gentilmente puo darmi un piccolo aiuto???
grazie
saluti
Good Morning
Out of curiosity I'm trying to compile the kernel for the device GRA-L09.
Here I took the source: h ## p: //emui.huawei.com/en/plugin.php? Id = hwdownload & mod = detail & mid = 90
but finding some little difficulty
1) the command adb pull /proc/config.z no effect
2) I try to recover the config from the manufacturer so I go in / arch / arm / config but can not find, or rather, are not able to determine which defconfig face to my case.
can someone kindly give me a little help ???
thank you
Greetings
Click to expand...
Click to collapse
Ho avuto il tuo stesso problema: il file /proc/config.gz è prodotto durante la compilazione del codice sorgente solo se l'opzione CONFIG_IKCONFIG_PROC è abilitata nel defconfig utilizzato. Potresti dirmi quale kernel stai cercando di configurare? In genere da qualche parte nel codice sorgente dovrebbe esserci un file BoardConfig.mk nel quale l'opzione CONFIG_TARGET dovrebbe puntare al defconfig utilizzato. Quanti e quali defconfig ci sono un /arch/arm/configs?
I had your same problem: the file /proc/config.gz is produced during the source code compilation only if the option CONFIG_IKCONFIG_PROC is enabled in the defconfig file used. May you tell me what kernel are you trying to configure,/ROM to build? Generally there should be a BoardConfig.Mk file in the source tree that under the option CONFIG_TARGET should address to the defconfig which is being used. How many and what kind of defconfig files are under /arch/arm/configs?
Ciuffy's SM-G900F CM 12.1 spirit hath marked this way.

Ciuffy said:
Ho avuto il tuo stesso problema: il file /proc/config.gz è prodotto durante la compilazione del codice sorgente solo se l'opzione CONFIG_IKCONFIG_PROC è abilitata nel defconfig utilizzato. Potresti dirmi quale kernel stai cercando di configurare? In genere da qualche parte nel codice sorgente dovrebbe esserci un file BoardConfig.mk nel quale l'opzione CONFIG_TARGET dovrebbe puntare al defconfig utilizzato. Quanti e quali defconfig ci sono un /arch/arm/configs?
I had your same problem: the file /proc/config.gz is produced during the source code compilation only if the option CONFIG_IKCONFIG_PROC is enabled in the defconfig file used. May you tell me what kernel are you trying to configure,/ROM to build? Generally there should be a BoardConfig.Mk file in the source tree that under the option CONFIG_TARGET should address to the defconfig which is being used. How many and what kind of defconfig files are under /arch/arm/configs?
Ciuffy's SM-G900F CM 12.1 spirit hath marked this way.
Click to expand...
Click to collapse
Buongiorno Ciuffy
in /arch/arm/configs trovo:
HTML:
kernel/arch/arm/configs/debug
kernel/arch/arm/configs/acs5k_defconfig
kernel/arch/arm/configs/acs5k_tiny_defconfig
kernel/arch/arm/configs/ag5evm_defconfig
kernel/arch/arm/configs/am200epdkit_defconfig
kernel/arch/arm/configs/ap4evb_defconfig
kernel/arch/arm/configs/ape6evm_defconfig
kernel/arch/arm/configs/armadillo800eva_defconfig
kernel/arch/arm/configs/assabet_defconfig
kernel/arch/arm/configs/at91_dt_defconfig
kernel/arch/arm/configs/at91rm9200_defconfig
kernel/arch/arm/configs/at91sam9g20_defconfig
kernel/arch/arm/configs/at91sam9g45_defconfig
kernel/arch/arm/configs/at91sam9rl_defconfig
kernel/arch/arm/configs/at91sam9260_defconfig
kernel/arch/arm/configs/at91sam9261_defconfig
kernel/arch/arm/configs/at91sam9263_defconfig
kernel/arch/arm/configs/at91x40_defconfig
kernel/arch/arm/configs/badge4_defconfig
kernel/arch/arm/configs/bcm2835_defconfig
kernel/arch/arm/configs/bcm_defconfig
kernel/arch/arm/configs/bockw_defconfig
kernel/arch/arm/configs/bonito_defconfig
kernel/arch/arm/configs/cerfcube_defconfig
/kernel/arch/arm/configs/clps711x_defconfig
kernel/arch/arm/configs/cm_x2xx_defconfig
kernel/arch/arm/configs/cm_x300_defconfig
kernel/arch/arm/configs/cns3420vb_defconfig
kernel/arch/arm/configs/colibri_pxa270_defconfig
kernel/arch/arm/configs/colibri_pxa300_defconfig
kernel/arch/arm/configs/collie_defconfig
kernel/arch/arm/configs/corgi_defconfig
kernel/arch/arm/configs/da8xx_omapl_defconfig
kernel/arch/arm/configs/davinci_all_defconfig
kernel/arch/arm/configs/dove_defconfig
kernel/arch/arm/configs/ebsa110_defconfig
kernel/arch/arm/configs/em_x270_defconfig
kernel/arch/arm/configs/ep93xx_defconfig
kernel/arch/arm/configs/eseries_pxa_defconfig
kernel/arch/arm/configs/exynos4_defconfig
kernel/arch/arm/configs/exynos_defconfig
kernel/arch/arm/configs/ezx_defconfig
kernel/arch/arm/configs/footbridge_defconfig
kernel/arch/arm/configs/h3600_defconfig
kernel/arch/arm/configs/h5000_defconfig
kernel/arch/arm/configs/hackkit_defconfig
kernel/arch/arm/configs/hisi_3630_defconfig
kernel/arch/arm/configs/hisi_3630emulator_defconfig
kernel/arch/arm/configs/hisi_3630fpga_defconfig
kernel/arch/arm/configs/hisi_3630_suspend_debug_defconfig
kernel/arch/arm/configs/hisi_hi6210oem_defconfig
kernel/arch/arm/configs/hisi_hi6210sft_defconfig
kernel/arch/arm/configs/hisi_hi6620oem_defconfig
kernel/arch/arm/configs/hs_defconfig
kernel/arch/arm/configs/imote2_defconfig
kernel/arch/arm/configs/imx_v4_v5_defconfig
kernel/arch/arm/configs/imx_v6_v7_defconfig
/kernel/arch/arm/configs/integrator_defconfig
kernel/arch/arm/configs/iop13xx_defconfig
kernel/arch/arm/configs/iop32x_defconfig
kernel/arch/arm/configs/iop33x_defconfig
kernel/arch/arm/configs/ixp4xx_defconfig
kernel/arch/arm/configs/jornada720_defconfig
kernel/arch/arm/configs/kirkwood_defconfig
kernel/arch/arm/configs/kota2_defconfig
kernel/arch/arm/configs/ks8695_defconfig
kernel/arch/arm/configs/kzm9d_defconfig
kernel/arch/arm/configs/kzm9g_defconfig
kernel/arch/arm/configs/lart_defconfig
kernel/arch/arm/configs/lpc32xx_defconfig
kernel/arch/arm/configs/lpd270_defconfig
kernel/arch/arm/configs/lubbock_defconfig
kernel/arch/arm/configs/mackerel_defconfig
kernel/arch/arm/configs/magician_defconfig
kernel/arch/arm/configs/mainstone_defconfig
kernel/arch/arm/configs/marzen_defconfig
kernel/arch/arm/configs/mini2440_defconfig
kernel/arch/arm/configs/mmp2_defconfig
kernel/arch/arm/configs/msm_defconfig
kernel/arch/arm/configs/multi_v7_defconfig
kernel/arch/arm/configs/mv78xx0_defconfig
kernel/arch/arm/configs/mvebu_defconfig
kernel/arch/arm/configs/mxs_defconfig
kernel/arch/arm/configs/neponset_defconfig
kernel/arch/arm/configs/netwinder_defconfig
kernel/arch/arm/configs/netx_defconfig
kernel/arch/arm/configs/nhk8815_defconfig
kernel/arch/arm/configs/nuc910_defconfig
kernel/arch/arm/configs/nuc950_defconfig
kernel/arch/arm/configs/nuc960_defconfig
kernel/arch/arm/configs/omap1_defconfig
kernel/arch/arm/configs/omap2plus_defconfig
kernel/arch/arm/configs/orion5x_defconfig
kernel/arch/arm/configs/palmz72_defconfig
kernel/arch/arm/configs/pcm027_defconfig
kernel/arch/arm/configs/pleb_defconfig
kernel/arch/arm/configs/prima2_defconfig
kernel/arch/arm/configs/pxa3xx_defconfig
kernel/arch/arm/configs/pxa168_defconfig
kernel/arch/arm/configs/pxa255-idp_defconfig
kernel/arch/arm/configs/pxa910_defconfig
kernel/arch/arm/configs/raumfeld_defconfig
kernel/arch/arm/configs/realview_defconfig
kernel/arch/arm/configs/realview-smp_defconfig
kernel/arch/arm/configs/rpc_defconfig
kernel/arch/arm/configs/s3c2410_defconfig
kernel/arch/arm/configs/s3c6400_defconfig
kernel/arch/arm/configs/s5p64x0_defconfig
kernel/arch/arm/configs/s5pc100_defconfig
kernel/arch/arm/configs/s5pv210_defconfig
kernel/arch/arm/configs/sama5_defconfig
kernel/arch/arm/configs/shannon_defconfig
kernel/arch/arm/configs/shark_defconfig
kernel/arch/arm/configs/simpad_defconfig
kernel/arch/arm/configs/socfpga_defconfig
kernel/arch/arm/configs/spear3xx_defconfig
kernel/arch/arm/configs/spear6xx_defconfig
kernel/arch/arm/configs/spear13xx_defconfig
kernel/arch/arm/configs/spitz_defconfig
kernel/arch/arm/configs/tct_hammer_defconfig
kernel/arch/arm/configs/tegra_defconfig
kernel/arch/arm/configs/trizeps4_defconfig
kernel/arch/arm/configs/u300_defconfig
kernel/arch/arm/configs/u8500_defconfig
kernel/arch/arm/configs/versatile_defconfig
kernel/arch/arm/configs/vexpress_defconfig
kernel/arch/arm/configs/viper_defconfig
kernel/arch/arm/configs/xcep_defconfig
kernel/arch/arm/configs/zeus_defconfig
per quanto riguarda il kernel : h##p://emui.huawei.com/en/plugin.php?id=hwdownload&mod=detail&mid=90

@lello22
Buongiorno Ciuffy
in /arch/arm/configs trovo:
defconfig files...
per quanto riguarda il kernel : h##p://emui.huawei.com/en/plugin.php?id=hwdownload&mod=detail&mid=90
Click to expand...
Click to collapse
Grazie, ho scaricato il codice sorgente del kernel. Guardando in giro tra i file ho trovato in /kernel/Android.mk (il file che viene utilizzato per settare la configurazione durante la compilazione) queste righe://
Thanks, I downloaded the source code of the kernel. By having a look around at the files I first found in /kernel/Android.mk (the file which is being used to set up the make configuration for android building) these lines:
Code:
+mkdir -p $(KERNEL_OUT)
$(MAKE) -C kernel O=../$(KERNEL_OUT) ARCH=$(KERNEL_ARCH_PREFIX) CROSS_COMPILE=$(CROSS_COMPILE_PREFIX) hisi_$(TARGET_PRODUCT)_defconfig
+rm -frv $(KERNEL_GEN_CONFIG_PATH)
Queste generano il file .config utlizzato durante la compilazione da un defconfig in particolar, questo://
These basically generate the .config file to use during the building from a defconfig file. In particular, this defconfig file:
Code:
hisi_$(TARGET_PRODUCT)_defconfig
il quale nome è completo solo quando al momento della compilazione viene esportata la variabile "TARGET_PRODUCT". Ma adesso sapiamo che inizia con "hisi_", quindi è fra questi file://
which name is completed only when the environmental variable "TARGET_PRODUCT" is set. But now we know that the file starts with "hisi_", so among these there is probably going to be one which is begin used:
Code:
kernel/arch/arm/configs/hisi_3630_defconfig
kernel/arch/arm/configs/hisi_3630emulator_defconfig
kernel/arch/arm/configs/hisi_3630fpga_defconfig
kernel/arch/arm/configs/hisi_3630_suspend_debug_defconfig
kernel/arch/arm/configs/hisi_hi6210oem_defconfig
kernel/arch/arm/configs/hisi_hi6210sft_defconfig
kernel/arch/arm/configs/hisi_hi6620oem_defconfig
Forse uno di questi ti è familiare? Ancora non conosco i codename per p8.
Is any of these familiar to you? I don't know p8 codenames yet.
CI sto ancora lavorando, volevo solo farti sapere che ho trovato qualcosa://
I'm still working on it, trying to figure out where is TARGET_PRODUCT defined.
PS. Don't talk exclusively in italian.

Ciuffy said:
@lello22
Grazie, ho scaricato il codice sorgente del kernel. Guardando in giro tra i file ho trovato in /kernel/Android.mk (il file che viene utilizzato per settare la configurazione durante la compilazione) queste righe://
Thanks, I downloaded the source code of the kernel. By having a look around at the files I first found in /kernel/Android.mk (the file which is being used to set up the make configuration for android building) these lines:
Code:
+mkdir -p $(KERNEL_OUT)
$(MAKE) -C kernel O=../$(KERNEL_OUT) ARCH=$(KERNEL_ARCH_PREFIX) CROSS_COMPILE=$(CROSS_COMPILE_PREFIX) hisi_$(TARGET_PRODUCT)_defconfig
+rm -frv $(KERNEL_GEN_CONFIG_PATH)
Queste generano il file .config utlizzato durante la compilazione da un defconfig in particolar, questo://
These basically generate the .config file to use during the building from a defconfig file. In particular, this defconfig file:
Code:
hisi_$(TARGET_PRODUCT)_defconfig
il quale nome è completo solo quando al momento della compilazione viene esportata la variabile "TARGET_PRODUCT". Ma adesso sapiamo che inizia con "hisi_", quindi è fra questi file://
which name is completed only when the environmental variable "TARGET_PRODUCT" is set. But now we know that the file starts with "hisi_", so among these there is probably going to be one which is begin used:
Code:
kernel/arch/arm/configs/hisi_3630_defconfig
kernel/arch/arm/configs/hisi_3630emulator_defconfig
kernel/arch/arm/configs/hisi_3630fpga_defconfig
kernel/arch/arm/configs/hisi_3630_suspend_debug_defconfig
kernel/arch/arm/configs/hisi_hi6210oem_defconfig
kernel/arch/arm/configs/hisi_hi6210sft_defconfig
kernel/arch/arm/configs/hisi_hi6620oem_defconfig
Forse uno di questi ti è familiare? Ancora non conosco i codename per p8.
Is any of these familiar to you? I don't know p8 codenames yet.
CI sto ancora lavorando, volevo solo farti sapere che ho trovato qualcosa://
I'm still working on it, trying to figure out where is TARGET_PRODUCT defined.
PS. Don't talk exclusively in italian.
Click to expand...
Click to collapse
sono d accordo totalmente
comunque se nel web cerco hi6620oem trovo defconfig adatto a P7. Comunque ad intuito e ripeto ad intuito mi sembra questo
Non conosco nessun modo per determinare il defconfig giusto
continuo la ricerca spero con il tuo aiuto
totally I agree upon
However if the web looking hi6620oem find defconfig suitable for P7. However to insight and intuition I seem to repeat this
I know of no way to determine the right defconfig
continuous research I hope with your help
Continuous research
in ogni caso nei miei file all interno del dispositivo trovo hi3635
ed anche nei sorgenti trovo README_KERNEL.TXT :
$ mkdir ../out
$ make ARCH=arm64 O=../out merge_hi3635_defconfig
$ make ARCH=arm64 O=../out -j8
update: trovo tante altre cose che alla fine mi mandano solo in confusione

@lello22
Nel file "Makefile", il principale file al quale "make" fa riferimento, ho trovato riferimenti a questi due elementi://
In the "Makefile", the main file used by "make" during the compilation, I found some lines referring to these two elements:
Code:
hi3635_udp //used three times always to set OBB_PRODUCT_NAME, whish is referenced nine times
hi3630 //only once, to set CFG_PLATFORM, referenced five times.
Questa riga ha attirato la mia attenzione://
Then this line caught my attention:
Code:
-include $(BALONG_TOPDIR)/config/product/$(OBB_PRODUCT_NAME)/config/balong_product_config.mk
"-include" viene utilizzato solo sei volte, e solo ona per riferirsi ad un file "config.mk", che assomiglia molto al BoardConfig.mk che stavo cercando, utilizzato per compilare Cyanogenmod (ce n'è uno anche in questa sorgente, ma non so a cosa serva). Puoi trovarlo qui: kernel_huaweip8/drivers/vendor/hisi/config/product/hi3635_udp/config/balong_product_config.mk//
The "-include" is only used six times, and only one time it references a config.mk, which looks similar to the BoardConfig.mk file I was looking for, used when building Cyanogenmod (there is one in this kernel anyway, but I don't know what is it for).
You can find it here: kernel_huaweip8/drivers/vendor/hisi/config/product/hi3635_udp/config/balong_product_config.mk
Aprendo quel file, ho trovato questa riga://
Opening that file, I found this line here too:
Code:
CFG_PLATFORM :=hi3630
We got a little evidence that references to hi3630 are not an option. Then, if you look at the config files, you will find:
Code:
kernel/arch/arm/configs/hisi_3630fpga_defconfig
Cercando su google ho scoperto che "FGPA" sta per "Field Programmable Gate Array". Se cerchi su google "FPGA Huawei p8" vedrai che difficilmente Google troverà entrabmi gli elementi nei risultati, invece "FPGA Huawei p8" riporta risultati migliori. Infatti, citando un sito a caso tra questi: "FPGA è integrato nel nuovo Huawei P8 per migliorare il segnale 4G".//
Searching around on goole I found out that "FGPA" stands for "Field Programmable Gate Array". If you search for "FGPA Huawei p8", you find results that address both the elements, for example: "FGPA is intgrated in the new Huawei P8 flagship smartphone for better 4G reception".
Tutto questo per dimostrare che probabilmente il file che cerchi è kernel/arch/arm/configs/hisi_3630fpga_defconfig o kernel/arch/arm/configs/hisi_3630_defconfig. Cercando nei due file dovresti riuscire a capire quale è utilizzato per il dispositivo e quale per la tecnologia 4G.//
This is my best guess to demonstrate that the file you are looking for is either kernel/arch/arm/configs/hisi_3630fpga_defconfig or kernel/arch/arm/configs/hisi_3630_defconfig. By giving a look at the two files you might be able to recognize which is being used for the device and which might be only an external configuration for that technology.
Prova intanto, almeno andiamo per esclusione e puoi vedere se la compilazione del codice sorgente avviene senza troppi problemi. Il tuo problema è che hai un dispositivo molto all'avanguardia e non troppa gente ci ha ancora messo le mani sopra.//
Just try, at least we can exclude these two and see if the building succeeds without too many problems. Your problem is that you have a very recent device, not many people have yet tried it out or built anything for it.

Ciao Ciuffy
mentre aspettavo con ansia una tua risposta mi stavo concentrando su i due defconfig da te considerati.
In effetti trovo riscontri tra il defconfig 3630 e qualche file all interno del dispositivo.
dando un dmesg all interno del phone vedo>>>>>>hisi_hi6421v300 e sul defconfig hisi3630 vedo>>>>> HI6421V300 pmu drivers e questo mi ha fatto pensare forse ci sono inquanto su altri defconfig non trovo questo dato
Adesso c e da valutare tra:
hisi_3630_defconfig
hisi_3630fpga_defconfig
l emuletor lo escludo a priori
as I waited anxiously for your reply I was concentrating on the two defconfig you considered.
In fact I find feedback between defconfig 3630 and some files inside the device.
giving a dmesg inside the phone I see >>>>>> hisi_hi6421v300 on defconfig hisi3630 >>>>> HI6421V300 pmu drivers and this made me think maybe there are other giveaway defconfig not find this
Now there and evaluated between:
hisi_3630_defconfig
hisi_3630fpga_defconfig
the emuletor I exclude
inoltre noto che su tale defconfig è attivato, se cosi si puo dire, il governor userspace il quale puo darmi la possibilita di modificare la frequenza cpu con le apposite app
also known that on that defconfig is activated, so if you can say, the userspace governor who can give me the chance to change the CPU frequency with the appropriate app
thanks a lot
appena ho novita ti faccio sapere
I just updates to let you know

lello22 said:
Ciao Ciuffy
mentre aspettavo con ansia una tua risposta mi stavo concentrando su i due defconfig da te considerati.
In effetti trovo riscontri tra il defconfig 3630 e qualche file all interno del dispositivo.
dando un dmesg all interno del phone vedo>>>>>>hisi_hi6421v300 e sul defconfig hisi3630 vedo>>>>> HI6421V300 pmu drivers e questo mi ha fatto pensare forse ci sono inquanto su altri defconfig non trovo questo dato
Adesso c e da valutare tra:
hisi_3630_defconfig
hisi_3630fpga_defconfig
l emuletor lo escludo a priori
as I waited anxiously for your reply I was concentrating on the two defconfig you considered.
In fact I find feedback between defconfig 3630 and some files inside the device.
giving a dmesg inside the phone I see >>>>>> hisi_hi6421v300 on defconfig hisi3630 >>>>> HI6421V300 pmu drivers and this made me think maybe there are other giveaway defconfig not find this
Now there and evaluated between:
hisi_3630_defconfig
hisi_3630fpga_defconfig
the emuletor I exclude
inoltre noto che su tale defconfig è attivato, se cosi si puo dire, il governor userspace il quale puo darmi la possibilita di modificare la frequenza cpu con le apposite app
also known that on that defconfig is activated, so if you can say, the userspace governor who can give me the chance to change the CPU frequency with the appropriate app
thanks a lot
appena ho novita ti faccio sapere
I just updates to let you know
Click to expand...
Click to collapse
As a further help, here it is a comparision of the two files.

Complimenti lavoro a dir poco stupendo
Tornando a noi direi che il defconfig da usare è il hisi_3630_defconfig
deduzione data da questa differenza:
CONFIG_NR_CPUS=8 hisi_3630_defconfig
CONFIG_NR_CPUS=1 hisi_3630fpga_defconfig
deduzione corretta?????
Congratulations for a wonderful work
the defconfig to use is the hisi_3630_defconfig
deduction given by this difference:
CONFIG_NR_CPUS = 8 hisi_3630_defconfig
CONFIG_NR_CPUS = 1 hisi_3630fpga_defconfig
correct deduction ?????

Ciao Ciuffy
quando hai tempo cortesemente puo dare uno sguardo nei sorgenti : /arch/arm64/configs
grazie
Hello Ciuffy
when you have time can kindly take a look in the source: / arch / arm64 / configs
thank you

lello22 said:
Complimenti lavoro a dir poco stupendo
Tornando a noi direi che il defconfig da usare è il hisi_3630_defconfig
deduzione data da questa differenza:
CONFIG_NR_CPUS=8 hisi_3630_defconfig
CONFIG_NR_CPUS=1 hisi_3630fpga_defconfig
deduzione corretta?????
Congratulations for a wonderful work
the defconfig to use is the hisi_3630_defconfig
deduction given by this difference:
CONFIG_NR_CPUS = 8 hisi_3630_defconfig
CONFIG_NR_CPUS = 1 hisi_3630fpga_defconfig
correct deduction ?????
Click to expand...
Click to collapse
Ho sempre pensato che fosse quello giusto perché credo che l'fpga non sia da non utilizzare completamente, ma che utilizzi per un altra parte della compilazione del codice: è presto detto, fai le tue modifiche su hisi_3630 e rinomina quello fpga in "old" ad esempio e vedi se la compilazione ritorna qualche errore! Allo stesso modo puoi andare per esclusione togliendone altri (come il balong di prima) e vedendo se riscontri errori.
I've always though that one is the right one to use because I do believe the fpga one is used for the building of another part of the source code: easy to tell, use menuconfig on hisi_3630 and rename the fpga one into "old" and see if it causes an error. Same goes for other ones like the balong from before.
Ciuffy's SM-G900F CM 12.1 spirit hath marked this way. Thank if helped your soul.
---------- Post added at 05:25 PM ---------- Previous post was at 05:22 PM ----------
lello22 said:
Ciao Ciuffy
quando hai tempo cortesemente puo dare uno sguardo nei sorgenti : /arch/arm64/configs
grazie
Hello Ciuffy
when you have time can kindly take a look in the source: / arch / arm64 / configs
thank you
Click to expand...
Click to collapse
I was thinking about that. Hisi_3635 is actually the biggest config file. Still, I haven't checked the differences yet, but I think we are going to find something interesting in there. Plus, it is the one most references in the various make files. Have you ever tried actually compiling and using one? The output might give us some clues...
Ciuffy's SM-G900F CM 12.1 spirit hath marked this way. Thank if helped your soul.

Ciao Ciuffy
provo a fare cosi:
I try to do :
1. How to Build
- get Toolchain
From android git server, codesourcery and etc ..
- aarch64-linux-android-4.9
- edit Makefile
edit "CROSS_COMPILE" to right toolchain path(You downloaded).
Ex) export PATH=$PATH:$(android platform directory you download)/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin
Ex) export CROSS_COMPILE=aarch64-linux-android-
$ mkdir ../out
$ make ARCH=arm64 O=../out merge_hi3635_defconfig
$ make ARCH=arm64 O=../out -j8
2. Output files
- Kernel : out/arch/arm64/boot/Image
- module : out/drivers/*/*.ko
3. How to Clean
$ make ARCH=arm64 distclean
$ rm -rf out
che non è altro il file README_kernel.txt nella cartella kernel sorgenti
this is the file text README_kernel.txt in the file folder kernel sources

lello22 said:
Ciao Ciuffy
provo a fare cosi:
I try to do :
1. How to Build
- get Toolchain
From android git server, codesourcery and etc ..
- aarch64-linux-android-4.9
- edit Makefile
edit "CROSS_COMPILE" to right toolchain path(You downloaded).
Ex) export PATH=$PATH:$(android platform directory you download)/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin
Ex) export CROSS_COMPILE=aarch64-linux-android-
$ mkdir ../out
$ make ARCH=arm64 O=../out merge_hi3635_defconfig
$ make ARCH=arm64 O=../out -j8
2. Output files
- Kernel : out/arch/arm64/boot/Image
- module : out/drivers/*/*.ko
3. How to Clean
$ make ARCH=arm64 distclean
$ rm -rf out
che non è altro il file README_kernel.txt nella cartella kernel sorgenti
this is the file text README_kernel.txt in the file folder kernel sources
Click to expand...
Click to collapse
È probabile che abbia sottovalutato un particolare//
I think I may overlooked a particular.
"Make filename_defconfig"
Genera sempre un file .config dal defconfig. A questo punto sono abbastanza sicuro che la configurazione principale, quella che vuoi modificare, sia "/arch/arm64/configs/merge_hi3635_defconfig".//
Always generates a .config file
At this point, I'm pretty sure that the main configuration, the one you want to edit, is "merge_hi3635_defconfig" under /arch/arm64/configs.
Sto cercando ulteriore conferma, ma penso che questa sia la soluzione finale. Scusa per averlo sottovalutato.//
Looking for more evidence right now, but I guess this is the final answer. Sorry for overlooking.
Edit: 90 kB, actually the average size for a legit defconfig, finally.
Ciuffy's SM-G900F CM 12.1 spirit hath marked this way. Thank if helped your soul.

In effetti se si cerca in google hi3635 si trova Hisilikon kirin 930 che corrisponde al processore del dispositivo
if you search in google hi3635 is Hisilikon kirin 930 that corresponds to the device's processor

lello22 said:
In effetti se si cerca in google hi3635 si trova Hisilikon kirin 930 che corrisponde al processore del dispositivo
if you search in google hi3635 is Hisilikon kirin 930 that corresponds to the device's processor
Click to expand...
Click to collapse
Esatto, hi e hisi stanno per Hisilikon, interamente posseduta da Huawei.
Exactly, hi and hisi stand for Hisilikon, by Huawei.
Ciuffy's SM-G900F CM 12.1 spirit hath marked this way. Thank if helped your soul.

Bene le sorgenti sono state compilate prendendo in considerazione il file hisi_3635_defconfig e non modificando nulla
Non ho dato menuconfig quindi ho compilato senza modificare nulla per verificare la compilazione.
A prima vista tutto è andato bene
- Kernel : out/arch/arm64/boot/Image>>>>>>>>>>>>>>>>>>>in effetti qui trovo un file eseguibile di nome image ed image.gz
- module : out/drivers/*/*.ko>>>>>>>>>>>>>>>>>>>>>>>>>>> sto verificando!!!!!!!!!!!!!!!!
Good sources were compiled taking into account the file hisi_3635_defconfig and do nothing to change
I did not give menuconfig so I compiled without changing anything to verify the compilation.
At first all went well
- Kernel: out / arch / arm64 / boot / Image >>>>>>>>>>>>>>>>>>> actually here I find an executable file name image and file image.gz
- Module: out / drivers / * / *. Ko >>>>>>>>>>>>>>>>>>>>>>>>>>> I am checking !!!!!!!!! !!!!!!!
update:
out/drivers/ modules.builtin and modules.order

Ciuffy non credo sia finita qua, inoltre ho qualche dubbio
quando hai tempo prova a dare un occhiata al file README_version.txt nei sorgenti.
ciao
Ciuffy i think it's no closed here, I also have some doubts
when you have time try to take a look at the files in the source README_version.txt.
Hello

Buongiorno
come mai non mi si è formato un file zimage ma solamente un file image.gz ???
è la stessa cosa???
Good Morning
why no formed a file zimage but only one file image.gz ???
it's the same thing???

lello22 said:
Buongiorno
come mai non mi si è formato un file zimage ma solamente un file image.gz ???
è la stessa cosa???
Good Morning
why no formed a file zimage but only one file image.gz ???
it's the same thing???
Click to expand...
Click to collapse
Purtroppo non ho provato a compilarlo ancora, oggi lo farò. Puoi dirmi la grandezza del file e il contenuto?
Unfortunately I haven't tried to compile it yet, I'll do it today. Can you tell me the size and contents of that file?
Ciuffy's SM-G900F CM 12.1 spirit hath marked this way. Thank if helped your soul.

Problema en whatsapp, trouble on whatsapp

Mi problema es que con las siguientes rom cyanogenmods: guatum, cyanhacker no recuerdo cual otra (perdón si los nombres no están bien escritos) el problema es que cuando alquien o yo llamo a alguien por whatsapp, la persona con la que estoy hablando me escucha pero esa persona no a mi. Yo quiero saber como solucionar eso o si hay alguna cyanogenmod 100% confiafle y estable en la que no suceda eso. Gracias!!! My problem is that rom cyanogenmods the following: guatum, cyanhacker not remember which other (sorry if names are not well written) the problem is that when someone or I call someone for whatsapp, the person I'm talking about listening but that person is not me. I want to know how to fix it or if any cyanogenmod 100% confiafle and stable in that it does not happen. Thank You !!!

wilo02 said:
Mi problema es que con las siguientes rom cyanogenmods: guatum, cyanhacker no recuerdo cual otra (perdón si los nombres no están bien escritos) el problema es que cuando alquien o yo llamo a alguien por whatsapp, la persona con la que estoy hablando me escucha pero esa persona no a mi. Yo quiero saber como solucionar eso o si hay alguna cyanogenmod 100% confiafle y estable en la que no suceda eso. Gracias!!! My problem is that rom cyanogenmods the following: guatum, cyanhacker not remember which other (sorry if names are not well written) the problem is that when someone or I call someone for whatsapp, the person I'm talking about listening but that person is not me. I want to know how to fix it or if any cyanogenmod 100% confiafle and stable in that it does not happen. Thank You !!!
Click to expand...
Click to collapse
There is a fix in most threads, you just need to change a few lines on the build.prop.

FreedFromDeath said:
There is a fix in most threads, you just need to change a few lines on the build.prop.
Click to expand...
Click to collapse
which build lines of pro ?, and if you know of a video that help me.

wilo02 said:
which build lines of pro ?, and if you know of a video that help me.
Click to expand...
Click to collapse
Use the search function. It's not that hard.

Use any build prop editor
http://forum.xda-developers.com/showthread.php?t=3064132

Hola

Gracias por aceptar mi solicitud.
Seguro que aprenderé mucho con vosotros, y quizás pueda aportar algún granito de arena.
Un Saludo para todos

Fran1955 said:
Gracias por aceptar mi solicitud.
Seguro que aprenderé mucho con vosotros, y quizás pueda aportar algún granito de arena.
Un Saludo para todos
Click to expand...
Click to collapse
Translated by GT:
Thanks for accepting my request.
I'm sure I'll learn a lot with you, and maybe I can contribute a bit.
Greetings to all
Greetings, and welcome to XDA. We hope you find what you're looking for, and please post in English as per XDA Rule #4.
Cheers, and have a great day.