yashsingh1/xdaforums huggingface dataset:
[Touch CDMA General] denasqu:
If you used the imcokemans unlocker a 2nd time, I believe you re-lock your phone.

You also mentioned that you tried to flash the ROM from the Welcome Screen. That certainly won't work. You have to be at the unlocked rainbow bootloader screen which will load when you run the RUU or when you press Power-Camera-Reset. If it doesn't go into bootloader then you've probably re-locked your phone.
[Touch CDMA General] jim256:
haha sorry this is a problem that i had a VEERRRRY LONG time ago. have learned a lot since since then, now it is this other fella here we are trying to help him :)

thx tho!
[Verizon LG G3] Yaemish:
I figured that I would reach out to the larger community because I am really stumped. I've got a rooted LG G3 on Verizon, I've had it a few years now. I recently changed ROMs and my status bar pulldown no longer works while in portrait orientation, it is fine in landscape. Easy enough right? It would either be a problem with the ROM or the digitizer along the top of the screen is shot.

Pretty standard stuff so far. I can do the status bar pulldown from the lockscreen while in portrait mode, so we know the digitizer is fine. I would usually say to reflash, go to your backup, or try a different ROM.

Doing all of those things, the problem persists. On all of the flashes, I did complete wipes. As of today, I even did a TWRP format followed by complete wipes and a fresh install (note that this made me loose my backup). Problems are still there. Any ideas what I should try next?
[Verizon LG G3] cory733:
Read this guide to flash back to stock (10b TOT) and start over: https://xdaforums.com/showthread.php?t=2785089

After that you'll be on kitkat, just root with stumproot, then flash TWRP with flashify.

I've had to do this probably 5-8 times because of weird issues. So far it's helped me every time.
[Galaxy S6 Edge Q&A, Help & Troubleshooting] Ponns15:
Hi good day

Currently my Galaxy S6 Edge 925i, presents problems with the signal inside the home or office loses signal to only emergency call or 3G in very weak way, only to the foreigner I have 4G LTE intermittently, which I recommend? My service provider is ATT Mexico.

1. Check with other SIMs from different companies and the same.

2. Firmware upgrade from 6.01 to 7.0.

3.Reset factory values.

I'm thinking of getting him to change his antennae to see if it works correctly.

Thanks and best regards.
[Sony Xperia X Performance ROMs, Kernels, Recoverie] pavlinux:
PURE CLEAN NOT MODIFIED SONY ROM 41.2.A.7.8

F8131_RU_1302-6562_41.2.A.7.8_R2D_Customized.ftf: (2.66Gb)

Tested work with :

Kernel: XP_AndroPlusKernel_v26.zip (md5sum: b2c6f2fbafaf985d51ae858b28a43dfb)

TWRP: twrp-3.1.1-0-dora.img (md5sum: 787ce5110ab188c4df9ce96239426737)

SuperSU: SR1-SuperSU-v2.82-SR1-20170608224931.zip (md5sum: 663adcd65d3165e716570545dac5ea35)

Download

https://mega.nz/#!hzp3yY6I!CVKJdiEXCIcp6UGHOT5WFMCIJNEmLPc29x8e1aLHoDQ
[Sony Xperia X Performance ROMs, Kernels, Recoverie] Gabrik1986:
Thanks

How i can install this firmware? with Flashtool?
[Sony Xperia X Performance ROMs, Kernels, Recoverie] acme64:
i dont understand how to flash this. what am i missing?
[Sony Xperia X Performance ROMs, Kernels, Recoverie] Yondaimul:
The file you are trying to download is no longer available.

Can u please upload it? especially for SOV33, much thanks~
[Sony Xperia X Performance ROMs, Kernels, Recoverie] biansishuo:
I am 502SO and I need it,please upload it again
[Sony Xperia X Performance ROMs, Kernels, Recoverie] Gabriel'Cyan:
this is unavailable? somebody can help me?
[Google Pixel XL Questions & Answers] taylor310:
So, I'm currently on a Verizon Pixel XL with OctOS 7.1.2 June release, I updated without touching the bootloader/radio etc. What do i need to do to get updated to the latest of everything? I hadn't really been active in the community since I put the March release on my phone and now i'm kind of confused as to what to do. I used skipsoft tools at that point to get everything updated in february/march, but it doesn't look like that's still being updated for newer Pixel XL releases? So what steps do i need to do to get everything up to date?

1) download newest platform tools

2)fastboot flash radio/bootloader?

I'm also confused about active/passive partitions. I don't really want to brick my phone, and am currently in search of the newest everything. I haven't even found the radio/boot/bootloader for the newest release, it doesn't look like that thread is being updated either? I saw them hanging out in the OctOS download page, and also the PN rom post.
[Google Pixel XL Questions & Answers] 3aucla1r3:
If you like Skipsoft, you can download the June factory image and put in the file marked for putting google images, then go through the flash full image and it'll put all the latest stuff on both partitions. Then you go back and flash all your stuff like ROM, TWRP, SU, kernel, etc. This means starting all over but it works the best for me.

You don't have to use Skipsoft though, you can issue the commands. Or, you can just flash the bootloader and radio as you said but I'd be sure to flash to both slots to avoid problems.
[Google Pixel XL Questions & Answers] taylor310:
Would this completely wipe the device? All Titanium backups etc. Also probably a dumb question but would my bootloader stay unlocked if i went this route? I want to make sure it doesn't get locked again since I'm on Verizon.
[Google Pixel XL Questions & Answers] veskostoev:
Do a Titanium backup and copy on your PC.
[Samsung Galaxy S7 Edge Questions and Answers] mattan1999:
Please delete
[Samsung Galaxy S7 Edge Questions and Answers] EasyAndroidPro:
Your signature says your on ambasii s8 port... me too

I just installed [MENTION=6157501]envy~[/MENTION] 's apk provided in the post you linked & reboot and it works for me.
[Samsung Galaxy S7 Edge Questions and Answers] mattan1999:
after installing it 6 times it started working for me :)
[Samsung Galaxy J7 Questions & Answers] fennucci:
Title basically says it, after rooting is my phone no longer encrypted? How is that possible?
[Samsung Galaxy J7 Questions & Answers] fennucci:
I guess it reset settings after root, and it was set to not ask for password/pattern. I'm assuming this was the issue, I've never seen that setting before in settings. However I'm confused though because now it asks for a pattern instead of a pin/password.
[Nexus 7 Android Development] namerke:
Reserved
[Nexus 7 Android Development] Geko45:
Looking forward to trying future versions of this kernel, but unfortunately on a talapia device it currently never leaves the bootloader screen (Google and the unlocked icon).
[Nexus 7 Android Development] namerke:
Well, as said in the list of bugs, tilapia is not tested at all due to lack of device.

But if you didn't perform a clean install than it can take it's time to get through the bootloader screen, even on grouper. So make sure you wait there for a while.

On clean install I didn't encounter this issue.
[Nexus 7 Android Development] adstraylight:
Aside from the freezing issue, this is way smoother than stock.

My current config includes

200MB Zram (swappiness 100 - like Andisa's)

CPU quiet policy: runnable (experiment in reducing the freezes)

interactive perameter 'midrange_go_maxspeed_load' reduced to 90 from its default of 95.

Root Killing SystemUI when the screen is off (Again to try to prevent freezing/need for manual reboot)

SSD Boost

Running this command at startup :

service call SurfaceFlinger 1009 i32 1

(old habit - suggestion of parrotgeek's to speed up rendering of transparency)

Current result: freezing maybe eliminated, time will tell...

Current theory: Freezing may be due to excessive background cpu load, ie. the system trying to do too much at once. SystemUI may have nothing to do with it, but I still have my suspicions.
[Nexus 7 Android Development] adstraylight:
35hrs uptime with the above config + forced GPU 2D rendering, frequent use, so far so good...
[Nexus 7 Android Development] abhifx:
why the force gpu 2d rendering?
[Nexus 7 Android Development] adstraylight:
It was a thought to take some load off of the CPU, bear in mind I'm not a developer, so am working from basic principles, but it did seem to make everything run smoother. Could be wrong though, what do you think?

I should also add that /sys/block/zram0/max_comp_streams is set to 2, I don't remember doing this, but it could have changed when I was playing with bits of the parrotmod script file, and may have some bearing on the situation. In fact I think it was when I was trying to find an alternative to using Kernel Auditor to initiate the zram...

Uptime 58.5 hrs ?
[Nexus 7 Android Development] abhifx:
well 2d gpu acceleration should on by default, However the developers can use software rendering. This setting just overrides software rendering.

just to add that i am also not a developer. :D
[Nexus 7 Android Development] adstraylight:
Amateurs of the world unite!?

It was something I remembered from trying to optimise MM on grouper that made a lot of difference at points.
[Nexus 7 Android Development] adstraylight:
So I've stopped killing the systemui, rebooted, and have had 19hrs of uptime since, so I think we can discount that as a cause.
[Nexus 7 Android Development] adstraylight:
I have to say that the battery life with this configuration is extremely good. Do you think it would be possible to enable some overclocking?

The stability issue seems to be sorted now, and I see there's a commit under evaluation on the UA Gerrit that might consolidate things further, with regards to a possible memory leak. So it's all looking rather good ?
[Nexus 7 Android Development] abhifx:
you should post your findings on main ulegacy thread too. maybe this will prompt the devs to incorporate these settings.

this thread has been great and i have finally fixed my broken grouper to try these roms and kernel again
[Nexus 7 Android Development] adstraylight:
My guess is that they're already aware of what's been posted here, how are you finding it?
[Nexus 7 Android Development] abhifx:
they are relying more on changes pushed to their gerrit rather than tracking all the thread. so i dont know posting in their thread is also a good idea.. but hey its better than nothing.
[Nexus 7 Android Development] HTCDreamOn:
[MENTION=4573282]namerke[/MENTION] great to see someone build something off of the work the 3.4 guys achieved. This was the sort of thing we hoped for from the beginning and I really am surprised that you're the only one so far, years after the project started, to brave the source code and use it for a project.

Also, does the original kernel not have zram at all, or have you simply updated the current code to upstream? Cheers :)
[Nexus 7 Android Development] chosin137:
I am running [MENTION=2583740]adstraylight[/MENTION] suggested tweaks and its running Rock Solid. The only thing I did not do was reformat for F2FS since it wont work by default with Unlegacy. After the initial start the tablet stops having any system ui, force close, or mtp reboot issues. Boot is much faster and functions more like a normal tablet. I would recommend these changes to be incorporated into grouper unlegacy because as of now, running stock unlegacy with updated builds still has freezing, random rebooting and general issues with slowdowns. Honestly I still don't know why F2FS got scrapped for data and cache. I get that they are working on adding support for a lot of devices but it's just not useable in its current form with stock Unlegacy, unless you are okay with systemui freezes and random reboots.
[Nexus 7 Android Development] namerke:
New version is up

, please refer to the #1 post for the updated changelog.

Hi @adstraylight , thanks for all the feedback, it's been helpful , really, since i don't have much time to pressure test our device.

New version is including some of your suggestions to the interactive governor + some adjustments to it from Unlegacy-Android gerrit.

Also, [MENTION=2188693]AndDiSa[/MENTION] uses 250MB of ZRAM with swappiness of 60 by default , therefore this is the way I have configured the latest version since it seems to work just fine on 3.1 .

Number of ZRAM streams have been reduced to 1, just like [MENTION=2188693]AndDiSa[/MENTION] 's config, again , to reduce CPU load.

Hi [MENTION=4693882]HTCDreamOn[/MENTION] , to be honest i didn't even really checked the capabilities of the base 3.4 regarding ZRAM.

I followed a simple logic when I decided to go with the 3.10 upstream version: it proved itself fast and reliable on my Nexus 5, and also since it's from the upstream, it's more recent :)

All these said, I suspect that the base is lacking some files to enable ZRAM by default but I'm not sure since as I mentioned I didn't really checked the base source regarding ZRAM.

[MENTION=5139588]chosin137[/MENTION] , thanks for the feedback. As it turns out, based on my experience F2FS on cache causes some instabilities on this version too, therefore I have removed the option to use in in fstab.grouper on the updated version.

Also, this way it will be closer to the base , which can help with merging if [MENTION=2633638]Ziyan[/MENTION] and [MENTION=4619263]sheffzor[/MENTION] decides to go that way.

Thank you all for the feedback, happy testing :)
[Nexus 7 Android Development] HTCDreamOn:
Makes sense, I've seen a lot of kernels using zram and similar from 3.10. That could be it, it doesn't look like zram is enabled at all in the default kernel but I find it odd that it would be missing the files. I only just flashed the recent version of the ROM a few days ago so it's running fine on the stock kernel, will give yours a go once I've bogged it down with some more apps though.
[Nexus 7 Android Development] abhifx:
sadly my experience is on the negative side as i can easily completely freeze my tablet. only reboot is the solution. i guess i have seen this issue more in the stock 3.4x kernel too so i guess its more of a rom / memory leakage issue. However the tab does feels smother than other 3.1x kernel based rom. so the tweaks does seem to help more. i might try flat rom+kernel for while, if things are better then i can blame gapps and remove it altogether (although i do want maps for navigation purpose)
[Nexus 7 Android Development] adstraylight:
Same, I had two freezes in the first hour using the default config, so I've reverted to my setup for the governor and zram. I think the key is the balance between userspace and background tasks. This is why I was asking for the ability to overclock, to pep up the snappiness of the ux while still leaving enough for the system.

Under the default config, the ux is great until it crashes, under mine it's more languid, but stable.

I've found in the past a modest oc up to 1500mhz can make a significant difference to the general feel, without sacrificing too much in the way of battery life. I seem to remember Metalice saying once that the CPU runs at that speed during boot and is actually underclocked by the system during runtime.

Andi seems to try a different snappiness value with each release, 60 is the Google default, the value of 100 was from the last version of his ROM that I tried, before jumping to 3.4. I was pleasantly surprised how effective it was, as my tendancy is generally to be a lot more conservative.

I've always found 256MB zram to be too much for the limited RAM, particularly with big dynamic apps like Maps or Reddit. I settled on 200 via trial and error, all depends on your personal usage though.
[Nexus 7 Android Development] chosin137:
No issues on the new build using [MENTION=2583740]adstraylight[/MENTION] setup. I'm still *STRONGLY* recommending this over stock or default builds. The difference being this makes the 2012 Nexus completely functional after everything is fully loaded in on first boot. Even Chrome functions better after initial load. The CPU / IO / ZRAM changes are preventing the system ui reboots and freezes now. Running the Force GPU options seem to be helping as well. The key to OpenGapps is to run it after first boot and SuperSU install through TWRP. If you dirty install over an old build you are still going to have to either unnistall a bunch of google apps and reinstall from the play store to get them to start AND OR go into each and enable permissions again. Just the nature of the beast. The apps thing happens everytime you update a build but its manageable if you have dealt with it before.
[Nexus 7 Android Development] adstraylight:
I just reread my last post, and realised it could come across as being very critical, and maybe even rude. I'd like to say how great it is that there's people willing to give their time and energy to keeping this old tablet going, and my intention is solely to help in this endeavour. Thanks so much to namerke and the UA guys for the opportunity to keep tinkering with the good ol' grouper?

Back to business... I've been trying to run with the min sample time at 500000, as opposed to my 50000, and it does make the tablet snappier, but I use an app that has locked up twice using the higher value. I think that the extended sample time, that is 10x higher, may impede the reactivity of the CPU clock a bit too much.
[Nexus 7 Android Development] namerke:
No hard feelings :) .

It's always nice to have feedback , even if it's critical because it sheds light on issues which can be addressed in future iterations.

All these feedback of your's guys are very welcome.

This right here is the line that we should keep in mind. You see, the current default configuration works pretty flawlessly for me, since the min sample time at 500000 and the 250mb zram size gives a pretty snappy overall performance and a fluid UI. Even under heavy usage (For example: sync for reddit with lots of GIFs and multitasking with video playback from youtube with Newpipe + background music , etc.) I can not really lock up the device. There are some hiccups for 1-3 secs once in awhile, for sure, but no complete freeze yet. As you mentioned, this is also the default governor value from Google.

However, all of you mentioned that you use maps therefore you must use gapps too.

Since I don't use gapps I have to suspect that the overall system load with gapps + default settings are too much for our 5 year old piece of silicon.

I had other bad experiences with the base ROM + gapps combo earlier , based on that the base ROM unfortunately doesn't play nice with Gapps.

There were a lot of unfixed permissions for a while, and the usability of google's android webview / chrome webview as a default is still broken, I had to edit the framework-base.apk to fix it.

But it's not a blame game, the Unlegacy guys are great and doing very hard work for us in their free time. I'll try to fix the framework issue I found with them in a pull request once I'll have the time.

The point is that right now we should try to find the right balance between fluidity and stability even with Gapps installed, but before I adjust the default values somewhere in the region of your suggestions I want to confirm with some things with you guys.

I know you are advanced users and probably didn't forget these things, but could you please confirm that:

Cache partition is on EXT4,

Zram got initialized properly before you changed its size / swappiness value ?

Thanks in advance :good:
[Nexus 7 Android Development] adstraylight:
Yes, and yes (cache/zram)?

Maybe you can explain something about the cache partition though, why is it no longer used in N? It just sits there with 7MB used out of 443, seems like a waste of good space to me...
[Nexus 7 Android Development] abhifx:
this.. seems more like a gapps issue as without gapps everything feels great. but i really do need gapps as i use my tab as car infotainment system.

this webview seems very intriguing, and i suspect it could be the culprit.

and yes.. zram gets initialized and i have all partitions with ext4
[Nexus 7 Android Development] adstraylight:
Is there any way you could release your edited apk for others to test?
[Nexus 7 Android Development] abhifx:
+1
[Nexus 7 Android Development] namerke:
Unfortunately I don't think that's a good idea, for two reasons:

1. I might wasn't clear enough, sorry about that, but the edited APK wouldn't help much with the freezes. As I tried to emphasize the issue is that the system load seems to be too high with gapps + it's background services and the default settings. The edited APK would only enable you to use Google/chrome webview as a default instead of aosp's. Our aim should be finding the best governor and zram values in order to keep stability with gapps too, since without gapps it seems like everything is fine. Reducing the min sample time seems to help to avoid lock ups under heavy load.

2 framework can change with each release of the base ROM, and I surely don't have the resources/time to decompile/edit/recompile and share it with each release. The best way will be to open a pull request with unlegacy team, and once it gets merged you will have it by default
[Nexus 7 Android Development] abhifx:
what my contention was that it is possible that usage of webview could be one of the reason to cause slowdown and instability. if we can test it then filing the bug report to unlegacy jira should be easy. we dont have to get new framework for every release then as the fix will come inherently build in.

of course this is just a possibility, but could fix 3.1x kernel based roms roo. however, [MENTION=2188693]AndDiSa[/MENTION] might be able through more light, what if he already has similar fix built in with his ROM.
[Nexus 7 Android Development] adstraylight:
How very odd, because in the developer options it says I'm using chrome as the webview provider, and in the apps menu it shows aosp webview as being disabled permanently (ie I can't reenable it).*

I think reducing the midrage load value helps also by decreasing the response time on an increasing load. I have also tried to expedite the wakeup time by raising the minimum frequency to 102, but I think this is more down to the maximum speed to reinitialise the background processes after sleep.

Sorry to nag, but it really would be great to have a max frequency allowance of 1500 to cover spikes in CPU demand, would you consider this?

*EDIT: This may be due to something I did a while ago, I think I may have a vague recollection of disabling the aosp webview in the course of some experiments....
[Nexus 7 Android Development] chosin137:
Any update on this? Is it going to be merged?
[Nexus 7 Android Development] abhifx:
you can always check with unlegacy gerrit if anything new is merged.

but short answer is no.. not merged
[Nexus 7 Android Development] namerke:
Probably everyone is on the Oreo hype-train, but in the meantime I've uploaded an update after being on vacation and being busy in my Daytime job.

Update - 2017.08.26

Updated with all the latest kernel commits from the Unlegacy-Android project.

Governor tweaks to play nice even with Gapps installed.

Few, minor tweaks inspired by [MENTION=3292224]franciscofranco[/MENTION] 's grouper and hammerhead kernels, which in theory should help with overall performance.

Have fun testing.

P.S.:

It's possible for the new version to load for a while on first boot at the Google bootloader logo.

Don't panic, it should boot up eventually.
[Nexus 7 Android Development] marras:
just flashed over unlegacy android, everything work, but is not as good as I hope. It crash or freeze easily (in particular using chrome or playstore) and takes ages to do the first loading opening apps like youtube, nova launcher or chrome. Naosp works waaaaaay better in my abused 5 year grouper. I've to change file system from f2fs for data to ext4? cache and system are on ext4
[Nexus 7 Android Development] pmitrik:
I've had the kernel loaded for a few days. I had to convert my cache back to ext4 in order to boot. I also have had the freezes, but the logs have not been reliable to me (perhaps I'm not pulling them correctly). I've noticed that the xda site through the browser causes a freeze, but the app is working fine. I also noticed that the camera does not work and there is a camera server error in the log.