Develop Bugs

[Q] tablet reboots after going to sleep

Hi.
I installed a custom ROM (CM10) yesterday but ever since then, when the screen is turned off, it will restart after about 1 minute. If I try to turn the screen on again before 1 min, it'll restart. In other words, when it goes to sleep, restart will be required. Please help me on solving this issue. I searched a lot and I thought maybe it has to do with the maximum CPU frequency, I tried changing it but didn't help.
Any ideas on how to solve this problem?

What did you wipe during the install? And what ROM did you install?
Probably to start the best thing to do is redownload the rom, do a full wipe (cache, davlik cache, data, and system), then reflash the rom.

RE
Romman0 said:
What did you wipe during the install? And what ROM did you install?
Probably to start the best thing to do is redownload the rom, do a full wipe (cache, davlik cache, data, and system), then reflash the rom.
Click to expand...
Click to collapse
Thank you for the response.
Yes I did wipe the tablet (a full wipe as you mentioned) before flashing the ROM.
First I had tried Jellytime Sosei and when I realized the problem, I tried "Build 4 Linaro Stock" from this post but still the problem exists :/ Before installing the first ROM, I had done a full wipe, but not for the second one.
Thanks again for helping me.

Try a full wipe to build 1 from the sosei thread, build 1 or 2 from the linaro thread, or the original cm10 thread. Those were the most stable for me. It's a weird issue, so it's probably a bad download or flash issue.

Its screaming bad install or bad settings, wipe twice then flash again, make sure to change nothing for speed, governor, io scheduler, and stock included kernel.
Don't even install an app for OC. It may be a huge bug showing for the first time, if we go carefully we'll find it, or get it going properly again. Occasionally the blackhole wipe used can clear up flash issues, but wipes internal sd as well.
Tapatalked from my HTC DNA

Thank you guys. I'll try what you said when I get home.
Romman0 said:
Try a full wipe to build 1 from the sosei thread, build 1 or 2 from the linaro thread, or the original cm10 thread. Those were the most stable for me. It's a weird issue, so it's probably a bad download or flash issue.
Click to expand...
Click to collapse
I'm gonna give those three that you said a try, when I get home. But, can you give me the link of the original CM10 thread that you're saying? I thought there isn't one for A100, since I didn't find it on their website. Is there a official CM10 ROM for A100?

There is no Official CM10 for the A100, Romman was referring to this link for the original CM10: http://forum.xda-developers.com/showthread.php?t=1792634

OK, after wiping everything twice and also wiping internal SD, I flashed "Build 2" from CM10 Unofficial Builds thread. Apparently this one doesn't have that bug and everything is fine, but the problem is that it's buggy and clock doesn't show well and when you press recent apps button, the overlay doesn't cover the bottom of the screen. So, I'm gonna try and flash Build 1 or maybe newer Builds and see what I get.
But is there a work around for the clock and other bugs problem in Build 2?

aminbandali said:
OK, after wiping everything twice and also wiping internal SD, I flashed "Build 2" from CM10 Unofficial Builds thread. Apparently this one doesn't have that bug and everything is fine, but the problem is that it's buggy and clock doesn't show well and when you press recent apps button, the overlay doesn't cover the bottom of the screen. So, I'm gonna try and flash Build 1 or maybe newer Builds and see what I get.
But is there a work around for the clock and other bugs problem in Build 2?
Click to expand...
Click to collapse
There isn't one, no, but it was corrected in B4. I think. I'm building this stuff without the device so I can only go by reports. You're reporting issues that no one else has, is your device functional otherwise? Like is it ok on a stock Rom? Using the correct gapps, any other changes or mods?
Tapatalked from my HTC DNA

pio_masaki said:
There isn't one, no, but it was corrected in B4. I think. I'm building this stuff without the device so I can only go by reports. You're reporting issues that no one else has, is your device functional otherwise? Like is it ok on a stock Rom? Using the correct gapps, any other changes or mods?
Tapatalked from my HTC DNA
Click to expand...
Click to collapse
It was totally OK on the stock ROM and this never had happened, not even once.
I'm using the gapps that I got from your CM10 ROMs thread, which is apps for v 4.1.2. I haven't changed ANYTHING else in the tablet, no mods or customization at all... :/
P.S. I tried Build 4 again, this time I fully wiped everything before flashing, but again, the bug still exists. gonna try some other guys' ROM to see if the problem is with this ROM or it's from my device.

aminbandali said:
It was totally OK on the stock ROM and this never had happened, not even once.
I'm using the gapps that I got from your CM10 ROMs thread, which is apps for v 4.1.2. I haven't changed ANYTHING else in the tablet, no mods or customization at all... :/
P.S. I tried Build 4 again, this time I fully wiped everything before flashing, but again, the bug still exists. gonna try some other guys' ROM to see if the problem is with this ROM or it's from my device.
Click to expand...
Click to collapse
If its fine on stock then its gonna be Rom or kernel, just never heard of this happening before. What governor did you use?
Tapatalked from my HTC DNA

[Q] Flashed update, now I have a blank screen

Hey all -
I have a T-Mobile Galaxy SIII with TWRP, AOKP JB Milestone 5 and GooManager. I got a pop-up for AOKP JB Milestone 6 this morning, so I downloaded it and added that file, Lean Kernel 2.9 and gapps (latest that could be downloaded) to the flash list. I set my Dalvik cache to clear before flashing anything, then rebooted the phone to flash everything. Immediately after the flash, the phone seemed to reboot, but with a blank screen. After a while, the capacitive buttons on the front started working and when I plugged the phone into my computer the file transfer program popped up.
However ... at no point can I ever get anything to display on the screen. I've tried rebooting into recovery (volume up, home button, power button) and nothing. I don't really care about the data on my phone, I have proper backups of everything. But what I can't seem to do is get it to a point where I can recover it. What are my options here if rebooting into recovery doesn't work?
Thanks!

As an addendum, the phone is clearly booted into the OS. I have a blinking notification LED that indicates a new e-mail, and calls placed to the phone cause it to ring. I just can't see .... anything on it.

I was able to get into TWRP, somehow. I took out my T-Mobile SIM card and had it plugged into USB. I held down the recovery combo and then it booted up into recovery. It also displayed the Galaxy SIII white splash screen for the first time since the bad flash. What the hell.

chuffykow said:
I was able to get into TWRP, somehow. I took out my T-Mobile SIM card and had it plugged into USB. I held down the recovery combo and then it booted up into recovery. It also displayed the Galaxy SIII white splash screen for the first time since the bad flash. What the hell.
Click to expand...
Click to collapse
so was you able to use your phone again i say go back to a nandroid you have or flash a rom that you know works good on your phone without that white screen and trouble shoot from there that it very strange indeed if you get success with the other just try posting in the ROM thread that you flashed you could possibly get more help where it happened :good:

I went back to AOKP Milestone 5 after doing a full wipe. I saw a number of graphics changes in the Milestone 6 code review, so it's possible that had something to do with it. In any case, I'm no longer panicing

Does mr6 use the 3.4 kernel? If yes, then you were using the wrong version of leankernel.

Ya its all kernel related and user error.

Aerowinder said:
Does mr6 use the 3.4 kernel? If yes, then you were using the wrong version of leankernel.
Click to expand...
Click to collapse
mt3g said:
Ya its all kernel related and user error.
Click to expand...
Click to collapse
I assumed it was user error. I just wanted to lay out the steps I took, so I could get some help on a recovery path. I thought that a JB based ROM would work with any kernel that supports JB. Looks like I was wrong.

chuffykow said:
I assumed it was user error. I just wanted to lay out the steps I took, so I could get some help on a recovery path. I thought that a JB based ROM would work with any kernel that supports JB. Looks like I was wrong.
Click to expand...
Click to collapse
Nope, JB can be AOSP, TouchWiz, 4.1, 4.2, 4.2.2, 3.0 kernel, 3.4 kernel. Just need to read and make sure you know what you're doing before just doing it. That's why I frown at people being lazy (not just you) and not reading the forums and such, and just using apps to update and flash.

mt3g said:
Nope, JB can be AOSP, TouchWiz, 4.1, 4.2, 4.2.2, 3.0 kernel, 3.4 kernel. Just need to read and make sure you know what you're doing before just doing it. That's why I frown at people being lazy (not just you) and not reading the forums and such, and just using apps to update and flash.
Click to expand...
Click to collapse
Thank's for the condescension, I appreciate being called lazy. I might not have an encyclopedic knowledge of Everything Android, but between the knowledge I do have and the details I read on the AOKP release page, I saw nothing that indicated I _couldn't_ run LeanKernel, especially when it was only a point release on the same ROM I was previously using.

I had a look at the changelog that's available on their page. It's pretty lame. http://gerrit.sudoservers.com/#/q/status:merged,n,z that one will probably have the kernel info. A good rule of thumb is when you flash a new rom, wait until the kernel is up to date (release date). For instance, don't flash a 3/01 kernel on a 4/24 rom - wait for kernel update.
I don't recommend flashing anything with the 3.4 kernel right now. Even if you manage to pull off stability, it's still laggy and eating about 3x the battery it should. This goes for the custom kernels, too. I'll put up with stability issues, but can't deal with bad battery. Already bad enough as it is. Need my phone during the day and not near a charger.

chuffykow said:
Thank's for the condescension, I appreciate being called lazy. I might not have an encyclopedic knowledge of Everything Android, but between the knowledge I do have and the details I read on the AOKP release page, I saw nothing that indicated I _couldn't_ run LeanKernel, especially when it was only a point release on the same ROM I was previously using.
Click to expand...
Click to collapse
calm down lol, you could have read up any of the kernel threads that there are some compatible issues with kernels and roms right now.

Aerowinder said:
I had a look at the changelog that's available on their page. It's pretty lame. http://gerrit.sudoservers.com/#/q/status:merged,n,z that one will probably have the kernel info. A good rule of thumb is when you flash a new rom, wait until the kernel is up to date (release date). For instance, don't flash a 3/01 kernel on a 4/24 rom - wait for kernel update.
I don't recommend flashing anything with the 3.4 kernel right now. Even if you manage to pull off stability, it's still laggy and eating about 3x the battery it should. This goes for the custom kernels, too. I'll put up with stability issues, but can't deal with bad battery. Already bad enough as it is. Need my phone during the day and not near a charger.
Click to expand...
Click to collapse
Thanks for the tip! I appreciate it.

CM11 Discussion Here. [Links/Download/Info/Discussion/More]

Please discuss all CM11 related items here until we get official nighties / another thread from shellnut. Here I will link what we have so far.
******Backup EFS partitions using recovery/freegee!******
---------------
You need the latest clockworkmod recovery. Use Flashify from the Play store to flash. Be sure to READ the installation instructions.
---------------
Download Area. Do NOT forget to read installation instructions:
Clockworkmod Recovery Image (Go to page 4): Clockworkmod Latest Recovery! Click Me!
Flashify: Flashify Play Store Link. Click me!
Downloads (Unofficial from Shellnutt2): Shellnutt2 Unofficial CM11. Click me!
New Official updates; download.cyanogenmod.org
choose LS970
Gapps (Choose CM11): CM 11 Gapps. Click Me!
-----------------------------------------
Working:
Phone Calls
SMS/MMS
Camera (Autofocus Too!) (Camera is only 8 Megapixels though.)
UI
Pretty much everything
Bugs known so far: WiFi is hit or miss. Some people has it working, some do not.
Extra info:
To install, Do the normal.
1. Place Rom/Right Gapps on internal storage
2. Download recovery from link.
3. Use Flashify to flash the new recovery
4. Be sure to backup everything important to you.
5. Did you backup? Good.
6. Backup EFS partitions using recovery/freegee!
7. Wipe normal as you would. Be sure to not wipe internal storage. Wiping system may or may not help.
8. Install rom/gapps
9. Profit. Have fun!
MikeEx Posted:
Shellnut2 has said that we are slated to go for nighties when they officially start.
If your WiFi is giving you "Association rejected" please hop on IRC and get some logcats to Shellnut2
Server: irc.freenode.net
Channel: #lg-optimus-g
Click to expand...
Click to collapse
Also, how to use ART
MikeEx Posted (Couldn't quote or it wouldn't show red on XDA app):
Remove your phone from any case and place in front of a fan where the top front and back receive air flow.
The phone will get extremely hot (80*C+) if left uncooled while ART compiles everything. This could be a total brick hazard.
Having around 200 apps could take well over 10 minutes.
ART will recompile every time you flash a new nightly.
-----------------------
Disclaimer!
No on here takes responsibilty for anything YOU do to YOUR phone. You can not blame us for anything that happens.
---------------------------
All credit here go to its respective Builders/Complilers/Owners. I am merely providing links until official support is given.

Do I have to use CWM to flash this? Has anybody used flashify on our phone? How's Wi-Fi? I'm full of Qs but I'm dying to run a 4.4 that isn't from mako sources.

HdMsTrTeCh said:
Do I have to use CWM to flash this? Has anybody used flashify on our phone? How's Wi-Fi? I'm full of Qs but I'm dying to run a 4.4 that isn't from mako sources.
Click to expand...
Click to collapse
Use CWM, I believe there's an updated version that someone built (it's in the cwm recovery thread towards the last couple pages). Flashify works on LGOG as that's what I used to flash the cwm touch img file. Wifi works on my end. I flashed the 11/30 build and then dirty flashed 12/03 build.

I realize this is probably buggy but is it worth the switch from 10.2 to use as a dd? What if I want to go back? All my backups are TWRP

Use online nandroid backup to make a CWM backup without CWM
Here: https://play.google.com/store/apps/details?id=com.h3r3t1c.onnandbup
Sent from my Bangin' LS970 on who knows what ROM

HdMsTrTeCh said:
Do I have to use CWM to flash this? Has anybody used flashify on our phone? How's Wi-Fi? I'm full of Qs but I'm dying to run a 4.4 that isn't from mako sources.
Click to expand...
Click to collapse
WiFi is hit or miss for certain people. You must use clockworkmod recovery. I will add links to op here in a min. I use flashify and it worked just fine.
-Whiplashh
"I think a ducks opinion of me is heavily influenced by whether I have bread or not."

Shellnut2 has said that we are slated to go for nighties when they officially start.
If your WiFi is giving you "Association rejected" please hop on IRC and get some logcats to Shellnut2
Server: irc.freenode.net
Channel: #lg-optimus-g

Links up. Thread cleaned up. Have fun.

jblazea50 said:
Use CWM, I believe there's an updated version that someone built (it's in the cwm recovery thread towards the last couple pages). Flashify works on LGOG as that's what I used to flash the cwm touch img file. Wifi works on my end. I flashed the 11/30 build and then dirty flashed 12/03 build.
Click to expand...
Click to collapse
Linked recovery in OP
-Whiplashh
"I think a ducks opinion of me is heavily influenced by whether I have bread or not."

Whiplashh said:
.
Click to expand...
Click to collapse
Hey add a warning to OP for using ART. Red bold letters. something like:
Remove your phone from any case and place in front of a fan where the top front and back receive air flow.
The phone will get extremely hot (80*C+) if left uncooled while ART compiles everything. This could be a total brick hazard.
Having around 200 apps could take well over 10 minutes.
ART will recompile every time you flash a new nightly.

Wifi works fine for me at home but at work it will not connect.
Sent from my LG-LS970 using Tapatalk

Basically everything worked for me except video recording and playback. Try recording a video in snapchat and see what happens.
That said, the camera works better than on the other 4.4 ROMs. No autofocus issues and no weird coloration issues, no capture rate issues either.

MikeEx said:
Hey add a warning to OP for using ART. Red bold letters. something like:
Remove your phone from any case and place in front of a fan where the top front and back receive air flow.
The phone will get extremely hot (80*C+) if left uncooled while ART compiles everything. This could be a total brick hazard.
Having around 200 apps could take well over 10 minutes.
ART will recompile every time you flash a new nightly.
Click to expand...
Click to collapse
Added it. Will add red letters tomorrow.
-Whiplashh
"I think a ducks opinion of me is heavily influenced by whether I have bread or not."

Fresh bacon up!
Sent from my LG-LS970 using Tapatalk
---------- Post added at 10:29 AM ---------- Previous post was at 09:34 AM ----------
Still can't connect to my work wifi after a dirty flash. Going to try clean here in a minute. Strange though how I can connect to some routers but not others.... They are both WPA security
Sent from my LG-LS970 using Tapatalk

Ran the 12/3 build all night last night - dirty flashed up from the latest 10.2 build just for kicks.
Initial boot the OS was just crawling (likely dirty flash issue) - 2nd boot brought everything back to life and been fine since.
Not running ART just yet - need to verify and trim down my 200 app list lol (plus I don't want to lose Xposed just yet)
3G/4G both work great
Wifi worked fine at 3 different locations
GPS worked great
Auto Focus of course works fine
USB Tether works (woot!) and no long kills my phones USB connection when un-tethering (double woot!)
BT worked fine
NFC Works
Audio book played without any audio distortions/glitches (issue in another KK rom)
Google Nav/Maps is still using the wrong voice - an issue I had in the 10.2 build which may have carried over due to dirty flashing. The other KK rom I use uses the correct voice.
Using the PA Gapps Mini-Mod package
Had to reset my battery meter setting since the 10.2 option doesn't exist (yet) in 11 - had me confused for a bit since I had >no< battery meter lol
Aside from having to use CWM, this is pretty dang slick so far.

has the updater been implemented? The one really cool thing I liked about CM

What is ART? Is it optional?

Here's the CWM -6.0.4.5.zip file for the LS970, Uploaded by shellnut
http://www.4shared.com/zip/jULzGS4j/cwm-6045-ls970.html
Here's the stock LG Optimus G camera zip (For AOSP/CM)
http://www.4shared.com/zip/6UeG0pi_/CamCM1018030.html
MMS zip
http://www.4shared.com/zip/ZMj_Eds5/Mms.html
Everything works great, even auto focus.
Today is my birthday, and I flashed my 12/5 birthday build, I couldn't be happier

MikeEx said:
Hey add a warning to OP for using ART. Red bold letters. something like:
Remove your phone from any case and place in front of a fan where the top front and back receive air flow.
The phone will get extremely hot (80*C+) if left uncooled while ART compiles everything. This could be a total brick hazard.
Having around 200 apps could take well over 10 minutes.
ART will recompile every time you flash a new nightly.
Click to expand...
Click to collapse
i've never had these issues myself, but i can see why they would arise. i think a warning or piece of advice should be mentioned stating that if someone plans on using ART, they should enable it immediately upon rom installation, before other apps are installed. that way, optimization isn't as tedious of a process

Derp

massive lags and crashes; can't fix.

I was on CyanogenMod M5 lately and everthing worked fine. After M6 was released and I flashed it my device started to behave strangly.
Basicly every action has the cance to freeze the device, making it unusable for the next 20 seconds to 2 minutes. These are the symptoms:
1. Screens goes black. Notification bar and software buttoins remain visible but unusable
2. Power button still works
3. screen goes blank eventually
4. Does not come back when power button is pressed, while still frozen.
5. Afrter a while screen can be reactivated
6. Notifcation bar is pulled down; disappears
7. phone is usable again.
I've tried a factory reset to no avail. After this I tried factory reset + flashing Omni Rom. Lastly I tried flashing OmniRom without gapps. I have no idea what i going wrong right now.
If this a known symptom for failing hardware, please let me know.
Kind regards

Maybe its because of their theme engine bug.. Might be solved in next snapshot..
Sent from my Galaxy Nexus using XDA Free mobile app

Yup, the new CM theme engine bug. Either you go back to M5 or use another ROM that doesn't have the new CM theme engine.

I went back to M4 and It did not resolve.
I'll start to backup my media folders (pictures/music/videos) before something serious happens. After this I'm going to format the sd card and flash SlimKat as a last ditch effort - maybe with another kernel.

servellia said:
I went back to M4 and It did not resolve.
I'll start to backup my media folders (pictures/music/videos) before something serious happens. After this I'm going to format the sd card and flash SlimKat as a last ditch effort - maybe with another kernel.
Click to expand...
Click to collapse
Did you do a clean install for the M4? People that updated to M6 and downgraded back to M5 without clean install still had the issues. You won't need wipe your SD card.

As clean as it can get: Factory reset. Format system. Install.
It gets worse everytime.... or my patience is dwindeling. I'm this short of grabbing my hardware-reprogramming-tool (read: hammer) and give it a few good hits.

servellia said:
As clean as it can get: Factory reset. Format system. Install.
It gets worse everytime.... or my patience is dwindeling. I'm this short of grabbing my hardware-reprogramming-tool (read: hammer) and give it a few good hits.
Click to expand...
Click to collapse
The Hardware-Altering Magically Miraculous Efficient Rectifier (patent pending) [emoji6]?
In all seriousness, this maybe a dumb question but since I didn't see you mention about wiping cache and Dalvik, have you done that while wiping data and system before flashing a new ROM?

jkleo said:
The Hardware-Altering Magically Miraculous Efficient Rectifier (patent pending) [emoji6]?
In all seriousness, this maybe a dumb question but since I didn't see you mention about wiping cache and Dalvik, have you done that while wiping data and system before flashing a new ROM?
Click to expand...
Click to collapse
Yep, done all of that.
What a shame, I love my gnex. Time to move on.

servellia said:
Yep, done all of that.
What a shame, I love my gnex. Time to move on.
Click to expand...
Click to collapse
Hmmm.. So you have tried wiping everything and flashing SlimKat and it still didn't work? I had pretty much the same symptoms as you after flashing to M6 and M5 but after I did a clean install to another ROM without the buggy CM theme engine, my phone is working fine again. And since you said your problems began after flashing the M6 build then it should be a software issue, not hardware issue.

jkleo said:
Hmmm.. So you have tried wiping everything and flashing SlimKat and it still didn't work? I had pretty much the same symptoms as you after flashing to M6 and M5 but after I did a clean install to another ROM without the buggy CM theme engine, my phone is working fine again. And since you said your problems began after flashing the M6 build then it should be a software issue, not hardware issue.
Click to expand...
Click to collapse
Excactly this. Every partition, which is accessible via Recovery has been wiped at least once in the process.
I solved this problem eventually by ordering a Nexus 5 and put the Gnex on ebay. If I can get 20 bucks out of it, at least the SPIGEN case is payed for

servellia said:
Excactly this. Every partition, which is accessible via Recovery has been wiped at least once in the process.
I solved this problem eventually by ordering a Nexus 5 and put the Gnex on ebay. If I can get 20 bucks out of it, at least the SIGMA case is payed for
Click to expand...
Click to collapse
Wow.. Well like they say, if the old doesn't go, the new doesn't come. Enjoy your Nexus 5 [emoji106]!

[ROM][P900][UNOFFICIAL] LineageOS 13.0 | Android 6.0.1 Marshmallow | 20160406

By request, I have made my own LineageOS 13.0 thread. I will work on this when I have time during the evenings and after work.
Thanks
Exynos5420 Dev Team ( @deadman96385 @thompatry @ZakooZ @Orion116 @mosimchah @joshndroid @Andmoreagain @thermskin, @javelinanddart )
@Valera1978 - Setting up the initial build and getting it to device work
@deadman96385 - For continuous support on helping me make a better ROM
@ZakooZ and @javelinanddart - For helping me fix the Camera
@deadman96385 and @javelinanddart - For helping me fix the IR blaster
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
Do not ask for ETAs. If you do, I will ignore you and your post.
SEANDROID ERROR
If you see a message at boot about Recovery or Kernel is not SEANDROID Enforcing, you can ignore it. This is just telling you that you are not running Samsung stock software. It has no effect on recovery or the ROM itself nor related to either.
Instructions
1. Install custom recovery Link
1.*I have built a new version of TWRP with the MM kernel. MTP, Vibations, ADB now work and there are performance increases. The rom will need to allow v1awifi naming for flashing in recovery. Link
2. Download the zip(s) - ROM and Google Apps additional package (optional)
3. Backup all partitions in TWRP - this will be your recovery point if things don't install correctly.
4. Full wipe all
5. Flash ROM
6. Flash GApps
Note: Please make sure you have a Lollipop bootloader. Below are the steps to flash it.
Known Issues
Lower than stock audio volumes
MHL out to TV not working
Nightlies
Latest Nightly Date: 12/23/16
Device Builds
GApps
http://opengapps.org/
Platform: ARM
Android: 6.0
Bootloader Information
You need to make sure you have a lollipop bootloader installed or else your device won't boot. Here you can go grab the latest bootloader and odin and flash it in download mode. Read all the steps before you do this.
Make sure you have a full backup because just in case you something fails.
Here are the steps to flash this via ODIN:
Reboot your tablet into download mode. Do this by first switching off the phone, then pressing and holding the volume down + home button together and then pressing the power button. Press volume up button to enter download mode.
Open ODIN on your computer. You’ll see the ID:COM box turning yellow with a COM port number upon successful connection with the tablet.
In ODIN click the BL button, select the bootloader firmware. It's a tar.md5 file.
Make sure Auto Reboot & F. Reset Time options are selected in ODIN
Click on the start button. When the process is completed your phone will reboot.
Sources
In the readme file (see device tree) all instructions for build.
LineageOS: https://github.com/LineageOS/
Device: https://github.com/exynos5420/android_device_samsung_v1awifi
Kernel: https://github.com/exynos5420/android_kernel_samsung_exynos5420
Vendor: https://github.com/exynos5420/proprietary_vendor_samsung

Over clock?
Hi Thom,
want to know if you are able to make this kernel ready for over clock. Further I use Valera s 5.11, which one is faster this or Valera's 5.11. I know that marshmallow are in generally slower then 5.11 so will it make sense to change. I have some applications + movies which do not play/work fine, need a little more performance in GPU and cpu.
Thanks for supporting this device, I love this tablet

Deltabravofoxotango said:
Hi Thom,
want to know if you are able to make this kernel ready for over clock. Further I use Valera s 5.11, which one is faster this or Valera's 5.11. I know that marshmallow are in generally slower then 5.11 so will it make sense to change. I have some applications + movies which do not play/work fine, need a little more performance in GPU and cpu.
Thanks for supporting this device, I love this tablet
Click to expand...
Click to collapse
This rom is really fast. Like faster than 5.1.1. I am still making changes and it is speeding up by the day. I would almost say it is stable and fast enough for videos and apps that you trying to run. Try tonight's nightly and give it a shot and let me know what your thoughts are.

Yes, I was hoping there's a list of launchers compatible with CyanogenMod. I always used Nova Launcher pre-root, but post-root post-adding CM, it crashes constantly to the point of unusability. But I'm not fond of the default launchers included so as I said, I was hoping there's a list somewhere. Thanks.

Thank you for the ROM. YouTube and .gif files aren't working properly in the latest nightly. Used Micro Gapp install. Also web pages very laggy, especially ones that contain a lot of ads.

Just thought I'd report that I installed the latest (4/26) over the top of the earlier april version via a "dirty" install (no wipe). Also installed the latest open gapps stock version with no error message after reboot. That's it so far...

ElsaReyes said:
Yes, I was hoping there's a list of launchers compatible with CyanogenMod. I always used Nova Launcher pre-root, but post-root post-adding CM, it crashes constantly to the point of unusability. But I'm not fond of the default launchers included so as I said, I was hoping there's a list somewhere. Thanks.
Click to expand...
Click to collapse
What device are you on? All these problems you have is not normal. Sure you're on the P900 wifi? I haven't come across one single app ,including launchers, that don't work with this ROM.

i have a problem for downloading the latest build. The link in this forum give me only 3 old builds of the rom. When i use the old link from the old post i can download the 26 apr build. I have downlaoded that one (is the same?) and installed it with latest gaps and so problems so far

thompatry said:
This rom is really fast. Like faster than 5.1.1. I am still making changes and it is speeding up by the day. I would almost say it is stable and fast enough for videos and apps that you trying to run. Try tonight's nightly and give it a shot and let me know what your thoughts are.
Click to expand...
Click to collapse
It's a completely new ROM @thompatry Much snappier and very smooth. No prob with new Gapps and setup wizard. All in all a very promising ROM. Thanks a million!

Hi I installed your latest cm 13 on my sm-p901 and it's very smooth and fast ! Thanks so much ! But I have problem with sound ! When I change the volume with up/down key , tablet freezes for a sec or when I go to settings-sound , tablet freezes, keyboard kepress sound has latency for example , what's wrong with sound ?! Thanks so much again for bringing MM to exynos variant! ?
Edit : I can't play audio files too !! What could it be related to ?? Gapps maybe?! Does anybody else have audio problem?!
Sent from my Nexus 5X using Tapatalk

thools60 said:
What device are you on? All these problems you have is not normal. Sure you're on the P900 wifi? I haven't come across one single app ,including launchers, that don't work with this ROM.
Click to expand...
Click to collapse
Yep, P900 wifi.
It's not the app though, or the rom, or any of that. It's me, technology has always and will always take a sick ammount of pleasure in royally screwing me over in all things everyone else manages perfectly fine.
But if it's me, even if I do exactly as everyone else does, the computer will probably explode in my face.

ElsaReyes said:
Yep, P900 wifi.
It's not the app though, or the rom, or any of that. It's me, technology has always and will always take a sick ammount of pleasure in royally screwing me over in all things everyone else manages perfectly fine.
But if it's me, even if I do exactly as everyone else does, the computer will probably explode in my face.
Click to expand...
Click to collapse
Did you wipe everything clean before you installed?

thools60 said:
Did you wipe everything clean before you installed?
Click to expand...
Click to collapse
Not the files. But Factory Reset, Wipe - Davik, Cache, System, whatever that fourth one listed was called.

ElsaReyes said:
Not the files. But Factory Reset, Wipe - Davik, Cache, System, whatever that fourth one listed was called.
Click to expand...
Click to collapse
Can you save you files on a flash or something?

thools60 said:
Can you save you files on a flash or something?
Click to expand...
Click to collapse
Yeah, but would that even make any difference? It takes like 10 hours to get everything back on, transfers slow, and I'd rather avoid that if this might not even work.

ElsaReyes said:
Yeah, but would that even make any difference? It takes like 10 hours to get everything back on, transfers slow, and I'd rather avoid that if this might not even work.
Click to expand...
Click to collapse
Well, if your device isn't broken in some way, I guess thats the only way to fix it.... You haven't thought about keeping your files in the cloud? 100gb Storage on Google drive is about 2 bucks a month

Anyone managed to get xposed to work? I tried a lot of builds of the app and of the binairy, but every time I open xposed and I click on something, I get a black screen and I need to restart to get my tablet working again.

The new version is very fast. I am, however, having issues with Chrome playing back media (video) and in fact while using youtube got an error message that Android was having trouble playing media. Sometimes it will play video... but often it will not.
Anyone else having that issue, or should I wipe this baby and do a clean install?

shonkin said:
The new version is very fast. I am, however, having issues with Chrome playing back media (video) and in fact while using youtube got an error message that Android was having trouble playing media. Sometimes it will play video... but often it will not.
Anyone else having that issue, or should I wipe this baby and do a clean install?
Click to expand...
Click to collapse
Same here. It's the same issue with play music. Tried everything. Clean install. Full Gapps and second time Pico Gapps and downloaded Play music from Play store. And no go. Installed older build and voila, works again. Must be ROM related.

shonkin said:
The new version is very fast. I am, however, having issues with Chrome playing back media (video) and in fact while using youtube got an error message that Android was having trouble playing media. Sometimes it will play video... but often it will not.
Anyone else having that issue, or should I wipe this baby and do a clean install?
Click to expand...
Click to collapse
thools60 said:
Same here. It's the same issue with play music. Tried everything. Clean install. Full Gapps and second time Pico Gapps and downloaded Play music from Play store. And no go. Installed older build and voila, works again. Must be ROM related.
Click to expand...
Click to collapse
I have problem with sounds too , for example when you go to settings - sound , tablet freezes for a sec , or I can't play music , there is a problem with media !
Sent from my Nexus 5X using Tapatalk