i release this version with this changelog:
- ext2/ext4 support
- adb working on windows (remember to install drivers on windows)
- ipv6 support
- bluetooth modules
- nand stable
*update with ramswap*
you need the android update (new version of modules)
the ext4 support is compiled but i didn't edit the initrd.
Tomorrow i'll release a new version of atools (1.2.0) with ext4 enabler and new initrd.
I'll commit all changes to git after positive comments.
Backup all and reinstall after flash.
just great, I'll test as soon as possible!
l1q1d said:
i release this version with this changelog:
- ext2/ext4 support
- adb working on windows (remember to install drivers on windows)
- ipv6 support
- bluetooth modules
- nand stable
Click to expand...
Click to collapse
Because of this, Kaiser will be my primary phone tomorrow.
Magic is boring anyway, everything is working
Contacts lost after reboot using softreset button.
Goggles working fine!
Sent from my CyanogenMod Kaiser/Kaiser using XDA App
@tiagoclc: did you reinstall all before install new kernel?
You mean after...
Yes. I put new modules directly in androidinstal.tar.
After install system, clearing data, I restored data.
Setting google account again. After sync, ill try to reboot again.
Sent from my CyanogenMod Kaiser/Kaiser using XDA App
yes after...
strange, i reset so many times...
I'm getting ready to flash this on my Kaiser as well, and I'll report if I get any corruption after 1-2 days of use, as that seems to be the timeframe for me whenever the phone starts corrupting badly, especially framework and lost apps.
Will be installing the new Cynogen 7 Alpha by Scoot as well, as I'm really interested in getting Gingerbread on my Kaiser, as it worked really well (besides GPS not working, and facebook.
EDIT: At the moment, so far so good, I'm not transfering my SIM over just yet until I can confirm for myself if the phone will be stable enough... I had a serious issue with Android and the Kernels going on the frits when I needed it the most (was in a car accident, and couldn't make any calls because the phone decided to go into a reboot loop, and didn't have time or the patience to deal with the issue as I had more pressing issues to deal with)
Which brings me to one question, what exactly was done to resolve NAND corruption, and to post "nand stable"? As far as I was seeing, there was speculation that the YAFFS2 driver and the NAND driver were fighting over ECC, and that also the NAND driver hasn't been fully ironed out bug wise.
I do see the checkpointing is now working correctly, as I see the YAFFS2 driver constantly creating checkpoints every couple of minutes, then sitting idle, and doing it again (possibly whenever writing to the NAND occurs).
Also, was wondering if there were any improvements made to Power Management? I know the PM7500 chip is now enabled and working, and power management is now fully working for components like the radio and possibly the WiFi module as well, but still no control over the CPU dynamic clocking, or scaling.
l1q1d said:
i release this version with this changelog:
- ext2/ext4 support
- adb working on windows (remember to install drivers on windows)
- ipv6 support
- bluetooth modules
- nand stable
you need the android update (new version of modules)
the ext4 support is compiled but i didn't edit the initrd.
Tomorrow i'll release a new version of atools (1.2.0) with ext4 enabler and new initrd.
I'll commit all changes to git after positive comments.
Backup all and reinstall after flash.
Click to expand...
Click to collapse
so far pretty smooth on my vogue i have restarted a few times without issues, using a modified cm7 build. what was causing the nand issue?
This is a beta tester kernel, for explanation read the kernel thread and wait for source release.
After a fresh install, without data restore, rebooted 4 times (button) and 1 pulling out sim card and data partition is aparently ok.
Probably my data partition was corrupt when I made the backup.
Ill post more results later.
Sent from my CyanogenMod Kaiser/Kaiser using XDA App
Wow, that IPv6 module is huge!
Bad: I've had five or six freezes since installing this.
Good: no corruption, with data on NAND.
EDIT: It crashes precisely at:
insmod /system/lib/modules/ramzswap.ko disksize_kb=26010
I've turned off compcache until we figure this out.
ramzswap.ko is not compiled for this kernel so i will post it soon.
EDIT:
add ramswap module
Also had about 3 crashes since flashing this kernel, but no data or framework corruption as of yet.
Sent from my AT&T Tilt using XDA App
Check if crash are due to the rom or ril.
l1q1d said:
Check if crash are due to the rom or ril.
Click to expand...
Click to collapse
this is just a guess but i think his might be RIL based, my phone isnt connected to a network actively and i haven't had any crashes or data corruption and i have loaded my contacts and a messaging backup on it. i know your looking for real world beta testers, so i will stop posting on this thread if you so desire
it could be useful a log of crash
l1q1d said:
- nand stable
*update with ramswap*
Click to expand...
Click to collapse
This mean android dont gonna die after 3 days of use when you install on nand? (its called yaffs, or i am wrong) regards!
NAND is the architecture of our phones internal flash memory.
Yaffs is the filesystem applied to this flash memory.
l1qu1d, wich radio version is recommended to use with this kernel?
Sent from my CyanogenMod Kaiser/Kaiser using XDA App
I am testing new Kernel with CM7 too... seems to be quite stable so far...
More results after more days of full use...
Related
OK guys, My solution to the reboot data corruption is to install an ODEX version. I figured out that the DALVIk-CACHE was the main culprit, thus with an odexed version there are less data written to the DALVIK-CACHE.
USE l1q1d's latest 11/29 kernel.
This is my latest build BETA 3 protection. I have made changes on the way partitions are mounted, extra mount options added to /data to decrease writes and more speed. All apps in data are automatically odexed and a few apps in system folder is odexed. Wifi tether, skyfire, estrong file explorer etc were moved to system to provide more space in data partition for odexing apps. Few files in the build are replaced.
BETA3
http://www.4shared.com/file/yDdKUQcL/androidinstall_8.html
HOW TO INSTALL:
1. Clear Dalvik-cache and repair permssions
2. Install androindinstall.tgz
3. Install all your apps, MAKE SURE YOU INSTALL TERMINAL EMULATOR
4. Open Terminal Emulator and type:
su
sh /system/bin/odex.sh (This will odex your apps without rebooting)
Wait till it is finish.
5. Reboot
6. Make sure you press the D-Pad while reboot to enter LAUNCHER
7. Clear-Dalvik cache
THAT"S IT Hope this helps and let me know how it goes.
-------------------------------------------------------------------------------
------------------------------------------------------------------------------
Beta2 (depreciated)
http://www.4shared.com/file/p0BrSQVK/androidinstall_7.html
----------------------------------------------------------------------------------------
Beta1
http://www.4shared.com/file/lvONbK35/androidinstallodex.html
ENG/Spanish Only.
*** DO NOT DO A RESTORE of APPS, INITIAL FRESH INSTALLATION OF APPS IS REQUIRED ***
Rename to androidinstall.tgz and install system/data on NAND
Requirements and tips:
1. LATEST 11-27 kernel by l1q1d 2.6.32
2. Install system and data on NAND only
3. Radio 1.65 - 1.70 (reported issues with 1.71 have been noted but not verified)
4. Overclock and Reboots should be done within reason
5. If you press the power button and it seems like it is not responding, It's on Fake Vsync mode. Open keyboard and press FN+Left Soft button, then FN+ Right Soft button and it should wake it up.
BTW, if you were having any issues with my Final Release, it would be the same issues with this build. This is basically just an ODEX'd Version of my Eng/Spanish ROM
Bring it on !! I spent all of my sunday getting my TyTn2 to work on your builds....lets hope this one will be The One !
Much appreciated !
btw: do I need to make an install-sq with atools? with what settings ????
Goldfingerz said:
Bring it on !! I spent all of my sunday getting my TyTn2 to work on your builds....lets hope this one will be The One !
Much appreciated !
btw: do I need to make an install-sq with atools? with what settings ????
Click to expand...
Click to collapse
Let me know specs for your tilt and I'll upload one after I upload the rom..eg. Keyboard type, Screen type, battery...BTW, are u using 1.70 radio now?
PM me the data and I'll PM you of the link
clemsyn said:
Let me know specs for your tilt and I'll upload one after I upload the rom..eg. Keyboard type, Screen type, battery...BTW, are u using 1.70 radio now?
PM me the data and I'll PM you of the link
Click to expand...
Click to collapse
okay, done !...thanks !
Goldfingerz said:
okay, done !...thanks !
Click to expand...
Click to collapse
Check ur PM, I need more info
currently my kaiser is running your build, but i haven't done a reboot yet.
what could happen if i do it?
vaupunkt said:
currently my kaiser is running your build, but i haven't done a reboot yet.
what could happen if i do it?
Click to expand...
Click to collapse
A chance of data corruption since it is deodexed and would have more data written in dalvik-cache. Simply clearing out the dalvik cache and fixing permissions should help. With an Odexed build, there are less data written in dalvik cache coz the data is with the odex files.
thank you!
is there a way, to install it as an update?
so that it won't delete everything?
just rename it to "androidupdate" instead of "androidinstall"?
vaupunkt said:
thank you!
is there a way, to install it as an update?
so that it won't delete everything?
just rename it to "androidupdate" instead of "androidinstall"?
Click to expand...
Click to collapse
Sorry, I don't think there is a way to make an androidupdate, the whole odex build is different in a way..
Gonna take it for a spin right now
Gonna give it a shot right now, send u my impressions later, thkns in advance
Update
OK, did my igo GPS to go to McDonalds, did some browsing at McDo then went home played some music, pulled out the battery while playing music...STILL NO loop, FC or lost app...so far so good. If this is OK for 24 hrs, I'll take off the beta label.
could you please also update the corresponding one for installation on system/NAND and data/SD?
I tried the version of system/NAND and data/SD with the latest the kernel. it crashed and rebooted many times.
cqf20022002 said:
could you please also update the corresponding one for installation on system/NAND and data/SD?
I tried the version of system/NAND and data/SD with the latest the kernel. it crashed and rebooted many times.
Click to expand...
Click to collapse
I don't think this odex will work with SD coz I haven't tried it. I suggest you try to Final release instead of this odexed beta for NAND installation. The main purpose of this release is to attempt to fix data corruption on NAND installation (which so far this odex version has done for me at the moment).
Update:
Pulled the battery out and reboot was OK. Ate dinner with the family. Went back and was stuck on white screen. Was on massive Fake Vsync so I pulled the battery out and restarted. Looks good except my Launcher had no app (black blank), it might have been loading but I pulled the battery out again....Turned it on and everything is back as it should, no FC no rpc loop, every app back in launcher. Still looks good.
Hey clem I'm testing ur SD build with latest l1qu1d's kernel (11-27) its rock solid but kinda sluggish... how's ur new build in speed? I mean, its odexed.. that's a pro, but I have my doubts bout having cache on the SD (look at my sig, I'm using a class 2 SDHC) could it be compared to a NAND or its more lika a SD installation?
Sent from my Kaiser.
clemsyn said:
Update:
Pulled the battery out and reboot was OK. Ate dinner with the family. Went back and was stuck on white screen. Was on massive Fake Vsync so I pulled the battery out and restarted. Looks good except my Launcher had no app (black blank), it might have been loading but I pulled the battery out again....Turned it on and everything is back as it should, no FC no rpc loop, every app back in launcher. Still looks good.
Click to expand...
Click to collapse
Didn't realized I overclocked at 570...will drop it to 475 but so far no reinstallation required.
albertorodast2007 said:
Hey clem I'm testing ur SD build with latest l1qu1d's kernel (11-27) its rock solid but kinda sluggish... how's ur new build in speed? I mean, its odexed.. that's a pro, but I have my doubts bout having cache on the SD (look at my sig, I'm using a class 2 SDHC) could it be compared to a NAND or its more lika a SD installation?
Sent from my Kaiser.
Click to expand...
Click to collapse
Yeh, class 2 is pretty slow so that is your slow down. I would you ask you try this odexed build for NAND installation on both system and data. So far so good for my testing.
So far, so good
well beem triying this for like 2 hours and got to say its neraly perfect, i´ve rebooted 3 times now and everything is working perfectly
i put on the NBH the following config:
Kaiser, panel type 2, 240X320, froyo, tilt,and overcloked to 470 and is working woderful with wifi, many widgets, and a lot of apps installed about 12, have not triying data and oo i almost forgot, im using latest l1qu1d kernel 27-11
mizad09 said:
well beem triying this for like 2 hours and got to say its neraly perfect, i´ve rebooted 3 times now and everything is working perfectly
i put on the NBH the following config:
Kaiser, panel type 2, 240X320, froyo, tilt,and overcloked to 470 and is working woderful with wifi, many widgets, and a lot of apps installed about 12, have not triying data and oo i almost forgot, im using latest l1qu1d kernel 27-11
Click to expand...
Click to collapse
Thanks for trying it I think we really got it this time. I was driving with Igo Running, asked my wife to pull out the battery while Igo was running (this usually gives me errors and requires reinstallation) and locked on a signal. Then turned it back on...no errors, no loops, all apps still in my Launcher.
I will build an all language after 24 hrs of testing this.
Hey Clemsyn! Thanks for this build, I'm testing right now. So far so good. Turned off, turned on. Pulled battery, Still working.
Now I have a question, Way before, when I used Vanilj Eclair, I never had any problems with data corruption. I used the build for like 3 months before I decided it was time to upgrade to a more Up-to-date Android Build for my Kaiser. My main point is, Why is it just now that there are problems with Data corruption??? Thanks!
hi guys,i'm wondering,what is the best and stable Android build that u haved tested? i see alot of builds here but i dont know witch one to choose
All builds are pretty good, it really depends on your personal taste, and what you're looking for.
I'm running Not So Super Froyo Latest RLS, with 2.6.25 kernel by l1q1d, so far pretty good build.
Had several crashes the last 2 weeks, but all kernel related to phone sleeping, but minor data corruption (fixed by reinstalling the corrupted app, unless it's a system file then I just reinstall the build)
Krazy-Killa said:
All builds are pretty good, it really depends on your personal taste, and what you're looking for.
I'm running Not So Super Froyo Latest RLS, with 2.6.25 kernel by l1q1d, so far pretty good build.
Had several crashes the last 2 weeks, but all kernel related to phone sleeping, but minor data corruption (fixed by reinstalling the corrupted app, unless it's a system file then I just reinstall the build)
Click to expand...
Click to collapse
exactly the same on polaris
phone
crashes on phone sleeping?
dany547 said:
crashes on phone sleeping?
Click to expand...
Click to collapse
Probably due to me tinkering so much.. Some people have the issue others don't. lol
Krazy-Killa said:
All builds are pretty good, it really depends on your personal taste, and what you're looking for.
I'm running Not So Super Froyo Latest RLS, with 2.6.25 kernel by l1q1d, so far pretty good build.
Had several crashes the last 2 weeks, but all kernel related to phone sleeping, but minor data corruption (fixed by reinstalling the corrupted app, unless it's a system file then I just reinstall the build)
Click to expand...
Click to collapse
your systems apps should not get corrupted, potentially minor data loss though because of the odexing process the classes.dex files are not kept in the dalvik cache. so the only thing that could have a problem is the launcher.
this is what the reboot protection was moving the dalvik to the sd so that way it wasnt kept on the system, since the sd does unmount when shutting down
for me the best is Fat Free Froyo with lastest 2.6.25 kernel from git.
The stability really comes from the .25 kernel as it is much more older and mature. My barebones build might work with .25? I haven't tested it but I recall someone saying it worked.
I don't think it will work since scooters cyanogen has a different libskia than other builds
aceoyame said:
The stability really comes from the .25 kernel as it is much more older and mature. My barebones build might work with .25? I haven't tested it but I recall someone saying it worked.
Click to expand...
Click to collapse
Sent from my HTC Hero using XDA App
Oh I know, was just saying that someone said they got it to work so just saying it might work lol
thoughtlesskyle said:
your systems apps should not get corrupted, potentially minor data loss though because of the odexing process the classes.dex files are not kept in the dalvik cache. so the only thing that could have a problem is the launcher.
this is what the reboot protection was moving the dalvik to the sd so that way it wasnt kept on the system, since the sd does unmount when shutting down
Click to expand...
Click to collapse
Apparently that doesn't work for me, especially with the 2.6.32 kernel. No matter how I reboot (button, battery, actual menu option), almost all apps get corrupted, and the Framework gets completely shot the **** (no lock screens, unable to silence phone or turn on Airplane mode).
The Dalvik move to SD apparently doesn't work for me either, unless it's only on a certain build? I'm using Not So Super Froyo RLS18.
I must reflash rom every one -two day, its crash, not workink proceses, system its very slow, after restart phone not remember settings and sometimes delete any data. i test very much roms,
Best Android build is Warbyte Donut for me, very stable and all works fine and quickly, but it is Donut and I Need Froyo..
i see
i got instaled a Donut build,but the white screen and the file system coruption made me to switch back to Wm i'll w8 untill a new build will appeare
fat free
I've got the fat free froyo on kaiser with .32 kernel downloaded with atools.
It works fine with an sd system install (class 6). Fast and stable.
You can olso try system on nand and data on sd! I could not do this because my nand is corrupt....but the result was really good.
The problem you were having was caused by your kernel not the build
dany547 said:
i got instaled a Donut build,but the white screen and the file system coruption made me to switch back to Wm i'll w8 untill a new build will appeare
Click to expand...
Click to collapse
Sent from my HTC Hero using XDA App
no
no,the karnel was for my device
dany547 said:
no,the karnel was for my device
Click to expand...
Click to collapse
Yes it was a kernel fault. Listen to people who are more knowledgeable than yourself. Next time install kernel from '25 branch which is stable and doesn,t suffer from white screens and data corruption. The kernel you used was experimental and it still doesnt work as well as we would want it to.
dany547 said:
no,the karnel was for my device
Click to expand...
Click to collapse
people like you the, i know everything because i manage to get android booting on my windows mobile phone even though i looked at maybe 1 tutorial and read it half way. the flash first read 2nd type. are pretty much the entire reason why there hasnt been a new Not so super or fat free froyo.
-Arturo- said:
Yes it was a kernel fault. Listen to people who are more knowledgeable than yourself. Next time install kernel from '25 branch which is stable and doesn,t suffer from white screens and data corruption. The kernel you used was experimental and it still doesnt work as well as we would want it to.
Click to expand...
Click to collapse
is u want to give me that Kernel i'll apreciate! my karnel was from l1q1d's page (2.6.32)
Well, I've been loving Voodoo on my Galaxy S Fascinate for quite a while now, so I've decided to get it running on our Tab. This version has a fully functional version of Voodoo CwM. It is based off of CWM 2.5.x and not 3.0. 3.0 isn't nearly as good IMO. You do not need to have Koush's bootstrapper or recovery installed. However, if you do, it's okay as well.
I haven't tested the conversion process yet, so I'm just going to say this until someone tells me otherwise.
YOU DO NOT NEED TO HAVE CWM INSTALLED!
Fixing it is the next big thing on the list. I promise.
Preamble
1. Don't ask me on how to install koush's recovery, that's what his thread is for. Laymen's terms- Did you do THIS? If you did, you're good to go, if not. do it.
2. I am not going to teach you how to use, or set up the applications that you need to use/flash this. I have included links to everything you need to know, just click and read for a second. If you are not willing to put out a little bit of effort to better your experience with your Tab, I am not going to waste even more of my time that could be dedicated towards making my kernel better. Also, if you aren't willing to give yourself the fundamental knowledge required for flashing this and something goes wrong, you will then have the required skill to fix it, instead of blaming me for bricking your Tab. I don't need that. I am willing to support my ROM and help with some confusion, but if you want me to do everything for you- lo siento.
What is Voodoo
Read about it HERE. Note, some of the information is outdated, but it's still a good general idea.
Features
Voodoo CwM v2.5.3.x Recovery for all your flashing/backup/restore needs.
TBH, I can't remember them all off the top of my head. I'll need to double check for all of them.
Tun.ko support
CIFS support
Slow-work.ko support
ext4 support
Voodoo lagfix!
Voodoo Sound fix!
Optional 1.4GHz overclocked kernel.
AOSP Boot animation support (I haven't tested fully yet)
init.rc speed/stability optimizations
many, many other tweaks
Changelog
v5 Major Update - Highly recommended install
Based on EC02 kernel source
Added Powersave, Userspace and Ondemand CPU Governors
All patches and modifications from before have been added to the EC02 kernel source
Fixed a conflict with TinyRCU (a goof up I didn't notice I made with the DJ11 source, this helps an immense amount with stability)
Tweaked the touchscreen voltage to help with battery life
Added ext4 patches from the 2.6.32.11 kernel (found here http://kan.gd/8hp), thanks to imnuts for pointing them out.
Overall this kernel is much smother and stable from the last 12 hours of my testing. Take it for a spin and let me know what you think. BT HID? Maybe, I've given up trying to get it to work until I have the ability to test some of the devices myself.
I didn't update the Odin tars or heimdall/SGS kernel flasher links from v4 because A. Most of you should have CWM installed at this point anyway and B. If you're not, step 2 will write over the kernel partition anyway (the recovery partition is only used on very rare occasions and the version difference won't make a difference)
v4 Major Update - Highly recommended install
I'm just including the updates from v3 (that never made it to the first post) in v4 for the changelogs sake.
Voodoo Sound updated to version 7, many thanks to supercurio again, and thanks to JT for reminding me that SC actaully updates his code like a madman!
Lzma compresson on the intiramfs (lowering the file size to just over 6MB, from 7.4) This will increase the speed a bit, but mostly it allows for more room for me to add more BT HID modules (lots of devices require their on module, which is why some devices work and some don't currently) and other features I find down the road
Replaced Samsung's RCU with TinyRCU (ported to the tab by jt1134, many thanks)
Added lowmemorykiller, this should give you a good 240MB free at boot
Okay, I don't want to shoot myself in the foot, but I think I really got BT HID this time, for most common products. We'll find out though!
More modules built from source (vibrator.ko, dhd.ko, tun.ko, dpram_vzw.ko, s3c_lcd.ko, s3c_bc.ko, pvrsrvkm.ko, dpram_recovery.ko and cifs.ko)
I'm stopping the production of the 1.0GHz branch of kernels, if you don't want to run it at 1.4GHz, just use setCPU to have the max be 1000MHz, there will be no difference.
Also, If you test this for BT HID please report back to me on the working, or non working status including the information below
PLEASE
device - Manufacturer and Model number would be great.
status - did it pair and work? did it just pair and not work? did it not pair at all? did it not detect at all?
It would be really, really helpful. This is one feature I'm adding for you, the users. I have a pure and utter hatred for the bluetooth protocol and have no BT hardware, at some point it would be cool to have onna those little apple keyboards though.
v3 Major Update - Highly recommended install
Fully functional CwM. This is about the only change, but it's a huge one. This allows for flashable zips, clearing of dalvik cache, normal cache, toggling of Voodoo features and more! I am working on a tutorial for those new to how Voodoo CwM works.
Other small tweaks and init optimizations.
Rebuilt initramfs from base code to insure optimal build and function.
New Branch 1.4GHz overclocked Version added. It's fast.
See below for downloads.
Don't forget to download the Voltage Control App | (source)
v2 - Feature update
Added Voodoo Sound! Thanks to some (a lot) of help from supercurio, we know have the benefits of his sound fix in addition to his lag fix. Get the Voodoo Control App off the market to see it's full feature set. It's a difference you have to hear to believe.
v1.1 - Maintenance update
Added slow-work.ko
v1 - Initial Public Release
Primary Recovery is jacked. to get into a (more) functional backup recovery, boot into recovery, go into the advanced menu and reboot recovery will bring you into the backup recovery.
Plans
streamlining it some more and sorting out any issue that make revolve around current features. Got an idea, throw it my way, but I am not going to guarantee I'll do anything about it. Full Bluetooth HID support (wimote, apple keyboard, etc).
Known Issues
Sometimes on the first boot after flashing I will have a FC window pop up, but with no description of what is force closing. If I click force close on this, I end up having wifi problem. If I click wait I do not wifi issues.
This will work with Sprint Tabs, however there are some compatibility issues, namely, it will mount on your PC as a CDROM drive, not a removable disk. Fix - Use dropbox or CIFS. Also, the camera doesn't work properly on the Sprint Tab. I will start a new branch with 100% Sprint compatibility As soon as I can.
If you run into any issues, boot into recovery, clear cache and dalvik cache (in advanced menu)
If you have any further issues with the initial boot/conversion, hold down the power button until the device powers off and reboot into recovery (power + volume up). Go into the advanced menu, turn off voodoo lagfix and voodoo system lagfix. Now Reboot, you should fully load into android. Reboot into recovery and enable the lagfixes. Conversion should happen successfully now.
Conversion will not occur if you don't have a SD card inserted or if your SD card is full.
Installation
Read the instructions all the way through before starting
Part 1
For initial installation only! If you have v3+ installed already, skip to part 2!
I have documented how to flash your initial installation two ways. If one way doesn't work for you, try another. You do not need to use all 3 methods! Using the SGS Kernel Flasher should be the most fool proof method, FYI.
Option A: Heimdall
Download a kernel zImage- 1.4GHz Overclocked Kernel
Power Down your device
Boot into download (Power + Volume Down)
Flash Via heimdall GUI in the kernel and recovery or via command line with heimdall flash --recovery *filename* --kernel *filename*
Pay attention to the progress.
When the progress bar gets to 100% your tab will reboot. If everything has gone as it should. Your installation is now complete. If you have any issues, see above in the known issues section.
You do not need to continue to step two, but I would recommend it, just to make sure everything is flashed correct.
Option B: SGS Kernel Flasher
READ ABOUT SGS KERNEL FLASHER HERE
Download a kernel zImage- 1.4GHz Overclocked Kernel | (Voltage Control App) | (source)
Flash via SGS Kernel flasher (really, just select it. I don't think anyone should be lost by this process).
Continue to Part 2
Option C: Odin
Download a kernel tar package- 1.4GHz Overclocked Kernel | (Voltage Control App) | (source)
Power Down your device
Boot into download (Power + Volume Down)
Flash via PDA in Odin. Do not change any other options.
Continue to Part 2
Part 2
This step insures that the recovery partition was successfully flashed and that everything is functioning successfully. Also, a how to flash zip's via recovery tutorial for those that haven't before.
Download a kernel zip package- 1.4GHz Overclocked Kernel | (Voltage Control App) | (source)
Power Down your device
Boot into recovery (Power + Volume Up)
Voodoo CwM controls! Volume up/down = Navigate up/down || Power button = Select/confirm || Back = Back || Menu = Screen Toggle || Home = Screen Toggle || Search = Nothing
Select install zip from sdcard
Select select zip from sdcard
Navigate to the location of your downloaded .zip
Select zip
Select yes in confirmation screen. My install script will scroll through and say install from sd card successful if all has gone as planned.
Rejoice and be happy
Make themes/mods/ROMs/hacks/awesomeness to share!
Thanks
jt1134, Adrynalyne, rotohammer, TCMAN, Supercurio, koxudaxi, Punk.Kaos, mike, buggs, 1techydude everyone in IRC as usually is great help. Kangers, women, kittens, ninjas, Open Source.
Finally, if you like my work, donate to me so I can donate money to devs that make my world easier (and therefore yours).
i knew we were bound to see voodoo for they tab, willing to make for gsm?
I've been thinking about it, but no promises.
Boushh said:
I've been thinking about it, but no promises.
Click to expand...
Click to collapse
at least you thought about it. adding this to the bible
What is difference between standart ext4 fs and voodoo lagfix when the sound improvements arent ported yet?
Sent from my GT-P1000 using XDA App
Is there a noticeable speed boost with kernel? I don't have a galaxy s phone and I've never uses the lag fix so I'm curious as to the real world benefits and risks of this kernel
Sent from my SPH-P100 using XDA App
futuregerald said:
Is there a noticeable speed boost with kernel? I don't have a galaxy s phone and I've never uses the lag fix so I'm curious as to the real world benefits and risks of this kernel
Sent from my SPH-P100 using XDA App
Click to expand...
Click to collapse
Yes it is. if you care about benchmarks I'm getting around 14mflops in linpack and 1750 in quadrant, which is more than I was getting with just the ext4 conversion. I've done a lot of other optimizations to this. However, the only real way to see if you like it is to try it out yourself and see if it works for you.
I see you say this should work on sprint, but there is no working CWM for sprint so how the hell do you get ext4 then?
Sent from my SPH-P100 using XDA App
idumych said:
I see you say this should work on sprint, but there is no working CWM for sprint so how the hell do you get ext4 then?
Sent from my SPH-P100 using XDA App
Click to expand...
Click to collapse
I am not saying you are rude I am just saying that sounded rude... don't take it personal it's just that coming off a little more polite is more likely to get you some help/answers.
You are awesome! Once everything is ironed on ill bust my Sprint tab out the drawer! Can't wait!
Sent from my PC36100 using Tapatalk
idumych said:
I see you say this should work on sprint, but there is no working CWM for sprint so how the hell do you get ext4 then?
Sent from my SPH-P100 using XDA App
Click to expand...
Click to collapse
Well, I have heard of people flashing CWM 3.0 on their sprint tabs using the vzw kernel. it's in the CWM 3.0 beta thread. So, there's that. Or you can manually convert your system to ext4.
What does any of that have to do with my thread? Seriously.
sh!t sorry, to many threads open and this is the wrong one. I am working on extracting a working modem.bin for the sprint device is all. I'll edit those out or have a mod delete them, sorry folks.
HAH! No worries, I thought as much, just wanted to make sure.
Boushh said:
Well, I have heard of people flashing CWM 3.0 on their sprint tabs using the vzw kernel. it's in the CWM 3.0 beta thread. So, there's that. Or you can manually convert your system to ext4.
Click to expand...
Click to collapse
I just read that thread an no one says they got it working
Anyone know where I can find info how to convert it manually? Everything I've read says you must have CWM.
Fantastic! As a verizon tab user, i'm grateful to you boush for working on giving us cdma people some options.
I'm going to wait until the recovery is ironed out before flashing, but great work!
b0ricuaguerrero said:
i knew we were bound to see voodoo for they tab, willing to make for gsm?
Click to expand...
Click to collapse
+10
I actually PM'd Hardcore also if he wants to make his kernel for Tab as well... but I think the dude has no Tab
Read it again, I just did last night on my sprint tab, posting details later tonight.
Sent from my SPH-P100 using XDA App
If the title says it's for Sprint/VZW why would you come in here asking about GSM?
I'm also curious how to convert to EXT4 manually?
cruiserbax said:
Read it again, I just did last night on my sprint tab, posting details later tonight.
Sent from my SPH-P100 using XDA App
Click to expand...
Click to collapse
Looking forward!
shoman24v said:
I'm also curious how to convert to EXT4 manually?
Looking forward!
Click to expand...
Click to collapse
Not sure, since im still too noob to mess with this and to top it off, just went full time with ubuntu and got rid of win7, and need to figure out all this driver stuff ,
soo i think the manual method its listed in this thread via ADB , but please dont flame if im wrong, still new to this tab stuff
http://forum.xda-developers.com/showthread.php?t=870690&highlight=recovery+BETA
Flash the kernel using flash_image: http://koush.tandtgaming.com//test/flash_image (This will flash both boot and recovery)
adb push flash_image /data/local/bin/flash_image
adb push verizon_zImage /sdcard/
adb shell
su
chmod 755 /data/local/bin/flash_image
/data/local/bin/flash_image boot /sdcard/verizon_zImage
sync
exit # This should take you back to your computer's console
adb reboot recovery # Boot into recovery
CyanogenMod 11 KitKat for Optimus S/V
This is a basic CyanogenMod 11 rom for the Optimus S/V. It has NOT been tested extensively and I take NO responsibility for any bricked phones, data loss or damages that occur as a result of flashing any version of this rom. It requires ClockWorkMod 6.0.4.5 or later, or TWRP 2.6.3 or later, in order to flash.
What works:
Phone calling (ZVH and ZVJ radios require a patch)
Wifi
Mobile data (thanks to thekraven)
USB tethering
Camera
USB mass storage, MTP
What's broken:
Bluetooth
Wifi tethering
SELinux
You tell me
CWM 6.0.4.6 can be found in the rom directory. Flash Skinny_4.4_Gapps.zip after flashing the rom to get Play Store and Google Sync. Other Gapps will probably be too big to fit on /system.
https://www.mediafire.com/folder/nfgfef6qpril7/CM11
Contributors:
skinbark
bigsupersquid
thekraven
Special thanks to the CyanogenMod and androidarmv6 teams, also gu5t3r for GOptimize.
CM11 KitKat os2sd Version:
cm-11-20140116-thunderc-skinbark-sd.zip is a version of CM11 which is designed to run off your sd card.
To use this version:
1) create and format 3 ext4 partitions following the fat32 partition on your sd card (use gparted not a windows partitioning tool)
/data - at least 256 mb (512 mb or more recommended)
/system - at least 256 mb
/cache - at least 256 mb
2) format /boot in cwm
3) install cm-11-20140104-thunderc-sd.zip
4) install Skinny_4.4_Gapps-sd.zip and reboot
Known Issues (in addition to those in post #1):
formatting/backup/restore issues
possible reduced performance (older/slower sd cards)
reduced battery life (?)
Add wipe zips to a folder on your sd card and flash them from recovery to clear external /data, /system, /cache, or all three.
CWM_6.0.4.6-thunderc-sd.zip is a special version of CWM for os2sd that should only be used if you understand how it works.This version of CWM is not necessary to flash the os2sd rom. See this post for more info about recovery issues with this rom.
A Class 10 microSD card is recommended for best performance.
Power off or reboot to recovery before removing sd card.
os2sd mod courtesy of bigsupersquid
https://www.mediafire.com/folder/dj2d4vpp0hzvb/CM11sd
Warning: This is a highly experimental setup and a work-in-progress. You should have adb installed and know how to use it, along with the flash_image command, before attempting this install. If you have trouble installing this and are unsure how to resolve the problem ask for help on this thread. I take no responsibility for bricked devices, data loss or any other damages resulting from the use of this software. USE AT YOUR RISK.
New build with rild fix for ZVD/ZV5. You'll want to upgrade to this for stability and battery life even if you're not activated.
cm-11-20131225-thunderc-skinbark.zip
Link in OP.
Merry Christmas guys!
Sweet! Will flash once o find my ov...
Virgin fix uploaded.
Virgin.fix.CM11.0.zip
Link in OP.
I'll test. I still use this phone a bit. I don't use gapps anymore so I wouldn't be ale to ile any bugs against them. Is thereanything in particular you want tested?
captaincrook said:
I'll test. I still use this phone a bit. I don't use gapps anymore so I wouldn't be ale to ile any bugs against them. Is thereanything in particular you want tested?
Click to expand...
Click to collapse
Well the biggie right now is getting data going which is sort of difficult for me since my phone's not activated (next week I hope). I'm assuming you're not activated? I guess just general stability and performance, battery life, see what you can run on on it, put it through the wringer. All info is welcome since I really haven't had much feedback yet. It seems to be pretty stable. Let me know if you have any problems, thanks.
really works well...nice job. No chance to test 3g data yet, but everything else works very well...I had to install a keyboard manually, and the battery stats are wrong (fully charged, and stayed fully charged all day) but it is def a daily driver for me.
I uploaded a new 'OS2SD' rom with special recovery, gapps and virgin fix:
cm-11-20140101-thunderc-sd.zip
CWM_6.0.4.6-thunderc-sd.zip
Skinny_4.4_Gapps-sd.zip
Virgin-fix-CM11-sd.zip
Link in post #2. Happy New Year!
Got the order of the partitions wrong in post #2, sorry. Fixed now. 3G fix coming soon!
I uploaded new standard and os2sd builds with data fix.
cm-11-20140104-thunderc-skinbark.zip
Link in post #1
cm-11-20140104-thunderc-sd.zip
Link in post #2
After a crash fest with the build at the time of my last post, this newish one is alright so far. Things get choppy fast and the input is a real pain. That is about as good as I have it. Alternate market works, wifi is good, and its chugging along.
captaincrook said:
After a crash fest with the build at the time of my last post, this newish one is alright so far. Things get choppy fast and the input is a real pain. That is about as good as I have it. Alternate market works, wifi is good, and its chugging along.
Click to expand...
Click to collapse
long press home and press the three-bar onscreen button to close running apps.
also fast reboot off market is very handy to manually clear ram. heard about that one from andyopie150, like it.
Ya the main issue is just generally its a bit slow. I'm not trying to be one of those people who dog the ROM cause devs sibt human but this is just what I have experienced. I know our SOC came out when Moses was around so I'm not expecting miracles. I'm not sure if you guys have more planned or not but its really neat how efficient the phone is on 4.4 and if it was to get faster it'd be amazing.
The keyboard, can you guys adjust the size values? Its microscopic! Hacker's Keyboard fits the bill in the meantime.
captaincrook said:
Ya the main issue is just generally its a bit slow. I'm not trying to be one of those people who dog the ROM cause devs sibt human but this is just what I have experienced. I know our SOC came out when Moses was around so I'm not expecting miracles. I'm not sure if you guys have more planned or not but its really neat how efficient the phone is on 4.4 and if it was to get faster it'd be amazing.
The keyboard, can you guys adjust the size values? Its microscopic! Hacker's Keyboard fits the bill in the meantime.
Click to expand...
Click to collapse
For now I can just suggest the usual speed-up stuff - turn off animations, ksm, cpu/governor etc. There may be some build.prop tweaks you could use, and I'm expectiing zram support to be enabled soon. Crossbreeder might be something else to try. If we could get ART going it might help some but I don't know if that's likely. I probably won't try to tweak the stock keyboard, there's plenty of alternatives available.
tried flashing this on my optimus V and i got a error when i was flashing it, error 7 i think it was, i used the CWM you wanted us to use but it made it so that i couldnt boot into recovery.
Trozzul said:
tried flashing this on my optimus V and i got a error when i was flashing it, error 7 i think it was, i used the CWM you wanted us to use but it made it so that i couldnt boot into recovery.
Click to expand...
Click to collapse
regular rom or os2sd?
skinbark said:
regular rom or os2sd?
Click to expand...
Click to collapse
regular i tried a different CWM 6+ and that one gave me the error*
Trozzul said:
regular i tried a different CWM 6+ and that one gave me the error*
Click to expand...
Click to collapse
Here's another recovery you can try.
https://www.mediafire.com/?s8c94941y8kubdd
captaincrook said:
Ya the main issue is just generally its a bit slow. I'm not trying to be one of those people who dog the ROM cause devs sibt human but this is just what I have experienced. I know our SOC came out when Moses was around so I'm not expecting miracles. I'm not sure if you guys have more planned or not but its really neat how efficient the phone is on 4.4 and if it was to get faster it'd be amazing.
The keyboard, can you guys adjust the size values? Its microscopic! Hacker's Keyboard fits the bill in the meantime.
Click to expand...
Click to collapse
Any information is a good thing, positive or negative. Harmonia with the Xionia kernel fairly flies speed-wise, but everything since that seems to choke my phone somewhat. And Mirage is the best Gingerbread available... but I enjoy the extra features more than the speed, which is what keeps me trying for the bleeding edge.
(example: the double-tap-hold-and-slide to zoom is built in all over 4.4, in 4.2 I only saw that in Maps.)
ART may or may not happen. I have to learn more thumb assembly to fix it. My decent class for school this session (the easy one since I did 8088 back in 1991) is x86 assembly. Doesn't apply, but maybe I can get more parallell info from it. There's lots of good info out on the net with minimal searching as well, but not much if any on downconversion of thumb2 to thumb1 code. I found enough to fix a few files but there's still more to go. I'd be impressed with myself if I got that to run.
CrossBreeder seems to work.
Q&A for [ROM][UNOFFICIAL] CyanogenMod 11 Nightlies / Releases [M11]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
my desire hd cant boot when i swich to ART mode
Mustaavalkosta said:
General:
These are UNOFFICIAL CM11.0 Kitkat Nightlies / Releases brought to you by AceEnablementProject and TeamCodefire as a continuum to CM10 and 10.1 nightlies. Builds are generated automatically each night. Process starts around 00:30 PDT. If it fails, then there will be no build until the reason for failure is taken care of which can take time. Latest 12 nightlies will be kept on the server. If you want a longer history of them, you are free to archive them yourself.
Thanks and credits:
Andromadus
CodeAuroraForum
CyanogenMod
BananaGranola
Epic Beard Men
eXistZ
Flemmard
Flinny
goo.im
Juansheng
paulb_nl
randomblame
synergye
TeamCodefire (for build server and hosting, priceless)
All the rest that have helped to construct these builds and develop software for ace directly or indirectly in the past.
Githubs:
CyanogenMod
AceEnablementProject
Changelogs:
CM Gerrit
CM Google+
Github (see above)
Installation instructions:
Download Nightlies / Releases [BasketBuild mirror]
Download gapps from here. Pico/Nano/Micro recommended, Mini/Full/Stock doesn't fit in our system partition after the ROM has been installed.
Put the files on SD card.
Reboot to recovery.
Do factory reset (ie. format /data, /cache, /sd-ext and /sdcard/.android_secure)
Flash cm-11-YYYYMMDD-UNOFFICIAL-ace.zip
Flash gapps zip
Remember to reflash boot.img via fastboot if you are HTCDev unlocked.
Reboot and enjoy.
Update instructions:
Download Nightlies / Releases [BasketBuild mirror]
Put the file on SD card.
Reboot to recovery.
Flash cm-11-YYYYMMDD-UNOFFICIAL-ace.zip
Remember to reflash boot.img via fastboot if you are HTCDev unlocked.
No need to flash gapps as CM backuptool script should take care of them. (Results may vary depending on which gapps package you are using.)
Reboot and enjoy.
InspireMod
http://downloads.codefi.re/mustaavalkosta/inspiremod
Kernel
Source: github
Compiler: stock AOSP gcc-4.7
Branch: cm-11.0
Kernel Version: 3.0.101
defconfig: spade_defconfig
Contact:
My Google+
My twitter
#codefireX @ freenode
Donations:
For hosting: codefi.re (use the donation button at the bottom of the page)
I don't really need your money right now but if you insist on donating to me I suggest you donate that money to EFF instead here: https://supporters.eff.org/donate
Q&A:
Q: I tried to flash the ROM and got this:
Code:
Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/..path od ROM.zip
(Status 7)
Installation aborted.
A: Update your recovery to one that is compatible with new recovery functions. See the list below.
4EXT Recovery Touch v1.0.0.6 RC 3 or newer
CWM 6.0.4.8 Advanced Edition / PhilZ Touch 6.29.8 or newer
TWRP 2.7.1.0 ACE or newer
Q: I've used HTC Dev unlock and flashed the rom but it won't boot. What should I do?
A: You need to extract boot.img from the zip and flash it via fastboot. If you don't have fastboot executable anymore from flashing recovery, install Android SDK platform tools (Linux users should find it from distro's package management) and then reboot to bootloader, open command prompt and navigate to the location you extracted your boot.img and type:
Code:
fastboot flash boot boot.img
You need to repeat this everytime you flash new version of this rom to ensure everything will work fluently as long as you have just basic HTC Dev unlock.
Q: Where are my developer and performance options?
A: http://goo.gl/jpS8r
Q: Feature X doesn't work, let's make 1000 posts about it to annoy everyone.
A: Please, dont. Use search and then use search again and only then report your problem with necessary logs. [Logcat guide, thanks to MusikMonk for the link]
Q: I hate you for not fixing this issue X!!!
A: I love you too.
Q: How I can build CM11.0 myself?
A: Setup a basic Android build environment.
Code:
mkdir cm11
cd cm11/
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
mkdir -p .repo/local_manifests
wget https://github.com/AceEnablementProject/android/raw/cm-11.0/local_manifest.xml -O .repo/local_manifests/cm_ace.xml
repo sync
cd vendor/cm/
./get-prebuilts
cd ../../
. build/envsetup.sh
lunch cm_ace-userdebug
mka bacon
Once the build finishes you'll find your goods from out/target/product/ace/ directory.
Q: Something about something something something.
A: Ask the guy/gal next to you.
XDA:DevDB Information
[UNOFFICIAL] CyanogenMod 11 Nightlies / Releases [M11], ROM for the HTC Desire HD
Contributors
Mustaavalkosta, paulb_nl
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Beta
Current Beta Version: M11
Beta Release Date: 2014-10-08
Created 2014-04-11
Last Updated 2014-10-09
Click to expand...
Click to collapse
some saids it`s because the partition of cache is too small
CM11 latest release freezes after first reboot
GD to all. I am trying to install CM11 latest release, first time starts ok, but after reboot it doesn't start, freezes with black screen before bootanimation. Tried to flash boot.img via ADB & also tried to install CM 10.1 SR3, nothing helped, same situation. Waiting for your replies. Thx in advance.
Hey!
Would it be possible to you to add gpu overclock to that kernel?
Thx
Question about bugfixes
Hi,
at the moment i have M10 installed but i want to ask if there is a fix in M11 included which fixes sudden restarts.
My DHD restarts over night or when i want to something (it doesnt depends on what i am doing).
And another Problem sometimes the screen wont turn on when pressing the power button only the menu keys lighten up.
And i think it is more like off topic but how i can unlock the phone that i do not need to flash boot.img it is at the moment only HTC-Unlocked.
And very much thanks for this ROM it is great!
Thanks in advance for your answers
ag1707
Cannot dirty flash Nightlies
Hi
Since sometime around M11 release, I can not dirty flash nightlies on nightlies. The phone stuck at booting with the message "Android is upgrading / Finishing boot".
I'm using TWRP 2.7.1.0 for recovery.
1. Install Rom
2. Wipe Cache/Dalvik (I've tried without wipe too)
3. Reboot System
Am I missing something here?
I'm using non-English locale. Could it be the reason?
Best Regards,
Solved
Nanashi_anon said:
Hi
Since sometime around M11 release, I can not dirty flash nightlies on nightlies. The phone stuck at booting with the message "Android is upgrading / Finishing boot".
I'm using TWRP 2.7.1.0 for recovery.
1. Install Rom
2. Wipe Cache/Dalvik (I've tried without wipe too)
3. Reboot System
Am I missing something here?
I'm using non-English locale. Could it be the reason?
Best Regards,
Click to expand...
Click to collapse
Just figured it out that PA_GAPPS requires flash every update for recent ROMs.
Hi and thx for your rom!
I flashed the cm-11-20141008-UNOFFICIAL-M11-ace from releases, using twrp 2.7.1.0 for the recovery on a HTC Desire HD.
I am experiencing some lag when opening the screen or starting apps / widgets. It can take be almost instant up to 3-5 sec for the app to launch and be accessible (camera, gallery, weather, settings, mail anything really).
Also once in a while parts of the text in the screen get deformed (example here), any action by me (moving my finger around) or by the OS (some notification) fixes it.
As far as I can tell I followed your instructions properly. Is there anything I could try?
XZelin said:
some saids it`s because the partition of cache is too small
Click to expand...
Click to collapse
Possibly. There are some posts about this from paulb_nl on the main thread but I didn't find them right now. They are there though.
sky141 said:
GD to all. I am trying to install CM11 latest release, first time starts ok, but after reboot it doesn't start, freezes with black screen before bootanimation. Tried to flash boot.img via ADB & also tried to install CM 10.1 SR3, nothing helped, same situation. Waiting for your replies. Thx in advance.
Click to expand...
Click to collapse
Are you using the latest recoveries mentioned in the first post's Q&A section in the development thread? If your issue is what I think it is, full wipe with the previously mentioned recoveries should fix it.
_Bon_Bon said:
Hey!
Would it be possible to you to add gpu overclock to that kernel?
Thx
Click to expand...
Click to collapse
Is there working GPU OC for ace? I thought it was hardware locked thus can't be overclocked via software.
ag1707 said:
Hi,
at the moment i have M10 installed but i want to ask if there is a fix in M11 included which fixes sudden restarts.
My DHD restarts over night or when i want to something (it doesnt depends on what i am doing).
And another Problem sometimes the screen wont turn on when pressing the power button only the menu keys lighten up.
Click to expand...
Click to collapse
I haven't heard any complaints about frequent reboots. I know that there are those but it's been said to happen like once a week or so. M11 may change something if your issues come from corrupted devlog partition but if it's something else, then M11 won't do anything for your reboot issue.
Nihim said:
Hi and thx for your rom!
I flashed the cm-11-20141008-UNOFFICIAL-M11-ace from releases, using twrp 2.7.1.0 for the recovery on a HTC Desire HD.
I am experiencing some lag when opening the screen or starting apps / widgets. It can take be almost instant up to 3-5 sec for the app to launch and be accessible (camera, gallery, weather, settings, mail anything really).
Also once in a while parts of the text in the screen get deformed (example here), any action by me (moving my finger around) or by the OS (some notification) fixes it.
As far as I can tell I followed your instructions properly. Is there anything I could try?
Click to expand...
Click to collapse
It's a bit slow but I suppose that's understandable considering we are talking about 4 year old device. People have reported it gets slower the more apps you install. I'm not sure why.
I'm seeing that kind corruption on the screen graphics for the first time. Any chance of figuring out how to reproduce it and write step-by-step what to do so I could maybe replicate the issue on my end?
Mustaavalkosta said:
It's a bit slow but I suppose that's understandable considering we are talking about 4 year old device. People have reported it gets slower the more apps you install. I'm not sure why.
I'm seeing that kind corruption on the screen graphics for the first time. Any chance of figuring out how to reproduce it and write step-by-step what to do so I could maybe replicate the issue on my end?
Click to expand...
Click to collapse
Yea that is very much true, this might sound bad but would is there some other version you would recommend (even if it's a previous android release) which would be snappier? (your ROM so far is absolutely fine outside of that lag which as you stated is probably because DHDs hardware can't handle it).
As for that graphics glitch can't think of something, any apps were installed from play store (not restored by titanium for example) it happens on different ones but a lot more often on k-9 email client (from which the screenshot is).
If there is something that you would like me to try, feel free to tell me, though any action on the screen restores it to its normal way.
Nihim said:
Yea that is very much true, this might sound bad but would is there some other version you would recommend (even if it's a previous android release) which would be snappier? (your ROM so far is absolutely fine outside of that lag which as you stated is probably because DHDs hardware can't handle it).
As for that graphics glitch can't think of something, any apps were installed from play store (not restored by titanium for example) it happens on different ones but a lot more often on k-9 email client (from which the screenshot is).
If there is something that you would like me to try, feel free to tell me, though any action on the screen restores it to its normal way.
Click to expand...
Click to collapse
I don't mind people looking for better solution for their needs. You may want to try my CM10.1 builds which were noticeably faster if I recall correctly. I haven't been using other ROMs that much during the time I've kept my own stuff going here so I can't really recommend anything else. A fellow user may be a bit less biased to recommend other options.
I'll see if I can catch that graphical glitch with K-9 myself. Thanks for reporting it!
Mustaavalkosta said:
I'm seeing that kind corruption on the screen graphics for the first time. Any chance of figuring out how to reproduce it and write step-by-step what to do so I could maybe replicate the issue on my end?
Click to expand...
Click to collapse
I get that black boxes glitch with the standard Email app all the time. They usually go away in less than a second. I also checked for those when I was testing the 4.4 adreno drivers and it was still not fixed.
paulb_nl said:
I get that black boxes glitch with the standard Email app all the time. They usually go away in less than a second. I also checked for those when I was testing the 4.4 adreno drivers and it was still not fixed.
Click to expand...
Click to collapse
Oh ok. If it has been mentioned in the development thread, I've just probably forgotten about it.
Mustaavalkosta said:
I don't mind people looking for better solution for their needs. You may want to try my CM10.1 builds which were noticeably faster if I recall correctly.
Click to expand...
Click to collapse
Thanks! What would be the proper way to backup the whole "phone" so I can switch back and forth between roms? Atm I 'm only backing up apps & data with titanium.
Nihim said:
Thanks! What would be the proper way to backup the whole "phone" so I can switch back and forth between roms? Atm I 'm only backing up apps & data with titanium.
Click to expand...
Click to collapse
Doing a backup in recovery should be sufficient to backup everything except sdcard.
Mustaavalkosta said:
Are you using the latest recoveries mentioned in the first post's Q&A section in the development thread? If your issue is what I think it is, full wipe with the previously mentioned recoveries should fix it.
Click to expand...
Click to collapse
Thx 4 yours above. I'm using latest 4ext recovery touch + full wipe, of course. Will try to do something with partition.
Update from M11 to Nightly
It is possible to flash the newest nightly over the M11 release?
Or I need a full wipe.
Christian1987 said:
It is possible to flash the newest nightly over the M11 release?
Or I need a full wipe.
Click to expand...
Click to collapse
Well, generally it's recommended to wipe if you switch from one to another but it may work in this case without wiping. Make a nandroid backup and try it.
My battery dies really fast. Do you guys have a recommendation in terms of which battery to get? Link it here. Thanks.
prufessor_oak said:
My battery dies really fast. Do you guys have a recommendation in terms of which battery to get? Link it here. Thanks.
Click to expand...
Click to collapse
You can get original Desire HD battery on ebay cheaply, no point looking at other batteries which cost almost the same. Just look for one in your region.
Install Wakelock Detector from the Play store and find out what is causing your battery drain. Depending on phone use it should be able to last all day, 2 days if just left on standby all the time. Screen on all the time will be around 3-4 hours.