yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Android Development] chourmovs:
this morning i did the 130 mb trick with atool and flash again without success

in fact i'm not very confident with atools result as we can see it physically

in atool i have always been with a nand p2/nand p3 setup as you say

Another thing : update don"t go wrong in nand environment : it installs well and say "update completed" (with standard kernel but not with debug kernel)

Now I'm going to ubuntu+gparted to test system and data into ext4 partition for debug purpose

We're gonna get it :D
[Tilt, TyTN II, MDA Vario III Android Development] chourmovs:
it works on both system and data on sd card ext4 part :D

my config FYI :

2.5gb fat32

500 mg ext4

256 mg swap

500 mg ext4

we've to find what's break in nand

Liquid are you sure of your "alterate fstab option", i've already noticed with other kernel that trying to resize nand partition give strange result, like maybe an inversion between system and data size

Maybe nothing to do with it
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
i didn't change the code from the original version and it always works... i'll ckeck it
[Tilt, TyTN II, MDA Vario III Android Development] chourmovs:
Ok liquid forget about it, i did some further test and fstab alteration works well (i inverted space and get a new "no more space for system" error)

that's something else

I tried sys on 212 mb nand and data on ext part and i get the kernel update error

Question is : why only polaris get this error ?
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Hm, I've never had a problem adjusting NAND space between system and data with my Kernel. Though again I'm using a HTC Kaiser, and you're using a Polaris so could be slightly different memory spaces for each device.

Anyways, glad that the SD Card trick worked. One thing you could try is loading a stripped Froyo version like Gingerbones, and then applying the Kernel update. That build is pretty lightweight (about 88MB if I recall), and my update should load on a stock partition setup.

I've actually made a very important leap in my Power Management indevor. Last night I left my phone on and off the charger, and the phone sat at 98% charge when I unplugged it and went to bed. This morning at 7am, the phone was at 66%. Yes that is a big drop, but that is also because I had left my wifi on all night.

I checked my Battery History, and it showed correctly that the phone had been awake for only 15minutes. I shut off the wifi, and head off for a job interview that lasted 2hrs. When I came home, the battery only dropped 1%, and the phone still reported correct sleeping time.

I am making more fine tune adjustments to the idle time and sleep times of the phone, and hopefully I believe I may have gotten our battery life increased! :)

I will report back with more information when I test my new kernel build.
[Tilt, TyTN II, MDA Vario III Android Development] chourmovs:
Good evening

i tried with aceoyame gingerbone 5.25 and get the same bad result

Congrats for the battery, i saw a very good detection level when i succeed to install on ext4 but it was to slow for daily use :cool:
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Did you modify the fstab to change the size of your system partition?

Plus which version of atools are you using (1.1.0)?

Earlier versions would cause an issue with the kernel reading the NAND partitions after hey were modified with atools. Basically report that the mtdblockp# is not a valid device or "device not found" error.

Try flashing an unmodified version of the kernel and see what happens?
[Tilt, TyTN II, MDA Vario III Android Development] chourmovs:
no, not for this last attempt, but polaris have 102 mo for the system by default like kaiser and vogue :confused:

1.2 the last one

i flashed everything everyday with success (kalt kaffe, dzo, liquid...etc) but i'm not sure of witch version of "unmodified version of the kernel" you are speaking about

at your service :)
[Tilt, TyTN II, MDA Vario III Android Development] -Arturo-:
@ Krazy

Is there any chance that you could build 2.6.25 kernel with ext4 support and with your recent tweaks?
[Tilt, TyTN II, MDA Vario III Android Development] chourmovs:
Very ambitious kernel as it has not been for a while, i'm sure we will win against this polaris issues

a suggestion : why don't you try to build us a polaris nbh as martin use to do before , maybe something wrong with atools and your kernel, and you may see what's going wrong in your code by doing this :o

maybe you can share your source with liquid,scoot and n2rjt (i'm not sure of this last sentence because you're smarter than me and maybe it's already a collaborative work :o)

I can't wait for your kernel working together with my nand :p
[Tilt, TyTN II, MDA Vario III Android Development] V3rt!g(o):
still wrestling with battery usage. Is there any way to find out what is using so much power? I switched everything off, kill all programs and services, enabled airplane mode, and it is still arrount 1000mA drag. Tried few distros and radios...getting out of options.:confused:
[Tilt, TyTN II, MDA Vario III Android Development] scooter1556:
I'd be happy to take a look at any source code changes. I haven't had time to keep up with the experiments in this thread what with exams etc... but i intend to spend a lot of June working on the kernel as I have a month relatively free. I can push worthwhile changes to git also :) Happy to help any way I can.
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Glad to hear. Though currently I'm unsure why, but CPUFreq is enabled in the config, but apparently does not enable in the Kernel during startup. I spent a good deal of the morning going through the directory structure of my phone trying to find some reference of CPUFreq. At this point I don't care if it's running, i'm more worried if it's even in there.

The last week or so, I have been studying the kernel source, as I am pretty new at this, and trying to get my bearings on what I can do safely and what can be done aggressively to further tune this Kernel for our devices.

From what I'm understanding the phone is not idling properly while it is on, but sleeps and idles at that point just fine. Which could be why CPUFreq is not able to recognize the fact the CPU supports clock scaling, which I believe it does support as it ramps down it's clock to 20MHz upon entering standby mode.
[Tilt, TyTN II, MDA Vario III Android Development] ben.kank:
Problems installing

I am trying to install rls 4 but am having trouble. I keep getting the message 'Install module for this kernel apply modules/androidupdate.tgz failed from sourceforge'. Noticed another person had the same problem but applying androidupdate,tgz doesn't seem to resolve the problem. Just want to verify that I am installing everything properly. I partioned my sdcard with a 7.5gb fat32 partion and two 216 mb ext4 partitions. I flashed the kernel. I downloaded the modified CM7 RLS1 androidinstall.tar provided in the first post and installed it with system on nand and data on sdcard. Finally, I updated with the androidupdate,tgz in the Latest Kernel.tar. Am I missing something? Any ideas on what I am doing wrong?
[Tilt, TyTN II, MDA Vario III Android Development] chourmovs:
i'm one of the other person

The good question is "what is your device" ?
[Tilt, TyTN II, MDA Vario III Android Development] ben.kank:
Sorry about that. I'm running an ATT Tilt.
[Tilt, TyTN II, MDA Vario III Android Development] chourmovs:
:eek: :confused: :D
[Tilt, TyTN II, MDA Vario III Android Development] Magister2k7:
Krazy-Killa,

is there some public repository with your's changes?
[Tilt, TyTN II, MDA Vario III Android Development] spawn4group:
I am having the same issue mine is also AT&T Tilt are these modules polaris only or something, cause i've flashed the kernel & installed modules 3 to 4 times now :confused:
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Too everyone who is having issues with androidupdate.tgz file. I'm going to look into tomorrow. As ben.kank mentioned, it's possible one of my archive files may have a damaged directory structure, so I'll take a look, and see if that's the case.

I'll look at my archives tomorrow, and see what's wrong.
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Once I resolve the issue with the module update files, after running a 1 1/2 day test with my phone sitting in airplane mode and idle for 1day 6hrs and 30minutes, my phone was at 84% capacity.

Still battery drains faster than it does in WinMo while you use the phone, as it still does not idle while active.

Too everyone, I am looking at my archive files in the OP, and checking their directory structure, and also will even use the files to flash my phone and see if I can replicate it as well.

Currently I am backing up my data on my SD Card as it's producing a ton of errors and very very very slow read/writes. So I'm backing up all my data, and re-formatting the SD Card completely.
[Tilt, TyTN II, MDA Vario III Android Development] pupinito:
still getting the install modules message with RLS5 :S

Thanks for your effort!
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Did you try downloading the seperate androidupdate.tar file and removing the one from the other package you downloaded?
[Tilt, TyTN II, MDA Vario III Android Development] chourmovs:
i just retried it without success
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
It should definitely now be fixed, and it was something very simple, lol.

Everyone who was having problems with installing system on NAND will have their issue resolved now. There was a code error in the update install script that prevented system from mounting correctly during the update process.

This was not device specific to Polaris, nor was there an issue with the androidupdate file. Everything should be back to normal.

Thank you all for your patience and please let me know if there are any other issues with the Kernel that needs to be addressed, or if the off chance this issue still persists! :)
[Tilt, TyTN II, MDA Vario III Android Development] chourmovs:
I'm afraid it is not, here is the root bootlog, nothing in nand

sh: 0: unknown operand
AutoMode for system
AutoMode for data
Install module for this kernel
apply modules/androidupdate.tgz
Failed
from sourceforge
sh: 0: unknown operand
AutoMode for system
AutoMode for data
Install module for this kernel
apply modules/androidupdate.tgz
Failed
from sourceforge
sh: 0: unknown operand
AutoMode for system
AutoMode for data
e2fsck 1.38 (30-Jun-2005)
e2fsck: while determining whether /dev/block/mmcblk0p3 is mounted
/dev/block/mmcblk0p3: clean, 11/64256 files, 8126/257024 blocks
/init: line 338: data_partition: not found
Install module for this kernel
apply modules/androidupdate.tgz
Failed
from sourceforge
sh: 0: unknown operand
AutoMode for system
AutoMode for data
Install module for this kernel
apply modules/androidupdate.tgz
Failed
from sourceforge
sh: 0: unknown operand
AutoMode for system
AutoMode for data
Install module for this kernel
apply modules/androidupdate.tgz
Failed
from sourceforge
sh: 0: unknown operand
AutoMode for system
AutoMode for data
Install module for this kernel
apply modules/androidupdate.tgz
Failed
from sourceforge
sh: 0: unknown operand
AutoMode for system
AutoMode for data
Install module for this kernel
apply modules/androidupdate.tgz
Failed
from sourceforge

Let me know if you want something else...

PS : got an unusual EncFiltLog.menc at the root of my sd
[Tilt, TyTN II, MDA Vario III Android Development] pupinito:
Same here, reinstalled kernel, applied modules update but got the same install modules message
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Have you tried a full reinstall of Android on system NAND then install update and then fix Permissions?
[Tilt, TyTN II, MDA Vario III Android Development] chourmovs:
yes i did it again right now, same result
[Tilt, TyTN II, MDA Vario III Android Development] pupinito:
Same result as you, i just have to clarify this is happening with a Kaiser, i don't know if you'r testing it witha a Pola
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Ok, it is now fixed! I managed to test it myself by diverting every scrap of my NAND to system, and it gave me 107MB of available space for system to use, which is more than enough to install Android.

After running through it myself, I found that there was an issue with the configuration for NAND, and reverted to an older configuration I had, and went from there.

Result, NAND installations are now successful, and fast. Since I'm now able to install Android on NAND, i'm going to work on re-enabling some of the features that were enabled in the Kernel without breaking usability.

New files are in the OP. :)
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
Maybe you can update the kernel changes to git :-)
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Do I need special permission to push to the git? :o
[Tilt, TyTN II, MDA Vario III Android Development] chourmovs:
it works :o

Unfortunately i have a "no sim card" error whatever i try (even if i flash back to stock WM)... i think my phone is bricked

If anyone know the problem... i saw a lot of people claim about hardware issue looking like this
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
if you don't have it already susbscibe to sourceforge and ask to dzo
[Tilt, TyTN II, MDA Vario III Android Development] scooter1556:
If you have any trouble or want someone to look over the changes do a git diff and send it over.
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
I'll have to do that.

I think my pm.c modification is working really well. I now have a working SIM in my phone, and have a solid radio connection with my carrier, and phone still sleeps deeply while the radio is on, and battery life still holds steady or drops very very slowly.

Also Battery Status is reporting that the phone is not awake while in standby, unlike with other kernels I have used, the phone remains awake more often than what I am seeing here. And under Spare Parts > Battery History, the Running bar reports an accurate level. And for the 1hr 31 minutes my phone has been booted on battery, it's been running 9.3% of the time, and the screen has been on 8.8% of the time. :)

I am really looking forward to being able to code, confirm and bring online CPUFreq, as it will provide a significant boost in our battery life, hopefully to near WinMo standards. :D

I know it's been less than 24hrs, but if anyone else is using the Kernel, can anyone report their status on how battery life is doing while the phone sleeps? :o
[Tilt, TyTN II, MDA Vario III Android Development] dany547:
good

nici job man,if the phones battery is at 0% you must charge the battery from an external adaptor? or the problem is fixed?
[Tilt, TyTN II, MDA Vario III Android Development] pupinito:
I'll try later on today and post the results!!
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
As far as I know, I still recommend letting the battery charge on an A/C charger until the battery reaches a good level then you'll be fine to plug it in anywhere (PC, Laptop, Wall, etc)

Sounds good. Now just want to make sure you're aware. I'm wanting results of the phone sleeping with the radio on and possibly a separate test with radio and wifi on as well.

Reporting battery life while phone is on more than 50% of the time will yield results I do not want, as that is not the scope of my changes. CPUFreq will solve, if it works the huge drain in battery while the phone is on by down-clocking the ARM9 and possibly, though highly unlikely, the ARM11 core as well, which controls the Radio Voice/Data chip and also decreasing (I hope) the voltage of the processor(s).

Oh I would also like to report the phone charges faster while sleeping on the charger. Though I am not sure if this is just a placebo effect or an actual effect of the new pm.c code in place. I am still running more tests myself, and because it involves testing power drain, it is very time-consuming.

EDIT: After checking Battery Status while charging. The phone is still deep sleeping while on the charger, which is another big jump, which confirms as well why the battery charges faster, as there is more voltage available to go to the battery for charging as everything else is in low power mode. :D
[Tilt, TyTN II, MDA Vario III Android Development] oroo708:
hey there...

nice work dude...

i've try ur kernel & its working great!!

but i'm more a haret user so just tried it but it seems ur zImage hav some sort of problem.

the bootloader just didn't load-up..it just stuck on haret loading..or probably its just a problem with my phone??

i've tried using ur zImage with different initrd but stil won't work..

nwy thanks for the nice work..
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Hm... Unfortunately I have no way of loading WinMo on my phone, and this one I can't find a workaround. :(

It could be because HAReT uses a different method of initializing Kaiser's devices, some of my modifications may not be compatible with the HAReT method then, but I want to see if there are any other HAReT users having this issue as well?
[Tilt, TyTN II, MDA Vario III Android Development] oroo708:
owh ok...

thank for quick feedback..

:)
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
What kind of device do you have btw? So far I can confirm my kernel working for Polaris and Kaiser, but no info from any vogue users. :-(
[Tilt, TyTN II, MDA Vario III Android Development] oroo708:
i'm using Kaiser WM6.1
[Tilt, TyTN II, MDA Vario III Android Development] msichal:
Is it still recommended to use data on sd or is the nand working fine now?

Does USB work or is it still broken?

I need to flash this new kernel, i think im still using like RLS 5.3 or something like that.(and my android behaves strange, it is now vibrating in random delays o_O)
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Yes, it is still recommended to use Data on SD due to the NAND driver issues.

I recommend upgrading to RLS5.7 as it fixes a lot of issues from previous builds and introduces my Power Management change which boosts battery life almost 3x.
[Tilt, TyTN II, MDA Vario III Android Development] drfno1:
FYI

Thanks for the new kernel.

On one of my phones tried using Haret and had the same result as oroo708 (locked up booting).

Past 24 hours

kernel = your RLS5.7.

system = Scoot CyanogenMod 6.1.2 RLS6

Atools edits: overclock to 500, overclock GPU, alter /system= 163MB

/data on ext4 (don't know if it matters but if using ext4 why not give the NAND to system?)

RougeTools bumps overclock to 529

GPS OK

Wifi OK

GPRS data (limited to EDGE) OK

Had some trouble receiving calls, added phonerenicer app to change priority and calls are OK

Phone has been very stable and battery status reports are very similar to yours.

If it can get past the 3day crap-out I always seem to have, this will be a great step forward.
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Thanks for that, and glad you reported that HAReT doesn't work for you as well as it gives me more proof so to speak to look into why HAReT doesn't work with my Kernel.

Also thanks for the battery report, and for the fact that you have an overclocked CPU and GPU and you still get about the same results as I do.

Which brings me to my next thing, if I do get CPUFreq operational, I will test this, but I believe overclocking using Rogue Tools will be impossible because CPUFreq will go by the saved clock speed during bootup, which is what you set in atools. So if that'll be the case, I'll make a point of overclocking using atools only, since you even reported the phone is stable even with an atools overclock.

Please, everyone is testing, bring in more reports on battery life during standby so I can gauge how well this is working. I am personally doing a test too see how long the battery will last on one charge (from 10:45am this morning onward), and with below normal usage (checking XDA, making a post or two, checking email whenever it arrives, and responding to one or two text messages so far)
[Tilt, TyTN II, MDA Vario III Android Development] drfno1:
I decided to stop the RogueTools and just go with the Atools overclock to test the stability. So far the phone is stable and appears faster than with RogueTools. Maybe it is my imagination.
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
There is a way to check the CPU frequency. If you load up the Terminal, and type cat /proc/cpuinfo

At normal speeds (400MHz), You'll see BogoMIPS: 383, so at any other speed, this should read different, and possibly less than what the stock speed is at.
[Tilt, TyTN II, MDA Vario III Android Development] tiagoclc:
cache folder

Krazy,

I'm getting 8kb/s downloading from market.

Could you, please, change download location from /sdcard/Download to /cache and set mtd@userdata to be mounted on /cache

Thanks!
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
I'm not getting those speeds while I use Market. I've used two builds, and each download Market at about 200-400KB/s, but it only spikes due to SD Card read/write speed limitations.

Making those changes will definitely be a drastic change that I feel is not necessary unless more people are reporting this extremely slow speed.

What class SD Card are you using? Class 6 or higher is highly recommended, class 4 is doable for NAND installations with SD Card apps. Also check if you're using WiFi or EDGE/3G. There are ALOT of factors that'll explain the slow speeds, but moving not only the Android download location AND userdata to /cache is not recommended as Cache is not permanent, if the phone crashes or you reboot, that data is lost.
[Galaxy S I9000 General] Coolman4now:
- Hi there

- Can the Ovi Maps from nokia be ported to SGS in anyway ???

- I used to have i8910 years ago and with a hacked firmware I could change the Phone ID to N97 For example and use all Nokia services.

- I only need the Ovi Maps as it has offline Maps for Egypt.

- So any help would be extremely appreciated, thank you.

:)
[Galaxy S I9000 General] SkinBobUk:
Ovi maps runs on symbian os so i imagine it would be incredibly difficult to port it over.

Just like most windows software won't work on linux and vice versa.
[Galaxy S I9000 General] Bo$s:
No. Without sources it's impossible to port Ovi Maps from Symbian to Android.

Yes but Nokia hasn't any services for Android so it's pointless.

You should try Android navigation apps (f.e. iGO, Sygic, Navigon). They also should have offline maps for Egypt.
[General Questions and Answers] owerlord87:
when i was on darky 9.2, SECuRET SpyCam worked great and after i installed darky 9.3 the video mode makes the shutter sound no matter what options i do, silent mode not helping

any help?
[General Questions and Answers] owerlord87:
can anyone help me? : o