Related
The CM team has been working around the clock getting CM9 running on devices. I'm currently responsible for the Nexus S. Everything seems to be running great so far, and this ROM can easily be a daily driver for most enthusiasts. This thread will be updated until the build bot starts popping out nightly builds again.
IF YOU HAVE ANY BUGS, PLEASE WIPE DATA, REINSTALL OFF OF ROM MANAGER, AND SEE IF IT STILL OCCURS. I WILL NOT RESPOND TO BUGS IF YOU DO NOT INSTALL OFF ROM MANAGER OR YOU HAVE NOT WIPED DATA AND TESTED.
FOR EVERY BUG REPORT, PLEASE PUT THE FOLLOWING AT THE BOTTOM, OR I WILL IGNORE IT:
"I wiped data and installed off of ROM Manager and retested before reporting this bug."
Has only been tested on i9020A
Android zip (Alpha 11):
http://developer.clockworkmod.com/downloads/579/1424/cm_crespo-ota-eng.koush.zip
Google Apps addon:
http://download.clockworkmod.com/test/gapps-ics-20111125-2.zip
What doesn't work:
Choppy video playback.
MMS is apparently flaky.
Sources:
Kernel:
https://github.com/CyanogenMod/samsung-kernel-crespo/tree/ics
Device:
https://github.com/CyanogenMod/android_device_samsung_crespo/tree/ics
Proprietaries local_manifest.xml (use the typical gingerbread ones, but the ics branch of imgtec):
https://gist.github.com/1382062
CHangelog
Alpha 11:
Fix missing dictionaries.
Fix duplicate keyboards.
Add Google Wallet.
Alpha 10:
Fix signal strength.
Fix mounting usb storage on computers.
Alpha 9:
Fixed usb tether.
Fixed live wallpapers.
Fixed data usage stats.
Fixed data limits.
Alpha 8:
Fixed Gapps.
Fixed i9023 HOME button.
Fixed calendar sync.
Alpha 6/7:
Fixed Camcorder
Alpha 5:
Fixed tethering.
Fixed various missing apks.
Fixed missing apns.
Pinch to zoom fixed.
Alpha 3/4:
Don't use these
Alpha 2:
Fixed boot flash fail.
Alpha 1:
initial release
Have fun!
it's good to see.
Ah finally. A Koush ROM. Thanks man
Awesome thanks!!!
Sent from my Nexus S using XDA App
Can this build work with GLaDOS kernel?
Wow this is great. Thanks!
Nice build koush!
great have been waiting for this a long time!!
is it usable with the kernels working on kwiboos rom? francos and/or mathkids?
Whats the problem with the camcorder?
Which kernel is used?
I'll be happy if you got some further info for us.
thanks!
Koush said:
As the title says, I have uploaded my ICS build to ROM Manager and my website.
Android zip:
http://developer.clockworkmod.com/downloads/579/1382/full_crespo-ota-eng.koush.zip
Google Apps addon:
http://download.clockworkmod.com/test/gapps-ics-20111115-with-gmail-unsigned.zip
What doesn't work:
Camcorder
Facebook account sync, missing apps from market. I am fairly sure this is a build fingerprint issue. Can probably be resolved by using the fingerprint of the Galaxy Nexus, etc. Will need to wipe between changing fingerprints.
What may not work:
GPS (it's really ****ing cold outside, and I don't wanna go find out if GPS works )
Sources:
Kernel:
Needs PVR 1.8 and new multitouch reporting format (different patch from what is floating around on other threads).
https://github.com/CyanogenMod/samsung-kernel-crespo/tree/ics
Device:
This contains a bunch of leaked libs in the leakedlibs directory to fix audio/video/etc.
https://github.com/CyanogenMod/android_device_samsung_crespo/tree/ics
Proprietaries local_manifest.xml (use the typical gingerbread ones, but the ics branch of imgtec):
https://gist.github.com/1382062
Have fun!
Click to expand...
Click to collapse
Ahhh nice! Been waiting for this.
Koush is a hero...and a meme, too, I guess.
Thanks dude!
Sent from my Nexus S using Tapatalk
Have it flashed and it's the fastest AOSP ICS I ever tried lol
LKNim said:
Have it flashed and it's the fastest AOSP ICS I ever tried lol
Click to expand...
Click to collapse
Haha... How many AOSP ICS's have you tried?
Thanks Koush , great job as usual
LKNim said:
Have it flashed and it's the fastest AOSP ICS I ever tried lol
Click to expand...
Click to collapse
Is it more complete and faster than kwiboo's?
Sent from my Nexus S using Tapatalk
now we just need it for Nexus S 4g
i got stuck at google screen when try to boot up.
koush i have one little question: would you recommend using the kernel that comes with the rom or a custom kernel like glados/franco/..?
MYPaT said:
i got stuck at google screen when try to boot up.
Click to expand...
Click to collapse
Same here
1PATRIK said:
Haha... How many AOSP ICS's have you tried?
Click to expand...
Click to collapse
2 out of 3
This is the thread for the T599x variants (not the S3 mini).
We have the following ROMs available:
Stock
The following have ceased development:
CM 10.1 (09/20) Build by Unjustified Dev
CM-10.2 by Unjustified Dev
Pac Rom by Unjustified Dev
BeanStalk 4.4 by Meticulus (Still good to try out!)
CM-11 by Unjustified Dev + Exothermic
The following have active development:
AOKP4.4 by dadacup
Carbon 4.4 by Meticulus
CM-11 by dadacup
Omni 4.4 by Exothermic
VanirAOSP 4.4 by Unjustified Dev
We also have the following recoveries available:
Stock
CWM Touch Recovery
TWRP Touch Recovery
Philz Recovery
Check the links of the 4.4 based roms for more current recoveries!
Also check out this guide on how to increase space (enables link2sd) : http://forum.xda-developers.com/showthread.php?t=2596290
All credits to tys0n (for index of stock roms) and Unjustified Dev (for CM10.1, CM10.2, CM11, VanirAOSP, and his initial work on our devicies), Meticulus for (CWM, BeanStalk and Carbon, and for his continued work on our device), dadacup (for his work on AOKP and CM11) and morepr for creating the guide to enable link2sd)
-------------------------------------------------------------------------------------------------------
Use this thread as a general discussion thread.
I'll help maybe this weekend. I am busy for the week.
So I installed CM 10.1 on my phone and now it says it can't find any contacts on my SIM card. Is this just an issue with CM 10.1, or did installing it delete the contacts?
ClaireVoyant94 said:
So I installed CM 10.1 on my phone and now it says it can't find any contacts on my SIM card. Is this just an issue with CM 10.1, or did installing it delete the contacts?
Click to expand...
Click to collapse
Apparently it's an issue with jellybean rather then CM0.1; some fixes might be try inserting your sim card into a spare phone that uses a lower version of android (gingerbread/froyo/ics) or a different os and save the contacts there, and send them over text or bluetooth.
So I found another problem with CM 10.1: I can't use my SD card. It gets recognized under Settings -> Storage, but I can't play music from it, and I can't view files in it from the file browser. Is this a known issue (one that other people are experiencing) with the 9/20 build of CM 10.1 for this phone, and if so, is there a later build that fixes it?
It's not a big deal since all of my music is on an iPod I carry with me (usually), and I don't do anything else on my phone that needs more than a few MBs of space, but it's annoying.
ClaireVoyant94 said:
So I found another problem with CM 10.1: I can't use my SD card. It gets recognized under Settings -> Storage, but I can't play music from it, and I can't view files in it from the file browser. Is this a known issue (one that other people are experiencing) with the 9/20 build of CM 10.1 for this phone, and if so, is there a later build that fixes it?
It's not a big deal since all of my music is on an iPod I carry with me (usually), and I don't do anything else on my phone that needs more than a few MBs of space, but it's annoying.
Click to expand...
Click to collapse
I'm on the 09/20 build and SD card works fine. Perhaps you need to format your sd card so that its compatible with android; I believe it should be formatted to FAT32, and try using Root browser (free from play store) and go to extSdCard and the files should be there given that the sd-card is working. There are more builds after 09/20 but since the original dev has not reuploaded them to goo (or goo has deleted them by accident) we're stuck with 09/20 until I can build a version of cm myself (I'm somewhat close to it).
I have a few of these phones and they are great, I cant believe we don't have more devs on these for a clean unbloated rom. Let us know if you come up with something. :_)
Just a quick update; I'm done exams which means I could start my attempts at porting over CM10.2 again. I had some issues applying a patch needed to enable STE Hardware, so I just manualIly downloaded the files to the correct places for the time being (which should get help me get past the build-error I was seeing before). I'm compiling a build now, and hopefully I don't run into any build errors and can test in on my phone.
Exothermic said:
Just a quick update; I'm done exams which means I could start my attempts at porting over CM10.2 again. I had some issues applying a patch needed to enable STE Hardware, so I just manualIly downloaded the files to the correct places for the time being (which should get help me get past the build-error I was seeing before). I'm compiling a build now, and hopefully I don't run into any build errors and can test in on my phone.
Click to expand...
Click to collapse
Cool! Looking forward! Thanks for the update.
Sent from my SGH-T599N using XDA Premium 4 mobile app
Is pac the only legit rom available for this phone? I'd really like to see a stock version of jelly bean...
DevilDogg said:
Is pac the only legit rom available for this phone? I'd really like to see a stock version of jelly bean...
Click to expand...
Click to collapse
There is stock firmware, unless you mean an AOSP version? I don't think any of the U8500 based phones have AOSP built, so porting it over would be difficult. There's also CM10.1 available for the phone with working camera (no video camera), issues with audio at times (which requires a reboot). I'm working on CM10.2, but running into some kernel issues, so I yet have to see to how that goes.
Exothermic said:
There is stock firmware, unless you mean an AOSP version? I don't think any of the U8500 based phones have AOSP built, so porting it over would be difficult. There's also CM10.1 available for the phone with working camera (no video camera), issues with audio at times (which requires a reboot). I'm working on CM10.2, but running into some kernel issues, so I yet have to see to how that goes.
Click to expand...
Click to collapse
I managed to find an odin flashable rom somewhere that includes su so that's what I'm running in the mean time. I tried both the roms in the o.p.
Pac was pretty close to what I like in a rom but it's abandoned so there's no chance of the bugs getting fixed.
This is such a great little phone and now that metro is giving them away for free I assumed xda would be blowing up with development but I guess not...
I'll be checking this thread everyday and I'll test out any thing you come up with. really looking forward to your rom.
I managed to compile CM10.2 and it did indeed boot. I'm not yet releasing it because camera is missing. But other then that everything seems fine, does require more testing, and I've been working non-stop for a couple of hours now (it's 4am here, lol).
Edit:
Changelog:
V.1.0.0
- initial build of CM10.2
- SmartAss v2 governor (should help with battery life) (unjust already had this there, and I could add in other governors in future)
List of Current Bugs:
- missing camera (have an idea on how to fix it )
- random boot logo appears (i believe this was on pac as well, will look into it)
- torch not working (dependent on camera working as well but since camera isn't working, torch isn't working as well)
- sound issues (like CM10.1 most likely)
I'll make a new thread for this rom, once camera is working, and we could start from there. I've yet to test out calling and bluetooth.
Just a reminder; I'm learning how to dev as I'm going so please don't expect nightlies (slow upload rate + lack of free time + lack of knowledge) and fixes to be posted suddenly.
Excellent. and thanks for not adding another half baked ROM to the list.
DevilDogg said:
Excellent. and thanks for not adding another half baked ROM to the list.
Click to expand...
Click to collapse
+1
SWisaiahAG said:
+1
Click to expand...
Click to collapse
nice job @Exothermic
Camera and what not is easy haha your missing more than you know
add me on hangouts [email protected]
I'll add you to teamcanjica they work on ste devices.
Unjustified Dev said:
nice job @Exothermic
Camera and what not is easy haha your missing more than you know
add me on hangouts [email protected]
I'll add you to teamcanjica they work on ste devices.
Click to expand...
Click to collapse
Thanks, and aha, yeah I figured. Originally one of the patches for multimedia didn't go through, so I figured that was the culprit, but now that I applied and recompiling, I'm running into more build errors, but I'll get through them.
I just messaged you,
Unjustified Dev said:
nice job @Exothermic
Camera and what not is easy haha your missing more than you know
add me on hangouts [email protected]
I'll add you to teamcanjica they work on ste devices.
Click to expand...
Click to collapse
@Unjustified Dev Thanks for helping @Exothermic. I'm sure he and the whole T599 community would highly appreciate your support on getting an updated CM ROM with less bugs. Thank you again. As always if you need help with testing I'm here for you.
Sent from my SGH-T599N using XDA Premium 4 mobile app
DJVargas said:
@Unjustified Dev Thanks for helping @Exothermic. I'm sure he and the whole T599 community would highly appreciate your support on getting an updated CM ROM with less bugs. Thank you again. As always if you need help with testing I'm here for you.
Sent from my SGH-T599N using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If anyone is interested: I still have a copy of the cm-10.1-20130925-UNOFFICIAL-codinamtrgapps-jb-20130812-signed.zip with gapps files. This wast the last build i believe unjustdev was working on before he moved to PAC...this build has a functioning camera, but no video and the sound issues. I would be happy to upload, let me know.
If u have the out of space issue I created this quick tutorial that it might help some of you guys if it does please click thanks
http://forum.xda-developers.com/showthread.php?t=2596290
Sent from my SGH-T599N using XDA Premium 4 mobile app
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??
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!
Update from jerpelea
jerpelea said:
sorry for forgetting this info
i have updated the build guide
to flash system you have to use
fastboot -S 256M flash system system.img
br
J
Click to expand...
Click to collapse
This is now booting for me.
This thing flies on AOSP but there appears to be something wrong with the baseband info / wifi info as neither of them are working
Now Booting
Once I figure out why Cell Service / WiFi doesn't work I'll post a flashable zip or systme img
ChrisJ951 said:
Now Booting
Once I figure out why Cell Service / WiFi doesn't work I'll post a flashable zip or systme img
Click to expand...
Click to collapse
I just built an image as well. Do you want to try the version I built to rule out any possible issues in the build environment? I don't want to unlock my bootloader yet...
dl12345 said:
I just built an image as well. Do you want to try the version I built to rule out any possible issues in the build environment? I don't want to unlock my bootloader yet...
Click to expand...
Click to collapse
It's okay, jerpelea said it's because they haven't released the kernel wireless driver or GSM:
jerpelea said:
This is normal for an initial release
We have not added yet kernel wireless driver or GSM
Br
J
Click to expand...
Click to collapse
dl12345 said:
I just built an image as well. Do you want to try the version I built to rule out any possible issues in the build environment? I don't want to unlock my bootloader yet...
Click to expand...
Click to collapse
Do you think following parts of these guides:
http://forum.xda-developers.com/showthread.php?t=2475352
http://forum.xda-developers.com/crossdevice-dev/sony/guide-porting-custom-roms-t2828854
We may be able to get Wifi/cell working with the stock ROM libraries? We may be better off going to CM 5.0.1 isntead of AOSP 5.1.1 if we do this