rolled back
[Custom ROM] MYGingerB (Android Gingerbread 2.3.7), Our own Commtiva z71 (mi300) Custom ROM
[Custom ROM] MYGingerB (Android Gingerbread 2.3.7), Our own Commtiva z71 (mi300) Custom ROM
|
|
Oct 4 2011, 09:40 AM
Return to original view | Post
#1
|
![]() ![]() ![]() ![]() ![]()
Senior Member
847 posts Joined: Jan 2011 From: Tenom, North Borneo |
tried your rom, looks promising.. but me touchscreen doesn't work
rolled back |
|
|
|
|
|
Oct 4 2011, 10:45 AM
Return to original view | Post
#2
|
![]() ![]() ![]() ![]() ![]()
Senior Member
847 posts Joined: Jan 2011 From: Tenom, North Borneo |
QUOTE(angelictears @ Oct 4 2011, 10:17 AM) Owh about that, have you imported any keyboard with titanium backup? i can't even touch the droid on startup... so never import nothing or whatsoever I believe that with the new kernel (2.6.35.x) doesn't compatible with any keyboard calibration data, same have happened to other 2.3.7 based rom on other phones The best way would be wipe data,cache and dalvik without reflashing, and walla the touch is working again(it happened to me also Be sure to not import any data from any keyboard app, or any app that included hardware control permission. |
|
|
Oct 4 2011, 11:06 AM
Return to original view | Post
#3
|
![]() ![]() ![]() ![]() ![]()
Senior Member
847 posts Joined: Jan 2011 From: Tenom, North Borneo |
what i've done:
currently using cm7-eav5.1 + #3 kernel wipe data/factory reset wipe cache wipe dalvik install .zip (gingerb) install .zip (gapps) reboot touchscreen doesnt work so back to recovery mode wipe data/factory reset wipe cache wipe dalvik reboot touchscreen still does not work so i restore to my previous rom |
|
|
Oct 4 2011, 02:32 PM
Return to original view | Post
#4
|
![]() ![]() ![]() ![]() ![]()
Senior Member
847 posts Joined: Jan 2011 From: Tenom, North Borneo |
tried your kernel, still wont fix touchscreen problem..
maybe just me using Edgar86's EAv5.1 oh well, just wait for your stable release then |
|
|
Oct 5 2011, 08:27 AM
Return to original view | Post
#5
|
![]() ![]() ![]() ![]() ![]()
Senior Member
847 posts Joined: Jan 2011 From: Tenom, North Borneo |
feedback:tested v1.0 stable, v1.0.1
touchscreen still not working This post has been edited by ralph_d: Oct 5 2011, 09:23 AM |
|
|
Oct 11 2011, 08:55 AM
Return to original view | Post
#6
|
![]() ![]() ![]() ![]() ![]()
Senior Member
847 posts Joined: Jan 2011 From: Tenom, North Borneo |
feedback:
1. needs ad blocker 2. the default gps server is europe.pool.ntp.org, as this is a malaysian rom, why don't set it to my.pool.ntp.org. 3. if can integrate google apps into rom on next release that would be gr8 |
|
|
|
|
|
Oct 13 2011, 12:18 PM
Return to original view | Post
#7
|
![]() ![]() ![]() ![]() ![]()
Senior Member
847 posts Joined: Jan 2011 From: Tenom, North Borneo |
https://market.android.com/details?id=com.Double.FasterFix
to set gps server for those who lazy to korek their dir... |
|
|
Oct 22 2011, 07:15 AM
Return to original view | Post
#8
|
![]() ![]() ![]() ![]() ![]()
Senior Member
847 posts Joined: Jan 2011 From: Tenom, North Borneo |
@angelictears wanna make ice cream sandwich when it was available? jz saw the system req, think u cn handle it?
QUOTE ICS will be a much larger release than any previous Android release. That means that it will also put a much bigger strain on the machines that people use to compile it. As a rule of thumb, everything about ICS in AOSP will be about twice as large as it was for Gingerbread. source: http://www.androidpolice.com/2011/10/21/wa...t-it-will-take/Here are some preliminary numbers. Final numbers will probably be a bit different, but those should be a reasonable first-order approximation. Of course, your mileage may vary. •6GB of download. •25GB disk space to do a single build. •80GB disk space to build all AOSP configs at the same time. •16GB RAM recommended, more preferred, anything less will measurably benefit from using an SSD. •5+ hours of CPU time for a single build, 25+ minutes of wall time, as measured on my workstation (dual-E5620 i.e. 2x quad-core 2.4GHz HT, with 24GB of RAM, no SSD). Naturally, if you plan to work on multiple branches (e.g. ICS release, ICS development branch and AOSP master branch), you need to plan for disk space accordingly, and you could easily end up using 250+GB. This post has been edited by ralph_d: Oct 22 2011, 11:49 AM |
|
|
Apr 7 2012, 09:06 AM
Return to original view | Post
#9
|
![]() ![]() ![]() ![]() ![]()
Senior Member
847 posts Joined: Jan 2011 From: Tenom, North Borneo |
Today probably got sell mi300 dirt cheap price at asia city kota kinabalu.
|
| Change to: | 0.0281sec
0.65
7 queries
GZIP Disabled
Time is now: 3rd December 2025 - 07:08 PM |