Related
Alright. Now that Cyanogenmod has fixed the android.git.kernel.org sync errors, I have continued my CM7 Development (lockscreen stuff for now).
There are currently four new features:
1) Changeable pattern lockscreen size (3x3 - 5x5).
2) Visible dot toggle, for pattern unlock screen.
3) Custom lockscreen message (on normal and keyguard ones).
4) Carrier name change. NOT MINE anymore. Thanks Frederic Van Assche
After I get these problems fixed and setting for all of the features, I will release the mods here, and hopefully into official CM7.
Now for some pictures. See attached (untill i upload). Note: all images are at 180 lcd density (sortof needed for 5x5)
---------- Post added at 01:28 PM ---------- Previous post was at 01:10 PM ----------
Development Section
Im currently really busy with school, so most of the work will be done on the weekends.
Current development status, and todo list.
1) The lockscreen size mod works fine. Few small code cleanup things and stuff needed.
2) The visible dot toggle has a setting and works perfect. The checkbox sometimes doesn't display right so you may have to click it twice to turn it on/off (not sure whats wrong, low priority).
3) Custom lockscreen message works great. Sometimes you have to enable+disable it for it to update (work on auto do/fix). And I haven't added it to the PIN lock and stuff (have to check). In the end I would like the enable/disable and message to be on a different settings screen (like on Honeycomb).
4) And the carrier name thing is now obsolete. Thanks to the patch by Frederic Van Assche, shown to me by one_love_420.
Ohh. And if any of you have any suggestions on things to add or change, i'm happy to listen and try.
Beta Testing.
Current Bugs
Code:
1. Choose pattern size, press back, doesn't revert size (ex: unlock problem from 5x5->3x3)
2. Change lock pattern size. Can't unlock from the actual lockscreen, in settings its fine. (IMPORTANT!)
Fixed by rebooting. Changing to same size is fine
Notes
These builds are buggy. Use at your own risk.
If you cannot unlock your phone, you can fail 5 times and then log in with your google account.
Downloads
http://androtransfer.com/development/smasher816/cm7 beta/
For a better way to do the custom carrier text and to have it in the settings as an option check this over at the gerrit. I have used since he posted it for review and it works great.
http://review.cyanogenmod.com/#change,7314
And
http://review.cyanogenmod.com/#change,7313
Sent from my PG06100 using Tapatalk
Thanks man.
I'm assuming I would run the patch command (git fetch http://review.cyanogenmod.com/p/CyanogenMod/android_frameworks_base refs/changes/14/7314/2 && git format-patch -1 --stdout FETCH_HEAD)
Edit: that seemed to do nothing but output the changes.
I did the checkout one ("git fetch http://review.cyanogenmod.com/p/CyanogenMod/android_frameworks_base refs/changes/14/7314/2 && git checkout FETCH_HEAD") and now it says
Code:
~/android/system/packages/apps/CMParts$ git fetch http://review.cyanogenmod.com/p/CyanogenMod/android_packages_apps_CMParts refs/changes/13/7313/3 && git checkout FETCH_HEAD
From http://review.cyanogenmod.com/p/CyanogenMod/android_packages_apps_CMParts
* branch refs/changes/13/7313/3 -> FETCH_HEAD
Note: checking out 'FETCH_HEAD'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
git checkout -b new_branch_name
HEAD is now at 5ed9b01... Custom carrier label (2/2)
Sorry, i'm still pretty new at git. What do I do now?
I'm new to the git and I do it probably the more difficult way but it gets the job done. What I do is download each change one by one, use "meld" to compare my java/xml files and add the new edits in. Like I said the more difficult way to do it.
Sent from my PG06100 using Tapatalk
Smasher816 said:
Alright. Now that Cyanogenmod has fixed the android.git.kernel.org sync errors, I have continued my CM7 Development (lockscreen stuff for now).
There are currently four new features:
1) Changeable pattern lockscreen size (3x3 - 5x5).
2) Visible dot toggle, for pattern unlock screen.
3) Custom lockscreen message (on normal and keyguard ones).
4) Carrier name change. No setting yet.
After I get these problems fixed and setting for all of the features, I will release the mods here, and hopefully into official CM7.
Now for some pictures. See attached (untill i upload). Note: all images are at 180 lcd density (sortof needed for 5x5)
---------- Post added at 01:28 PM ---------- Previous post was at 01:10 PM ----------
Developer Help Needed Section.
1) For the carrier name replacement I edited
Code:
String plmn = "<WHATEVER>"; //ss.getOperatorAlphaLong();
(line 587) in GsmServiceStateTracker.java. I would like to find a way to add this as a setting to CMParts but haven't looked around enough to figure out how yet. If any of you could hint me in the right way or something that would make my life easier.
2) SOLVED
Click to expand...
Click to collapse
how do we change our pattern size???
maxib123 said:
how do we change our pattern size???
Click to expand...
Click to collapse
If you read, he's developing it. Hence, you can't get it as of this moment.
sixstringsg said:
If you read, he's developing it. Hence, you can't get it as of this moment.
Click to expand...
Click to collapse
sorry, it wasnt that clear first time i read it
If you want a tester btw, you know where to find me
Thanks dude. I was out of town this weekend but started work on getting the pattern size setting more formal and correct.
However my Ubuntu vm decided to not boot.
Edit: fixed it with commands in slax, then in some terminal on ubuntu reboot.
However everything seems to be only. And I can't change the folders permissions due to read only filesystem. Any ideas?
e2fsck /dev/sda2 from root recovery seems to say it was fixed. but continues to not boot, and allowing me to run that command again and again.
If this doesn't get fixed soon. I think I'm gone to attempt to get my edited files from the read only (but bootable) snapshot, and add them back into the last working snapshot.
Smasher816 said:
Thanks dude. I was out of town this weekend but started work on getting the pattern size setting more formal and correct.
However my Ubuntu vm decided to not boot.
Edit: fixed it with commands in slax, then in some terminal on ubuntu reboot.
However everything seems to be only. And I can't change the folders permissions due to read only filesystem. Any ideas?
e2fsck /dev/sda2 from root recovery seems to say it was fixed. but continues to not boot, and allowing me to run that command again and again.
If this doesn't get fixed soon. I think I'm gone to attempt to get my edited files from the read only (but bootable) snapshot, and add them back into the last working snapshot.
Click to expand...
Click to collapse
have you tried chmod 777? if im on the right page, that should work. if not i have no idea mate, sorry
Smasher816 said:
Thanks dude. I was out of town this weekend but started work on getting the pattern size setting more formal and correct.
However my Ubuntu vm decided to not boot.
Edit: fixed it with commands in slax, then in some terminal on ubuntu reboot.
However everything seems to be only. And I can't change the folders permissions due to read only filesystem. Any ideas?
e2fsck /dev/sda2 from root recovery seems to say it was fixed. but continues to not boot, and allowing me to run that command again and again.
If this doesn't get fixed soon. I think I'm gone to attempt to get my edited files from the read only (but bootable) snapshot, and add them back into the last working snapshot.
Click to expand...
Click to collapse
e2fsck -A /dev/sda2
Try that
I ended up getting my read only changes and putting them on my actual computer,
then re doing my VM and melding my changes back in.
I got a backup, and a build made.
However settings crashes (doesn't look like my edits). I will attempt to fix it. Worst comes to worse go back to the good build and merge piece by piece.
Edit: The last two weeks and weekends have been super busy, barely able to turn on my PC. Anyways I got a 4 day weekend coming up, I should hopefully have everything worked out then.
any progress yet?
maxib123 said:
any progress yet?
Click to expand...
Click to collapse
He's got most of the work done, he just needs to get it all merged and get it all up on github. He got distracted by a fun new build system for our kernel.
Edit: Disregard the old information. I now have some freetime over this weekend, the last two weeks have been crazy busy. I am slowly putting my tweaks into the latest nightly and making sure everything is working (vm redo). Anyways the newest build works! - You go to settings -> location and security -> Change Screen Lock -> Confirm saved pattern -> Choose unlock type (pattern) -> Choose pattern size (3-5) -> Draw new pattern (x2).
Where in the settings should the custom lockscreen message be? CMParts -> Lockscreen -> Widget Options -> Custom Message, or Security -> Owner Info (like honeycomb), or somewhere else?
i prefer
CMParts -> Lockscreen -> Widget Options -> Custom Message
Click to expand...
Click to collapse
what i like best about this project is
a) i`ve always wanted a 5*5 unlock pattern
b) you`re working this into the Cyanogenmod Project
Thanks.
Heres a little development update. Im working on getting the 5x5 lockscreen perfect before adding back in the lockscreen message and stuff. The actual 5x5 works fine, all my problems come from the dynamically changing size. Im trying to fix these two important bugs I have found. Hopefully I can get it solved, if not I might upload my work and see if you guys can help me out
Code:
#BUGS#
1. Choose pattern size, press back, doesn't revert size (ex: unlock problem from 5x5->3x3)
2. Change lock pattern size. Can't unlock from the actual lockscreen, in settings its fine. (IMPORTANT!)
Fixed by rebooting. Changing to same size is fine
If your willing to put up with these bugs check the OP.
Is there anyway to add this on to a current build of cyanogen nightly rather than flashing an older one?
Sent from my Nexus One using XDA App
Ummmmm. I edited frameworks/base and packages/apps/Settings
So So replace the Settings.apk and framework folder or something.
This is something,I don't mind testing out. hopefully it'll work on cm7.1
From my fist to your face, enjoy.
WARNING:
This update zip use write mot_boot_mode as shell script to run bootmenu,
don't modify it. otherwise, maybe you will get stop at M logo.
NOTICE: This update zip is ONLY for mb511, if you want to update, please check your stock rom.
If you use this update zip at charm(mb502), is unstable, mb502 and mb511 still has some different.
My STOCK ROM VERSION:
Code:
RUTEM_U3_01.14.16_DEBLUR_SIGNED_USARUTH15ND0RTINT056.0R_PDS000_USARUTHEHKTWEMARA_P011_A010_HWp3_1FF.sbf
If you try to call, but can't hear sound or can't registration of the carrier network, try this ROM version to update RC version.
RC version 5: v0.7.4
configure sources
NOTICE:If you want update fix zip, you should use bootmenu to update.When boot at motologo,click click and click "vol -" to enter bootmenu.
->because bootmenu executed by mot_boot_mode, so /system can't umount, only can remount.
--and update zip have to modify updater-script, remount /system.
[2013/11/13]:
last update:
Seems we can use the command of telnetd to do emergency rescue.
I write telnetd as shell script. It's only to execute bootmenu, if someone modify mot_boot_mode maybe cause bootmenu can't execute.
The telnetd will execute by eclair's init_mapphone30_umts.rc. But it's only can use bootmenu to execute adb to do some things (ex. modify mot_boot_mode).
These days, I try using 2ndboot, but still freeze on hbootmod, I don't know why we can't execute hbootmod.
I can't find anything solution, and can't get more message.
For me, it's hard to debug, I'm not kernel developer. I try to understand the source code of hbootmod, should stuck on do_branch.
But I still can't get any idea to solve this question.
Hope someone can complete it, let we can use new kernel.
RC version 5 should can be a stable version.
[2013/10/04]:
RC version 5:
Seems when I try fix camera, has incorrect modify of sensors. Fix incorrect modify.
write shell script /etc/init.d/07cphostapconf, copy /system/etc/wifi/softap/hostapd.conf to /data/misc/wifi/hostapd.conf
modify updater-script, clear /data/dalvik-cache. if already upgraded previous version update zip, should can direct flash RC5, skip double wipe.
[2013/09/26]:
20130926.zip:
I forget modify configure sources of buttonblink.sh.
old buttonblink.sh file will get bad battery life.
[2013/09/19]:
20130919.zip:
According to this, use smartass is more stable, thanks edgarsongla.
modify init.mapphone30_umts.rc, set smartass as default and delete cpufreq_interactive.ko.
[2013/09/18]:
for traditional chinese user:
fork tcime unofficial for flipout.
upload tcime.apk for flipout.
source code
[2013/09/16]:
baseband:
use and modify cyanogenmod4milestone's configure files of mmparts.
but I'm not do full test, should be ok.
reduce reboot times:
seems wakelock cause reboot, I guess.
these steps maybe can reduce reboot times.
disable wi-fi or don't set wi-fi sleep policy at never.
disable Android debugging.
but maybe still has reboot problem. I can't find solution.
[2013/08/28]:
camera:
use and modify CyanogenKobe's configure of libcamera.
fix part of camera. Take picture is normal, solved rotation 90 degree problem. But video recorder still rotation 90 degree.
wifi:
use stock rom's files.
media:
add libraries of 720p files. but 720p still has problem.
[2013/08/15]:
fix part of magnetic sensor, tested by google map.
modify lights code. when enter standby to check notification, if exist set buttons backlight on.
and if already standby when get notification, set blink and backlight on.
delete /system/etc/init.d/99buttonblink, modify /system/xbin/buttonblink.sh(for enter standby and exist notification use).
[2013/08/08]:
seems write to Android services will get bad use of battery.
so write to /system/etc/init.d/99buttonblink, to start service (check blinking of buttons backlight).
[2013/08/01]:
fix notification blinking of buttons(menu, home and back) backlight.
[2013/07/03]:
find the way to compile tiap_drv.ko
-->if get error, try this command then reboot.
Code:
cp /system/etc/wifi/softap/hostapd.conf /data/misc/wifi/hostapd.conf
modify overlay of auto brightness and notification LED.
[2013/06/26]:
use CyanogenModXT720's libaudio.so, ril should be normal.
use CyanogenModXT720's dsp directory.
get some kernel modules from CyanogenModXT720.
-->seems tiap_drv.ko can use, but still has problem, try to fix in next version.
[2013/06/23]:
define open keyboard of orientation by overlay.
modify BoardConfig.mk.
use cyanogenmod4milestone's apns-conf.xml.
use "mka bacon" to compile cm7.
separate gapps:
-->attachments gapps.zip for bootmenu use.
can work:
camera
battd
fmradio
bluetooth
gps
sensors
usb connect
audio
half work:
video
-> 720p has problem.
wifi
->I only use 2G service, so I can't test softap.
ril
->I only use 2G service, so I can't test 3G.
use mknod to replace mv /dev/xxx
[2013/04/01]:
resume original parameter in init.mapphone30_umts.rc
->symlink /dev /dev/netmux
I don't know why I deleted it...
modify /system/bootmenu/2nd-init/init.rc:
/mnt/sdcard -> /sdcard
modify void.fstab:
/mnt/sdcard -> /sdcard
delete /system/etc/init.d/02movedevice
fix sdcard mount question.
replace files by upload zip, and delete /system/etc/init.d/02movedevice. Or wait release new version.
fix in preview version 2.
In terms of audio recorder, following information may help:
Flipout uses Sample Rate '16KHz' or "22KHz" to record sound, NOT '44KHz'. This is why flipout cannot use skype >_<. If you guys are using a recorder that uses Sample Rate "44KHz" (which almost all recorders set as default Sample Rate), you have to change the setting.
No phone to test
>.<
Sorry guy I can't help
May be I can help to fix this bugs.audio,fmradio,sensors,camera,ril&wifi,look this:https://github.com/xn-Dream/android_device_motorola_sage-1,and you can pm me else.
Seems use mb508's libaudio.so can use video(low quality,landscape orientation) and audio recorder.
-- hard decoding still problem, can use some player (like mxplayer) to play with soft decoding.
-- Spirit FM will be no sound.
-- call phone number still no sound.
[2013/04/02]:recompile cm7 with mb508's libaudio.so
Now we can hear sound from the other side , but the other side can't hear what I say .
But use speaker it's no problem.
sim unlock problem
Hi, first thanks for do this ROM :good:
I install but when start now the system want to give a sim unlock code, I was use before so do u have any idea or something that i have to do to solve this problem
Sorry for my english is not my native language
Best regards
phchshow said:
Seems use mb508's libaudio.so can use video(low quality,landscape orientation) and audio recorder.
-- hard decoding still problem, can use some player (like mxplayer) to play with soft decoding.
-- Spirit FM will be no sound.
-- call phone number still no sound.
[2013/04/02]:recompile cm7 with mb508's libaudio.so
Now we can hear sound from the other side , but the other side can't hear what I say .
But use speaker it's no problem.
Click to expand...
Click to collapse
error log
about 3G
3gw.Service 7225 Mobile Network not connected - not roaming
about codec
Error TIOMX_CORE 2045 dlopen libOMX.TI.720P.Decoder.so failed because Cannot load library: load_library[1111]: Library 'libOMX.TI.720P.Decoder.so' not found
Info TI_Video_Decoder 2045 TI Video Decoder
Error OMXCodec 2045 Profile and/or level exceed the decoder's capabilities.
Error MediaPlayer 16597 error (1, -2147483648)
Error MediaPlayer 16597 Error (1,-2147483648)
Error MX.Player.Joint 16597 1st error: what=1 extra=-2147483648
Use 508 libOMX.TI.720P.Decoder.so put into system/lib
Error OMXCodec 2048 [OMX.TI.720P.Decoder] ERROR(0x80001009, 1)
I'm impressed that you finally got it working, but i have a evil kind of Bug around here!
The Play Store vanishes every Reboot, Titanium says it is Frozen and im unable to unfreeze it.
If i can i would provide a logcat in the next hours!
Anyway, awesome to finally see 2.3.7 on MB511 ^^
//EDIT: I connected the Device with the Internet, now it is working fine ^^
everything is working except that when phone reboot version is still 2.1 and nothing changed :/
adout keylayout:
unzip keylayout.zip
--init.mapphone30_umts.rc
--init_prep_keypad.sh
to /system/bootmenu/2nd-init/
chmod 0644 /system/bootmenu/2nd-init/init.mapphone30_umts.rc
chmod 0755 /system/bootmenu/2nd-init/init_prep_keypad.sh
Integrate to fix-20130413.zip.
phchshow said:
adout keylayout:
unzip keylayout.zip
--init.mapphone30_umts.rc
--init_prep_keypad.sh
to /system/bootmenu/2nd-init/
chmod 0644 /system/bootmenu/2nd-init/init.mapphone30_umts.rc
chmod 0755 /system/bootmenu/2nd-init/init_prep_keypad.sh
Click to expand...
Click to collapse
Is This QWERTZ?
Should be QWERTY.
There are two files, ruthp0-keypad.kl and ruthp1-keypad.kl.
use this command
"cat /proc/device-tree/[email protected]/[email protected]/name"
My device get ruthp1-keypad.
If you want to use QWERTZ, you can try replace ruthp0-keypad.kl, ruthp1-keypad.kl, ruthp0-keypad.kcm.bin and ruthp1-keypad.kcm.bin.
Get from QWERTZ version.
ShockBuddy said:
Is This QWERTZ?
Click to expand...
Click to collapse
Maybe can solved Turn on USB storage problem.
Integrate to fix-20130413.zip.
if replug usb, maybe has problem, use killall com.motorola.usb to reset usb.
Hi to all,
Thanks to all that are working on this rom.
Since both models are merged in the same post because the same hardware, I wonder if I can deploy this rom into a Motorola Charm, or if I got to make changes on code, I guess at least have to change some files where refers to 511 to 512, and where refers "Ruth" to "Charm".
What other changes should I do to make this model work?
Thanx for response.
Please help
Please help me, How do i do to work because i have not service,
The problem is SIM NETWOR UNLOCK PIN
Please HELP!!!!
just the key pad related files, I was unable to compile this ROM from source using charm files, I think an update file to replace keypad files with charm should do the trick.
I shall try it and let you know.
there are so many attachments here
please put them into #1
Great job, men!
netmanmac said:
Please help me, How do i do to work because i have not service,
The problem is SIM NETWOR UNLOCK PIN
Please HELP!!!!
Click to expand...
Click to collapse
I dont have the Issue and i haven't inserted any SIM Card, it should be enough to reboot without Sim Card.
If you get to Homescreen, use a Root Explorer and edit /system/build.prop, check if
Code:
keyguard.no_require_sim=xyz
is set to "false", if it isn't in there, add it!
Hope i helped :fingers-crossed:
finally installed.is the screen orientation working good?when i flip out the keyboard the screen orientation remains protrait,pretty annoying!anyway great job,never though i'd have seen cm on flipout!love this device,unlike any other
Hi everybody,
I work on a light Launcher (to replace Launcher2.apk).
One of my objectives is obviously to have a quick boot.
But when my app is ready to show something, the bootanimation is still visible until the Boot timeout (40s after the first log):
WindowManager: ***** BOOT TIMEOUT: forcing display enabled
If I reboot with my command line :
adb reboot && adb wait-for-device && adb shell setprop service.bootanim.exit 1
My boot time is around 15s but with a bad rotation display until I receive the first ConfigurationChanged event. Without this point, the app is ready so...
Question 1: Do you know a way to properly close the boot animation?
Question 2: If the Q1 don't solve the ConfigurationChanged event, do you know a method to receive the ConfigurationChanged event in my Launcher?
Best Regards,
Kikiwa
PS : I hope this topic is in the right section, sorry if it's not the case.
Same problem
kikiwa said:
Hi everybody,
I work on a light Launcher (to replace Launcher2.apk).
One of my objectives is obviously to have a quick boot.
But when my app is ready to show something, the bootanimation is still visible until the Boot timeout (40s after the first log):
WindowManager: ***** BOOT TIMEOUT: forcing display enabled
If I reboot with my command line :
adb reboot && adb wait-for-device && adb shell setprop service.bootanim.exit 1
My boot time is around 15s but with a bad rotation display until I receive the first ConfigurationChanged event. Without this point, the app is ready so...
Question 1: Do you know a way to properly close the boot animation?
Question 2: If the Q1 don't solve the ConfigurationChanged event, do you know a method to receive the ConfigurationChanged event in my Launcher?
Best Regards,
Kikiwa
PS : I hope this topic is in the right section, sorry if it's not the case.
Click to expand...
Click to collapse
I am having the same problem , have you found any solution?
Hello !
Sorry but no. I'm still interested by the solution BTW.
Good luck
Kikiwa
kikiwa said:
Hello !
Sorry but no. I'm still interested by the solution BTW.
Good luck
Kikiwa
Click to expand...
Click to collapse
In my case I pushed my custom launcher apk to system/app and deleted launcher2.apk
Could it be that the system is waiting for some special response from default launcher? That should be made in custom luancher?
Possible Solution
Hey guys,
I was having this same issue for a while now, and I finally found a solution that works for me, at least as of Android 4.4.4 on a Nexus 7 2013 (LTE)
What I did to find this was selectively disable system apps one by one, and then test a reboot.
In my case, disabling Launcher2 didn't affect the boot sequence, but SystemUI (com.android.systemui) did cause these delayed boot times.
I dug through the ASOP source code, and found that the WindowManagerService performs a few checks in performEnableScreen() before stopping boot animation / displaying normally:
- System services must all be ready (mSystemBooted)
- A keyguard or application must be attached to Window Manager (haveApp || haveKeyguard)
- The Wallpaper Service must be disabled or ready (!wallpaperEnabled || haveWallpaper)
Since monitoring logcat showed my replacement launcher was open, and the system services had no errors, I suspected #3 was the problem
In the source for SystemUI, I found a single reference for "wallpaper" - com.android.systemui.ImageWallpaper is an included class that extends WallpaperService but itself is never referenced from that package.
Checking logcat again, I found these lines:
Code:
Attempted wallpaper ComponentInfo{com.android.systemui/com.android.systemui.ImageWallpaper} is unavailable
Default wallpaper component not found!
It turns out that the system-level WallpaperManagerService has hard-coded that particular class.
As a test fix, I created a new project with package name "com.android.systemui" and a single class "ImageWallpaper" that extends WallpaperService, declared this as a service in my manifest, and installed this apk on a device.
I rebooted, and the boot times were back to normal (~20sec) instead of the previous ~50sec.
So in summary: SystemUI was the culprit in my case; creating a fake replacement package with that hardcoded class back in fixed the long boot times.
Thank you
dtyler7 said:
Hey guys,
I was having this same issue for a while now, and I finally found a solution that works for me, at least as of Android 4.4.4 on a Nexus 7 2013 (LTE)
What I did to find this was selectively disable system apps one by one, and then test a reboot.
In my case, disabling Launcher2 didn't affect the boot sequence, but SystemUI (com.android.systemui) did cause these delayed boot times.
I dug through the ASOP source code, and found that the WindowManagerService performs a few checks in performEnableScreen() before stopping boot animation / displaying normally:
- System services must all be ready (mSystemBooted)
- A keyguard or application must be attached to Window Manager (haveApp || haveKeyguard)
- The Wallpaper Service must be disabled or ready (!wallpaperEnabled || haveWallpaper)
Since monitoring logcat showed my replacement launcher was open, and the system services had no errors, I suspected #3 was the problem
In the source for SystemUI, I found a single reference for "wallpaper" - com.android.systemui.ImageWallpaper is an included class that extends WallpaperService but itself is never referenced from that package.
Checking logcat again, I found these lines:
Code:
Attempted wallpaper ComponentInfo{com.android.systemui/com.android.systemui.ImageWallpaper} is unavailable
Default wallpaper component not found!
It turns out that the system-level WallpaperManagerService has hard-coded that particular class.
As a test fix, I created a new project with package name "com.android.systemui" and a single class "ImageWallpaper" that extends WallpaperService, declared this as a service in my manifest, and installed this apk on a device.
I rebooted, and the boot times were back to normal (~20sec) instead of the previous ~50sec.
So in summary: SystemUI was the culprit in my case; creating a fake replacement package with that hardcoded class back in fixed the long boot times.
Click to expand...
Click to collapse
It is exactly my problem and your solution seems perfect
Thank you for your efforts
command "setprop ctl.start bootanim" to perform boot animation;
command "setprop ctl.stop bootanim" stop the boot animation.
DON'T FORGET TO HIT THE THANKS BUTTON
!!!DISCLAIMER!!!!
You are solely responsible for whatever shtuff happens to your device by installing either of the two files to your device.
!!!DISCLAIMER END!!!
So this still needs a lot of work but I am providing a working boot.img and root filesystem archive for all Nexus 9 variants? (not sure needs others to test and confirm).
Will be edited as things start working
What's working:
WiFi. (Must use 'nmcli dev wifi con "SSID" password "passwd" ')
GPU @ anywhere from 900-2000 FPS
Sound works just needs reconfiguring
Screen rotation works best with minimal issues as desktop taskbar widgets command to turn clockwise into landscape:
Code:
sudo xrandr -o right; sudo xinput set-prop 7 "Evdev Axis Inversion" 0, 1; sudo xinput set-prop 7 "Evdev Axes Swap" 1
&
Code:
sudo xrandr -o right; sudo xinput set-prop 7 "Evdev Axis Inversion" 0, 0; sudo xinput set-prop 7 "Evdev Axes Swap" 0
For normal portrait orientation
However DO NOT USE THE DISPLAY SETTINGS TO ROTATE IT MESSES UP THE LOGIN ROTATION AND SCREEN GOES BLACK AND SOMETIMES SHOW BACK UP IN LANDSCAPE AND WILL NOT DEFAULT BACK INTO PORTRAIT ORIENTATION. SO YOU MUST DO IT MANUALLY!!!!! See screenshot below
Swipe gestures (Chromium-browser only).
Bluetooth: WORKING!!! Install package bluetooth-touch and set this command into a shell script or enter manually the ENTIRE string:
Code:
brcm_patchram_plus --enable_hci --use_baudrate_for_download --scopcm=0,2,0,0,0,0,0,0,0,0 --baudrate 3000000 --patchram /lib/firmware/bcm4354.hcd --no2bytes --enable_lpm --tosleep=50000 /dev/ttyTHS2
Also using a Bluetooth audio sink works by itself without keyboard connected. I've found it still needs work but, connecting to a keyboard still flawless in its function file transfer locks it up when sending not receiving. Pairing and connecting are all good but functionality of Bluetooth is down to one device at a time for best results
What's not working:
Cameras (Neither front nor rear camera works at all. Needs work).
NFC? (I have no idea how to check for this. Needs work).
Probably other things I missed.
What you will need:
Any Nexus 9 with an unlocked bootloader & latest TWRP recovery installed
USB keyboard
OTG cable
Instructions:
MAKE A BACKUP! Just in case.
1.) Enter into recovery go to wipe and format Data partition as Ext4
2.) Reboot into recovery and with the boot.img and rootfs on a flash drive or, push them to device via ADB.
3.) Go to terminal command in recovery issue the commands: cd /data; mkdir linux; cd linux
4.) tar xvjf /sdcard/rootfs.tar.bz2 -C /data/linux
5.) Flash N9boot.img with install image in TWRP Install submenu.
6.) Reboot into the new Linux system.
7.) If the Kernel panics and boot loops, go back into recovery and format the data partition again it will ask are you sure type yes & repeat steps 2-4
You will need to use a USB keyboard & OTG cable to install the necessary packages and connect to WiFi/Bluetooth.
It's much easier to install on device than in a chroot environment as I have had problems in the past. And some people have different favorite Desktop Environment's. However Gnome and KDE both do not work correctly and crash.
Fluxbox, Mate, XFCE, LXDE, all work as they should with Lightdm.
If there's anything I missed you can add it below, PM me and ask, whatever and I'll try to answer as soon as I am able.
If you are interested in building the entire thing from start to finish here are the original sources
https://forum.xda-developers.com/nexus-9/general/guide-linux-nexus-9-t2985958
https://forum.xda-developers.com/nexus-9/general/guide-linux-nexus-9-t2985958/page14
And thanks to @sonicadvance1 for his original guide & @Vartom for his work on porting some of the necessary Kernel drivers. And @Vartom again for his contributions to the Bluetooth and everything else to get us this far :good::good::good::good::good::good::good::good:
Xubuntu-Desktop Preinstalled 21.5 Drivers 1GB username=ubuntu password=ubuntu
https://drive.google.com/open?id=0B8NgGANYGMhOZS1OenNzZl94bEE
rootfs base only necessary packages root password=toor
https://drive.google.com/file/d/0B8NgGANYGMhOMjVObElVVnBWamM/view?usp=drivesdk
boot.img
https://drive.google.com/open?id=0B8NgGANYGMhOZXAwZHVrUUotZ0k
In order to get the preinstalled to fix login if having issues use the command as root in virtual terminal Ctrl+Alt+F1/F2, etc
Code:
chown ubuntu:ubuntu /home/ubuntu
.
This should fix the login issues, if you want you can create a different user and remove the premade user using these commands as root in virtual terminal.
Code:
deluser username
adduser username
addgroup username adm
addgroup username sudo
Additionally if you have an error when running glxgears there is a fix
Code:
xauth list
It should output something similar to this
Code:
localhost.localdomain/unix:0 MIT-MAGIC-COOKIE-1 a4f6256398303725763c5595f404afbb
You will need to export the display and add that MIT-MAGIC-COOKIE you got from xauth list
Code:
export DISPLAY=":0"; xauth add $DISPLAY . a4f6256398303725763c5595f404afbb
This should fix the display error.
And finally,
Enjoy Ubuntu on your Nexus 9
Video of it booting
https://youtu.be/PIGm47pwzj0
Booted fine.... However a username and password would help...lol
---------- Post added at 10:30 PM ---------- Previous post was at 09:45 PM ----------
andyroidking said:
Booted fine.... However a username and password would help...lol
Click to expand...
Click to collapse
Found the root password in the other thread. toor
Now on to getting wifi up so i can get a de installed....
Reserved
andyroidking said:
Booted fine.... However a username and password would help...lol
---------- Post added at 10:30 PM ---------- Previous post was at 09:45 PM ----------
Found the root password in the other thread. toor
Now on to getting wifi up so i can get a de installed....
Click to expand...
Click to collapse
sk1tch said:
Ha! Sorry I updated the guide above to include that little tidbit of info. Sweet I'm excited to read it worked so far. Hope the guide is simple enough for everybody who wants to try it out
Click to expand...
Click to collapse
Yeah now that I got wifi working I'm off to study how to get xfce4 installed. Everyone says Arch is hard but I'll tell you their repo's are extensive. Now I have to learn about ppa's...
Also, I'm over 50 and because we have a 2048 x 1536 display everything is very tiny making all of this more of a challenge... I tried a couple things to bump the font size but they don't work....
andyroidking said:
Yeah now that I got wifi working I'm off to study how to get xfce4 installed. Everyone says Arch is hard but I'll tell you their repo's are extensive. Now I have to learn about ppa's...
Also, I'm over 50 and because we have a 2048 x 1536 display everything is very tiny making all of this more of a challenge... I tried a couple things to bump the font size but they don't work....
Click to expand...
Click to collapse
I knew you were old school. I did get Arch Linux running on the original guide but it was choppy at best and only ran in the framebuffer but this was the aarch64 version. I do think it could be done because it's my preferred distro these days as well. I think we'd have to change a few things in the CPIO init scripts.. You know point to what it needs but, that's a little too advanced for me.
Also try setting a custom dpi in the settings menu if you're using XFCE I know there's the option there
and to install it you need to uncomment all the extra repos in /etc/apt/sources.list then do apt update && apt install xubuntu-desktop
it should look like in the picture
Well, I'm stuck. X won't start... I'll have to pull the log and see what up. Unfortunately I'm back to work tonight so it will be a while before I get to play again. Don't fret, I'll be back. :silly:
Edit: Pulled logs:
As root user:
https://pastebin.com/3bJE7HkJ
As reg user:
https://pastebin.com/ZVBrCAuM
They look the same to me...
andyroidking said:
Well, I'm stuck. X won't start... I'll have to pull the log and see what up. Unfortunately I'm back to work tonight so it will be a while before I get to play again. Don't fret, I'll be back. :silly:
Edit: Pulled logs:
As root user:
https://pastebin.com/3bJE7HkJ
As reg user:
https://pastebin.com/ZVBrCAuM
They look the same to me...
Click to expand...
Click to collapse
They look identical to me as well. Um try apt install xorg xubuntu-desktop lightdm-gtk-greeter.
then reboot it should automatically enable it with systemd while installing
Error 404
The links to the downloads are no longer working.
sk1tch said:
They look identical to me as well. Um try apt install xorg xubuntu-desktop lightdm-gtk-greeter.
then reboot it should automatically enable it with systemd while installing
Click to expand...
Click to collapse
I'll give that a shot. Sounds like solid advice. Probably not until Thursday or Saturday. Busy week kids back to school
a such...
humannequin777 said:
The links to the downloads are no longer working.
Click to expand...
Click to collapse
I fixed the links but the rootfs.tar.bz2 is down as I am uploading a preinstalled image archive with the XFCE4 DE w/ onscreen keyboard, still ironing out Bluetooth made good progress so hopefully I will have that finished soon
Cameras are not included in the kernel. I did not check their performance in this kernel.
Linux Inside... Nice. Well I found a few minutes and got this far.... https://imgur.com/a/VuDEN Xauthority issue? I'll check into it later. I assume suspend doesn't work? I tried once but didn't want to crash it right now. also changed scroll bar width... easier to tap. Border width is next.
Scroll bar width:
Open the .gtkrc-2.0 file, add the following to a new line starting at the bottom of the file:
Code:
style "myscrollbar"
{
GtkScrollbar::slider-width=XX
}
class "GtkScrollbar" style "myscrollbar"
How's the performance ?
Can I use it as a desktop?
Yes indeed it does work as a desktop I got screen rotation down to two three command scripts with desktop widgets. Most things work as of now Bluetooth sucks no matter what I do but, touchscreen works fine WiFi works fine no Cameras yet Sound only through headset. Hardware acceleration works at anywhere from 800 FPS - 2000 FPS. Videos like on YouTube stutter a little if you are doing other things while watching. Swipe gestures work in Chromium browser only. (Still working on installing multifunction swipe gestures) Your best bet would be to buy one of those $11 Micro-B USB wired tablet keyboards or just use the Onboard keyboard if its already in a rugged case or whatever. Those two green arrows at the top of the desktop are my rotate widgets
andyroidking said:
Linux Inside... Nice. Well I found a few minutes and got this far.... https://imgur.com/a/VuDEN Xauthority issue? I'll check into it later. I assume suspend doesn't work? I tried once but didn't want to crash it right now. also changed scroll bar width... easier to tap. Border width is next.
Scroll bar width:
Open the .gtkrc-2.0 file, add the following to a new line starting at the bottom of the file:
Click to expand...
Click to collapse
Yes there is an .Xauthority error when I flashed it as well that was why I said it's difficult to make a working install and that it was easier to install on device but either try chown ubuntu:ubuntu /home/ubuntu as root and it may fix your issue or you have to create a new user
Vartom said:
Cameras are not included in the kernel. I did not check their performance in this kernel.
Click to expand...
Click to collapse
I added the configs for the camera to my custom config to no avail... I dont have a headset jack debug cable so I can't see what going on during boot
sk1tch said:
I added the configs for the camera to my custom config to no avail... I dont have a headset jack debug cable so I can't see what going on during boot
Click to expand...
Click to collapse
Porting the cameras was not 100% complete. Therefore, simply adding lines to the config is not enough.
---------- Post added at 02:14 PM ---------- Previous post was at 02:08 PM ----------
Porting the cameras was not 100% complete. Therefore, simply adding lines to the config is not enough.
For bluetooth work, you need to download the corresponding firmware.
with some similar string
exec /usr/sbin/brcm_patchram_plus --enable_hci --use_baudrate_for_download --scopcm=0,2,0,0,0,0,0,0,0,0 --baudrate 3000000 --patchram /lib/firmware/bcm4324.hcd --no2bytes --enable_lpm --tosleep=50000 /dev/ttyTHS2
this can be added to the nvwifibt.conf config file.
Vartom said:
Porting the cameras was not 100% complete. Therefore, simply adding lines to the config is not enough.
---------- Post added at 02:14 PM ---------- Previous post was at 02:08 PM ----------
Porting the cameras was not 100% complete. Therefore, simply adding lines to the config is not enough.
For bluetooth work, you need to download the corresponding firmware.
with some similar string
exec /usr/sbin/brcm_patchram_plus --enable_hci --use_baudrate_for_download --scopcm=0,2,0,0,0,0,0,0,0,0 --baudrate 3000000 --patchram /lib/firmware/bcm4324.hcd --no2bytes --enable_lpm --tosleep=50000 /dev/ttyTHS2
this can be added to the nvwifibt.conf config file.
Click to expand...
Click to collapse
So just add this too the sbin config file??
sk1tch said:
So just add this too the sbin config file??
Click to expand...
Click to collapse
brcm_patchram_plus this package was not found. Add it to the fast failed.
Since I originally wrote this I have found an even easier way that works 100% without root using Setting database editor so I've updated this guide to the better method.
as a few of us 2XL owners will know Google derped sounds on the factory image of Q and our nice charging sound has been replaced with a horrible Error sound (Google Bug tracker.)
after a few weeks of waiting & trying to fix the issue myself I have finally managed to figure it out...
turns out they're trying to access sounds from the WRONG location
UI sounds on factory Q image seem to trigger from /product/media/audio/ui but this directory only has boot animations, no audio as these files are actually located in /system/media/audio/ui
it's probably why upgrading from 9 to 10 keeps the audio settings but factory flashing doesn't.
https://play.google.com/store/apps/details?id=by4a.setedit22
Install the settings database editor (link above)
Code:
open a terminal app and type(or copy paste) the line below;
pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
or using adb:
Code:
adb shell
pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
using setedit go to the global tab and look for each of the UI audio settings, switch /product/media/audio*.* to /system/media/audio/*.*
Restart your phone to apply the settings.
car_dock_sound /system/media/audio/ui/Dock.ogg
car_undock_sound /system/media/audio/ui/Undock.ogg
desk_dock_sound /system/media/audio/ui/Dock.ogg
desk_undock_sound /system/media/audio/ui/Undock.ogg
lock_sound /system/media/audio/ui/Lock.ogg
low_battery_sound /system/media/audio/ui/LowBattery.ogg
trusted_sound /system/media/audio/ui/Trusted.ogg
unlock_sound /system/media/audio/ui/Unlock.ogg
wireless_charging_started_sound /system/media/audio/ui/ChargingStarted.ogg
Minor notes:
I'm unsure why the charging sound is dictated by wireless_charging setting.
I've had a report that settings revert after a few reboots, I've not had this myself and I've rebooted a lot but if it happens just reapply the changes in setedit.
You can also change the sounds to files on your system, I've not had luck pinpointing my sdcard folder but I have been able to change Lock.ogg to Dock.ogg as a test.
(/Sdcard/download didn't work)
_________( Old method )_________
This is my first write up so please bear with me
please note I'm not responsible for any messups you make doing this
it can be done on a terminal emulator, I prefer ADB shell
in order to sucessfully do this you will need HiddenSettings magisk module
Thank you skittles9823
I'm unsure if you need busybox but the module certainly looks for it
Code:
[B][COLOR="red"]adb shell[/COLOR][/B] or launch your [I]TerminalApp[/I]
taimen:/ $[B][COLOR="red"]su[/COLOR][/B]
taimen:/ [I]#[/I] [B][COLOR="red"]hidden[/COLOR][/B]
4 - All settings
[CHOICE]:[B][COLOR="red"]4[/COLOR][/B]
3 - Modify settings
[CHOICE]:[B][COLOR="red"]3[/COLOR][/B]
===== Modify Settings =====
[Search?]:[B][COLOR="Red"]wireless_charging_started_sound /system/media/audio/ui/ChargingStarted.ogg[/COLOR][/B]
press enter & reboot your phone.
That is pretty much it, hopfully the android team fix this next patch.
I'll add some notes from what I have found through tinkering
you must reboot after modifying EACH setting.
you can see the "=" is not added when changing the settings wireless_charging_started_sound=/system/media/audio/ui/ChargingStarted.ogg (wrong)
wireless_charging_started_sound /system/media/audio/ui/ChargingStarted.ogg (Right)
Here are all the settings i can find
car_dock_sound /system/media/audio/ui/Dock.ogg
car_undock_sound /system/media/audio/ui/Undock.ogg
desk_dock_sound /system/media/audio/ui/Dock.ogg
desk_undock_sound /system/media/audio/ui/Undock.ogg
lock_sound /system/media/audio/ui/Lock.ogg (this causes an error on my phone)
low_battery_sound /system/media/audio/ui/LowBattery.ogg
trusted_sound /system/media/audio/ui/Trusted.ogg
unlock_sound /system/media/audio/ui/Unlock.ogg
wireless_charging_started_sound /system/media/audio/ui/ChargingStarted.ogg
Awesome job figuring this out. Hopefully Google will fix this in the November system images since You've done all the work for them.
Great job and thanks for it, so this works with the charging sound issue but not the locking/unlocking sound?, As for the charging sound i already have a workaround for it as i have gravitybox and edxposed installed and gravitybox have a option to change charging sound, hoepfully google will fix both in upcoming noember update
Nightf0x_007 said:
Great job and thanks for it, so this works with the charging sound issue but not the locking/unlocking sound?, As for the charging sound i already have a workaround for it as i have gravitybox and edxposed installed and gravitybox have a option to change charging sound, hoepfully google will fix both in upcoming noember update
Click to expand...
Click to collapse
I have found an even easier way that works 100% using setedit:
https://play.google.com/store/apps/details?id=by4a.setedit22
Install the app open a terminal app
pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
Job done easier to edit
Out of habit I typed su to enable root before granting write permissions so if it doesn't work without enabling su try that
co4 said:
I have found an even easier way that works 100% using setedit:
https://play.google.com/store/apps/details?id=by4a.setedit22
Install the app open a terminal app
pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
Job done easier to edit
Out of habit I typed su to enable root before granting write permissions so if it doesn't work without enabling su try that
Click to expand...
Click to collapse
Does settings revert back after multiple reboots ? Cause this happened to me
Nightf0x_007 said:
Does settings revert back after multiple reboots ? Cause this happened to me
Click to expand...
Click to collapse
I've yet to have anything revert yet if it does happen I'll post, I guess you can reapply the settings? Or once they revert can they be re changed?
Awesome it worked I have all my sounds back!!!!
krolla03 said:
Awesome it worked I have all my sounds back!!!!
Click to expand...
Click to collapse
I'll add that it's been reported that setting may revert and reapplying will fix it again
co4 said:
I'll add that it's been reported that setting may revert and reapplying will fix it again
Click to expand...
Click to collapse
so far so good
Thank you SOOO much! :highfive: It works on my Pixel 2. Had to reset it to factory after the December update killed my Pixel launcher app. After the reset I faced this horrible charging sound and the lack of lock sounds, too.
God this was driving me crazy on a warranty replacement Pixel 2. 3rd replacement and finally it boots and the battery is decent.
I don't know if I would have noticed but for having 2 phones side by side. After that, I couldn't un-hear it.
What about Effect_tick.ogg? Is there any way to set this custom sound?
Hi,
I've tried the first method, but I couldn't grant permissions in the Terminal app, it fails!
I don't have root.
Can anyone help?
Thank you so much
All these sounds work on my Pixel 1, but I get the error sound whenever I get a notification while in call. Does anybody know where I can find that sound? It's not in SetEdit.
Mandrutz said:
All these sounds work on my Pixel 1, but I get the error sound whenever I get a notification while in call. Does anybody know where I can find that sound? It's not in SetEdit.
Click to expand...
Click to collapse
I have this also on my pixel 2 does anyone know the ADB script for that?