Closed GoogleCodeExporter closed 8 years ago
Quote: (From xerxes86 via XDA-Developers)
Hello Brian,
your work is great. You are a real lifesaver.
After my old old old phone broke down I grabbed the X1 out of a box and when I
remembered its windows mobile I nearly broke down.
But due to your work the phone really works out.
So, THANK YOU SO MUCH.
Two days ago I only knew the terms HSPL, Bootloader, Kernel and ROM from
hearsay due to your work and the tutorial, on which I already posted a little
feedback, I know a little bit more today.
Now I want to give you a little feedback as well:
Problems:
Hardware keys: I have the same problems as so many others. The Hardware keys
stop working sometimes. Sometimes after a few minutes. Sometime everything is
fine for hours and hours. I couldn't figure out a patern jet. But I hope and
already read that there are already people working on the problem.
Battery: I dont know if this is only at my device but I have a problem with my
Battery. I charge it to 100%. After disconnecting from the power supply it
rappidly goes down until it reaches around 13% to 14%. At this point you might
figure that my Battery is broken but it stays at 14% for hours! Yesterday it
stayed there for almost 6 hours.
WLAN: This kind of plays into the one above. When I check the Battery Status it
says that the WLAN used up a minimum of 50% of the
Battery. I figure this is quite a lot. Because its more than the Display.
Ideas/suggestions:
Swipe: I think that swype in combination with the x1 pen might be something
worth to consider.
Kalender: Is it possible to include the new google calender from the bginning?
googleplay: Might be more of a problem. I am not sure but I often do not get a
connection to google-play while connected per wlan. Also I have the feeling
that app-downloads get stuck quite often. But I have to keep an eye on both for
a more time.
Thats all for the moment.
Hope you dont mind my wall of text,
Thanks for your work again.
xerxes
EDIT: Almost forgot, I am using the Build 2012.11.10!
Original comment by BrianXP7
on 13 Nov 2012 at 7:16
I fully acknowledge the same situation with the buttons.
"Hardware keys: I have the same problems as so many others. The Hardware keys
stop working sometimes. Sometimes after a few minutes. Sometime everything is
fine for hours and hours"
Complied with all the instructions, rebooted the phone, the problem is not
resolved in this way
"We can use "aShell + aSQLiteManager apps" for enhancing the screen off/on
performance and to solve some hardware keys problem. So install both apps and
after open aShell and check "Root" in the main screen, after click on "File
Explorer" and go to "/data/data/com.android.providers.settings/settings.db", so
click on "settings.db" to open it and select aSQLiteManager, now go to
"system", then to "Data" and "PageDown" to know the last ID number created and
finally click on "New". So, we just have to add three new records to "system"
table:
electron_beam_animation_off=0
electron_beam_animation_on=0
lockscreen_disabled=1
(NOTE: "_id" is the one you like after the ones already created,
"electron_beam_animation" is the name and "0" is the value and so on) "
Original comment by romanc...@gmail.com
on 10 Dec 2012 at 8:56
with broken hardware keyboard, plugged charging usb, and the hardware key to
start working again.
Original comment by romanc...@gmail.com
on 12 Dec 2012 at 5:56
I'd also like to add this also applies to the optical joystick. It seems that's
more common to occur but difficult to notice.
Original comment by BrianXP7
on 13 Dec 2012 at 9:08
I have made some changes to the microp-keyboard interrupt handler. It may
resolve the lost keys bug. Could you try the latest boot.img file in the file
list and test it.
Original comment by tor...@gmail.com
on 3 Jan 2013 at 9:19
Sure, when I have time. I sort of lost my SD card. This may take a while.
Original comment by BrianXP7
on 3 Jan 2013 at 10:08
Original comment by BrianXP7
on 7 Jan 2013 at 9:11
after upgrading the kernel, I have no more problems
Original comment by romanc...@gmail.com
on 11 Jan 2013 at 7:32
Yeah, the issue seems to be fixed. I'll mark it as "Fixed" now.
Original comment by BrianXP7
on 11 Jan 2013 at 9:17
Original issue reported on code.google.com by
BrianXP7
on 13 Nov 2012 at 7:10