yashsingh1/xdaforums huggingface dataset:
[LG G2 Mini] invaderjohn:
thx for the info. i think most of it is used allready

il have a bit closer look asap

https://github.com/G2Mini-DevTeam

this is the github we are using. for now its a bit messy though since we just started with getting this for other g2mini devices also making common repo and such

our device d620 is g2m, the g2mss is the d610

seems like g2m uses msm8926 but msm8226 as board. so yeah i find it a bit messy with the dts files since i dont really know where to point the mktbootimg.

like, the l90 w7 sources wich use msm8226 worked on our phone with som minor mods. but some stuff didnt quite work as u know. and theres i think where the msm8926 "addon" comes in right?

and there is no include/hardware/ in the kernel source :/
[LG G2 Mini] :
hey hey,

okay, will look through it,

Not in kernel source, in your device tree, you can, if you haven't, establish and include directory for device specific headers

meaning

$TOP/device/lge/toaster/include/blah_blah.h

and to grab it during build, in boardconfig.mk

define your local path with example;

LOCAL_PATH := device/lge/toaster

TARGET_SPECIFIC_HEADER_PATH := $(LOCAL_PATH)/include

m
[LG G2 Mini] invaderjohn:
Oh OK cool :)

Well the file isnt in device tre either. Maybe its something to be added. But the w7 doesnt have any vibrator extension wich is a very similar phone
[LG G2 Mini] siracuervo:
Where did you see that?
[LG G2 Mini] :
okay,

android_device_lge_g2m/cm-12/BoardConfig.mk points to msm8226 except for

G2MINI_DTS_TARGET := msm8926-g2m_global_com

in android_device_lge_g2m/system.prop, you may need the following,

ro.product.board=MSM8???

ro.board.platform=msm8???

android_device_lge_g2mini-common/cm-12/mkbootimg.mk points to msm8226

MSM8226_DTS_NAMES := MSM8226

MSM8226_DTS_FILES = $(wildcard $(TOP)/$(TARGET_KERNEL_SOURCE)/arch/arm/boot/dts/$(G2MINI_DTS_TARGET)/*.dts)
MSM8226_DTS_FILE = $(lastword $(subst /, ,$(1)))
DTB_FILE = $(addprefix $(KERNEL_OUT)/arch/arm/boot/,$(patsubst %.dts,%.dtb,$(call MSM8226_DTS_FILE,$(1))))
ZIMG_FILE = $(addprefix $(KERNEL_OUT)/arch/arm/boot/,$(patsubst %.dts,%-zImage,$(call MSM8226_DTS_FILE,$(1))))

i won't quote the whole file but you get the idea, if incorrect you can use find and replace in text editor [all at once] to replace 8226 with correct

and according to your vendor sources your device is msm8226, with the binaries/libraries being what they are

you may be able to rename them to make the fit

meaning for android_vendor_lge_g2m/proprietary/vendor/lib/hw/power.msm8226.so <----rename---->power.msm8???.so

??? being whatever msm common source you're pointing to.

alternately for that last one you can utilize a symlinking event in your updater script to create a symlink power.msm8???.so <----which points to ----> power.msm8226.so

on the vibrator, try my suggestion, we're kinda winging it on that for now, check your stock boot.img *.rc's for VIBETONEZ entries to see if you are missing a proprietary binary, if you are manually include it your vendor resource, the script doesn't get everything most of the time.

if you are indedd missing a binary, or library run strings for the binary/library in terminal to find out what other files [bin/lib] you need

strings <name of file> | grep "\.so" to find out what other libraries you may need that ARE NOT standard android

strings <name of file> | grep "bin/" to find out what binaries you may need that ARE NOT standard android

that's pretty much what i could see, hope it helps guys. :good:

m

---------- Post added at 04:35 PM ---------- Previous post was at 04:25 PM ----------

S,

hi, i'm just providing a generic example that may effect a possible solution. :good:

m
[LG G2 Mini] partyzant_x:
Old boot.img from what source? Zaaap72? His source is from Quarx2k and this is caf patched kernel. You dont have to add any caf to cm12 only to kernel. [MENTION=5864662]moonbutt74[/MENTION]

Our vibrator is immvibe immersive. Is tspdrv in kernel source and there is some libs for that on stock.
[LG G2 Mini] invaderjohn:
From bigmajsters kernel source wich i modified to work with our device. And if vibration is libs then we should be able to use his kernel source?
[LG G2 Mini] partyzant_x:
And he had source from? All source for LG msm8226 is from Quarx2k. Anybody simply fork his work on GitHub and modified for personal use. But this is Quarx2k kernel and this is caf.

You guys dont listen me. I told a while ago that is wrong defconfig and source. But if you know better then good luck.
[LG G2 Mini] invaderjohn:
Yeah i know its a big mess for me. I cant figure out weather it uses msm8226 or msm8926
[LG G2 Mini] :
According to the vendor sources you need msm8226,

now, some kernel sources using variant defconfigs

call for additional settings/code specific to msm8974,8926 etc

but your board is still msm8226.

goto your vendor/<device> /proprietary/vendor and search the directory using the term power

in ib/hw/ you will find power.msm8226.so , so board=msm8226.

m
[LG G2 Mini] partyzant_x:
@up

msm8226 and msm8926 are the same. Only different is that msm8926 has LTE. And LG D620 is msm8926.
[LG G2 Mini] :
P,

hey hey, not to drive you crazy, :silly:

can you run in terminal while on stock rom

cat /proc/cpuinfo

and then again on cm11/12 ?

thanks.

m
[LG G2 Mini] Garcia98:
Let's think a bit, MSM8926= MSM8226+LTE

LG G2 Mini D620 has LTE, so it has to be MSM8926.

BTW, what do logcats say about vibrator issue?
[LG G2 Mini] :
That may be true, however the information i am looking for is the output of

cat /proc/cpuinfo

specifically the entry for

Hardware : Qualcomm MSM 8???

;)

m
[LG G2 Mini] Garcia98:
Oh my...
[LG G2 Mini] :
HAH! that is a funny picture !

still I would like to see the output of

cat /proc/cpuinfo

;)

m
[LG G2 Mini] Garcia98:
OK, I did that joke without bad intentions, sorry if I offended you, it won't happen again.

Please look at this press release by LG about G2 Mini, where it clearly states that 3G variant uses MSM8226 and LTE variant uses MSM8926: http://www.lg.com/uk/press-release/introducing-g2-mini-lgs-first-compact-smartphone
[LG G2 Mini] :
Okay, thanks :good:

that's had me confused for a few weeks now,

the reason i asked for the output is that i have a similar issue with a device i am working on and the 3g variant

which i'm working on blind, so my revised question is this

do i build msm8226 across the board for both the wifi AND the 3g variant?

also with that portion of information from the article along with my previous posts in this thread today after scouring

the device tree for THIS project, is the dt.img setting incorrect in mkbootimg.mk 8226, meaning does the entire device configuration

need to be geared towards msm8926 [lte] or msm8226 [3g]?

I will remove my previous comment.

m

---------- Post added at 07:39 PM ---------- Previous post was at 07:37 PM ----------

hey thanks, the 8 thanks a day limit thing. :o

v3n0m93's screen output = msm8226

:good:

m
[LG G2 Mini] steffenbakke:
Just a smaller correction there is no Wi-Fi version. Its LTE(4G) and 3G this is at least for the d620-(r). Which this thread and all the development goes towards right now if you look besides the WIP with the cm 12 ROM development for d610. But if you re-read the last page or two. And pay attention to the posts saying which version of d620 uses which board it should stand clear to you.
[LG G2 Mini] partyzant_x:
Logcat from stock when launch vibrator mode. Sorry for screenshot but im on Tapatalk. Look at LGImmersionVibrator
[LG G2 Mini] invaderjohn:
But the dts in msm8226-g2m_global_com folder has the msm8226-g2m.dts wich also points to msm8226-common/msm8926.dtsi. So i still think 8226 is the one we are have to use? Cant the vibration be something that needs to be added to vendorblobs? Though it doesnt work in trwp either.

And i got LTE working on my cm12 build with some system.prop and ril patches
[LG G2 Mini] :
Missing blobs, permissions [/system/etc/permissions], service entry/settings in *.rc file ?

a device/node needs to be created for vibrator , right?
[LG G2 Mini] invaderjohn:
Yes i think so, since we still uses modified vendorblobs from l90 i think alot of firmware is loaded that we perhaps dont even need. So what we need is someone who can with rooted original rom extract the vendorblobs and have a look ?
[LG G2 Mini] partyzant_x:
When i change vendor to stock libs (replaced) there is the same result and ril not working
[LG G2 Mini] Garcia98:
But actually that's not an error I think that that is still the normal behaviour, search for an error or fatal (or even a warning) related to vibrator.

Maybe a logcat on stock ROM of vibrator would be useful.
[LG G2 Mini] partyzant_x:
This is logcat what is activated when launch vibrator mode on stock rom. I mean that is our vibrator is immvibe immersion . On cm when You add all necessary things on init.rc(permissions) there is no errors but vibrator dont work.

When i back to home will extract vendor blobs for Immvibe and post it.
[LG G2 Mini] invaderjohn:
Well guys, all of you that wants and can be a help can be a part of g2mini-devteam and commit changes to the gith!? Who wants and can be on board? For now its me and sira. And everyone will get equal cred for the release.
[LG G2 Mini] partyzant_x:
Ok.

I check /system/bin/immvibed and its required system/lib/libpparam.so
[LG G2 Mini] siracuervo:
It's required by that lib, or immvibed requires that lib
[LG G2 Mini] partyzant_x:
immvibed required that lib. In attach are second blobs with all libs that have something with vibrator or immvibe in name.

But when i check immvibed with Android_Blob_Utility its only required libpparam.so
[LG G2 Mini] siracuervo:
Okay, gonna test it later, thanks
[LG G2 Mini] Fikret488:
John have any news? There will be a new update before the new, or will it be a surprise for the new 2015 year? :)
[LG G2 Mini] partyzant_x:
Kmsg from stock rom:

<6>[ 0.760720 / 01-01 00:00:00.750] vib: sm100_probe()
<6>[ 0.760761 / 01-01 00:00:00.750] vib: sm100_parse_dt() vpwr_on:0, en_gpio:53, pwm_gpio:34, vibe_n_value:92, clk_rate:29813
<6>[ 0.760851 / 01-01 00:00:00.750] vib: sm100_probe() dev->init_name : vibrator, dev->kobj : syncoam_sm100_rev_a.74
<6>[ 0.761022 / 01-01 00:00:00.750] vib: ImmVibeSPI_ForceOut_Initialize()

And full:
[LG G2 Mini] invaderjohn:
To be honest im kinda stuck at the moment. Seems like the more i do the worse it gets. Need to figure som stuff out first. But we still working hard on it.
[LG G2 Mini] Fikret488:
Slowly look, I asked BigMajstors to help us, he is currently busy working on the kernel promised if you find some free time to help us.
[LG G2 Mini] invaderjohn:
Yeah i have a couple of people wanting to take a look. But everyone is Bush atm :/
[LG G2 Mini] invaderjohn:
look, we got a build with the original kernel.

the vibration and nfc didnt work cause of worng dts and baord files for the old builds.

and the baordfiles and dts doesnt work that well with quarx2k's kernel since it been heavely modded to work with w7 device.

so yeah got the original kernel source to build but stuck at lg bootscreen

heres a dmesg from bootup

http://pastebin.com/5WJCE0RT

seems like theres a mdss error
[LG G2 Mini] Garcia98:
If you're using stock kernel you can't use CAF variants and you have to add retire fence support in kernel, BTW, logcats provide more information for these errors
[LG G2 Mini] :
Ditto on the logcat, but i did see this;

Is this right ?

<6>[ 0.590833 / 01-01 00:00:00.580] [23620] bootmode_set_model_name: put lg_model_name LG-D620r to smem
<6>[ 0.590868 / 01-01 00:00:00.580] [23820] g_stUSD.enUpdateState = 0
<6>[ 0.590907 / 01-01 00:00:00.580] [23820] [COLOR="Red"]use_signed_kernel=0, is_unlocked=0, is_tampered=0[/COLOR].
<6>[ 0.590944 / 01-01 00:00:00.580] [23820] Loading boot image (11380736): start
<6>[ 0.590980 / 01-01 00:00:00.580] [23950] Loading boot image (11380736): done
<6>[ 0.591023 / 01-01 00:00:00.580] [23960] Using DTB entry 200/00010001/131/0 for device 200/00010001/131/0
<6>[ 0.591057 / 01-01 00:00:00.580] [23960] Secure boot started
<6>[ 0.591094 / 01-01 00:00:00.580] [23970] security_interface_command = 0x53 result = 16
<6>[ 0.591125 / 01-01 00:00:00.580] [23970] Secure boot End

I ask because earlier in the process the first boot.img test failed with security warnings

on dtb/dts/dt.img, your mkbootimg may be pointing to the wrong location of dt's

Updating device tree: start

<6>[ 0.592084 / 01-01 00:00:00.580] [23970] Could not found lcd_primary node.
<6>[ 0.592117 / 01-01 00:00:00.580] [23980] Could not found imx179 node.
<6>[ 0.592148 / 01-01 00:00:00.580] [24000] sbl_delta_time: 1000461
<6>[ 0.592178 / 01-01 00:00:00.580] [24020] lk_delta_time: 24020
<6>[ 0.592210 / 01-01 00:00:00.580] [24190] Updating device tree: done
<6>[ 0.592258 / 01-01 00:00:00.580] [24190] booting linux @ 0x8000, ramdisk @ 0x2000000 (3353221), tags/device tree @ 0x1e00000
<6>[ 0.592295 / 01-01 00:00:00.580] [24190] Turn off MIPI_VIDEO_PANEL.
<6>[ 0.592333 / 01-01 00:00:00.580] [24190] Continuous splash enabled, keeping panel alive.
<6>[ 0.592358 / 01-01 00:00:00.580]
<6>[ 0.592378 / 01-01 00:00:00.580] lge_bootlog_init: token (null)
<6>[ 0.592400 / 01-01 00:00:00.580] --------------------------------------------------------------

further along
<3>[ 0.757673 / 01-01 00:00:00.750] mdss_mdp_parse_dt_prop_len: [COLOR="Red"]Error from prop qcom,mdss-ad-off[/COLOR] : spec error in device tree

further along
<7>[ 0.886906 / 01-01 00:00:00.880] msm_vidc: 1: Failed to read qcom,load-freq-tbl from device tree
<7>[ 0.886924 / 01-01 00:00:00.880] msm_vidc: 1: no elements in frequency table
<7>[ 0.886937 / 01-01 00:00:00.880] msm_vidc: 1: Failed to read qcom,reg-presets from device tree
<7>[ 0.887017 / 01-01 00:00:00.880] msm_vidc: 1: Failed to read qcom,buffer-type-tz-usage-table from device tree

From Instructions in official kernel source , w7ds_open_cis_defconfig

so should your script be pointing to arch/arm/boot/dts/msm8226-w7ds_global_com/msm8226-w7-*.dts
[LG G2 Mini] siracuervo:
Cool get, but we aren't w7ds, we are g2m, g2mss and g2mds

---------- Post added at 02:04 AM ---------- Previous post was at 02:03 AM ----------

Unfortunately, logcat isn't working with the phone in that stage
[LG G2 Mini] :
Okay, right but i am going by official release readme, they may be general instructions.

if so then maybe,

defconfig = g2m_global_com_defconfig

and mkbootimg dts setting pointing to

arch/arm/boot/dts/msm8226-g2m_global_com/msm8226-g2m-*.dts ?

at the beginning i was using [MENTION=5156330]Garcia98[/MENTION] 's source, being unfamiliar with the device and wanted to get a kernel build through

just to see how it went. But i definitely prefer to go from the official release and patch as necessary.

Also though i'm working on a different device, it's all qcom, and i haven't had any success with any caf-new stuff.

m
[LG G2 Mini] invaderjohn:
Logcat isnt working since i cant adb in that state. Dmesg was the only thing i could get

Well since the dts is working on our phone with w7 open cis maybe i could just try to change the boardfiles? Seems like its in the boardfiles it is where i points to the right drivers for vibration and such.

And ive added a dts file in that location to point at the right dts files.

Just have a look at our github and maybe you guys can sen anything that needs to be changed
[LG G2 Mini] Garcia98:
Enable eng build to get logcat working, also you should know that using stock kernel source won't fix anything but will mess up audio
[LG G2 Mini] invaderjohn:
How come? U have any clue then what messes up the vibration and nfc? Doesnt that have to be with the baord config? Wich manage the tspdrv?
[LG G2 Mini] :
IJ,

hi, quick question, when on stock, do you see directories in root such as /firmware /firmware-modem etc, or if present

have those already been accounted for by way of symlinking? scripts may be in /system/etc.

m
[LG G2 Mini] invaderjohn:
Il check when i get home from work. I dont have stock flashed since cm11 came out but have the system.img extracted on my comp. Though i know there is alot of permissions not beeing used from stock in the cm Roms. Just need to know what files needed for vibration
[LG G2 Mini] invaderjohn:
You where right, it didnt fix anything, i have no clue what to do next. U have any idea what causes nfc and vibration not working?
[LG G2 Mini] enzo_cz:
This is gonna be a little bit off topic comment, John. I start to feel that likely you won't get the support you need as this needs someone else's help and I am not sure whether there's any dev to put hands on this. I just wish to be able to help alas I don't know enough. When CM11 was delivered on our device it did not include vibration and some minor stuff. Perhaps you can redo your initial release wirh Quarx kernel and try to optimize I/O settings and camera. Maybe worth having lollipop without vib and nfc than no lollipop? I can recall that Zaaap had the same issues when trying to use and compile stock kernel on CM11.
[LG G2 Mini] sebatox:
Btw where did Zaaap go ?
[LG G2 Mini] enzo_cz:
Private matters I think. Somewhere amongst the rows on the thread he said he needed to concentrate more on his family and this kind of stuff. But when remembering that Zaaap had as the same issues as John has to deal with now I am not sure whether Zaaap could be of any assistance. What I am sensing here is John's approach to fix the vibs and nfc but you guys were tellling that nfc can be either killed or even uninstalled, hence that is not a real bother unless any of you are a real nfc fella and I still doubt that there's a plenty of folks going for this nowadays. And no vib is an issue indeed but I am sure that we can live without it. If any of you got CM11 installed you had not vib in it and you were okay. So this way I would like just to encourage John to get the ROM stable and I would be more than happy with it. And if there's plenty of you who agree than perpahs John can feel a bit more comfortable and just fix the governors and camera (unless he alrady did) and that's it. It would be a fair compromise to me since as I fear, folks, there is no official lollipop release to come up from LG directly. So let's grasp the best option John is about to offer and that's it. By all means I'll still be obliged to him.
[LG G2 Mini] Flamestorm:
Maybe this is wrong thread but can anyone build AOSP rom from Stock ROM ?
[LG G2 Mini] Garcia98:
Any interesting logcat?
[LG G2 Mini] invaderjohn:
Nope not yet, ive got my device to boot with bigmajsters kernel with our board files and dts but that killed the sound, i think there where missing .so files in vendor for audio. By now i dont even know if g2m_global_com is the right one since vibration is kernel related and it still doesnt work. Ive added libs for camera so it should work. Ive just havnt got a good build to try it out on daylight. Would be great to have nfc working but i dont care that much about it. In the latest build from cm12 Repo it seems like the other governors are working at least for me i tried it like 30 mins. So for now im focusing on getting vibration, if the sound works on my next build and camera but not vibration i will release it. And if zaaap did as much testning as me i understand he had to set it to side. This is to much sometimes.

And if u perhaps can help me out a bit u can allways add me on hangouts. A proper defconfig and vendor should be great.
[LG G2 Mini] Garcia98:
I already knew that sound would be ****ed up using LG kernel sources, it seems that the best way is working with CAF sources (from Quarx).

For vibrator you can try this commit:

https://github.com/CyanogenMod/andr...mmit/3284936192d3782c271e1adc23eba60d6ad074fa

And for NFC these two:

https://github.com/CyanogenMod/andr...mmit/11d36a4f12fd8b9a25df1cb91760764b2d88ee56

https://github.com/CyanogenMod/andr...mmit/cf9efb1d67e9b37f62d8e829bb3a14a83b43add3

Send me a PM with your Hangouts if you want
[LG G2 Mini] invaderjohn:
well the thing is i use the source from quarx/bigmajster just chnaged the boardfiles and dts in it and defconfig, and sound stopped working

thx il have a look at those :)
[LG G2 Mini] partyzant_x:
For sound You make a look at prebuilt/etc/audio_policy.conf with some changes it can work. I had that issue with omni and add some changes to that file give me working sound. Dont remember what im change because i dont work anymore and dont have source on my laptop.
[LG G2 Mini] invaderjohn:
you dont have it on github then ?
[LG G2 Mini] partyzant_x:
No i dont sorry. But i saw that Quarx make some changes for opensource driver to sound https://github.com/Quarx2k/proprietary_vendor_lge/commit/5ed31bbbb88e5603d429d20fe76344a1d1f55cb9
[LG G2 Mini] System_F:
Now camera MUST work without overexposure :)

i used empty template (downloaded from xda) to create this zip :)

Download
[LG G2 Mini] steffenbakke:
This is the one which won't work on cm12?
[LG G2 Mini] System_F:
yeah, but it works on cm11=)
[LG G2 Mini] wooolfgang:
How do you install this? Via recovery?

Edit : flashed via recovery, still has overexposure
[LG G2 Mini] System_F:
hm, in this case i think it need to be added to ROM.zip in system/vendor/lib

replace this libmmcamera2_sensor_modules.so with this and flash the rom normally :)
[LG G2 Mini] predragiPredrag:
Did you use libs from stock rom?
[LG G2 Mini] wooolfgang:
I've replaced the file and created a new zip but it an error shows whenever I flash it
[LG G2 Mini] System_F:
nope :)

---------- Post added at 11:16 AM ---------- Previous post was at 11:15 AM ----------

later i'll upload the fixed rom... for who want it :)
[LG G2 Mini] simo14:
The fix work for camera only or for videocamera too?
[LG G2 Mini] System_F:
tried only on camera, about the videocamera i don't know.

a, yeah... i tried it on this version cm-11-20140909-UNOFFICIAL-d620

upd: so... to obtain camera without overexposure you need to flash the rom :(

Flash with wipe: cache, dalvik cache, system, data

Download

before flashing the rom

after flashing the rom :)
[LG G2 Mini] doloresmiska:
second image dont work
[LG G2 Mini] System_F:
try now
[LG G2 Mini] wooolfgang:
Thanks. I'll give feedback when I'm done flashing

Edit: cameta works without overexposure. Good job man!
[LG G2 Mini] partyzant_x:
Really!!?? My build from november 2014 had fixed camera. BTW good job.:)
[LG G2 Mini] System_F:
lol, maybe i missed that moment :D

In any case we have a working camera :D
[LG G2 Mini] wooolfgang:
My phone automatically turns on when I charge it and when the cm11 has booted the touch screen doesn't work. I have to remove the battery and turn it on again for it to work
[LG G2 Mini] Flamestorm:
Sim work and camera i can take pictures and talk to friends? :D NFC and vibration doesnt work and i dont need it :D if this are the only bugs please someone tell me.
[LG G2 Mini] enzo_cz:
Yes, these are the only bugs I am aware of plus double tap to wake. As for the camera partyzantX is right. He released a cam fix Nov commencing. I have fixed video using Crystal Pa libs that time.
[LG G2 Mini] Flamestorm:
DELETED
[LG G2 Mini] trapacska:
I cannot get out from bootloop. Any help pls? Freshly installed from TWRP and Data is formatted.

Thx
[LG G2 Mini] Fakirr1:
Sorry to write in Hungarian...

A twrp csinál furcsa dolgokat. Használd a cwm-et inkább..

Lehet,hogy a bootloadert nem nyitottad ki rendesen?

Csak ötletelek..

Prohardverre is írtál már?

Again: sorry for Hungarian answer, but my English is not so good..
[LG G2 Mini] AntonPanos:
What is going with this rom? Is in progress or aborted? :rolleyes:

EDIT: Sorry for asking here.. i forgot about Q&A section.
[LG G2 Mini] Nikita Pro Android:
If someone you this ROM please try: http://xdaforums.com/g2-mini/development/kernell-cyanogen11extended-lg-g2-mini-t3113955

I hope it works on D620 model and maybe fix problems with vibration.
[LG G2 Mini] WoytazZer CZ:
Yeah, yes it's working on CPA on my d620r great! CPU oc/uc ,NFC and vibration works! :D

Sent from my LG-D620, CPA ROM , KERNEL CM11 extended v3.1
[LG G2 Mini] Nikita Pro Android:
Thanks for testing.

NFC also works???