yashsingh1/xdaforums huggingface dataset:
[G2 Android Development] RenderBroken:
Yes this is the GPU Gov that is making it change freqs. You don't want to run at 450MHz all the time. While in trickster move the screen around for a bit and then look. You will see that it uses the max freq. If you want more GPU performance change the GPU Governor to msm-adreno-tz
[G2 Android Development] bleached45:
Ok. Thank you. I'm ok with it working like that. I guess I was just confused because it was changing the max_frequency value. As opposed to a current level. So it seemed more like a throttle. Much appreciated.
[G2 Android Development] goast:
Hi not sure if this has been asked so pardon me if it has, is there a chance in the future you could add some overclocking? Maybe to 27000 at the most... I tried dori on liquid smooth and got everything working but Bluetooth doesn't work right but dang I miss over clocking!!!
[G2 Android Development] RenderBroken:
Did you try mine on LS? lol Why would you even need overclocking? By default when you set to build for overclocking the V-Core (Main Voltage) is raised for ALL freqs regardless if you even use the higher than stock freqs or not. I sometimes feel 2.3GHz is too much lol What would you use it for that my kernel cannot do with stock freq? I am always willing to listen.
[G2 Android Development] 1ceb0x:
I guess is that feeling of having "more power"
[G2 Android Development] goast:
Just felt faster but at you heed I'll try render on ls[emoji12]
[G2 Android Development] RenderBroken:
OK I was just curious. If you are wanting a more smooth experience. Change this to 2

/sys/module/msm_hotplug/cpus_boosted
[G2 Android Development] Matze060906:
[MENTION=5438598]RenderBroken[/MENTION]: here it is...

https://docs.google.com/file/d/0BwVur07uzqm6X0RYbWxweHZsSlE/edit?usp=docslist_api
[G2 Android Development] goast:
Worked great thank u
[G2 Android Development] Raagh:
Hey [MENTION=5438598]RenderBroken[/MENTION] i have a question.

how can i merge everything but one commit?

example: i wanna keep my vendor_aicp source updated, but i made modifications to common.mk , if i fetch aicp, and then merge the changes.

the merge ll show errors because Theirs common.mk wont match mine. how can i merge every changes except the changes they make to their common.mk?

thanks in advance
[G2 Android Development] bleached45:
Render may know better, but this looked similar to something I saw here.

http://www.android-x86.org/getsourcecode

Down near the bottom under" How To Solve Conflicts"

Maybe you can use this?
[G2 Android Development] RenderBroken:
Was this after the screen issue you reported?

awesome

Use

git mergetool

I use Meld for merging and you will have to Google how to set the default merge tool.

After merging run

git commit

Not sure if this is what you mean. Let me know.
[G2 Android Development] ZeNiXxX:
hey all,

will dt2w work on newest aicp nighltly with your newest Kernel ?

Tried bart dorimanx Kernel with aicp and dt2w doesn't work. The community tells me that they changed some ramdisk settings or so. So on liquidrom and aicp dt2w doesn't work.

Gesendet von meinem LG-D802 mit Tapatalk
[G2 Android Development] hovanhuang:
echo>1 /sys/devices/virtual/input/lge_touch/touch_gesture

you need to enable it this way. Search on Vanir's thread
[G2 Android Development] ZeNiXxX:
tried to Run it as a Script with script manager but somehow it doesn't work or should I try it with a Terminal?

Gesendet von meinem LG-D802 mit Tapatalk
[G2 Android Development] hovanhuang:
Definitely try terminal first with su access. Then play with ect/init or use tasker to make it run every time rebooted.
[G2 Android Development] Raagh:
Hey [MENTION=5438598]RenderBroken[/MENTION] sorry to bother you again. Could you take a look to this? https://plus.google.com/102251647281654134166/posts/GAJFfyY2Rwz read the post and my comments, in the comment is the translation for the error.

Sorry but i need some help. Bart452 is studying hard and dorimanx wont help me because its a twist of his work.

Edit: if i take time to answer its because ive been studying hardware arquitecture all day, reading xda in the breaks ahaha
[G2 Android Development] RenderBroken:
Have you made sure those files being referenced in the error are actually where it thinks they are?

«/home/raagh/AICPKK/out/target/product/d802/recovery/root/sbin/lzop»

«/home/raagh/AICPKK/out/target/product/d802/recovery/root/sbin/tar»

«/home/raagh/AICPKK/out/target/product/d802/recovery/root/sbin/busybox»
[G2 Android Development] Raagh:
Yeah they re there. Cp is a symlink file( when i make right button--> properties on for example cp it says its broken thats what bugs me)

The error in english is : "cp:not writing through dangling symlink"

I tried downloading the ramdisk from lge_g2-common(stweaks branch) repo(rootdir directory) using git clone and downloading it by zip both show the same.

So i dont know its a compiling error if the files are getting donwloaded wrong or what( dont know much about linux so dont know how symlink files are supossed to be showned under file properties)
[G2 Android Development] RenderBroken:
Sorry bro, I dont know either. I am not used to building Kernel inline with the rom.
[G2 Android Development] crnkoj:
That's an issue with your system. Cp as of late has this feature that it won't copy things into a directory which has broken symlinks. Open your directories from the build error in a terminal and write "ls - l" check which links are broken and fix their respective linking. That might fix it. However if that's during compile time you need to look at your respective source code and makefiles and fix the issues there.
[G2 Android Development] RenderBroken:
You hit the nail right on the head! Thanks for chip'n in !
[G2 Android Development] Raagh:
Dont worry men i know its not your comfort zone

Wow thats what i call giving me a hand ahahah thanks a lot men i ll see what i can do and report here :)

---------- Post added at 09:00 PM ---------- Previous post was at 08:44 PM ----------

hey men just another a question : there re a lot of symlink files broken . a symlink is just a file pointing somewhere or it has commands and code inside?

i mean for example this files are broken, i need to remove them an create a new file named cp that points to the right location? thats all?

chmod

chown

cksum

cp
[G2 Android Development] RenderBroken:
This is the poart of Linux my knowledge fails me. If you asked me to setup a Linux Server to host thin client and have old computers run Windows 8, then I am game. ;p

Still I believe the problem is with your source. Are you building for just a single model?
[G2 Android Development] Raagh:
yeah just for d802/5/6 (same phone) guess that what im facing its the diference between vanir source and aicp because im pulling the ramdisk directly from bart452 sources.
[G2 Android Development] RenderBroken:
Some good news and you will not believe it, the cause for the color artifacts at boot with R18 was because Thermal Protection was enabled at boot. FML lol. I have spent a good amount of time trying to figure this one out! But its good to know. As I said the issue was not a permanent screen problem. The issue was caused because the MDSS Driver was not able to poll correct information at bootup. I cant say WHY this is caused by Thermal being enabled at boot but it is what it is. More good news is once I figure out either how to how to enable the protection at boot without any issues or just replace it with my previous protection, I will be ready to release the test build I have been using. I am pretty pumped about it too!!
[G2 Android Development] Raagh:
great news men keep up the good work.

im playing some crazy magic here for my build ahaha.

i erased every symlink file in the directory (32 of them) create the new ones pointing to the right directories and rename them to the original names(most of them where in the same folder that the original file but a few where .../init , so i search that directory in the rom source and found that it has files with the same name of the original symlink ahaha . lets say im trying to build just following intuition xd, lets see if actually works.
[G2 Android Development] crnkoj:
Symlinks are symbolic links :P those are like pointers in programming languages. They just point to the actual files. But from your pastebin in the gplus post it seems like you are missing 3 working links in the out directory (lzop, tar, busybox). What I would assume is that the ramdisk you are trying to build needs those, but you don't have them properly set up or configured in your sources, possibly you are entirely missing them or just that they are in the wrong place, hence the cp command complains about missing links. All in all if I'm correct lzop and tar are being supplied by busybox like Symlinks (maybe read online on the function of busybox, basically it's a bigger binary that supports symlinking other named basic linux commands and than it runs them - it's like a whole /bin or /s in combined in a small package for embedded devices, I don't know the whole mechanism behind it though), so it might either be you are just not building busybox or its built in the wrong directory, or its just the Symlinks in the build (or out) directory that are not pointing right.

Where did you check that cp and chmod are broken links, was it in the build directory or in your actual system (though your system wouldn't work without those, so I assume it's in the build directory)? If it's in the build directory it speaks for wrongly set up Symlinks by the compile. I have to say that this crosscompiling is a dirty business...
[G2 Android Development] Matze060906:
Good to know, but I had it 1 time on R17 too. Is that the same reason with this build like R18?

Btw: yesterday I switched from Mahdi to liquid smooth and I'm very happy about this rom. I'll test the stock kernel for 2 days and then switch to R17 or a newer build from you.

Thanks for your hard work... [emoji4]
[G2 Android Development] willi_3609:
Last time I tried render it was unstable for my vs980. Is r17 better or should I wait for r18/19
[G2 Android Development] RenderBroken:
R17 is pretty solid.
[G2 Android Development] bleached45:
I haven't had one reboot in the last few days with R17. But that is on the D800 so YMMV.
[G2 Android Development] mazroui:
Very strange . just got the freaky lines issue on R17 which looked like the boot screen but lines where out of place and looked fuzzy but u could still tell

2014-09-06_22.15-crash.zip
[G2 Android Development] :
wait does this kernel support CAF?
[G2 Android Development] RenderBroken:
I am doing a Video Driver overhaul to prevent this though its nothing serious. Just the driver freaking out. You can let it boot all the way up and then turn the screen off then back on and it will return to normal. The next release is so close. I am testing numerous changes to see if it will help. A few things I may do before the next release is:

MDSS (Video Driver) Overhaul even more

Linux Kernel bringup (pain in the ass merging)

LG CAF, There are numerous CAF additions but still this will not work for CM. They have their own blobs.
[G2 Android Development] mhajii210:
R17 on D801 Mahdi 7/29 ROM

Hi guys. I just wanted to report Mahdi 7/29 seems to be more stable on my D801 than Mahdi 8/17. I have not had any issues with R17 and Mahdi 7/29 for over 72 hours now (knock on wood). Thank you for this amazing kernel work!

mhajii210
[G2 Android Development] fix-this!:
Test build this weekend render?
[G2 Android Development] RenderBroken:
Shooting for Release this weekend. Still having the weird screen issue at boot up. Working on it currently then I will release. The newest build is pretty freaking sweet. I have re-enabled some C States that don't seem to cause any issues.
[G2 Android Development] bleached45:
Is this still because of thermal being on at boot? Have you thought about writing a script that enables it after boot? I don't know if init is done at boot or after the boot completes. But maybe put it in there? Just a thought.
[G2 Android Development] RenderBroken:
Besides, why you rush'n me bra?! lol Since I know the exact cause of the reboots I even added Quick Wakeup back in :D This I am excited to see if it helps!
[G2 Android Development] RenderBroken:
Really its more of a symptom so I am trying to fix the problem. Thanks though!
[G2 Android Development] fix-this!:
Cause im a crack flasher. ;)
[G2 Android Development] hovanhuang:
Any body can confirm that dt2w is a kernel function or ROMs? I am on mahdi 8/17 built. Feel like furnace kernel more responsive than r17. Like furnace 70% time will work and r17 is 50%. But R17 is really good for battery. Thanks for the tweaked interactive governor, render.
[G2 Android Development] Raagh:
ORD
[G2 Android Development] hovanhuang:
QUOTE=mhajii210;55285210]Hi guys. I just wanted to report Mahdi 7/29 seems to be more stable on my D801 than Mahdi 8/17. I have not had any issues with R17 and Mahdi 7/29 for over 72 hours now (knock on wood). Thank you for this amazing kernel work!

mhajii210[/QUOTE]

How's the knock on/dt2w function working? I'm on mahdi 8/17. 50% time doesn't work, especially when deep sleep. No body can confirm now it's a kernel thing or ROM's thing.
[G2 Android Development] hovanhuang:
How's the knock on/dt2w function working? I'm on mahdi 8/17. 50% time doesn't work, especially when deep sleep. No body can confirm now it's a kernel thing or ROM's thing. which G2 do you have?
[G2 Android Development] RenderBroken:
Its weird because we have the same source files regarding DT2W . . . lol
[G2 Android Development] hovanhuang:
It's just my feeling. But definitely both doesn't have 100% dt2w functioning, especially after deep sleep. some guys said mahdi 7/29 with R17 is rock. So i am not sure the dt2w is a kernel or ROM issue? What's your opinion?
[G2 Android Development] bleached45:
I definitely noticed dt2w was acting up on mahdi for me. But so was the back button. I definitely notice an improvement with AICP.

So it leads me to believe mahdi is at least part of the reason.
[G2 Android Development] RenderBroken:
It works 100% of the time just takes more than 2 taps. Sometimes way too many to count. Its ridiculous. Now the problem is Rom side. If you install this kernel on other builds like Mahdi 6/20 (I think) and it works fine. Also the sysfs for this:

/sys/devices/virtual/input/lge_touch/touch_gesture

Is corrupt. If you try to set 1 it will not stick. I don't know why but it is just one more clue.
[G2 Android Development] crnkoj:
Yeah I updated Mahdi to 8/17 and went back to 7/9 because dt2w just took so many taps instead of the 2 required...
[G2 Android Development] mhajii210:
DT2W

I feel it's a little better on my D801 on the 7/29 build versus the 8/17 one. Plus it seems to be more responsive and overall more stable.

mhajii210
[G2 Android Development] count_martin3z:
Few mins ago I went back to Alegenmod from AICP. For sure Alegen has better dt2w than AICP. Mahdi looks the worst from these 3 roms regarding to dt2w
[G2 Android Development] 1ceb0x:
you haven't tried liquid smooth ;)
[G2 Android Development] count_martin3z:
Yep, that's why I mensioned about these 3 ;) Will try liquid for sure... how Zach's r17 looks on it?
[G2 Android Development] 1ceb0x:
i don't know yet. the stock kernel is pretty solid. i am waiting for another version of Render's.
[G2 Android Development] RenderBroken:
I use it and really like the results.

Its like that huh? . . . lol

Yea the stock kernel is pretty solid. I tried it out as well to gauge it. REV3N has done a good job with the whole package. He is very motivated like me and we both want to do a good job and we enjoy it when it pays off. I am certain we will see more from him.
[G2 Android Development] Matze060906:
Looks like you are jealously... [emoji16]

For your awareness of the self: you are the best kernel dev of the World... [emoji6]
[G2 Android Development] RenderBroken:
lol thanks! Nah, he is good people. I even think he is going to build/release a kernel. That's fine with me. People will choose what they want, it will also make the community better for it. Before I was here, there really was not any AOSP support and I wanted to fill a gap. It just so happens that i love AOSP roms as well! If there are two AOSP Kernels then that will just make me sharper.
[G2 Android Development] 1ceb0x:
it will benefit the AOSP community as a whole if we will have 2 kernel devs for it. ideas will pass from one to another, commits, improvements... I want to come back to your kernel but i am waiting for the next master piece of yours;)
[G2 Android Development] RenderBroken:
We talk pretty regularly already. I imagine we will do just like you said.
[G2 Android Development] fix-this!:
the furnace kernel cant run better than renders. its outdated from may and doesn't have 4.4.4 sources.
[G2 Android Development] SREEPRAJAY:
[MENTION=5438598]RenderBroken[/MENTION] [MENTION=5037435]REV3NT3CH[/MENTION] ...although I don't prefer to be OT ....you surely need to be appreciated ... Love such selfless and good people...

Thanks a lot....world becomes beautiful when you find goodness among us
[G2 Android Development] RenderBroken:
Thanks! :D
[G2 Android Development] RenderBroken:
I am soo close to release. I just want to squash this last issue then I will do so. I believe this will be even better than R17! R17 is Rock freaking solid and this will be too. It will also have more battery saving going on along with better performance.
[G2 Android Development] Matze060906:
Which governers and schedulers will be in the next build?
[G2 Android Development] 1ceb0x:
i believe same like R17 but this time he enabled some other sleep states (other than the ones in R18). hopefully every phone out there will like it and no reboots will follow after!
[G2 Android Development] RenderBroken:
HYPER

Intelliactive

OnDemand

All the Schedulers ie:

Zen

FIOPS

SIO

etc

I will post a full list of changes when I release. Its pretty substantial.
[G2 Android Development] RenderBroken:
Man, you guys dont know how hard it is to update your linux kernel version. lol Here are the steps I am using. (I like to share knowledge)

First I turn ALL of my commits into patches so I can just re-apply them over my new working branch after the Linux Kernel is updated. To do so you need to run:

git format-patch CommitSHA1..CommitSHA2

CommitSHA1 is your first commit you want to apply

CommitSHA2 can be any commit that is newer than CommitSHA1. For me this is about 300 commits ahead of CommitSHA1. This makes it easy to re-apply your commits to a new branch or source.

To apply the patches all at once:

git am *.patch

You WILL have errors and I like to use:

patch -p1 < CommitPatchName

When you finish patching the individual commit you just run:

git am --continue

It will then proceed to apply the rest of the patches til its done. This saves a metric crap ton of time!
[G2 Android Development] count_martin3z:
No way... No more Mahdi? As I remember you created this kernel specialy for Mahdi? :)

---------- Post added at 06:31 PM ---------- Previous post was at 06:27 PM ----------

I felt the stock wasn't so smooth as roms on Render's...
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] Cache-Lei:
I and using the AKU 3.2 rom.

and I find that is just work in a "short Distance" (around 40cm) in A2DP blueT. connection. otherwise, the sound will "pause" or "skip", is that normal?
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] Brazilian Joe:
Are you using the default MS stack which comes with it or the experimental Broadcom Stack ('WM5 Broadcom 1.7.1 Build 3400 Stack (Test)' thread)?

I couldn't even get A2DP to fly with the MS stack, but handsfree worked fine. On the other hand, A2DP was hassle-free with the Broadcom stack, but Handsfree was problematic.

But we did a test and we could spread around 5 meters until the sound started popping every now and then.

for the record, I am using Helmi AKU 2.6.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] Robrecht:
I have the same problem with A2DP on a 2003SE rom (1.40.00WWE). The connection is clear but very unstable; distances up to 2m are possible as long as there is line of sight, but the moment I turn my head so it blocks the antenna side of my headset, it starts skipping and pausing, even at a much smaller distance.

As far as I know, I don't have any metal plates in my head.

When the device is in my pants pocket and I'm walking, it also starts skipping everytime a part of my body gets in the way. Extremely annoying. After using the bluetooth headset for a couple of months, I just went back to the wired one because of this.

BT build 3900

Anycom stereo headset
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] invictus:
Blue angel with A2DP bad range

i agree. i have the T-Mobile 1.42 Windows 2003SE Rom and the bluetooth range is extreamly bad. On A2DP the range is something like 1meter in direct range. if i cover the pda with my hands actually hear crackings, drops in the headphones...

Can we fix that? any firmware patch to increase the range? can as an extreme solution to build inside a small high gain antena?

i start to believe that all that is wireless in this device has poor range...

BR,

Invictus

Qtek 9090
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] marksken:
Yeah would like a fix to
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] kanomen:
I have the same error.
[Moto G Q&A, Help & Troubleshooting] Jakub Ch.:
Hi, I necessarily need GPE 4.4.4 ROM, because firstl install this ROM: http://xdaforums.com/showthread.php?t=2646404 and received 4.4.4 OTA. Then I try install other ROM (4.4.2) and phone is half-brick, I can go to bootloader and recovery, system no works. I find this: http://xdaforums.com/moto-g/help/recover-4-4-4-downgrade-brick-temporal-t2801946 , but not help for me. Only ROM, which work is Official CyanogenMod 11, but in CM not work GSM for me :/

P. S: sorry for my english
[Moto G Q&A, Help & Troubleshooting] massithereaper:
Try to use this http://xdaforums.com/moto-g/general/unbrick-method-t2794271
[Moto G Q&A, Help & Troubleshooting] Jakub Ch.:
Not work. I need 4.4.4 ROM... :( When I flash CyanogenMod 11 (4.4.4), phone boot Ok. Whne I flash different ROM (based on 4.4.2 or 4.4.3) - not work.

EDIT: RESOLVED!!!
[Moto G Q&A, Help & Troubleshooting] jfcc58:
Please let us know how you resolved this!
[Moto G Q&A, Help & Troubleshooting] Jakub Ch.:
In the end - no way :/

Flash: http://xdaforums.com/showthread.php?t=2626803, V1. Phone start ok, but when I recieve 4.4.4 OTA update, during instalation, error message and finished. :/ No way to update 4.4.4, OTA not work and install from zip not work - same error. I try install this ROm V2

- but wifi not work (all V2 version).

I found http://xdaforums.com/moto-g/development/rom-4-4-4-gpe-using-philz-recovery-t2806546 and install this. Ok, phone start, but NO WIFI! :/ . I try this: (i) No Wifi after flashing Stock Kernel? Flash 'Stock Kernel Modules.', not work.

O think: I need backup from 4.4.4 phone. Can you help me, please? Thank You.
[Moto G Q&A, Help & Troubleshooting] lost101:
What about using this recovery backup?

[rom][nandroid backup] 4.4.4 gpe using philz recovery

http://xdaforums.com/showthread.php?t=2806546​
[Moto G Q&A, Help & Troubleshooting] Jakub Ch.:
I try this, but wifi not work :/ This is based on "V2" GPE ROM... I need backup 4.4.4 based on ONLY "V1" ROM
[Moto G Q&A, Help & Troubleshooting] fl4m3y:
I Have similar problem and im trying to fix it... if i find something i will let you know :)I know a way how to unbrick your phone until theres a full fix.... im gonna upload my cwm backup
[Moto G Q&A, Help & Troubleshooting] Jakub Ch.:
Do you upload your's backup to Google Drive or other cloud? And do you have GPE 4.4.4 backup?

Thank You very much!!!

Sorry for my bad english
[Moto G Q&A, Help & Troubleshooting] fl4m3y:
Im uploading to my gdrive for fast downloading but i will take a while because of my upload speed... It's Stock Rom Motorola 4.4.2 but this method i will post later should work for most cwm backups

its better than a half bricked phone