Related
I am still experiencing occasional Sleep of Death issues with CM7.2-RC2. I thought this had been taken care in independent development before RC1; has the fix not been integrated into the CM7 repository yet?
Have other people been seeing this, too?
jicama said:
I am still experiencing occasional Sleep of Death issues with CM7.2-RC2. I thought this had been taken care in independent development before RC1; has the fix not been integrated into the CM7 repository yet?
Have other people been seeing this, too?
Click to expand...
Click to collapse
I has not been integrated into the repository for cm7. Look at my tips thread in my signature for a fix for cm7.
Hmm, I went to install the updated driver and found that it was already there. And now I see that it's in update-cm-7.2.0-RC2-encore-signed.zip:
1078520 Defl:N 430749 60% 02-29-2008 02:33 d968c8a3 system/lib/modules/tiwlan_drv.ko
This seems to be the same as the version in nookcolor_CWM-OC-SASDmod.rar.
Curious. Well, perhaps my unrelated reinstall yesterday will have fixed it...
jicama said:
Hmm, I went to install the updated driver and found that it was already there. And now I see that it's in update-cm-7.2.0-RC2-encore-signed.zip:
1078520 Defl:N 430749 60% 02-29-2008 02:33 d968c8a3 system/lib/modules/tiwlan_drv.ko
This seems to be the same as the version in nookcolor_CWM-OC-SASDmod.rar.
Curious. Well, perhaps my unrelated reinstall yesterday will have fixed it...
Click to expand...
Click to collapse
What is nookcolor_CWM-OC-SASDmod.rar? Where did you get it? Whoever made it may have included the fixed module.
It's a collection of changes to make to a stock firmware zip, from
http://forum.xda-developers.com/showpost.php?p=23009596&postcount=162
I just had another SoD, so clearly that version doesn't fix the problem.
But I managed to download your zip from Megashares (earlier it said too many people had been downloading it), and it looks to be significantly different:
969596 Defl:N 396999 59% 11-10-2011 14:21 367e274d system/lib/modules/tiwlan_drv.ko
So I'll give this one a try. Thanks!
Ah, I think I see what's happening. In the SOD thread on cyanogenmod forums,
http://forum.cyanogenmod.com/topic/32316-sleep-of-death-debugging/
there were two SOD fixes posted: One was the modified wifi driver from Embedded that your post includes, and the other was a modified kernel from dalingrin that is used with the unmodified wifi driver. I think the SASDmod bundle includes the modified kernel, so it also includes the unmodified wifi driver. But when I saw the driver in there I assumed it was the one I wanted.
Anyway, hopefully Embedded's driver will do the trick. Thanks again.
jicama said:
Ah, I think I see what's happening. In the SOD thread on cyanogenmod forums,
http://forum.cyanogenmod.com/topic/32316-sleep-of-death-debugging/
there were two SOD fixes posted: One was the modified wifi driver from Embedded that your post includes, and the other was a modified kernel from dalingrin that is used with the unmodified wifi driver. I think the SASDmod bundle includes the modified kernel, so it also includes the unmodified wifi driver. But when I saw the driver in there I assumed it was the one I wanted.
Anyway, hopefully Embedded's driver will do the trick. Thanks again.
Click to expand...
Click to collapse
That's all true. The modified kernel helped with SODs but did not eliminate them. You need the modded kernel module to totally get rid of them. It's ok to use them together.
Sent from my Nook Color running ICS and Tapatalk
Ok, as you all know Scritch007 has compiled CM10 for our old X10, Considering how ICS was running on our device achieving a fast & reliable JB was sort of a dream but the dream has become true thanks to Scritch007 & CMX10 team as he's named it himself
So I opened this thread in order to keep the development thread clean & save the dev & others who want to actually contribute to the project the headache of having to go through non-development posts, You can use this thread for any noob/kinda noob/not so noob questions, issues or problems you have with installation or even the rom itself before confirming it as an official bug, "thanks" comments if you ever feel the "Thanks" button is not enough, any mod or extra features & add-on s that you request (because Scritch007 has clearly stated that he wants to deliver a pure & clean CM10 & he won't add these kinds of stuff) or anything else you'd like to say on the subject which is unrelated to development
Original thread in development section
Changelog, Links & other stuff you need to know
Installation Guide:
- First be aware that you need to be rooted & also on unlocked bootloader
- Download the latest version of the rom(cm10-v10.zip) & the latest kernel(kernel-CM10-v22.ftf) from HERE & copy the rom to your sd card (If you need Gapps grab it(gapps-jb-20121011-signed.zip) from HERE & copy it to your sd card too)
(The standard procedure for installing this is like any other rom: 1- Flashing the latest kernel using Flashtools 2- Powering on the device & booting into CWM recovery 3- Performing a full wipe (wipe data/factory rest, wipe cache partition & advanced > wipe dalvik cache) and 4- installing the rom & then the gapps; but as reported by many users you may have problems with the standard procedure specially If you's coming from other roms & kernels & this is your first time installing this, The problem may be facing a black screen & not being able to enter recovery & such, So I recommend you follow the instructions below which will surely work)
- Do NOT Flash the 4.1 kernel at first, Download & flash any other kernel that has a working CWM recovery using FLASHTOOLS (For example Scritch007's CM9 kernel or FeraVolt's ICS kernel), If you already have a kernel with working CWM recovery you can skip this step (Also it seems I should mention that by CWM recovery I mean ClockworkMod recovery not xRecovery, This rom can only be installed using ClockworkMod recovery)
- Boot into CWM recovery(by pressing the back key repeatedly when you see kernel logo & notification led) and Perform a full wipe (wipe data/factory rest, wipe cache partition & advanced > wipe dalvik cache)
- Install the rom(cm10-v10.zip) & if you need Gapps(gapps-jb-20121011-signed.zip) install it too, after that do NOT reboot, while still in CWM recovery, just power off the device (If your CWM recovery doesn't have a power off option, take your battery off, wait for 10 seconds & put it back again)
Attention: If you faced the Status 7 error (getprop error / assert fail) when trying to install the rom in CWM, HERE is one solution, The other solution is editing your current build.prop (system/build.prop) to make at least one of the conditions you see in the error message true
- Flash the 4.1 kernel(kernel-CM10-v22.ftf) using Flashtools
- Power on the device & let the fun begin!!
Bugs & Issues:
- Camcorder captures low quality videos
- Turning GPS on & off will result in losing Deep Sleep and therefore battery drain until next reboot
- Tethering turns off when phone goes into deep sleep
- Video playback in gallery
Attention: If you want to report a bug/issue, THIS is the proper & helpful way to do it
Fixes & Add-ons:
- Fix for when Status bar freezes & doesn't update: Reboot into CWM recovery, Fix permissions and Wipe dalvik cache
- Fix for no data connection: It's been reported by users that a simple reboot will solve it
- Working Timescape For This Rom
- [APK] Seeder 2.0.0 entropy generator to provide significant lag reduction
- Xperia Z lockscreen for CM10
- SONY Xperia Z Walkman Clear Audio+, Movies Album & BE 2
- [MOD][APP]AwesomeBEATS™ v.5
- Xloud, Bravia 2 and Clear Bass for CM10 v 6.0 (I don't know if it will work for later versions of the rom or not, so kindly test & report here in this thread)
- Experimental tweaks & tips posted by a member (please test & report the results)
- On-screen button for Beta V3
- [MOD/THEME][CM10]All in 1 Transparent
- For root access issues (which apparently appears when flashing Ferakernel) THIS might help
Themes:
- Official MEGA CM10 Theme Chooser Thread [541 THEMES]
Screenshots (by aleespa) attached
Video preview of the pre-alpha version (by efgeni)
I'll update this post with more necessary info in the future
Good to see someone took the initiative on starting a discussion thread.
x10
So many GREAT THINGS released by Scrith, feel likes New Legend being growing up, also CM10
very much promissing than CM9.
I'm a noob, this thread very usefull to post 'a noob questions, ideas, etc etc, so.... thanks
@Riginal
Would you please to attach some screenshoots on the first post?
EDIT :
May be video review?
Regards
LOL..i tot i am dreaming right now.
Slapped myself.It's fxxking real!
So..What are the main issues yet?
Battery draining?
Camera working? (Dont bother bout camcoder.i'm not in a rush for recording videos.)
HW encoding?
random Reboots?
Lagginess?
And last one..
The NewsWORTHY thread button~
HIT IT!
SmokyX8 said:
LOL..i tot i am dreaming right now.
Slapped myself.It's fxxking real!
So..What are the main issues yet?
Battery draining?
Camera working? (Dont bother bout camcoder.i'm not in a rush for recording videos.)
HW encoding?
random Reboots?
Lagginess?
And last one..
The NewsWORTHY thread button~
HIT IT!
Click to expand...
Click to collapse
Give it a try, i thing gonna love it
AFAIK, this gonna be a great base rom for mod.
Still on the alpha stage but, it looks really promissing.
For some above issues, i believe we can to handled it .
FYI
Screenshots: (Thanks to aleespa)
This is really a dream I think.No other developer ever has given this stable rom in such a good time. Scritch really has made the most awesomest rom for our X10. This deserves a mention to the portal. Please vote for his thread !!
This Rom certainly rocks!!
On my third day now I can tell you that battery life is great & the Rom feels wicket Scritch has to be a magician.
Until now the only bugs I've found are:
no sound over headphones
(playing music over power amp),
sometimes no vibrate
(incoming messages or alarm),
cm recovery flickering &
titanium backup can't delete system files
(you can delete them with a root
explorer).
All these bugs have been mentioned in main thread.
I guess my next donation goes to You Scritch
Here is a video review of pre-alpha (thanks to efgeni)
Added screenshots, bugs & issues and a note on installation process, Feel free to add or correct & I'll update the OP
Really loving this rom, by the way someone reported that by adding the sound fix, video playback in gallery will also work, can anyone confirm because for me it doesn't
nfs most wanted working fine on this rom..but asphalt 7 no luck...anyone tried asphalt 7?
riginal said:
Added screenshots, bugs & issues and a note on installation process, Feel free to add or correct & I'll update the OP
Really loving this rom, by the way someone reported that by adding the sound fix, video playback in gallery will also work, can anyone confirm because for me it doesn't
Click to expand...
Click to collapse
jianlinooi said:
nfs most wanted working fine on this rom..but asphalt 7 no luck...anyone tried asphalt 7?
Click to expand...
Click to collapse
Sorry mates, i cant to corfirm these
Since my X10 is my only phone, and this is still on the alpha stage (but absolutely promissing, and i'm gonna wait for a while though).
I just returned back to my previous rom .
Anybody can confirm these please ???
Regards
riginal said:
Added screenshots, bugs & issues and a note on installation process, Feel free to add or correct & I'll update the OP
Really loving this rom, by the way someone reported that by adding the sound fix, video playback in gallery will also work, can anyone confirm because for me it doesn't
Click to expand...
Click to collapse
It was me! And yes for me every thing works like video recorded on GB works straight from gallery. Youtube works without any problem I ran HD video (1080p) which was playing without any lag.
Try to set permissions to read for all (root, group, other)
Video show it works:
kingstonxl said:
It was me! And yes for me every thing works like video recorded on GB works straight from gallery. Youtube works without any problem I ran HD video (1080p) which was playing without any lag.
Try to set permissions to read for all (root, group, other)
Video show it works:
Click to expand...
Click to collapse
That means HWA works!! Amazing,mine doesn`t work btw,...
moritd said:
That means HWA works!! Amazing,mine doesn`t work btw,...
Click to expand...
Click to collapse
Yes HWA works from first release Granny Smith confirms that too
btw what u mean ?i`ve to set that permisson for that audio file or ?
moritd said:
btw what u mean ?i`ve to set that permisson for that audio file or ?
Click to expand...
Click to collapse
for media_codecs.xml from this post:
ljose7 said:
about the sound of jb i found this i will try it right now
http://forum.xda-developers.com/showthread.php?t=1783993
it works
Click to expand...
Click to collapse
any progress in the headphone bug? damn i bored with those books..and no music in my head right now.
Sent from my Xperia X10 using xda premium
yey ty working like a charm KingstonX :X
SmokyX8 said:
any progress in the headphone bug? damn i bored with those books..and no music in my head right now.
Sent from my Xperia X10 using xda premium
Click to expand...
Click to collapse
Try Tinitus^^
really dubstep....
goddam i the worst thing you can do is reading books cause this must drain battery like hell
Greets
Sent from my Xperia X10 using xda app-developers app
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.
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??
Recently installed TWRP and CM12.1-20150426-UNOFFICIAL-matissewifi and all has gone well... although I can't seem to initialize either camera. Any ideas?
nofalsehero9 said:
Recently installed TWRP and CM12.1-20150426-UNOFFICIAL-matissewifi and all has gone well... although I can't seem to initialize either camera. Any ideas?
Click to expand...
Click to collapse
It's a known bug on all the cm12 variants, it's even listed in the thread. No known fixes yet
thisisapoorusernamechoice said:
It's a known bug on all the cm12 variants, it's even listed in the thread. No known fixes yet
Click to expand...
Click to collapse
Its my understanding that the same issue persists to CM13 also. As a noob to the forums, and to tablets, but extensive history with desktops, can someone point me in the direction of some documentation that might explain better how these sort of issues occur, which is to say the (for lack of a better term) driver works in stock android but not in the stripped down version?