Related
Hey Guys at first sorry for my english i'm not good in it. And I'm a Android newbie I just gained a bit exerience with my Touch Diamond but it's broken now..okay but that's not the probleme....
If got a question:
After about 2 days of searching for an android 2.0 or 2.1 ROM I was a little bit confused of the diffrent news everybody was talking about. I'm root on my Hero. That was the first an last thing I made with my device.
1. Everybody is gonna talk about MoDaCo 3.0 but when I was trying to download his ROM my browser never got a request. Is the site down, where that ROM is hosted ?? Could someone give me a working link with this ROM ??
2. Is there a ROM with Android 2.0 or 2.1 outside or even not ??? And if yes are they working well ???
Would be nice if someone can help me =) thanks a lot.
Please answer soon if you know something about that =)
Greetz BassdoxXx
you can get modaco's roms at his website, www.modaco.com.
in the android development section there are some 2.0/1 roms, none of them works flawless, see for yourself if it fits your needs.
Thanks a lot for your fast answer. =)
The problem that i couldn't open the modaco page was my isp -.- i downloaded it at school
BassdoxXx said:
Thanks a lot for your fast answer. =)
The problem that i couldn't open the modaco page was my isp -.- i downloaded it at school
Click to expand...
Click to collapse
What? Does ISP's block that site? Lol, would never happened in Norway
there is a few 2.0+ roms out there for the hero.
most seem to be very usable now.
best sense ui would be lox/behnaam community release on 1.6.
http://htcpedia.com/forum/showthread.php?t=1448
there are two aosp roms worth looking at.
lox aosp ( im using that on a daily basis)
http://htcpedia.com/forum/showthread.php?t=1416
jnwhiteh aosp
http://htcpedia.com/forum/showthread.php?t=1528
Hello all,
I am having very specific request when it comes to choosing a proper rom for install on to my hero.
I am blind. Stock roms are only running Android 1.5. More robust accessibility features are available starting with Android 1.6 and improving even more with Android 2.0.
So for sure I am forced to upgrade my hand set.
There are various roms, some of their authors have even disable google specific features so I know I can't install such a rom.
All the accessibility efforts are being lead by the google developers.
Most likely these accessibility tools won't be usefull to most of you but please can anyone recommend me a rom where market is working and where the following applications can be installed and used?
- eyesfree suite of applications,
- talkback - the google screen reader for android,
- tts service.
All possible help is already appreciated.
sorry for the double posting. I've accidentally posted twice and I am unable to remove the post.
Hope anybody can help me please.
pvdeejay said:
Hello all,
I am having very specific request when it comes to choosing a proper rom for install on to my hero.
I am blind. Stock roms are only running Android 1.5. More robust accessibility features are available starting with Android 1.6 and improving even more with Android 2.0.
So for sure I am forced to upgrade my hand set.
There are various roms, some of their authors have even disable google specific features so I know I can't install such a rom.
All the accessibility efforts are being lead by the google developers.
Most likely these accessibility tools won't be usefull to most of you but please can anyone recommend me a rom where market is working and where the following applications can be installed and used?
- eyesfree suite of applications,
- talkback - the google screen reader for android,
- tts service.
All possible help is already appreciated.
Click to expand...
Click to collapse
i am on mcr3.0, i looked in the market, i can find 8 apps for eyesfree, tts is one of these. i didn't try to install one of these, but usually it works. the search for talkback returned nothing.
not that i want to be rude, but wouldn't you be better off with another phone if you are blind? i can not imagine a touchscreen only phone would be suitable for someone who is not able to see... especially because there are great devices out there that have a full qwerty keyboard, and come with android 2.0 out of the box... imho this would be a better solution.
again, the last thing i want to be is rude, but maybe this was your mistake: you posted in the htc hero section of this forum, the hero is a touch screen only device, including a virtual keyboard on the screen. it has only six buttons and a trackball, and two rocker buttons for the volume. just to make clear we are talking about the same device
if you are still up for the hero you could try the 2.1 rom from here: http://htcpedia.com/forum/showthread.php?p=30418&posted=1#post30418
best you try for yourself, it has some drawbacks, but maybe in areas you don't need (afaik syncing with exchange does not work for example, which wouldn't be a problem for me...). otherwise it might be worth to wait another week or two, we all are waiting unpatiently for the official eclair release from htc
keep asking if you need to know more, but maybe open a new thread, since your problems are very specific, and might drown between all the newbies question about "how to root my phone".
Hello,
Thanks for your reply and a great attitude.
Yes it may sound strange I have really got HTC Hero here. I know I'll be having problems with virtual keyboard but also I am afraid accessibility features of Android phones are not really such mastered one can use it daily. For example reading emails and content from the web browser is not yet possible. I just want to try how things work and I would also like to touch the virtual keyboard. If I can memorize computer keyboard and use it daily, typewriter keyboard, nokia mobile phone keyboard, then perhaps I might be able to make some use of this too.
I am sory but here are some more questions:
I haven't yet verified with some sighted friends but... is it possible my hero is running even older version of android like Android 1.5? I've based the assumption that it's most likelly running 1.5 because majority of the devices I was reading on the net are running it.
You've been triyng to locate eyes-free applications on the market but you were unable to find talkback. Are you sure you are running newer version of Android than 1.5?
Talkback is supposed to be installed with Android 1.6 andd 2.0 by default and you should be able to find it in the accessibility menu of your phone. I am not sure how well this applies to the custom roms.
Talkback requires google's accessibility api which is reported to be available on Android 1.6 upwards.
To tell you the full story first I've asked on the eyes-free google group whether some accessibility experts from there can help me but no one knowledgeable enough has replied to my query, so I'm trying my luck here then.
Oh I am really excited since I've got really well formed informative reply.
Thanks again
Edit:
Also, I've seen somewhere in the forums here this leaked HTC rom does not support the market. Has this been rectified already? You know if market does not work then most likelly I won't be able to install these applications I am tallking about.
Also you are mentioning possibility to wait a few weeks until HTC guys role out the official update for Hero. Wouldn't that break chances I will be able to root my device later?
Edit2:
Ooops, I should read better next time. Market works on this rom. The problem is paid apps can't be installed which is hopefully not a big issue for me since most of the accessibility enabled applications are free.
Which of the downloads from Hero 21 do I need?
63.18.55.06JU_6.35.09.26) or No Wipe Download. I will need a wipe I am sure but since this link says nowipe I am ehmmm. confused.
pvdeejay,
Unfortunately there is not an 'official' update for Android 1.6, 2.0 or 2.1 as of yet. There are rumours of one coming out soon, but nothing cast-iron yet.
You are correct in that the Hero runs 1.5. It does say it under Settings | About Phone (bottom item on list)| Firmware Version (bottom on list again), although without a working screen reader, there is probably little use in knowing how to find that.
If you did want to upgrade, I'm sure plenty of people could help find a ROM that would suit. The only issue with that is that you would need a rooted phone with a custom recovery image installed. Unfortunately, a lot of the procedures would not be easy for you, as the software that you might need to use to go through the procedure is probably not designed that well for accessibility tools. I don't know what kind of software you are using, but some of the instructions for making goldcards are quite complex, and involve editing some numbers in a 'table' which could be quite difficult for you, I would imagine.
I'm sure a friend would be able to help you out with making a goldcard/rooting if you did want to install a custom ROM (you'll probably be waiting a while otherwise ). They could even root their phone while doing yours (just share the goldcard between the devices).
Nonetheless, there is probably a ROM out there with little removed from it. I'll have a look just now, but you would need to have your phone rooted to do anything just now.
When it comes to rooting and installing custom recovery image. Do you thing the following instructions might work for me?
These instructions don't require a gold card:
- How to Root HTC Hero and Install Amon Ra Recovery Image
- How to install a custom rom on a HTC Hero
Hello,
Here are some numbers I've asked my friend to read from system -> about screen. The phone interface is in czech so I am unable to get some names translated to english, but I believe some of the geeks will understand these identifiers and might be able to help me what is best:
Code:
firmware: 1,5
63.118.55.O6U|6.35.04.25
2.6.27-a5504199
Build number: 1.76.405.6 146733 CL# 47214 release-keys
Software version: 1.0.0.A6288
pvdeejay,
to sum it up:
the hero definitly runs on android 1.5. there are no roms for older android versions, and a few homebrewn for newer versions, as we said already.
i searched for talkbalk on my 1.5 rom, so it is obvious that i couldn't find it...
about rooting of newer roms: it is just a matter of time, sooner or later there will be always methods of rooting a rom. what i meant by waiting is: wait until the official update is out, then wait a few more hours until the first rooted and customized rom is out
@pvdeejay,
I would have to agree with kendong2 that waiting for the official ROM is probably the best idea for you at the moment. There are no guarantees that an unofficial ROM would help, and it would be another user interface to try and learn.
@kendon,
I noticed he has the original, easily rooted version of the hero. IIRC, that is what I had on my G2 (and had the security unlocked bootloader out the box). If that's the case, would pvdeejay be able to 'fastboot boot' a full system img file for the purposes of testing it out to see if it meets the requirements.
The reason I ask is that I've only ever fastbooted my AmonRA recovery (I didn't flash it, because I never felt any need to). I'm guessing you could fastboot a full img, but I'm not sure about the practical issues of where it would be stored in memory...
Sorry guys originally I believed I am slowly getting into the matter and am begining to understand how flashing / rooting / upgrading home brew firmwares works on these phones.
After these 2 posts I feel like a total noob again.
Now again some very concrete questions:
What about these 2 guides I've posted links to?
Can I somehow got [Recovery] [13-Dec-2009] RA-hero-v1.5.2 installed so I will be able to do nandroid backup and then possibly flash some new roms?
Can I really brick my phone by trying to install amon ra?
Originally I thought the process works as follows:
1) get the custom recovery image installed (that's the amon ra in this case),
2) do a nandroid backup which will dump everything usefull on to the memory card,
3) backup and reformat the card,
4) download a rom, rename it to update.zip, put it onto the root folder of the cart, reboot the hero in recovery mode, do the wipe of the data partition, and run update,
5) reboot again and believe it's good.
Also some very significant bit is the thing you are all calling the radio. I am afraid I've not identified this bit thus it's missing in this summary.
Which files will I need to download if I decide to try Android 2.1 community edition 1.8? Are these files I've copied links to a few posts earlier both needed?
Can you please check this list, identify the things I am missing, and make suggestions and corrections why this may not work on my device based off of those number I tried to put down here?
Even if I won't be able to do this right now I'd be happy to get corrections as I can learn something new.
Of course I won't be doing all this on my own. I will ask my bro to read all the stuff to me and we'll do it according to your advices.
To give some bits about me and my computer skills, I believe I am a Windows power user, Basically I do also understand unix, I know what's bash how the files are arranged in a file system, can use command-line tools, telnet, ssh. I am working as a network administrator here so some background is there really.
Hi pvdeejay,
Answers to your questions here.
You can actually use fastboot to 'temporarily' load up the AmonRA recovery image into memory and run it from there. I do that on my phone, for the simple reason that I can't be bothered ) ) to flash the recovery. Once you get AmonRA running, the first thing you should do is make a Nandroid backup. It will be saved to your SD card, so then get the nandroid directory of your card and save it to your PC (just in case!)
So, here's how you'd go about this.
(Make sure you have the android sdk installed, and that adb and fastboot commands are working). USB cable should be plugged in throughout.
Before you begin, put the ROM you want (ie. Android 2.1 community edition 1.8) into the root of the microSD card (a .zip file).
Code:
adb devices
Should list your phone's serial number
Now turn off the phone, and turn it on with the back key held down (the one at the very bottom right of the device).
You should enter fastboot mode. Now type
Code:
fastboot devices
and you should see the serial number again.
Now type
Code:
fastboot boot AmonRA.img
where AmonRA.img is a file in your present working directory that is the filename of the latest custom recovery image. This does NOT flash your phone, it merely runs the image (pretty much as close as you get to risk free, other than sitting there with a tinfoil hat on )
See screenshot of the recovery image here:
http://www.sizzledcore.com/wp-content/uploads/2009/12/RA-hero-recovery-image-500x375.jpg
Make the Nandroid backup by choosing 'Nandroid Vx.x Backup' and waiting a while.
If your ROM needs a wipe first (most new ones do), select Wipe data/factory reset. You will lose all your user data on the device (but you've got a nandroid backup just in case)
You're now good to go. So choose "Apply sdcard:choose zip"
Now select the custom ROM zip file you downloaded. It doesn't even need to be called update.zip! Choose it from the list and push trackball.
Wait for the update.zip to go in. Do NOT turn off the device or pull the battery. First boot can take a very long time (upto 30 minutes). Just keep it plugged in via USB and wait...
As for radios, see http://android.modaco.com/content/h...-24-11-hero-roms-radios-in-update-zip-format/ and look at the section titled radios. The latest one is in bold. It is a .zip file as well, that you use these exact same instructions for to install (don't do the wipe or anything like that. Just install the .zip file)
anon2122 said:
@kendon,
I noticed he has the original, easily rooted version of the hero. IIRC, that is what I had on my G2 (and had the security unlocked bootloader out the box). If that's the case, would pvdeejay be able to 'fastboot boot' a full system img file for the purposes of testing it out to see if it meets the requirements.
The reason I ask is that I've only ever fastbooted my AmonRA recovery (I didn't flash it, because I never felt any need to). I'm guessing you could fastboot a full img, but I'm not sure about the practical issues of where it would be stored in memory...
Click to expand...
Click to collapse
this is correct so far, i did the same, except i installed the recovery. i play a lot with my phone, the installed recovery image with the nandroid backup is the best i have ever seen for a phone...
@pvdeejay
you always write so much...
i try to answer everything:
the two guides you posted are good for your situation. i never tried flashrec, but from what i read it is safe to use. i installed my recovery image through fastboot, the guide is here: http://android.modaco.com/content/h...ng-the-patched-recovery-image-on-your-device/
i have no idea how this works out for you, but my honest suggestion would be that you have someone seeing assisting you, you CAN brick your phone, though it is not likely if you follow the instructions precisely. the process is not very time consuming at all, so you don't need to bother anyone for days of their time.
edit: and now i read your post to the end and saw that your brother will be helping you, so you are on the right track
once you have the recovery installed you can make nandroid backups, and i would suggest that you do this first thing after installing the recovery, better make a backup too much than one too less...
the 5 steps you described are correct, except there is no need to rename the zipfile anymore, you can select any .zip from your sdcard.
the radio part is the number that begins with 63.18.55.06, then comes two letters and then more numbers. as by now the version can be identified by the letters, with JU being the up-to-date one. in general you can say the newer the better, but you have to try for yourself. start with the newest one, if you have problems go back.
thanks this seems to be pretty doable plus I will easily be able to restore the current data backed using nandroid backup.
Which android SDK do I need the latest one?
The commands I need to type are supposed to be typed on the PC or on the phone? I assume on the PC but I just would like to ensure.
Hero21 1.8 community edition has a recommended radio listed in the first post. Is it necessary to install that one as well? What should I install first the actual rom or the radio? Do I need installing radio at all? Should i do the same with radio i.e. renaming it to update.zip and using amonra to install it?
Also will I be able to use this method even if I install another rom (running amonra without actually flashing it)?
Edit:
sorry guys did not realize renaming to update.zip is no longer needed.
Edit2:
is there an easy way on how to access sd card from windows? I can't just remove the card from phone and insert it into my laptop because I don't have the proper adapter. Previously my boss was using the hero and perhaps it would be nice to backup the sd card first.
Edit3:
uhmmm, installing android sdk is perhaps not as simple as it sounds.
I have just seen this article.
I am on a limited gprs internet connection, can you please suggest sdk features I won't need to save some download bandwith?
- you need only the adb binary (thats adb.exe for windows) from the sdk, the rest is not needed for this.
- install the radio from the 2.1community-rom-thread, it is the newest. install the radio first. DO NOT PULL THE BATTERY until the phone has rebooted completely. if you pull the battery during radio upgrade your phone will be dead. it takes a few minutes, do not panic!
- you can copy the contents of the sdcard via the usb-cable, plug it into your pc and pull down the notification bar...
Do I need to run SDK Setup.exe when I have downloaded android sdk for windows?
Or can I simply run that binary from the command-line without the installation?
Do I need any USB drivers so my phone can be recognized?
I want to take the cardock.apk from one ROM and use it on another. Both are 2.1 flavors, so I thought it would be as easy as taking the apk from one and pushing it to another. It worked for a little while but then it stopped working. I got an error about permissions. When I ran fix_permissions, it disapeared.
lil help?
rudeguy said:
I want to take the cardock.apk from one ROM and use it on another. Both are 2.1 flavors, so I thought it would be as easy as taking the apk from one and pushing it to another. It worked for a little while but then it stopped working. I got an error about permissions. When I ran fix_permissions, it disapeared.
lil help?
Click to expand...
Click to collapse
I would suggest taking the rom with the cardock.apk and running it in android rom kitchen . You can find a video at TheUnlockr showing you how to set it up and create your own rom. What you'll want to do in essence is un-compiled that rom and remove the apk and drop it into the rom you want (which will also be un-compiled ) once thats done just recompile the new rom with your apk in it and sign it, and flash it too your phone. Of course make sure you Nand backup first just incase something doesnt go right.
hi
as the Title says... don't do it...
i've done it... now black Screen...
But no change to edit it back with droidexplorer or adb shell...
file is emtpy...
i'm running with Froyostone V1 maybe someone can send me the build.prop file of this build...
i don't want to restart from scratch...
thx
futureshock said:
hi
as the Title says... don't do it...
i've done it... now black Screen...
But no change to edit it back with droidexplorer or adb shell...
file is emtpy...
i'm running with Froyostone V1 maybe someone can send me the build.prop file of this build...
i don't want to restart from scratch...
thx
Click to expand...
Click to collapse
The quickest way would be to load up another clean version changing the original to froyo boot it up & go to astro copy the build from system to SD or to the froyo version & restart then delete new version and paste the build into the original froyo & reboot
so i got my froyostone back to working
have pulled the build.prop from my shubcraft build... and pushed it to the froyostone build!!
hopefully the trick will work without that problem on my hopefully soon arriving android tablet
Next time, try backing up the android folder on ur SD card before changing anything.. that way a quick format and a trip to ur computer will get ur phone working again..
Sent from my HTC HD2 using XDA App
futureshock said:
so i got my froyostone back to working
have pulled the build.prop from my shubcraft build... and pushed it to the froyostone build!!
hopefully the trick will work without that problem on my hopefully soon arriving android tablet
Click to expand...
Click to collapse
Can you share this file here? i got the same problem that many applications can't work with full screen, and i didn't backup this file...
thx~
Sorry for my Englisch.
Problems with the screen in fullscreen games.It is easy to change it.
Open the file with a text editor Build.Prop and edit the line of "ro.sf.lcd_density = 220" to "ro.sf.lcd_density = 240"
Followed the instructions and did this mod.
I sorta of like it. Didn't encounter any problems at all. It's hard to tell the difference. Some apps will support it, Sense UI does not.
The bigger question is. Does this impact battery life. I am still testing this..so right now that's debatable.
I set dpi to 192 and love it. Most apps show more info on screen, a few games are not clever enough.
After using WinMo for 2 years, I'm used to high precision "touching" :-D
A tip: download Spare Parts and use it to turn off compatibility mode.
i just read http://forum.xda-developers.com/showthread.php?t=765639
will it work with our hd2
vua777 said:
i just read http://forum.xda-developers.com/showthread.php?t=765639
will it work with our hd2
Click to expand...
Click to collapse
Not exactly.
The app works but doesn't really make any difference to build.prop file nor does reboot the device.
Your can manually make the changes.
I set it to 200 and I use adw launcher to make usage of the extra space.
Black screen from changing build.prop
So i really wish I found this thread before i tried to change anything. So i also have the black screen when loading android after changing build.prop file, I did copy the file before I changed it. Now i just dont know how to get into the system folder to change it back because when i load android its all black. Can anybody help me here?
NOTE: This is a thread for the build devs.
Users who want to try this solution themselves should head over to TheAgent1982's thread: RTL Support Project, or go to the Hebrew guide at htcaddicts.com.
Update: Hey devs. Just so you'd know, we're even willing to do the framework.jar patching for you!
All we ask from you is to deodex your builds, and include the patched framework.jar (which appears to be almost the same for all builds, barring sense/non-sense differences).
PM if you're willing to let us help
Hey devs
First of all, thanks to all the devs who are doing a great work with everything!
There's one thing though that's a pox on all Android builds (even native android devices), and that is full-on right-to-left support. What do I mean?
Sure, there are Hebrew (and I assume Arabic) fonts in Android, and MOST applications work just fine, with the notable exceptions of Gmail, Google maps, and most native Google-apps, who all display Hebrew backwards.
A far more stressing issue, however, is that ALL android applications without exception display numbers backwards in right-to-left texts (so 10 becomes 01, 12 becomes 21, etc. It can get really confusing really fast).
Any way, there exists a solution for both these problems that can USUALLY be fixed with a medium amount of experience on native Android devices, but requires a bit of a hassle for HD2 owners.
Hopefully, you devs can incorporate this fix to future releases, once the fixed files are obtained it shouldn't be too hard to spread in the future.
Here's the process:
BTW, This only works on completely deodexed builds!
First, you have to download this zip file. It basically contains the fixed files and some other stuff you devs probably won't need.
The fix then involves extracting 'framework.jar' from the phone, and extracting the 'classes' file thusly:
Code:
java -jar baksmali-1.2.2.jar -o classes classes.dex
Then, in the subsequently created "classes" folder, you need to replace the files in "/classes/android/graphics/" and "classes/android/text" with the relevant files in the aforementioned zip file (from the corresponding folders, of course, under "files/froyo/")
After that is done, you need to re-create 'classes.dex' using:
Code:
java -Xmx512M -jar smali-1.2.2.jar classes -o classes_new.dex
Then, replace the old 'classes.dex' in 'framework.jar' with the new one (after renaming it back to 'classes.dex', of course), and push the new and fixed 'framework.jar' back to the phone.
Reboot, and voila: full-on Left-to-Right support!
I'm sure you devs have far better ways of including these fixed files without having to edit the entire thing every time, but what would I know?
We would be extremely appreciative to all you builds devs if you could incorporate those fixed 'classes' files in future builds, it'll save us a ton of work.
Also, if any of you guys also need volunteers for beta-testing this solution (as I'm sure you don't have Hebrew content to test it with), feel free to PM me.
Thank you for listening, and keep up the great work!
((PS, thanks to member silverbluem who helped simplify the process))
+1
i use the htc sense to read sms so
the msg wont appear word4 word3 word2 word1
+1 for that. although i am using bifbif ver 1.2 with CM6 and its OK here.
i've test it on Mdj Evolution 2.3 and it work perfect:
i never copied the files to /graphic only to /text folder
to put the Framework.jar in the device because we dont have recovery mode
use this commands:
to pull the file:
adb pull system/framework/framework.jar
install the attached files
adb push (your file location/framework.jar) system/framework/framework.jar
after putting the file restart the device
restart might take 5-10 min first run after applying the file
thanks
silverbluem said:
i've test it on Mdj Evolution 2.3 and it work perfect:
i never copied the files to /graphic only to /text folder
to put the Framework.jar in the device because we dont have recovery mode
use this commands:
to pull the file:
adb pull system/framework/framework.jar
install the attached files
adb push (your file location/framework.jar) system/framework/framework.jar
after putting the file restart the device
restart might take 5-10 min first run after applying the file
thanks
Click to expand...
Click to collapse
This sure does absolve us of needing to use Linux and needing all that messy system.ext2 stuff. I'll give it a try.
Still, it'd be nice to have these updated files already incorporated into future builds.
Ambious said:
This sure does absolve us of needing to use Linux and needing all that messy system.ext2 stuff. I'll give it a try.
Still, it'd be nice to have these updated files already incorporated into future builds.
Click to expand...
Click to collapse
still need to figure out how to replace the graphic file
cause the view is not perfect without it...
Ambious said:
Edit: I tried this method, and while it DID boot, the solution didn't work - numbers still backwards, Google applications still reverse.
Click to expand...
Click to collapse
what rom are you using?
EDIT: the only thing that need to change to you is the phone book is now need to be RTL and the number backwards
Gmail need the Graphic file
silverbluem said:
what rom are you using?
EDIT: the only thing that need to change to you is the phone book is now need to be RTL and the number backwards
Gmail need the Graphic file
Click to expand...
Click to collapse
My WM rom is OzDROID2.0, my Android rom is MDJ FroyoHD 3.7
Well, the phone book was never a problem for me, only hybrid text/numbers like in text messages etc.
Anyway, turns out I didn't modify framework.jar correctly, so I tried again using the script, and this time the phone just won't boot (like when I used Linux, it just hangs at boot screen).
Edit: Tried all day, all combinations of 'texts' files and with or w/o the 'graphics' file, and it always either just didn't fix anything (when I did the fix manually), or didn't boot at all (when I tried the script). This got me to conclude that I must not be doing it right, or else it would fail to boot for me as well (at least, I'm not even considering me being able to totally fix it myself )
Not a week ago, i was referred to the Samsung Galaxy S's newest ROM which came from Orange..
The rom includes (to my understanding) all the latest fixes regarding left to right text and even a hebrew version of Swype
It is easily retrievable. Obviously, it isn't legal to extract their work and use it to manutfacture a widespread ROM... but you can use it for personal use if you want to check how to fix that annoying hebrew thing.
+1000
Thanks
nir36 said:
Not a week ago, i was referred to the Samsung Galaxy S's newest ROM which came from Orange..
The rom includes (to my understanding) all the latest fixes regarding left to right text and even a hebrew version of Swype
It is easily retrievable. Obviously, it isn't legal to extract their work and use it to manutfacture a widespread ROM... but you can use it for personal use if you want to check how to fix that annoying hebrew thing.
Click to expand...
Click to collapse
It COULD be used to reverse engineer some of the stuff, but I doubt it's similar enough to the HD2 builds to use it.
+1
Thanks
Hebrew RTL Support
For those who are asking, i have made a working framework.jar , time ago.
It is working for most FROYO Sence, CM6.+ does not need it...
BUT NOT Desire HD Sence ( Because is is odex files, not only *.jar).
If needed i will upload it, and put a tutorial how to make it work...
Good Day!
RTL HEbrew
Please do that !
Thanks
Framework.jar
Tomorrow i will post the file with short tut how to put it, i must say that Ambious bring a good tut directly from iAndroid
Any way, Ambious, if i will upload the file please stick it to 1st page.
For now, good night...
This fix is a must for all RTL language users.
As mentioned, CM6+ already includes the fix and is working pretty good!
Problem is, for some reason, CM6 builds are rare...
I tried a few Sense builds but eventually i came back to a CM6 based build
because of it's support for RTL languages.
Devs, please include this fix in you builds, to make them as much accessible
as possible.
Thanks.
TheAgent1982 said:
Tomorrow i will post the file with short tut how to put it, i must say that Ambious bring a good tut directly from iAndroid
Any way, Ambious, if i will upload the file please stick it to 1st page.
For now, good night...
Click to expand...
Click to collapse
I sure will!
Thank you
However, as a Sense user myself, I'm pretty anxious to see if a fix can be applied to any of the Sense builds (especially DesireHD, which is my current build).
Well Organized Post
I have made well organized post for it:
RTL Support Post.
I must say, it will NOT Work for Desire HD for now, because it is ODEX and jar combined, and as you have read at iAndroid, for now there is NO solution for it,
and i do not have the experience and time to learn and convert it, since i am a student.
But i will give it a try between the semesters...
Hey,
The HD2 Desire HD builds are fully deodexed.
Froyo HD 3.7 for example: http://forum.xda-developers.com/showthread.php?t=795914
Maybe you could use them for preparing a RTL fix for when the deodexed desire HD ROMS come and for us HD2 android users.
Cheers.
It may be my semi-n00bness, but all my attempts to create a fix for DesireHD 3.7 failed.
Also, trying the supplied fix in the thread above on MDJ Sense Clean (non HD based) failed, wouldn't boot.
Hopefully someone can get it to work, and better yet - that the devs will incorporate those fixes in their builds.
Hi Everyone,
I am in need to know how to change the default homepage of litening rom as it gos to the very first page when i push the home button.
I would like to go to the middle page when i push it which requires i edit a line somewhere and put the number 3 in it.
Could anyone help me and the many others who dont know.
Thank you.
rom of Cognition provide this function base on official launcher, but i prefer 3rd party launchers such as adw launcher, zeam launcher and etc. all of which are configable.
Me too
Hey guys,
I wan't another screen to be default, so brought if I press the home button, too. I managed to change it on stock Samsung ROM with this method
http://forum.xda-developers.com/showthread.php?t=1096521
however there is no default.prop in system directory in Litening ROM! (I use 1.5).
So i wrote this ro.csc.homescreen.defaultscreen=4 into the "build.prop" file of the system folder -> does not work :'(
Then I have written it to the "default.prop" file in the / folder (so nothing ) -> does not work either : Seems to be that the Litening ROM overwrites this file every restart!
Please someone help me
I am in the exact same boat as you now. It does get annoying always going to the first page.
So not 1 person knows how to change it?
Easy way is to use Launcherpro, you an choose the amount of screens and which to use as default.
Put the below string in default.prop file. Replace 3 with whichever
screen as default.
ro.csc.homescreen.defaultscreen=3
This will set the homescreen at start up, but not working on pressing home screen button.
Sent from my GT-I9100 using XDA Premium App
kirdroid said:
Put the below string in default.prop file. Replace 3 with whichever
screen as default.
ro.csc.homescreen.defaultscreen=3
This will set the homescreen at start up, but not working on pressing home screen button.
Sent from my GT-I9100 using XDA Premium App
Click to expand...
Click to collapse
I dont get why it doesnt work when you press the homescreen button? LiteRom definately needs the feature to allow you to change it.
WhiteXR said:
I dont get why it doesnt work when you press the homescreen button? LiteRom definately needs the feature to allow you to change it.
Click to expand...
Click to collapse
This feature does not depend of LiteRom(only if he finds a way to modify the rom somehow)
This file witch we were modifying up to now is missing in the latest rom's so another way must be found.
Maybe somebody with more skills can help us of corse the suggestions of changing the launcher are not solving our problem.
we need solutions for touchwiz.
this makes me sad
I am very new to android and rooting and roms, etc. I finally figured out how to flash a rom so i decided to go with lightening 6.1. Its really frustrating when small things like these don't work.
I really hope someone can come up with a fix. I've also noticed that adfree android app also doesn't work with this rom and thats such a bummer. I dont want to go back to my stock rom...
chmsalman said:
I am very new to android and rooting and roms, etc. I finally figured out how to flash a rom so i decided to go with lightening 6.1. Its really frustrating when small things like these don't work.
I really hope someone can come up with a fix. I've also noticed that adfree android app also doesn't work with this rom and thats such a bummer. I dont want to go back to my stock rom...
Click to expand...
Click to collapse
and just what is it that doesnt work for you?
i tried litening 6 then cyanogen and returned running to litening 6.1 i should had never left it lol
Everything works ok for me.