yashsingh1/xdaforums huggingface dataset:
[G4 Android Development] seanpr123:
Two questions.

Installed the 20161030 build on my G4 H811 after a clean wipe and format, but I'm noticing lots of stutter/lag in the OS just interacting with the phone. Nothing processor intensive. Any idea how to fix that? I had this on my phone months ago and it was quite snappy I recall.

Also, is there by chance a simple unroot zip I can flash after installing a nightly? I'm only using CM on a my phone to deal with apps that require SafetyNet, and I was able to unroot by installing SuperSU and running the option there, but figure a zip would be much easier. Just a thought.
[G4 Android Development] kessaras:
for the 1st one we need a log, unless someone has the same problem.

cm is pre-rooted. you can't undo that. you can only disable root access and/or use xposed to hide "root" from the apps you want.
[G4 Android Development] Wolf2231:
I'm wondering , before I flash CM13 should I wipe data and system... Etc. The whole memory or I can just Flash it. I have h811 20p software installed. I got TWRP.
[G4 Android Development] brossovitch:
First, obviously make a nandroid (twrp backup) to your external sd card.

Do a full wipe. System, Data, cache, Dalvik, & Internal Storage (optional but recommended). Before you wipe internal make sure anything saved there is backed up if its important to you. Like Downloads or screenshots or whatever you have that you want to keep.

Flash ROM & GApps, reboot, enjoy.
[G4 Android Development] z0mghii:
Had the stutter/lag problem and I flashed back to an earlier build (10/7 or /8 or something) and everything is fine now.
[G4 Android Development] kessaras:
keep the system clean.

even the crap windows os is doing that. ( windows old )
[G4 Android Development] Wolf2231:
I noticed an issue with CM13 on my LG G4. In voice calling while I use the phone speaker to listen to the caller. The caller hear an echo, I called with a different phone the echo disappeared . So I reflashed a clean CM13 in case of any software issues. And the the echo reoccur. After troubleshooting I realized the echo was actually the phone re sending the voice of the caller. The speaker create the voice and the Mic resend it to the caller. To appear like an echo.

I'm not sure whats the fix. But I know its not normal. But there is some delay or not optimized drivers on this ROM. I hope this Message gets to the developers. Its already an awesomme job they did with this ROM. Though we still strive for VoLTE and Wi-Fi calling.

I'm using it as a daily driver, but still these features are critical.

Update: Hmmm. Maybe because the mic on the bottom should be deactivated. And use the top while on speaker.

Update: I'm 99% positive its the mic resending the sounds. Because when I mute the echo stops.

---------- Post added at 08:01 AM ---------- Previous post was at 07:09 AM ----------

Its not as easy as Android. Or should I say Windows doesn't have any method to do it with ease. Or we just fill windows with a lot of junk (myself) that we don't want to bother cleaning it.
[G4 Android Development] kessaras:
that issue doesn't happen to all phones ? i mean , i remember since years, that we understand when the "other side" has the speaker on, because we hear our voice. All my phones do that.

yea in windows we can't wipe because we will lose everything. windows os is a mess with everything installed in the same disk/partition and that's why it gets infected too.

But microsoft when updating to a new windows version it does a clean install of the system. And thats what we are talking about here ;)

Always when updating to a newer os version or moving from another rom to another we must clean up ;)

(system,data)

Cache and dalvik are not important, but it will be filled with junk.

SD card (internal sd) isn't important, and you can use it to backup everything you want and wipe it later after you restore your app settings.
[G4 Android Development] seanpr123:
Interesting, thanks for the tip.

I feel like this should be pointed out in some bug log if it's not just me.

It's certainly livable, but far from pleasant when you know what you're looking for.

What about other people on the newer builds?
[G4 Android Development] Wolf2231:
The echo is apart from original voice and its enough to hear a whole word back. The delay is long. And it don't happen on stock. I'm just stating this to be know issue.
[G4 Android Development] seanpr123:
Do you by chance have that build saved?

Not sure how to find an older upload.
[G4 Android Development] z0mghii:
https://mega.nz/#!ig0mgZ7Z!XbN32KGuZBiOUNVWhG2A_WbpqV6Do_ylqR45eIN0b18
[G4 Android Development] dextructor:
I've flashed the latest nightly (2016-11-06) and the gallery it's taking so long to open(sometimes the message to force close) and the screenshots it's all gray.
[G4 Android Development] flatratte82:
I'm on the same build and the gallery is working fine for me. Maybe try to delete the app data of the gallery.
[G4 Android Development] seanpr123:
Are you guys noticing the same FPS drops here and there in the core OS or is it just on my end?
[G4 Android Development] flatratte82:
Everything is running smoothly on my device.
[G4 Android Development] Retro295:
Hey all,

I used the search function but wasn't able to find anything related.

I'm having two issues:

1 - Knock on (dt2w) is unresponsive. Most of the time it takes 4 knocks, and often it doesn't respond at all.

2 - Occasionally when I wake the screen it wakes with no backlight, so dark that I can't even see the PIN entry.

Anyone run into these? Otherwise...superb ROM.

Thanks!
[G4 Android Development] xrad:
Works completely reliable here (no custom kernel, no mods). The to knocks must not be too close. You could check your logcat to see if there is anything suspicious.
[G4 Android Development] Retro295:
Tried reading logs via logcat - nothing at all is happening when I do my 'failed' knock. As in, I do a double-knock to try and wake it, and logcat shows no new activity at all. When I do it a second time, it simply responds.

Puzzled.
[G4 Android Development] thewild:
Yes, this issue has been around for quite a time for some users. I have no idea what the cause could be.

I did have it, but lately it did not happen very often. It depends on the release I believe. I'm on 20161002.
[G4 Android Development] xrad:
This could point to a hardware issue (since the kernel drivers apparently work for others). Do you have a chance to go back to stock and try there?
[G4 Android Development] audinswfc:
Hi all,

Sorry if this kind of question isn't allowed but I haven't flashed a ROM on my personal phones for about two years so I just wanted to ask how this ROM compares to the stock ROM on the H815? Is this ROM stable enough to use as a daily driver? I haven't even unlocked my bootloader yet but i'm getting bored with it now so I want to start playing around again :)

Thanks
[G4 Android Development] dulexetina:
Check out on youtube stock (nexus) vs lg UI. Rom is stable and responsive,but its still early to tell cause development is in progress. Only thing i am missing is camera app from stock. Photo quality is much better with lg camera
[G4 Android Development] PhrostB:
CM14 official nightlies released.
[G4 Android Development] kessaras:
hi. i know we moved on to cm14 but , i need to know first about this toybox tombstone i get on every reboot, because i'll move on to cm14 after gravitybox is ready.

So is there any fix for the toybox or we just ignore it ?
[G4 Android Development] Wolf2231:
Is CM13 stable now. I couldn't find change logs .
[G4 Android Development] piotreks4:
CM-13 nightly issues

I've got the weirdest problem:

I was running CM13 nightlies without any issues until I decided to upgrade to the latest nightly (which was 11/08, at the time) using the CM updater - which completed fine.

Yesterday (11/12) I ran into issues with the camera and decided to reboot the phone.

It ended up being stuck at the CM logo, and that's how far it's gotten ever since.

I've tried flashing all the known-working versions of CM13 along with 6.0 nano gapps (complete wipe of system/data/dalvik/internal storage), but the phone gets stuck at the initial "starting apps".

Has anyone seen anything like this before? It really looks like the gapps are messing things up (since I was able to boot the phone with just the CM13 ROM flashed, without gapps).

Should I try another version of gapps (micro?).

Any additional input would be appreciated.
[G4 Android Development] codeworkx:
Did u accidently install 14.1 nightly?
[G4 Android Development] piotreks4:
No, it was through the CM updater and it listed only CM13's.
[G4 Android Development] piotreks4:
I factory-reset the phone (cleared system/data/internal storage/dalvik), flashed CM13 11/11 & gapps 6.0 nano, still stuck on starting apps...

Will try 14.1 & gapps 7.1 next...

Edit: no-go with 14.1/7.1 gapps -- going back to CM13 20160228 & gapps 6.0 nano, we'll see...
[G4 Android Development] FadeFx:
I guess only a kdz can help you then...

Gesendet von meinem LG-H815 mit Tapatalk
[G4 Android Development] piotreks4:
Yup, i CM13 02/28 and 6.0 gapps are a no-go. Will try to go back to stock via kdz (problem is that directions/applications run on windows and I've got linux machines at home -- will have to spin up a windows VM and go from there).
[G4 Android Development] cybertron12:
Great ROM everythings works fine except

When I log into snapchat, video's and photo's wont load and/or send.
[G4 Android Development] brossovitch:
Have you tried 1108 build of cm13? Its the last build and it's perfect. Such an old build with newer GApps would probably not work, why not just update? Haha.

Godspeed.

---------- Post added at 09:26 PM ---------- Previous post was at 08:58 PM ----------

And wireless display doesn't work
[G4 Android Development] walter79:
Enable multi window for cm13/14/14.1

only edit build.prop and add this line:

persist.sys.debug.multi_window=true
[G4 Android Development] piotreks4:
I have not, to be honest, but have tried all the other combinations.

For some reason, I only see the last two nightlies on CM.org. Do you happen to have a link to the 11/08 build?
[G4 Android Development] brossovitch:
Its here: http://download.cyanogenmod.org/?device=h811

Its the 5th one at the bottom. For H815 I have no idea, sorry.

Last build, tomorrow it will be gone forever, hence why I saved a copy on my SD card and via nandroid.

If necessary I'll upload to my Google Drive and share..

Edit: here's the file on my Drive:

https://drive.google.com/file/d/0B-0AY5y9hzZIaVBwTTF6alp0S0U/view?usp=drivesdk

In case anyone should need it later..
[G4 Android Development] piotreks4:
Got it off the site - cheers.

Will get the phone back to stock at my earliest convenience and re-try flashing CM13. I don't want this to be the end of my CM adventure.
[G4 Android Development] codeworkx:
There will be weekly builds of 13.

One per week.
[G4 Android Development] bellanano:
Has anyone the stock recovery 20D-recovery.img ?
[G4 Android Development] toy203:
Did someone saved the last 13 for the h815 version? Thanks
[G4 Android Development] :
Is SlimPort supported?
[G4 Android Development] roze84:
Get CM13 Nightly

Hey guys,

has anyone of you a download link for a working CM13 release for the H815?

I accidentally installed CM14.1 yesterday and in this build it is not possible to make a phone call cause the mircophone and the speaker seems to be not working properly.

Thanks!

Best regards and thanks for all the great work!

Robert
[G4 Android Development] toy203:
Here's the 20161028 , not the latest sadly.

https://dl.dropboxusercontent.com/u/75375058/cm-13.0-20161028-NIGHTLY-h815.zip
[G4 Android Development] picard47:
here is the last available cm13 nightly:

cm-13.0-20161108-NIGHTLY-h815.zip

https://www.dropbox.com/s/4w4ulawe2ipeaw3/cm-13.0-20161108-NIGHTLY-h815.zip?dl=0
[G4 Android Development] roze84:
Thanks toy203 and picard47 - you guys saved my day! :good:
[G4 Android Development] kessaras:
you can use mega too if its easier for you, until cm dev team have their links ready.

Mega: Lastest cm13

picard's link

DropBox: Latest cm13
[G4 Android Development] mattnin:
I'm currently suffering the same issue at the moment. Were you running a really old version of CM13? I was, I believe it was an April version. I am on H811, installed the stock rooted 20o version, flashed TWRP, tried installing the 11/08 CM13 and unfortunately it's still stuck on starting apps!! I'm about ready to pull my hair out, I guess I need to KDZ too but I wasn't able to get LGUP working for some reason. I guess I'll have to work on it some more but I missed a very important phone call today! :( I need to figure out a way to get that KDZ installed. I kinda wished I just stuck with my really old CM13, it was working perfectly.

*edit*

Updated to 20p using LG Bridge. LG UP wasn't working at all for me. Installed TWRP, then installed 1108 CM and Pico GAPPS. Phone is started and looking good so far!
[G4 Android Development] mattnin:
I'm running ES File Explorer and it requested root access for transferring files on the ext SD card. After I closed it, the # symbol is still up in the status bar and it is listed as running when viewing the # tile in the pull down menu. Even if I disable root in developer settings the # still remains in the status bar. If I reboot it goes away. Is there anything else I can do? I do not want to use SuperSU. I am running the latest stock CM13 ROM with no other mods.
[G4 Android Development] kessaras:
many things.

1. hide it using xposed and search for a tool to hide superuser indicator and install it.

2. if you use greenify in general, kill es file explorer.

3. manually kill the app from settings.

4. check ES permissions, put it to not run in background or keep awake.

5. a service disable app to disable this specific service that keeps ES running in the background without a reason.
[G4 Android Development] DragonautMk:
The rom is close to end or support Will still goes on? :)
[G4 Android Development] xrad:
You only have to go one page back to find your answer.
[G4 Android Development] FadeFx:
Dont suggest using xposed in this thread, and if you have to, dont forget to mention that xposed users wont get support here and should not report ANY problems.

Gesendet von meinem LG-H815 mit Tapatalk

---------- Post added at 03:45 AM ---------- Previous post was at 03:40 AM ----------

Es should not need root for ext-sd access, it does not for me. If it does for you, you missconfigured it.

Gesendet von meinem LG-H815 mit Tapatalk
[G4 Android Development] mattnin:
Ok, thanks FadeFx. I'm not sure why it was requesting root but the weird thing was it still showed the # symbol in status even after greenifying or force closing. I likely did have it misconfigured but it doesn't matter now because I decided to use Ghost Commander File Manager instead. After doing further research about ES File Manager I found it communicates with some server in Beijing and verified that on my own phone using OS Monitor, so it's permanently removed now. I have no plans to install Xposed, SuperSU, or BusyBox. I like that CM warns about root usage in status and I am not looking to hide the symbol but rather understand why it's there.

I am on day two of the latest CM13 build and it is running great! Seems a bit speedier than the April build I was running :D great job codeworx!
[G4 Android Development] kessaras:
Sorry i just mentioned all possible solutions.

The root symbol if its there permanently, must be cause of an app that need root access is running in the background. You can also check it (without any further effort or installation of anything)

in dev settings , running procedures and check the specific service of that specific app.
[G4 Android Development] FadeFx:
Put the su tile in quick settings and you can check from there, but that isnt his problem, he knows it is es fileexplorer, which imo in the last years has turned into malware anyways, id suggest using a different filemanager that has not so many unwanted "features" like Solid Explorer, ok that is a payed one, but there is plenty of other filemanagers that support root mode and dont abuse their rights...

Gesendet von meinem LG-H815 mit Tapatalk
[G4 Android Development] eriklion:
You'll need to flash the stock KDZ version 20o or 20p to fix that. I don't know what causes it. I apologise, I did not see that this thread is for h815 at first.

I was looking for the last build of CM13 for h811, close but no cigar.

[MENTION=3208754]codeworkx[/MENTION] Where can someone find one for h811? I've attempted building again and it's failing randomly.
[G4 Android Development] codeworkx:
There should be one new cm13 build per week. Normally sundays. But last time the download server failed so you have to wait another week.
[G4 Android Development] genesixxbf3:
i can build one for you
[G4 Android Development] ceanth:
Hi guys,

Where can I download the latest CM13 from? On the Cyanogenmod website it only shows CM14.1

https://download.cyanogenmod.org/?device=h815
[G4 Android Development] piotreks4:
Good to hear you got that issue resolved -- I haven't been able to try it until now: Did you just update the firmware to 20p, or did you end up going through the entire KDZ procedure?
[G4 Android Development] kessaras:
i always keep a backup of a last version of every rom for my device when i know that life will go on without it. ( just to remember it :p )

**EDIT: but i forgot to share the link now haha
[G4 Android Development] mattnin:
I didn't KDZ. I just used LG Bridge and let it update my phone to the latest official build. After that, I had to root the phone and then flash the latest TWRP and then CM 13 worked without issue. So I'll bet you have been running a really old CM13 like me based on old firmware.
[G4 Android Development] piotreks4:
Ok, so I just need to get LG Bridge to actually recognize the phone when it's booted and I should be good to go (Windows 7 VM recognizes the phone, but LG Bridge says that no device is connected). Cheers.
[G4 Android Development] mattnin:
Yea, I just got LG Bridge to recognize it and then I think it said update available. I crossed my fingers lol and just let it update. It went perfectly fine. I hope it works for you through the VM.
[G4 Android Development] piotreks4:
Consider yourself lucky: LG Bridge wouldn't connect to the phone, I've got LGUP connected and now need the actual bin file....

**Edit**

Flashed KDZ and now back to stock with 20p firmware -- going to try flashing twrp/cm13 (11/08 nightly) now.

Helpful threads/links:

http://xdaforums.com/tmobile-g4/development/rom-lg-g4-h811-20p-stock-rooted-radio-t3477821

http://xdaforums.com/g4/help/lgup-install-kdz-mm-lp-t3249803

http://www.theandroidsoul.com/download-lg-g4-driver-for-windows-and-mac-mtp-adb-download-mode
[G4 Android Development] genesixxbf3:
http://eu.host.erwanleboucher.fr/genesixx/cm/h815/ if you want
[G4 Android Development] geier86:
I also have the problem with the camera focus not working on CM. Will there be a fix? What was changed in that boot.img?
[G4 Android Development] genesixxbf3:
it's fixed on cm-14.1 :D time to move (going to add it on cm-13 )
[G4 Android Development] flatratte82:
Auto focus is working with build 11/27.

Thanks :good:
[G4 Android Development] Spillunke:
No. Same error.

Also cant write on sd card on pc or android. Root is enabled.
[G4 Android Development] johnny8910:
Yep.

No go sorry
[G4 Android Development] codeworkx:
If you've used the external sdcard as internal storage on android 6, then android has created two partitions on your card.

One with 15 MB and one with the remain storage.

If you switch back to using it as external storage, then android formats the 15 MB partition to FAT32 and tells you that everything is fine. :D

Currently manual repartitioning is required to get the full storage back. (delete both partitions and create one big)
[G4 Android Development] dd0s:
Is there any tutorial? Is this the reason why I can't create folders? Thx for the advice.

Gesendet von meinem LG-H815 mit Tapatalk
[G4 Android Development] Spillunke:
But if i format the sdcard in portable storage, i have 15mb again as external storage. Also the missing writing permissions still there.

EDIT: If i format the sdcard with guiformat.exe, i cant write on sdcard in phone. If i format the sdcard again on android 5.1.1. with another device, i have only 15mb -.-.

how can i complete delete all partitions to create a single partition, so that this wont happen again?
[G4 Android Development] codeworkx:
Probably not.

Afaik windows isn't able to handle multiple partitions on removable storage.

You have to use your favourite linux distribution and gparted to get it done.
[G4 Android Development] Darkmasterhk:
you can use partition tools, even under windows, like "minitool partition wizard"
[G4 Android Development] Prazaar:
Format with stock v20a and after with CM13 and its work fine

Gesendet von meinem LG-H815 mit Tapatalk
[G4 Android Development] Spillunke:
Thats what i will try now.
[G4 Android Development] crucky:
you have to use a cardreader at the pc and then just use diskpart to delete all partitions and create one new :) if you have the 16mb partition problem
[G4 Android Development] Spillunke:
i tried, but the laptop is slow as hell. i format the sdcard with v20a LG based rom and try cm13 the next days again, also trying to fix the laptop.
[G4 Android Development] dontpannic:
Steps to repartition on Windows

Insert SD card into PC

Open Elevated Command Prompt (right click, run as administrator). Commands to type are in bold.

diskpart

list disk (note the disk number of your SD card - MAKE SURE IT'S THE SD CARD AND NOT YOUR HARD DISK!)

select disk X (X being the disk number of your SD card)

clean

create partition primary

select partition 1

active

assign

format fs=fat32

exit
[G4 Android Development] Donric13:
Had the same problems some days ago (you will find it some pages back). Win10 seems to have problems format the card readable for our device. Only working way for me was (as stated) flash a stock rom (genisys or else) and format the card. It seems also to work format the sd card on a mac or linux computer.

Gesendet von meinem LG-H815 mit Tapatalk
[G4 Android Development] ahmad.afef:
Better change the format part to

format fs=fat32 quick

And i see no reason to use the command "active"
[G4 Android Development] dontpannic:
Just habit, just marks the partition as active, no downside to doing it :)
[G4 Android Development] ahmad.afef:
I guess this habit is from when you install Windows from a USB drive. Marking it as active makes the system know that it has a boot Sector and it's ready to be booted.
[G4 Android Development] dd0s:
Method worked for me. Card has full storage and full permission. Thank you

Backup on sd via twrp working well.

Gesendet von meinem LG-H815 mit Tapatalk
[G4 Android Development] thermskin:
Hi [MENTION=3208754]codeworkx[/MENTION],

here is an interesting patch to allow SuperSU to run in SELinux enforcing.

Hope this helps.

T.
[G4 Android Development] codeworkx:
don't know yet if it fixes something or creates some big security holes.
[G4 Android Development] f-rouz:
Could someone please make a quick check if his bluetooth is also causing a 100 percent wakelock when turned on?

I would really appreciate this because with my TWRP beeing very unreliable (creating a backup crashes at 98 percent every time) and that system rw bug it would be a bit more of an effort for me than usual to wipe my phone and set it up again just for testing if that's a general bug or just my current setup... :angel:

Thank you very much ;)
[G4 Android Development] mattnin:
I noticed that SELinux on my phone is set to permissive. I am running the 1108 nightly. I thought stock was enforcing mode. Was there something I did to cause that? I tried changing it back using setenforce but that didn't work.
[G4 Android Development] genesixxbf3:
codeworkx derped will fix it on the next build
[G4 Android Development] FadeFx:
Hehe, that sounds like rule #1 at my workplace: it was always the one who isnt here... ;)

Just kidding guys...

Gesendet von meinem LG-H815 mit Tapatalk
[G4 Android Development] flatratte82:
Actually he did it himself:

https://review.cyanogenmod.org/#/q/status:merged+owner:"Erwan+Leboucher"

:good: