Related
Made a new thread for the update.zip versions of the LagFix since i have had people asking me to do that so it doesn't get cluttered up together with RyanZA's fix in his thread.
Only one file included... Will overwrite old root version.
Testet on firmware: (Did a fresh reflash every time)
I9000:
I9000XWJG5 (Eclair - Europe)
I9000XWJM1 (Eclair - Europe)
I9000XWJM5 (Eclair - Europe) (Thanks Peaster111)
I9000XXJP2 (Froyo - Europe)
I9000JPJG8 (Eclair - Africa)
Captivate: (Thanks to Zilch25 for testing)
I897UCJH2
I897UCJH3
Instructions:
(Note that i recommend that you do a fresh reflash through ODIN.)
1. Download the update.zip of your choice and rename it to update.zip.
2. Place it on your internal sdcard.
3. Turn off your phone.
4. Hold down Vol Up+Power button+Home Button for a couple of seconds until u see the galaxy logo .
5. Use the up and down buttons to get to update.zip.
6. Press menu button on update.zip to select it.
7. After install, the phone restarts.
8. Go to the newly installed 'SL4A' application from the app list, open it and choose either LagFix_Ext2.sh or LagFix_Ext4.sh to install the fix.
9. The script should run takes around 2-4 mins before it reboots.
10. First reboot after applying script will take some time as it's moving data around and mounting folders.
Regarding Step 4: What is written is for GT-I9000 version.
For Captivate and Vibrant as other people with that phone.
For Captivate people that are trying this on I897UCFJ6 please read the following post: http://forum.xda-developers.com/showpost.php?p=7939738&postcount=177
Notes:
The current version works on Froyo BUT you can only use the ext2 option as the current kernels in Froyo doesn't support ext4.
Known Bugs:
Got no idea if people still will have problems with changing fonts with ext2 since it works for me.
Credits:
RyanZA - Original bat fix
husq510 - Supplied files needed to enable ext4 support
Zilch25 - For being my test subject on the Captivate board
Donations:
Had a few people ask for donation link so here it's: Donate
Do note though that you don't have to donate if you don't want to.
Changelog:
v.2.3.3
Minor bug fixes.
Put all into one file that will remove old root and reapply new root in the same zip file.
v2.3.2
Removed custom hosts file for ads blocking as that was the problem with SL4A crashing.
v.2.3.1
Changed version of SL4A which should fix the FC that SL4A is giving.
v2.3.0
Scripts redone to do all moving of data on boot to minimize chance of loosing applications and settings.
Firmware check added to scripts to check if your firmware needs GPS Logging fixed.
Removed support for Ext3 as there is no reason to have it since we can use ext4
Added custom apn-conf.xml file for APN settings.
Added hosts file for blocking ads.
v2.2.2
This fix is for Captivates running firmware I897UCJH2
Turns off GPS logging and removes whatever logs that might already have been made
v2.2.1
Fixed old bug with /data/app-private
Added checks to scripts so they check if your system has support for the filesystem you choose
v2.2
Added Check_Space.sh to sl4a
Added support for ext4 (Only works on eclair builds)
Busybox 1.17.1 is NOT required anymore, but is the version i'm including.
v2.1
Based on RyanZA's v2.3
Added support for ext3 (Only works on eclair builds)
Removed support for /dbdata/databases
Changed /data/app-private from mount to symlink
Added two versions of the zip's. One for people who already have a rooted SGS and one that will root the SGS.
v2.0
Based on RyanZA's v2.0
Initial release.
Added support for /dbdata/databases
Added support for /data/app-private
Hey, would you like me to test this on JP3??
Thread
is it possible to undo this lag fix? what scores in quadrant are we expecting with this?
All lag is gone with this or is there some left as I encounter in ryan's? tnks in advance for the hard work
Hi
Great tool
if i'll replace files in the zip will it still work?
(like replacing busybox with version 1.18 and replacing apn-conf with one who has Israeli carriers or adding fonts library for hebrew fonts)
Thread Astaire said:
Hey, would you like me to test this on JP3??
Thread
Click to expand...
Click to collapse
You are welcome to test it on JP3 if you want to but just remember Clockworkmod Recovery can have problems with applying the update.zip's
rbanaco said:
is it possible to undo this lag fix? what scores in quadrant are we expecting with this?
All lag is gone with this or is there some left as I encounter in ryan's? tnks in advance for the hard work
Click to expand...
Click to collapse
There is a script included to remove the lagfix. From test with stock kernel quadrant score is excepted to be around 2100-2200 with ext2 and 1800-1900 with ext4.
From all the testing we have been doing on this release when fixing bugs there haven't really been that much lag... you might see small lag when opening an application for the first time or when installing an app since we are using a different method this time where we don't move the application's apk's after it's installed, but personally i haven't seen this yet.
omrij said:
Hi
Great tool
if i'll replace files in the zip will it still work?
(like replacing busybox with version 1.18 and replacing apn-conf with one who has Israeli carriers or adding fonts library for hebrew fonts)
Click to expand...
Click to collapse
Hmm no idea tbh... You might be able to open the zip, replace the files and close it again without losing the signature that it's signed with, but this is something that i haven't tried yet so don't know if it will work.
thanks for the answer.. one more question if you don't mind answering.. what would you advise ext2 or ext4? which provide better performance despite of the score? thank you
rbanaco said:
thanks for the answer.. one more question if you don't mind answering.. what would you advise ext2 or ext4? which provide better performance despite of the score? thank you
Click to expand...
Click to collapse
I would recommend ext4 since it have journaling, which means there is a smaller chance on losing data if your phone lose power by pulling the battery or if the battery reach 0%.
Other people would say ext2 since ext4 might reduce the lifetime on the NAND since it has journaling
I have only tested the ext4 myself pretty much while i have had others to test both ext2 and ext4. Also this is what Zilch25 has posted about ext2 and ext4 on the captivate forum:
Is EXT2 for me?
If you want your Quadrant scores to be bloated beyond belief and don't care if your data spontaneously combusts (Results may vary). Alternatively if you're worried about your NAND wear leveling not being able to handle the strain of EXT4 journaling.
Okay EXT2 is scary, how about EXT4?
You can't afford for your things to get corrupted? Weirdo. Real world performance between EXT4 and EXT2 is barely noticeable if at all, for the everyman this is probably your best bet.
Click to expand...
Click to collapse
omrij said:
Hi
Great tool
if i'll replace files in the zip will it still work?
(like replacing busybox with version 1.18 and replacing apn-conf with one who has Israeli carriers or adding fonts library for hebrew fonts)
Click to expand...
Click to collapse
i think u can replace or delete files as u like.
i replaced, delted or added files every time before i flashed a new ROM, like HACKECLAIR or SamSet.
Works well.
applying ext4 gives me the stopped unexpectedly google error
Yeah I can second that... after a full wipe SL4A is giving me FC's now too =P
Just wanted to add:
EXT2 may be less safe than EXT4, but to-date, there has been no reports of any corrupt or lost data using the EXT2 fixes. This is over a pretty huge sample over a fairly long period. Not to say there are no problems with EXT2, but there has not been any impact to anyone for using EXT2 as yet.
Other than that, awesome job Tayu! Looks great!
yep, i get the force close for either script from sla4
OK ill reupload with the old version of sl4a then.
Im still not sure wether i should go for Ryan's one-click .apk fix or this one.
Anyone tested this one on I9000XXJM2? wich is stock firmware for me.
Tayutama said:
OK ill reupload with the old version of sl4a then.
Click to expand...
Click to collapse
v2.3.1 uploaded which replaces sl4a_r1 with sl4a_r0 which was the one used in the older versions of the fix. Should fix the problem with getting force close
Tayutama said:
v2.3.1 uploaded which replaces sl4a_r1 with sl4a_r0 which was the one used in the older versions of the fix. Should fix the problem with getting force close
Click to expand...
Click to collapse
Applying it now, I'll let ya know how it goes
do i need to remove the previous sl4a?
A.VOID said:
do i need to remove the previous sl4a?
Click to expand...
Click to collapse
would be the best as they each got a different name.
If you got root explorer you can remove it from /system/app
It's called: sl4a_r1.apk
Tayutama said:
would be the best as they each got a different name.
If you got root explorer you can remove it from /system/app
It's called: sl4a_r1.apk
Click to expand...
Click to collapse
Yeah you might need to... I just reapplied without removing it and only r1 shows up =P
Please read this entire post!
<<<This is a link to the... FAQ Click it!!>>>
I have created a complete bundle of GingerBread with the newest kernel from GIT (Feb 28 / 1276), and the newest rootfs from GIT (Feb 24).
Please, feel free to DONATE to the XDAndroid project!
Every little bit helps!
Directions:
1. Download the full bundle (zip). (Updated Mar. 11 2011)
If instead you just want the system.ext2 (zip) file (updated Mar. 25 2011) by itself... Don't download this unless you know you want to update!!
2. Extract it. You’ll see a folder, GBX0A, copy its contents to the root (base) of your SD card. If you want to run Android from a folder instead of all the files on the root of the card, follow the steps below.
3. Go into the STARTUPS folder. Grab the appropriate startup.txt for your device (if you don't know what device you have, you should read the FAQ), and move it to the root of the card (or where you run haret.exe from. If you want to change the location of the build, put a rel_path= statement in the cmdline section of the startup.txt. Mine is located two folders deep on the SD, so my rel_path=Androids/TP2Ref)
4. Download the ts-calibration file from this post (should work for RAPH/DIAM) and extract the .zip to where you run haret.exe from - typically the root or 'base' folder of the SD card. Not within any folders, unless you run haret.exe from a folder!
**If you have issues with the above file, you must calibrate manually. To start manual calibration, just delete any ts-calibration files and boot. Sometimes this doesn't work, and you have to use an older kernel from GIT (I found 1225 works well) and generate the ts-calibration file by booting and pressing the 5 zones. Once you have a good calibration file hold on to it (make 15 copies if it's a really good one ), reboot & go back to the newest kernel from the autobuild service! Thanks**
6. Run haret.exe... Profit!
Let it settle out on the first boot. Many have reported they had to reboot basically because it was so slow - if you let it sit for about 10 mins or so the media scanner can go thru everything, etc. If you want adb in and watch the processes via top, you'll see why the phone seems so slow - there's lots of background processes cranking because this is the first boot .
Troubleshooting:
Please read the... FAQ
If you have any issues with the kernel, feel free to change it:
There are some devices that are having issues with the newest kernels. Please see the kernel autobuild service to get newer or archived kernels. Once you download a replacement kernel, go to where you run haret.exe from - remove your old zImage/modules-xxxxx.tar.gz. Take the new zImage/modules-xxxxx.tar.gz and replace the old ones, same folder - where you run haret.exe from. Make sure the ‘zImage’ is named just that. Do not rename the modules file, do not extract it - should be in .tar.gz format.
In addition, I am using the newest rootfs from GIT - Feb. 10. There are other rootfs options, see F22’s thread if you want to use more keys or move around the home button. Of course, there's always the roofs autobuild service if you want "stock" rootfs images - F22 builds his off of these and modifies them .
See Incremental Updates for more information on this topic of updating!!
Random issues can often be solved by forcing the system to create a new data.img. If you're worried about losing data, Titanium Backup works quite well. If you wish, you can rename the data.img to something else, and let the system create a new one - just to see if it resolves your problem.
Similarly, if you wish try formatting your SD card - I prefer to use the HP Tool - do a full format, FAT32.
Obviously this build is Alpha, and there are going to be problems. The next post will address issues particular to this build - PLEASE READ THESE before asking questions! Feel free to post questions in this thread, I will do my best to address them. Big thanks to stinebd for releasing the system image, and of course the other developers for their hard work on making these kernels available.
stinebd's original post HERE
Mar. 11 2011 Changelog
Things broken in this build:
libgps - explains itself, no GPS and probably no netloc (cell-tower based location)
HW3D is either not working, or just not preset - I ran neocore and let's just say a lot of textures are missing. Got a ridiculous score, but again - no textures, not much to render haha.
DIAM users have reported the g-sensor is flipped -
emc02 said:
ok, the solution for DIAM100 is:
change "gsensor_axis=2,-1,3" to "gsensor_axis=-2,1,3"
works perfect!
Click to expand...
Click to collapse
This line should be in the startup.txt file if that wasn't obvious .
Thanks to emc02 for that solution!
The keyboard should be fine, but I've had some Blackstone users complain - if you want, switch the keyboard out with another. mr_grisha's original post.
Anything that's broken in Froyo, is probably broken in this build.
Changelog March 25, 2011
Further tuned keyboard sizing to be useful on VGA (also made the key labels bigger)
World-phone settings support (very important for future RIL enhancements especially on CDMA)
Enabled HSPA icon (someone on GSM please let me know if it actually works)
Strange, I never saw the calib. screen. Probably because I just replaced the system.ext2 file and let it run it's course? I do recall there being calib. "issues" with 1253 because the text would continue to scroll even while you were attempting to tap the points.
[R^7Z EDIT]I don't suppose that would work if you were re-working this from the beginning or starting over from scratch (doh!). Lucky me, I save just about every new/update regardless of kernel package or rootfs update[/R^7Z EDIT]
R^7Z said:
Strange, I never saw the calib. screen. Probably because I just replaced the system.ext2 file and let it run it's course? I do recall there being calib. "issues" with 1253 because the text would continue to scroll even while you were attempting to tap the points.
Click to expand...
Click to collapse
If you already have a ts-calibration file, there's no need to create a new one .
A note to all troubled users
And additionally, to those who are reporting issues, it would behoove you to help the devs out by not making them guess what you are using (device) to include but not limited to, which rootfs and kernel package (date of release and commit ID might be helpful). That being said, be aware of what you are talking about (app discussion should not fall into this thread) and please keep talks of neopeek variants to a minimum (I know a little bit about these builds and will help out where I can, PM me if you really think I can help and if you really need some assistance)
arrrghhh said:
[CUT]
HW3D is either not working, or just not preset - I ran neocore and let's just say a lot of textures are missing. Got a ridiculous score, but again - no textures, not much to render haha.
I noticed the (virtual) keyboard is comically tiny. Seems to work fine tho...
[CUT]
Click to expand...
Click to collapse
Noticed the same thing in neocore (30fps without textures) but quadrant 3D tests looked good. Probably we need to test more apps.
Virtual keyboard is unusable on Blackstone. All buttons are tiny and kind of stacked together at the bottom of the screen.
BTW. I can't calibrate the screen since .35 FB commit (17 Dec). I think it's because of FB debug spam - this should be easy to fix.
on ralph100 i've been stuck on "busy" loop for about 20mins now.
loops saying "INFO task rpcrouter: 15 blocked out for more than 120 seconds"
thebranded said:
on ralph100 i've been stuck on "busy" loop for about 20mins now.
loops saying "INFO task rpcrouter: 15 blocked out for more than 120 seconds"
Click to expand...
Click to collapse
Hrm. I'm going to go with format your SD card using the HP Tool. Full format, FAT32.
Also, might want to try kernel 1258. Let me know if neither of those things improve it. Is it creating a data.img...?
g3rm0 said:
Noticed the same thing in neocore (30fps without textures) but quadrant 3D tests looked good. Probably we need to test more apps.
Virtual keyboard is unusable on Blackstone. All buttons are tiny and kind of stacked together at the bottom of the screen.
BTW. I can't calibrate the screen since .35 FB commit (17 Dec). I think it's because of FB debug spam - this should be easy to fix.
Click to expand...
Click to collapse
Sorry forgot to respond to this. Two things, there's an app called "gingberbread keyboard". Find it on the market, see if it works better for you.
Second, I've heard the new 1258 kernel is fixed - not sure how, but it seems the clocks commit from jb's tree did it.
works with 1258, did reformat SD card.
Still had issue with not seeing the touchscreen calibration though, just copied over a old TS file.
thebranded said:
works with 1258, did reformat SD card.
Still had issue with not seeing the touchscreen calibration though, just copied over a old TS file.
Click to expand...
Click to collapse
Glad it's working for you. I think we've narrowed down the calib issue, so hopefully we'll get that fixed for all devices soon. Not sure why but RHOD's don't seem to have the issue any longer - no matter, we will get it resolved for all devices. Sometimes just takes longer for the old devices unfortunately...
[xda Link] Gingerbread keyboard
For those of you who need it, check THIS thread out!
n-Joie! (Enjoy)
R^7Z said:
For those of you who need it, check THIS thread out!
n-Joie! (Enjoy)
Click to expand...
Click to collapse
I've heard it doesn't work... Per another user, I have added a different recommendation:
arrrghhh said:
I noticed the (virtual) keyboard is comically tiny. Seems to work fine tho... If it does bother you, user "webxplore" said the app "gingerbread keyboard" (on the Market) fixes the issue. Thanks webxplore!
Click to expand...
Click to collapse
Gingerbread keyboard (market version)
Will see about getting the market version upped for those who are not able to access a wifi or have the awesome pull-out keyboard the RAPH/TP has
[R^7Z EDIT]Keep in mind, I have a RAPH110/TP/at&t Fuze
Free for all!
n-Joie! (Enjoy)
[/R^7Z EDIT]
Please note, we now have a source fix for the keyboard size and it will be integrated in the next testing image.
Not sure why WiFi works better in GB than FroYo but I just disabled and re-enabled like several times, without fail/error. I'm using the packaged build found in this thread and using Glemsom's kernel package for the 14th. If needed, I can supply screenshots.
R^7Z said:
Not sure why WiFi works better in GB than FroYo but I just disabled and re-enabled like several times, without fail/error. I'm using the packaged build found in this thread and using Glemsom's kernel package for the 14th. If needed, I can supply screenshots.
Click to expand...
Click to collapse
No need. I'll let stinebd know, I'm not sure what the difference would be... if he can backport something to Froyo, or if we are just going to be moving forward and focusing on GB. Thanks again for testing!
Thanks alot man this build is great! seems to boot and run faster and smoother then froyo ever did for me...only issues i ran into were not being able to see the calibration which if youtap on the screen it glitches and shows part of it.....but the main thing is i seem to have a problem staying connected to the internet and have to soft reset to get it working again....also airplane mode seems to get stuck once clicked and only a soft reset fixes it
m using this one is there anyway to chnge keyboard cx buttons are to small and my phone doesnot rotate any help
xtremists said:
m using this one is there anyway to chnge keyboard cx buttons are to small and my phone doesnot rotate any help
Click to expand...
Click to collapse
Read the second post. Gsensor doesn't work yet, but there's a fix in the pipeline. Keyboard fix as well, in the meantime... read the second post!!!!
Please read this entire post!
<<<This is a link to the... FAQ Click it!!>>>
I have created a complete bundle of GingerBread with the newest kernel from GIT (Feb 28 / 1276), and the newest rootfs from GIT (Feb 24).
Please, feel free to DONATE to the XDAndroid project!
Every little bit helps!
Directions:
1. Download the full bundle (zip). (Updated Mar. 11 2011)
If instead you just want the system.ext2 (zip) file (updated Mar. 25 2011) by itself... Don't download this unless you know you want to update!!
2. Extract it. You’ll see a folder, GBX0A, copy its contents to the root (base) of your SD card. If you want to run Android from a folder instead of all the files on the root of the card, follow the steps below.
3. Go into the STARTUPS folder. Grab the appropriate startup.txt for your device (if you don't know what device you have, you should read the FAQ), and move it to the root of the card (or where you run haret.exe from. If you want to change the location of the build, put a rel_path= statement in the cmdline section of the startup.txt. Mine is located two folders deep on the SD, so my rel_path=Androids/TP2Ref)
4. Download the ts-calibration file from this post (should work for RHOD/TOPA) and extract the .zip to where you run haret.exe from - typically the root or 'base' folder of the SD card. Not within any folders, unless you run haret.exe from a folder!
**If you have issues with the above file, you must calibrate manually. To start manual calibration, just delete any ts-calibration files and boot. Sometimes this doesn't work, and you have to use an older kernel from GIT (I found 1225 works well) and generate the ts-calibration file by booting and pressing the 5 zones. Once you have a good calibration file hold on to it (make 15 copies if it's a really good one ), reboot & go back to the newest kernel from the autobuild service! Thanks**
6. Run haret.exe... Profit!
Let it settle out on the first boot. Many have reported they had to reboot basically because it was so slow - if you let it sit for about 10 mins or so the media scanner can go thru everything, etc. If you want adb in and watch the processes via top, you'll see why the phone seems so slow - there's lots of background processes cranking because this is the first boot .
Troubleshooting:
Please read the... FAQ
If you have any issues with the kernel, feel free to change it:
There are some devices that are having issues with the newest kernels. Please see the kernel autobuild service to get newer or archived kernels. Once you download a replacement kernel, go to where you run haret.exe from - remove your old zImage/modules-xxxxx.tar.gz. Take the new zImage/modules-xxxxx.tar.gz and replace the old ones, same folder - where you run haret.exe from. Make sure the ‘zImage’ is named just that. Do not rename the modules file, do not extract it - should be in .tar.gz format.
In addition, I am using the newest rootfs from GIT - Feb. 10. There are other rootfs options, see F22’s thread if you want to use more keys or move around the home button. Of course, there's always the roofs autobuild service if you want "stock" rootfs images - F22 builds his off of these and modifies them .
See Incremental Updates for more information on this topic of updating!!
Random issues can often be solved by forcing the system to create a new data.img. If you're worried about losing data, Titanium Backup works quite well. If you wish, you can rename the data.img to something else, and let the system create a new one - just to see if it resolves your problem.
Similarly, if you wish try formatting your SD card - I prefer to use the HP Tool - do a full format, FAT32.
Obviously this build is Alpha, and there are going to be problems. The next post will address issues particular to this build - PLEASE READ THESE before asking questions! Feel free to post questions in this thread, I will do my best to address them. Big thanks to stinebd for releasing the system image, and of course the other developers for their hard work on making these kernels available.
stinebd's original post HERE
Mar. 11 2011 Changelog
Things broken in this build:
libgps - explains itself, no GPS and probably no netloc (cell-tower based location). I think this also breaks the stock browser, I recommend using Dolphin Mini!
HW3D is either not working, or just not preset - I ran neocore and let's just say a lot of textures are missing. Got a ridiculous score, but again - no textures, not much to render haha.
Data - very flaky - CDMA users have data break for them after every phone call, and GSM users seem to have better luck but it's not flawless. Even seen reports of wifi having issues with data not going out to the WAN. There is a bug filed on this issue.
Anything that's broken in Froyo, is probably broken in this build. Although what is interesting, I noticed that in this build I don't have the landscape-on-boot issue that I get with Froyo...
Changelog March 25, 2011
Further tuned keyboard sizing to be useful on VGA (also made the key labels bigger)
World-phone settings support (very important for future RIL enhancements especially on CDMA)
Enabled HSPA icon (someone on GSM please let me know if it actually works)
Works good so far
Been using this for about 3 hours so far. Here's a little review. Upgraded through Stinebd's link in the XDAndroid thread (same as this I guess, but the arggggh's complete package includes all files needed). I deleted the data.img and replaced my system2 file. The first boot set itself up and then rebooted to winmo. The second boot worked. I was able to download Titanium backup from the market and restore my apps that I was using in Froyo. Overall it was working well. The default keyboard is tiny on my screen. My data connection is a little finicky as it was working when I restored my apps, but I could not connect after a while (same thing happened in my Froyo build periodically). As far as speed is good and bad, sometimes it's quick, other times it's quite slow. Overall, it's pretty good considering it was just released to us. Looking forward to future builds.
Edit: I reused my calibration file from Froyo. No issues
Rhod400, 2/10 Zimage and Rootfs from GIT
mmm, I may be blind but I can't see any download link! I'd like to test it and let you know!
anyway I already want to thank you for the hard work!
The system file was posted by stinebd in this thread:
http://forum.xda-developers.com/showthread.php?t=627997&page=1226
Thanks, I've included the original link to stinebd's post in my first post.
Still working out kinks, and stine will probably want me to host it on files.xdandroid.com - sorry for the delay... It will be here soon .
so this is the neopeek build only in an image?
husam666 said:
so this is the neopeek build only in an image?
Click to expand...
Click to collapse
This has nothing to do whatsoever with neopeek. This is AOSP code, modified to work on our phones. The system image work is done entirely by stinebd, and I have made a bundle - Link up!
arrrghhh any idea what the kernel incompatibility comes from? Thats strange...
edit- nvm I reread it a 5th time and understood heh
randomblame said:
arrrghhh any idea what the kernel incompatibility comes from? Thats strange...
Click to expand...
Click to collapse
You mean the calibration issue? Some commit broke it, not sure which one. There's rumors that we can read it from the spl, then we won't need a kernel-based calibration - we'll be able to do it in userland, which is really what we want especially going forward to NAND.
Gonna try this release this weekend
rhod100 does have the same panel problems as on a FRX04 release a guess?
JBS2 said:
Gonna try this release this weekend
rhod100 does have the same panel problems as on a FRX04 release a guess?
Click to expand...
Click to collapse
Panel problems are kernel related, not system image related.
What kernel do you run FRX04 on...? Thanks.
arrrghhh said:
Panel problems are kernel related, not system image related.
What kernel do you run FRX04 on...? Thanks.
Click to expand...
Click to collapse
Most recent from your testing topic.
Panel wakes up very slow normally or after touching the screen or power button multiple times.
JBS2 said:
Most recent from your testing topic.
Panel wakes up very slow normally or after touching the screen or power button multiple times.
Click to expand...
Click to collapse
Ah. Again, that's a testing kernel. Let's keep testing kernel discussion in that thread and build talk about this build in this thread... Thanks...
arrrghhh said:
Ah. Again, that's a testing kernel. Let's keep testing kernel discussion in that thread and build talk about this build in this thread... Thanks...
Click to expand...
Click to collapse
I know, you asked which kernel I was using
Just wondering if these release has something to do with the panel issues but I realize this is a kernel related problem.
Keep up the goog work, I'll keep testing the testing kernels to see if the known problem could be fixed
Okay, here's my 2cents:
BTW, i use rhod100.
Hardware3d doesn't work because the line is missing from the startup (as far as i am concerned, maybe you removed it on purpose).
steyn_e said:
Okay, here's my 2cents:
BTW, i use rhod100.
Hardware3d doesn't work because the line is missing from the startup (as far as i am concerned, maybe you removed it on purpose).
Click to expand...
Click to collapse
That entry is no longer required. Put it in and see... Thanks!
this is such an exciting build. It runs really fast. keep up the good work guys. Btw, to get a bigger gingerbread keyboard, search for "gingerbread Keyboard" in the market. its a larger sized version of the one that comes with the rom.
kdub94 said:
this is such an exciting build. It runs really fast. keep up the good work guys. Btw, to get a bigger gingerbread keyboard, search for "gingerbread Keyboard" in the market. its a larger sized version of the one that comes with the rom.
Click to expand...
Click to collapse
I've already included a fix in the second post, thanks!
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
FAQ
What is apps2ext?
Code:
Apps2ext (previously called apps2SD) moved all user installed apps to a secondary ext partition on your sdcard.
This method had the advantage of being straight forward and simple, However, it had the drawback of being difficult to set up.
This method is no longer officially supported by CyanogenMod.
Please see the forum for device specific work-arounds if you really want apps2EXT on CyanogenMod.
Why did I include a apps2ext script to the rom?
Code:
Even though we have 1GB space of internal memory and a lot of the G2 users believe that is enough.
The more apps that are installed, the slower our phones can get after time.
Apps2ext takes all of that stress from our internal storage and diverts it to our sd-ext partition if there's any.
This results in our phones never have to worry about slowing down just because of the number of apps that we have installed.
What is swap?
Quoted from Cyanogenmod Wiki
Code:
Swap is, in short, virtual RAM. With swap, a small portion of the hard drive is set aside and used like RAM.
The computer will attempt to keep as much information as possible in RAM until the RAM is full.
At that point, the computer will begin moving inactive blocks of memory (called pages) to the hard disk, freeing up RAM for active processes.
If one of the pages on the hard disk needs to be accessed again, it will be moved back into RAM, and a different inactive page in RAM will be moved onto the hard disk ('swapped').
The trade off is disks and SD cards are considerably slower than physical RAM, so when something needs to be swapped, there is a noticeable performance hit.
Unlike traditional swap, Android's Memory Manager kills inactive processes to free up memory.
Android signals to the process, then the process will usually write out a small bit of specific information about its state (for example, Google Maps may write out the map view coordinates; Browser might write the URL of the page being viewed) and then the process exits.
When you next access that application, it is restarted: the application is loaded from storage, and retrieves the state information that it saved when it last closed.
In some applications, this makes it seem as if the application never closed at all.
This is not much different from traditional swap, except that Android apps are specially programed to write out very specific information, making Android's Memory Manager more efficient that swap.
Requirements:
- HTC G2 / HTC Desire Z
- S-OFF
- SDCard
Recommended Requirements:
*Only need this is you plan to use sd-ext and swap*
- Sd-ext partition at least 1024MB
- Swap partition at least 256MB
I DO NOT RECOMMEND USING ANY KIND OF SUPERWIPE
The rom has it's own built in wipe
Installing Process
- Backup your previous rom
- Repartition your sdcard ONLY if you want sd-ext and/or swap enabled
- Download the rom
- Wipe everything (data, cache, dalvik-cache, battery stats)
- Flash the rom
- Once flashing process is complete it will auto reboot!
Working
- Everything should be
Not Working
- Nothing, but tell me if anything is broken
Issues
- None at the moment
REGARDING ISSUES
Post the issues on http://pastebin.com/
- Please give me a logcat if you have an error, I can not help you if there's no logcat of the issue
Credits:
- HTC (Making HTC G2/Desire Z)
- Google (Android OS)
- Cyanogenmod (Source)
- SparksCo (Sd-ext, swap, kernel, cycling bootanimation, symlink scripts and sysctl tweaks)
- SparksCo (Kernel)
- Rambooster script (Credits to Darkky)
- Sdcard increase script (Credits to brainmaster)
If I missed anyone, let me know and I'll add you to here
Download link:
CM7-PyroMod-Stable-V2.3.7
checksums md5: I will provide one later
If you love my roms, donate and hit that thanks button!
Much appreciated!
Great stuff. Congrats on your first ROM! Just i dont think its ok that you have GAAPS installed already. Just a heads up.
Changelog
Version 2.3.7:
Rom
- Compiled from CM Source (Credits to SparksCo)
- Added kernel script (Credits to SparksCo)
- Added sysctl tweaks (Credits to SparksCo)
- Added cycling bootanimation (Credits to SparksCo)
- Working audio (Credits to SparksCo)
Theme
- Stock theme
- Stock font
- Stock audio tones
- Nice FOUR looking bootanimation (Credits to SparksCo)
Kernel
- Custom kernel (Credits to SparksCo)
EDIT: badass dude. Keep it up!
travisd4est said:
Any screenies??
Click to expand...
Click to collapse
Like I said in the OP, it's stock themed for right now
Okay blah I'm downloading and will give a spin this morning. I'll update you on what I think.
Update: This rom is pretty stable. Everything is working perfectly even the wireless tether. No FC's now its time to test the battery life. For just the begin this rom is great. Now its time for some themes! lol
313dash said:
Okay blah I'm downloading and will give a spin this morning. I'll update you on what I think.
Click to expand...
Click to collapse
Thanks, let me know what you think about it
Congrats on your first rom.
siulmagic said:
Congrats on your first rom.
Click to expand...
Click to collapse
Thanks, also thanks for helping me a little
Cause Myjbarr is being a complete douche about me forgetting to asking for his permission to use his rom as a base, he has to remember did he even ask cyanogen to use his rom as a base?
I don't think so
So for everyone, blame him for killing my rom
blahbl4hblah said:
Cause Myjbarr is being a complete douche about me forgetting to asking for his permission to use his rom as a base, he has to remember did he even ask cyanogen to use his rom as a base?
I don't think so
So for everyone, blame him for killing my rom
Click to expand...
Click to collapse
Lol...
Sent from my Desire HD using Tapatalk
blahbl4hblah said:
Cause Myjbarr is being a complete douche about me forgetting to asking for his permission to use his rom as a base, he has to remember did he even ask cyanogen to use his rom as a base?
I don't think so
So for everyone, blame him for killing my rom
Click to expand...
Click to collapse
Why do I always have to take the blame....??? Its never anyone elses fault. Its always my mistake. Shame on me, for not handing over my rom to you so you can call it yours. Also it "mjybarr" and not "myjbarr".
meXdroidMod GingerMex Ghost Chile TEST
mjybarr said:
Why do I always have to take the blame....??? Its never anyone elses fault. Its always my mistake. Shame on me, for not handing over my rom to you so you can call it yours. Also it "mjybarr" and not "myjbarr".
meXdroidMod GingerMex Ghost Chile TEST
Click to expand...
Click to collapse
blahbl4hblah said:
Cause Myjbarr is being a complete douche about me forgetting to asking for his permission to use his rom as a base, he has to remember did he even ask cyanogen to use his rom as a base?
I don't think so
So for everyone, blame him for killing my rom
Click to expand...
Click to collapse
why does it have to be a blame game at all, guys? Seriously, we are all big boys and girls. If someone makes a mistake, they need to own up to it and fix it, not blame anyone else. All that does is cause bad feelings in the community. You guys are both awesome, and I believe we can all get along in peace, and learn from and help one another, to the benefit of the whole community. Sound like a plan, guys?
mjybarr said:
Why do I always have to take the blame....??? Its never anyone elses fault. Its always my mistake. Shame on me, for not handing over my rom to you so you can call it yours. Also it "mjybarr" and not "myjbarr".
meXdroidMod GingerMex Ghost Chile TEST
Click to expand...
Click to collapse
Question... is your rom based off of CM? If it is, why shouldn't he be able to say the same thing you just did... The best way to get great roms is by sharing and expanding. That is why CM is so great, it is a contribution from many people!
Durkbeef said:
Question... is your rom based off of CM? If it is, why shouldn't he be able to say the same thing you just did... The best way to get great roms is by sharing and expanding. That is why CM is so great, it is a contribution from many people!
Click to expand...
Click to collapse
Yeah he's rom is based off of CM, but it doesn't matter anymore actually. I'm already working on a new release based off CM#17, along with the chance of better things
blahbl4hblah said:
Yeah he's rom is based off of CM, but it doesn't matter anymore actually. I'm already working on a new release based off CM#17, along with the chance of better things
Click to expand...
Click to collapse
sounds like a great plan good luck, bro, and cant wait to see where this will go from here. Still keeping the increased vm and apps2sd, I hope?
jmwils3 said:
sounds like a great plan good luck, bro, and cant wait to see where this will go from here. Still keeping the increased vm and apps2sd, I hope?
Click to expand...
Click to collapse
vm yes, but apps2sd of course but different haha
blahbl4hblah said:
vm yes, but apps2sd of course but different haha
Click to expand...
Click to collapse
ok, cool means one less zip to flash for CM, sounds like a definite plus to me.
jmwils3 said:
ok, cool means one less zip to flash for CM, sounds like a definite plus to me.
Click to expand...
Click to collapse
I'll leave it at this, you'll flash ONE thing and that's it
No need to worry about going into terminal for apps2sd
blahbl4hblah said:
I'll leave it at this, you'll flash ONE thing and that's it
No need to worry about going into terminal for apps2sd
Click to expand...
Click to collapse
wow... if that works, thatll be quite the feat indeed. We will still need to go into terminal emulator to move the apps though, i assume?
Remixed Kernel
/only for KitKat/
Remember i am not an developer, this is just my personal builded kernel for my own needs.
Also i am not responsible if your device bricked or else, i give my best and test every build that bad things don't will happen.
If you want to support my work, you can do it here
Changelog remixed.kernel-sr1
- GPU OC up to 512 Mhz
- Fixed OC up to 1,6 Ghz
- Revert few commits for performance reason
DOWNLOAD KERNEL HERE
Sources proper the GPL
Last but not least, my biggest thanks and with them credits goes to:
@Ziyan, @MWisBest, @pattyboi:), @franciscofranco, @boype, @bsmitty83, @osm0sis, @Christopher83 and all other i have forgotten :good:
Reserved for future...
So you decided to share it. Thank you
Nice. Got the sources listed anywhere? I want to create my own personal SuperRAM version. (Plus...that GPL stuff ya know )
redj12 said:
So you decided to share it. Thank you
Click to expand...
Click to collapse
Yes, its ready and as i think good to go but this will show the time.
Culex316 said:
Nice. Got the sources listed anywhere? I want to create my own personal SuperRAM version. (Plus...that GPL stuff ya know )
Click to expand...
Click to collapse
Github can be found in my profil...
I flashed this kernel on omni ROM and it works very well, my phone works smoothly
f2fs support?
It has same features as franco kernel so if francos has it, this also has it
Testing!!! thanks for keeping the scene alive. I'll back with comments.
Edit: not working for me. It doesn't pass boot animation. Vanir ROM with /data and /cache in F2FS.
Wiped cache and dalvik and neither works.
sergialess said:
Testing!!! thanks for keeping the scene alive. I'll back with comments.
Edit: not working for me. It doesn't pass boot animation. Vanir ROM with /data and /cache in F2FS.
Wiped cache and dalvik and neither works.
Click to expand...
Click to collapse
franco doesn't support F2FS because F2FS is bullsh*t.
qtoo941 said:
franco doesn't support F2FS because F2FS is bullsh*t.
Click to expand...
Click to collapse
Strange... I'm pretty sure I've read that it was supporting F2FS. Anyway... I won't argue if F2FS is good or bad. I've been using it since BSmitty featured it first time in the GNex, and I'm satisfied. So... back to my beloved Fancy, which supports F2FS without inconvenience.
qtoo941 said:
franco doesn't support F2FS because F2FS is bullsh*t.
Click to expand...
Click to collapse
how is f2fs bullsh*t.
pattyboi:) said:
how is f2fs bullsh*t.
Click to expand...
Click to collapse
f2fs is just experimental. tried it and actually .. it is not as stable as ext4. the whole story about f2f's performance over ext4's performance is just placebo effect. tried it on galaxy nexus and also on s4.. both models without any real benefit from f2fs system. EXT4 is just better and most stable. that's it.
Don't really know much about f2fs because i never used it...
But if you want it, i can add it into the kernel then you can take your decision what you want use
qtoo941 said:
f2fs is just experimental. tried it and actually .. it is not as stable as ext4. the whole story about f2f's performance over ext4's performance is just placebo effect. tried it on galaxy nexus and also on s4.. both models without any real benefit from f2fs system. EXT4 is just better and most stable. that's it.
Click to expand...
Click to collapse
mind i ask which kernel you tried f2fs with on a gnex? i gain 200+ mbs on writes with f2fs on my gnex on a bad day. && how can you actually prove is just placebo? have you done tests showing it doesn't gain ANY write/read performance compared to ext4?
Guys please... if you wanna have f2fs support hit "THANKS" lets see how many want it.
This shows how many need it and want it, if enought need/want it i will add support in next release
sgspluss said:
Guys please... if you wanna have f2fs support hit "THANKS" lets see how many want it.
This shows how many need it and want it, if enought need/want it i will add support in next release
Click to expand...
Click to collapse
I did it in the OP. If you don't mind, please try to support it as long as you can. Thanks.
Enviado desde mi Galaxy Nexus usando Tapatalk 2
sgspluss said:
Guys please... if you wanna have f2fs support hit "THANKS" lets see how many want it.
This shows how many need it and want it, if enought need/want it i will add support in next release
Click to expand...
Click to collapse
f2fs support was in r398, franco just missed one or two commits for the ramdisk i think so f2fs didn't work....but @osm0sis'es last synapsed version works very well with f2fs on data and cache and system on ext4.
i think he gave permission to use his latest ramdisk
pattyboi:) said:
mind i ask which kernel you tried f2fs with on a gnex? i gain 200+ mbs on writes with f2fs on my gnex on a bad day. && how can you actually prove is just placebo? have you done tests showing it doesn't gain ANY write/read performance compared to ext4?
Click to expand...
Click to collapse
fancy and smitty. yes, it shows upgrade in w/r performance at tests but there is no feeling of anything better compared to ext4. Do you know why PA-Team has never supported f2fs? Totally because it's experiment. The same like ART in KitKat. You can send logs to check some bugs only if its on dalvik runtime, but if you were on art runtime nobody would even check your log. ART became official and fully stable in lollipop... i truly think that f2fs can become more stable but i don't actually know when. At this moment ext4 has nearly the same performance as f2fs but is times more stable. It is not worth spending this stability for such a performance upgrade.
qtoo941 said:
fancy and smitty. yes, it shows upgrade in w/r performance at tests but there is no feeling of anything better compared to ext4. Do you know why PA-Team has never supported f2fs? Totally because it's experiment. The same like ART in KitKat. You can send logs to check some bugs only if its on dalvik runtime, but if you were on art runtime nobody would even check your log. ART became official and fully stable in lollipop... i truly think that f2fs can become more stable but i don't actually know when. At this moment ext4 has nearly the same performance as f2fs but is times more stable. It is not worth spending this stability for such a performance upgrade.
Click to expand...
Click to collapse
I find F2FS absolutely stable, and I don't know in what manner it could compromise stability.
ART is working amazingly well in my Moto G, so I don't agree when you saying it's an experiment in KitKat. The fact that ART is choking for our GNex, doesn't mean it's an experiment. Are you a Google engineer to say that ART is fully stable in lollipop?. I think it never won't work smooth in our devices.
You defend EXT4. I defend Dalvik