Develop Bugs

M2 10 Open Sourcecode (M2 A01L)

Hi guys,
Since today Huawei delivers the open sourcecode for the drivers, I guess.
Anyone in here capable to create a nice clean AOSP ROM or anything else good for our tablet?
Search link for LTE version:
http://m.huawei.com/enmobile/consum...roid=M2-A01L&proKey=Tablets_T/Tablets/M2-A01L
Direct download for LTE version:
http://download-c.huawei.com/downlo...oadId=89345&version=347349&siteCode=worldwide
Search link for WiFi version:
http://m.huawei.com/enmobile/consum...roid=M2-A01w&proKey=Tablets_T/Tablets/M2-A01w
Direct download for WiFi version:
http://download-c.huawei.com/downlo...oadId=89346&version=347353&siteCode=worldwide
I do not have the experience with ROM building, forking, ... etc. here.

One good room would be good.

Edit. Nevermind

Anyone with the LTE version of this can you upload to a cloud link so that I can download? I would rather not waste my time having to send an email to [email protected] just to get it. Thanks

Huawei Open Source Released
Hey,
maybe it is late, i have found the open source.
the link: consumer.huawei.com/en/opensource/
and we can find m2-a01l in the tablet part, and it is on page 4.
Emm...i dont know how many people use this tablet because it is out of date.:laugh:
and i dont know if it is everything we want

whatareyou007 said:
Huawei Open Source Released
Hey,
maybe it is late, i have found the open source.
the link: consumer.huawei.com/en/opensource/
and we can find m2-a01l in the tablet part, and it is on page 4.
Emm...i dont know how many people use this tablet because it is out of date.:laugh:
and i dont know if it is everything we want
Click to expand...
Click to collapse
Hi! Thank you, i'll do an AOSP for our poor tablet, the only problem in my case, I'm unable to unlock the bootloader because i haven't in dev options "OEM unlock". If I'll pass this issue, I'll immediately start to develop the ROM.

Crypto18 said:
Hi! Thank you, i'll do an AOSP for our poor tablet, the only problem in my case, I'm unable to unlock the bootloader because i haven't in dev options "OEM unlock". If I'll pass this issue, I'll immediately start to develop the ROM.
Click to expand...
Click to collapse
Hi! Have you able to develop for our poor table? 1 stable ROM should be enough

and0ng said:
Hi! Have you able to develop for our poor table? 1 stable ROM should be enough
Click to expand...
Click to collapse
The only problem in this moment still remain unlocking bootloader. I'm searching solutions

Crypto18 said:
The only problem in this moment still remain unlocking bootloader. I'm searching solutions
Click to expand...
Click to collapse
Yeah it's a pain to unlock the bootloader. But since I need to install Google Workspace device policy I have no other option

@Crypto18 - There is a possibilty to unlock the bootloader by using dc-unlocker - amount about 4 Euro. I had success in doing so a year ago. It would be very nice to get an AOSP-ROM für the tablet.

I think, I unlocked it with dc-unlocker, too, four years ago or so.
I would be happy to have any clean/empty/fresh AOSP ROM for this tablet, as up to today it is still fast and really usable.
If you need any help, I would also be eager to learn how to do it (building a ROM). @Crypto18

Crypto18 said:
Hi! Thank you, i'll do an AOSP for our poor tablet, the only problem in my case, I'm unable to unlock the bootloader because i haven't in dev options "OEM unlock". If I'll pass this issue, I'll immediately start to develop the ROM.
Click to expand...
Click to collapse
I did the DC-unlocker thing today as described in the sticky, so it still works. Somebody in this thread mentioned that it worked for him without the OEM unlock option (it disappeared in EMUI 4), but to be on the safe side I had done a downgrade to EMUI 3 before (the oldest one I found didn't have a working dialer, I didn't try the landscape calculator trick to activate the manufacturere mode, but updated to a later EMUI 3 version that had a a working dialer: "Huawei MediaPad M2-801L Android 5.1.1 EMUI 3.1 B007.zip").
I am now looking for a working TWRP (see my post in the sticky thread a few minutes ago).
If you manage to unlock your bootloader, I would be willing to go the "build your own version from scratch" way with you. I have experience as embedded Linux developer one decade ago, but never did it for Android. Would be more fun to have a second person interested in this "classic" tablet.

@coocooc , @Crypto18 ,
Have you made any progress with developing a custom rom?

@coocooc - Please search for "TWRP-3.1.0-recovery-MediaPadM2-10.0-LISZT-A01L-A01W.img" in TWRP. That's the TWRP you're looking for.

rotter99 said:
@coocooc , @Crypto18 ,
Have you made any progress with developing a custom rom?
Click to expand...
Click to collapse
Crypto18 so far did not come back, and I didn't start the journey yet.
I am on the way to prepare a Linux laptop for building Android and SBC stuff, but family life does not allow to spend many hours on my pet projects.
I wrote a mail to Huawei to get the latest sources (EMUI 4), but the first level support shown on their GPL site couldn't fulfill the wish. They gave me a developer address to apply to; let's see how this ends.
gelrav said:
@coocooc - Please search for "TWRP-3.1.0-recovery-MediaPadM2-10.0-LISZT-A01L-A01W.img" in TWRP. That's the TWRP you're looking for.
Click to expand...
Click to collapse
Thanks for the hint! I will try this TWRP version tonight. Which EMUI version are you using with this TWRP (EMUI 3 or 4)? Is there something to check in the flash layout first, to succeed with this TWRP?

@coocooc - I'm using a Huawei Mediapad M2 10.W with Emui 3.1., Android 5.1.1.
If you're on Mediapad 801L, the above mentioned TWRP will not work for you!

I am using “TWRP-3.1.0-recovery-MediaPadM2-10.0-LISZT-A01L-A01W.img“ om my M2-A01W and it working without any problems.

gelrav said:
@coocooc - I'm using a Huawei Mediapad M2 10.W with Emui 3.1., Android 5.1.1.
If you're on Mediapad 801L, the above mentioned TWRP will not work for you!
Click to expand...
Click to collapse
@gelrav Oh that might be the reason for my problems as I do use the 801L version. What alternative TWRP ist available then?

coocooc said:
@gelrav Oh that might be the reason for my problems as I do use the 801L version. What alternative TWRP ist available then?
Click to expand...
Click to collapse
Funny, the name of the TWRP file suggests that it is valid for both the L and the W versions of the M2-A01.
What is exactly the problem with this file?
I unlocked both the phone und FRP on my device before installing this file.
I am on EMUI 3.1. and Android 5.1.1.

@coocooc
Maybe this link can help you getting further:
Downloads for : Huawei -All-General-Generic- | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com

[ROM][SM-T560/gtelwifi][4.4][UNOFFICIAL] LineageOS 11.0 for Samsung Galaxy Tab E

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

laggy pixel c after updates

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 : )

Rooted Note 10+ & s3 frontier die not work

Hi, ich have no idea, whats my Problem is... maybe you can help???
short explanation .. I need a firewall and an ad blocker. So OEM activated in the developer and rooted via magisk with the current rom. everything works great including banking etc but my galaxy s3 gear frontier doesn't work anymore. Just set it up, it continues endlessly. Hid the gear apps in magisk, reset the clock, and installed and reinstalled the necessary programs ... it just doesn't want to. anyone have an idea? Android 10 und magisk is neueste
Thank you

Chrischi797979 said:
Hi, ich have no idea, whats my Problem is... maybe you can help???
short explanation .. I need a firewall and an ad blocker. So OEM activated in the developer and rooted via magisk with the current rom. everything works great including banking etc but my galaxy s3 gear frontier doesn't work anymore. Just set it up, it continues endlessly. Hid the gear apps in magisk, reset the clock, and installed and reinstalled the necessary programs ... it just doesn't want to. anyone have an idea? Android 10 und magisk is neueste
Thank you
Click to expand...
Click to collapse
Im on ketan Custom Rom V7.0 rooted and both my Galaxy watch 46mm and Active 2 44mm work superb with my Note10 plus.
Maybe its time for you to try a custom rom since you already have root

Ok thx.
What a rom you take?
I wait for a Update if dosnt work, i will change to Custom. Greez from germany

Had the same issue. Went back to stock ROM in order to get my Gear S3 Frontier to successfully pair - while I was rooted, it would just get stuck on 'Finishing Pairing', no matter what I tried.

Please see post 18 in this topic
https://forum.xda-developers.com/ga...-dbt-n975fxxu3ctc9-rooted-twrp-t4072507/page2
kangaroo72 provide solution for watches
have a nice day

Chrischi797979 said:
Ok thx.
What a rom you take?
I wait for a Update if dosnt work, i will change to Custom. Greez from germany
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-note-10+/development/29-08-19-n975fds-dr-ketan-rom-t3962839

Zero development

Why no development for 7t?

-No fully functional twrp
- Some development is switching to telegram

Short: Good old times are almost gone!

Kollachi said:
Short: Good old times are almost gone!
Click to expand...
Click to collapse
Gone to the Xiaomi phones :-|

Two of the best kernel devs are putting their time into this device
---------- Post added at 12:02 PM ---------- Previous post was at 11:59 AM ----------
3 custom roms and 5 kernels=zero?
Go to the poco forums plenty of entitled users like yourselves there.

Skinpipe said:
Two of the best kernel devs are putting their time into this device
---------- Post added at 12:02 PM ---------- Previous post was at 11:59 AM ----------
3 custom roms and 5 kernels=zero?
Go to the poco forums plenty of entitled users like yourselves there.
Click to expand...
Click to collapse
Relax dude ... by zero i meant nothing when compared to other oplus devices.
Argue with your wife maybe over burnt toast rather than attacking people on forums

suvam69 said:
Relax dude ... by zero i meant nothing when compared to other oplus devices.
Argue with your wife maybe over burnt toast rather than attacking people on forums
Click to expand...
Click to collapse
You said why no development... there is, not enough for your liking jog on, I wish I had a toaster, seriously you'd like the poco forums...

suvam69 said:
Gone to the Xiaomi phones :-|
Click to expand...
Click to collapse
No, it doesn't matter which phone. I'm flashing roms since Galaxy S1 and it's not the same as in the past.
Old senior member know what about I'm talking.

Kollachi said:
No, it doesn't matter which phone. I'm flashing roms since Galaxy S1 and it's not the same as in the past.
Old senior member know what about I'm talking.
Click to expand...
Click to collapse
Me since 2014 . Good old days yep.

It's true, im guessing the reason is that all the major devs are dont have the non PRO variants... the 7 and 7T Pro have pretty decent custom ROMs with support without twrp... its just the fact that the devs dont have this device for testing I miss RR OS and Havoc OS

shaunakdsilva said:
It's true, im guessing the reason is that all the major devs are dont have the non PRO variants... the 7 and 7T Pro have pretty decent custom ROMs with support without twrp... its just the fact that the devs dont have this device for testing I miss RR OS and Havoc OS
Click to expand...
Click to collapse
I guess most of you already tried and saw that op7tPro roms are running on op7t with some minor issues . Camera is not working , fingerprint is working but it needs a bit calibration due to resolution differences between two phones . Other features already running very well . RR , Havoc , Paranoid Android and some other roms are already developing for op7tpro . I am not developer but it should be easier port from op7tpro to op7t than developing from the beginning . I am very eager to test this kind of efforts . Sometimes I am thinking that why I didn't buy op7tpro .

Somehow I can't complain with my OnePlus 7T on stock system and stock recovery with root coz I have actually everything what I need. Even without fully working TWRP. Magisk Root with YouTube Vanced, Axet's Call Recorder, BusyBox, LSpeed,MagiskHide Props Config and and few other modules is not enough?All bank apps works good and SafetyNet Pass as well using Termux and few commands to get fingerprint certification. Netflix "visible" in PlayStore etc.
What other profits can you get guys with Custom ROM? I don't think that much more than with this. If is not enough for someone always can add module RiRuCore and EdXposed for more customization.
Wysłane z mojego HD1903 przy użyciu Tapatalka

Riski3Run said:
Somehow I can't complain with my OnePlus 7T on stock system and stock recovery with root coz I have actually everything what I need. Even without fully working TWRP. Magisk Root with YouTube Vanced, Axet's Call Recorder, BusyBox, LSpeed,MagiskHide Props Config and and few other modules is not enough?All bank apps works good and SafetyNet Pass as well using Termux and few commands to get fingerprint certification. Netflix "visible" in PlayStore etc.
What other profits can you get guys with Custom ROM? I don't think that much more than with this. If is not enough for someone always can add module RiRuCore and EdXposed for more customization.
Wysłane z mojego HD1903 przy użyciu Tapatalka
Click to expand...
Click to collapse
I definetely agree with you . I am trying all custom roms and trying to use a few hours and go back to stock or beta (mostly beta because It has more features than stock) . Because there is no custom roms stable , robust and fluent like OOS . But I love to use different tastes that's why we are in XDA and we are using Oneplus which known as best brand to support custom roms and developers . I know oneplus already giving us beta per month and stable per two month . Ours is rom installing passion .

Devs got older and wiser. They don't have much time to do free stuff.

Well I think we should blame "google dynamic partition" that our device (and other device that ship with android 10) didnt get proper TWRP. You all can see forum for pixel 4/4XL also got slow development. Also device like pixel3/3xl getting slow after android 10 release compared to android 9. Google is not friendly to development anymore... day by day google slowly became apple.

awandroid89 said:
Well I think we should blame "google dynamic partition" that our device (and other device that ship with android 10) didnt get proper TWRP. You all can see forum for pixel 4/4XL also got slow development. Also device like pixel3/3xl getting slow after android 10 release compared to android 9. Google is not friendly to development anymore... day by day google slowly became apple.
Click to expand...
Click to collapse
Honestly, right now I wouldn't blame the Google changes and no TWRP. Developing is pretty much the same except a different flashing procedure.
I think it's either the developer who doesn't own the device, or they are not willing to try living without TWRP.
(Whether we like it or no, this is the future, or at least for a long time).
There are more on telegram, if you search around you should fine some good ROMs.

Yes the twrp situation is the biggest problem here it makes flashing stuff a pita and using msmtool to fix a minor issue when your phone won't boot ??

a g bell said:
using msmtool to fix a minor issue when your phone won't boot
Click to expand...
Click to collapse
Nah. You can easily flash a fastboot rom or some images of it. You don't need to use MSM if you aren't fully bricked.

True still not as noob/user friendly as zip and twrp though ?

Which fastboot roms are full working? I have test aosip and MSM-Xtended but both have bad auto brighness.