Just flashed Axura 2.2, and it's pretty cool, but got a couple questions.
1.) Is there any way to modify the top status bar? If so, how? I want to see if i'm on 3g or Edge...
2.) OCLF isn't working, it says I have another lag fix installed, but my quadrant score is only 1000
3.) The launcher (i'm using Zeam) seems to be always running in the task killer, is that supposed to be?
Thanks.
I think this needs to be in the QA.
1. doesn't it show the H or the E? if so, H is for 3g then E is edge.
2.don't know about that because i don't use any lag fix and do you really need that in the axura? it's fast even without it.
3. Yes, it's normal.
iynfynity said:
I think this needs to be in the QA.
1. doesn't it show the H or the E? if so, H is for 3g then E is edge.
2.don't know about that because i don't use any lag fix and do you really need that in the axura? it's fast even without it.
3. Yes, it's normal.
Click to expand...
Click to collapse
Is it really fast for you?
My phone has lagged unbearably since I flashed 2.1 and 2.2. My vibrant was sooo much faster when it was running stock 2.1 and the OCLF. I just want it to be fast again while retaining Axura.
Axura is not compatible with OCLF. In fact, if you force install it, you'll softbrick. Install Voodoo instead.
Ar318307 said:
Is it really fast for you?
My phone has lagged unbearably since I flashed 2.1 and 2.2. My vibrant was sooo much faster when it was running stock 2.1 and the OCLF. I just want it to be fast again while retaining Axura.
Click to expand...
Click to collapse
Did you reinstall settings that were in red? If so, you shouldnt have.. I have never had one speed issue nor had a complaint over it.
Ar318307 said:
Is it really fast for you?
My phone has lagged unbearably since I flashed 2.1 and 2.2. My vibrant was sooo much faster when it was running stock 2.1 and the OCLF. I just want it to be fast again while retaining Axura.
Click to expand...
Click to collapse
Then something is really wrong with that. Axura is on of the best roms i've flashed. Try reflashing it.
Master™ said:
Did you reinstall settings that were in red? If so, you shouldnt have.. I have never had one speed issue nor had a complaint over it.
Click to expand...
Click to collapse
Could you be a bit more specific. Which settings that were in read are you talking about?
I love your ROM, but it feels like my old iPhone 3G at times.
Ar318307 said:
Could you be a bit more specific. Which settings that were in read are you talking about?
I love your ROM, but it feels like my old iPhone 3G at times.
Click to expand...
Click to collapse
I think Master means the settings that are red in Titanium Backup. Those should not be restored after a new flash.
Good_Orion said:
I think Master means the settings that are red in Titanium Backup. Those should not be restored after a new flash.
Click to expand...
Click to collapse
Still not quite sure. I flashed Axura 2.2, then went to titanium backup, hit "batch" then hit restore missing apps+system data.
I don't recall any red settings. :-/
If I wanted to reflash Axura 2.2, would it just be as easy as going to Clockwork Mod, and installing it from there?
Ar318307 said:
Still not quite sure. I flashed Axura 2.2, then went to titanium backup, hit "batch" then hit restore missing apps+system data.
I don't recall any red settings. :-/
If I wanted to reflash Axura 2.2, would it just be as easy as going to Clockwork Mod, and installing it from there?
Click to expand...
Click to collapse
Yeah the red settings are the system ones you restored. There are red, green, and white items in the application list in Titanium. The red often cause problems if you restore those from a previous rom. I'd Odin to stock, reflash Axura, and then do restore missing apps and data, instead of apps+system data.
Sent from my SGH-T959 using XDA App
Good_Orion said:
Yeah the red settings are the system ones you restored. There are red, green, and white items in the application list in Titanium. The red often cause problems if you restore those from a previous rom. I'd Odin to stock, reflash Axura, and then do restore missing apps and data, instead of apps+system data.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Ah, got it thank you.
Quick question, I installed the Voodoo lag fix and it got all the way to "Step two" then my phone got stuck on the Vibrant screen for like 20 minutes. Thinking it was bricked I took out the battery to try to Odin it back to life but before I did that I hit volume up+volume down and rebooted it and it flashed back to Axura 2.2 as if nothing had happened.
Now I notice that everything is running fast as hell. I'm wondering if the Voodoo lag fix actually got installed even though I never heard the "process complete" message from that robot girl.
My question is, is there a way to tell if the Voodoo lag fix is actually running on my phone? The speed increase in everything should probably be enough but I'd like to see some kind of official confirmation somehow. Is this possible?
if you want you can flash eugenes super io kernel and that should help a bit with lag, quadrant scores at 1300 but you should note quadrant scores doesnt equal real life performance meaning like on stock your at 800-900 oclf at 2200-2300 your phones not really 2x faster
ikevinnyii said:
if you want you can flash eugenes super io kernel and that should help a bit with lag, quadrant scores at 1300 but you should note quadrant scores doesnt equal real life performance meaning like on stock your at 800-900 oclf at 2200-2300 your phones not really 2x faster
Click to expand...
Click to collapse
Just ran it and I've got a quadrant score of 1370.
Yeah and the kernel also fixes any mounting issues if you had problems with that
ikevinnyii said:
Yeah and the kernel also fixes any mounting issues if you had problems with that
Click to expand...
Click to collapse
Would you happen to know how I can tell if the Voodoo lag fix is running on my phone?
Ar318307 said:
Would you happen to know how I can tell if the Voodoo lag fix is running on my phone?
Click to expand...
Click to collapse
I think there's an adb command you can run to see. Can't remember what it was. Going to see if i can find it.
You could also put the the disable-lagfix file in your voodoo directory and reboot I suppose to see if it disables anything.
Ar318307 said:
Would you happen to know how I can tell if the Voodoo lag fix is running on my phone?
Click to expand...
Click to collapse
download terminal emulator from the market. its free
open and at the money sign type su
then type mount
should get a line like this if voodoo went thru ..
dev/block / yadda yadda " EXT 4 " that is what you are wanting to see
Ok, this is gonna look ugly but here's what it came back with:
export PATH=/data/local/bin:$PATH
$ $sumount
sumount: not found
$ su
# mount
rootfs / rootfs rw,relatime 0 0
proc /proc proc rw,relatime 0 0
sys /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p2 /data ext4 rw,noatime,barrier=0,data=ordered,noauto_da_alloc 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/stl9 /system rfs rw,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p3 /data_tmo rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:9 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:9 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/external_sd/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.casual.puzzle.sheeprun.free-1 vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/com.agilesoftresource-1 vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-2 /mnt/asec/com.rovio.angrybirds-1 vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
#
Sent from my SGH-T959 using XDA App
can you link me to axura 2.2?
i cant find it im on 2.1
is this the link? it says 2.1
http://forum.xda-developers.com/showthread.php?t=821468
nvm found it!
http://www.devsforandroid.com/forum...brant-edition-▼△-devs4android-2-2-12-13-10.2/
Related
This is a quick walkthrough of how to apply my variant of "Mimicans speedfix" using my kernels on the Captivate. The speedfix essentially consists of making an ext3 or ext4 filesystem on an sdcard, and using that as our /data directory. This method is different from the original method in many of the details, but the underlying basis is that the stock /data partition is slow as molasses so we replace it.
This method should be pretty safe. As you will notice we dont copy around stuff and create a symlink mess. We just mount a partition over the current one. Yes we still mount the old one as well, even though it wont be used unless you take your card out. If that happens the phone will mount your old /data (that will probably be very out of date at the time) but itll get you up and running right away.
Right now there are two kernels, these mount the default partition, ext3 or ext4 on the second sdcard partition, the two options are:
Stock clock speed and Overclocked.
The overclocked kernel will clock from 100 to 800 Mhz as stock, then skippinig 1Ghz going to 1.2 Ghz.
Also, before we begin make sure you have this version of Odin. I used Samsung windows drivers that I found here.
You'll also want to read this thread about download mode. here you'll learn that you will have to try real hard to actually brick these phones, and even then it may still boot.
Ofcourse you also want to have root on your captivate.
You'll also need the android sdk.
If you are on Windows or Mac you will need some software to partition and format the sdcard, this live cd will work. You could also just get an ubuntu live cd or similar.
So, now we have the necessary tools and our new kernels and can get started.
Partition the disk:
There were reports from the modaco forums when mimocan first released his fix that ext3/4 partitions larger than 2gb were a problem, so keep your 2nd partition 2gb or smaller.
Use your favorite partitioning sofware to create 2 partitions on your sdcard. the first one will be formated FAT32 (vfat), and the second one ext3 or ext4. Make sure both are 'primary partitions'. You may want to make the second partition have partition type 83 (linux native).
Copy data files to sdcard:
If you are coming from stock, (eg without an existing a2sd /data partition on your sdcard) boot the phone without your formatted card and hotplug it before starting this process.
Using the sdk you need to connect the phone and use 'adb shell' to get a prompt on the phone.
Then follow these steps:
Code:
$
$ su -
# mkdir /sdcard/mnt
# mount -t ext4 /dev/block/mmcblk1p2 /sdcard/mnt
# busybox cp -a /data/* /sdcard/mnt
# umount /sdcard/mnt
# exit
$ exit
Flashing the kernel
1) Disconnect USB cable.
2) Open up odin.
3) Put your phone into download mode.
4) Connect USB cable, wait a second Odin should detect your phone, if not fiddle about with your drivers and reboot windows or something. This can be a real PITA.
5) In Odin load the kernel tarfile as "CSC"
6) Click "Start" in Odin, flashing should only take a few seconds.
You may run into issues here randomly and have a phone with the phone-!-computer image (I did!). Just go read up on the 'download mode' thread linked above it tells you how to proceed.
7) When you have booted your new kernel and /data partition you may have some issues with a few widgets/apps. Reinstalling or waiting/fiddeling with them seems to solve the issue. Maps was slow to open the first time after a new /data partition was mounted for me a few times, but subsequent launches were snappy.
If you want you may donate to my beer fund. It is not necessary but much appreciated
Didn't work for me. I partitioned my external SD card, flashed the speedup2 kernel, then ran the commands you posted, replacing 'ext3' with 'ext4'. My quadrant score is still in the low 900's.
Can you explain exactly what those commands do? The mimocan fix makes a lot more sense to me. Why did you decide to take a different approach?
Thanks for your help and effort!
I get 1716 scores in quadrant, but with real world running tests Touchdown and Dolphin HD browser still lag like holy hell.
I originally had the "method 2" hack (moving apps to the NAND) and that worked wonders, especially with these apps.
Can anyone test these two applications and see if there is lag for you?
Dolphin - try opening a new tab, closing it, and goto a large page and scroll with the volume buttons - it should all be smooth and quick
Touchdown - It should be very quick going between emails, I get a 5+ second delay before showing the email
Also in Quadrant, even though I get 1700 scores, do you guys get stuck at I/O Database writes for a good 3+ minutes?
The captivate speedup kernel link is dead. Can soneone please post a mirror? Thanks
Worked great for me using ext4 partition/kernel. It brought my quadrant to 1817! Thats with a poor little 4gig, class 2 micro sd card. Im also running the i9000 JM2 firmware with Samset 1.6.
Thank you for all your hard work!!!! My phone is now complete (for now lol).
andy2na said:
I get 1716 scores in quadrant, but with real world running tests Touchdown and Dolphin HD browser still lag like holy hell.
I originally had the "method 2" hack (moving apps to the NAND) and that worked wonders, especially with these apps.
Can anyone test these two applications and see if there is lag for you?
Dolphin - try opening a new tab, closing it, and goto a large page and scroll with the volume buttons - it should all be smooth and quick
Touchdown - It should be very quick going between emails, I get a 5+ second delay before showing the email
Also in Quadrant, even though I get 1700 scores, do you guys get stuck at I/O Database writes for a good 3+ minutes?
Click to expand...
Click to collapse
Might be tome for you to pick up a new SD card. I have used both fix's and find this fix to be way better. I get no lag in Dolphin HD.
_Opiate_ said:
Might be tome for you to pick up a new SD card. I have used both fix's and find this fix to be way better. I get no lag in Dolphin HD.
Click to expand...
Click to collapse
Its a brand new Kingston 8gb class 4 card, havent used it before applying this hack
Postal76 said:
Didn't work for me. I partitioned my external SD card, flashed the speedup2 kernel, then ran the commands you posted, replacing 'ext3' with 'ext4'. My quadrant score is still in the low 900's.
Can you explain exactly what those commands do? The mimocan fix makes a lot more sense to me. Why did you decide to take a different approach?
Thanks for your help and effort!
Click to expand...
Click to collapse
All you do is copy the files from your original /data partition onto the root of your ext{3|4} partition on the sdcard. Then that is mounted on reboot ontop of /data so you can use the new data partition from your card.
I feel this is a MUCH cleaner method than the original Mimocan fix, that copis a full copy of data into the root of the device (unnecessary backup since you still have your original /data partition as well), then it mounts your sdcard on /disk and symlinks that to /data.
I just don't see the need for the symlinks and stuff and honestly I thought this was a simpler method, no symlinks or anything.
If you arent seeing any speedups I'm betting something didn't go right, you are probably still running of the old /data partition. Are you sure you are running the speedup2 kernel and not the ext4 only kernel?
spyz88 said:
The captivate speedup kernel link is dead. Can soneone please post a mirror? Thanks
Click to expand...
Click to collapse
It seems to work from here...
_Opiate_ said:
Might be tome for you to pick up a new SD card. I have used both fix's and find this fix to be way better. I get no lag in Dolphin HD.
Click to expand...
Click to collapse
Except the Quadrant scores do you notice any real speed boost?
andy2na said:
.....
Also in Quadrant, even though I get 1700 scores, do you guys get stuck at I/O Database writes for a good 3+ minutes?
Click to expand...
Click to collapse
yeah database I/O takes forever still.
Like I said in the other thread, try to reinstall the apps, Dolphin is very very fast here (thanks for getting me a new browser btw.)
I'm still a complete failure and now i get stuck at the galaxy s boot screen
Nuke, after doing the ext4 only method, I only get quadrant scores of 900.
Am I doing something wrong? I go through all the steps fine and everything seems like it went well but it seems like I'm doing something wrong down the line.
one thing I do notice is that I have A LOT MORE AVAILABLE MEMORY in advanced task killer. I use to only have 100 now I have 180MB.
Is it crucial to have to flash the Speedfix2?
after i put in
busybox cp -a /data/*
nothing happens it just sits there
igm503 said:
after i put in
busybox cp -a /data/*
nothing happens it just sits there
Click to expand...
Click to collapse
that part took like 15 min for me since I have a lot of application and app data
but there is no trailing dot it just repeats what i typed and then leaves a blank space
same thing it just repeats it
igm503 said:
but there is no trailing dot it just repeats what i typed and then leaves a blank space
Click to expand...
Click to collapse
What do you mean by "there is no trailing dot" ? Did you type it in? You need to include the trailing dot in your command; based on what you posted it appears you did not do that.
WOW! Okay... So now I'm getting 1756...
You just have to leave Quadrant on for like 15 minutes sometimes! This is very strange!
Notice the period after the asterisk. In the old forum, someone had a problem with that.
I did this fix last night after countless times of my messing up and figuring out how to partition with my phone still being able to read the card, flash problems with Odin, etc etc. I'm using an 8gb Classic 6 and just got an 1805 in Quadrant, and the phone is incredibly, noticeably faster. Did have some weird app problems when it was first applied, but some reinstalls fixed it. Thanks again Nuka!
Sent from my SAMSUNG-SGH-I897 using XDA App
I installed the bionix 1.5 today (Bionix 1.5 w/JACs OC/UV/VOODOO Kernel). I have not installed any lag fixes before. The install went great, but my quadrant score is still 1300. I do not have the "disable-lagfix" file on my sdcard. The Voodoo directory has but one subdirectory - "logs". I looked through the logs, and it looks like things are happening. The phone is running fine, but I just wonder if the voodoo lag fix is actually doing anything. The mount command does show /dev/block/mmcblk0p4 /data ext4 rw,noatime,nodiratime,barrier=1,data=ordered 0 0
So, is it working???
Cheers!
Skip
MrGibbage said:
I installed the bionix 1.5 today (Bionix 1.5 w/JACs OC/UV/VOODOO Kernel). I have not installed any lag fixes before. The install went great, but my quadrant score is still 1300. I do not have the "disable-lagfix" file on my sdcard. The Voodoo directory has but one subdirectory - "logs". I looked through the logs, and it looks like things are happening. The phone is running fine, but I just wonder if the voodoo lag fix is actually doing anything. The mount command does show /dev/block/mmcblk0p4 /data ext4 rw,noatime,nodiratime,barrier=1,data=ordered 0 0
So, is it working???
Cheers!
Skip
Click to expand...
Click to collapse
Yes it is enabled, and you are under ext4. I wouldnt read too much into quadrant scores and other benchmarks, voodoo is the way to go. Dont be fooled into using those other adb shell ext2 lagfixes for benchmark scores, theyre unstable and are prone to data corruption.
Thanks! That's what I was hoping.
I flashed with the same ROM today and my 2200 quadrant score went down to 900....still trying to figure out what happened. I don't care, but it's a nice to know scenario.
darquegt said:
I flashed with the same ROM today and my 2200 quadrant score went down to 900....still trying to figure out what happened. I don't care, but it's a nice to know scenario.
Click to expand...
Click to collapse
open a terminal and type 'mount' - look for the /data partition. If it's mounted ext4, the lagfix is applied. If it says RFS, you are likely in the same boat as me. You are part of the small percentage of people with a different NAND chip than the rest. Voodoo beta 4 does not support it, wait for beta 5. On the bright side, from what I've read, it also means I have about 500MB more storage than everyone else
I did the manual lag fix and quadrant scores went up to 2400 (about 200 above the previous score on the factory ROM without the OC). The biggest gain was at the DB writes.
Thanks time killer, do you know what that percentage is?
Seems like I don't get voodoo for now either.
A there any other good/bad news about the small percentage?
I came across this post:
SpeedMod based (Doc's ROM and others) and every other Universal Lagfix corrupt badly /system
Thus is will cause the user Some FC overtime, Slow downs, The inability to Revert the lagfix.. or complete system failure.
It means that as long as they don't restore a /system with Odin, they're stuck on kernels using broken mount options.
Want proof
https://github.com/sztupy/universal_...e-init.sh#L273
Highlighted line is using wrong and corruption mount points
Second Issue:
Even with Advance NO RFS Config selected... RFS is still used in /system mounts... Dangerous And mean phone are slowly Dying of corruption..
Click to expand...
Click to collapse
Source: http://forums.hardwarezone.com.sg/showthread.php?t=2998903
Does anyone know what he is warning about?
XxDrAg0nxX said:
I came across this post:
Source: http://forums.hardwarezone.com.sg/showthread.php?t=2998903
Does anyone know what he is warning about?
Click to expand...
Click to collapse
Does someone tell you to check in the forum before starting a thread?
That post is from Supercurio in his tweeter page.He is working on his lagfix for froyo and came out with that today.It would be nice if he could come here and explain further more.
ps i see now that is already another thread with this subject and Ryan tried to explain a little whats happening
Copied my response from other thread on this issue to try and avert panic in case it turns out to be false - don't drop your sztupy kernel just yet - sztupy may be doing the correct thing here, he does usually know what he's doing!
Not 100% sure on this, since I have not used or looked at sztupy's lagfix very much, but that line you are pointing out is not a problem.
If /system is EXT4, then calling mount -t rfs on it will simply return an error message, and not mount it. It will do exactly nothing.
The following line would then mount it correctly.
Basically, this seems to be totally false. More evidence please.
Click to expand...
Click to collapse
EDIT: Okay, OP was updated with better information. Lack of check=no means that the FAT32 check *may* be running on the /system, which would cause corruption.
Probably a good idea to confirm if the filesystem check is actually happening though!
And there should probably only be 1 thread on this issue, this one should be closed!
Well. Dont overreact. I've been running sztupy's kernel fork -> raspdeep's oc for a time being, NO PROBLEMS AT ALL.
Dont confuse users.
Changing a file system doesn't corrupt anything, that's BS. Also long time JFS and EXT4 user.
I've began to work on a ClockworkMod Recovery for the A500.
The work is based on what I've written down in this thread: http://forum.xda-developers.com/showthread.php?t=1056170
As I didn't have the chance to test yet but I'm pretty sure someone wants to play with the code I'm providing it via GitHub:
https://github.com/SeraphimSerapis/Acer-A500-Recovery
This is the link to a first compiled version of it: http://dl.dropbox.com/u/1661232/cwm-alpha-2.img
>> Donate link for buying me lots of coffee <<
Everything is based on the log of the original recovery:
Code:
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /system ext4 /dev/block/mmcblk0p3 (null) 0
2 /data ext4 /dev/block/mmcblk0p8 (null) 0
3 /cache ext4 /dev/block/mmcblk0p4 (null) 0
4 /misc emmc /dev/block/mmcblk0p5 (null) 0
5 /flex ext4 /dev/block/mmcblk0p6 (null) 0
6 /mnt/sdcard vfat /dev/block/mmcblk1p1 (null) 0
7 /boot emmc /dev/block/mmcblk0p2 (null) 0
8 /aboot emmc /dev/block/mmcblk0p8 (null) 0
9 /recovery emmc /dev/block/mmcblk0p1 (null) 0
I couldn't check this part of the code of BoardConfig.mk because /proc/mtd is empty.
As this Device uses MMC this won't be important (IMO)
Code:
# fix this up by examining /proc/mtd on a running device
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x00380000
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x00480000
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x08c60000
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_FLASH_BLOCK_SIZE := 131072
I'd be glad to hear if it worked well for you or if there occured problems.
Have fun with it,
Tim
Update: I've done lots of changes and tried to boot into my recovery.
I just got this message in the upper left corner:
secure boot: image SOS checksum fail!
This means that the bootloader is protected.
The good thing is: I could flash my recovery.img backup and I've got it working again
Update 2: I've split the recovery.img and boot.img to get some more information:
These are the files I got:
recovery kernel: http://dl.dropbox.com/u/1661232/recovery.img-kernel
recovery ramdisk: http://dl.dropbox.com/u/1661232/recovery.img-ramdisk.gz
boot kernel: http://dl.dropbox.com/u/1661232/boot.img-kernel
boot ramdisk: http://dl.dropbox.com/u/1661232/boot.img-ramdisk.gz
I updated my fstab config at GitHub based on these findings.
AWESOME!!!
Thanks for getting efforts started in getting the A500 the Clockworkmod man... This is sweet. I am not an Android developer at all (mainly in WP7) but I would love to help testing anything that is needed.
Thanks DEVS for your hard work and allowing us to costumize our devices to OUR taste!!! jejeje
was exploring my rom out of boredom.... and found the kernel config "around" someone screwed up
anyone can tell me where to find a tegra2 kernel , wana start building some modules
UPDATE: I'm gonna try working with the xoom kernel...
Locked bootloader? That's a bummer and shame on Acer! Right now I love this device so much so that it doesn't bother me but I do indeed hope the wonderful devs get it cracked. I'm happy to test if needed. Good luck and thanks guys!
I hope this gets fixed talked to bumble bee in irc today and hes tryn also. my rom is ready when we get recovery.
dc13 said:
I hope this gets fixed talked to bumble bee in irc today and hes tryn also. my rom is ready when we get recovery.
Click to expand...
Click to collapse
nice i hope he finds a solution. my recovery is ready and wants to get flashed
anything i can do to help u get it before him or help u both find something?
as i've stated here: http://forum.xda-developers.com/showthread.php?t=1059490 you're welcome to have a look if you can find the matter
Any progress on clockwork???
Sent from my A500 using XDA Premium App
The Recovery is finished already. What we need is a secure way to flash it
Sent from my LG-P990 using Tapatalk
seraphimserapis said:
The Recovery is finished already. What we need is a secure way to flash it
Sent from my LG-P990 using Tapatalk
Click to expand...
Click to collapse
How likely is this? Could be a good enough reason to ditch the Iconia and get the Transformer which already has an unlocked boot loader.
chr0m said:
How likely is this? Could be a good enough reason to ditch the Iconia and get the Transformer which already has an unlocked boot loader.
Click to expand...
Click to collapse
I'm a developer, no fortune teller.
Sorry
Sent from my LG-P990 using Tapatalk
i'm thinking an update must be inbound... because they cant be that retarded(excuse the language) to leave the device without at least basic recovery for the user.... that will mean massive warranty work...
this is the worst part we cant experiment very deep because theres no recovery... so fingers crossed on the update...
PS: if you what my opinion any device can and will be hacked just takes the right person or the right idea... a good example is the SE X10
thor2002ro said:
i'm thinking an update must be inbound... because they cant be that retarded(excuse the language) to leave the device without at least basic recovery for the user.... that will mean massive warranty work...
Click to expand...
Click to collapse
Well if they aren't going to unlock the boot loader they had better be super fast with updates.
someone sent me an update.zip saying it was from acer.. its 300mb I have no idea really how to tell if its legit, the build.prop says a build date of 4/22, my current build.prop is 3/29. so maybe?
I'm going to drop it in my drop box, called acer.update.zip.. you guys take a look and tell me!
http://dl.dropbox.com/u/26425679/acer-a500/update.acer.zip
give it an hour to upload
So far its looking like the Android experience Google wanted to protect by holding Honeycomb source code isn't worth protecting. With an overpriced Xoom that still has nonfunctional hardware, Asus launching the TF without much of a supply chain, Samsung doing a full last minute redesign with some TouchWiz thrown in for good measure, and locked bootloader on the Iconia (which I was loving until I read this)...getting a tweaked Honeycomb seems like one of the few perks Android tabs and their users would have. I really hope the situation starts looking up fast
nycbjr said:
someone sent me an update.zip saying it was from acer.. its 300mb I have no idea really how to tell if its legit, the build.prop says a build date of 4/22, my current build.prop is 3/29. so maybe?
I'm going to drop it in my drop box, called acer.update.zip.. you guys take a look and tell me!
http://dl.dropbox.com/u/26425679/acer-a500/update.acer.zip
give it an hour to upload
Click to expand...
Click to collapse
Downloaded...But how would I go about flashing this? I'm willing to sacrafice my tablet and try this out for the greater good of man kind(or our Iconia community. Which ever you prefer. )
kxs783kms said:
Downloaded...But how would I go about flashing this? I'm willing to sacrafice my tablet and try this out for the greater good of man kind(or our Iconia community. Which ever you prefer. )
Click to expand...
Click to collapse
If I remember correctly when you boot hold power and vol down it will boot into an update mode looking for an update.zip on the SDCard. Perhaps if you renamed it update.zip and put it in the base directory of your sd card it might attempt to update.
I'll be having a look into that file..
Regards
that is what I was hoping for, I wouldn't just go flashing it, perhaps sir seraph can figure out If in fact its an update, and maybe it can bring some good
Hi all
can't post in the dev forum so i'm posting here instead. I have installed insanitycm009 and i love it so far, much faster than the previous insanity rom (none cm one) but i'm having some problems with random reboots.
I believe that it may have something to do with my filesystem as i was previously running ext4 on the last insanity rom. i loaded the ext4 manager app i have and it is unable to help me as i don't have a cf-root kernel installed. i am running glitch kernel v10.
ext4 manager shows my filesystems as follows:
/system = yaffs2
/dbdata = unknown
/data = unknown
/cache = yaffs2
as you can see the os is unable to identify the filesystems so i think this is the cause for the reboots. How can i fix this?
insanity cm is based on cyanogenmod 7
this is a custom built rom from the google sources that has nothing to do with other custom roms that are usually based on Samsung roms.
cm7 and miui and of course insanity cm need another type of kernel that is built to support a rom built in that fashion. the filesystem is also handled differently for example other partions are created and other filesystems used (yaffs for example) that means that probably the ext4 manager can't handle the environment. If you want to check what filesystems and partitions you have open the adb shell and type "mount" the same thing works in terminal emulator (an app from the market)
If there really was a problem with your filesystem that would cause you not to be able to read what it, the phone would probably not even boot.
read the insanity thread to see whether other people have the same problem or even a solution.
EDIT:
I know that's not really helpful, I'm sorry
thanks very much for your response.
I have had a quick look through the thread and have been unable to find anything remotely similar to what i am experiencing. (granted it was a quick look)
Don't suppose you have any thoughts do you as to what might be causing the reboots?
If i can't solve it i might just go back to a stock rom and see if i still get the reboots then.