Does anyone have wifi connection issues? There's one wifi point (at work) which I cannot connect with as it'll say wifi connection failure every time. I've tried rebooting the router but it hasn't changed a thing. My Xperia phone can connect and the tablet will connect to other wifi points but just not this one. What can do I?
[ROM][V500][5.1.x][CM12.1] Official CyanogenMod 12.1
- Thread starter Deltadroid
- Start date
NFS and tilt working
After a reboot haven't had much problems. An occasional reboot but several unmounted SD-card. I think this is the reason the Pad reboots. That's how it was on stock LP anyway. Other thing is the updater can't seem to find the new version (2804). I'm downloading that while typing. We'll see how that one runs.
After a reboot haven't had much problems. An occasional reboot but several unmounted SD-card. I think this is the reason the Pad reboots. That's how it was on stock LP anyway. Other thing is the updater can't seem to find the new version (2804). I'm downloading that while typing. We'll see how that one runs.
@jimmys_
The next nightly build (20150503) contains more "black screen" fixes.
http://review.cyanogenmod.org/#/c/97077/
The next nightly build (20150503) contains more "black screen" fixes.
http://review.cyanogenmod.org/#/c/97077/
Last edited:
I have the same black screen issue where it blacks out on various applications at intermittent times. No rhyme or reason on when it occurs....
I flashed the 3 May build yesterday & have had no significant problems. The interface is buttery smooth. I had a few minor problems:
1. Some Amazon Appstore apps wouldn't install until I physically ejected the SD card (this is a known bug)
2. The splash screen is very dim and when the tablet boots up you need to turn off the screen & then turn it on again before it's bright enough to see. This bug has been present since CM11.0 as far as I can remember. Does anyone know why it happens & if there is a fix?
3. The stock Cyanogenmod Superuser app is a bit patchy at remembering which apps have been granted SU status. I installed SuperSU & everything seems fine. (Is there any reason not to install SuperSU on top of the CM SU app?)
1. Some Amazon Appstore apps wouldn't install until I physically ejected the SD card (this is a known bug)
2. The splash screen is very dim and when the tablet boots up you need to turn off the screen & then turn it on again before it's bright enough to see. This bug has been present since CM11.0 as far as I can remember. Does anyone know why it happens & if there is a fix?
3. The stock Cyanogenmod Superuser app is a bit patchy at remembering which apps have been granted SU status. I installed SuperSU & everything seems fine. (Is there any reason not to install SuperSU on top of the CM SU app?)
Last edited:
Typing "umount /storage/sdcard1" from terminal also works instead of having to physically remove the card.
The dim screen is because you need the 4.2.2 bootloader with stock cm kernel. There is a thread to flash the other bootloader.
Supersu is fine, but you need to disable built in superuser in development settings.
The dim screen is because you need the 4.2.2 bootloader with stock cm kernel. There is a thread to flash the other bootloader.
Supersu is fine, but you need to disable built in superuser in development settings.
Thanks for this, I found the thread http://forum.xda-developers.com/showthread.php?t=2762526. I have a bumped, permissive kernel and 4.4 bootloader. From what I understand I need to flash the 4.2 bootloader using TWRP then reboot into recovery. Will I then need to re-flash my CM12.1 ROM or can I just boot back into CM12.1?
PS it was a pleasant surprise to see that "tap to wake" worked, I thought that this was only with stock LG ROMs
PS it was a pleasant surprise to see that "tap to wake" worked, I thought that this was only with stock LG ROMs
Last edited:
Just to be safe do this:
Reboot to recovery
Flash 4.2.2 bootloader
Flash recovery (not necessary if recovery is already bumped)
Reboot to recovery
Flash Rom
Reboot to system
Interesting. Every time I have had the black screen bug, I was also using the web browser. Although, I have not yet experienced the problem with recent nightly builds.
Hi Deltadroid, after 1.5 months I will give the ROMS another try and hope that the "blank screen" und rebooting issue is not bothering me anymore. I was sick of clean install an reconfiguring every 2nd day ^^
My question is: I am on 4.2.2 bootloader and TWRP 2.8.5.0. Which Recovery should I use and what means "bumped"? Did I miss somehting in the last weeks. Read 12 and 12.1 Threads but were not able to find the answer. Any other changes also? Thanks in advance and still your work is awesome! Thanks for keeping our device alive!
Edit: Couldn't wait so took your v500-CWM-6.0.5.1 bumped and your GAPPS from here http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368 and the ROM froM CM Site. Now I hope, while I take everything from one hand, that I can use my tablet again
My question is: I am on 4.2.2 bootloader and TWRP 2.8.5.0. Which Recovery should I use and what means "bumped"? Did I miss somehting in the last weeks. Read 12 and 12.1 Threads but were not able to find the answer. Any other changes also? Thanks in advance and still your work is awesome! Thanks for keeping our device alive!
Edit: Couldn't wait
so took your v500-CWM-6.0.5.1 bumped and your GAPPS from here http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368 and the ROM froM CM Site. Now I hope, while I take everything from one hand, that I can use my tablet again
Last edited:
This recovery is also good for 4.2.2 bootloaders:Hi Deltadroid, after 1.5 months I will give the ROMS another try and hope that the "blank screen" und rebooting issue is not bothering me anymore. I was sick of clean install an reconfiguring every 2nd day ^^
My question is: I am on 4.2.2 bootloader and TWRP 2.8.5.0. Which Recovery should I use and what means "bumped"? Did I miss somehting in the last weeks. Read 12 and 12.1 Threads but were not able to find the answer. Any other changes also? Thanks in advance and still your work is awesome! Thanks for keeping our device alive!
Edit: Couldn't wait
http://forum.xda-developers.com/showthread.php?t=2968472
Bumped means the image (recovery or kernel in rom) is signed to look like it was signed officially by lg. This gets rid of the secure boot error message on startup. A bumped recovery does not require a bumped rom or bumped kernel.
Last edited:
Thanks, so I could have used latest TWRP (I think interface and everything is much nicer to use than CWM). But Maybe next clean install I will switch back. But even if I use this bumped recovery and CM12.1 ROM i get this secure booting error message.
Both the kernel and the recovery need to be bumped to fully get rid of the secure boot error message on startup. If you install a bumped recovery, install the cm rom, then flash the "loki kernel to bumped kernel" script, the secure boot error message on startup will be completely gone.
There is another crucial bug fix included in the next nightly (20150506) for the video driver in the v500 kernel. This might also fix the black screen bug.
http://review.cyanogenmod.org/#/c/97458/
Included is also a crucial bug fix for ipv4 specifically for v500 kernel.
http://review.cyanogenmod.org/#/c/97454/
It seems like the v500 kernel is getting some needed attention.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone