Related
I've installed the 1.2 Black Edition ROM and keep getting the Pink/White "Simple" looking PIN entry screen.
I thought this was fixed in this new version?
Any ideas?
Have a look in the initial thread. There is the changed dll.
I had a look at the initial thread and it said it was fixed, however I have flashed it several times and still get it...
I read the thread and only one other persion mentioned it but no one suggested a fix..
Any ideas or pointers?
Thanks
Mark
mdavenport said:
I had a look at the initial thread and it said it was fixed, however I have flashed it several times and still get it...
I read the thread and only one other persion mentioned it but no one suggested a fix..
Any ideas or pointers?
Thanks
Mark
Click to expand...
Click to collapse
here it is brother....
Do I simply copy this over the existing?
mdavenport said:
Do I simply copy this over the existing?
Click to expand...
Click to collapse
yes you do...
will this fix ruin the H/U/E/G icons?
.VIBE said:
will this fix ruin the H/U/E/G icons?
Click to expand...
Click to collapse
its included in the base ROM bro.... Black 1.2
walshieau said:
yes you do...
Click to expand...
Click to collapse
Thanks this fixed my problem.
How come no one else with 1.2 is finding this problem? Do it only affect certain devices?
Thanks
Mark
mdavenport said:
Thanks this fixed my problem.
How come no one else with 1.2 is finding this problem? Do it only affect certain devices?
Thanks
Mark
Click to expand...
Click to collapse
no it affects everyone... but you whinge louder hahahahahah... kidding.....
mdavenport said:
Thanks this fixed my problem.
How come no one else with 1.2 is finding this problem? Do it only affect certain devices?
Thanks
Mark
Click to expand...
Click to collapse
its actually not a problem, its just eh pin entry skin,
your personal tastes may be different to others.
next time please search the thread of 1.2 before starting a new thread, tis thread is wasting valuable real estate,
jasjamming said:
its actually not a problem, its just eh pin entry skin,
your personal tastes may be different to others.
next time please search the thread of 1.2 before starting a new thread, tis thread is wasting valuable real estate,
Click to expand...
Click to collapse
I did and there was nothing about it at the time and someone has only just posted the fix this morning..
Searching on the proximity sensor I found these two parameters for the startup.txt:
board-htcrhodium-proximity.on=1 to enable the proximity device (default off)
board-htcrhodium-proximity.wake=1 to wake up the phone on proximity
http://xdandroid.com/wiki/Kernel_boot_command-line_parameters
But I can't get them to work.
Are they really available on FRX07 or NeoFroyo?
Thanks
Daved+ said:
Searching on the proximity sensor I found these two parameters for the startup.txt:
board-htcrhodium-proximity.on=1 to enable the proximity device (default off)
board-htcrhodium-proximity.wake=1 to wake up the phone on proximity
http://xdandroid.com/wiki/Kernel_boot_command-line_parameters
But I can't get them to work.
Are they really available on FRX07 or NeoFroyo?
Thanks
Click to expand...
Click to collapse
The prox sensor is not enabled on the hardware level (kernel). Perhaps they will be available soon tho, I think ACL was working on them.
arrrghhh said:
The prox sensor is not enabled on the hardware level (kernel). Perhaps they will be available soon tho, I think ACL was working on them.
Click to expand...
Click to collapse
Oh... good. Thanks for letting me know!
Would you mind if I ask you about using the PTT button?
Daved+ said:
Oh... good. Thanks for letting me know!
Would you mind if I ask you about using the PTT button?
Click to expand...
Click to collapse
What about it? Only the RHOD300 has it... No other RHOD has one.
arrrghhh said:
What about it? Only the RHOD300 has it... No other RHOD has one.
Click to expand...
Click to collapse
Yes and I have one of those. Any chance I can give it some use? I googled a lot and tried a couple things with no success. Thanks!
Daved+ said:
Yes and I have one of those. Any chance I can give it some use? I googled a lot and tried a couple things with no success. Thanks!
Click to expand...
Click to collapse
I think that if it's enabled kernel-side(I don't think so) you need to edit keymaps in rootfs to use it
But if it's not used kernel-side then you have to mess with the source
Daved+ said:
Yes and I have one of those. Any chance I can give it some use? I googled a lot and tried a couple things with no success. Thanks!
Click to expand...
Click to collapse
There's some hacking at the rootfs you'd have to do. F22's rootfs allowed you to remap the key to a few different things, but unfortunately he never made a merge request for his code... which wouldn't have been easy, he would've had to change the way he did certain things. His rootfs hasn't been updated in quite some time, so I would not recommend using it. I'm sure you can take his keymap stuff tho and put it into an updated rootfs - with a little bit of manual labor you'll be able to remap the PTT key to a few different things.
See F22's rootfs thread for more info on that.
i should have something to test for the prox sensor this week. Just finished the patch .. To be honest i have no idea when it's actually used or if our userland is ready for it.
[ACL] said:
i should have something to test for the prox sensor this week. Just finished the patch .. To be honest i have no idea when it's actually used or if our userland is ready for it.
Click to expand...
Click to collapse
I'll be happy to test it
kernel done but turns out we need some userland patches.
Wow you're really Johnny on the spot
i dunno if thats good or bad
I thought it was good, but sometimes when I try to make a reference it goes horribly awry.
Looks like this will be saved for gingerbread. Since userland changes need to be made, its not worth it to make em for froyo.
So next release of GB will have it
[ACL] said:
Looks like this will be saved for gingerbread. Since userland changes need to be made, its not worth it to make em for froyo.
So next release of GB will have it
Click to expand...
Click to collapse
One more reason to be eagerly awaiting a new GB drop.
Any ETA at all on that?
mbellot said:
One more reason to be eagerly awaiting a new GB drop.
Any ETA at all on that?
Click to expand...
Click to collapse
Never ask for eta.
It's better to have a nice surprise than a delayed build..
helicopter88 said:
Never ask for eta.
It's better to have a nice surprise than a delayed build..
Click to expand...
Click to collapse
Pretty much the first rule of any dev work - especially free/OSS - never ask for ETA.
Thanks!
actually prox is only tested on cdma and the gsm portion needs to be checked. Anyone have a recmodded rom ? or know how to pull dlls? PM me please since i need to double check on some stuff
Currently, Ventriloid and Mangler are non functional for the Android JB firmware. Although the Ventriloid dev has posted a temp fix in the app description, it crashes alot and will not serve much use for me. Is it possible for someone to post a fixed app or a way to access vent on JB?
Store link:
https://play.google.com/store/apps/details?id=com.jtxdriggers.android.ventriloid&hl=en
Temporary fix link:
https://code.google.com/p/ventriloid/downloads/list
Buuump. I totally need this, and many do aswell.
Metal Slug said:
Buuump. I totally need this, and many do aswell.
Click to expand...
Click to collapse
Ventriloid dev here. What issues are you having with the test version on the site? I just finished up my semester at school and will hopefully have an official release out by January, but I need some help testing.
Ventrilo for JB not working?
jtxdriggers said:
Ventriloid dev here. What issues are you having with the test version on the site? I just finished up my semester at school and will hopefully have an official release out by January, but I need some help testing.
Click to expand...
Click to collapse
Just wanted to jump in and mention that I am having issues too. Samsung SII, cm10. When I start ventriloid is initially says connecting, but then very often goes back to mobile's home screen. It then leaves a notification bar entry saying that it is connected. When you click on that, it does its two vibrates and goes off entirely. Sometimes I can get it going again, but is very fiddly. Dont know if this helps. Hope so.
London Lad
LondonLad said:
Just wanted to jump in and mention that I am having issues too. Samsung SII, cm10. When I start ventriloid is initially says connecting, but then very often goes back to mobile's home screen. It then leaves a notification bar entry saying that it is connected. When you click on that, it does its two vibrates and goes off entirely. Sometimes I can get it going again, but is very fiddly. Dont know if this helps. Hope so.
London Lad
Click to expand...
Click to collapse
Hey LondonLad, thanks for the report.
Are you using the Play Store version of the app or the Alpha on my Google Code?
jtxdriggers said:
Hey LondonLad, thanks for the report.
Are you using the Play Store version of the app or the Alpha on my Google Code?
Click to expand...
Click to collapse
Playstore version.
LondonLad said:
Playstore version.
Click to expand...
Click to collapse
Go try out the Alpha at ventriloid.googlecode.com in the downloads section and let me know how it works for you. I apologize for any lack of features in that version but it's a huge work in progress.
jtxdriggers said:
Go try out the Alpha at ventriloid.googlecode.com in the downloads section and let me know how it works for you. I apologize for any lack of features in that version but it's a huge work in progress.
Click to expand...
Click to collapse
Have downloaded and it seems to work well. (Did loose the Ventriloid icon though!) One comment: One must tick the box Enable Global Push to Talk in order to see key. That is fine, but it does cover up part of you keyboard if you, for example, need to type in a password for a channel. Not a problem, but thought I would at least mention it.).:good:
LondonLad said:
Have downloaded and it seems to work well. (Did loose the Ventriloid icon though!) One comment: One must tick the box Enable Global Push to Talk in order to see key. That is fine, but it does cover up part of you keyboard if you, for example, need to type in a password for a channel. Not a problem, but thought I would at least mention it.).:good:
Click to expand...
Click to collapse
I'm glad it's working for you I'm working on a complete UI overhaul and that global push to talk was more or less a proof of concept for being able to talk outside of the app. Android has limitations for hardware key interception that won't allow push to talk while the app is in the background, so hopefully people will enjoy this new button. It will eventually be a bar with other options that can be hidden. Thanks so much for testing, I'm glad the ICS/JB fix is working.
jtxdriggers said:
I'm glad it's working for you I'm working on a complete UI overhaul and that global push to talk was more or less a proof of concept for being able to talk outside of the app. Android has limitations for hardware key interception that won't allow push to talk while the app is in the background, so hopefully people will enjoy this new button. It will eventually be a bar with other options that can be hidden. Thanks so much for testing, I'm glad the ICS/JB fix is working.
Click to expand...
Click to collapse
Thank you for your work on this. It is helping a lot of people! (I will make a donation shortly.)
LondonLad said:
Thank you for your work on this. It is helping a lot of people! (I will make a donation shortly.)
Click to expand...
Click to collapse
I greatly appreciate it I need to get a Bluetooth headset for testing, but Christmas and next semester's tuition has completely drained me haha. Let me know if you have any other issues or feature requests!
I get always "Sorry! We could not process your edit due to a loss of session data. Please try again. If it still does not work, try logging out and logging back in." when i trie to edit i9001 Wiki Page.
Tried Chrome, Firefox, Internet Explorer with/without all addons. No way to edit the Wiki-Page (i9001).
How to solve this?
Thanks in advance
Yup, i get that too, in fact i tried editing only my user page.
roofrider said:
Yup, i get that too, in fact i tried editing only my user page.
Click to expand...
Click to collapse
I tried it over the last days several times.
buffo1987 said:
I tried it over the last days several times.
Click to expand...
Click to collapse
Well, you can contact either svetius or TheManii (there's one more, can't remember who, daveshaw?)..through their talk pages or a PM here.
I think the talk page is to be used for wiki issues but either might work.
Also the wiki seems to be taking forever to load.
Thanks for the reports all... I've fixed an error with memcache, and it seems to have improved load time considerably and I am able to edit the wiki with no issues. Can you confirm it is also working for you all?
bitpushr said:
Thanks for the reports all... I've fixed an error with memcache, and it seems to have improved load time considerably and I am able to edit the wiki with no issues. Can you confirm it is also working for you all?
Click to expand...
Click to collapse
God! That was quick!!
Thanks it's all fixed.
Outta thanks.
bitpushr said:
Thanks for the reports all... I've fixed an error with memcache, and it seems to have improved load time considerably and I am able to edit the wiki with no issues. Can you confirm it is also working for you all?
Click to expand...
Click to collapse
works :good:
Did not now how fast the wiki can load.
roofrider said:
Outta thanks.
Click to expand...
Click to collapse
FTFY. :cyclops:
coolsandie said:
FTFY. :cyclops:
Click to expand...
Click to collapse
Thanks! It's back now.
I have a list of posts to be thanked, gotta get 'em all done now.
--edit--
Nope. They still are not back.
It tricked me, only one was back.
roofrider said:
Thanks! It's back now.
I have a list of posts to be thanked, gotta get 'em all done now.
--edit--
Nope. They still are not back.
It's tricked me, only one was back.
Click to expand...
Click to collapse
And that one, gave away to me rather than Bitpushr. How kind of you.
coolsandie said:
And that one, gave away to me rather than Bitpushr. How kind of you.
Click to expand...
Click to collapse
Lol i went for bitpushr after that and BOOM!
Marked as fixed.
The development team has fixed the issue that you have reported and it will be available in a future build.
Click to expand...
Click to collapse
No don't laugh but Google have marked the Pixel 6 as fixed in the next up date even though they've not released it thus won't know for sure everyone is happy
Google Issue Tracker
issuetracker.google.com
Just hoping the camera freezing issue is fixed soon!
Texan1 said:
Just hoping the camera freezing issue is fixed soon!
Click to expand...
Click to collapse
According to them it is even though its not been released for people to test, this will be the last Google device I buy
Texan1 said:
Just hoping the camera freezing issue is fixed soon!
Click to expand...
Click to collapse
I sure hope so! It's so annoying!!!!!