Best Android Build! - Tilt, TyTN II, MDA Vario III Android Development

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)

Related

CM6.0.1 issues

I'm aware of the issues associated with CM6 RC3, but when I installed 6.0.1 today, I booted, the touchscreen was non-responsive, but the scroll wheel allowed me to reboot.
Initially, I forgot to install the stock htc kernel over the hydrakernel I had for Sense (#2), so I put that on. When I rebooted, my screen was responsive, but I noticed a lot of page tearing, and my "SD Card is damaged. May require a format" or some such nonsense.
I'd like to try CyanogenMod but thats a major issue to me. I followed the wiki guide to a T, so its not like it could have been install issue. I reverted to Virtuous 2.2 for the time being, so I find it hard to believe my SD card is damaged, especially since Virtuous doesn't come up with the error.
Any thoughts or ideas that could fix this? Anyone experience similar issues? Thanks in advance.
You should be using the CM6 kernel only. I'd guess that's the source of your woes.
Sent from my Incredible using XDA App
@rmaccr
Only use the kernal that comes with the rom. CM6 is very picky when it comes to custom kernals. I tried to flash hydra and kingx kernals and no go. Just use the original kernal and u should be good.
Sent from my Incredible using XDA App
Make sure you're wiping data/factory reset and wiping the cache partition in Recovery before you install a different ROM.
There's also an alternate kernal you can flash if the stock CM6 kernel is giving you problems - search the RC3 thread to find it.
Thank you for all of your feedback. I'll have to do some thread searching to find that kernel. I assumed that may be the issue.
rmaccamr said:
Thank you for all of your feedback. I'll have to do some thread searching to find that kernel. I assumed that may be the issue.
Click to expand...
Click to collapse
Just reflash the rom and it will include the kernel. Just make sure you have set cpu or some other app to underclock your processor if need be. It's clocked at 1.15 and that gives my phone a bootlooping and crashing party.
Sent from my Incredible using Tapatalk.
rmaccamr said:
I'm aware of the issues associated with CM6 RC3, but when I installed 6.0.1 today, I booted, the touchscreen was non-responsive, but the scroll wheel allowed me to reboot.
Initially, I forgot to install the stock htc kernel over the hydrakernel I had for Sense (#2), so I put that on. When I rebooted, my screen was responsive, but I noticed a lot of page tearing, and my "SD Card is damaged. May require a format" or some such nonsense.
I'd like to try CyanogenMod but thats a major issue to me. I followed the wiki guide to a T, so its not like it could have been install issue. I reverted to Virtuous 2.2 for the time being, so I find it hard to believe my SD card is damaged, especially since Virtuous doesn't come up with the error.
Any thoughts or ideas that could fix this? Anyone experience similar issues? Thanks in advance.
Click to expand...
Click to collapse
Its not the SDCard that requires formatting. It is the internal phone storage. If you view it via Astro, it should appear ok.
whewstoosae said:
Just reflash the rom and it will include the kernel. Just make sure you have set cpu or some other app to underclock your processor if need be. It's clocked at 1.15 and that gives my phone a bootlooping and crashing party.
Sent from my Incredible using Tapatalk.
Click to expand...
Click to collapse
I thought 6.01 was clocked to normal speed and if you wanted the overclocking you just get 6.0 instead.
bippy_b said:
I thought 6.01 was clocked to normal speed and if you wanted the overclocking you just get 6.0 instead.
Click to expand...
Click to collapse
I think that 6.0.1 is defaulted to 1GHz, but you can o/c it if you want to with SetCPU or similar.
The kernel that comes with cm6.0.1 is already great. i get the best battery life i have ever had on my incredible. It can be overclocked to 1.15ghz
When I downloaded it defaulted to 1.15 so I guess YMMV.
Sent from my Incredible using Tapatalk.
rmaccamr said:
Thank you for all of your feedback. I'll have to do some thread searching to find that kernel. I assumed that may be the issue.
Click to expand...
Click to collapse
Slow down and read everything over a bit better.
Hydra and King usually state somewhere SPECIFICALLY that they DON'T work with/support CM6. You don't need to find any kernel, just WIPE your device properly ( wipe data/cache/dalvik) before you flash it. Once flashed don't try any kernels.
Also understand there are known issues with it. One is that BT music streaming doesn't work at all. The other is that the OS doesn't scan the built in 8gb of memory. The third one is that you may experience a random reboot or suddenly get a black screen and unresponsive phone when using wifi. It may happen in 30 minutes, it may take 12 hours. It may not happen at all. It's not even close perfect yet.
The only issue I have seen so far is random reboots and yesterday when I booted up my Phone all my widgets were brown boxes and said they were not compatible, a reboot fixed that.
Android Version 2.2
Model Number - Incredible
Baseband - 2.15.00.07.28
Kernel Version - 2.6.32.15......koush
Mod Version Cyanogen 6.0.1
When you mount your phone via usb mass storage it is mounting more than just the /sdcard/ and /emmc/(internal storage)
It is mounting /data/ and /system
If you're running Windows it will ask you to format these partition's b/c it cannot read them. Do not format them because you will then have issues mounting those partitions and you would have to RUU/PB31IMG.zip
I have already seen this happen to more than two people.
AndroidBruce said:
When you mount your phone via usb mass storage it is mounting more than just the /sdcard/ and /emmc/(internal storage)
It is mounting /data/ and /system
If you're running Windows it will ask you to format these partition's b/c it cannot read them. Do not format them because you will then have issues mounting those partitions and you would have to RUU/PB31IMG.zip
I have already seen this happen to more than two people.
Click to expand...
Click to collapse
Thanks for the pro-tip, I could see myself having done this.
I've had multiple lock ups and reboots but the first day was good.
Sent from my Incredible using XDA App
seanmcd72 said:
third one is that you may experience a random reboot or suddenly get a black screen and unresponsive phone when using wifi.
Click to expand...
Click to collapse
Gah, that's still happening with 6.0.1? I was hoping that would be fixed since the official source drop from HTC.
I'd really like to give an AOSP ROM a good run on my Inc, but that's a deal killer for me.
Thanks for the heads up though.
ardax said:
Gah, that's still happening with 6.0.1? I was hoping that would be fixed since the official source drop from HTC.
I'd really like to give an AOSP ROM a good run on my Inc, but that's a deal killer for me.
Thanks for the heads up though.
Click to expand...
Click to collapse
I have had NO reboots at all since putting 6.0.1 on 2 days ago - and I connect to Wifi at least 50% of the time. Today, I moved toward overclocking, but for the past 2 days I have been running stock speed
ncwildcat said:
I have had NO reboots at all since putting 6.0.1 on 2 days ago - and I connect to Wifi at least 50% of the time. Today, I moved toward overclocking, but for the past 2 days I have been running stock speed
Click to expand...
Click to collapse
I was also fine for over a day. Then today I have had to lockups, where the screen was black and only a bat pull fixed it plus one random reboot.
jratzo said:
I was also fine for over a day. Then today I have had to lockups, where the screen was black and only a bat pull fixed it plus one random reboot.
Click to expand...
Click to collapse
Exactly what I experienced. I went half a day with it seeming perfect, then out of the blue I pick up the phone and it's just off and nothing I do will get it to come on. It's either pull the battery or wait several minutes and suddenly it finally reboots on it's own. It doesn't happen to everyone, but it happens to enough people to say it is a definite unresolved issue. It's very good otherwise, as soon as these little issues are cleared up It will be the ROM for me.

MODS PLEASE CLOSE THREAD --- new kernel by scooter fixed YAFFS error

Mods please close these thread
clemsyn said:
OK, this is from l1q1d latest 2.6.32 (10-29) and merged with dream kernel by ezterry. I used HTC Android kitchen by dsixda and with help from scooter, got me an nbh from a zimage file.
I installed my ROM with this kernel and then installed iGO, ran some GPS and wifi, restarted about 30 times (clean shutdown) and yaffs stayed intact. Reset the device 5 times after each reboot..First, second, third reset was good...Fourth reset gave me a Google Framework error..Fifth reset gave me yaffs error....Anyone interested can try it and let me know how it works in your Kaiser. BTW, edit the Kaisimg.nbh depending on your device.
I recommend acayoeme or scooters ROM.
Click to expand...
Click to collapse
Thanks for the recommendation, I will give the kernel a try with my build to personally test it and see if I can figure out a way to keep it stable enough.
aceoyame said:
Thanks for the recommendation, I will give the kernel a try with my build to personally test it and see if I can figure out a way to keep it stable enough.
Click to expand...
Click to collapse
Ur welcome, thanks for trying out my kernel My friend is currently testing out this kernel with my ROM but since your ROMs are optimized for 2.6.32, I think it's best that this kernel be tested with your roms
Yeah I just downloaded it and just copied it to the phone, will let you know how it goes.
NAND did not work with the nbh for me. SD worked though, going to test further. With NAND it just hung at the android part of the nbh and in the install menu it did not detect the NAND in it. I have a TILT with display type 2 if that narrows down perhaps a difference in the NAND that there could be.
aceoyame said:
NAND did not work with the nbh for me. SD worked though, going to test further. With NAND it just hung at the android part of the nbh and in the install menu it did not detect the NAND in it. I have a TILT with display type 2 if that narrows down perhaps a difference in the NAND that there could be.
Click to expand...
Click to collapse
I'm pretty sure he had a type 2 Tilt too. I'll ask him.
Yes, he does have a Tilt type 2
Hmm thats odd, also I noticed it seems like I can't overclock to 570 mhz with the kernel so far, seems like its a little less tolerable to cpu instabilities. Other than that though all features seem to be working and 6+ reboots later with both on SD I haven't seen any corruption yet.
aceoyame said:
Hmm thats odd, also I noticed it seems like I can't overclock to 570 mhz with the kernel so far, seems like its a little less tolerable to cpu instabilities. Other than that though all features seem to be working and 6+ reboots later with both on SD I haven't seen any corruption yet.
Click to expand...
Click to collapse
It was pretty snappy at 400 mhz...so we never did overclock and kept it at default speed. Just wondering why it won't install nand for you while we did not have any issues in his tilt.
Has anyone on a vogue or kaiser or anything else tried this yet?
I just tried NAND again and the error is a umount error, it seems like it tries to format with the wrong parameters, it gives an invalid argument error.
err seems like it is trying to unmount properly so it cant format it.
Looked a little closer at the error and it is actually saying it cannot find a flash device and that is why the sub sequent umounts are failing.
OK, got a hold of my friends Tilt...I am currently installing your Build..I'll post the dmesg and boot messages...somehow it installs with no issues on this Tilt both system and data on NAND. Currently on bootanimation.
OK booted fine...here are the files
BTW, very nice build Very fast..cant find the reason to overclock with this combo in NAND
I can't possibly think of why it isn't finding the NAND on mine. I am going to try reloading winmo and then re-loading the nbh fresh tomorrow. Thank you for the compliments, I overclock mine so high just because I have a hunger for speed, trying to make it as fast as I can, to compete with the dream and be faster even if possible.
Works fine with NAND. No problem detected yet.
Clean installation on NAND/NAND seems to install and boot just fine on a tilt screen 2
Grandelama said:
Clean installation on NAND/NAND seems to install and boot just fine on a tilt screen 2
Click to expand...
Click to collapse
Thanks for trying it...LMK how it goes for you eg. stability, adb, SD removal and insertion while running etc..
I will just install it and see how it goes. Looks good
Installed, and so far so good using scooters cyanomod. Did a boot-reboot-boot-reboot-boot-reboot stress test, and so far no yaffs errors, and no data corruption. This is using a tilt with panel 3. I'll run it for a few days and keep you posted.
matcha20 said:
Installed, and so far so good using scooters cyanomod. Did a boot-reboot-boot-reboot-boot-reboot stress test, and so far no yaffs errors, and no data corruption. This is using a tilt with panel 3. I'll run it for a few days and keep you posted.
Click to expand...
Click to collapse
I appreciate you guys trying it...I suggest you no overclocking since it is very sensitive to overclocks
I have tried this kernel today with "Scoot CyanogenMod RLS4" and "Galaxy S for AndroidonHTC 11/1" which is based on Fresh Froyo. After the setup with both builds I installed a few apps and then I made an normal reboot (switch off, switch on again). Then I got the same error with both builds:
init: untracked pid xxx
And then the phone is in a loop and does not boot. Seems, that there are yaffs errors with this kernel after the reboot?
So I think this error belongs to the kernel and not the build because these are both different builds. My installation was system and data on nand and not overclocked. Maybe someone can help?

Clemsyn's BEST FROYO w/ REBOOT PROTECTION (BETA3) ENG/SPanish ONLY 12-3-2010

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!

Kernel for beta tester (2.6.32)

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

[ROM][WIP][4.4.2] CyanogenMod 11 KitKat for Optimus S/V

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.

Categories

Resources