[ROM] Evervolv | 4.0.0p1 [AOSP 4.4.4] [3.4 kernel] [Nightlies] With /data/media - TouchPad Development

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??

Related

[ROM][ICS][alpha1]ICYXMAS p5wifi ICS build for GTab 8.9 GT-7310

**Last update! This thread will (shortly) be locked, and a new one will be posted With Galaxian-Soup ICS Alpha 2
Check back in a few hours!
**Update, this tread will be retired and locked come this Thursday 1/5/2012
Read between the lines, and you will see that a brand new thread in its place will be posted, complete with a yummy new alpha of ICS for our dedicated fans to enjoy... We thank you for your patience, after this alpha goes out we believe tere will be more frequent releases and postings
Stay tuned, but from what I've seen so far we have many surprises in store for our next release, and you, is ICS nirvana just around the corner? Check back on thursday!
Please don't take this to mean we've fixed every outstanding bug, but we have made major core improvements, and fixed some of the big "items"
We are seaking anyone with expeirence working HAL's and drivers.. if you are interested please PM me.
TTFN!!
** Update ** Work around for voice search
It appears that voice search is broken in several AOSP roms, during my research I managed to get voice search working, however its the older version (prior to ICS). So far it seems to work fine!
So until Google fixes (or we do hah) do this to get voice search to work
Download
Voice_Search_2.1.4
Go to the location the this file was downloaded and from a terminal (linux/mac) or the command prompt (windows)
Code:
adb shell
su (if not root)
rm /system/app/VoiceSearch.apk
reboot
Then side load adb Voice_Search_2.1.4
Code:
adb install Voice_Search_2.1.4.apk
After the install click on the microphone icon near search at the top left of the home screen, accept the permissions (you have to do this a few times, 3 by my count), don't panic if it asks a few times, it does stick.
Enjoy!
** Update** Happy New Year XDA and esp our friends with the Galaxy Tab 8.9! is this the year of the droid? We shall see!
Hey everyone I wanted to give everyone an update and general goings on! Im sorry to inform you that there will not be a New Years alpha, but we will have something for you all very soon after.
Here is a taste of what early 2012 will bring to Alpha 2.
1. We have decided to use ASOP source rather than Cyanogen Mod, this is primarily why there hasn't been a new release since xmas. After reviewing some of the initial bugs, and reflecting on what we accomplished in under 4 days, we decided we wanted the focus of this rom to become "best in breed" optimized for the Galaxy Tab 8.9. Meaning we are going to cherry pick the best features of both to create the best possible experience, with the lightest footprint, and most importantly stock ICS launcher! NoWiz, no Trebuchet. So far it has yielded very positive results.
2. Moving to ASOP and stock launcher has fixed one of the big bugs, automatic home screen orientation. I know more than a few of you were hoping this would be resolved fast, well there.. happy now?
3. MTD
4. General cleanup and optimizations have resulted in improved launcher response, it feels more fluid and less laggy...
5. Our repo is nearly finished, we are just ironing out some manifest bugs, when alpha2 arrives, so will our git links!
6. We have chosen a team name! Galaxian-Soup!
Thanks for supporting us, and we look forward to celebrating a "Droid 2012".
In the spirit of openness, if you would like to use our rom in your work please credit us in your OP and release notes. Our git repo should be up soon.
***Update*** Xmas Dinner Edition ***
Updated links to a 1.1 version, I added the livewallpaper.apks and re-zipped, no other changes.
and a newer version of Google Apps, seems to be more stable, but I've only been using it an hour, let us know!
Good Morning and Merry Christmas!
Is there something in your stocking for your GT7310? Well Santa Clause (in the form of _Motely, nycbjr, poisike, termleech (still need a team name!)) is delivering the first public alpha!
This build has been tested on the 7310 (Gtab 8.9 wifi, no 3g), and 7300 with no 3g (3g is being looked at).
Standard YMMV tag: You are flashing this at your own risk, make a nandroid backup first! If this breaks your tab we are NOT responsible.. now go play and have fun!
ICYXMAS-p5wifi-alpha1.1-cwm
icyGapps V2
Alpha V1 - ICYXMAS!
ICS 4.0.3_r1 vanilla
Rooted, deodexed,
Includes motley kernel v2e beta (see his thread for git details)
WiFi, GPS, Bluetooth
Installation:
In CWM recovery, clear your data/factory reset
Clear the dalvik cache (under advanced, or under the wipe menu in overcome cwm)
Flash the provided zip using CWM recovery
Flash gapps from CWM recovery
Bootup and setup your Google account
Install cpu control of choice, and set to interactive governor (this is required!)
​*tested SetCPU, No-frills CPU control, and Antuantu.
Give it a chance, this is a deodexed ROM and will boot slow the first time and when you use apps the first time.
Doesn't work/Limitations:
WiFi-only, but 3G will be looked at for a future version (no ETA at the moment)
Camera doesn't work, don't know when or if it can be fixed.
Some video limitations, youtube HD vids not working. Some stuttering will occur until we get the kinks out.
Charger screen doesn't look correct when you plugin without booting up (charging status)
Voice search doesn't work - May have something to do with this error:
W/PackageManager(257): Failure retrieving resources forcom.google.android.voicesearch: Resource ID #0x0
Probably more that we haven't listed, this is an alpha - please let us know.
Team members:
nycbjr - project manager, dev (first working build), testing/troubleshooting
motley - lead dev, p5 device tree, final build, kernel development
poisike - pioneer testing with other tegra ICS ROMs, testing/troubleshooting
termleech - testing
Credits:
Google - for the releasing the OS
Cyanogen Mod Team - for their awesome git repo and developers. We used the p4 device tree as a starting point.
We would like to offer our p5 device if they are interested.
Samsung for the awesome device and kernel source (for HC 3.1 at least)
digetx - for pointing us in the right direction on the green frame buffer fix!
alterbridge - for his CWM Recovery port for 73xx.
JaeCar99 - for the sweet "Blue Hallway" bootanimation
I'm looking forward to a fully working ICS rom But a good thing takes time. Keep up the good work, guys!
great to see this development start
Sent from my HTC Incredible S using Tapatalk
Do you guys want some help? I'm currently working on a rom for the nexus with some other guys but could lend a hand here as well. What's the best way to get a hold of you guys?
Sent from my Full AOSP on Maguro using Tapatalk
termleech said:
Do you guys want some help? I'm currently working on a rom for the nexus with some other guys but could lend a hand here as well. What's the best way to get a hold of you guys?
Sent from my Full AOSP on Maguro using Tapatalk
Click to expand...
Click to collapse
I would never turn down any help, I'm very new at this (long time sysadmin, but only been a droid head since march hah).
Only caveat is you will need approval from motley before I can release anything to you, for now you can PM me and I will give you my aim/gchat and offline email, but I think we should setup an IRC, or aim/gmail chat to make this go faster.
As this is coming from CM9 sources I need to contact them too, I don't want to flub any licensing issues, etc, and maybe they will want to help, or us to help them!
Awesome! Thanks fellers!
great work
_motley said:
As far as WiFi, the P4 (Galaxy 10.1) uses a broadcom 4329 and we (the P5) uses the newer 4330. This is where the challenge will come it. When I get a better look at the Android code and have a flash up and running, hopefully it will become clear if something needs to be done on the kernel side or the Android side. If we start making good progress, we will need to get a git setup for our P5 stuff so we can share changes and files etc.
Click to expand...
Click to collapse
I don't know... I just flashed my P7300 with P7500 rom and wifi driver loads just fine. I only edited the build.prop and used a kernel from overcome rom, i didn't touch anything else. Also if you look in \system\etc\wifi you will see that both 7500 and 7510 roms have bcm4330 files there, so it looks to me that the wifi card is the same as our.
I also tried the kernel you sent me with 7500 rom and wifi driver still loads.
this is awesome guys.. after the posts yesterday and staying up till 3:Am , I got the sucker booting.. of course that was it though. Great to see this post today.. Sounds like it's not too far off.. at least for me wifi would be the only thing left that's important since I havent touched the camera app or bluetooth yet.
poisike said:
I don't know... I just flashed my P7300 with P7500 rom and wifi driver loads just fine. I only edited the build.prop and used a kernel from overcome rom, i didn't touch anything else. Also if you look in \system\etc\wifi you will see that both 7500 and 7510 roms have bcm4330 files there, so it looks to me that the wifi card is the same as our.
I also tried the kernel you sent me with 7500 rom and wifi driver still loads.
Click to expand...
Click to collapse
right, I'm going back over the source, and the board config, some wifi stuff seems commented out. I know I need to get on irc.. but work interjects lol..
for the record on linux to use broadcom it has to extract the firmware for the card, I don't think it has to for droid as in this case the firmware is provided to us. I should probably stop spinning my wheels and go back and read/learn more about how android treats these things.
I am all ears however, anyone with debugging exp can have the rom with permission to use the kernel from motly.
I don't think that the problem is in your build. I have tried 3 different builds and they all have the same error:
Code:
ERROR/WifiStateMachine(168): Failed to load driver!
ERROR/WifiStateMachine(168): DriverFailedState
So it looks to me that the problem is in kernel. Of course i could be wrong.
Also it looks to me that the bcm4330 driver source is posted on github (https://github.com/cyanogen/galaxy-2636/tree/ics/drivers/net/wireless/bcm4330), so i hope _motley finds time to take a look.
poisike said:
I don't think that the problem is in your build. I have tried 3 different builds and they all have the same error:
Code:
ERROR/WifiStateMachine(168): Failed to load driver!
ERROR/WifiStateMachine(168): DriverFailedState
So it looks to me that the problem is in kernel. Of course i could be wrong.
Also it looks to me that the bcm4330 driver source is posted on github (https://github.com/cyanogen/galaxy-2636/tree/ics/drivers/net/wireless/bcm4330), so i hope _motley finds time to take a look.
Click to expand...
Click to collapse
ok thanks I was looking at the source on my build system remotely, and the drive went oiffine, I think my ssd is going, so I'm going to get a new on on the way home. pisses me off!
Great work!
I'm seeing forward to try this out.
Gesendet von meinem GT-P7300 mit Tapatalk
poisike said:
I don't think that the problem is in your build. I have tried 3 different builds and they all have the same error:
Code:
ERROR/WifiStateMachine(168): Failed to load driver!
ERROR/WifiStateMachine(168): DriverFailedState
So it looks to me that the problem is in kernel. Of course i could be wrong.
Also it looks to me that the bcm4330 driver source is posted on github (https://github.com/cyanogen/galaxy-2636/tree/ics/drivers/net/wireless/bcm4330), so i hope _motley finds time to take a look.
Click to expand...
Click to collapse
Sorry, I misspoke, the 10.1 does indeed use the 4330 like us...been looking at Iconia, Xoom, and ASUS TF1 ROMs too much lately.
Well other than the green screen affect, wifi, camera,bluethooth this thing really runs well.
HC was a pig for memory, as I noted on my Acer when I ran ICS for a bit, memory mamagment is hugely improved over honeycomb, I never had more than 200mb free on a regular basis, with ICS its well over 400mb.
and the thing really cooks along, I snap in and out of screens really fast, and angry birds works! haha
I will spend some time tonight on wifi, and making a new build.
poisike I'll setup irc tonight, I may have to rebuild the macpro, who knew running an os other than apple would cause a problem lol..
_motley said:
Sorry, I misspoke, the 10.1 does indeed use the 4330 like us...been looking at Iconia, Xoom, and ASUS TF1 ROMs too much lately.
Click to expand...
Click to collapse
The otapackage build does spit out a file called "kernel" would that help you any?
I can drop it in my dropbox
actually there is a boot.img.cm9 in my alpha zip you have, but I can still upload just the file called kernel if yoi think it would help.
also once I have my macpro back in op I'm not against setting up accounts for you and poisike, or setting up our own git repo, would be beneficial to work against the same source once we zero in and attempt to create a working port for everyone.
oh and btw, your OC settings work, running ICS at 1.4ghz
This is great news!! Once the wifi is working, I'll be using this as my daily driver. Will this be a completely AOSP project or still based on TouchWiz. I wish I could have stock e-mail, calendar, etc.
Excellent news! I will be waiting patiently....
Asop only! "Don't wiz on my ICS"
Sent from my SGH-I777 using xda premium
nycbjr said:
The otapackage build does spit out a file called "kernel" would that help you any?
I can drop it in my dropbox
actually there is a boot.img.cm9 in my alpha zip you have, but I can still upload just the file called kernel if yoi think it would help.
also once I have my macpro back in op I'm not against setting up accounts for you and poisike, or setting up our own git repo, would be beneficial to work against the same source once we zero in and attempt to create a working port for everyone.
oh and btw, your OC settings work, running ICS at 1.4ghz
Click to expand...
Click to collapse
That sounds like it is just the zImage binary for their build, I think I remember seeing it there too. It won't do me any good. Sounds good about the repo. I can still browse the repos to look at code as necessary for the time being. Glad to hear that the OC is is still working good.
I just sent poisike a 3G kernel with the touchscreen fix so he can start working on that end.
"Don't wiz on my ICS!" haha

Unofficial announcement of CM10.1/10.2

Latest Downloads
CM10.1 http://d-h.st/i3V
CM10.2 https://drive.google.com/file/d/0B1V_hMyelDz0Rm1nenlqT2JKWkE/edit?usp=sharing AS OF 21.11.2013
UNOFFICIAL FAQ FOR CM10.1/10.2
DOWNLOAD AND INSTALLATION
Q: Where’s the download?A: The initial FXP release had an incorrect kernel – you can download a working version of ROM from here. http://d-h.st/TPT
This ROM has since been updated a download can be located here. http://d-h.st/i3V
If you wish to try a CM10.2 (that’s Jelly Bean 4.3 – have Sony actually released a 4.3 ROM yet?) one can be downloaded from the link above.You can also download the correct version of GAPPS for Jelly Bean 4.3 here. http://brintaylor.info/Android/CM/gapps/
For the CM10.2 build you should use this link to report bugs. https://docs.google.com/forms/d/185s...9UINQ/viewform
Uberlaggydarwin plans to take a 'light touch' approach to support via XDA, so don't necessarily expect an answer to a query if you post in this thread
It seems like FXP have delayed releasing for our device for now, but information about CM builds that are being actively supported and developed can be found in this thread for now.
Q: How do I install?
A: You need an unlocked bootloader and an installed recovery. BACK UP your current ROM to your external SD card. Put the ROM and GAPPS on your external SD card. Boot into your recovery, do the necessary wipes, flash the ROM, flash GAPPS, reboot, victory. Disclaimer: if it breaks your phone, it’s your fault.
Q: Do I need to install the supplied kernel before installing the ROM?
A: No, unlike older xperia models CWM is able to flash both the kernel and the ROM at the same time. There is no need to use fastboot or flashtools to flash the kernel first, just a working recovery and an unlocked bootloader on your phone.
Q: Can I use another kernel instead?
A: No, for now only the supplied kernel will work.
Q: I’ve installed the ROM but can’t find the play store?
A: Immediately after installing the ROM you should install the 4.2.2 version of GAPPS (Google Apps) – this installs the play store and several other applications that Google regard as essential to the Android experience. This can be found here – http://goo.im/gapps/gapps-jb-20130812-signed.zip
Q: How do I update to the latest version of the ROM?
A: Once you’ve downloaded the latest version to your SD card, boot into recovery. No need to wipe your data, though you probably should wipe cache and dalvik cache (I don’t know whether this is done automatically as part of the installation but it can’t do any harm). You don’t need to install GAPPS again as this is a firmware update, not a new installation.
However if you’re moving between versions i.e. 10.1 to 10.2 you should definitely do a factory reset – the ROM may well work fine without a data wipe, but it may not and any problems might not be immediately noticeable (making bug tracking difficult). I would advise you NOT to report bugs if you’ve moved between android versions without a factory reset.
Q: When will they release a version that works on a locked bootloader?
A: Never. Some the features of the ROM simply won’t work very well/at all on a stock kernel. If you are rooted you can simulate some of the features with apps and mods though.
POST-INSTALLATION QUESTIONS
Q: I’ve installed the ROM – I can use Titanium Backup to reinstall all my apps right?
A: Yes and no. They may work fine, they might not – you are better off letting Google’s back up service restore all your apps. If you restore an app using Titanium or similar software and it’s buggy, there’s no point reporting it – re-install the app instead, perhaps even the ROM.
Q: 4G isn’t working – what do I do?
A: It’s not enabled by default on CM10.1 so you must do the following.
Go to the dialpad/phone.
Dial in the this number: *#*#4636#*#* (This will bring up "Phone info").
Tap WCDMA from under "Set preferred network type".
Select "LTE/GSM/CDMA auto (PRL)".
The 4G LTE network should now be activated.
Q:Where’s USB mass storage?
A: After ICS Google stopped including it in their Android builds, as such mass storage mode is not a feature that was kept by CM for Jelly Bean. Individual manufacturers do what they want though, which is why Sony, Samsung and others still have it. Skilled modders may be able to add to ROMS based on this development, I reckon they might be able to patch this one to include it too
Q: This ROM is buggy as hell and drains my battery – how do I let the developers know?
A: Logcat and/or a kernel log - or it didn’t happen for bugs.
Better battery stats for battery drain.
There are lots of guides out there showing you how to take logs and how to record battery stats.
Anecdote – I activated Google+ yesterday as I like the auto-photo upload feature but wakelock detector revealed it was killing my battery (I think it’s dodgy on stock too). The choice was the app or the ROM, I chose the ROM.
Q: After installation something random doesn’t work – what do I do?
A: Check the thread to see if other users have mentioned the issue and to see if the developer has posted a solution. Also, you’re on XDA, you’re an advanced user, you have unlocked your bootloader, thrown out your warranty and accepted the consequences. So please try to resolve the issue yourself. In general if you are having a problem and no one else is, it will be a problem with your phone/download/installation.
Phone - obviously a hardware fault can't be foreseen by the developer and have you unlocked your bootloader!
Download - Most downloads are fine. But I've flashed enough ROMS to know that sometimes a file gets corrupted and sometimes they say they are complete when they are not. Sometimes I've been careless and clicked on the wrong download, sometimes the website hosting the site is haveing a a bad day, sometimes the developer puts the download in the wrong place too The first things to check are the name and size of the file - if these tally you're probably fine to install. If you want to be extra cautious you can check the MD5 hash to see if your download matches. Sometimes the file gets corrupted on upload - nothing anyone can do about that...
Installation - (Please back up your orignal ROM). Typically you'll be installing this ROM using a recovery from another ROM/kernel/MOD - so if you have problems installing , it might be that you have a bad recovery.
The wipes really need to be done to ensure the smooth running of your phone, but as you've backed up, the 15 seconds you spend properly wiping should not be much of a chore.
If you're one of the first downloaders, I guess there is some merit in saying you couldn't install, but if it's been out for a while and there are loads of posts saying 'what a great ROM' there's little point posting 'won't install'. Describe exactly what you've done and someone might help.
Bear in mind there are apps/hardware that the developers of this ROM won’t have heard of/care about - so if something doesn’t work properly on your phone it could be for numerous reasons. Either way, this may be something you have to live with. Alternatively, if the app is essential to you, you’ll have to return to a backup.
Remember this ROM is in development, there are no promises of perfection and no one is forcing you to use it. However, the right kind of feedback is always welcomed by the developers and may be acted on – the wrong kind will often be ignored.
Q: What does a perfect bug report look like?
A: Go here. http://forum.xda-developers.com/showpost.php?p=46935640&postcount=313
Q: What are the known bugs?
A: FM radio doesn’t work.
A: Attempts to offline charge cause the phone to boot.
A: 4G activation is not remembered between boots for CM10.1.
A: For 10.2 there is a known battery drain issue related to WiFi. See the solution here. http://forum.xda-developers.com/showpost.php?p=46923723&postcount=301
The following issues have been reported by some users, but others say it doesn’t affect them. They are regarded as hardware issues – anecdotal ‘me too’ posts will be ignored. However, supply a log and your phone’s date of manufacture and the developer may look into it (this might help you prove that your phone is faulty, so it’s a worthwhile exercise).
Erratic touch screen response.
Reading external SD Card in recovery and in use.
As others have said this is possibly the most stable first CM build they’ve encountered and I agree – it’s definitely suitable for daily use. I've been using it from release and haven't had a single reboot/app crash or freeze.
http://uploaded.net/f/q3au96
CM 10.1 released for huashan
Its cm for our phone right?!??
Sent from my ZTE Blade G using xda app-developers app
Thanks for sharing. I saw yesterday in the changelog that both 10.1 and 10.2 where announced on FXP 242 (10.1 in beta and 10.2 in alpha), but I can't find the 10.2 download anywhere.
Maybe they don't publish public download links for alpha versions ?
Parkside said:
...no announcements, I can't keep it to myself. You'd do the same right?
Click to expand...
Click to collapse
Its safe to download huanshan cm file for our phone.(know that huanshan is code name for our phone)????
Sent from my ZTE Blade G using xda app-developers app
Yes take a look
karma123 said:
Yes take a look
Click to expand...
Click to collapse
Wooohooooo im so happy i cant wait to test itThanks to FXP team !
When i flash it im gonna make review wohoooooo
Sent from my ZTE Blade G using xda app-developers app
---------- Post added at 12:06 PM ---------- Previous post was at 11:58 AM ----------
karma123 said:
Yes take a look
Click to expand...
Click to collapse
Can you tell me what file to download??
Sent from my ZTE Blade G using xda app-developers app
Download this :- http://uploaded.net/file/7ntq0zp6/from/q3au96
Flashed and booted. Its nice. But some screen flickering while scrolling. Like in settings etc etc. But that can resolve with enable the " Disable Hardware Overlay" option from Developer Settings
What about performance ? Can you run antutu bench ? how much is free / used RAM ? etc.
thanks
Are mirrors allowed? Can somebody mirror this file? Im sorry but uploaded has failed me several times already...
mmm273 said:
What about performance ? Can you run antutu bench ? how much is free / used RAM ? etc.
thanks
Click to expand...
Click to collapse
Now only i flashed this. I dont have any apps installed. So performance is awsom now. Free RAM is 509 and used 333
ok, only for compare - what antutu score ? With stock ( fresh flash) i have 21 000...
Screen Flicker
Hi @Rajeev
I didn't experience screen flickering at ALL in ANY test builds so I find this really difficult to believe but I'm happy to take a detailed look at it ..
Log's plus video(so I can see what you mean) would be useful so I can get this possible ?issue? and if it is an issue then I'll get it resolved.
None whatsoever for me so this is a really weird issue....
Thanks
I have the flickering too ! And the phone often soft freezes. Seems like the app isnt updated anymore on screen. It can also be just the keyboard for example. Hiting recent tasks unfreezes it but systemui sometimes freezes until reboot.
Sent from my C5303 using xda app-developers app
uberlaggydarwin said:
Hi @Rajeev
I didn't experience screen flickering at ALL in ANY test builds so I find this really difficult to believe but I'm happy to take a detailed look at it ..
Log's plus video(so I can see what you mean) would be useful so I can get this possible ?issue? and if it is an issue then I'll get it resolved.
None whatsoever for me so this is a really weird issue....
Thanks
Click to expand...
Click to collapse
Hi Bro @uberlaggydarwin
Yes i am saying truth only.
1) While Scrolling in settings Its flickering like waves. But its not coming after Click the " Disable Hardware Overlay" Function.
2) When i press the Reboot option its rebooting but its rebooting like something weird in Screen..
3) Soft reboots happens multiple Times...
I know its a Beta release. I am not complaining . But answering ur question...
mmm273 said:
ok, only for compare - what antutu score ? With stock ( fresh flash) i have 21 000...
Click to expand...
Click to collapse
I'd like to see a screen of that score. Seems a bit too high. Sure you have the SP ?
You're using V4 ofcourse, my bad.
Bootloader
Just wondering if you are guys are using locked or unlocked bootloader? I'm locked with CWM and I'm wondering what the process would be of installing... (e.g. wiping /data...)
jakelooker said:
Just wondering if you are guys are using locked or unlocked bootloader? I'm locked with CWM and I'm wondering what the process would be of installing... (e.g. wiping /data...)
Click to expand...
Click to collapse
Hey, Make a backup, you need an unlocked bootloader for this. Then wipe all cache and data etc. then flash the rom on your phone
jakelooker said:
Just wondering if you are guys are using locked or unlocked bootloader? I'm locked with CWM and I'm wondering what the process would be of installing... (e.g. wiping /data...)
Click to expand...
Click to collapse
Well asfaik CM requires a custom kernel which can only be installed on a phone with unlocked bootloader. Hope ive helped.
Rajeev said:
Hi Bro @uberlaggydarwin
Yes i am saying truth only.
1) While Scrolling in settings Its flickering like waves. But its not coming after Click the " Disable Hardware Overlay" Function.
2) When i press the Reboot option its rebooting but its rebooting like something weird in Screen..
3) Soft reboots happens multiple Times...
I know its a Beta release. I am not complaining . But answering ur question...
Click to expand...
Click to collapse
LOG"S OR IT DIDN"T HAPPEN . I'm serious.
I'm downloading this release to test but I can't help much if you don't provide logs.
Are you sure its not auto-brightness being turned on as auto-brightness doesn't work very well in stock so the changes are probably more noticeable.
Reboots work perfectly fine for me..
On the recent test builds I haven't had a reboot issue but as you know the kernel is temporary so I'll redo it when 4.3 comes out....
WE NEED LOGS.

[ROM] Evervolv | 4.0.0p1 [AOSP 4.4.2] [3.4 kernel] [TEST][Non-Data/Media]

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).
Current version: 4.0.0p1
Current Items not working/Buggy
Updated 4-4-14
No Bluetooth ** FIXED WIP but a majority of items work
Camera ** FIXED WIP camcorder recordes with a blue tint
Battery draw around 50mA in sleep
You tell me what you find.
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.
05-03-2014 Test Build
-- Updates that were in the data/media build since 4-24-204 plus a few more misc fixes.
04-21-2014 Test Build
--some audio fixes for the random SOD along with adding in OTG its not 100% but working well with USB stick, keyboard, and mouse. Activate OTG before plugging in device.
Netflix 1.8.1 -- Don't upgrade Netflix to the latest if you did download here and downgrade and uncheck auto update in the Play Store this is temp until I figure out what changed again.
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
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.
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.
Click to expand...
Click to collapse
Reserved
Awesome thx flint man! Any changes from the Nov 10 test build?
Way to go Flintman, this is great!
Sent from my Touchpad using XDA Premium HD app
flintman said:
Reserved
Click to expand...
Click to collapse
Minor for now
Sent from my SCH-I545 using xda app-developers app
You might want to change the 2nd line down in the OP to KitKat 4.4 and not Jellybean.
theechap said:
You might want to change the 2nd line down in the OP to KitKat 4.4 and not Jellybean.
Click to expand...
Click to collapse
I am using Nexus 5 and was wondering if TP will get Kitkat or not...this is awesome....will flash tonight
Anyone that had lost data can you give me some information. Which acmeinstaller version did you use? Are you still on the smaller partition or did you upgrade? Im still on the i believe it's 400mb system part and haven't upgraded to the larger partition and still yet to loose data. It also could be the way kitkat mounts the partition now. After the inital loose of data did you experience it again? I'm trying to boil this down and having issues pinpoint it as i have yet to loose anything. The more information I can gather the quicker i can fix this issue. Thanks all for testing and helping me out getting this great device updated to the latest OS.
Thanks for this ROM - I have standard partition size and CWM and had no data loss, clean installed. Running well ☺
Sent from my Touchpad using Tapatalk
I tested it briefly and came from datamedia build of 10.2. I did system wipe and install using milaq's datamedia version of CWM. I had no major problems with the install and no lost media as far as I know. Looking forward to testing it again, when it gets a little more stable.
Is everyone just using the 4.3 gapps or is there a 4.4 gapps?
SDcard files
flintman said:
Anyone that had lost data can you give me some information. Which acmeinstaller version did you use? Are you still on the smaller partition or did you upgrade? Im still on the i believe it's 400mb system part and haven't upgraded to the larger partition and still yet to loose data. It also could be the way kitkat mounts the partition now. After the inital loose of data did you experience it again? I'm trying to boil this down and having issues pinpoint it as i have yet to loose anything. The more information I can gather the quicker i can fix this issue. Thanks all for testing and helping me out getting this great device updated to the latest OS.
Click to expand...
Click to collapse
Hey Flintman,
I only lost the data just once so far, if you want I could test out a reinstall. I installed Kitkat by wiping system data and cache and flashing the Rom and gapps through recovery. I already had a 600MB partition but was monitoring the free space left. I should also note that I used CWM to advance restore my data partition from my Evervolv 4.3.1 backup. This seems to be working fine.
Because I use my tablet to test mods and games I had a lot of extra folders that disappeared. These were all added by me like, Dos Games folders about a dozen, image files, Beta apks and the Rom and gapps, that were placed in the internal memory ect. All these files vanished, however files I added that were already in system folders stayed, like music, downloads and shows. It seems to just delete things that the user added into non system or app related folders.
Thanks for letting us take this fun test drive, I was all backed up before I started
DemonicHawk said:
Is everyone just using the 4.3 gapps or is there a 4.4 gapps?
Click to expand...
Click to collapse
Here ya go. You should add that to your OP Flintman
flintman said:
Interesting on the SD card i have yet to experience it. I have a new one that will be going up soon fixed wifi but browser is broken. Firefox works though. Oh BTW still able to keep the stock partition size even with install gapps. KK Gapps i'm using from HERE. Might want to start downloading as it takes a while 8)
Click to expand...
Click to collapse
This was the info I compiled about Flintmans fantastic Test Build. I had a few notes and warnings for users, I will need to update it with a link to this new thread.
Edit: I updated the video for the newer build
Download 4.4 Kitkat Gapps here:
Notes:Low to Medium battery drain(-4mA to -30mA) h/w video, Test Build Make a Backup!, Automated Updater, Audio plays with the screen off, Camera, No Bluetooth.
Note: Windows users may need to do the following in order to attach the Touchpad with the USB cable.
1. Go into the Device manager. You will see "MTP USB Device" under portable devices.
2. Right Click it and select update driver software
3. Select Browse my computer for driver software.
4. Select Let me pick from a list of device drivers on my computer
5. Select USB Mass Storage Device then click next.
and/or
6.To transfer files to PC, turn on USB mass Storage from the USB connection notification on the Android device.
Note(Important): (This might be fixed now) Backup and transfer all your SDcard files to PC. This is a testing build and could wipe files from your SDcard data.
[Note(Important): I would recommend increasing the size of your System Partition for this build. After my install I had 398/400MB free, so Flash the 512MB zip below or use Tailor to adjust the size.
Note(Important): This is an Android Open Source Project (AOSP) rom not a CyanogenMod (CM) rom. Dirty flashing an AOSP rom over a CM rom can causes errors and rebooting issues. Always do a clean install when moving from CM to AOSP and vise versa.
Flash through recovery to change the partition size to 512MB(Gradular&codycoyote)
Flintmans Posts about the new Pre-Beta Build here:
I did a clean install with the standard CWM recovery and had no loss of data or files that i can find. I also restored my apps with TiBU and everything came back good.
The Quadrant score came in a lot lower than the first test build, 1500 (first test build was 2350). The CPU portion is what suffered the most, the other portions seemed normal. It doesn't seem slower than normal though.
I haven't found any problems with any apps.
Great job, thanks!
Sent from my Touchpad using XDA Premium HD app
Sweet, glad to see this. I think we should wait for Android 4.4.1. Which the UI will be fixed for the Nexus 10.
Sent from my Galaxy Nexus using xda app-developers app
Hey Flintman,
Would you clear up some confusion about this build. I've seen a post over in the Evervolv 4.3 thread and also over in Rootzwiki. Is this build of 4.4 a traditional build like your 4.3 build or a data-media build that is going to require the data-media version of CWM and resizing partitions like the Milaq 4.3? Thanks
nevertells2 said:
Hey Flintman,
Would you clear up some confusion about this build. I've seen a post over in the Evervolv 4.3 thread and also over in Rootzwiki. Is this build of 4.4 a traditional build like your 4.3 build or a data-media build that is going to require the data-media version of CWM and resizing partitions like the Milaq 4.3? Thanks
Click to expand...
Click to collapse
I use the normal twrp recovery. This ROM doesn't require the data-media version of cwm. I hope that answers your question.
Sent from my SCH-I545 using xda app-developers app
I want to go back to CM10.1 but everytime I flash it back bootloader defaults to evervolv despite having an option for Cyanogenmod but the bootloader fails when I select cm10.1 after flashing... I only wanted to test it out a little too unstable for a daily driver but now it seems like I am stuck on this rom
Very cool looking forward to flashing this as soon as some of the major bugs are worked out
Sent from my Nexus 4 using Tapatalk
flintman said:
Anyone that had lost data can you give me some information. Which acmeinstaller version did you use? Are you still on the smaller partition or did you upgrade? Im still on the i believe it's 400mb system part and haven't upgraded to the larger partition and still yet to loose data. It also could be the way kitkat mounts the partition now. After the inital loose of data did you experience it again? I'm trying to boil this down and having issues pinpoint it as i have yet to loose anything. The more information I can gather the quicker i can fix this issue. Thanks all for testing and helping me out getting this great device updated to the latest OS.
Click to expand...
Click to collapse
Hi,
I experienced loss of data, much like as reported another member here, I only lost the folders that were added by me, it also removed the TWRP back up folder, however folders that are the usual like Music, Download remained as they were, however, the gallery app refused to load any images.
In between the reboots, I connected the TouchPad to PC and noticed something peculiar, after the very first boot, it showed about 9GB free, the same was on TWRP too, even though my folders were all gone, and after the next reboot on being connected to PC it showed me about 17GB free.
My install method was using TWRP, system wipe and flashing the zips,
I have extended the system and data partitions using the Tailor method to 512mb and 2.5gb respectively.
For now, I am back on 4.3 but would like to be able to help test out if there are any fixes that you are trying. Once again, thanks for the all the good work on these ROMs :good:
You know I think TWRP is the cause if data loss just reading peoples experiences in this thread. CWM FTW!
Sent from my Nexus 4 using Tapatalk

Galaxy Exhibits / Galaxy Ace 2 E General Discussion [T599 | T599N | T599V | T599X]

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

[ROM] Evervolv | 4.0.0p1 [AOSP 4.4.2] [3.4 kernel] [TESTING] With /data/media 4G

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).
Current version: 4.0.0p1
Current Items not working/Buggy
home key sometimes doesn't turn device on need to use power button-
Battery draw getting around 65mA in sleep
Wifi tether breaks WIFI. If you turn it on just reboot and wifi will be back
Cell service speeds getting 1.5 down and .7 up test build 8-10 getting 6 down and 2 up in my area
Cell service is pause once and a while and will reconnect Known issue. So far solved in 8-10
Cell service cuts out completely this is very rare but it did happen once and after reset hasn't done again. On a clean install after booting up completely do a reboot and seems to eliminate for now. So far solvednin 8-10
You tell me what you find.
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.
If you don't have a SIM card or setup with ATT then you can use the regular Touchpad Rom wifi model as the battery life will be better.
ev_tenderloin4g-testing-2014.06.02.zip ->Inital Build
ev_tenderloin4g-testing-2014.06.25.zip see updated issues above
test build 8-10
FLINTMAN-update-TWRP-touch-data_media-SELINUX-TEST-Build_4-25-14.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
--reboot in recovery seems to be working 100% of the time. I have tried about 20 times without an issue.
Netflix 1.8.1 -- Don't upgrade Netflix to the latest if you did download here and downgrade and uncheck auto update in the Play Store this is temp until I figure out what changed again.
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, NewbyJE, 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
Sorry all the 4g will only have Data/media as i have too many devices to maintain. It's a better setup with the size of roms and Apps now a days.
Thanks
Thanks for the great work on the 4g. This truly brings 4g owners out of the dark ages.
Sent from my Touchpad using XDA Premium 4 mobile app
Great News HP TP 4G users!
It's really great news for HP Touchpad 4G owners to be getting along awaited update for their Touchpads. Really incredible work Flintman especially considering you're making two separate Kitkat Builds(DM and Non-DM) for the HP Touchpad already. You sir are deserving of a Touchpad medal of honor. Must be some sort of record maintaining 3 HP TP builds at once.
I wanted to ask you about the installation methods for 4G owners. I have read that the TPToolbox is not currently compatible with 4G, so I must ask if would you be able to install these builds with my Older data media guide below? I have a newer guide for the TPToolbox and I'll add it there when its supported. I've already added it into my older thread so hopefully 4G users will be able to locate and install it. Wish I had a 4G tablet to test on
Thank you for your continued support of our aging but awesome HP TouchPad:highfive:
[ROM GUIDE]How to install Android 4.4.2 Data Media builds on the HP TouchPad
[ROM GUIDE]How to use the TouchPad Toolbox to install Android "The Super Easy Way"
RolandDeschain79 said:
Wish I had a 4G tablet to test on
Click to expand...
Click to collapse
No, it's me who wishes to have a 4G tablet right now because then I could send it to you at once to do my part to support this fantastic community, too.
RolandDeschain79 said:
It's really great news for HP Touchpad 4G owners to be getting along awaited update for their Touchpads. Really incredible work Flintman especially considering you're making two separate Kitkat Builds(DM and Non-DM) for the HP Touchpad already. You sir are deserving of a Touchpad medal of honor. Must be some sort of record maintaining 3 HP TP builds at once.
I wanted to ask you about the installation methods for 4G owners. I have read that the TPToolbox is not currently compatible with 4G, so I must ask if would you be able to install these builds with my Older data media guide below? I have a newer guide for the TPToolbox and I'll add it there when its supported. I've already added it into my older thread so hopefully 4G users will be able to locate and install it. Wish I had a 4G tablet to test on
Thank you for your continued support of our aging but awesome HP TouchPad:highfive:
[ROM GUIDE]How to use the TouchPad Toolbox to install Android "The Super Easy Way"
Click to expand...
Click to collapse
Yes; the thread is indeed useful.i used files
Philz+Jcsullins Touch Interface DM-CWM along with the file "32gbTP_and_up_ONLY_Gradular_data_resize_24576-0.1 to resize the partition with instructions. TP looks young and cute these days
Thanks all for your interesting work and much respected.
Ok just uploaded a new test build. I got the speeds up on DL and UL not all the way but alot better. You will get a freeze up once and a while looking into that. Read this issues section in the first post. Test it out and let me know if anyone exeriences something different or not at all
Thanks
New test build up i had a little time and fixed the cell service getting good speeds and no disconnects. Pretty smooth. Let me know.
Sent from my Touchpad using XDA Free mobile app
Still up to date and this latest build is the best thing to ever hit this device...

Categories

Resources