Related
For those that don't know what evervolv is, Evervolv is an AOSP (Android Open Source Project) rom. We're fully open sourced and encourage it with no restrictions. The work put into this rom is community driven and and Evervolv Project is made up of numerous members and contributors.
Right now the current source we are working on is KITKAT(Android 4.4.4).
Current version: 4.0.0p1
Current Items not working/Buggy
Updated 4-4-14
Bluetooth working --Still a WIP as some devices don't connect
Camera working --Still a WIP as the camcorder records in blue and a few minor issues
home key doesn't turn device on need to use power button--FIXED in the next nightly should be 4-5-2014
Battery draw around 50mA in sleep
Some experience SOD when hotword detect is active
Location service has stopped with Googles update looking into now
You tell me what you find.
4G Models are not currently supported
Click to expand...
Click to collapse
Evervolv Github: https://github.com/Evervolv
Evervolv Gerrit: http://review.evervolv.com/
Evervolv website: http://www.evervolv.com/
(New Site is up Check it out)
Evervolv Bug Tracker: http://bugs.evervolv.com/
(Please have discretion when reporting issues, and be descriptive / helpful. Also understand that we'll have some growing pains with this. So don't expect everything to be perfect.)
Twitter: https://www.twitter.com/wbellavance
IRC: #evervolv
Click to expand...
Click to collapse
[GPL Compliance]
Kernel Source
Click to expand...
Click to collapse
[Download]
If you already have evervolv installed you should see this build under testing if you refresh and can download that way.
No more nightlies Moved to 5.0 Lollipop
ev_tenderloin-1-23-15 Last and final for 4.0 -> Fix netflix
FLINTMAN-TWRP-touch-data_media-SELINUX-2.7.1.0-6-7-2014.zip
--This is a flashing TWRP recovery with data/media and SELINUX support. I have tested 100% of the features and everything is working great as far as i can tell. Soo
with that being said. Use at your own risk 8). Make sure you save a backup from your current recovery just in case. BACKUP BACKUP BACKUP
--Broke Vibration as i updated kernel.
Click to expand...
Click to collapse
NOTE: Recommend a clean install if moving from a previous version and or another ROM.
Flashing from cm or any other ROM will require a clean install, dirty flashes can cause random reboots and random errors
[Disclaimer]
I am not responsible for bricked devices, lost data, etc, etc. You all know the drill. BACKUP BACKUP BACKUP
Click to expand...
Click to collapse
[Special Thanks]
i would like to thank Flemmard, Jcsullins, Dorregaray, Invisiblek, Milaq, and anyone else that helped to make this happen. More great work to come.
Mitchbaria --for a 4g model to start in on this
Colchiro-- For a spare Touchpad WIFI to be able to test on one and develop at the same time
Click to expand...
Click to collapse
GAPPS
---These are the gapps i use. You should be able to use any that are KitKat compatible
http://forum.xda-developers.com/showthread.php?t=2397942
Grabbing logcats and dmesg along with last_klog.
These are helpful in figuring out what is going on
Install the sdk in you PC http://developer.android.com/sdk/index.html
Logcat
"adb shell logcat >logcat.txt"
This will run until unplugged or ctrl c and all the content will go into that file
dmesg
"adb shell cat proc/kmsg >dmesg.txt"
This will run until unplugged or ctrl c and all the content will go into that file
Last_klog
"adb shell cat proc/last_klog >lastklog.txt"
This is for if you have a reboot run this right after the device starts back up and it will get me the last dmesg from before it reboot and will help determine the cause of the reboot.
This will help me and everyone that uses this ROM as i can determine the cause of issues.
Thanks
Thank you for the continued HP Touchpad Development and support Flintman.
Cheers:highfive:
Touchpad Toolbox By Jcsullins
[ROM GUIDE]How to use the TouchPad Toolbox to install Android "The Super Easy Way"
[GAPPS][4.4.x/4.3.x] OFFICIAL 0-Day PA-GOOGLE APPS (Use Mini or Micro packages)
Thanks to both of you. For the roms and the video walk thru. I haven't tried art on the touchpad because it actually makes my Galaxy Nexus slower most of the time. And with some gapps it's even worse. Since it isn't listed as broken I am assuming you have tried it. If I may ask. What gapps did you use and what was performance like? It prevented my nexus from booting at times. Just wanna stick with what you have tried until I get use to the new data media and such. Thanks again.
Moody66 said:
Thanks to both of you. For the roms and the video walk thru. I haven't tried art on the touchpad because it actually makes my Galaxy Nexus slower most of the time. And with some gapps it's even worse. Since it isn't listed as broken I am assuming you have tried it. If I may ask. What gapps did you use and what was performance like? It prevented my nexus from booting at times. Just wanna stick with what you have tried until I get use to the new data media and such. Thanks again.
Click to expand...
Click to collapse
I haven't tested as its still a wip from Google. I do have it as broken in the op. But good to know that it boots 8)
Sent from my SCH-I545 using xda app-developers app
Added another build see OP for what was changed. I also adding in a touch recovery TWRP with data/media and SELINUX support. This will also allow you access to your webOS media folder which is know in the new build as external_sd. I have tested out all the features and everything is working great but please save a full backup from your previous recovery if you decide to use this recovery as it's still in an Alpha state.
Enjoy
flintman said:
Added another build see OP for what was changed. I also adding in a touch recovery TWRP with data/media and SELINUX support. This will also allow you access to your webOS media folder which is know in the new build as external_sd. I have tested out all the features and everything is working great but please save a full backup from your previous recovery if you decide to use this recovery as it's still in an Alpha state.
Enjoy
Click to expand...
Click to collapse
Thanks a lot for this amazing ROM and the recovery I had few bug with the reboot ... The recovery freezed and i have to manually reboot to unfreeze it ... A part from that great job Can't wait to see what you are going to bring next
And just one little request ... I love having the clock center on the status bar ... Do you think you can add it to the Evervolv project ? That's would be a great feature
Lyok0ne said:
Thanks a lot for this amazing ROM and the recovery I had few bug with the reboot ... The recovery freezed and i have to manually reboot to unfreeze it ... A part from that great job Can't wait to see what you are going to bring next
And just one little request ... I love having the clock center on the status bar ... Do you think you can add it to the Evervolv project ? That's would be a great feature
Click to expand...
Click to collapse
I have flashed with this recovery about 20 times now and only got the reboot to hang once. I'm looking into it.
Lyok0ne said:
Thanks a lot for this amazing ROM and the recovery I had few bug with the reboot ... The recovery freezed and i have to manually reboot to unfreeze it ... A part from that great job Can't wait to see what you are going to bring next
And just one little request ... I love having the clock center on the status bar ... Do you think you can add it to the Evervolv project ? That's would be a great feature
Click to expand...
Click to collapse
install xposed + gravitybox. it works like a charm and has this feature and many others.
Sent from my Nexus 4 using Tapatalk
Okay, I am doing something wrong. I have downloaded the recovery multiple times from multiple devices. I have tried installing via TWRP and manually extracting the image to /boot.
Each attempt, I get:
Checking uImage... Invalid Size
BOOT FAILED!
Please SELECT to continue
Any thoughts? I can still load my backup copy of TWRP without issue.
Update:
After purging the other copies of TWRP from /boot, the new version loads without issue. Thanks flintman!
Discovered that the TP 4G not compatible with the test 3.X Kernel yet
Hey Flintman just wanted to point out my findings after going crazy over the past couple weeks trying to figure what I was doing wrong when flashing the test Kit Kat ROMs w/3.X kernel.
Previously my TP 4G was working fine on shumash's SCHIZOID 4.2.2 ROM but I was extremely eager to try out the new 3.X kernels. I first tried out your non-data/media Evervolv 4.0.0p1 version and was unable to connect to WiFi despite repeated clean install methods and variations of cache wipes. I know that I had re-sized partitions with Tailor sufficiently for Kit Kat as warned so I then attempted to try out Invisblek's CM11 ROM. Not only was WiFi still not wanting to toggle on, but the rotation sensor was acting oppositely for landscape orientations and I was getting frequent crashing reboots just going through the UI. I then decided to try out JCSullins' updated CM10.1 ROM with his 3.0 kernel and then encountered the same behavior as Invisblek's CM11 ROM, but with even worse random touch driver issues that resulted in erratic automatic screen touches and ultimately soft-reboots.
Restoring a backup to SCHIZOID's 4.2.2 ROM worked fine to restore all functionality, but I couldn't help but think that I was still doing something wrong.
I got a hold of a normal TP (WiFi only model) and tried your latest 1-10-2014 Evervolv 4.0.0p1 ROM and was amazed to see that it was working great including WiFi (although 5GHz APs don't seem to scan as reliably as the past kernel) aside from the known issues. I tried the exact same install process on my TP 4G again just to see if anything changed, but unfortunately WiFi still wouldn't toggle and the orientation sensor behavior exhibited the same opposite landscape behavior as Invisiblek and JCSullins' ROMs.
I had thought that aside from the 3G HSPA modem in the TP 4G model chipset-wise it would be identical to the WiFi-only model so kernel 3.X developments would be complimentary across all TP devices. Unfortunately this doesn't appear to be the case and I hope with time you guys are able to work out any compatibility with the 4G model to benefit from the already terrific development that's going on with the 3.X kernel now.
I admire your guys' skills and look forward to all the improvements in store!
PS: I'd be more than happy to beta test anything you guys feel would address any compatibility issues on the TP 4G!
If we flash your twrp will it remove cwm or add another entry? I've never been able to have two recoveries working. I would much rather not have to use the power button and what not all the time in cwm but want to make sure I'm covered if something goes wrong. Thanks
Sent from my TouchPad using Tapatalk
Due to the limit of the boot directory it will remove all recoveries before installing this one.
Sent from my SCH-I545 using xda app-developers app
Sorry for the Nube question I've searched and I'm sure it's been answered already....
So I got my touchpad with ClockworkMod Recovery version 6.0.1.9 can I flash the TWRP SE data/media recovery from there? Trying with the acme installer 5ET has failed.
I do have the original 4.4 Evervolv up and running and my partitions have been updated.
Thanks
Steve
SteveoSupremo said:
Sorry for the Nube question I've searched and I'm sure it's been answered already....
So I got my touchpad with ClockworkMod Recovery version 6.0.1.9 can I flash the TWRP SE data/media recovery from there? Trying with the acme installer 5ET has failed.
I do have the original 4.4 Evervolv up and running and my partitions have been updated.
Thanks
Steve
Click to expand...
Click to collapse
So I replaced the ulimage in the boot directory and was able to install the 1/10/14 rom. So I guess I needed to search and just try a little more.
anyway -- I think it's a little slower than the first 4.4 version.... Maybe I need to reboot.... thoughts?
steve
Both using same cpu settings? Although with more things implemented it could seem slower.
---------- Post added at 01:11 AM ---------- Previous post was at 01:07 AM ----------
emph4tic said:
Hey Flintman just wanted to point out my findings after going crazy over the past couple weeks trying to figure what I was doing wrong when flashing the test Kit Kat ROMs w/3.X kernel.
Previously my TP 4G was working fine on shumash's SCHIZOID 4.2.2 ROM but I was extremely eager to try out the new 3.X kernels. I first tried out your non-data/media Evervolv 4.0.0p1 version and was unable to connect to WiFi despite repeated clean install methods and variations of cache wipes. I know that I had re-sized partitions with Tailor sufficiently for Kit Kat as warned so I then attempted to try out Invisblek's CM11 ROM. Not only was WiFi still not wanting to toggle on, but the rotation sensor was acting oppositely for landscape orientations and I was getting frequent crashing reboots just going through the UI. I then decided to try out JCSullins' updated CM10.1 ROM with his 3.0 kernel and then encountered the same behavior as Invisblek's CM11 ROM, but with even worse random touch driver issues that resulted in erratic automatic screen touches and ultimately soft-reboots.
Restoring a backup to SCHIZOID's 4.2.2 ROM worked fine to restore all functionality, but I couldn't help but think that I was still doing something wrong.
I got a hold of a normal TP (WiFi only model) and tried your latest 1-10-2014 Evervolv 4.0.0p1 ROM and was amazed to see that it was working great including WiFi (although 5GHz APs don't seem to scan as reliably as the past kernel) aside from the known issues. I tried the exact same install process on my TP 4G again just to see if anything changed, but unfortunately WiFi still wouldn't toggle and the orientation sensor behavior exhibited the same opposite landscape behavior as Invisiblek and JCSullins' ROMs.
I had thought that aside from the 3G HSPA modem in the TP 4G model chipset-wise it would be identical to the WiFi-only model so kernel 3.X developments would be complimentary across all TP devices. Unfortunately this doesn't appear to be the case and I hope with time you guys are able to work out any compatibility with the 4G model to benefit from the already terrific development that's going on with the 3.X kernel now.
I admire your guys' skills and look forward to all the improvements in store!
PS: I'd be more than happy to beta test anything you guys feel would address any compatibility issues on the TP 4G!
Click to expand...
Click to collapse
I am curious. Have you tried turning the 4g off. Like airplane mode then just turning wifi back on? Was thinking of getting one of these models to tinker with.
Moody66 said:
Both using same cpu settings? Although with more things implemented it could seem slower.
---------- Post added at 01:11 AM ---------- Previous post was at 01:07 AM ----------
Click to expand...
Click to collapse
I think it was because of sync.... it's running smooth now. after I loaded a different set of GAPPS.
Now I have to figure out the camera apk. it would help if I RTFM.... Thanks Flintman for the awesome update!
Which version of gapps is recommended for 01-10-14 version?
New Test build up which fixes vibration
emph4tic said:
Hey Flintman just wanted to point out my findings after going crazy over the past couple weeks trying to figure what I was doing wrong when flashing the test Kit Kat ROMs w/3.X kernel.
Previously my TP 4G was working fine on shumash's SCHIZOID 4.2.2 ROM but I was extremely eager to try out the new 3.X kernels. I first tried out your non-data/media Evervolv 4.0.0p1 version and was unable to connect to WiFi despite repeated clean install methods and variations of cache wipes. I know that I had re-sized partitions with Tailor sufficiently for Kit Kat as warned so I then attempted to try out Invisblek's CM11 ROM. Not only was WiFi still not wanting to toggle on, but the rotation sensor was acting oppositely for landscape orientations and I was getting frequent crashing reboots just going through the UI. I then decided to try out JCSullins' updated CM10.1 ROM with his 3.0 kernel and then encountered the same behavior as Invisblek's CM11 ROM, but with even worse random touch driver issues that resulted in erratic automatic screen touches and ultimately soft-reboots.
Restoring a backup to SCHIZOID's 4.2.2 ROM worked fine to restore all functionality, but I couldn't help but think that I was still doing something wrong.
I got a hold of a normal TP (WiFi only model) and tried your latest 1-10-2014 Evervolv 4.0.0p1 ROM and was amazed to see that it was working great including WiFi (although 5GHz APs don't seem to scan as reliably as the past kernel) aside from the known issues. I tried the exact same install process on my TP 4G again just to see if anything changed, but unfortunately WiFi still wouldn't toggle and the orientation sensor behavior exhibited the same opposite landscape behavior as Invisiblek and JCSullins' ROMs.
I had thought that aside from the 3G HSPA modem in the TP 4G model chipset-wise it would be identical to the WiFi-only model so kernel 3.X developments would be complimentary across all TP devices. Unfortunately this doesn't appear to be the case and I hope with time you guys are able to work out any compatibility with the 4G model to benefit from the already terrific development that's going on with the 3.X kernel now.
I admire your guys' skills and look forward to all the improvements in store!
PS: I'd be more than happy to beta test anything you guys feel would address any compatibility issues on the TP 4G!
Click to expand...
Click to collapse
Do you think you can get me some dmesg and logcats??
Hi everyone.
First of all, i apologize if there's an answer out there i'm looking but i cant find it anywhere of the hundreds of threads containing thousands of posts.
I bought a cracked Nexus 4 on ebay and i already fixed the screen by replacing a new one and everything is working now.
The phone was already rooted with Mako's Android L beta4 i believe and to be honest i didnt really liked it.
I know it is on its early stages and the official one from google is still far from the next month of its release and im in no rush to get it and experience until it gets more stabilized so i would rather use Cyanogenmod 11.
So i did a full wipe/factory reset, wipe partition cache, wipe dalvik cache and installed with a nightly CM 11 from 20140907.
Everything works perfectly and cant find anything thats causing problems except one thing.
When i make a phone call, the screen turns off as if i pressed the lock screen button which i didn't but the call is still ongoing and i have to press to unlock button to turn on the screen and unlock, and when i'm on the call at the dialer i cant hang up by pressing the red hang up button, neither pressing the numbers or anything. Nothing works, the dialer is frozed and the only way i can hang it up is by going on the home screen and going to notifications and hang it up from there.
I never encountered this problem before on cyanogenmod and i believe its not from it but from the installation of makos android L b4 itself from its kernel that its not allowing me to make the phone calls. That's just my opinion. Anyone has any idea of whats causing the problem?
Is there a solution? Do i have to do a fresh clean install from the beginning maybe like to stock and from there to cyanogenmod?
Please help me out guys, im loving the Nexus 4, came from the Galaxy S2 i9100M and i had no problem rooting it at all and its still with CM 11.
Thank you all for taking the time to read this, and any ideas are welcome.
ilum90 said:
Hi everyone.
First of all, i apologize if there's an answer out there i'm looking but i cant find it anywhere of the hundreds of threads containing thousands of posts.
I bought a cracked Nexus 4 on ebay and i already fixed the screen by replacing a new one and everything is working now.
The phone was already rooted with Mako's Android L beta4 i believe and to be honest i didnt really liked it.
I know it is on its early stages and the official one from google is still far from the next month of its release and im in no rush to get it and experience until it gets more stabilized so i would rather use Cyanogenmod 11.
So i did a full wipe/factory reset, wipe partition cache, wipe dalvik cache and installed with a nightly CM 11 from 20140907.
Everything works perfectly and cant find anything thats causing problems except one thing.
When i make a phone call, the screen turns off as if i pressed the lock screen button which i didn't but the call is still ongoing and i have to press to unlock button to turn on the screen and unlock, and when i'm on the call at the dialer i cant hang up by pressing the red hang up button, neither pressing the numbers or anything. Nothing works, the dialer is frozed and the only way i can hang it up is by going on the home screen and going to notifications and hang it up from there.
I never encountered this problem before on cyanogenmod and i believe its not from it but from the installation of makos android L b4 itself from its kernel that its not allowing me to make the phone calls. That's just my opinion. Anyone has any idea of whats causing the problem?
Is there a solution? Do i have to do a fresh clean install from the beginning maybe like to stock and from there to cyanogenmod?
Please help me out guys, im loving the Nexus 4, came from the Galaxy S2 i9100M and i had no problem rooting it at all and its still with CM 11.
Thank you all for taking the time to read this, and any ideas are welcome.
Click to expand...
Click to collapse
Try flashing other roms... Stock I would recommend and then test for that issue if not good or else then flash AOSP romwith good custom kernel(ak , hellscore)
Rohit02 said:
Try flashing other roms... Stock I would recommend and then test for that issue if not good or else then flash AOSP romwith good custom kernel(ak , hellscore)
Click to expand...
Click to collapse
Is it possible to use hellscore kernel wit CM rom?
Sorry for the noobish questions but i havent mastered when it comes to rooting and all.
I never installed any rom besides CM.
ilum90 said:
Is it possible to use hellscore kernel wit CM rom?
Sorry for the noobish questions but i havent mastered when it comes to rooting and all.
I never installed any rom besides CM.
Click to expand...
Click to collapse
yes hellscore has cm version too..
I would recommend you to flash aosp rom -any.
Rohit02 said:
yes hellscore has cm version too..
I would recommend you to flash aosp rom -any.
Click to expand...
Click to collapse
At first, i installed another rom like paranoid 4.45 20140729 and it didnt work, it got worse.
When i would make a call, the screen would turn off and couldnt get to back on and it does but not even for a sec so it kept remaining wit a screen off but the call was still going.
The next step i tried AOSP build 12 rom, with same kernel and it also didnt work. Same as before when i had CM 11.
I just installed CM 11 rom with hellscore b55 CM anykernel and it does the same thing.
My only next step based on your opinion is trying AOSP rom with hellscore kernel (not the CM version).
Is there anything else i can try if the aosp wit hellscore kernel doesnt work?
could you indicate me where to get the stock kit kat because i see versions of them and im not sure if their stock or not.
is it also possible to use stock with hellscore kernel?
Much appreciate for all the help you have given me so far.
Same problem with simple AOSP with hellscore b55 anykernel.
Any other ideas?
try this fix :
http://forum.xda-developers.com/nexus-4/help/proximity-sensor-fix-screen-replacement-t2657176
RolF2 said:
try this fix :
http://forum.xda-developers.com/nexus-4/help/proximity-sensor-fix-screen-replacement-t2657176
Click to expand...
Click to collapse
I can't believe it! After all this time, blaming on the software so hard and for the last resort I actually did dissembled my N4 to check the sensors and everything but did nothing. But dude, you solved the mystery! Everything is working perfectly now. I can't appreciate how thankful I am. Many thanks
Hi,
Any suggestion for a stable ROM ?
Thank you all
You are asking what ROM to run in the paranoid android forum section.... What rom do you think we would suggest? Paranoid android of course....
#stayparanoid
Sorry and thanks
Paranoid is by far the best rom I had
Can't live two days on the stock rom (Sony)
Anyone with OPPO find 7 is running Paranoid ROM can tell us how is it and if there are any issues . thanks
ma8ash said:
Anyone with OPPO find 7 is running Paranoid ROM can tell us how is it and if there are any issues . thanks
Click to expand...
Click to collapse
I'm using The latest version of PA 4.6 beta on my find 7 QHD as my daily driver and love it.
Haven't noticed any major issues, battery life is really good. Wifi, 3G, and bluetooth all work flawlessly. (I haven't tried LTE because I haven't got it on my mobile plan)
The only issue that I've encountered is that, on a couple of games I have, sometimes they become slow and unresponsive (family guy game and 2014), I didn't have these problems on ColorOS.
PA 4.6 is currently beta so I'm not really concernecd and I think the minor issues will be ironed out in future updates.
Thank you very much
I have tried PA 4.6 Beta 5 today
My story here
T
Paranoid and mahdi room
ma8ash said:
Anyone with OPPO find 7 is running Paranoid ROM can tell us how is it and if there are any issues . thanks
Click to expand...
Click to collapse
Had a very bumpy ride with the first installation. I think I forgot to reset to factory settings, so it might be my fault.
Second installation was better. There are certain things I don't love:
Chrome browser runs on windowed version, no matter what setting you try to change.
Battery seems very short. I need to recharge halfway through my day.
I can't get the gestures to work when the screen is off. (double tap works great, nothing else).
Everything else is buttery smooth. Maybe I'm just unlucky with a few glitches here and there.
Chrome issue happens on any ROM with floating mode implemented. Its a google chrome issue. They have fixed it in their latest beta.
#stayparanoid
I just can advice you to use PA. It's my personal favorite
PA Lollipop where?
I have searched high and low. Where can I find PA 5.0.x for my Find 7?
flemmingski said:
I have searched high and low. Where can I find PA 5.0.x for my Find 7?
Click to expand...
Click to collapse
We haven't released any pa 5.0....on any device.
#stayparanoid
Error downloading rom
Whenever I try to download the latest paranoid android rom for the find7s (qhd), I get an "error executing updater binary" message. I looked up and saw that you had to install the latest cyanogenmod nightly first, which I did, but I still couldn't get it to work. I first wiped everything (data,dalvik,cache) then I installed the cyano nightly, then I wiped the data, then I installed paranoid android and I still get the error. I am also running the latest twrp recovery (2.8.6.0). Thanks in advance for anyone that can help me out
chair96 said:
Whenever I try to download the latest paranoid android rom for the find7s (qhd), I get an "error executing updater binary" message. I looked up and saw that you had to install the latest cyanogenmod nightly first, which I did, but I still couldn't get it to work. I first wiped everything (data,dalvik,cache) then I installed the cyano nightly, then I wiped the data, then I installed paranoid android and I still get the error. I am also running the latest twrp recovery (2.8.6.0). Thanks in advance for anyone that can help me out
Click to expand...
Click to collapse
Use the legacy build.
Q&A for [ROM][OFFICIAL] CyanogenMod 12.0
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][OFFICIAL] CyanogenMod 12.0. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Running Slim LP
Hello i am running FreakSlimLP ROM based on 5.0.2 F2FS and MultiROMv30. I cant seem to install as secondary ROM. What do i have to do to run CM12 as Secondary and on F2FS? is there any app?
mobile internet
Mobile internet Not work on Russian Federation...
a whole day trying to set up mobile Internet on my tablet did not work... so sad... had to restore BackUp
Drefik said:
Mobile internet Not work on Russian Federation...
a whole day trying to set up mobile Internet on my tablet did not work... so sad... had to restore BackUp
Click to expand...
Click to collapse
There's no mobile internet, this rom is for grouper, which is WiFi only tablet.
If you mean your grouper can't connect to Wifi, it's working fine for me, on all official nightly builds.
Just flashed it. Not to much of a difference between cm12 and stock 5.0.2.
Runs fine so far. Waiting for themes and some more Cm specific futures.
I guess I'm spoiled with CM11S on my Opo.
sent using Tapatalk
FC when change keyboard
This is in reply to mate Dan Demonic in main discussion: Same for me. I can't change keyboard to a different one in 01/18 release. I also did a clean install. Thanks!
Same here. Installed swiftkey but no way to change the keyboard
Keyboard FC
fjpalacios said:
This is in reply to mate Dan Demonic in main discussion: Same for me. I can't change keyboard to a different one in 01/18 release. I also did a clean install. Thanks!
Click to expand...
Click to collapse
Just to add that in 01/19 release isn't fixed this FC yet.
I am also having the wi-fi connecting problem. Still persists even after flashing cm 12 20150120 nightly. Any help would be appreciated.
20.1 nightly installed. Keyboard bug fixed.
tamilkhadar said:
I am also having the wi-fi connecting problem. Still persists even after flashing cm 12 20150120 nightly. Any help would be appreciated.
Click to expand...
Click to collapse
I readjusted my DHCP Server in my Router that Nexus 7 will get always a new IP (v4) adress instead of a dedicated one. This solved my problem.
I guess there is still a problem with the asignment of v4 IP adresses. Check under Settings - Wi-Fi - Advanced - IP address if a v4 IP address is assigned.
Just flashed 23.1 nightly. "unfortunately system ui has stopped" all the time
:-/
sent using Tapatalk
Hi all, tanks to developers for your's incessant developing!!
I have a question: is possible to have the virtual button fix to one side of screen like smartphone version?
In my opinion this is more useful in landscape mode (horizontal) for type on keyboard and this occupy less on screen.
(I have CM12 last version 03/02, original cm kernel)
Sorry for my bad english.
Thanks all!!!
Back softkey have a strange shape
Hi, in my Nexus 7 "Grouper" the back softkey have a strange shape, it's bigger than the other softkeys. Anyone have the same problem?
I attach a screenshot with lines to show the problem.
dj_simo said:
Hi, in my Nexus 7 "Grouper" the back softkey have a strange shape, it's bigger than the other softkeys. Anyone have the same problem?
I attach a screenshot with lines to show the problem.
Click to expand...
Click to collapse
Well spotted :thumbup: didn't notice until you mentioned, mine same, back key definitely larger.
Bootloop
Guys,
Currently running CM12 nightly 03/02 and working OK. Tried to update to 04/02 flashes fine but goes into bootloop which I stopped after about 30 mins. Tried 05/02 today and the exact same thing happens. On my Grouper I am using Multirom, could this be the issue? I have checked the Multrrom thread but nothing on there. I notice from 04/02 F2FS was incorporated into the ROM, again could this be the issue. The 03/02 version that I have running OK, Multirom Manager is telling me that it has a Kexec compatible Kernel so I assume 04 and 05 would be the same. I have even tried to install it as a new ROM, but that doesn't work either. Anydody got any ideas what is causing the bootloops?
smegbat said:
Guys,
Currently running CM12 nightly 03/02 and working OK. Tried to update to 04/02 flashes fine but goes into bootloop which I stopped after about 30 mins. Tried 05/02 today and the exact same thing happens. On my Grouper I am using Multirom, could this be the issue? I have checked the Multrrom thread but nothing on there. I notice from 04/02 F2FS was incorporated into the ROM, again could this be the issue. The 03/02 version that I have running OK, Multirom Manager is telling me that it has a Kexec compatible Kernel so I assume 04 and 05 would be the same. I have even tried to install it as a new ROM, but that doesn't work either. Anydody got any ideas what is causing the bootloops?
Click to expand...
Click to collapse
Did you try flashing the multirom patched kernel with it again? I updated to 04/02 nightly yesterday but reflashed the multirom kernel with it before booting and it booted up fine.... I'm about to test f2fs later today
when updating to f2fs, what are the installation instructions, does it need to be a full clean wipe (system/data/cache/dalvik)? Or since the system is not formatted to f2fs, does all that needs to be wiped is /data and /cache, then format both to f2fs, and then install cm12 as usual?
methslushee said:
Did you try flashing the multirom patched kernel with it again? I updated to 04/02 nightly yesterday but reflashed the multirom kernel with it before booting and it booted up fine.... I'm about to test f2fs later today
Click to expand...
Click to collapse
Hi. Thanks I tried that and it doesn't work, but thanks again
methslushee said:
when updating to f2fs, what are the installation instructions, does it need to be a full clean wipe (system/data/cache/dalvik)? Or since the system is not formatted to f2fs, does all that needs to be wiped is /data and /cache, then format both to f2fs, and then install cm12 as usual?
Click to expand...
Click to collapse
The latter should be sufficient. Flashing formats /system anyway.
Remember that formatting /data will wipe your internal sdcard, so backup that to some external drive beforehand!
Hey guys,
Does anyone know why the camera has always been broken for this phone when it comes to non-official roms?
I really want to just use Cyanogenmod Lollipop from the Cyanogenmod site but the camera always crashes when trying to focus. There's often new nightly builds but it's never fixed. (I'm a few months out of date now though). Do new nightly builds indicate changes were made or is a server automatically re-compiling the sources and uploading new "builds" or something?
Can it be fixed? Is there a work-around?
The only two things I'm after is a close to stock rom with DPI settings.
Thanks!
I couldn't even get CM12 to flash.....gives me an error in twrp
Sent from my SM-G935F using XDA-Developers mobile app