Anyone else notice their pixel c getting sluggish and laggy after the most recent updates. Nothing seems to fix it. A reboot might make it appear better but a few minutes in it just stutters and lags like crazy. Already restored it once and that helped a bit but then it just started doing it again....
Just curious before I start looking into a rouge app. Any idea how I could search to see if an app is causing the problem?
Thanks
Same here, I have tried resetting the device with no effect, when I check with AIDA64 my CPU iss stuck on 204 mhz (all cores). Before all this happened it was not accepting my pin code (which I have been using for 3 years) so I done a resset. I am thinking to go back on Nougat now. Let me know if you find a solution. Thanks
---------- Post added at 11:23 AM ---------- Previous post was at 10:50 AM ----------
OK now seems to be fine, try disabling google chrome (uninstall updates from that app and dissable automatic updates from playstore), enable chrome again but don't install update for that. Its back to normal for me, we need to wait for fix for google chrome
damjan006 said:
Same here, I have tried resetting the device with no effect, when I check with AIDA64 my CPU iss stuck on 204 mhz (all cores). Before all this happened it was not accepting my pin code (which I have been using for 3 years) so I done a resset. I am thinking to go back on Nougat now. Let me know if you find a solution. Thanks
---------- Post added at 11:23 AM ---------- Previous post was at 10:50 AM ----------
OK now seems to be fine, try disabling google chrome (uninstall updates from that app and dissable automatic updates from playstore), enable chrome again but don't install update for that. Its back to normal for me, we need to wait for fix for google chrome
Click to expand...
Click to collapse
My C also stopped accepting my known-good PIN. No choice but reset , but the cause remains a mystery. Does anyone have a fix for a laggy external keyboard? Often (but not always) the kybd will be unavailable for login or filling form fields unless I'm quite patient. Seems to be infamous BT lag and is the only annoying thing about my C. If only there were a way to speed up BT … is there?
I´m having the same issue for a long time now.
Already unlocked the bootloader and installed LineageOS, but nothing seems to fix it.
I´m going to try the damjan006´s solution with chrome to see if I got lucky and report back. Thanks in advance.
Tested removing Chrome, still the same issue, not fixed for me.
RickRand said:
My C also stopped accepting my known-good PIN. No choice but reset , but the cause remains a mystery. Does anyone have a fix for a laggy external keyboard? Often (but not always) the kybd will be unavailable for login or filling form fields unless I'm quite patient. Seems to be infamous BT lag and is the only annoying thing about my C. If only there were a way to speed up BT … is there?
Click to expand...
Click to collapse
I believe the delayed response is due to the keyboard going into a power saving state after a certain period of inactivity. It usually takes around 3 or 4 seconds for the keyboard to "wake up" and respond to my key input. It's indeed rather annoying...
Hey guys, any update here? Noticed that mine lags particularly bad when battery drops below 40%. Battery drain is real bad, and the tablet is often warm after leaving it idling all day.
Mine too
I've had problems with my Tablet since 8.1 (I think) I only use it moderately bedside so it could have been 8.
It's just slow. Try sliding the home screen and animations stick. Everything is slow. Apps load like this is a cheap 5 year old phone. I did do a factory reset but did nothing since it updated to 8.1 still. Think rolling it back is only way, and that's not fun as I understand I have to hook it up to a PC with some software.
Same happening here. Don't even chrome enabled.
I had the same problem. Suddenly, but not really directly related to the Android 8 upgrade, the tablet became very very slow. There was indeed some correlation to the battery charge (as reported elsewhere). Eventually I also ended up with the Invalid Pattern Death (productforums.google.com/forum/#!topic/Nexus/ImQsmQ8-8JA).
So I decided to downgrade to Android 7 (mmikowski.github.io/pixelc-revert-nougat/).
This was three weeks ago. So far the tablet is as good as it was before the problems began. Not sluggish anymore, not sensitive to battery charge. Hopefully it will last.
I actually did a similar reversal on my old Nexus 10 (downgraded to Android 5) and was able to make it usable again. I guess this is the same old problem as we have experienced for years with Windows machines just getting slower and slower with each update. The hardware is only able to cope with updates for a couple of years, after that the newer code updates exceed the capabilities of the old processor.
Mine is running completely fine although I bought it running Android 8.1 out of the box, I have not experienced any lags nor the pin problem. The keyboard is also fine, like the other guy said it goes into power saving mode after a while which requires some time to start back up again but only takes a few seconds.
I am quite pleased with my tablet considering that I got it for a good price and it was second-hand. Mind you I'm a light user I don't do many heavy tasks.
My Pixel C was lagging quite bad when the battery fell below 67% using stock 8.1 (locked bootloader, everything untouched). I tried reflashing the factory images, but the problem stuck around. I rooted (magisk 18.1) and installed Kernel Adiutor. The problem was obvious, the CPU would heavily throttle (under 67% battery) depending on the amount of core active (with 4 cores, they would all run at ~200 mhz, with 2 cores, about 700 mhz and with 1 core about 1100 mhz). It wasn't so terribly laggy with 1 core running at 1100 mhz, but it was still pretty slow.
To try and troubleshoot the problem I then installed LineageOS 15.1 and followmsi's kernel (https://forum.xda-developers.com/pi...p-flashable-monthly-update-zip-pixel-t3375591). To my surprise the problem remained, despite the custom ROM and custom kernel. I think there is something wrong with the 8.1 oreo kernel and the Pixel C (see google forum post here: https://productforums.google.com/forum/#!msg/nexus/x7izNIUIHeI/VO4n9l_DCAAJ ). So I tried a second solution. This time I did the following:
1. Flashed TWRP: twrp-3.2.3-0-dragon.img
2. Flashed in TWRP: Followmsi's unoffical lineageOS 16.0: lineage-16.0-20190206-UNOFFICIAL-dragon.zip
3. Flashed in TWRP: (same session, before booting into LineageOS): OpenGAPPS Arm64 Pico package: open_gapps-arm64-9.0-pico-20190302.zip (m
4. Flashed in TWRP: (same session, before booting into LineageOS): Followmsi's Android 9 custom kernel: tegra-3.18_kernel_pie_dragon_v190205_unicorn-xceed-followmsi.zip
And voila, back to full speed. In fact the tablet seems to run better than ever. After some testing I installed Magisk 18.1 (for root and to pass safetynet), and everything is running great. The CPU's now appear to be managed properly by the 9.0 kernel. I'd recommend anyone experiencing this problem to go ahead with what I outlined above. Alternatively, if you're not comfortable with custom roms, you can install the last Android 7.1 build (ryu-n2g48c-factory-0bc0ee15.zip - guide here: https://mmikowski.github.io/pixelc-revert-nougat/).
Hope this helps.
kingweee said:
My Pixel C was lagging quite bad when the battery fell below 67% using stock 8.1 (locked bootloader, everything untouched). I tried reflashing the factory images, but the problem stuck around. I rooted (magisk 18.1) and installed Kernel Adiutor. The problem was obvious, the CPU would heavily throttle (under 67% battery) depending on the amount of core active (with 4 cores, they would all run at ~200 mhz, with 2 cores, about 700 mhz and with 1 core about 1100 mhz). It wasn't so terribly laggy with 1 core running at 1100 mhz, but it was still pretty slow.
To try and troubleshoot the problem I then installed LineageOS 15.1 and followmsi's kernel (https://forum.xda-developers.com/pi...flashable-monthly-update-zip-pixel-t3375591). To my surprise the problem remained, despite the custom ROM and custom kernel. I think there is something wrong with the 8.1 oreo kernel and the Pixel C (see google forum post here: https://productforums.google.com/forum/#!msg/nexus/x7izNIUIHeI/VO4n9l_DCAAJ ). So I tried a second solution. This time I did the following:
1. Flashed TWRP: twrp-3.2.3-0-dragon.img
2. Flashed in TWRP: Followmsi's unoffical lineageOS 16.0: lineage-16.0-20190206-UNOFFICIAL-dragon.zip
3. Flashed in TWRP: (same session, before booting into LineageOS): OpenGAPPS Arm64 Pico package: open_gapps-arm64-9.0-pico-20190302.zip (m
4. Flashed in TWRP: (same session, before booting into LineageOS): Followmsi's Android 9 custom kernel: tegra-3.18_kernel_pie_dragon_v190205_unicorn-xceed-followmsi.zip
And voila, back to full speed. In fact the tablet seems to run better than ever. After some testing I installed Magisk 18.1 (for root and to pass safetynet), and everything is running great. The CPU's now appear to be managed properly by the 9.0 kernel. I'd recommend anyone experiencing this problem to go ahead with what I outlined above. Alternatively, if you're not comfortable with custom roms, you can install the last Android 7.1 build (ryu-n2g48c-factory-0bc0ee15.zip - guide here: https://mmikowski.github.io/pixelc-revert-nougat/).
Hope this helps.
Click to expand...
Click to collapse
Excellent, thanks for the share. I just installed the March update for mine, seems to be running great still. I've been lucky enough not to have the issues a lot of people have been seeing with theirs. Hoping it stays that way. Lol. Well definitely be doing this once performance takes a hit or Google stops sending monthlys for it.
I found out why (at least mine) Pixel C gets laggy. Turns out that closer to 20-25% of the battery remaining, the voltage from the battery gets to 3.8 Volts. However when the battery is full the output voltage gets to 4.22 Volts. That's very strange since the battery is designed to output 3.8 volts... Also, I've found out that if you use a non-pixel c charger, the battery doesn't charge properly. It charges very very slow and the voltage stays at 3.8 volts even when the battery is 100% charged. In my case, I was using a Oneplus 6 charger which outputs 3 amps, and the Pixel C would take a whole night to charge. Yesterday I used the Pixel C charger and the battery charged properly, and now at 100% it outputs again the needed 4.2 volts. Hope that helps.
Mein Pixel C lag ziemlich schlecht, als der Akku mit Lager 8.1 unter 67% fiel (gesperrter Bootloader, alles unberührt). Ich habe versucht, die Werksbilder zu reflashieren, aber das Problem blieb bestehen. Ich habe rooted (magisk 18.1) und Kernel Adiutor installiert. Das Problem war offensichtlich, die CPU würde stark drosseln (unter 67% der Batterie), abhängig von der Menge des aktiven Kerns (mit 4 Kernen würden sie alle bei ~ 200 MHz laufen, mit 2 Kernen etwa 700 MHz und mit 1 Kern etwa 1100) MHZ). Es war nicht so schlimm, dass 1 Core auf 1100 MHz lief, aber es war immer noch ziemlich langsam.
Um das Problem zu lösen und zu beheben, habe ich LineageOS 15.1 und den Kernel von followmsi ( https://forum.xda-developers.com/pix...pixel-t3375591) installiert). Zu meiner Überraschung blieb das Problem trotz des benutzerdefinierten ROM und des benutzerdefinierten Kernels bestehen. Ich denke, dass mit dem 8.1 oreo-Kernel und dem Pixel C etwas nicht stimmt (siehe Google-Forum hier: https://productforums.google.com/for...I/VO4n9l_DCAAJ ). Also versuchte ich eine zweite Lösung. Diesmal habe ich Folgendes getan:
1. Flashed TWRP: twrp-3.2.3-0-dragon.img
2. Flashed in TWRP: Followmsis unoffical lineageOS 16.0: lineage-16.0-20190206-UNOFFICIAL-dragon.zip
3. Flashed in TWRP : (gleiche Sitzung vor dem Starten in LineageOS): OpenGAPPS Arm64 Pico-Paket: open_gapps-arm64-9.0-pico-20190302.zip (m
4. Flashed in TWRP: (gleiche Sitzung vor dem Booten in LineageOS): Followmsis Android 9-Custom-Kernel : tegra-3.18_kernel_pie_dragon_v190205_unicorn-xceed-followmsi.zip
Und voila, wieder auf vollen Touren. Tatsächlich scheint das Tablet besser zu laufen als je zuvor. Nach einigen Tests habe ich Magisk 18.1 (für root und passnet safetynet) installiert, und alles läuft bestens. Die CPU scheint nun korrekt vom 9.0-Kernel verwaltet zu werden. Ich kann jedem, der dieses Problem hat, empfehlen, mit den oben genannten Schritten fortzufahren. Wenn Sie mit benutzerdefinierten ROMs nicht vertraut sind, können Sie alternativ den letzten Android 7.1-Build installieren (ryu-n2g48c-factory-0bc0ee15.zip - Anleitung hier: https://mmikowski.github.io/pixelc-revert-nougat/ ).
Hoffe das hilft.
Click to expand...
Click to collapse
Hello,
I have the same problem with my Pixel C.
Does pixel C run stablely with LineageOS 16 and the new kernel even after a long time?
In addition, I am relatively new to Custom Rome. Could you send me the links to the kernel and the ROM?
Do I have to pay attention to anything else?
Hi,
Thank you for this tip !
I did the same, but with the latest Lineage 17.1 (Android 10). Here are the links :
1 - TWRP : https://dl.twrp.me/dragon/twrp-3.3.1-0-dragon.img.html
2 - Lineage : https://drive.google.com/drive/folders/0By6p5AdQfavBUTZmNWJoaU1iazg ("lineage-17.1-20200113-UNOFFICIAL-dragon.zip")
3 - OpenGApps : https://www.cyanogenmods.org/downloads/pico-opengapps-for-android-10-arm64/
4 - Kernel : https://drive.google.com/drive/folders/18cqluw7lp1S720QdV0p-OtHfY9MNpSwn ("tegra-3.18_kernel_10_dragon_v191220_unicorn-xceed-followmsi.zip")
Enjoy !
Running lineage 15.1 with microg and had this problem. Flashed the unified oreo kernel and problem solved!
My Pixel C has suddenly become afflicted with the "My cores are all locked at 204MHz" issue. For me it starts when the battery reaches around 70% charge and it's so crippling.
I read the advice here but was too wimpy to go with a higher ROM than 8.1 and decided first to try downgrading to Android 7.1.
One thing I found really difficult was getting fastboot to work because "fastboot devices" wasn't showing any devices. Somewhere on the internet I discovered that when your device is in fastboot mode, it actually has DIFFERENT hardware identifiers than when it is in normal mode.
The android_winusb.inf in the official google distribution and also the "15 second" distribution also doesn't contain any hardware identifiers for my device so I had to add them manually before Windows 10 could detect and install the drivers for fastboot *sigh*
I also discovered that when trying to use "fastboot flash" the operation always failed. I found (on the internet again) that before you can flash you need to "fastboot oem unlock" before it will succeed.
Finally I couldn't manage to get the 7.1 ROM to load because of some other nonsense where the latest fastboot has some new feature that prevents it (ARGHHHHH). After more searching I found that I had to download an older platform tools (v27) and using that... FINALLY I managed to write the 7.1 ROM to the device.
It has been a long ad very tiring road but now hopefully my Pixel C will perform how it is supposed to. I've posted mostly because I couldn't find this kind of troubleshooting information (in one place) anywhere myself and hopefully it might save some other Pixel C owners the frustrations I encountered
Ulunyth said:
Hi,
Thank you for this tip !
I did the same, but with the latest Lineage 17.1 (Android 10). Here are the links :
1 - TWRP : https://dl.twrp.me/dragon/twrp-3.3.1-0-dragon.img.html
2 - Lineage : https://drive.google.com/drive/folders/0By6p5AdQfavBUTZmNWJoaU1iazg ("lineage-17.1-20200113-UNOFFICIAL-dragon.zip")
3 - OpenGApps : https://www.cyanogenmods.org/downloads/pico-opengapps-for-android-10-arm64/
4 - Kernel : https://drive.google.com/drive/folders/18cqluw7lp1S720QdV0p-OtHfY9MNpSwn ("tegra-3.18_kernel_10_dragon_v191220_unicorn-xceed-followmsi.zip")
Enjoy !
Click to expand...
Click to collapse
This solved everything that I wanted to fix, I was so annoyed that wipes and different ROMs couldn't make a difference. Thanks!
Ulunyth said:
Hi,
Thank you for this tip !
I did the same, but with the latest Lineage 17.1 (Android 10). Here are the links :
...
Enjoy !
Click to expand...
Click to collapse
Following this with the various listed files in their latest version. Working well, just have the odd now and then reboot. All else is good.
I own the Pixel C since launch day in 2015. It was smooth and fast first years but after this years it becomes laggy and slow.
I tried some Custom ROMs and else but nothing changed. Finally I read this thread and follow flash Lineage 17 and Tegra 3.18 Kernel and it seems back to the speed and smooth of first years.
I'm very happy now : )
Related
https://gist.github.com/PerceptionPointTeam/18b1e86d1c0f8531ff8f
Don't know if it works. But even on i7 it takes 30 minutes.
Got it from here (sorry, it's german): http://www.heise.de/newsticker/meld...anfaellig-fuer-Rechte-Trickserei-3076663.html
Edit: http://perception-point.io/2016/01/1...cve-2016-0728/ (thanks to T0m93 for the link)
Any comments?
Here the exploit in english:
http://perception-point.io/2016/01/...f-a-linux-kernel-vulnerability-cve-2016-0728/
veeroohre said:
https://gist.github.com/PerceptionPointTeam/18b1e86d1c0f8531ff8f
Don't know if it works. But even on i7 it takes 30 minutes.
Got it from here (sorry, it's german): http://www.heise.de/newsticker/meld...anfaellig-fuer-Rechte-Trickserei-3076663.html
Any comments?
Click to expand...
Click to collapse
The article also says:
Allerdings wird dies durch Intels Schutztechniken SMAP und SMEP sowie SELinux, beziehungsweise SEAndroid auf Mobilgeräten, erschwert oder auch ganz verhindert.
Click to expand...
Click to collapse
In english (quick and dirty translation ):
But through Intels scurity techniques like SMAP and SMEP and also SELinux, or SEAndroid on mobile devices, this can´t be done easy or is prevented at all.
Click to expand...
Click to collapse
Since Amazon did also secure the aTV1 very well I doubt this will be a root solution. But who knows.
Calibaan said:
Since Amazon did also secure the aTV1 very well I doubt this will be a root solution. But who knows.
Click to expand...
Click to collapse
This exploit seems to affect a lot of devices because it already exists for a long time within the kernels. I doubt that Amazon found this flaw themselves and patched their systems without notifying the linux community, so chances are high that this might work (provided the kernel in den aTV1/2 is not too old). Someone needs to compile this stuff (ideally into an APK) and try it
It was the same with all other critical vulnerabilities in the last time, unfortunately none of them worked for the aTV1.
I believe that a special aTV/FireOS 3 related exploit must be found but my personal bet would be that the coming switch to FireOS 5 might give better chances for a root exploit. We will see. I´m still hoping for a tailored root for aTV1.
I believe the kernel on the fire tv 1 is too old for this exploit.
rbox said:
I believe the kernel on the fire tv 1 is too old for this exploit.
Click to expand...
Click to collapse
Is the kernel updated to a vulnerable version in the FireOS5 update for AFTV1?
Ludacrisvp said:
Is the kernel updated to a vulnerable version in the FireOS5 update for AFTV1?
Click to expand...
Click to collapse
Pretty sure it's still the same version.
In the above linked article they say
The vulnerability affects any Linux Kernel version 3.8 and higher.
Click to expand...
Click to collapse
According to http://kernelnewbies.org/Linux_3.8 3.8 was released on the 18th of February 2013. So I don't think the kernel of AFTV1 is too old.
Does not look good: https://plus.google.com/u/0/+AdrianLudwig/posts/KxHcLPgSPoY
Further, devices with Android 5.0 and above are protected, as the Android SELinux policy prevents 3rd party applications from reaching the affected code. Also, many devices running Android 4.4 and earlier do not contain the vulnerable code introduced in linux kernel 3.8, as those newer kernel versions not common on older Android devices.
Click to expand...
Click to collapse
veeroohre said:
In the above linked article they say
According to http://kernelnewbies.org/Linux_3.8 3.8 was released on the 18th of February 2013. So I don't think the kernel of AFTV1 is too old.
Click to expand...
Click to collapse
The date a kernel is released is irrelevant when it comes to Android. Android devices only use specific kernel versions, it's not just whatever the latest is. In the case of the firetv 1, it is 3.4.0: https://github.com/androidrbox/android_kernel_amazon_bueller/blob/master/Makefile
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
1. Install TWRP
2. Boot into TWRP
3. Do a Factory Reset!
4. Copy LineageOS zip to your SDCard
5. Flash LineageOS
6. Optional: Flash Google Apps Addon (opengapps.org, arm, 4.4, nano)
7. Reboot & Enjoy
I'LL NOT PROVIDE ANY SUPPORT OR UPDATES!
IF YOU WANT SOMETHING TO BE FIXED, GRAB THE SOURCES AND DO IT YOURSELF!
Download: lineage-11-20171127-UNOFFICIAL-gtelwifi.zip
Sources: https://github.com/gtelwifi/manifest
Thanks a lot... I was wondering if there were someone concerned about porting lineage for sm-t560(gtelwifi).
Do you know if there are plans to port a newer version of lineage for this device?
leonardoramosantos said:
Thanks a lot... I was wondering if there were someone concerned about porting lineage for sm-t560(gtelwifi).
Do you know if there are plans to port a newer version of lineage for this device?
Click to expand...
Click to collapse
I don't own this device. A friend gave me his tab for a few days and that's what i got so far.
Everything else is up to the non existing community.
Thanks for your work, i will test it! appricate that you are workin for this device. Would be very nice if you could throw out a Lineage14 release, i would test for you, too @codeworkx!
This thread is not in the Tab E page https://forum.xda-developers.com/t/galaxy-tab-e
Does it work?
CarlsonHD said:
This thread is not in the Tab E page https://forum.xda-developers.com/t/galaxy-tab-e
Does it work?
Click to expand...
Click to collapse
Yep works on my very good!
Tried today, Tab is even much faster!
Thanks to codeworkx, this should be more visible
It works excellent, but I can not integrate it into Kernel Kitchen is loaded.
Been waiting for a custom ROM for this for a long time. Been running rooted stock with Nova launcher and xposed modules. This ROM is light speed in comparison. Google account recovered apps perfectly, no data loss at all. Smooth, seamless upgrade.
Top work chap. Top work. Not tried firing it up under ART yet? Any point?
Any application to have the pincer gesture?
Tab E is having an identity crisis
it clearly says its a SM-T560NU.
said it in android before I started this adventure, says it on the back of the device as well.
I used Odin 3 to flash TWRP 2.8.7.0
got there
used TWRP to flash SUv2.82 SR5
at this point I realized I had forgotten to backup the stock system
it hung at the logo screen
tried again, same result.
used twrp to try a different SU.
same result.
all that to say this weird occurrence....
I found the Lineage OS 14 rom for the SM-T560NU
flashed it
and the log literally said
this package is gtelwifiue for device smt560,smt560nu. this device is gtelwifi.
WTF??
so know I am grabbing the Lineage 11 rom for gtelwifi.
guess ill see what happens.
Jiminey.Moridin said:
it clearly says its a SM-T560NU.
said it in android before I started this adventure, says it on the back of the device as well.
I used Odin 3 to flash TWRP 2.8.7.0
got there
used TWRP to flash SUv2.82 SR5
at this point I realized I had forgotten to backup the stock system
it hung at the logo screen
tried again, same result.
used twrp to try a different SU.
same result.
all that to say this weird occurrence....
I found the Lineage OS 14 rom for the SM-T560NU
flashed it
and the log literally said
this package is gtelwifiue for device smt560,smt560nu. this device is gtelwifi.
WTF??
so know I am grabbing the Lineage 11 rom for gtelwifi.
guess ill see what happens.
Click to expand...
Click to collapse
Lineage 11 zip flash failed. it didn't specify any reason.
I can still get into TWRP. I just cant seem to find an OS itll accept.
could this have something to do with knox ?
Jiminey.Moridin said:
it clearly says its a SM-T560NU.
said it in android before I started this adventure, says it on the back of the device as well.
I used Odin 3 to flash TWRP 2.8.7.0
got there
used TWRP to flash SUv2.82 SR5
at this point I realized I had forgotten to backup the stock system
it hung at the logo screen
tried again, same result.
used twrp to try a different SU.
same result.
all that to say this weird occurrence....
I found the Lineage OS 14 rom for the SM-T560NU
flashed it
and the log literally said
this package is gtelwifiue for device smt560,smt560nu. this device is gtelwifi.
WTF??
so know I am grabbing the Lineage 11 rom for gtelwifi.
guess ill see what happens.
Click to expand...
Click to collapse
It's probably a problem of TWRP. They guy who did it made a misstake.
Just to make it clear:
This rom is only for SM-T560 (gtelwifi, Spreadtrum CPU) and not for SM-T560NU (gtelwifiue, Qualcomm CPU).
Sent from my OnePlus 5 using XDA Labs
After installing my PC doesnt recognize it anymore
The Menu-Key is also not working
Mensch, grad gesehen, dass du ja Deutsch bist
Naja, wie gesagt. Installation usw lief alles super, Tablet läuft auch fix
Allerdings erkennt mein PC jetzt das Tablet nicht mehr. Es kommt zwar der Windows Sound, dass ein Gerät angeschlossen wurde und auch das Tablet merkt, dass es angeschlossen wurde .. aber es taucht eben im Explorer nicht auf
Ebenso geht die Menü-Tatste nicht .. schmeiß es jetzt wieder runter, sehr schade :/
Flying-T said:
After installing my PC doesnt recognize it anymore
The Menu-Key is also not working
/
Click to expand...
Click to collapse
After quite some pain usiing it, Iam not recommending this rom.
Its mostly broken, many apps wont work for some reason and some buttons too
Returning to Stock Android, seems like the better choice .. :/
--- Tablet isnt recognized anymore in Odin, no way to flash it back to Stock OS ---
Stuck on this half-working Rom now ..
Flying-T said:
After quite some pain usiing it, Iam not recommending this rom.
Its mostly broken, many apps wont work for some reason and some buttons too
Returning to Stock Android, seems like the better choice .. :/
--- Tablet isnt recognized anymore in Odin, no way to flash it back to Stock OS ---
Stuck on this half-working Rom now ..
Click to expand...
Click to collapse
First of all, thank you very much, codeworkx, for working on this! I've given it a try and while I didn't find any apps that did not work, I also noticed that the menu button does not work. My primary motivation was to get off of Android 4 so that I can install Lego's Boost App on this device which requires Android 5+. Lineage OS 11.0 is still Android 4 so I knew it would not help but I wanted to learn more about LineageOS and this was the only tablet I could play with.
I just flashed it back to the stock ROM using the process described at https://forum.xda-developers.com/showthread.php?t=2283598 using the original firmware downloaded from https://samsung-firmware.org/de/model/SM-T560/ primarily because I noticed that Netflix is no longer available using LineageOS. I'll keep an eye on the development in that corner, though, maybe one day we'll have LineageOS 14.1 for this tablet with a working Netflix.
Get netflix from apkmirror.
I'll not continue to work on it because i dont own this tab. But maybe someone else will pick it up.
Sent from my OnePlus5T using XDA Labs
I have installed this rom on a SM-T560 using the proceedure detailed by the OP. Only issues I found was the recent apps button didnt work, so simply remapping the home key to carry out this function on double tap works perfectly, AOSP keyboard kept falling over, installation of Gboard solves this problem and ART will not enable correctly in the developer settings. Hey ho!
Made my tablet faster and now I have been gifted a cheap BT keyboard, its almost like a laptop.
thanks to the OP/dev for this, my hat is off to you Sir
I wanted to create a new Rom myself, but when I enter a repo sync -j20 --force-sync I get the following error:
Code:
fatal: error parsing manifest /home/marcel/.repo/local_manifests/gtelwifi.xml: not well-formed (invalid token): line 42, column 90
What could it mean?
mcc2005 said:
I wanted to create a new Rom myself, but when I enter a repo sync -j20 --force-sync I get the following error:
What could it mean?
Click to expand...
Click to collapse
Something within the xml file isn't well formated. Maybe just a missing char.
Sent from my OnePlus5T using XDA Labs
Hi all,
Since a few days I have troubles with my OnePlus 3 (bought two years ago and never have any problems).
It has random "soft" reboots (I don't see the OnePlus bios but only the ROM boot animation) or applications crashs.
I don't need to reenter my PIN code after those reboots, and apps that crashed are also randomly (sometime works, sometime not).
First time I saw the problem, I was on AOSP Extended ROM. Thinking that was a bug with the ROM, I try 3 others: LineageOS / Ressurection Remix / Omni but unfortunately the issue still here.
I also try various OnePlus firmware (OpenBeta29 and the lastest stable) but I no see differences.
So I suspect a material issue (maybe the RAM)?
But I'm not an expert in Android / device.
Someone already saw this problem?
If anybody can help me, thanks a lot. I love my OnePlus and I don't want to change it for the moment.
draccas said:
Hi all,
Since a few days I have troubles with my OnePlus 3 (bought two years ago and never have any problems).
It has random "soft" reboots (I don't see the OnePlus bios but only the ROM boot animation) or applications crashs.
I don't need to reenter my PIN code after those reboots, and apps that crashed are also randomly (sometime works, sometime not).
First time I saw the problem, I was on AOSP Extended ROM. Thinking that was a bug with the ROM, I try 3 others: LineageOS / Ressurection Remix / Omni but unfortunately the issue still here.
I also try various OnePlus firmware (OpenBeta29 and the lastest stable) but I no see differences.
So I suspect a material issue (maybe the RAM)?
But I'm not an expert in Android / device.
Someone already saw this problem?
If anybody can help me, thanks a lot. I love my OnePlus and I don't want to change it for the moment.
Click to expand...
Click to collapse
When you flash a new ROM are you restoring your apps/data from anything like titanium backup , swift or google etc , if not which gapps are you using it sounds to me like a software issue rather than ram ...
draccas said:
Hi all,
Since a few days I have troubles with my OnePlus 3 (bought two years ago and never have any problems).
It has random "soft" reboots (I don't see the OnePlus bios but only the ROM boot animation) or applications crashs.
I don't need to reenter my PIN code after those reboots, and apps that crashed are also randomly (sometime works, sometime not).
First time I saw the problem, I was on AOSP Extended ROM. Thinking that was a bug with the ROM, I try 3 others: LineageOS / Ressurection Remix / Omni but unfortunately the issue still here.
I also try various OnePlus firmware (OpenBeta29 and the lastest stable) but I no see differences.
So I suspect a material issue (maybe the RAM)?
But I'm not an expert in Android / device.
Someone already saw this problem?
If anybody can help me, thanks a lot. I love my OnePlus and I don't want to change it for the moment.
Click to expand...
Click to collapse
Without the proper logs you are sol.
Thanks for your responses.
I always do a "clean" flash in formatting all parititions.
I do not use backup/restore tools.
And I do not use Gapps nor microg. Only free apps founded on F-Droid repository.
... old school.
Concerning logs, I check on AOSP Extended and I saw a lot of "low memorry killer" or "no such memory" - but when I look the RAM, only 3.4 Gb was used on 6.
I'll try to get clean logs on my fresh install - but as I say the smartphone reboot in chain.
draccas said:
Thanks for your responses.
I always do a "clean" flash in formatting all parititions.
I do not use backup/restore tools.
And I do not use Gapps nor microg. Only free apps founded on F-Droid repository.
... old school.
Concerning logs, I check on AOSP Extended and I saw a lot of "low memorry killer" or "no such memory" - but when I look the RAM, only 3.4 Gb was used on 6.
I'll try to get clean logs on my fresh install - but as I say the smartphone reboot in chain.
Click to expand...
Click to collapse
Then I would relook at the rom you are running. And just a heads up. You will run into issues as there are core parts of android that run subpar without atleast micro g.
Are you sure about that? Is it not possible to use a pure Android without any gapps nor microg? I always done that before, and I never have issues. Howerver I try with AOSP Extended and microg: same trouble. Random reboots (sometimes 10 in 5 minutes, other times no reboots while some hours)...
So I'll try a full reset with official OxygenOS system and recovery. If the issue continue, I'll try to get proper logs.
Reverting to OxygenOS seems to resolve the problem. But I do not understand why...
Hi, I got a 2nd hand Samsung S5 model SM-G901F and compilation id MMB29M.G901FXXU1CQE3. I want to flash LineageOS on it but I'm not sure if the device is compatible. Looking into the official LOS website for compatible devices I see my device listed - I think - (https://wiki.lineageos.org/devices/kccat6) but without active development. Does the compilation ID matter? Does it really matter if I flash a LOS ROM that's not under active development? Are there alternative ROMs that I can flash on this phone? I just want to avoid GAPPS and bloatware, have some call recording functionalities and enhance my privacy.
Thanks!
Lee1010 said:
Hi, I got a 2nd hand Samsung S5 model SM-G901F and compilation id MMB29M.G901FXXU1CQE3. I want to flash LineageOS on it but I'm not sure if the device is compatible. Looking into the official LOS website for compatible devices I see my device listed - I think - (https://wiki.lineageos.org/devices/kccat6) but without active development. Does the compilation ID matter? Does it really matter if I flash a LOS ROM that's not under active development? Are there alternative ROMs that I can flash on this phone? I just want to avoid GAPPS and bloatware, have some call recording functionalities and enhance my privacy.
Thanks!
Click to expand...
Click to collapse
kccat6
Kernel Security patches stopped in april.
kurtn said:
kccat6
Kernel Security patches stopped in april.
Click to expand...
Click to collapse
Hi,
from the above Link : https://download.lineage.microg.org/kccat6/
i took the image : lineage-16.0-20211125-microG-kccat6.zip
for a test of "LineageOS 16 with microG "
and next I tried the image : e-0.19-p-20211125148133-dev-kccat6.zip from the link :
https://images.ecloud.global/dev/kccat6/
for a test of "/e/ OS" ,
both with the recovery : TWRP 3.2.3-0
on a Samsung galaxy S5 PLUS ( SM-G901F or kccat6 ) .
Both roms seem to be supported with updates
( meanwhile I made one OTA-Update successfully with both roms)
, but with both custom roms i had/have the big problem, that after shutdown from gui or via reboot -p the powerconsumption is untolerable high - if the accu capacity was 100 % before shutdown it's about 80 % an hour later.
At the moment i have installed the e/OS/ version from above and the phone is meanwhile rooted with magisk V23, which had no obvious impact on the problem with the powerconsumption.
Does anyone have an idea, if/how this problem can be fixed ?
Help woud be appreciated !
bikefreak1 said:
Hi,
from the above Link : https://download.lineage.microg.org/kccat6/
i took the image : lineage-16.0-20211125-microG-kccat6.zip
for a test of "LineageOS 16 with microG "
and next I tried the image : e-0.19-p-20211125148133-dev-kccat6.zip from the link :
https://images.ecloud.global/dev/kccat6/
for a test of "/e/ OS" ,
both with the recovery : TWRP 3.2.3-0
on a Samsung galaxy S5 PLUS ( SM-G901F or kccat6 ) .
Both roms seem to be supported with updates
( meanwhile I made one OTA-Update successfully with both roms)
, but with both custom roms i had/have the big problem, that after shutdown from gui or via reboot -p the powerconsumption is untolerable high - if the accu capacity was 100 % before shutdown it's about 80 % an hour later.
At the moment i have installed the e/OS/ version from above and the phone is meanwhile rootet with magisk V23, which had no obvious impact on the problem with the powerconsumption.
Does anyone have an idea, if/how this problem can be fixed ?
Help woud be appreciated !
Click to expand...
Click to collapse
I would not trust that battery charge level that much. It has only voltage measurement to to guess the stat of charge after a powered off period.
kurtn said:
I would not trust that battery charge level that much. It has only voltage measurement to to guess the stat of charge after a powered off period.
Click to expand...
Click to collapse
Thank you for the very fast response,
but it's not only a matter of a wrong display - if i tried the shutdown in the evening, the accu is really empty next morning - the smartphone can then not be started, there is no display, no vibration, nothing - the phone seams dead unless connected to a powersupply .
I've tried the shutdown procedure several times - as long as the mentioned custom roms are installed the accu is empty a few hours after ( the try of) a shutdown.
If i go back to the stock rom and use the same shutdown procedure the display of the accu-capacity decreases about 3 % within about 12 hours - and the phone can then be started again WITHOUT being connected to a powersupply .
I have tried this with two different accus which i had charged until 100 % before i started the tests and it was always the same effect.
Crazy, isn't it ?!
bikefreak1 said:
Thank you for the very fast response,
but it's not only a matter of a wrong display - if i tried the shutdown in the evening, the accu is really empty next morning - the smartphone can then not be started, there is no display, no vibration, nothing - the phone seams dead unless connected to a powersupply .
I've tried the shutdown procedure several times - as long as the mentioned custom roms are installed the accu is empty a few hours after ( the try of) a shutdown.
If i go back to the stock rom and use the same shutdown procedure the display of the accu-capacity decreases about 3 % within about 12 hours - and the phone can then be started again WITHOUT being connected to a powersupply .
I have tried this with two different accus which i had charged until 100 % before i started the tests and it was always the same effect.
Crazy, isn't it ?!
Click to expand...
Click to collapse
Oops. Can you try to boot into recovery and shut down from there?
i think , i tried the shutdown from recovery a few weeks ago but because I'm not absolutely shure about the result i will try this again and report later, here.
thanks and good bye !
Hi,
yesterday at 23:35 I bootet into TWRP with an displayed accu-capacity of 90% and made a ( try of ) shutdown vom TWRP via it's gui-function : Reboot --> Poweroff.
Today at 18:35 I tried to start the phone WITHOUT connected powersupply and it started into TWRP and displayed an accu-capacity of 89% - GREAT !
I think, that proves, that it's purely a softwareproblem of the installed custom-rom , or am I wrong ???
bikefreak1 said:
Hi,
yesterday at 23:35 I bootet into TWRP with an displayed accu-capacity of 90% and made a ( try of ) shutdown vom TWRP via it's gui-function : Reboot --> Poweroff.
Today at 18:35 I tried to start the phone WITHOUT connected powersupply and it started into TWRP and displayed an accu-capacity of 89% - GREAT !
I think, that proves, that it's purely a softwareproblem of the installed custom-rom , or am I wrong ???
Click to expand...
Click to collapse
Proof. Next step: find someone to fix that. Lineage.microg.org aswell as e.foundation do blind builds. Are you willing to join /e/ testing group and file a bug report in ?
Issues · e / Backlog · GitLab
GitLab Enterprise Edition
gitlab.e.foundation
Thank you for the fast response,
at the moment I'm not sure whether i fulfill the demands for a membership in an /e/ testing group - can you perhaps give me a link where i can get more information about it ?
good bye for today !
bikefreak1 said:
Thank you for the fast response,
at the moment I'm not sure whether i fulfill the demands for a membership in an /e/ testing group - can you perhaps give me a link where i can get more information about it ?
god bye for today !
Click to expand...
Click to collapse
https://gitlab.e.foundation/teams/test-team/documentation/-/wikis/home
kurtn said:
https://gitlab.e.foundation/teams/test-team/documentation/-/wikis/home
Click to expand...
Click to collapse
Hi,
when I click on the above link :
"https://gitlab.e.foundation/teams/test-team/documentation/-/wikis/home"
i get the message :
404
Page Not Found
Make sure the address is correct and the page hasn't moved.
Please contact your GitLab administrator if you think this is a mistake.
Is it sure , that the link is correct ?
Hi Guys,
I thought I'd post this here, I kind of hit something that can lead you guys /w fold 3 to excitement. Also need help and recommendation
Firstly I bought my Fold 3 a while back and is unlocked with O2 UK and Vodafone UK. It's currently rooted and no I'm not anally mad about Knox as I use an S22 ultra as my daily phone. I've managed to get Pixel Experience running on my Fold 3. However there are 2 noticeable problems listed in the table.
Hopefully this attracts a few devs who can help and sort out a few issues. Just for lols I've tried booting Android 12.1 but sadly it gets stuck in a boot loop.
Anyways I've attached several images.
Update - 05/02/23
Hi Thank you for all of your interest and suggestions. I am still working on this project but progress is slow. Please do not contact me directly!. I had a few Indian's nagging me on this project. I suggest you all wait until I get something out stable. I have bought an iPhone 14 Pro Max , moved to Cheddar in the south west of the UK and now working for a new company.
Ok for the fun stuff. I managed to get the outer screen working in conjunction with the inner screen. So when you finished with the inner screen and close it., all of the activities will push to the outer screen.
Wireless and reverse charge is now working.
Brightness is now working on both screens
RIL - working (3G, 4G, 5G, WiFi, Bluetooth) etc.
Camera Works
Still needs more testing - Please do not contact me until I fix a few more bugs. such as biometrics (Finger Print, Face Scanning) Flash light etc..
Here's a video of progress.
Cheers
Super291
What WorksWhat Doesn't WorkEverything...Flash light doesn't work, but who uses it though Biometrics ( Face Scanning, Finger Print Reader) - Screen pattern works.
nice i hope u get it to work.... but i dont think its an upgrade for ur fold ^^
(Just my opinion!) ^^
Immediately after I got my Fold 3 I tried various launchers to get it closer to a Pixel as I find the user experience on the Samsung to be quite poor compared to a Pixel. This project of yours looks promising and I hope you are able to get the remaining issues worked out.
surprised pixel experience works. What's the base made on? Maybe reach out to the developer and provide a logcat potentially to identify what the issue is.
They may be able to help but it is good progress.
I assume this isn't GSI based is it? I am curious because I would love to boot a GSI rom on my vivo x fold so I am curious about this
This isn't a GSI. Its a full port. As far as I know, I'm the only one who's working on AOSP port for now. But if devs with to help. Then I'm open to share my work.
You could try DSU loader.. If your brave that is. Basically DSU loader will allow you to some what dual boot. Essentially GSI on your phone but with your original OS. Bit like having a PC but you can dual boot with Windows and Mac.
Progress will be slow as I'm working full time but will post updates once I have everything fixed.
take a look on the link.... I'm not responsible if you phone turns into a nuclear bomb!
DSU Loader
Super291 said:
This isn't a GSI. Its a full port. As far as I know, I'm the only one who's working on AOSP port for now. But if devs with to help. Then I'm open to share my work.
You could try DSU loader.. If your brave that is. Basically DSU loader will allow you to some what dual boot. Essentially GSI on your phone but with your original OS. Bit like having a PC but you can dual boot with Windows and Mac.
Progress will be slow as I'm working full time but will post updates once I have everything fixed.
take a look on the link.... I'm not responsible if you phone turns into a nuclear bomb!
DSU Loader
Click to expand...
Click to collapse
Does it trip knox?
Super291 said:
This isn't a GSI. Its a full port. As far as I know, I'm the only one who's working on AOSP port for now. But if devs with to help. Then I'm open to share my work.
You could try DSU loader.. If your brave that is. Basically DSU loader will allow you to some what dual boot. Essentially GSI on your phone but with your original OS. Bit like having a PC but you can dual boot with Windows and Mac.
Progress will be slow as I'm working full time but will post updates once I have everything fixed.
take a look on the link.... I'm not responsible if you phone turns into a nuclear bomb!
DSU Loader
Click to expand...
Click to collapse
What device tree and kernel did you compile Pixel Experience with
cooldude20000 said:
Does it trip knox?
Click to expand...
Click to collapse
Custom roms or anything not officially made by samsung will ALWAYS trigger knox.
Super291 said:
This isn't a GSI. Its a full port. As far as I know, I'm the only one who's working on AOSP port for now. But if devs with to help. Then I'm open to share my work.
You could try DSU loader.. If your brave that is. Basically DSU loader will allow you to some what dual boot. Essentially GSI on your phone but with your original OS. Bit like having a PC but you can dual boot with Windows and Mac.
Progress will be slow as I'm working full time but will post updates once I have everything fixed.
take a look on the link.... I'm not responsible if you phone turns into a nuclear bomb!
DSU Loader
Click to expand...
Click to collapse
Hello
i saw your thread and im working also on a GSI for Galaxy Z Flip3
i build LineageOS 19.0 for this phone but i has a lot of bugs
for the low brightness (as i have this issue myself too) if you used treble gsi device tree you will know that TrebleApp has a feature called "use linear screen brightness" that will fix the low brightness for the screen, you can enable it also using props in system.prop (just apply treble patches)
for the second screen no clue , i manage to disable default screen mirroring to the second (you should not because fold screen have the same launcher for both of screens)
if you figure it out , to forgot me
Hi. Any activity of fixing bugs?
gis gibt es Neuigkeiten in Bezug auf Pixel Experience Rom für das installierte Fold. Es sieht gut aus. Schade, dass das Frontdisplay nicht reagiert würde euch sehr dankbar sein wenn es doch klappen könnte
I managed to install a working rom, almost everything works, only the brightness on the front of the display cannot be adjusted and unfortunately no google services, maybe someone has an idea how to install google services, otherwise the rom looks fine out
Andy Yan's personal builds // GSI
Download Andy Yan's personal builds // GSI for free. None
sourceforge.net
lineage-20.0-20221212-UNOFFICIAL-gsi_arm64_vS.img.xz
italo19811 said:
Ich habe es geschafft eine funktionierende Rom zu installieren, fast alles funktioniert, nur die Helligkeit auf der Vorderseite des Displays lässt sich nicht einstellen und leider keine Google-Dienste, vielleicht hat jemand eine Idee wie man Google-Dienste installiert, ansonsten sieht die Rom gut aus
Click to expand...
Click to collapse
wdys?
whassup1 said:
wdys?
Click to expand...
Click to collapse
Translated quote:
I managed to install a working rom, almost everything works, only the brightness on the front of the display cannot be adjusted and unfortunately no google services, maybe someone has an idea how to install google services, otherwise the rom looks fine out
whassup1 said:
wdys?
Click to expand...
Click to collapse
?
italo19811 said:
?
Click to expand...
Click to collapse
italo19811 said:
?
Click to expand...
Click to collapse
wdys = What Did You Say? .. lol
does anyone know of a way to install gapps later? even if the process has been installed via gsu sideloader? Tried to install twrp unfortunately I can't assign it a partition from where it should start to install the .ZIP
any new update here or a telegram channel?
Can anyone shot some photos or record a video how GSI working on Fold?
To install GSI we need to burn knox, so im afraid about use experience
russanandres said:
Can anyone shot some photos or record a video how GSI working on Fold?
To install GSI we need to burn knox, so im afraid about use experience
Click to expand...
Click to collapse
Yes because need open bootloader