In case you missed this from the Opera 9.5 Build 1957 thread, build 2392 is available from the link below.
http://forum.xda-developers.com/showthread.php?t=401643
This one has the zoom button in the lower left, which I've found is a bit annoying using the VGA buttons on 96 dpi - a lot of screen area is taken up by the two buttons (zoom and the menu button on the lower right). I might try the QVGA buttons to see if that works better, but then I'll loose easy non-stylus access. The zoom function itself is VERY nice, much better than the double-tap with a fixed zoom setting.
This one feels very stable, it hasn't crashed on me, unlike 1957 which crashed all the time even with few tabs and a low cache.
Unfortunately, the screen orientation problem is back and the can't-use-the-keyboard-to-enter-a-web-address problem is also back (both were fixed on 1957 and have been problems since 1409).
Some people are reporting success with Flash Lite 3.1 and this build, but I'm on AP4 and still can't get Flash to run. Some think its due to the older Flash Lite 2.1 being cooked in.
However, the advangates so far are better than the 2 problems, so I'm going to keep this one for now.
1184 is still the best version. 2392 has too many problem still.
Funny that the more they 'improve', the worst it becomes.
edit: sorry, I got mixed up between 2392 and another version.
Yes, I have to agree that this version is really good. Better than 1184.
this build is really good, better than 1957 and 2123, I use portrait mode all the time,so opera switching to portrait mode on exit doesn't bother me, plus i can't tell the last time i used the hardware keyboard to type, so the address thing don't bother me at all. i use TouchPal as my keyboard all the way. this is well improved, even though there's a lot left to be done, its still a good build.
Also, flash3.1 works with this build on Michyprima's rom, the thing is flash3.1 has to be installed first then opera after, soft reset and it's good to go.
1957 v. wins
For me 1957 version is the best. Before, I used 1184, but since 1957 was released, I am on this version and I like it.
1. It works with no crushes, at least for me.
2. Flash 3.1 works for YouTube(original x7510 rom).
3. No problems with keyboard and screen rotation.
4. Zoom works not only by double-click, but also with zoom scale in top right corner, which appears if you slide your finger there. More, text wrap works as well with this zoom.
Tadeusz said:
For me 1957 version is the best. Before, I used 1184, but since 1957 was released, I am on this version and I like it.
1. It works with no crushes, at least for me.
2. Flash 3.1 works for YouTube(original x7510 rom).
3. No problems with keyboard and screen rotation.
4. Zoom works not only by double-click, but also with zoom scale in top right corner, which appears if you slide your finger there. More, text wrap works as well with this zoom.
Click to expand...
Click to collapse
Can you point me to where your 1957 comes from? My 1957 does not have the zoom at the top right corner.
It also no longer gives me the ability to activate links in zoom out mode. In addition, the text overlaps unless small fonts are used (I use medium size font so 1957 version can't support that correctly). The display is also blurrly in zoom out mode.
I was confused and mistakenly believe this was another version that I've tried.
Yes, I have to agree that this version is the best ever version to date.
- Tengo types smoothly, unlike most versions where Tengo behaves wierdly.
- display at all zoom level are clear, unlike many versions, where displays are distorted at zoom out mode.
- texts flow correctly, or rather reflow correctly. Unlike some versions, where reflow does not take place at all.
- able to change minimum overview zoom to 85 so that links could be activated without zoom in.
- variable zoom bar works flawlessly.
- Connection is quick with minimal pause
- youtube works nicely.
- pictures are sized correctly, unlike some versions where the pictures are oversized.
The screen orientation issue has never bothered me.
Keyboard pop up issue is only a minor annoyance.
Only issu so far is that it is unable to download files. The usual download bar does not appear, so download seems to be happening in the background. Also, only part of the file is downloaded. Any idea?
eaglesteve said:
I was confused and mistakenly believe this was another version that I've tried.
Yes, I have to agree that this version is the best ever version to date.
- Tengo types smoothly, unlike most versions where Tengo behaves wierdly.
- display at all zoom level are clear, unlike many versions, where displays are distorted at zoom out mode.
- texts flow correctly, or rather reflow correctly. Unlike some versions, where reflow does not take place at all.
- able to change minimum overview zoom to 85 so that links could be activated without zoom in.
- variable zoom bar works flawlessly.
- Connection is quick with minimal pause
- youtube works nicely.
- pictures are sized correctly, unlike some versions where the pictures are oversized.
The screen orientation issue has never bothered me.
Keyboard pop up issue is only a minor annoyance.
Only issu so far is that it is unable to download files. The usual download bar does not appear, so download seems to be happening in the background. Also, only part of the file is downloaded. Any idea?
Click to expand...
Click to collapse
I would guess you're talking about build 2392, Downloads show up in the downloads manager, I've been downloading with it all morning so I know.
In config I also set image to 4 instead of the default 3, this seems to give better image clarity.
I also set update delay to 0 instread of the default 2000.
I also set tabs to 8, I don't need any more tabs than that at any 1 time
those are a couple of my default tweaks when I install.
lennie said:
I would guess you're talking about build 2392, Downloads show up in the downloads manager, I've been downloading with it all morning so I know.
In config I also set image to 4 instead of the default 3, this seems to give better image clarity.
I also set update delay to 0 instread of the default 2000.
I also set tabs to 8, I don't need any more tabs than that at any 1 time
those are a couple of my default tweaks when I install.
Click to expand...
Click to collapse
Yes, was talking about 2392.
My download manager definitely does not appear. Tried it so many times already. The files does get downloaded though, even if not always completed. Did you perform any tweak to make this happen because I can't get it to appear.
I can't seem to detect any differece after setting image to 4. Do you can a website that illustrates its impact?
Do you mean INITIAL update delay? I'm still trying to figure out what difference this would make.
eaglesteve said:
Yes, was talking about 2392.
My download manager definitely does not appear. Tried it so many times already. The files does get downloaded though, even if not always completed. Did you perform any tweak to make this happen because I can't get it to appear.
I can't seem to detect any differece after setting image to 4. Do you can a website that illustrates its impact?
Do you mean INITIAL update delay? I'm still trying to figure out what difference this would make.
Click to expand...
Click to collapse
the version I have is the one for main memory (I always have programs with the SD version)
its weird that it doesn't show up....what I can say is to uninstall it and delete the opera folder after uninstall, then reinstall, check if you get the download manager (I don't have flash3.1 installed so maybe thats causing the problem). I do remember on a build I wasn't getting the download manager I don't know which it was, I think it was 2123.
In User Prefs there's two update delay
in the quick search box type in delay and both will show up.
"First Update Delay" to 0
and then "update Delay" to 0
lennie said:
the version I have is the one for main memory (I always have programs with the SD version)
its weird that it doesn't show up....what I can say is to uninstall it and delete the opera folder after uninstall, then reinstall, check if you get the download manager (I don't have flash3.1 installed so maybe thats causing the problem). I do remember on a build I wasn't getting the download manager I don't know which it was, I think it was 2123.
In User Prefs there's two update delay
in the quick search box type in delay and both will show up.
"First Update Delay" to 0
and then "update Delay" to 0
Click to expand...
Click to collapse
Yes, uninstall and reinstall brings back the download manager. Thanks for the suggestion, Lennie.
eaglesteve said:
Yes, uninstall and reinstall brings back the download manager. Thanks for the suggestion, Lennie.
Click to expand...
Click to collapse
I'm glad to hear that it worked
lennie said:
I'm glad to hear that it worked
Click to expand...
Click to collapse
I can't get it to work, any suggestions ??
Here is what I did :-
1.) from your previous posts found that you are using SD version so downloaded it and downloaded flash lite3.1 cabs.
2.) installed flashlite 3.1 , reboot.
3.) installed opera SD , reboot.
now when i start opera, its splash screen opens , progress bar gets stuck at the initial 5-10% position and opera doesn't opens,
i tried reinstalling, both in micro drive, device same problem, any advices ??
paranoid1288 said:
I can't get it to work, any suggestions ??
Here is what I did :-
1.) from your previous posts found that you are using SD version so downloaded it and downloaded flash lite3.1 cabs.
2.) installed flashlite 3.1 , reboot.
3.) installed opera SD , reboot.
now when i start opera, its splash screen opens , progress bar gets stuck at the initial 5-10% position and opera doesn't opens,
i tried reinstalling, both in micro drive, device same problem, any advices ??
Click to expand...
Click to collapse
I install both on device memory. These are some of the very few programs that I don't install on my microdrive.
eaglesteve said:
I install both on device memory. These are some of the very few programs that I don't install on my microdrive.
Click to expand...
Click to collapse
I also installed both on the device, and it didn't worked
EDIT : NON SD version worked
I'll have to try uninstalling and reinstalling with Flash lite 3.1 first, then Opera. Installed it the other way around.
techntrek said:
I'll have to try uninstalling and reinstalling with Flash lite 3.1 first, then Opera. Installed it the other way around.
Click to expand...
Click to collapse
yes you have to install flash first to get it to work with opera properly. and I've always had problems with SD version, if it's not being able to enter passwords its me not able to post here on xda, and a whole lot more problems and i stick to the device version.
Related
I just installed the newest opera and it seems to work fine over the previous opera that is cooked in. I only used it for a few minutes but it seems better.
not to double post but:
http://www.megaupload.com/?d=SFVV497V
irus said:
not to double post but:
http://www.megaupload.com/?d=SFVV497V
Click to expand...
Click to collapse
Any extensive use results?
I like it!! Thanks again Irus. You're the man!
Have used it only for a few minutes, but I already have a good feelig about this. My www.smh.com.au webpage is correctly displayed now, whereas it was messed up with the alpha or pre-alpha version. I also feel that it is faster.
Life is getting better and better now....
Will later test the other things like internet banking, other webpages, youtube, etc.
Works on the Dopod U1000 stock ROM without problem.
Can anyone link it someplace else except megaupload? They keep telling me my country has no more available slots...
Thanks.
It Works in IRUS ROM
I am testing with IRUS rom and works.
Just remember , if you have FTOUCHFLO enabled, to set the exclusions for opera9.exe otherwhise the scrolling will be SLOOOOOOOOWWWW
Many improvements, faster, better rendering, settings menu'.....
I have tried it... but netfront 3.5 RC7 is still beter for me...
Thanks for letting us know. Yep, mostly looks nicer, better rendering. Some things are worse though!
** WARNING ** you lose all your favourites! Whoops.
How do I tweak this back to a more VGA-suited application? All menus are double spaced.
The favourites page is now on a grey background, looks worse than before (e.g. Transport for London favicon)
The bottom right popup button is now black instead of transparent. Why!
Also the popup onscreen keyboard bug is still there :-(
yaughan said:
Thanks for letting us know. Yep, mostly looks nicer, better rendering. Some things are worse though!
** WARNING ** you lose all your favourites! Whoops.
(
Click to expand...
Click to collapse
this version installs into /windows/opera9
copy the opera6.adr file from application data/opera9 to this folder and lo your bookmarks are restored!
I've been trying to tweak the skin file but it's not playing nicely. Maybe worth looking at some of the CSS files to take care of the other issues.
the rapidshare links are on page 2 in the dev and hacking thread, if ive got a sec ill get hem for you lot
rapidshare links:
WM6 QVGA http://rapidshare.com/files/11637540..._QVGA.cab.html
WM6 VGA http://rapidshare.com/files/11637863...lable__VGA.cab
WM5 QVGA http://rapidshare.com/files/11637799..._QVGA__WM5.cab
WM5 VGA http://rapidshare.com/files/11637934...__VGA__WM5.cab
I prefer the opera 9.5 onAP4 as the zoom is at an acceptable level whereas with this cab it is way too large.
I dont use RealVGA so I am not sure if this would improve its appearance.
I have used my bank site with no problems
lakeman said:
I prefer the opera 9.5 onAP4 as the zoom is at an acceptable level whereas with this cab it is way too large.
I dont use RealVGA so I am not sure if this would improve its appearance.
I have used my bank site with no problems
Click to expand...
Click to collapse
in address bar type in about:config and you can change that and a whole lot more
thanks irus, I had done this with the beta but forgot how to do this
I'm on AP4 and just tried the megaupload file - won't install because of incorrect permissions.
Edit: I just tried again and this time it installed. Odd.
Well, I've been playing with this for the last hour or so and here's my impression. It renders better than the one that came with AP4. It doesn't scroll the screen with the 4-way like the AP4 version did, but I can live w/o that. It has a bug where most (all?) links can't be successfully clicked until you zoom in on the page - they appear to select by turning red, but the new page doesn't load. After zooming they turn red, then get highlighted, then the progress bar starts to show as the new page loads. One other bug, same as in AP4, it briefly shows each character in password fields before turning them into asterisks.
Edit: the link issue seems to be fixed if you start off at a large enough zoom level. Here are my Adaptive Zoom settings currently, although I may increase the zoom levels further.
Browser Buffer Width: 800 (pixels)
Maximum Zoom: 120 (percent)
Minimum Overview Zoom: 85 (percent)
Minimum Zoom: 85 (percent)
Virtual Screen Width: 800 (pixels)
techntrek said:
I'm on AP4 and just tried the megaupload file - won't install because of incorrect permissions.
Edit: I just tried again and this time it installed. Odd.
Click to expand...
Click to collapse
You have to kill the old Opera if it is running. Otherwise you will get a permissions error.
techntrek settings help, but I'm not sure i liked them as much as the old default ones in the one installed with AP4. Anyone have a list of those? I didn't think to save them.
(You need to restart to make them apply, I didn't realise).
The settings do solve the clicking on a link in zoomed out view, although I'd rather be zoomed out more. It's an odd one, as you can still do the tap and hold click to bring up the menu and it realises you are on a link.
The big positive so far is that you get a progress bar in full screen mode now, so you actually know you have clicked on something. Otherwise I'm quite negative on this release.
The skin is too big and no longer transparent in full screen mode (the right hand corner arrow).
I've had the keyboard fail to display a few times, and as I work in tablet mode this is bad!
It doesn't seem to want to go to my homepage on start-up, but goes there if I click on home.
OK and cancel buttons just display as black boxes on pop-ups.
I think it feels more like a beta than the last build to me.
I made the Minimum Overview Zoom to 70, keep all other values, and also use large font size.
It works well.
Occasionally my onscreen keyboard pops up by itself. When I try toggle it off, the portion previously covered by the keyboard is not 'reclaimed' by the rendering mechanism.
Conflict with Tengo still not resolved.
Black font on black keys om some screen is annoying, but not big deal for me.
I like the big space occupied by the menu bars. Easy for fingers. Just don't like the space taken by each favourite items.
Overall, I like the improved speed and fantastic rendering accuracy as compared to the earlier versions, although it is still far from being stable and perfect. Mine freezes a few times forcing a soft reset.
I've now made this my primary browser over netfront 3.5.
techntrek said:
One other bug, same as in AP4, it briefly shows each character in password fields before turning them into asterisks.
Click to expand...
Click to collapse
That's not a bug. Lots of apps and platforms do that. It's to allow you to make sure that you've entered the right characters before moving on to the next.
Having played some more, I really like it despite the odd quirks.
The google reader gadget on my igoogle page now works, and google mail is working well (I don't think it did before).
Still had a few more issues...
Sometimes images don't show. You just get an empty box.
And sometimes in forums threads when changing page, or going to the next page in something like google images it doesn't always put me back at the top of the page.
Otherwise it just keeps getting better.
It's time to have a new Opera Mobile again.
http://www.megaupload.com/?d=C54S9CCB
See why I don't like them to be built into the ROM? These things change too fast.
Can this be installed to SD?
Sorry, no storage card version yet.
But keep a watch for it here
http://forum.xda-developers.com/showthread.php?t=401643
Not sure if this version is better than the last one. Still playing with it to find out.
edit: The display is a bit messed up in this version.
Does anyone else find this the case too on their Athena?
Eagle: What numbers are you liking for the adaptive zoom? Sorry I can't answer your question as I have never messed with these settings before. Also is yours rotating your screen after you close/minimize it?
Goatmaster said:
Eagle: What numbers are you liking for the adaptive zoom? Sorry I can't answer your question as I have never messed with these settings before. Also is yours rotating your screen after you close/minimize it?
Click to expand...
Click to collapse
I set the minimum overview zoom to 70 in earlier build, but 85 in more recent builds. The only purpose is to allow me to activate a link without zooming in.
Tried this build on my X7510. A few observations:
1. Screen rotates on shut down.
2. Couldn't use hardware keyboard. After each key stroke, the entire field was highlighted, which caused the next key stroke to over-write the one before.
3. Opera was not set as default browser.
I went back to build 1184. The first two issues made it unusable for me.
magxs said:
Tried this build on my X7510. A few observations:
1. Screen rotates on shut down.
2. Couldn't use hardware keyboard. After each key stroke, the entire field was highlighted, which caused the next key stroke to over-write the one before.
3. Opera was not set as default browser.
I went back to build 1184. The first two issues made it unusable for me.
Click to expand...
Click to collapse
I'm back to 1184 also. Thanks for posting your test results.
I found the following problem with most cooked ROMs (also including the last official one from HTC) /I tried that on fresh installations in every case/
I like AutoLock feature. So I made a small .reg file to modify one small entry in registry.
The moment this feature is on - if the device becomes locked, the screen goes dim. Problem is - it stays dimmed forever. I tried thousand different solutions - many combinations of registry values, power options, etc. nothing helps. If I lock the device manually - no problem. only with autolock. Anybody knows how to make it work?
Regards,
Vojtek
Maybe you should post your script, so that someone can have a look. Did this work on some previous ROM? Or has it been an ongoing problem?
Try using SmartLock, found on this site.
jmckeejr said:
Maybe you should post your script, so that someone can have a look. Did this work on some previous ROM? Or has it been an ongoing problem?
Click to expand...
Click to collapse
The official HTC ROM that I used to have before recent official update from HTC - worked very fine with this little registry mod.
The modification is as follows:
HKCU->ControlPanel->Backlight->AutoDeviceLockEnable
default value = 0
I change it to 1. This is all I do after totally fresh ROM update. that causes the dim to go permanently on from the next lock (doesn't matter if it was caused by auto or manual). even If I get back with the value to 0 in registry - problem stays. soft reset (and value set to 0) eliminate the problem.
one more thing - I never use auto-light sensor. My backlight level is always set to 2. with auto-light sensor - autolock works OK. however I loose a lot of battery life since auto-light sensor never allows backlight levels lower than 4.
Regards,
Vojtek
check out Lumos, it'll let you backlight go as low as you set it to
http://forum.xda-developers.com/showthread.php?t=450318
GldRush98 said:
check out Lumos, it'll let you backlight go as low as you set it to
http://forum.xda-developers.com/showthread.php?t=450318
Click to expand...
Click to collapse
Thank You for the tip. The tool itself is great. However it is affected same way by the autolock. Autolock causes device to stay dimmed permanently - even with Lumos running.
Regards,
Vojtek
First off... I'm new around here & still a little flabbergasted by everything WinMo, but this site has already helped me tremendously.
Secondly, I can confirm the AutoLock bug. I updated my Touch Pro to the latest official rom last night. While running through AdvancedConfig (i think...) I noticed the AutoLock option & enabled it. 10 minutes later I was freaking out that I had stuffed up my expensive new toy...
Disabled, rebooted & all is OK again.
First of all - Advanced Config has nothing to do with it (to defend the author).
Second - thank You for support. I could not find a solution for this problem anywhere and I spent hours googling. For the moment I thought that my TP is failed. Seems that nobody uses AutoLock these days. I don't know how everybody's doing it, but without locking, my TP calls to different people (especially from Favourites tab) from time to time...
Vojtek
vojtek11 said:
I don't know how everybody's doing it, but without locking, my TP calls to different people (especially from Favourites tab) from time to time.
Click to expand...
Click to collapse
I require a password/passcode level of security on my device - which the Lock/Unlock feature doesn't provide. Unfortunately, the current security implementation in WinMO 6.x doesn't allow the Today screen to be seen like the Lock/Unlock feature.
As a result of these shortcomings, most folks tend to use a 3rd Party lock application such as: S2U2, mLock, etc. as they provide the desired flexibility.
HTH,
very familiar with this issue. I'm working on it too. It affects the WM6.5 lockscreen for sure and I thought it was a problem with only that. Bugger that it affects official ROMs as well. Good info though, I can stop concentrating on the lockscreen and start looking at power mgmt.
mindfrost82 said:
Try using SmartLock, found on this site.
Click to expand...
Click to collapse
SmartLock all the Way!!
i have 2 new builds coming
NOW POSTED build 23420 found here:http://www.mobilitydigest.com/forums/showthread.php?t=1455
NOW POSTED build 23060 found here: http://www.mobilitydigest.com/forums/showthread.php?t=2002
Change log and known issues found at link above as well.
Please post any issue over there please.
Some Pictures Below FROM THE ROM
Hi, I cant seem to Fix the problem with my Wifi and your rom, It goes off after 20 seconds or so! by its self, and i want to get my email, but it wont stay connected..... and i cant figure out why but other than that... love the rom and the awesome window side slide animation
Great Job
kingfarmer said:
Hi, I cant seem to Fix the problem with my Wifi and your rom, It goes off after 20 seconds or so! by its self, and i want to get my email, but it wont stay connected..... and i cant figure out why but other than that... love the rom and the awesome window side slide animation
Great Job
Click to expand...
Click to collapse
ok i will look into the wifi to see if there is an error some where.
i ask please post any issues on the link above please
wifi - i am not having wifi issues - if you have wifi issues please do a hard reset and try wifi again - if you still have issues please post on the link posted above
same here. I tested both a secured and unsecured network without any issues. check your router.
herg62123 said:
wifi - i am not having wifi issues - if you have wifi issues please do a hard reset and try wifi again - if you still have issues please post on the link posted above
Click to expand...
Click to collapse
Ya, thanks anyways, it doesnt seem to go away for me, and i flashed Chrome rom, and it is fixed now.... thanks anyways, and again, great ROM, chrome isnt compared to it. but i like Wifi
am downloading it now (v13).. lets see. will update on ur link if i run across any problems
This is a great looking ROM. Like its almost ripped out of the TP2 or a Hero. Very quick and responsive. One noticeable isssue Ive had is a resizing problem when texting in landscape. Other than that, im also pleased i barely had to install anything, like almost everything i needed was there already.
Kudos
Just flashed this rom and I'm very happy with it. Runs very smooth and fast.
Only thing is I can't find the keyboard selector. Was it cooked in or do I have to install it? It seems the fuze keyboard is selected and this makes using the hw keyboard on a TP kind of difficult.
Awesome work on the rom!
Is all the hardware button working?
freedompeace said:
Is all the hardware button working?
Click to expand...
Click to collapse
All seem to be working on my touch pro including volume control.
I had to install the fuze / pro keyboard selector to get the hw keyboard working correctly.
Home button
Is there any chance to make Home Button open Manila Home Tab instead of WM start menu?
Hmm I installed chome editor 1.6 and now the lower left button (next to the start button) always says action and when pressed tries to start the htc action screen which isn't there. Is there a way to restore this?
First I want to say Thank You for such a beautiful ROM. It's fast, finger friendly, and professional looking. (Love the slider)
A couple things I have noticed are as followed:
1. Under the Notifications options, when I select "New Text Message", then try to select a different sound it scrolls the window behind the drop down box... not the actual drop down box. Same goes for the "Event" box, but only on some. Hard to explain.
2. Minor but annoying - When waking up and the device is locked, the clock jumps to the bottom of the screen then back up to the top.
3. Another Minor thing - "Start" occasionally shows up on the top left of the screen. Is it always supposed to be there or never? I know it brings up programs.
4. GfxBoost (lol "DO NOT DISTRIBUTE") has some icon issued on the bottom left and right. Bottom left (you can only see 1/4 of the windows logo) and bottom right (Don't know what it's supposed to be)
All-in-all i feel this is a fantastic ROM. I'd love to see what else you got up your sleeve. After about 16 hours I was down to 64% battery with hardly any use, but then again I was in the office where I get ZERO signal!
funny, I can only confirm the first issue. This happens only when using a sweep to scroll. When the slider is used it scrolls ok. I have also seen this pn the activesync screen when selecting message delivery schedules.
I'm running without manilla btw. I love Titanium
I am not registered (yet) on the other forum, hence posting here.
Installed v13 and its amazing.. fast and nice graphics..
Only one issue uptil now. In call recording is not working. It gives an error (something like cannot start ICR, wrong certificate etc..) Can I unistall ICR (not in the remove programs list) and install autocall recorder 1.2 instead? tht gives me more options..?
thanks
Thank You
Very nice ROM, thanks! I haven't gone through everything, but all seemes good so far!
Hey herg!
I had no idea you were a chef too! I flashed your rom and it is kick ass so far...
Aside from TF3D being a little sluggish (not that I care since I no longer use it... iPhoneToday all the way... for now ) it have not seen bugs.
BT file transfer - oK
3G connection - oK
ActiveSync - oK
Battery life - pretty good so far
GPS lock on - to be tested later
Wifi - to be tested later
I will try to report some more later on, but so far... kick ass!
love it
i havent updated to D-fresh-est but your doug-e-fresh is an amazing rom thank you for your contributions buddy im flashing this sucka tonight
rajackar said:
Just flashed this rom and I'm very happy with it. Runs very smooth and fast.
Only thing is I can't find the keyboard selector. Was it cooked in or do I have to install it? It seems the fuze keyboard is selected and this makes using the hw keyboard on a TP kind of difficult.
Awesome work on the rom!
Click to expand...
Click to collapse
in 6.5.1 builds the keyboard selector is gone. Instead, hold down the keyboard icon at the bottom of the screen and the selector pops up. That's the good...the bad is that it makes it harder to toggle the keyboard off the screen cause pressing it leads to he selector instead of toggling but that's the build, not the ROM. I'm still loving the ROM
[Solved] TS FREEZE FIXED / Orientation offset calibration & G-SENSOR CALIBRATION FIX
UPDATE: (13/11) A patch has been developed that completely eliminates TS FREEZE for good.
Thanks to mdebeljuh and jdivic, I tested it and it seems to be working perfectly.
Check post 140 on page 14:
http://forum.xda-developers.com/showpost.php?p=9194473&postcount=140
UPDATE: (20/11)A new patched 8.2 kernel without logging (better for daily use) is available.
Check post 234 on page 24:
http://forum.xda-developers.com/showpost.php?p=9304396&postcount=234
-----
EDIT: If you did autocalibration and messed your g-sensor, read post 10 & 11 to see a fix for it. (before going through post 1)
EDIT 2: Freezes of sensors and touch screen seem to be related to offset values. See post 10 & 11
Post 1 is for orientation offset. Check post 10 & 11 for g-sensor and ts freeze fix.
----
If your orientation is off when you lay your phone on a level surface and can't calibrate it in Android (because many people found it gets corrupted after auto calibration), this is one way to do so. (Winmo g-sensor calibration does not seem to affect android orientation)
Install an app that displays sensor information along with pitch and roll. (such as SensorDebug from Android market)
Put your phone on a level surface such as the floor or a table.
Note your pitch and roll values.
Use rootexplorer or similar file manager to edit /data/misc/AK8973Prms.txt file. (open in text editor) (For ASTRO CHECK POST 70 in page 7)
You will see AOFFSET.x and AOFFSET.y at the bottom. (May be on top if you autocalibrated previously)
y affects pitch and x affects roll, there is about 4 to 1 ratio.
What you are trying to do is make pitch and roll 0 with minimum flicker.
Press and hold home button to switch between rootexplorer and sensordebug. Your changes will be reflected in realtime (with most builds). Go back and forth a few times to get perfect result. (You can press and hold home button to go back and forth) If you think changing values don't have an affect, try to temprorarily change AOFFSET.x=90 and return to your app. When phone is on the table, your leveling bubble or pitch/roll must be way off. This way you can see if with your build changes are reflected in realtime or not. If not try restarting, use different sensor app and give feedback please. (After that revert AOFFSET.x to 0 or other value your want to fix back orientation)
For example:
If pitch is 3 and roll is -1
you may start by
AOFFSET.x=4
AOFFSET.y=-12
Then adjust with 1 increments to get rid of flicker.
It is best to adjust one value at a time.
EDIT: IF YOU WANT TO CALIBRATE Z AXIS, CHECK POST 61 in page 7
Calibrated AOFFSET values for my phone are x=2 y=-9 z=12
You can use gpsstatus or bubble app (to find bubble app search the market for bz.ktk.bubble and enable "show angle" from bubble apps settings.) for visual check of orientation calibration. Because of the protruding camera lens of hd2, there can be 1 degree difference between sideways and normal orientation. (It seems you can adjust in about 0.25 degree increments by each 1 increment of AOFFSET and compansate by lowering AOFFSET=y by 2 that gives 0 degrees in both normal and sideways orientation in bubble app)
- You don't need to reboot for most builds (if there is no affect check post 11)
- You don't need to kill/restart akmd
- You don't even need to close sensor app
- Because of not perfect kernel/build support for sensors, you may see them freeze when you move the phone (TS will also freeze). With evo kernels, just wait a few seconds and it will resume. (With nexus kernels they may freeze until sleep/wakeup) Interestingly the values of AK8973Prms.txt affect shake/move freezes. I wrote about this in post 10 and 11.
IT IS A GOOD IDEA TO BACKUP COMPLETE ANDROID FOLDER BEFOREHAND just in case something goes wrong. Chefs say you shouldn't auto calibrate your g-sensor under Android because with many people it gets messed up. Also good idea to backup your /data/misc/AK8973Prms.txt
You may have trouble accessing data folder with a file manager other than rootexplorer. Your build must be rooted. (most are) It is a good idea to update your su binary inside superuser app settings TWICE. If you change permissions of /data /data/misc folders you may access them even with standart astro file manager. Try chmod 777 /data from terminal emulator.
This procedure is also possible with adb or droidexplorer. But my way of doing is practical and it is in realtime. If your build has different file name, please tell us.
This IS a development thread, please don't tell me to post in generic section or clutter.
This is manual workaround for non-working auto calibration. If auto-calibration works in the future, it may very well fix your freezes.
Values of AK8973Prms.txt file may solve touch screen/sensor freeze problems with your games. Feedbacks are always welcome. We should find out what the other values do exactly. Also check post 10 & 11
Wow, thank you. I will certainly try this when I am sober (tomorrow morning).
I appreciate your taking the time to share this.
Have a good weekend!
Thanks! worked great....
thanks! worked perfectly
haha.. funny, this is the RIGHT way to do it: (credit goes to me )
1) put your phone on the surface and then
2) Gscript to stop gsen.
3) Go to callibration tool and press callibrate..
4) activate Gsensor through Gscript.
thats it and gsensor is fully callibrated to your way. no need to mess with system files.
eeeeeee said:
haha.. funny, this is the RIGHT way to do it: (credit goes to me )
1) put your phone on the surface and then
2) Gscript to stop gsen.
3) Go to callibration tool and press callibrate..
4) activate Gsensor through Gscript.
thats it and gsensor is fully callibrated to your way. no need to mess with system files.
Click to expand...
Click to collapse
Don't you think I already knew that? I wrote this long procedure because calibration tool corrupts calibration and doesn't work with many people. With many builds, chefs write don't calibrate your sensor. You need the gsensor script to be able to stop gsensor (kill akmd) since you didn't share it, people won't be able to do it anyway.
I suggest backing up complete Android folder before attempting to auto calibrate g-sensor within Android. Forum is full of people who calibrated under android and everything is messed up.
memin1857 said:
Don't you think I already knew that? I wrote this long procedure because calibration tool corrupts calibration and doesn't work with many people. With many builds, chefs write don't calibrate your sensor. You need the gsensor script to be able to stop gsensor (kill akmd) since you didn't share it. People won't be able to it anyway.
I suggest backing up complete Android folder before attempting to auto calibrate g-sensor within Android. Forum is full of people who calibrated under android and everything is messed up.
Click to expand...
Click to collapse
gsensor calibration tool causes nothing.. in my way -> t does exactly what you do..
i know that with the evo kernel the gsensor callibration is kinda corrupted, but it still works perfectly when following my orders.
although i would suggest not doing this with gsensor on.
as long as the gsensor is off when calibrating, there is no risk to mess the gsensor up.
although when callibrating with gsensor on messes the whole thing up, you can fix it following my orders again.
although its still nice that you edited the beginning of your tutorial:
memin1857 said:
If your orientation is off when you lay your phone on a level surface and can't calibrate it in Android (because many people found it gets corrupted after auto calibration), this is one way to do so. (Winmo g-sensor calibration does not seem to affect android orientation)
Click to expand...
Click to collapse
eeeeeee said:
gsensor calibration tool causes nothing.. in my way -> t does exactly what you do..
i know that with the evo kernel the gsensor callibration is kinda corrupted, but it still works perfectly when following my orders.
although i would suggest not doing this with gsensor on.
as long as the gsensor is off when calibrating, there is no risk to mess the gsensor up.
although when callibrating with gsensor on messes the whole thing up, you can fix it following my orders again.
Click to expand...
Click to collapse
I have made extensive tests and found out that you are actually doing no proper calibration. You are breaking other things.
- If you disable g-sensor before you open your sensor app (calibration tool) than you get no data from the g-sensor (since you disabled it) and can't calibrate.
- Phone must be very still while you disable g-sensor or the orientation data will get frozen at wrong values. And sensor app must be open beforehand.
If you fail calibration (y axis) will get messed up badly and won't work again. It wil flicker between full up and full down and further calibration attempts will make compass constantly spin.
- Still if you could do it all, nothing changes, offset is still there and calibration is wrong after following your instructions. (Try bubble app or sensor app with real sensitive degree values and you will see)
I searched your posts and saw that you are complaining about touch freezes. Maybe if you don't do auto calibration you may get less freezes?
Also please DO share anything you know. It is not enough to just say -disable g-sensor with gscript- People don't know that script, and if you don't share they can't do it. I saw your thread, you got 0 replies in 20 days, maybe because it doesn't work.
I advise against doing autocalibration. And remember, this is not a pissing contest. We are not doing this for the credit. We should be doing this for helping community. (You should have written nicer, instead of looking like showing off how genious you are and how fool we are. We know some things too.)
My way of doing it is NOT direct calibration. It is providing offset to g-sensor data that many people can do without the risk and can be restored back easily.
Note: I have found out that calibration tool generates a file named AccPrmsF.ini in the same folder with extreme z value. Sometimes a bma_result.txt gets created again with wrong values. Its content is input to AK8973Prms.txt again with extreme z value. If you restore your original AK8973Prms.txt g-sensor starts working properly again. (see post 10 & 11)
eywallah bro
How to restore g-sensor
If you calibrated with android calibration tool and your g-sensor freaked out. Here is how to fix it:
Use rootexplorer to
Delete AccPrmsF.ini and bma_result.txt file in /data/misc (if they exist)
Edit AK8973Prms.txt in /data/misc folder with rootexplorer to these values:
[AK8973]
HDOE_STATUS_SLIDER_OPEN=1
HDOE_STATUS_SLIDER_CLOSE=0
HDOE_SUCTEMP=114
HDAC_SLIDER_OPEN.x=128
HDAC_SLIDER_OPEN.y=135
HDAC_SLIDER_OPEN.z=4
HOFFSET_SLIDER_OPEN.x=250
HOFFSET_SLIDER_OPEN.y=593
HOFFSET_SLIDER_OPEN.z=175
HDAC_SLIDER_CLOSE.x=0
HDAC_SLIDER_CLOSE.y=0
HDAC_SLIDER_CLOSE.z=0
HOFFSET_SLIDER_CLOSE.x=0
HOFFSET_SLIDER_CLOSE.y=0
HOFFSET_SLIDER_CLOSE.z=0
ASENSE.x=256
ASENSE.y=256
ASENSE.z=256
AOFFSET.x=0
AOFFSET.y=0
AOFFSET.z=0
(These values may not solve freezes, check post 11 for different values that may fix freezes)
Some nexus based builds don't have slider open/close lines.
No need to reboot, just save and it should work instantly with most builds. (If it doesn't check post 11) If you delete AK8973Prms.txt or it may get recreated with wrong values (full zeroes) and freak out again. AOFFSET.z=xxx seems to be the culprit of calibrate tools vertical corruption. (Becomes full up or full down like digital when z=veryhigh). Only editing it to zero may solve the problem.
These values may change in time, or between builds. Those were my values, you may try to boot a new version of your android build and rip the file from it and use that instead.
If your g-sensor does not work at all after reboot you may need to restart it. Open terminal emulator and enter these commands:
su
/system/bin/akmd
Now it should be working.
Please tell if it worked for you. By comparing values and working on these values we may as well make g-sensor much better. (Accelerometer doesn't seem to be calibrated) If your build has different file name, please tell us. The instructions in post 10 may not be perfect and I am still working on this and will post if I find anything new. Of course kernel support is also required for getting less flickers, no freezes, proper poll intervall, correct i2c frequency and proper calibration.
EDIT: The values keep changing by itself. Interesting part is I am getting less shake/move freezes (or freezes in only one direction) in sensor apps or games now! I am experimenting with different values and it definitely affects how often freezes happen. I am trying to get the values of what a real calibration would do. Maybe sensor freezes happen when values are out of range. I am sure a proper calibration will get rid of these freezes but since with the current kernels we can't do proper auto calibration, maybe we can do manual one for now. Seems usual x y z accelerometer values are between 10 and -10. When freezes happen they seem to be more than 10 or less than -10. ASENSE values change the range of x y z (minimum working asense is 45 and the more you set the less range x y z has). Also ppp data seem to freeze/restart when sensor freezes happen. If freezes are eliminated even ppp data might work better! Some of the findings might be wrong, of course.
It seems you can update AK8973Prms.txt in realtime with droidexplorer and changes are reflected in realtime when you reopen, switch to the sensor app or sleep/wakeup. This makes testing easier.
It seems I have found non freezing values. Check next post. (Post 11)
Freezes are fixed now.
EVEN IF YOU ARE NOT GETTING TOUCH SCREEN / G-SENSOR FREEZES WITH USUAL USAGE OF YOUR PHONE, INSTALL SENSOR DEBUG, BUBBLE, COMPASS APP OR GAMES AND TRY IF THEY FREEZE WHEN YOU SHAKE/MOVE THE PHONE OR WALK WITH THE PHONE IN YOUR HAND. Bubble app is the most freezing app. To find it ssearch the market for bz.ktk.bubble. Enable "show angle" from bubble apps settings. Game example: Teeter
Make sure it has been at least 2 minutes since Android has booted. (Or it may fool you as it is busy when first home screen appears after boot)
Freezes have been mostly eliminated with newer builds/kernels, but they are not completely gone.
I am no longer getting any freezes in any app now. Not in compass apps, not in games, not in sensor displaying apps, not in calibration tool. I am also not getting freezes while I am walking with the phone.
I am not yet sure how this exactly happened (as I always had freezes in those apps when the phone moved) but currently my android build updates the AK8973Prms.txt file every minute by itself (doesn't change very much, but quite different from the beginning) and the current values have absolutely no freezes.
These values have no more freezes. (since they keep changing it may not last for days) Please try:
[AK8973]
HDOE_STATUS_SLIDER_OPEN=2
HDOE_STATUS_SLIDER_CLOSE=0
HDOE_SUCTEMP=111
HDAC_SLIDER_OPEN.x=4
HDAC_SLIDER_OPEN.y=135
HDAC_SLIDER_OPEN.z=8
HOFFSET_SLIDER_OPEN.x=-849
HOFFSET_SLIDER_OPEN.y=1179
HOFFSET_SLIDER_OPEN.z=-653
HDAC_SLIDER_CLOSE.x=0
HDAC_SLIDER_CLOSE.y=0
HDAC_SLIDER_CLOSE.z=0
HOFFSET_SLIDER_CLOSE.x=0
HOFFSET_SLIDER_CLOSE.y=0
HOFFSET_SLIDER_CLOSE.z=0
ASENSE.x=256
ASENSE.y=256
ASENSE.z=256
AOFFSET.x=0
AOFFSET.y=0
AOFFSET.z=0
Seems
A low HDAC_SLIDER_OPEN.x value
A large negative HOFFSET_SLIDER_OPEN.x value
A high HOFFSET_SLIDER_OPEN.y value
A large negative HOFFSET_SLIDER_OPEN.z value
and along with some other thing I did/happened fixed my freeze problems.
Some nexus based builds don't have slider open/close lines.
Change the AOFFSET.x y and z values to your device to level it on a table. (check post 1)
I am not attaching the file itself to this post because of differences between windows and linux with text files, just to be safe. (Paragraphs get messed up)
Also using the calibration tool with the phone face down gives better results with z axis. (to be able to tap on calibrate, put your phone on the table and make it just go over the edge of the table and tap from underside)
We need some feedback from other people now. Devs are welcome to use this information to open up ways to fix g-sensor in kernel.
I am using mdeejay desire hd 3.4 build. These may be different in other builds. If you find out please share.
Freezes returned after reboot. I am trying to find out how refix again.
I AM ASKING EVERYBODY TO TELL
1) If they have the freezes with their default configuration with bubble/sensor app moving/walking etc.
2) If my values fix the freeezes
3) If their filenames etc is different
4) Please also write your build and kernel type/version/base winmo rom and radio
Example: (copy paste and edit in your post please)
Default configuration have freezes: YES
New values fix freezes: YES
Different files: NO
Build/Kernel: mdeejay desire hd 3.4 / huanyu #21 evo base miri WM6.5 (21916) v19.1 (3.14 base) 2.15.50 radio
This is not over yet, with feedback we might find exact long term fix for everyone.
EDIT: These values work with some people. If they don't work you, experiment with different values. Since the results are reflected in realtime for most builds (no reboot required) it is much easier. Also don't edit the file on windows pc, it may get messed up. Some builds auto update the values when sensor app is reopened/switched to.
IMPORTANT: Try to temprorarily change AOFFSET.x=90 and return to your app. When phone is on the table, your leveling bubble or pitch/roll must be way off. This way you can see if with your build changes are reflected in realtime or not. If not try restarting and give feedback please. (After that revert AOFFSET.x to 0 or other value your want to fix back orientation)
EDIT 2: My sensors seem to be working perfectly since I also calibrated the z-axis. (post 61 on page 7) I need confirmation on this.
wow! thank you very much!
will try and post results soon.
Default configuration have freezes: YES (from time to time, not always)
New values fix freezes: YES. Post 11
Different files: NO
Build/Kernel: hyperdroid 1.6 / michyprima R11
before, using a live wallpaper called shake them all, the phone would insta-freeze on me.
using your values from post 11 (simple copy paste), no more freezes. And i really abused the wallpaper!
If this changes, i'll report here
EDIT: new answers
Post 1 is not for freeze fixes.
The solution is not long term.
I am extensively trying to find out what exactly made the freezes go away.
Because while it worked for many hours. After reboot freezes came back. I will hopefully find out why. Also the reason why the values change every minute is mistery. Contents of the file (values) change after you start or switch to any app that accesses the sensors. After android has booted it won't get updated unless the sensor reading apps are working.
I have been trying with many builds and kernels for theese freezes and they were never gone before. This time it never froze for several testing hours till I rebooted. That must be something.
Fixing the g-sensor after calibration corruption is ok. Adjusting level offset is also ok. But freezes need some more testing.
new answers in my above post.
you said that after the reboot freezes would happen. i change the permissions to read only on the AK8973Prms file, rebooted and no freezes.
crawlingcity said:
before, using a live wallpaper called shake them all, the phone would insta-freeze on me.
using your values from post 11 (simple copy paste), no more freezes. And i really abused the wallpaper!
...
new answers in my above post.
you said that after the reboot freezes would happen. i change the permissions to read only on the AK8973Prms file, rebooted and no freezes.
Click to expand...
Click to collapse
I am glad it worked for you and we are making progress.
I also had tried changing permissions before but after one minute permissions revert back to writable and the files is updated by the system.
just tested again. restored the default file (with the default values) and as soon as the little droids (or homers in my case) start moving - freeze.
Changed again to your values in post 11, changed permissions to read only, rebooted, played with the phone, i even juggled my HD2! No freezes. I think i won't change anything, unless i need to correct the pitch and the roll.
crawlingcity said:
just tested again. restored the default file (with the default values) and as soon as the little droids (or homers in my case) start moving - freeze.
Changed again to your values in post 11, changed permissions to read only, rebooted, played with the phone, i even juggled my HD2! No freezes. I think i won't change anything, unless i need to correct the pitch and the roll.
Click to expand...
Click to collapse
How are you changing the permissions?
I change permissions to readonly with rootexplorer and after I switch to sensordebug or bubble or phone tester app, the file reverts its permissions back to writable and gets updated.
BTW bubble app freezes more frequently than other apps. But when my freezes were gone, even bubble app never froze even when abused.
I'm just using root explorer. Select the file, uncheck the "write" option, close root explorer. Open sensor debug or whatever, check the file, untouched.
crawlingcity said:
I'm just using root explorer. Select the file, uncheck the "write" option, close root explorer. Open sensor debug or whatever, check the file, untouched.
Click to expand...
Click to collapse
I am doing the same but it becomes writable again. Must be because of different sensors.xxx.so file and build or maybe because you are trying with a wallpaper and not an app.
BTW editing the file on windows pc may not work because of paragraphing difference between windows and linux. If this happens, my phone just adds new zero values to the end of the file.
I am dying to reproduce the fix. I will test with some different builds. That constant file updating is killing me.