Jump to content

Recommended Posts

Guest equiliym
Posted (edited)

you can also check one of the many sense threads to see what people tried so far and why they dropped this project

Edited by equiliym
Guest Maxsas360
Posted

Because porting a MDPI rom is a long process. As I know this would be the worlds first HDPI ARMv6 Sense ROM

Guest saransh9
Posted

Because porting a MDPI rom is a long process. As I know this would be the worlds first HDPI ARMv6 Sense ROM

As much I know blade and skate are the only hdpi arm6 devices

Guest Maxsas360
Posted

As much I know blade and skate are the only hdpi arm6 devices

There are alot of ARMv6 tablets in the wild.

Guest saransh9
Posted

There are alot of ARMv6 tablets in the wild.

oh yes i forgot abt tablets

Posted

Lovely General Discussion. I've got a Guy from XDA who has done sense ports to Nexus 1, S and Mont others. He will help

Guest FelixL
Posted

-Screen right way up

-RIL

-resize

-everything else

That's the list sorted by priority, if you ask me.

Posted

-Screen right way up

-RIL

-resize

-everything else

That's the list sorted by priority, if you ask me.

That is pretty much it there.

Guest tilal6991
Posted

Is the screen not already the right way up?

Posted

Ill do the screen today. When I have my allocated time on my ex PC ( now a shared one due to my sister blowing up her one ) so ill try editting the build prop.

Guest tilal6991
Posted

Right. I'll send you the fix for that later today then.

Posted

Right. I'll send you the fix for that later today then.

Okay, cheers mate :-)

Guest equiliym
Posted

Ill do the screen today. When I have my allocated time on my ex PC ( now a shared one due to my sister blowing up her one ) so ill try editting the build prop.

this thread has been on for 5 days and you still didnt have time to edit build.prop? doesnt sound like the project is going well imho..

check hwrotation, set wifi to wlan0 instead of tiwlan0, libril seems legit, set heapsize to 32 ie standards, dont complain how theres no bootanim since its debug.sf.nobootanimation=1.. you guys.. took me 20 seconds

Posted

So I was talking to someone who has done a HTC sense port before, Here was they're reply;

Hi,

You messaged me via YouTube regarding HTC Sense. Yes you may help. I will send you the link for dev thread

Depends on what version your going to use.

I sold my blade the day i sent the message but i will still try to help. (:

So forexample your as base using the wildfire s 2.3 rom with sense 2.1 then you head over to the desire s which has the exact same resolution and use the png's from that one. recompile the apk's and sign them correctly.

Logically should that work and save alot of time.

Oh Damn. Im using the HTC Salsa base biggrin.gif SO what device would i use? Its a Sense3.0 with Android2.3.3 i think.

Oh haha that one would work too. you need an arm6 based platform and files in hdpi format like from the desire s. the salsa runs android 2.3.3 and sense 2.1 doesn't it?

If i am right is sense 3.x and up locked tightly to arm7+ based hardware.

Me = RED

His Reply = Blue

So, if i can verify if this is correct? Then I can carry this port onwards

Guest saransh9
Posted

So I was talking to someone who has done a HTC sense port before, Here was they're reply;

Hi,

You messaged me via YouTube regarding HTC Sense. Yes you may help. I will send you the link for dev thread

Depends on what version your going to use.

I sold my blade the day i sent the message but i will still try to help. (:

So forexample your as base using the wildfire s 2.3 rom with sense 2.1 then you head over to the desire s which has the exact same resolution and use the png's from that one. recompile the apk's and sign them correctly.

Logically should that work and save alot of time.

Oh Damn. Im using the HTC Salsa base biggrin.gif SO what device would i use? Its a Sense3.0 with Android2.3.3 i think.

Oh haha that one would work too. you need an arm6 based platform and files in hdpi format like from the desire s. the salsa runs android 2.3.3 and sense 2.1 doesn't it?

If i am right is sense 3.x and up locked tightly to arm7+ based hardware.

Me = RED

His Reply = Blue

So, if i can verify if this is correct? Then I can carry this port onwards

it seems there is no device running sense 3.x with a arm 6 processor.even the explorer is arm 7

Posted

it seems there is no device running sense 3.x with a arm 6 processor.even the explorer is arm 7

Yea. Unless this isnt sense 3.0... It looks like it. But in the Build Prop it says 1.0, which i do not believe. FelixL or The_Crevis, What Sense Version is this??

Guest saransh9
Posted

Why don't u check what Android@Sam had done as he said he is using other phone and choose the best one

Posted

Why don't u check what Android@Sam had done as he said he is using other phone and choose the best one

This is Sense 2.1 + 3.0 Looks. If this port dowsnt work or Android@Sams is the answer, we will hijack it :P With permission obv.

Guest saransh9
Posted

This is Sense 2.1 + 3.0 Looks. If this port dowsnt work or Android@Sams is the answer, we will hijack it :P With permission obv.

+1

Posted (edited)

this thread has been on for 5 days and you still didnt have time to edit build.prop? doesnt sound like the project is going well imho..

check hwrotation, set wifi to wlan0 instead of tiwlan0, libril seems legit, set heapsize to 32 ie standards, dont complain how theres no bootanim since its debug.sf.nobootanimation=1.. you guys.. took me 20 seconds

Ive editted it. there is no hwrotation in the bp. Shall i add it beneath ro.sf.lcd_density=240?

Edited by weeo
Guest FelixL
Posted

I don't think it matters where in the build.prop you insert the line. The full name is: ro.sf.hardwarerotation

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.