Какой рейтинг вас больше интересует?
|
Главная / Главные темы / Тэг «consent»
Google Android bugs and CM7 RC4 2011-03-31 05:39:33
This is a quick followup to my previous post on this topic. First bug mentioned by me (#3106: screen ...
+ развернуть текст сохранённая копия
This is a quick followup to my previous post on this topic. First bug mentioned by me (#3106: screen fails to refresh or goes black aka Android issue #15135) is now fixed in both Google AOSP repository and in CyanogenMod. Apparently it was the reason to roll out RC4.
/me likes.
Тэги: android, bug, cyanogenmod, google, nexus, one
CyanogenMod 7 RC3 Nexus One major issues 2011-03-29 01:56:07
These two issues are show-stoppers for "normal" people wishing to use CyanogenMod on their Nexus ...
+ развернуть текст сохранённая копия
These two issues are show-stoppers for "normal" people wishing to use CyanogenMod on their Nexus Ones, and I hope they will be fixed before CM7 goes final. Both bugs looks to be upstream ones, i.e. they are not born in CyanogenMod team but in Google itself.
(1) #3106: screen fails to refresh or goes black; logs say "/dev/pmem: no more pmem available" -> "OutOfResourcesException locking surface". This one is an upstream bug, see Android issue #15135. The only known workaround is to reboot, I am testing a solution (modified lib) suggested here.
(2) Call wonkiness. I heard that it's an upstream bug as well (a problem in a driver). Workaround: install the dewonkificator app.
On the good side, a kernel bug which made it lost 45-60 seconds of time every day (aka issue #1222) is now fixed. Kernel is doing a good work accurately keeping time.
Generally, I wish Google Android guys could've paid more attention to quality assurance. Yes, I know, nobody is perfect, and QA is rocket science (indeed it is, and a gap between good and very good is huge), but still I see a room for improvement here. I am very happy with their pace of innovation, but the tendency to trade quality for speed can ruin the whole effort easily.
For other (not so major) bugs I faced recently, see my blog post about a bug in browser find dialog and my patch fixing a bad glitch with keyboard layout. These two are not critical, although the first one is misleading and the second one can be very annoying, and they both are examples of bad UI QA.
Wake up, Android, if you want to keep eating apples for breakfast!
Тэги: android, bug, cyanogenmod, google, nexus, one, wtf
cm translation tips and tricks 2011-03-22 10:57:21
# Remove an (unused) string from translations (check the result with git diff!): ...
+ развернуть текст сохранённая копия
# Remove an (unused) string from translations (check the result with git diff!):
STR="widget_max_buttons"; for f in $(grep -rlwF $STR *); do sed -i "/$STR/d" $f; done
# Find out what strings are missing from the (ru) translation (compared to English one) # Strings that start with - are to be removed, with + are to be added.
fgrep '<string name="' res/values/strings.xml | \ fgrep -v 'translatable="false"' | \ sed 's/^[^"]*"\([^"]*\)".*$/\1/' | sort > en fgrep '<string name="' res/values-ru/strings.xml | fgrep -v 'translatable="false"' | \ sed 's/^[^"]*"\([^"]*\)".*$/\1/' | sort > ru diff -U 0 ru en | grep '^[+-][^+-]'
Тэги: cyanogenmod, howto, linux
Google Nexus One radio image vs AT&T 3G 2011-03-16 01:34:14
I am mostly using my Nexus One here in Moscow, Russia, and have "Use only 2G networks" option turned ...
+ развернуть текст сохранённая копия
I am mostly using my Nexus One here in Moscow, Russia, and have "Use only 2G networks" option turned on in Settings / Wireless & networks / Mobile networks for two reasons: first, it really improves battery life, second, my data plan is 220 RUR (about $8) per month flat rate unlimited, but shaped down to not exceed 128 kbps (so anything faster than EDGE won't improve my Internet speed. It perfectly suits my mobile needs (email, browsing, gtalk, Yandex and Google maps for traffic info and navigation, occasional photo upload), for everything else I have Wi-Fi in the office and at home.
So when updating my N1 to an alpha build of CyanogenMod 7 I flashed the latest radio firmware, version 5.12.00.08 (also known as Korean) and was happy with it. Until the day I came to US (for SCaLE) and started using my US number (naturally, by replacing my SIM card with a corporate AT&T SIM). I found out three things:
1. GPRS/EDGE from AT&T is crappy, it's barely working (at least in the areas I've been to, like LAX).
2. AT&T 3G is not working at all with this radio (version 5.12.00.08).
3. I am not able to flash the earlier radio image (version 5.08.00.04) using current ClockworkMod Recovery, version 3.0.0.5 (they dropped support for some old-style update scripts format which radio images are apparently using). I tried getting radio image from a couple of different sources (xda-developers, cyanogenmod wiki) to no avail.
So, I was aware what exactly the problem was, but didn't have enough time (or will) to solve it while in the USA.
I solved it tonight in 10 minutes, using nothing else than the phone (ie no need for a PC). Here's how (assuming you are using ROM Manager).
1. Go to ROM Manager, choose "Install alternative recovery (RA v2.2.1)". This will replace CWM 3 with Amon_RA 2 which understands old update scripts.
2. Repeat step 1 one more time (for some reason flashing for the first time lead to non-working recovery, although there's no error or warning). Do not worry, just flash it again.
3. Choose "Install ROM from SD card" and navigate to your downloaded radio image (my was in /sdcard/download). Ignore the warning about not using CWM.
4. Phone will reboot, flash, reboot, do something, reboot. If you will find yourself in some scary text-only menu, just select the "reboot" (following the on-screen instructions about how to select it).
5. Go to Settings / About, check the number under "Baseband version", it should be what you've just flashed.
6. Go to ROM Manager, select "Flash ClockworkMod recovery" to return back to CWM. You might need to do it twice, too, as in step 2.
Links to radio images: * http://wiki.cyanogenmod.com/index.php?title=Nexus_One:_Full_Update_Guide#Flashing_Radio * http://forum.xda-developers.com/showthread.php?t=723839
Hope that helps.
Posted via LjBeetle
Тэги: android, cyanogenmod, google, howto, linux, megafon, nexus, one
cm7 nightlies gapps trouble 2011-03-06 05:48:21
Решил, раз не сплю, накатить в свой телефон свежий CM7 (билд #12 от 3 марта -- новее почему-то нет). ...
+ развернуть текст сохранённая копия
Решил, раз не сплю, накатить в свой телефон свежий CM7 (билд #12 от 3 марта -- новее почему-то нет). До этого там стояло что-то с датой в середине февраля. Накатил (благо с ROM Manager это делается на раз-два, то есть в несколько кликов). После апдейта перестали работать market, gmail, gtalk.
Почистил (отформатировал, через CWM recovery menu) /cache. Не помогло.
Выполнил fix permissions (там у каждого приложения свой uid/gid и файлы данных должны принадлежать ему -- иногда, почему-то, это сбивается) -- тоже с помощью ROM Manager. Не помогло.
Перенакатил gapps. Помогло лишь отчасти -- маркет открылся, но gmail и youtube продолжали делать FC (force close, что-то вроде SEGFAULT).
И тут я сделал гениальную по своей простоте вещь -- деинсталлировал gmail и youtube и поставил их заново. Помогло!
PS я знаю, что помогает сделать wipe /data, но уж очень не хотелось прибегать к таким радикальным мерам. PPS я знаю, что это напоминает войну с неработающим Линуксом, но надо учесть, что это nightly build неофициального форка Андроида -- нормальные люди такой bleeding edge себе не ставят, конечно, и у них всё работает.
Тэги: android, cyanogenmod, google, linux, nexus, one
Главная / Главные темы / Тэг «consent»
|
Взлеты Топ 5
Падения Топ 5
|