Hi to all, i finished to edit atools:
Changelog:
Use the same selector for fstab and bse
added lcd density
correct partition resize for polaris and kaiser
Fix error in mapping
Now i need someone to test it.
You can find the latest version on git
I have also bad news. My friends gave me a present for my graduation: an Iphone 4, so i'll slow down a lot my android develop.
Thanks for all you do! I'm about to take it for a test run now.
I say sell the iphone and get an EVO!
I will test it in a few days when i have my 8Gb Class 10 SD-Card. But I must wait a few days.
l1q1d said:
...
I have also bad news. My friends gave me a present for my graduation: an Iphone 4, so i'll slow down a lot my android develop.
Click to expand...
Click to collapse
wow, that is bad news (for us) but good news on the graduation
so you have some choices, turn off your brain and just use the iphone, tear it apart and dual boot with android, sell it and buy something interesting.
keep us posted.......
in the mean time i will also be trying latest atools.
I haven't a shudown script for my brain so i keep working on android (but slowly).
i wait for news of new atools
Well, thanks for all the help! Maybe you can get android running on the Iphone 4 better lol.
l1q1d said:
I haven't a shudown script for my brain so i keep working on android (but slowly).
i wait for news of new atools
Click to expand...
Click to collapse
thanks for everything man, it is nice not having to have the androidonHTC phone as your primary, it should be easy for you to be able to continue development when you get time even with the iphone because unlike us vogue users you atleast have wifi to be able to test with along with being able to swap your sim.
i will be hitting the thank you button as soon as i finish posting this reply (everyone should)
l1q1d said:
Hi to all, i finished to edit atools:
Changelog:
Use the same selector for fstab and bse
added lcd density
correct partition resize for polaris and kaiser
Fix error in mapping
Now i need someone to test it.
You can find the latest version on git
I have also bad news. My friends gave me a present for my graduation: an Iphone 4, so i'll slow down a lot my android develop.
Click to expand...
Click to collapse
Noooo...another dev leaving!! You will be missed. BTW, you need to teach me how to edit init.lzma
sure:
checkout this git://androidhtc.git.sourceforge.net/gitroot/androidhtc/bootenv
then edit the initrd/init
from linux or mac do:
Code:
sudo sh buildInitrd
and you have the new initrd.gz and .lzma
I am really sorry to hear that You made a pretty good job here. I wish I could do the same... but I am far not as good as you are...
Thanx for what you did.
l1q1d said:
Hi to all, i finished to edit atools:
Changelog:
Use the same selector for fstab and bse
added lcd density
correct partition resize for polaris and kaiser
Fix error in mapping
Now i need someone to test it.
You can find the latest version on git
I have also bad news. My friends gave me a present for my graduation: an Iphone 4, so i'll slow down a lot my android develop.
Click to expand...
Click to collapse
I don't wich to say that i know you, because i don't. But from your job here, from what i've seen you do here... you'll be back. iOs will sufocate you...
Thanks for aTools. I've used it, but didn't change partitions. Will try next time.
@ l1qu1d
Congrats 4 ur graduation... party time! so ur turning to the dark side of the force with ur iphone 4?
I updated my kaiser to the latest kernel (VOGUIMG-320-FROYO-11-29-10.NBH) and used this version of atools to correct the kernel for kaiser,froyo & resolution, and now i can't select my data partition type anymore in the Android Installer bootloader. I can only select the type of the SYS. (replimenu 0.9)
Update: When i use version 1.0.4 of atools, my data selection is back. Tried 3 times with 1.1.0...
Also the AUTO screen detection doesn't work in version 1.0.4. (my screen type = 1 and i think it used 2) Could not see if this is fixed in 1.0.5.
Hi,
I also used 1.1.0 yesterday with my kaiser and couldn´t find the data partition (I have it on the p3 on the sd card
p1 = FAT32
p2 = swap
p3 = ext2 (where I have my data)
setting it to p3 didn´t seem to work
In the end I had to reinstall the android not so super froyo tar ball as well after putting the kernel (which I had planned to eventually do anyways to bring it to RLS18)
test results
nice work, here are my findings (pola100, kernel 2.6.25):
i needed to add a cast (also in previous versions) to be able to create partitions:
Code:
870 end = str([COLOR="Red"]int([/COLOR]start[COLOR="Red"])[/COLOR]+int(self.listofdata[i+1][2]))
but partitioning still fails on boot, obviously the total size is slightly smaller than the number defined in atools. i suggest getting the total size from parted using sed instead of rigid numbers - but then one must define which partition's size shall get adapted if necessary. e.g. user interface in atools:
8gb sd-card,
1st partition 4gb fat32 (*),
2nd partition 3.5gb ext2
3rd partition 0.5gb swap
*: will be decreased if necessary (e.g. if true total size is 7.98gb instead of 8gb)
quick and dirty alternative: allow manually entered 'total size' instead of dropdown selection.
further, formatting fails because the new version uses /dev/block/mtdblockx instead of /dev/mtd/mtdx.
hope this helps!
peter
peter s said:
nice work, here are my findings (pola100, kernel 2.6.25):
i needed to add a cast (also in previous versions) to be able to create partitions:
Code:
870 end = str([COLOR="Red"]int([/COLOR]start[COLOR="Red"])[/COLOR]+int(self.listofdata[i+1][2]))
Click to expand...
Click to collapse
I'll correct it in next release
peter s said:
but partitioning still fails on boot, obviously the total size is slightly smaller than the number defined in atools. i suggest getting the total size from parted using sed instead of rigid numbers - but then one must define which partition's size shall get adapted if necessary. e.g. user interface in atools:
8gb sd-card,
1st partition 4gb fat32 (*),
2nd partition 3.5gb ext2
3rd partition 0.5gb swap
*: will be decreased if necessary (e.g. if true total size is 7.98gb instead of 8gb)
quick and dirty alternative: allow manually entered 'total size' instead of dropdown selection.
Click to expand...
Click to collapse
It's totally unuseful because the partion size can't be read on the host and also in the generated code (install-seq.sh) there isn't the the highest limit in number but -0 so parted autocheck that number.
peter s said:
further, formatting fails because the new version uses /dev/block/mtdblockx instead of /dev/mtd/mtdx.
Click to expand...
Click to collapse
it's a know bug and it will be corrected in next release.
Just downloaded a regular kernel, Set Screen DPI to 160, 320x428, Panel type 1 and Keyboard type normal. Created a custom keymap with it as androidupdate.tar. Installed new kernel, and updated, wiped dalvik cache and my kaiser's keyboard is completely non-responsive. I double checked the kernel again with Atools and still the same :|
Just wanted a 2.6.32 for testing out Eclair and all of em were tick marked for Froyo
Still fails to install to the nand on my Vogue..
Thanks for the great software.
What is a good setting for a 1350 mah battery for Kaiser running Froyo from Haret? There are a few choices, which is most accurate?
Thanks again!
hi all,
again i tried to find the min reserved mem and max available mem in gingerbread
although i've found where to change them, i have no clues what the optimized values are up to this moment
for those who are interested in changing the mem thing or want to know where is FIMC0/FIMC1/FIMC2/MFC0/MFC1 etc, pls take a look at my blog at
http://ykkfive.blogspot.com/2011/04/reserved-memory-settings-for-galaxy-s.html
hope this helps
hi all,
i am very new in android OS.
i have bought the epad Superpad II Flytouch 3
spec shown on ads is: (main)
10.2" SuperPad II flytouch3
Android 2.2
GPS WIFI Camera 3G
RAM 512MB
CPU 1GHz Infortm X220
Flashplayer
option: 4G/8G/16GB built in memory.
and so i buy the 16GB build in memory.
What i need to know is:
i only seen with Android System Information:
Internal Memory : 3.38GB available space
RAM : 327mb and 228mb Free
CPU : ARMv6 Compatible (v6l)
but in MyPad Shortcut : there are 10.33GB Free (i don't know what it is)
My question is :
1. Is the ads exactly tells the truth or fraud?
2. What is the different between Internal Memory with Memory shown at MyPad
3. How can i use the 16GB build-in memory as promised?
Thanks for attentions.
awenk2000 said:
hi all,
i am very new in android OS.
i have bought the epad Superpad II Flytouch 3
spec shown on ads is: (main)
10.2" SuperPad II flytouch3
Android 2.2
GPS WIFI Camera 3G
RAM 512MB
CPU 1GHz Infortm X220
Flashplayer
option: 4G/8G/16GB built in memory.
and so i buy the 16GB build in memory.
What i need to know is:
i only seen with Android System Information:
Internal Memory : 3.38GB available space
RAM : 327mb and 228mb Free
CPU : ARMv6 Compatible (v6l)
but in MyPad Shortcut : there are 10.33GB Free (i don't know what it is)
My question is :
1. Is the ads exactly tells the truth or fraud?
2. What is the different between Internal Memory with Memory shown at MyPad
3. How can i use the 16GB build-in memory as promised?
Thanks for attentions.
Click to expand...
Click to collapse
Do you have adb shell access? The best way to settle this "dispute" with the device is to run
df -h
from adb shell, and it will tell you the size of each partition. Add the sizes up (if it ends M, it's Megabytes, if G it's Gigabytes). See if it adds up to 16 GB... Regarding RAM, post the output of the command
free
from adb shell and we can see how much RAM exists.
hi thank you for the answer.
where can i get this adb shell access?
i use terminal emulator but the command doesn't work.
If terminal emulator doesn't work please try Better Terminal Emulator.
Make sure you run:
SU ----> to run as superuser
For CPU information, is there anyway to check it?
Hi guys, I am writing to ask you this question because every time I see a new custom rom in the development section I always wonder: "How do they create or improve a rom and what are the languages that you need to know?". I know that may seem like a stupid question but I can not find a starting point.
translated from Italian to English with google translator, if I made some mistakes in the writing I apologize in advance.
http://source.android.com/source/initializing.html is a good starting point. You could then add stuff from other ROM devs.
You should also familiarize yourself with the concept of searching. That's definitely a requirement.
The guide says: It is possible to build Also Android in a virtual machine. If you are running Linux in a virtual machine, you will need at least 16GB of RAM / swap and 30GB or more of disk space in order to build the Android tree.
I have a laptop Acer Aspire5750G with Windows8, has only 4GB of RAM, a processor IntelCorei7-2630QM, HDD 750GB and a GPU Nvidia GT540M. If I put ubuntu 10.04 in dual boot just the ram?
it says 16GB of ram or swap space.....
Note: It is also possible to build Android in a virtual machine. If you are running Linux in a virtual machine, you will need at least 16GB of RAM/swap and 30GB or more of disk space in order to build the Android tree
Click to expand...
Click to collapse
Hello, I have a Asus Fonepad ME373CG, purchased in Italy, (the same as ME372CG: only changes the size of the SD memory CARD) and I would like to activate a virtual RAM memory to add to 1 GB provided by the device.
I tried with different app (Simple Root Swap, Swapper Configuration).
At the end, the app MemoryInfo & Swapfile Check gave me the message that my Kernel does not support swap.
The OS is Android 4.4.2
- Build KVT49L.6.4.4 WW_epad-V-20140922
044000263_201405210029
- Kernel 3.10.20-00002-gc4c2d96-android @ mec11 # 1.
Is it possible?
Greetings.