[ROM 07-12] TripNMiUI S001.1RC.1.12.2 | RELEASE CANDIDATE | ENDTIME Kernel

[Guest dolapo]

Is the kernel part of the ROM?

[Guest ofsinreno]

Is the kernel part of the ROM?

The kernel is the main piece of programming that the rom uses to operate. I have seen it compared this way: if a ROM is a car, the kernel is the engine.

[Guest Jim Mc]

Bricked kernel also works a fine treat =]

So no issues with bricked kernel at all

[Guest KhanSW]

Trip,

I'm also getting random reboots out of nowhere. Not using the phone at all, its just laying on my nightstand charging and its rebooted itself 3 times in the past hour.

[Guest Grudgie]

Trip, can i ask u if u can make a rom with the new market in it? Cause everytime i want to use the new market i get FC, so i cant use it.

Would be nice i if u want to make a rom version with the new market, pls?

Thank you!

[Guest maxtcee]

is there anyway to remap my search button back to use google i hate the miui search and want to use the old search with google

[Guest adclem]

is there anyway to remap my search button back to use google i hate the miui search and want to use the old search with google

Yes, just install google search from the market.

[Guest Kaahru]

Trip,

I'm also getting random reboots out of nowhere. Not using the phone at all, its just laying on my nightstand charging and its rebooted itself 3 times in the past hour.

What are you doing before and after flashing the ROM? MIUI Backup? You did all the correct wipes?? (data, cache, dalvik cache).

What I did is:

-Entered Recovery

-All wipes

-Flashed Rom

-Tested it, and wifi was not working, so the camera and other things were buggy, thought it was the kernel

-Entered Recovery

-Wiped Cache & Dalvik Cache

-Flashed Kernel 050

-Boot & Voilà, all working

Hope it helps!

[Guest KhanSW]

What are you doing before and after flashing the ROM? MIUI Backup? You did all the correct wipes?? (data, cache, dalvik cache).

What I did is:

-Entered Recovery

-All wipes

-Flashed Rom

-Tested it, and wifi was not working, so the camera and other things were buggy, thought it was the kernel

-Entered Recovery

-Wiped Cache & Dalvik Cache

-Flashed Kernel 050

-Boot & Voilà, all working

Hope it helps!

I've done all of the above except for revert back to 050 kernel as I want to wait till Trip releases his new one that he left at the house earlier today. I do appreciate the help though

[Guest chalie78910]

link for kernel v050 kernel ? and bt funkions pairing ?

Edited October 3, 2011 by chalie78910

[Guest Chatastropher]

Just a question... Is there any chance that i by my self can change the camera to the HTC sense 3.5 camera?

[Guest xlostsmile]

whats new on 09B?

Edited October 3, 2011 by xlostsmile

[Guest yoogie]

whats new on 09B?

Man, read some pages back and you will see the changelog.

On your way you will notice that you will gain some "annoyances" along with 009B like no BT and no WLAN. Apart from that, the phone stays cooler. Cheerio

[Guest TripNRaVeR]

Need some smart people here;

What does the values listed below mean????? :blink:

0x54410021

[/code]




When you read this as hexa you get [b]1413546017 decimal





[/b]The next one:



[code]

0x5441001e

When you read this as hexa you get 1413546014 decimal

I'm pretty sure that i dont need those decimal values, i need almost for sure a much more "normal" number to come out. So do i need to convert decimal to something else or can anybode give me the proper output.

Edited October 3, 2011 by TripNRaVeR

[Guest farfromovin]

Just a question... Is there any chance that i by my self can change the camera to the HTC sense 3.5 camera?

ROTFLMFAO, nope sorry. Unfortunately Sense apps and widgets don't play nice with AOSP based roms.

[Guest yoogie]

Need some smart people here;

What does the values listed below mean????? :blink:

0x54410021

When you read this as hexa you get 1413546017 decimal The next one:

0x5441001e

When you read this as hexa you get 1413546014 decimal

I'm pretty sure that i dont need those decimal values, i need almost for sure a much more "normal" number to come out. So do i need to convert decimal to something else or can anybode give me the proper output.

What is this? Proximity values?? Is so, these seem to be hardcoded. What kind of "normalized" output do you expect?

[Guest TripNRaVeR]

Well i have 2 more, i know the outcome but i want to now how to get them

First:

0x10000000


MAGICBOX


result: 1024

[/code]






Second:



[code]

0x4000000


MAGICBOX


result: 64

How do they do it? 2 numbers again that needs to be converted:

0x48000000

[/code]




[code]

0x23800000

PLEASE anybody help! I cant see the connection?!?!?!?! :blink: :blink: :blink: :blink: :blink: :blink: :blink:

Edited October 3, 2011 by TripNRaVeR

[Guest Kaahru]

Well i have 2 more, i know the outcome but i want to now how to get them

First:

0x10000000


MAGICBOX


result: 1024

Second:

0x4000000


MAGICBOX


result: 64

How do they do it? 2 numbers again that needs to be converted:

0x48000000

0x23800000

PLEASE anybody help! I cant see the connection?!?!?!?! :blink: :blink: :blink: :blink: :blink: :blink: :blink:

On which context? I don't understand where those values come from!

[Guest TripNRaVeR]

On which context? I don't understand where those values come from!

RAM size

[Guest Tomsijs]

0x100000 = 1 MB

0x200000 = 2 MB

0x400000 = 4 MB

0x800000 = 8 MB

0x1000000 = 16 MB

0x2000000 = 32 MB

0x4000000 = 64 MB

0x8000000 = 128 MB

and keep doubling

Edited October 3, 2011 by Tomsijs

[Guest ags29]

The lack of a changelog in the op is really starting to get old.. :-\

[Guest Matury]

Trip, I gatta say that I been fallowing you since the beginning of MIUI and this is by far the best rom out there for Pyramid THANKS!

BUT, I found that this rom does not have MHL compatibility, anybody can also check this? in other words no HDMI out.

Anybody knows a work around?

And Thanks Trip for all your hard work!

[Guest TripNRaVeR]

0x100000 = 1 MB

0x200000 = 2 MB

0x400000 = 4 MB

0x800000 = 8 MB

0x1000000 = 16 MB

0x2000000 = 32 MB

0x4000000 = 64 MB

0x8000000 = 128 MB

and keep doubling

EXTREME!

Can you help me again, in the same context what do the values below mean:

0x40400000

0x48000000

0x70000000

0x80000000 == 128mb right?

0x24000000

0x40400100

With these values known i should be able to enable the following:

1x768

+

1x1024

OR

1x1024

OR

1x768

+

1x256

If anybody can fill in those values we are DAMN close B)

edit:

0x48000000 == 256 LOLZ B)

Edited October 3, 2011 by TripNRaVeR

[Guest ags29]

Now we know who are the real supporters, and who are the "less interesting people"

well if it wasnt for me THEN NO badword OTHER ROM THEN SENSE OR CM7 HAD AUDIO

badword YOU ALL YOU LITTLE PIECES OF s***, YOU NEED TO LEARN TO SHOW SOME RESPECT, BET YOU NEVER ARCHIEVED ANYTHING IN YOURE LIFE OTHERWISE YOU WOULD KNOW WHY I DONT WANT TO SEE RIPS AND THEN SAYING NO I DID IT MYSELF

this is for the losers, i know who are the true supporters so those people can just read on

After reading through the last few pages and several similar posts like this one from Trip, all I can say is..

..Wow O_o

This is just downright disrespectful to the rest of the community. I appreciate your hard work Trip, but comments like that are simply unnecessary and I would rather support and use the work of a more respectful dev. I also see ppl defending these type of comments by Trip? Seriously, wth?? Just because you support his Android development work doesn't mean you have to agree with the way he composes himself through comments like that. Grow up and stop blowing him. Good luck Trip.

Btw, I'm also glad to see I'm not the first person who noticed this and that several other users had something to say as well (on their way out).

[Guest Tomsijs]

EXTREME!

Can you help me again, in the same context what do the values below mean:

0x40400000 = 1028

0x48000000 = 1152

0x70000000 = =1792

0x80000000 == 128mb right? too many zeros :) = 2048

0x8000000=128 mb

0x24000000 =576 mb

0x40400100 = 1028.00024414062

With these values known i should be able to enable the following:

1x768

+

1x1024

OR

1x1024

OR

1x768

+

1x256

If anybody can fill in those values we are DAMN close B)

edit:

0x48000000 == 256 LOLZ B)

This is what I got.

In case You need exact number, just get the hex in decimal and covert here http://www.matisse.net/bitcalc/?input_amount=1&input_units=bits&notation=legacy

Edited October 3, 2011 by Tomsijs