Hi guys,
I create a thread so it is easier to follow-up releases of the main Android for photon releases.
Latest release is available to download here:
http://code.google.com/p/photon-android/downloads/list
Version: 07.05.2011 r127
How to install (new users)
http://code.google.com/p/photon-android/wiki/Android_Installation_Tutorial
How to update (dont lose previous data):
Just copy&overwrite all files on your SDcard
Bug fix:
-FIX for USB detection (HTCSync etc) [by r0bin]
-charger fix (AC and USB) [by r0bin]
-battery gauge improved [by r0bin, pwel, munjeni, thanks photon community]
-GPS fixed [by schlund]
-fix camera sensor issue [by schlund]
-**NEW** fix for power button [by schlund]
-added media sources (ringtones,..etc)
-alarm clock can now be set
reserved for future use
Sorry, please delete this my post... i'm not able to do.
Hi -r0bin-,
first of all thanks to you and thanks to all the others developers.
You're doing a great job.
A small suggestion:
Why don't you insert in the release note the functionalities that are "temporarily" broken or that doesn't work anymore?
For example if in this release the wi-fi is not working, I think that could be useful read it in the release note, so every guy that want to install the new release knows the fixs and the problems and perhaps (only a hope...) we don't see anymore stupid thread with stupid questions.
-r0bin- said:
Bug fix:
-FIX for USB detection (HTCSync etc) [by r0bin]
-charger fix (AC and USB) [by r0bin]
-battery gauge improved [by r0bin, pwel, munjeni, thanks photon community]
-GPS fixed [by schlund]
-fix camera sensor issue [by schlund]
-**NEW** fix for power button [by schlund]
-added media sources (ringtones,..etc)
-alarm clock can now be set
Click to expand...
Click to collapse
Great work r0bin, schlund! Thanks a lot.
one minor remark: the power button fix does not seem to work for me. is this the correct thread to make such remarks?
3g not working
But, if i may know, what was problem with GPS and clock? I need it for cm6 and cm7 port. Thank you for all great work!
guys!
there is no download at the moment. my mistake was to create this thread before release was uploaded
ignore the previous one!
i am uploading the new one! wifi working, charge working, 3G working, etc.
thank you
-r0bin- said:
Version: 07.05.2011 r127
-alarm clock can now be set
Click to expand...
Click to collapse
the issue list shows the system time runs faster if so then setting alarm won't be of any use or had the time been fixed in this release.
rObin when you will lay out the corrected version?
sorry i have issues wit google download page.... after upload it is not moving anymore.
i will let it like this for some time, let's see...
-r0bin- said:
sorry i have issues wit google download page.... after upload it is not moving anymore.
i will let it like this for some time, let's see...
Click to expand...
Click to collapse
r0bin can u use rapidshare pls?or better www.ge.tt because it will let us download the file while you are uploading it
its online!
happy uploading
edit: USB connection for HTC Sync is not working anymore, i dont know why :-/ ill check it later
edit2: strangly, it works after 3rd boot (?)
-r0bin- said:
its online!
happy uploading
edit: USB connection for HTC Sync is not working anymore, i dont know why :-/ ill check it later
edit2: strangly, it works after 3rd boot (?)
Click to expand...
Click to collapse
This is what I'm talking about svn and changes
I have an isue on battery info (#*#*4636*#*#), randomly charging-not charging, also led lamp flashing, but charging work hmmm, maybe you forgot something
Hi! Thanks for update!
You know about this trick:
Plug headphones and launch FM radio in WinMo, then go to sdcard and launch haret - headphones completely working into android!
munjeni said:
This is what I'm talking about svn and changes
I have an isue on battery info (#*#*4636*#*#), randomly charging-not charging, also led lamp flashing, but charging work hmmm, maybe you forgot something
Click to expand...
Click to collapse
i had this one too.
=> update to latest release (r127) that was posted one hour ago.
if it's already the case, then sorry but you have to delete your user data (system.ext2, swap, data.ext2) and boot again.
make a backup of your files (SMS, contacts, applications) before!
DmK75 said:
Hi! Thanks for update!
You know about this trick:
Plug headphones and launch FM radio in WinMo, then go to sdcard and launch haret - headphones completely working into android!
Click to expand...
Click to collapse
thanks for the trick!
Hello,
HTC Sync works, but wi-fi doesn't works anymore.
I have done an update (overwrite all except data.ext2) and I don't know if it could be the problem.
asorcinelli said:
Hello,
HTC Sync works, but wi-fi doesn't works anymore.
I have done an update (overwrite all except data.ext2) and I don't know if it could be the problem.
Click to expand...
Click to collapse
yes, that's the problem. wifi module is inside data.ext2, it needs to be updated.
asorcinelli said:
Hello,
HTC Sync works, but wi-fi doesn't works anymore.
I have done an update (overwrite all except data.ext2) and I don't know if it could be the problem.
Click to expand...
Click to collapse
Strangely, I make same (data.ext2 is from previous) but wifi works.
And i moved all files from "andboot" folder to sdcard root.
Related
Continuing my quest of using the LED as flashlight for my new HD2, I updated TorchButton to support the HD2 as well.
Dropped your keys? Finding something behind the bench? Performing surgery on a computer and need to find that jumper on the mainboard?
This is a simple application built for some HTC devices that have a hardware LED, normally used to take pictures in the dark. However I found the LED to be perfect to be used as a handy pocket flashlight.
Usage
There is no GUI for this application. Just start TorchButton to enable the LED on the back of your device. Start TorchButton again to turn it off.
Check out the readme if you're an advanced user and wish to change some registry settings, i.e. to allow a longer maximum time the LED is enabled.
Known issues
- [Fixed] New icons are not working when TorchButton is installed to Storage Card
Todo
- Create an app to configure the registry settings
- See if support for Omnia Pro (B7610) is feasible (someone should send me the related dlls...)
- [Done] Add a seperate timeout for bright mode
- [Done] Add blink mode with bright led
- [Done] Use new icons provided by tnyynt
- [Done] Add support for Omnia (the one found here)
- [Impossible] See if it's possible to control leds seperately ('economic mode') Sorry, this is not possible. (Tech-talk: setting a single GPIO enables both LEDs. There doesn't seem to be a GPIO for each LED seperately.)
Wishful thinking
- Camera app to interpret the morse
History
Version 2.3
- Fix icons not showing in HTC Sense or WM 6.5 start menu when installed to Storage Card.
Version 2.2
- New icons for all TorchButton apps (thanks tnyynt!). These only work in WM6.5 and up. Older OS's will still see the old icons.
- Added registry setting to use bright setting in blink mode (see BlinkUsesBrightMode).
- Bright mode now has a seperate timeout, configurable in registry (see BrightModeTimeout).
- Added support for Samsung Omnia i9x0 devices (hopefully they all work). Thanks to raph/zemrwhite2/PaSSoA. Thanks to Chainfire for testing on his Omnia i900L.
- [edit] Shortcut names have changed. I found them nicer this way, no two-line icons. And the text is now also not cut-off when added as shortcut in the home screen.
- [edit] Improved handling of bright mode. It should stop immediately now when pressed again, instead of waiting for a 500ms interval. This makes BlinkUsesBrightMode possible combined with low intervals for blink mode.
- [edit] Soft-reset your phone after upgrading from an older version! Else the new icons will not show.
Version 2.1
- Bright mode is now support on the HTC HD2 (Leo).
- Added a one-time warning message when bright mode is used for the first time.
Version 2.0
- Initial version with support for the HTC HD2 (Leo) (bright mode is not supported on the Leo)
Version 1.x
- Support for the Touch Pro
Dont think about something. Untill i read your post. This could be handy sometimes. Thnx
Awesome man I was just thinking how I missed that
Btw what's missing for bright mode to work? If I'm not mistaken there is a brighter mode just before taking a pic.
Thanks! I was dissapointed that hTorch didn't work on the HD2 now I got this. Wonderful!
Great ! thanks
Have it on my Omnia and was hoping to have it for my future HD2 !
You're all welcome! Glad to hear you like it.
12aon said:
Awesome man I was just thinking how I missed that
Btw what's missing for bright mode to work? If I'm not mistaken there is a brighter mode just before taking a pic.
Click to expand...
Click to collapse
The mode is there, but it's not as easily called as it was on the Touch Pro. In fact I haven't found the API call at all yet. May need some hacking around the API to get that to work. The normal mode produces _quite_ the amount of light though, it's even more light than the bright mode of the Touch Pro thanks to the dual led.
Zero Masamune said:
Thanks! I was dissapointed that hTorch didn't work on the HD2 now I got this. Wonderful!
Click to expand...
Click to collapse
hTorch will work again once I update the C# wrapper to support the Leo, as hTorch makes use of my C# library. I'll do that somewhere in the upcoming week.
Great, works perfect ! Txs
Can anyone confirm this don't burn anything out? On the X1 the light modules weren't heatsinked properly and caused vibrator motor to screw up after 15secs use as a torch.
Thanks!
kinnyfaifai said:
Can anyone confirm this don't burn anything out? On the X1 the light modules weren't heatsinked properly and caused vibrator motor to screw up after 15secs use as a torch.
Thanks!
Click to expand...
Click to collapse
I can't confirm it won't ever burn out. However, realise that enabling the LED is actually the same as using your camera with the lights on in the dark. This _shoud_ be possible for prolonged times as well.
Were you using the 'bright' setting on the X1? (If that's possible there.) That might explain it better... otherwise you could just send in the device for repair, as it's normal use of the device. Especially if it's after only 15 seconds.
NetRipper said:
I can't confirm it won't ever burn out. However, realise that enabling the LED is actually the same as using your camera with the lights on in the dark. This _shoud_ be possible for prolonged times as well.
Were you using the 'bright' setting on the X1? (If that's possible there.) That might explain it better... otherwise you could just send in the device for repair, as it's normal use of the device. Especially if it's after only 15 seconds.
Click to expand...
Click to collapse
It was a known problem that the LEDs weren't heatsinked properly on the X1 and there was a huge warning on using hTorch. I've not installed hTorch and never used the LEDs on my X1 as a torch cos of this oversight by the manufacturer. I do miss being able to use the LEDs as a torch though, it's very handy.
Heej nice, i come from oud-Beijerland
nice app, but bright mode doesn`t work for me..
NetRipper said:
Continuing my quest of using the LED as flashlight for my new HD2, I updated TorchButton to support the HD2 as well.
Dropped your keys? Finding something behind the bench? Performing surgery on a computer and need to find that jumper on the mainboard?
This is a simple application built for some HTC devices that have a hardware LED, normally used to take pictures in the dark. However I found the LED to be perfect to be used as a handy pocket flashlight.
Usage
There is no GUI for this application. Just start TorchButton to enable the LED on the back of your device. Start TorchButton again to turn it off.
Check out the readme if you're an advanced user and wish to change some registry settings, i.e. to allow a longer maximum time the LED is enabled.
History
Version 2.0
- Initial version with support for the HTC HD2 (Leo) (bright mode is not supported on the Leo)
Version 1.x
- Support for the Touch Pro
Click to expand...
Click to collapse
20mihalko said:
nice app, but bright mode doesn`t work for me..
Click to expand...
Click to collapse
Isn't it clearly stated that brightmode doesn't work.......jeez....dude...read
ET said:
Isn't it clearly stated that brightmode doesn't work.......jeez....dude...read
Click to expand...
Click to collapse
sorry, my mistake
kinnyfaifai said:
It was a known problem that the LEDs weren't heatsinked properly on the X1 and there was a huge warning on using hTorch. I've not installed hTorch and never used the LEDs on my X1 as a torch cos of this oversight by the manufacturer. I do miss being able to use the LEDs as a torch though, it's very handy.
Click to expand...
Click to collapse
The vibrate function does not work at all on my X1 after installing and using hTorch. User beware..!
This is my next phone when O2 decide to put it on their shelves, and hopefully its built better than the X1.
Any chance of some source code?
I've been looking through the HD2 camera drivers, and have found a few things that should be the LED (can't test it as I have no device), but am wondering if it's the same method as yours!
l3v5y said:
Any chance of some source code?
I've been looking through the HD2 camera drivers, and have found a few things that should be the LED (can't test it as I have no device), but am wondering if it's the same method as yours!
Click to expand...
Click to collapse
Here are the important code snippets of the API that I'm using. The methods were pretty obvious (luckily).
typedef int (__stdcall *LEO_INIT)();
typedef int (__stdcall *LEO_SETCURRENT)(DWORD dw1);
...
LEO_INIT InitFlashLight;
LEO_SETCURRENT PMICFlashLED_SetCurrent;
...
hCamera=LoadLibrary(L"CameraPlatform.dll");
...
InitFlashLight = (LEO_INIT) GetProcAddress(hCamera, L"InitFlashLight");
PMICFlashLED_SetCurrent = (LEO_SETCURRENT) GetProcAddress(hCamera, L"PMICFlashLED_SetCurrent");
...
InitFlashLight(); // must be called before SetCurrent has any effect
...
PMICFlashLED_SetCurrent(0); // turns it off
PMICFlashLED_SetCurrent(1); // turns it on
There's also a PMICFlashLED_SetMode(x); but I haven't been able to figure out what it does. As far as I could see when disassembling it wants one parameter.
If you have any ideas on the bright mode, they'd be more than welcome. If you want the full source to make some modifications or to toy with it, let me know.
NetRipper said:
Here are the important code snippets of the API that I'm using. The methods were pretty obvious (luckily).
typedef int (__stdcall *LEO_INIT)();
typedef int (__stdcall *LEO_SETCURRENT)(DWORD dw1);
...
LEO_INIT InitFlashLight;
LEO_SETCURRENT PMICFlashLED_SetCurrent;
...
hCamera=LoadLibrary(L"CameraPlatform.dll");
...
InitFlashLight = (LEO_INIT) GetProcAddress(hCamera, L"InitFlashLight");
PMICFlashLED_SetCurrent = (LEO_SETCURRENT) GetProcAddress(hCamera, L"PMICFlashLED_SetCurrent");
...
InitFlashLight(); // must be called before SetCurrent has any effect
...
PMICFlashLED_SetCurrent(0); // turns it off
PMICFlashLED_SetCurrent(1); // turns it on
There's also a PMICFlashLED_SetMode(x); but I haven't been able to figure out what it does. As far as I could see when disassembling it wants one parameter.
If you have any ideas on the bright mode, they'd be more than welcome. If you want the full source to make some modifications or to toy with it, let me know.
Click to expand...
Click to collapse
That's what I'd come to as a conclusion, so glad that works!
Is there any need to un-init the flash light?
PMICFlashLED_SetMode will probably need some playing around, though might enable your "bright" mode. Will have a play with that when I get an HD2!
l3v5y said:
That's what I'd come to as a conclusion, so glad that works!
Is there any need to un-init the flash light?
PMICFlashLED_SetMode will probably need some playing around, though might enable your "bright" mode. Will have a play with that when I get an HD2!
Click to expand...
Click to collapse
There doesn't seem to be an un-init function. However, the debug console shows that it detects when the DLL is being attached to or detached from, so there's probably some cleanup code there.
I also haven't found any side-effects yet. TorchButton works fine even when the camera app is running. They don't interfere with eachother (other than toggling the LED to their own behalf). On the Touch Pro it wasn't possible to run TorchButton and the camera app at the same time. Not that I ever wanted to, but still.
In regard to that mode function. It must be for something. I tried using it in various ways already but it didn't matter. Maybe you'll have more luck
might be confused right now, but seems that when in camera mode, and battery is below 50% you cant use the flash - anybody know if this will affect the app?
haven't got my hd2 yet so cant help you out, but there's a thread under the Leo -- > Leo sub-forum
cheerios!
Flip4Silence enabled you to flip or shake an incoming call silent! It can also reduce the ringtone volume if you pick up your phone!
Unlike all the other ones I know Flip4Silence do not stress your battery. It's only active when you need it. This got some drawbacks... but hey, it works quiet well!
About "mute via flip/shake":
A friend of mine changed his good old WM6.5 phone into a Android powered device and was annoyed that you can't flip a call silent with a AOSP - now here it is, without the battery stress
About "reduce on pickup":
Someone with an HD2 told me that his phone got this "reduces volume on pick up" feature and I searched the market to find an app for android... Didn't find anything, wrote it myself! Hope you like it too!
Supported android versions: 1.6 and above
Link to Market: Link
Version 1.6.1
- The collection phase is over, thanks everyone for sharing!
Version 1.6.0
- Added "Improve F4S". It would be great if you could help me!
- UI rework
- Maybe fixed "volume not restored" problem
- The fakevibrator used by the "pickup" feature is now stopped when F4S snaps in
Version 1.5.1
- Gingerbread is now supported!
- Fixed 2 rare force closes
Version 1.5.0
- Fixed that "Vibrate only in silent mode" is not a valid mode to enable the pick up volume reducer
- Fixed a bug where the ringer volume is set to early to its normal value
- Fixed the pick up volume reducer behavior
- Fixed shortcut to the audio settings on 1.6
- Added sensitivity settings for the pick up volume reducer
- Added vibration as an option if the pick up volume reducer can't operate
- Minor UI rework
Features:
* flip or shake your phone to mute it (3 modes)
* Pick your phone up from the table and it reduces its volume!
* notifications after hang up (vibration/sound)
* extra battery friendly
Suppoerted modes:
* Mute a call when your phone is laying on its display
* Mute a call when you flip your phone from one side to the oder
* Or mute via a shake
Any feedback/wish/bugreport is welcome!
Will give a try. I've been using Shake2Mute, which is quite similar.
Sent from my HTC Desire using Tapatalk
Version 1.4 is on the market!
Thanks. I wanted this after i saw it on htc.
Sent from my GT-I9000 using XDA App
This wont work on my device: HTC MAGIC, I am confident it has an accelerometer and magnetic sensor because other apps use these features do you have any suggestions?
hayer said:
This wont work on my device: HTC MAGIC, I am confident it has an accelerometer and magnetic sensor because other apps use these features do you have any suggestions?
Click to expand...
Click to collapse
Hm, it seems that something is wrong with the sensorcheck. You are sadly not the only with this issue but the only one who got in contact with me (thanks for this, looking at the comments and see "does not work" is not very nice :/).
I got some questions to investigate this problem:
1) Am I right that the magic is currently on froyo? You got which version?
2) Am I right that a dialog is shown which says "Sorry, no accelerometer and/or magnetic field sensor found"?
3) As you sad other apps are working, which for example (something that uses the phone orientation)?
Currently I have no idea why the code is working on my device (N1) and the milestones I got for testing here...
For the technical people who might have an idea: I'm currently using SensorManager.getDefaultSensor() with the SENSOR_ACCELEROMETER and SENSOR_MAGNETIC_FIELD constants, any idea why this might not work?
Tested on i7500 with 2.2.1 GAOSP.
It lowers the volume when I take it in my hand.
It doesn't mute when flipped.
It does mute when shaked.
Excelent work ! Thanks !
I attached Version 1.4.1 which hopefully fix the issue many people reported. It would be nice if anyone with the message "Sorry your device is unsupported" can try this one and report back how it performs.
hayer said:
This wont work on my device: HTC MAGIC, I am confident it has an accelerometer and magnetic sensor because other apps use these features do you have any suggestions?
Click to expand...
Click to collapse
I finally fixed the issue you reported in version 1.4.3. Thanks for your report!
Luminger said:
I finally fixed the issue you reported in version 1.4.3. Thanks for your report!
Click to expand...
Click to collapse
Thankyou Luminger I appreciate the response and the quick fix and this is now working astoundingly on my magic saved my ass in physics class the other day
Thanks,Luminger, Works great on Moto Qunech XT3...thanks alot...
I've tested it on my LG Optimus One P500.
It works great but there is a little bug.
I have only enabled the option to reduce volume when picking it up. After 1-2 calls, the volume remains lowered. It doesn't come back to normal, I have to raise the ringtone level manual from the hardkeys. Hope you understood.
It is an excelent app ! Thank you !
so it's like one of the feature from HTC Sense, right?
gotta try it when I use clean build with no sense..
Yea, sounds like a bug as F4S should move the volume back to the previous level. I will take a look this evening, thank you for the report!
I really hope that you can fix it.
Thank you !
badeaioan said:
I've tested it on my LG Optimus One P500.
It works great but there is a little bug.
I have only enabled the option to reduce volume when picking it up. After 1-2 calls, the volume remains lowered. It doesn't come back to normal, I have to raise the ringtone level manual from the hardkeys. Hope you understood.
It is an excelent app ! Thank you !
Click to expand...
Click to collapse
badeaioan said:
I really hope that you can fix it.
Thank you !
Click to expand...
Click to collapse
Just wanted to inform you and everyone interested that I'm currently reworking F4S to work around those bugs. Currently I have no clue where this behaviour came from but I think it will be fixed with the rework.
alphadeeto said:
so it's like one of the feature from HTC Sense, right?
gotta try it when I use clean build with no sense..
Click to expand...
Click to collapse
It is suposed to be like the HTC Sense yea, don't know if its working in exact the same way (as I never have seen the Sense config dialog ).
badeaioan said:
I've tested it on my LG Optimus One P500.
It works great but there is a little bug.
I have only enabled the option to reduce volume when picking it up. After 1-2 calls, the volume remains lowered. It doesn't come back to normal, I have to raise the ringtone level manual from the hardkeys. Hope you understood.
It is an excelent app ! Thank you !
Click to expand...
Click to collapse
1.4.4 is out now which should fix your issue. I managed to reproduce the error by accident and reworked the code at this place - seems to be fixed with 1.4.4.
Luminger said:
1.4.4 is out now which should fix your issue. I managed to reproduce the error by accident and reworked the code at this place - seems to be fixed with 1.4.4.
Click to expand...
Click to collapse
1.4.4 appears to keep the "Reduce volume" option always grayed out. That's really the only feature I want from the app, and before this version I had enable flip4silence unchecked and only reduce volume checked.
c00ller said:
1.4.4 appears to keep the "Reduce volume" option always grayed out. That's really the only feature I want from the app, and before this version I had enable flip4silence unchecked and only reduce volume checked.
Click to expand...
Click to collapse
Hm, doesn't sound good...
Are you sure the ringer vibration is off? Off should be the only option F4S accepts.
Did you managed it to get it working when you change the F4S settings ore the vibration settings?
Which device on which version, ROM?
Sorry that I broke it for you, but it's working perfectly on my Nexus One here :-/
Oh, never mind! Somehow my ringer vibration became enabled again before I updated the app. Great app
Hi Photon community,
please find attached a patch to the sensor library.
i tested it on my phone, schlund too, it seems to works well.
if some of you can test it, can you send us feedback if it works better than before?
installation is simple:
unzip install.rar, copy folder "install" to your SDcard root, boot android:
library shall be installed.
this shall fix two issues.
the g-sensor will be fixed soon.
edit: LED keybd fixed, attachement updated.
Thanks! Is this from mahimahi device?
Update:
unzip install.rar, copy folder "update" to your SDcard root, boot android
Thanks Mr r0bin
the sensor worked well, but the light keys not worked
thanks for ur time
I tried and see light keys are always on
after the second attempt,This happened : power button no longer works, seems to be frozen,Press Volume + and power together not working i will need to remove the battery
now I tried a third time and I do not have that problem to freeze, power button works as before.
question: is it normal that after androd booted disappear folder "update" ?
Proximity working perfect, but light sensor I think not, also keypad led not working!
Update:
Ufff sorry, light sensor is perfect also!
Thanks robin&schlund!
now some feedback:
keypad light is working,but just with a lil issue,when screen light goes half off keypad lights are still 100% on(hope you get what i mean)
and also when u click the power button keypad lights are 100% on,and on WM is less.
and one more thing..when they are not touched they need to be half off so we can preserve battery
thanks for your feedback!
yes, LED are not working yet, it needs to be fixed.
15MA1L said:
question: is it normal that after androd booted disappear folder "update" ?
Click to expand...
Click to collapse
yes, it do the update and then auto-delete itself.
Thanks Mr r0bin
works great
munjeni said:
Thanks! Is this from mahimahi device?
Update:
unzip install.rar, copy folder "update" to your SDcard root, boot android
Click to expand...
Click to collapse
There are two update folders after extraction. Copy and paste only the second folder (which also happens to be labelled "update" folder) to your SDCard\ root directory!
update to enable the keyboard led, by schlund:
for those who knows how to use adb, try this:
adb shell
# echo 1 > /sys/class/leds/button-backlight/brightness
Click to expand...
Click to collapse
then, put phone in sleep and activate it. it should work automatic now
-when light is high, light off
-when light is low, light on
tell me if it worked!
-r0bin- said:
update to enable the keyboard led, by schlund:
for those who knows how to use adb, try this:
then, put phone in sleep and activate it. it should work automatic now
-when light is high, light off
-when light is low, light on
tell me if it worked!
Click to expand...
Click to collapse
yes, it work!
DmK75 said:
yes, it work!
Click to expand...
Click to collapse
Thanks DmK75
i updated the light sensor patch (auto-installation), for those who didnt tried yet with adb, please report if it fixed your LED keybd thanks
-r0bin- said:
Thanks DmK75
i updated the light sensor patch (auto-installation), for those who didnt tried yet with adb, please report if it fixed your LED keybd thanks
Click to expand...
Click to collapse
Thanks! Yes, it work one time because after "update" folder auto-deleted.
thanks for update robin!
i have one quick question though: is it possible to fix kepad backlight to dim too,as on WM?
-r0bin- said:
Thanks DmK75
i updated the light sensor patch (auto-installation), for those who didnt tried yet with adb, please report if it fixed your LED keybd thanks
Click to expand...
Click to collapse
I installed the old patch and this one. The LED keybd should light also when it is pressed? Or only when light is low?
By now it do not light at all for me
Thanks work light sensor.
But LED keyboard light is very high not Normal
-r0bin- said:
Thanks DmK75
i updated the light sensor patch (auto-installation), for those who didnt tried yet with adb, please report if it fixed your LED keybd thanks
Click to expand...
Click to collapse
the keypad led still always on after using update-lightsensor-ledkbd
please do less brightness
feedback
just installed a new pach (auto-installation) "update-ligntsensor-ledkbd" then, put phone in sleep and activate it...
the result is: the keypad led still always on
Work on the ROM is now progressing here: http://forum.xda-developers.com/showthread.php?t=1428046
I am no longer updating this OP.
.......
Link to ROM thread: http://forum.xda-developers.com/showthread.php?t=1373449
This is a list of known bugs of the various development ROMs. Features that are missing, such as an FM radio or Preferences in the Launcher, but are not part of the base AOSP, are not considered to be bugs.
Note: I started from b6r1, which was the first version closest to a workable, stable version. Let me know of any corrections or additions.
Apologies (5-Jan-12): I've not been able to keep up with the rate of ROMs produced, so I'm not updating this report until I either have a bit more time (I'm back at work) or the pace slows down a bit. :-(
b8r3.109
- Camera: does not work. Needs driver to be built.
- Display:
o Lockscreen/CRT animation missing.
- Keyboard: Long press on Menu doesn't dismiss keyboard. Partial Fix: Back key dismisses keyboard. Works in other ROMs also.
- Softkeys
o Brightness gets turned off even in low light. Partial Fix: turn off auto brightness. Sleeping will turn off SK brightness and must change brightness to turn them back on.
- Sound: Changing headphone volume changes the system volume.
- Video: effectively unusable. Static images at 240p; will not play above 240p. Workaround:
hyperdude111 said:
Use the Mobo player app in "soft decode mode" to watch video. I can watch smooth 720p .mkv videos through it.
Click to expand...
Click to collapse
b8r2.103
- Camera: does not work. Needs driver to be built.
- Display:
o Fonts get garbled occasionally. ) fixed in b8r3) Fix: comment out the following lines in /system/build.prop:
dev.pm.dyn_samplingrate=1
persist.sys.strictmode.visual=false
ro.screen.layout=normal
o Lockscreen/CRT animation missing.
o Lockscreen rotates, even if Settings/Display/Auto rotate set to No.
- Keyboard: Long press on Menu doesn't dismiss keyboard. Partial Fix: Back key dismisses keyboard. Works in other ROMs also.
- Softkeys
o Brightness gets turned off even in low light. Partial Fix: turn off auto brightness. Sleeping will turn off SK brightness and must change brightness to turn them back on.
- Sound: Changing headphone volume changes the system volume.
- USB Tethering not working
- Video: effectively unusable. Static images at 240p; will not play above 240p.
- WiFi AP/hotspot not working. (fixed in b8r3)
b8r2.100
- Browser: html display is broken, but fix for stock browser only is included. (fixed in b8r2.103) Workaround: use Opera.
- Camera: does not work. Needs driver to be built.
- Display:
o Fonts get garbled occasionally.
o Lockscreen/CRT animation missing.
o Lockscreen rotates, even if Settings/Display/Auto rotate set to No.
- Email: html display is broken. See "Browser". (fixed in b8r2.103) Workaround: use K9.
- Gmail: html display is broken. See "Browser". (fixed in b8r2.103) Workaround: use K9.
- Keyboard: Long press on Menu doesn't dismiss keyboard. Partial Fix: Back key dismisses keyboard. Works in other ROMs also.
- Softkeys
o Brightness gets turned off even in low light. Partial Fix: turn off auto brightness. Sleeping will turn off SK brightness and must change brightness to turn them back on.
- Sound: Changing headphone volume changes the system volume.
- USB Tethering not working
- Video: effectively unusable. Static images at 240p; will not play above 240p.
- WiFi AP/hotspot not working.
b8r1.96
- Browser: display is broken. Bug introduced in b7r1. Workaround: use Opera. (fix for stock browser only in b8r2.100) (fixed in b8r2.103)
- Camera: does not work. Needs driver to be built.
- Display:
o Fonts get garbled occasionally.
o Lockscreen/CRT animation missing.
o Lockscreen rotates, even if Settings/Display/Auto rotate set to No.
- Email: html display is broken. See "Browser". (fixed in b8r2.103) Workaround: use K9.
- Gmail: html display is broken. See "Browser". (fixed in b8r2.103) Workaround: use K9.
- Keyboard: Long press on Menu doesn't dismiss keyboard. Partial Fix: Back key dismisses keyboard. Works in other ROMs also.
- Softkeys
o Brightness gets turned off even in low light. Partial Fix: turn off auto brightness. Sleeping will turn off SK brightness and must change brightness to turn them back on.
- Sound: Changing headphone volume changes the system volume.
- su: problem causes apps requesting super user permissions to freeze or reboots the device. (fixed in b8r2)
- USB Tethering not working
- Video: effectively unusable. Static images at 240p; will not play above 240p.
- WiFi AP/hotspot not working.
b7r1
- Browser: display is broken. Bug introduced in b7r1. (fixed in b8r2) Workaround: use Opera.
- Camera: does not work. Needs driver to be built.
- Display:
o Artefacts seen on the screen after a while, including the lock screen.
o Colour gradients are not smooth (fixed in b8r1).
o Fonts get garbled after a while. Possible fix: try restarting.
o Lock screen rotates, even if Settings/Display/Auto rotate set to No.
- Email: html display is broken. See "Browser". (fixed in b8r2) Workaround: use K9.
- Gmail: html display is broken. See "Browser". (fixed in b8r2) Workaround: use K9.
- Keyboard: Long press on Menu doesn't dismiss keyboard. Partial Fix: Back key dismisses keyboard. Works in other ROMs also.
- Market: FC when accessing an app once Market is auto-updated from 3.1.1. (fixed in b8r1) Fix:
nk111 said:
[...] Delete the following file with a root explorer:
/etc/permissions/android.hardware.nfc.xml [...]
Then reboot
Click to expand...
Click to collapse
Workarounds:
1. Uninstall update in Settings/Apps/All/Market. Will work OK until it is again automatically updated.
2. Install old Market (2.3.6) application from HERE (credits for the tip goes to Mental_Atom). This way you have Market 2.3.6 working and no FCs and it does not update automatically (if you freeze/disable the MarketUpdater that comes with it)
- Softkeys
o Brightness gets turned off even in low light. Partial Fix: turn off auto brightness. Sleeping will turn off SK brightness and must change brightness to turn them back on.
- Sound: Changing headphone volume changes the system volume.
- Taskbar: mobile network indicator does not show H symbol, rather it shows 3G.
- USB Tethering not working
- Video: effectively unusable. Static images at 240p; will not play above 240p.
- Voice Input: only works if you plug in headphones. (fixed in b8r1)
- WiFi AP/hotspot not working.
- Various other things:
o FCs occasionally on various apps, such as System UI, Maps, and others. Includes apps that were ok under b6r1.
o Music stops playing if you delete a file using ES File Explorer.
b6r1
- Camera: does not work. Needs driver to be built.
- Keyboard: Long press on Menu doesn't dismiss keyboard. Partial Fix: Back key dismisses keyboard. Works in other ROMs also.
- Market: FC when accessing an app once Market is auto-updated from 3.1.1. Fix:
nk111 said:
[...] Delete the following file with a root explorer:
/etc/permissions/android.hardware.nfc.xml [...]
Then reboot
Click to expand...
Click to collapse
Workarounds:
1. Uninstall update in Settings/Apps/All/Market. Will work OK until it is again automatically updated.
2. Install old Market (2.3.6) application from HERE (credits for the tip goes to Mental_Atom). This way you have Market 2.3.6 working and no FCs and it does not update automatically (if you freeze/disable the MarketUpdater that comes with it)
- Softkeys: Brightness gets turned off even in low light. Partial Fix: turn off auto brightness. Sleeping will turn off SK brightness and must change brightness to turn them back on.
- Sound: Changing headphone volume changes the system volume.
- USB Tethering not working.
- Video: effectively unusable. Static images at 240p; will not play above 240p.
- Voice Input: doesn't work.
- WiFi AP/hotspot not working.
- Various other things:
o System UI crashes occasionally, as well as some other apps.
o Music stops playing if you delete a file using ES File Explorer.
One info regarding the b7r1 : i have titanium bkp pro apk on my sd and after installing wasn't able to restore aps (it runned all the procedures, mentioned that all apps restored...but nothing).
The other issue : the gradient colours are lost,the background colour is not "fluent" overall.
Great ideea with the dedicated bug report thread, the dev thread was filled with all kind of garbage
Sent from my HTC Desire S using Tapatalk
Sent from my HTC Desire S using Tapatalk
Some additions:
b6r1:
- EGL/full HW accel not working
- market: a workaround is to install OldMarket application from HERE (credits for the tip goes to Mental_Atom). This way you have Market 2.3.6 working and no FCs and it is not updating (if you freeze/disable the MarketUpdater that comes with it)
- USB Thethering not working
- WiFi AP/hotspot not working
cpx07 said:
One info regarding the b7r1 : i have titanium bkp pro apk on my sd and after installing wasn't able to restore aps (it runned all the procedures, mentioned that all apps restored...but nothing).
The other issue : the gradient colours are lost,the background colour is not "fluent" overall.
Great ideea with the dedicated bug report thread, the dev thread was filled with all kind of garbage
Sent from my HTC Desire S using Tapatalk
Sent from my HTC Desire S using Tapatalk
Click to expand...
Click to collapse
Just to add to the gradient comment, deva know of the issue and are working on the bug, but there's no hot fix, so we just gotta wait it out.
To add my own little bug too, I'm finding that now hw accel is in, after a while my phones display gets garbled, particularly the fonts. It was mentioned with a screen shot in the dev thread, but i don't think there'll be a fix until hw accel is better supported.
Sent from my HTC Desire S using XDA App
SolInvictus said:
...
To add my own little bug too, I'm finding that now hw accel is in, after a while my phones display gets garbled, particularly the fonts...
Click to expand...
Click to collapse
Confirm, lock screen was garbled also (I use PIN). After a while in stand by, has a lot of visual artifacts
cpx07 said:
One info regarding the b7r1 : i have titanium bkp pro apk on my sd and after installing wasn't able to restore aps (it runned all the procedures, mentioned that all apps restored...but nothing).
Click to expand...
Click to collapse
I also use TB Pro to restore my apps. It all worked fine.
Can someone else confirm this problem?
Swyped from my HTC Desire S on ICS b7r1 using Tapatalk
update TB to latest version. ICS Support was added in version 4.6.3, so you need a version above that for it to work.
Nice thread!
May i just add that after I've used the phone for a while it almost locks up, pulling down the notification menu takes about 1 minute, and after that if I'm opening the app drawer it takes another minute. Sometimes a reboot solves it, but not always, anyone else experienced this or could it be some application that's not ICS compatible?
Version: b7r1
Radio: 20.48.30.0822U_3822.09.08.20
Installation: Clean install (wipe everything) although i restored a lot of apps (no system apps) with titanium.
Edit: Another bug I found was that i couldn't seem to lower the volume during a call, nothing happened, can anyone confirm?
e2zippo said:
Another bug I found was that i couldn't seem to lower the volume during a call, nothing happened, can anyone confirm?
Click to expand...
Click to collapse
Lowering the volume during a call works for me.
Swyped from my HTC Desire S on ICS b7r1 using Tapatalk
e2zippo said:
Nice thread!
May i just add that after I've used the phone for a while it almost locks up, pulling down the notification menu takes about 1 minute, and after that if I'm opening the app drawer it takes another minute. Sometimes a reboot solves it, but not always, anyone else experienced this or could it be some application that's not ICS compatible?
Edit: Another bug I found was that i couldn't seem to lower the volume during a call, nothing happened, can anyone confirm?
Click to expand...
Click to collapse
None of the issues you've described are present on my phone.
NOTE: When reporting bugs here, it may be useful to specify which beta are you using or on what beta the bug is present. Since we're discussing about both beta 6 and 7, if you just report the bug, can be confusing.
Also due to various configurations, the best way to help and give feedback is to try to reproduce the bug on a clean install (wipe everything then flash the beta). This way the devs might know if the bug is caused by the ROM itself or a specific configuration (that's why some of the bugs are present to all and some just to few of us)
beta7：
1.lock screen rotates even the rotation is disabled (both in preference and display ).
2.sometimes the fonts become garbled , but it could be fixed by a restart .
3.some apps, such as maps, fc randomly, but never occurred with beta 6
4.cant play videos ,and moboplayer doesnt work
Sent from my HTC Desire S using xda premium
Rapier said:
None of the issues you've described are present on my phone.
NOTE: When reporting bugs here, it may be useful to specify which beta are you using or on what beta the bug is present. Since we're discussing about both beta 6 and 7, if you just report the bug, can be confusing.
Also due to various configurations, the best way to help and give feedback is to try to reproduce the bug on a clean install (wipe everything then flash the beta). This way the devs might know if the bug is caused by the ROM itself or a specific configuration (that's why some of the bugs are present to all and some just to few of us)
Click to expand...
Click to collapse
I totally agree, I'll do that with the next beta!
Cheers!
Don't know if it's only me but in beta 7 it seems that the H indicator is broke again. I got only 3G indicator even if with beta 6 I get the H in the same places
I can confirm that the same behavior happens for me.
Swyped from my HTC Desire S on ICS b7r1 using Tapatalk
Rapier said:
Don't know if it's only me but in beta 7 it seems that the H indicator is broke again. I got only 3G indicator even if with beta 6 I get the H in the same places
Click to expand...
Click to collapse
Same for me.
Sent from my HTC Desire S using XDA App
Launcher is not missing anything like preference as you said on b8r1 ...m-deejay built it from pure aosp code so the launcher is the factory android not one that was included in b7 ...
This can be a workaround for that launcher problem .. go to this trebuchet launcher forum.xda-developers.com/showthread.php?t=1410674 download and push it to /system/app then restart select default launcher trebuchet and delete launcher2.apk or whatever from system/app
Thanks for clarifying this. I'll update the OP.
Swyped from my HTC Desire S on ICS b6r1 using Tapatalk
Is the missing FM radio a bug or is that also something that's not in the base AOSP?
Swyped from my HTC Desire S on ICS b6r1 using Tapatalk
BillGoss said:
Is the missing FM radio a bug or is that also something that's not in the base AOSP?
Swyped from my HTC Desire S on ICS b6r1 using Tapatalk
Click to expand...
Click to collapse
might be not sure about that though!
happy new year!
It's finally here ! Oreo for R7 Plus.
https://download.lineageos.org/r7plus
Happy Flashing !
Bugs :
-Double tap to wake not working *FIXED*
-Fingerprint Sensor not working *FIXED*
-Audio stuttering at low volume
rch.aj34 said:
It's finally here ! Oreo for R7 Plus.
https://download.lineageos.org/r7plus
Happy Flashing !
Bugs :
-Double tap to wake not working
-Fingerprint Sensor not working
Click to expand...
Click to collapse
Hooray! Found it! And good to see confirmation that the Fingerprint sensor isn't working.
I can report a Bluetooth bug using Bluetooth headphones. It doesn't matter what app is used and in what environment. The sound is interrupted by a periodic, soft click, followed a nanosecond later by a split second drop off in sound. It's very quick, but noticeable.
Has anyone else noticed this?
If not, if the developer could let me know what files I need to provide to help, I'll gladly provide them
We always report the same bugs snail haha ! there's still the audio stuttering (headphones) issue but i finally found a fix , let me know if you're still having the bug.
rch.aj34 said:
We always report the same bugs snail haha ! there's still the audio stuttering (headphones) issue but i finally found a fix , let me know if you're still having the bug.
Click to expand...
Click to collapse
Haha! I also found this in the [Iron] Maiden Audio app, "Detected problem with app native libraries (libavcodec)", so there might be a codec bug there that's causing the regular dropouts on the wireless phones. It's too disruptive at the moment to tell if the other bug, with wired phones at low volumes, still exists. As I use the phone to compose, the audio issues are problematic. I love Oreo, though.
Are there any developers reading this thread, btw?
And I have issues with the screen not responding when it goes to sleep. I need to hit the power button again to sleep it again and wake it up, but I think that's already been reported.
snaily trail said:
Haha! I also found this in the [Iron] Maiden Audio app, "Detected problem with app native libraries (libavcodec)", so there might be a codec bug there that's causing the regular dropouts on the wireless phones. It's too disruptive at the moment to tell if the other bug, with wired phones at low volumes, still exists. As I use the phone to compose, the audio issues are problematic. I love Oreo, though.
Are there any developers reading this thread, btw?
And I have issues with the screen not responding when it goes to sleep. I need to hit the power button again to sleep it again and wake it up, but I think that's already been reported.
Click to expand...
Click to collapse
I fixed it by downloading a frequency generator app with background playback , set the frequency at 19Hz , and audio is perfectly fine even at 5% volume , i suppose those frequencies are harmless but that's how i fixed it.
as far as screen , double tap to wake is down but hopefully next build it's fixed along with the fingerprint sensor.
rch.aj34 said:
I fixed it by downloading a frequency generator app with background playback , set the frequency at 19Hz , and audio is perfectly fine even at 5% volume , i suppose those frequencies are harmless but that's how i fixed it.
as far as screen , double tap to wake is down but hopefully next build it's fixed along with the fingerprint sensor.
Click to expand...
Click to collapse
Frequency generator app!! Amazeballs!
snaily trail said:
Frequency generator app!! Amazeballs!
Click to expand...
Click to collapse
Yep ! Enjoy your great audio but lack of fingerprint sensor for now hahaha
rch.aj34 said:
Yep ! Enjoy your great audio but lack of fingerprint sensor for now hahaha
Click to expand...
Click to collapse
Except the sound isn't great at the moment! There's also an issue with Norton Password Manager reporting a fault in another API. I'll list it next time it appears
rch.aj34 said:
Yep ! Enjoy your great audio but lack of fingerprint sensor for now hahaha
Click to expand...
Click to collapse
Norton IDSafe has a libvault.so error that might also be non device specific. Very similar to the Bluetooth lib message
snaily trail said:
Norton IDSafe has a libvault.so error that might also be non device specific. Very similar to the Bluetooth lib message
Click to expand...
Click to collapse
Actually i tried the bluetooth in my car and it's perfect , no clicking and much more responsive than lineage 14.
rch.aj34 said:
Actually i tried the bluetooth in my car and it's perfect , no clicking and much more responsive than lineage 14.
Click to expand...
Click to collapse
Oh, bugger!
snaily trail said:
Oh, bugger!
Click to expand...
Click to collapse
I reset the phone and reinstalled 15.1 and Gapps, and the intermittent clicking has disappeared. Something obviously went wrong with the initial installation. So if anyone else has a problem with sound, retrying the fresh install might help. The low volume issue has also gone. The library errors remain for the sound and vault apps, though, so I presume they're non-device specific. And FL Studio is crashing at the end of longer recordings, not saving them in the process, which I think might also be fixed when the library error is addressed.
The wake issue isn't nearly as chronic as it was, either. In fact, I hardly notice it all now. I used the Nano version of Gapps, btw.
snaily trail said:
I reset the phone and reinstalled 15.1 and Gapps, and the intermittent clicking has disappeared. Something obviously went wrong with the initial installation. So if anyone else has a problem with sound, retrying the fresh install might help. The low volume issue has also gone. The library errors remain for the sound and vault apps, though, so I presume they're non-device specific. And FL Studio is crashing at the end of longer recordings, not saving them in the process, which I think might also be fixed when the library error is addressed.
The wake issue isn't nearly as chronic as it was, either. In fact, I hardly notice it all now. I used the Nano version of Gapps, btw.
Click to expand...
Click to collapse
Just upgraded to latest nightly and fingerpint sensor is still dead , i read everywhere that flashing firmware will solve it but no idea how to proceed without losing data.
*BUG Fixed : Double Tap To Wake now working.
rch.aj34 said:
Just upgraded to latest nightly and fingerpint sensor is still dead , i read everywhere that flashing firmware will solve it but no idea how to proceed without losing data.
*BUG Fixed : Double Tap To Wake now working.
Click to expand...
Click to collapse
Expanded desktop still causing havoc. Low audio still produces dreadful stuttering on wired headphones and fingerprint sensor still not there, but it's better. I don't know how to flash the firmware either.
snaily trail said:
Expanded desktop still causing havoc. Low audio still produces dreadful stuttering on wired headphones and fingerprint sensor still not there, but it's better. I don't know how to flash the firmware either.
Click to expand...
Click to collapse
Expanded desktop works perfectly for me. this thread looks like a pm between me and you lol. community dead but so awesome to have 8.1 on the R7 Plus haha.
rch.aj34 said:
Just upgraded to latest nightly and fingerpint sensor is still dead , i read everywhere that flashing firmware will solve it but no idea how to proceed without losing data.
*BUG Fixed : Double Tap To Wake now working.
Click to expand...
Click to collapse
Do you have a link to the information regarding firmware flashing?
rch.aj34 said:
Expanded desktop works perfectly for me. this thread looks like a pm between me and you lol. community dead but so awesome to have 8.1 on the R7 Plus haha.
Click to expand...
Click to collapse
Yep. I'm disappointed the developer hasn't a means of accepting bug reports from users.
I tried this on my r7plusf and wifi does not work. (Australia) Latest 14.1 works and has wifi region selections but 15.1 did not.
steve.rand said:
I tried this on my r7plusf and wifi does not work. (Australia) Latest 14.1 works and has wifi region selections but 15.1 did not.
Click to expand...
Click to collapse
I thought that WiFi should work regardless of the ability to select regions. Perhaps there is another problem. Maybe your persist partition was clobbered in the flashing.