[BETA] e2Revival Firmware

[zjole]

I've done some testing myself.See in my last post.

yeah,mplayer will be linked as the way I used to do it.

[arctu]

Alright. Cool. Hmm.. so, we need to change the kernel uh?

[keaglez]

Hoa... I wonder how to compile kernel... Any tutorial?

[zjole]

The problem is the kernel from that link don't have "multiple key pressing" support.I guess a lot people want it.

I wonder if there's someone here knows how to modify the kernel...

[arctu]

Wait the minute... use the kernel from EXTREME.. I should have support for OC.

Regarding the BogoMips going up only for a second.. I think it should be like that.. APMD has 3 levels right? Low, Mid, High. Meaning.. if I set Mid to 416 it will stay 416 all the way.. it worked on EXTREME..

EDIT:
@keaglez
I'm waiting for your scripts. Heh..

@Rauna
Can you make a bootscreen, powerup and powerdown animation for E2 Revival? Hehs..

EDIT2:
Tested on prototype rokrRevival(OYV3+REVIVAL CGs): Underclocked APMD 108_208_312. It works. My rokrCP reports bogomips as 208... How did you conclude that OC doesnt work on the current kernel?

[zjole]

Isn't the 108_208_312 apmd the standard one? And cpu bogomips changes among these three levels according to cpu usage.When idle
it should be 108.
In order to see if OC wokrs perfectly,I tested with a 416_416_416 apmd.cpu bogomips should be 416 all the time regardless of usage.But,it would drop to 312 once I pressed any key(it would remain 416 if I leave the phone "untouched").How did I know the frequency dropped?I checked the bogomips in telnet(cat /proc/cpuinfo) and with a "realtime sysinfo" app which can refresh every 0.5s.

[arctu]

Pictures as promised:



Some description:
The first few pictures shows a "loading" which means that the "Messaging" isn't running yet, so it is better to wait.
The "IMSI OK" means that the phone is not stolen.
The last few pictures shows what happens at startup if your IMSI isn't recognise. (;
The other pictures consists of the Menu, the tools, the font previewer, other tools and what have changed in rokrCP and some loading screens.

Do take note of rokrGui.. (passworded rar support and many more)(some pictures are at the middle some are at the end)

@zjole
In OYV3 or rather, this prototype fw, the default is 208_312_416 or probably 108_312_416. (; I changed the apmd to my own(the one I spoke of on the previous post[i wrote a typo there, its actually 52_104_208]) and the BogoMips changed. I even felt the phone to be more sluggish. FYI, I'm using my own custom APMD made using the software found on e2mod, not by using a script on the phone. Try the apmd I've attached.

[Taurnil]

cool
hey, why don't you link mplayer to a writeable directory? mplayer may be updated and would be great to replace it....
(still u can count me in for beta testing, even for script testing )

[zjole]

rokrcp and rokrgui are awesome.

I got the 416_all_apmd from motofan.ru,posted by dimichxp.(I believe it's he who made OC possible first)The modified kernel was compiled by him too.Take a look at this post: https://motohell.com/index.php?topic=678.msg3534#msg3534

oh,I've got something(attached) to show you,arctu.I guess you'll be interested.

@Taurnil
You mean link mplayer to /ezxlocal folder or sd card for example and provide a ins archive to let the user to install it after flash the fw?
Why don't you help us fix the apmd changer.

[arctu]

@zjole
You're right... I do believe that he's the one who made it work. Even so, have you tried my modified apmd? You'll know what I mean then.

Thanks for telling me about the e2mplayer. (: However, it's just basic gui. I wanted to make my qplayer this way at first actually but there was a lot of limitations(for eg. e2 doesnt have a file browser). Nevertheless, the source code taught me something... Maybe I'm gonna try the discovery on qplayer.. Thanks again... Ofcourse, thanks to the author for releasing the source code.

@Taurnil, zjole
I believe that isn't nescessarily. I don't want to use user's ezxlocal space(it should be used for other purpose like skins). If the user wants to update, we can just use mount --bind at autorun (now we have the brilliant autorun manager from keaglez).. (;

I hope I can share these wonders to everyone soon!

EDIT:
@zjole
Try the apmd I've attached with the default kernel on oyv3. My results are:
Idling - 103.76Mhz
Normal - 311.28/518.80Mhz
Heavy - 518.80Mhz

BOLD: I think this is where people get confused. As you know APMD job is actually to control speed according to needs... My apmd works fine.. Just that, why does 312 still exists? :S

Btw, tested speeds with cat /proc/cpuinfo with Rockbox and QPlayer.

RAW:

[23:46] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 518.80
[23:47] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 311.28
[23:47] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 311.28
[23:47] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 311.28
[23:47] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 311.28
[23:47] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 311.28
[23:47] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 311.28
[23:48] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 311.28
[23:48] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 311.28
[23:48] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 311.28
[23:48] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 311.28
[23:48] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 311.28
[23:48] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 311.28
[23:48] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 311.28
[23:48] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 311.28
[23:48] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 311.28
[23:48] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 311.28
[23:48] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 311.28
[23:48] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 311.28
[23:48] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 311.28
[23:48] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 518.80
[23:49] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 518.80
[23:49] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 518.80
[23:49] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 518.80
[23:49] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 518.80
[23:49] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 518.80
[23:49] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 518.80
[23:49] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 518.80
[23:49] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 518.80
[23:49] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 103.76
[23:49] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 518.80
[23:49] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 518.80
[23:50] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 518.80
[23:50] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 518.80
[23:50] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 518.80
[23:50] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 518.80
[23:50] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 518.80
[23:50] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 518.80
[23:50] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 518.80
[23:50] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 518.80
[23:50] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 518.80
[23:50] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 518.80
[23:50] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 518.80
[23:50] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 518.80
[23:50] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 518.80
[23:50] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 518.80
[23:51] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 103.76
[23:51] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 103.76
[23:51] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 103.76
[23:54] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 103.76
[23:54] root:/mmc/mmca1/.system/QTDownLoad$ cat /proc/cpuinfo | grep Bogo
BogoMIPS        : 103.76

[Taurnil]

sup
That happens cuz E2's processor speed is not only controled by apmd daemon; the kernel also controls the speed... you see 312MHz even if u use a 416-416-416 apmd for that reason.
Dimichxp compiled a kernel a some months ago, wich gives full speed control to apmd daemon, it's on e2mod. Sadly, it has a bug when you take pics with the camera... So I guess we'll need to compile our own custom kernel. There's a guide to achieve this @it168. It's a pain in the ass to find a thread there, but I'll check the forum and tell ya later... (^_^)

@zjole: I would be glad of helping you with the apmd changer, but I don't need an apmd builder on my rokr, only an apmd switcher... I made one a couple months ago I can work on it if you want. would be fun to put .apmd extensions on apmd files and associate them to this app... so you can pick it on your file manager to test it on your rokr, so you must run the app to make the apmd be mounted during boot time.... ¿what do you think?  (n_n)

@arctu:
About mplayer mounting... it's also a good idea. Keaglez should add a check+mount for /mmc/mmca1/.system/mplayer (or some similar path) to "replace" mplayer binary with ease. We shouldn't mount on my_favor, mplayer is kinda big and would fill our phone memory (X_x)
offtopic: may you post your font? i like it... want it sooo bad (*_*)

ADDED:
Got the link.
There's an index to the main threads on 3d's forum...
and here's the guide to compile your own kernel....

[pizzadox619]

@arctu:
About mplayer mounting... it's also a good idea. Keaglez should add a check+mount for /mmc/mmca1/.system/mplayer (or some similar path) to "replace" mplayer binary with ease. We shouldn't mount on my_favor, mplayer is kinda big and would fill our phone memory (X_x)

i think so

[arctu]

@Taurnil
Ah, I get it now... I missed a point.. no wonder... Really, thank you for all the info.. (esp. the kernel compiling)
Yeah, I think you should make the APMD changer.. After much consideration, I thought it would be best to make it a "changer".. I'll label it as "expert-only" so the new users would understand that it requires some knowledge for use. The file association idea is brilliant.. I will do it for fonts too.. (;

Offtopic: I'll post up the font later

@pizzadox
Yup, I agree too.

[zjole]

@arctu
I knew you would get some ideas from e2mplayer.
And you know why I was talking about the apmd and kernel issue,right?(Thanks Taurnil for the clearer explanation.)Anyway,OC still works with the OY3 kernel,just not so perfectly.

@Taurnil
I don't need a apmd builder either.(I even don't use OC)I think your idea of associating apmd is great.Then we don't need to leave space for predefined apmds.Would mind working on it?You know,I really suck at scripting(even had some trouble making the apmd changer working properly at first ).I guess I should just be the firmware maker.

[arctu]

@zjole
Yup, after I tested things out and Taurnil clear explanations.. I get what you meant. (; Yeah, OC works just not perfect. So now, the question is, do we really need another kernel? Because, I fear that if APMD totally controls the speed, battery life would be an issue.

You are a good FW maker.. no worries. (;

@Taurnil
For the APMD Changer here is what you should do:

Clicking *.apmd will pop up menu:
1. Use APMD
2. Auto Start This APMD

No. 1 will simply OC the phone. No. 2 will copy the apmd to /ezxlocal/.system/apmd and will autorun at startup. You need not worry about the autorun for now since we are using a different system of autorun... Just leave a spot so that autorun can be integrated easier later when the APMD changer is working perfectly. So, it runs down to:

1. Click *.apmd
2. showRadio: 1. Use APMD; 2. Use APMD as Default
3. Clicking 1 will do the command to use the APMD
4. Clicking 2 will copy the apmd to /ezxlocal/.system/apmd

That's all you need to do. (: I'm sure you can accomplish that...

Hmm.. I wonder where is keaglez, celebrating Chinese New Year perhaps? hehe..