Q&A for [ROM][EXP] AOSP Lollipop 5.0 for Evo 3D - November 12
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][EXP] AOSP Lollipop 5.0 for Evo 3D - November 12. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Good job! It's looked very sexy :fingers-crossed::fingers-crossed::fingers-crossed:
Awesome!!!
Gapps
Hi, I got a problem with gapps. I tried 4.4 gapps and cyanogenmod 12 gapps. Everytime I boot there is an error saying process *.wizard has failed. Basically all google services fail. So what gapps should I use. Thank you Hahaburger for this rom which works fine without gapps.
flashed
Hi, i flashed this rom earlier today and now I am stuck. when the phone turns on it tells me in a different language then english roughly translated "sorry but wizard application for settings has quit" and when i click OK the same message pops up. it just repeats. when I shut off and enter bootloader using the power and volume down buttons and try to go to recovery to restore the phone just shuts off which i can not turn back on without taking out the battery. HELP ME i am stuck. what can i do to fix this or restore back to a previous build
i did a full wipe, flashed this rom, then supersu.
after that i manually installed some apps via adb.
so far my experience has been very good considering this early stage of development!
its running smooth, no major problems so far, even the flashlight is working (although System-UI fcs when i activate it)
after a full day of light usage (no calls, no sms) only using wifi for chat/mail/browser and installing some apps, i still have over 80% left.
but when i try to call someone i just get an error saying something like "call not connected."
Here is a logcat: pastebin com /ZrbZTGtL
i think the error happens around these lines:
80. Telephony( 752): TelephonyConnectionService: Could not get subId from account: E
115. PhoneInterfaceManager( 752): [PhoneIntfMgr] getIccId: ICC ID is null or empty.
+ some more like the last one
---------- Post added at 07:53 PM ---------- Previous post was at 07:31 PM ----------
here is a logcat of the flashlight crashing System-UI
pastebin com /tsusu00p
i think it has to do with the camera not working yet but here are some errors:
D/QualcommCameraHardware3D( 189): getBuffersAndStartPreview: setPreviewWindow(320 x 240), iTotalBufferCount 5, mIs3DModeOn: 0
E/ ( 133): unrecognized pixel format: 0xf0
E/ ( 133): Format 240
W/GraphicBufferAllocator( 133): alloc(115200, 76800, 240, 00000100, ...) failed -22 (Invalid argument)
E/ ( 133): GraphicBufferAlloc::createGraphicBuffer(w=115200, h=76800) failed (Invalid argument), handle=0x0
E/BufferQueueProducer( 1281): [unnamed-1281-1] dequeueBuffer: createGraphicBuffer failed
E/QualcommCameraHardware3D( 189): getBuffersAndStartPreview: dequeueBuffer failed for preview buffer. Error = FFFFFFEA
Click to expand...
Click to collapse
the funny thing is i can hear the camera making shutter noises, so it's at least doing something with the camera
echs said:
i did a full wipe, flashed this rom, then supersu.
after that i manually installed some apps via adb.
so far my experience has been very good considering this early stage of development!
its running smooth, no major problems so far, even the flashlight is working (although System-UI fcs when i activate it)
after a full day of light usage (no calls, no sms) only using wifi for chat/mail/browser and installing some apps, i still have over 80% left.
but when i try to call someone i just get an error saying something like "call not connected."
Here is a logcat: pastebin com /ZrbZTGtL
i think the error happens around these lines:
80. Telephony( 752): TelephonyConnectionService: Could not get subId from account: E
115. PhoneInterfaceManager( 752): [PhoneIntfMgr] getIccId: ICC ID is null or empty.
+ some more like the last one
---------- Post added at 07:53 PM ---------- Previous post was at 07:31 PM ----------
here is a logcat of the flashlight crashing System-UI
pastebin com /tsusu00p
i think it has to do with the camera not working yet but here are some errors:
the funny thing is i can hear the camera making shutter noises, so it's at least doing something with the camera
Click to expand...
Click to collapse
@HaHaBuRGeR
echs said:
80. Telephony( 752): TelephonyConnectionService: Could not get subId from account: E
115. PhoneInterfaceManager( 752): [PhoneIntfMgr] getIccId: ICC ID is null or empty.
+ some more like the last one
Click to expand...
Click to collapse
Thanks for detailed explanation and logcats . I'm aware of this erros.
I'm trying to debug rild to find problems. Also for camera it seems codec error.
I'll look at that too after mobile data. And I can make calls I don't really know why you can't.
Are you using usim? If you would like to test more please send me a PM.
@HaHaBuRGeR:
i don't know how to find out if i have an USIM. according to some older posts regarding my provider all newer sims should be USIM.
i found some code examples but in most cases CDMA was detected as a USIM and GPRS as SIM.
on the sim card i have the letters UJ, the U should be for a USIM card but i'm not sure.. i'd guess its an USIM.
sms are working fine (sending and receiving).
i could receive calls and they were working fine.
but i still cannot make outgoing calls. USSD codes also aren't working.
btw: i got almost 48hours of uptime with no major errors, it's gonna be a fine rom!
still waiting for data, atm thats more important to me.
oh and i cannot send PMs until i have 10 posts...
Google PlayStore problem
I really like your ROM, have used it for week...
I have the last release - working (call, sms, headphones) ok and fast, but I'm not able to install apss from store (I got unknown error code 972 ).
I used the GApps from here: https://s.basketbuild.com/gapps . Which GApps are recommended for you ROM?
cajda77 said:
I really like your ROM, have used it for week...
I have the last release - working (call, sms, headphones) ok and fast, but I'm not able to install apss from store (I got unknown error code 972 ).
I used the GApps from here: https://s.basketbuild.com/gapps . Which GApps are recommended for you ROM?
Click to expand...
Click to collapse
Weird, I'm using same GApps for testing. Have you wiped your data partition before installing the ROM?
HaHaBuRGeR said:
Weird, I'm using same GApps for testing. Have you wiped your data partition before installing the ROM?
Click to expand...
Click to collapse
Yes, I'did.
I'll try tommorow again (the whole flash process) just to be sure. I don't know how to provide you more info...I'll try to look in syslog.
cajda77 said:
Yes, I'did.
I'll try tommorow again (the whole flash process) just to be sure. I don't know how to provide you more info...I'll try to look in syslog.
Click to expand...
Click to collapse
You can install and use adb to give me logs about errors. Here is a tutorial about how to use it http://forum.xda-developers.com/showthread.php?t=1726238
Unfortunate that this a GSM ROM because I'm on CDMA so I could possibly help out
Sent from my Evo 3D CDMA
HaHaBuRGeR said:
You can install and use adb to give me logs about errors. Here is a tutorial about how to use it http://forum.xda-developers.com/showthread.php?t=1726238
Click to expand...
Click to collapse
Probably the problem was that I used old recovery for flashing (TWRT, CWM), I got some errors. Today I have used the PhilZ Touch from here: http://forum.xda-developers.com/showthread.php?t=2764698 and GooglePlay installing apps seems to be working.
Thanks
Interesting! Seeing I still use my HTC Evo 3D as my daily driver, I'm going to try to work on a L version for CDMA and probably start here.
This would be my first try doing anything ROM related in terms of development, so it'll be interesting for me. I wish you luck in getting this thing into a daily driver on this old device . At least we are not forgotten!
No_file contexts
No_file contexts everytime I try to install it? On latest build It just stays on installing update.. adn nothing happens latest CWM recovery I really want to istall it
When I try to install the SELinux-disabled kernel I get this message in the photo. Is it normal? Flashing finishes OK, but when I reboot I still have no su access. I must mention that I have installed this ROM in dual-boot, so recovery sees my primary ROM environment which is ICS.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Oppo Find 7a X9007 with rare/no GSM/3G reception
ergün
ergün kardeş bana face adresini versene sormam gereken şeyler varda.
dreccon said:
When I try to install the SELinux-disabled kernel I get this message in the photo. Is it normal? Flashing finishes OK, but when I reboot I still have no su access. I must mention that I have installed this ROM in dual-boot, so recovery sees my primary ROM environment which is ICS.
Sent from my Oppo Find 7a X9007 with rare/no GSM/3G reception
Click to expand...
Click to collapse
I have no idea for dual-boot but we don't need SELinux disabled kernel anymore for using su command. You can just flash superSU's latest version, it works well.
Related
Добро пожаловать, друзья! Welcome, Friends! आपका स्वागत है, दोस्तों! Benvenuti, amici!
Bem-vindos, amigos! Ласкаво просимо, друзі! Bine ati venit, prieteni! 欢迎 朋友们
Vítejte, přátelé! chào đón, bạn bè! Willkommen, Freunde! Bienvenidos, amigos!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The latest CyanogenMod Nightly can be downloaded here or via ROMManager.
The new recovery in ROMManager (5.0.2.7) is not required, but is necessary to receive automatic updates.
Changelog
[I'm not going to provide my own changelog as all updates to CM7.2 are minor bugfixes only...]
Other necessary files: Google Apps (Also available in ROMManager)
night·ly /ˈnaɪtli/
adj.
Of or pertaining to the night, or to every night; happening or done by night, or every night.
A Fresh CyanogenMod ROM automatically built with the newest available code, usually compiled at night. Often contains many bugs.
Click to expand...
Click to collapse
This is the place to discuss the CyanogenMod nightlies. Feel free to talk about anything related to these ROMS, but to receive acknowledgement by a developer of any problems you find, the following conditions should be met:
Use the stock CyanogenMod kernel
Do not overclock
Use the default system apps (launcher etc.)
Do not use apps2sd or similar
Before posting a problem you should:
Check the posts below for a solution / fix
Read the last 10 pages of this thread for a post with a similar problem
Backup, reflash with a full wipe, check if the bug is still there
Wait 24 hours for the next nightly, the devs probably already know about it
If the problem still persists after the next nighlty appears and all the above steps have been followed, post your problem and we'll see if there is something we can do. Please include the following information:
Which Nightly you are running
Which Nightly the bug first appeared (if known)
*Confirm Stock Everything* (shows that you have read all the above)
Detailed steps to reproduce the bug (add a screenshot if it helps)
OLD BASEBAND?
If your phone uses the old baseband, you need to upgrade to the new baseband. This improves 3G signal and battery life. There are many guides on how to do this so just have a quick look around, or even watch a video on Youtube.
NO-APN PROBLEMS?
All APN problems related to 'funny SIMs' have been fixed, please thank werewolfo for generously donating an Italian funny SIM for me to test with!.
Major improvements include:
New baseband support
Better 3G Reception
.35 kernel support (only)
Offline charging
Quicker GPS lock
Smoother Accelerometers
Better 3G signal
Better battery life
CyanogenMod Updates
Mik is back?! Yeah!!!
Greets!
mDroidd said:
Mik is back?! Yeah!!!
Greets!
Click to expand...
Click to collapse
Really great news,I agree.
@adfad: Didn't know rmcc had a new whole p500 stuffs,thanks for the advices brother.
Aside from no data on T-Mobile UK, everything else seems to work fine.
People with data problems: Can you provide a radio logcat output please, the command you want is:
Code:
adb logcat -b radio
copy the output to http://pastebin.com/ and add the link here
Thanks!
digitalface said:
Aside from no data on T-Mobile UK, everything else seems to work fine.
Click to expand...
Click to collapse
One guy from dev thread suggested to flash baseband from latest official ROM for your country, may be that can help
He said:
"hey guys, try downloading the official gingerbread from vodafone in .kdz, extract the baseband from that rom and use it in your rom. If you don't know how, PM me."
Here is the link:
http://forum.xda-developers.com/showthread.php?p=21370547
@adfad
What do you think about that bug:Call settings/additional settings doesn't work. An error "network or Sim card error" occurs. This works in official roms and doesn't work in mik's 6.5.8 too.
lerkin said:
One guy from dev thread suggested to flash baseband from latest official ROM for your country, may be that can help
He said:
"hey guys, try downloading the official gingerbread from vodafone in .kdz, extract the baseband from that rom and use it in your rom. If you don't know how, PM me."
Here is the link:
http://forum.xda-developers.com/showthread.php?p=21370547
Sent from my LG-P500
Click to expand...
Click to collapse
It shouldn't make a difference, especially since it's been reported roms based on official LG gingerbread work with the same baseband
lerkin said:
What do you think about that bug:Call settings/additional settings doesn't work. An error "network or Sim card error" occurs. This works in official roms and doesn't work in mik's 6.5.8 too.
Click to expand...
Click to collapse
I've noted it, but the main bug should be to get this network problem sorted out. Just need to get some logcat readings as described above
Logcat
Logcat with WiFi enabled:
pastebin.com/735b5cz1
Logcat with GSM enabled:
pastebin.com/A1V0hZ2P
Sorry, I can't post links because I have not enough posts yet.
btw: great rom, thx for your work
Edit: Nightly 1, nothing changed
OS:Nightly full-1
*Camera... oops! AM I wrong or my phone or gallery started to take photos or and recording movies by 90 degrees counter-clockwise? That's strange behavior...
Too many resolutions in photo camera... maybe i am wrong but i never seen 1080p and 720p types in CMcamera
Here is my logcat (E-Plus Germany) calls are working, mobile data doesn't work.
http://pastebin.com/EvWRuxsz
homepage32 said:
Logcat with GSM enabled:
pastebin.com/A1V0hZ2P
Click to expand...
Click to collapse
Kaerper said:
Herese is my logcat (E-Plus Germany) calls are working, mobile data doesn't work.
http://pastebin.com/EvWRuxsz
Click to expand...
Click to collapse
Thanks, now can you do provide me with a full logcat from boot please. Switch it off, then back on and wait until the lock screen comes on and the screen times out and switches off.
(not the command from above, just a regular adb logcat)
Hope this is what you want...
http://pastebin.com/LAGXwC88
lerkin said:
What do you think about that bug:Call settings/additional settings doesn't work. An error "network or Sim card error" occurs. This works in official roms and doesn't work in mik's 6.5.8 too.
Click to expand...
Click to collapse
The problem is a CyanogenMod problem. Someone has already submitted some patches recently, I've tested them and they work fine so they should be merged very soon.
I encounter a pretty annoying bug with outgoing/incoming calls. I cannot hang up after the phone after the conversation. I get a a blackscreen. When the other person at the other end hangs up the sound comes on to say call has been disconnected. After this, you cannot use your phone. pushing and holding the power key only makes your buttons (on the phone) flash. You have to remove battery and reboot in order to fix the problem.
Nightly: #1.
Kaerper said:
Hope this is what you want...
http://pastebin.com/LAGXwC88
Click to expand...
Click to collapse
Hmm nothing funny there either. I'll need to see the logcat of the radio again but from boot (1st command again). It scrolls pretty quick sometimes so try to get it all from the very beginning.
edit - this might be easier:
Code:
adb logcat -b radio > logcat.txt
switch the phone off, run the command BEFORE you switch the phone on (it'll say waiting for device) then switch the phone on and wait until you see the lock screen. you won't see anything on the screen, it saves it all to the logcat.txt file.
press ctrl + C to quit adb and paste the content of the file
ScripterJR said:
I encounter a pretty annoying bug with outgoing/incoming calls. I cannot hang up after the phone after the conversation. I get a a blackscreen. When the other person at the other end hangs up the sound comes on to say call has been disconnected. After this, you cannot use your phone. pushing and holding the power key only makes your buttons (on the phone) flash. You have to remove battery and reboot in order to fix the problem.
Nightly: #1.
Click to expand...
Click to collapse
The proximity sensor driver needed updating in the kernel, it's already fixed and will be in Nightly #2. However there is a fix, plug the phone in to charge and it comes back to life!
Is this going to stay on new baseband? I just don't see the need in upgrading baseband if mobile data doesn't work
Sent from my LG-P500 using xda premium
Markox89 CyanogenMod 13 Builds
Help Thread
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please read the FAQ before asking any questions.
It is quite possible your question may have already been answered. Otherwise you may help me improve that section! :highfive:
I'd like to separate questions from the main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by myself. Thanks for understanding and for helping to keep XDA neat and tidy!
Welcome to the my builds' help thread! You can ask all questions here without the need of background knowledge. This thread is dedicated to solve users problems, so if you don't want to start a new thread for your question, ask it here. Members ready to help will be monitoring this thread and provide answers as soon as possible.
To those seeking help: Please don't write PMs asking for help. Instead, ask your question here in the thread so others can benefit from the solution to your problem as well. If you want to be sure someone particular gets notified of your question, put his / her username directly after an @. Also, if you have ROM related questions, post in the relevant ROM Q&A thread (if there is one) or directly in the ROM development thread. If you are not eligible of posting there, you may post here. Thank you!
ROM developers: Please read this. Consider if you want to have a ROM specific help thread or not, if not, most likely questions about your ROM will be asked here if the users aren't eligible for posting in development section.
To all of you: Remember the Rules and the Forum Etiquette.
Hi,i want to install this rom with new archi kernel,but i dont know whic version,ak 1.5.1 aosp or 1.5.1 aosp r4p0...i am knew here ...sorry for bad english
tandrcak90 said:
Hi,i want to install this rom with new archi kernel,but i dont know whic version,ak 1.5.1 aosp or 1.5.1 aosp r4p0...i am knew here ...sorry for bad english
Click to expand...
Click to collapse
1.5.1 AOSP
One+one cm11s lockscreen works well. Just flash the zip and reboot.
Thread link
http://forum.xda-developers.com/oneplus-one/themes-apps/oneplus-one-lockscreen-t2815737
Unstable CM11 build
I'm using the latest (2014-11-02) CM11 build for I9300. I have the following issues:
Error when using the camera - "Can't connect to the camera"
Happens randomly - "unfortunately , the process com.android.systemui has stopped"
What can be done to fixed the mentioned bugs?
Try cm11 aosp fix camera you can find it on forum
soflyj said:
I'm using the latest (2014-11-02) CM11 build for I9300. I have the following issues:
Error when using the camera - "Can't connect to the camera"
Happens randomly - "unfortunately , the process com.android.systemui has stopped"
What can be done to fixed the mentioned bugs?
Click to expand...
Click to collapse
A log would help. Grab it after system ui fc and post a link to the log so it can be looked at.
Same situation
Also have S3 with CM11 nightly from 2.11.2014 and can't connect to camera. Already done a reinstall of that CM11 and newest gapps manually by clockworkmod. Also whipped cache and dalvik cache. No change is done.
This Problem was starting with M10, start to occur more often with M11 on my unobjective perception.
Behaviour: Restart the phone let me start the camera once. After I close the camera once, it can't be restarted:
Attached you see the logfile of these case.
Thank you for your help.
Best regards
Vogon10
Try this http://forum.xda-developers.com/galaxy-s3/themes-apps/17-fixed-camera-app-lib-cm-aosp-roms-t2505973 it helped me,and the camera has better options,and more effect,and i think its little faster
vogon10 said:
Also have S3 with CM11 nightly from 2.11.2014 and can't connect to camera. Already done a reinstall of that CM11 and newest gapps manually by clockworkmod. Also whipped cache and dalvik cache. No change is done.
This Problem was starting with M10, start to occur more often with M11 on my unobjective perception.
Behaviour: Restart the phone let me start the camera once. After I close the camera once, it can't be restarted:
Attached you see the logfile of these case.
Thank you for your help.
Best regards
Vogon10
Click to expand...
Click to collapse
This thread is not for official cm builds. Test this ROM out. Better battery than official cm and the dev at least speaks to his user's. Best advice is to take the log to cm official thread.
Call Recorder
Hi,
CM add call recording option but it's disable by defaults.
I can't enable the option on CM and for my knowledge it can be enable on unofficial CM builds.
If I install this rom, can I use the native CM call recorder?
If not and it's depending on the developer, @Markox89 can you enable this in your builds?
Thanks.
@Clutchless, there're couple of Xposed Modules that can do the trick, I think it's the quickest way
I don't like Xposed
Markox89 said:
@Clutchless, there're couple of Xposed Modules that can do the trick, I think it's the quickest way
Click to expand...
Click to collapse
I don't like Xposed since it's not support with ART and slow down the device , I prefer using App instead.
It will be much better if that include in the ROM, it support by CM anyway.
But of course it's your call...
hi i'm new,i just install this rom,very stable and fast..and cool but on every boot the process com.android.phone is stopped(one time only after boot), why?How can fix this?Thank ypu
Full wipe system/cashe/dalvik and then install rom
hi
i wanna ask is your rom equip with radio?
just installed but no radio in apps
vincentchew said:
i wanna ask is your rom equip with radio?
just installed but no radio in apps
Click to expand...
Click to collapse
If you mean "radio" like "listening music radio app" no, the ROM doesn't come with it, but the Play Store is full with such kind of apps
Can i install pico gapps instead nano?
tandrcak90 said:
Can i install pico gapps instead nano?
Click to expand...
Click to collapse
Gapps is gapps as long as its 4.4 KitKat.
vincentchew said:
i wanna ask is your rom equip with radio?
just installed but no radio in apps
Click to expand...
Click to collapse
Search for "Spirit UL".
First, all we are say "thank so much" to @sbrissen shared this build for t0lteXX. and i'm only shared it again for every one.
Original thread by him : http://forum.xda-developers.com/note-2-verizon/orig-development/rom-cyanogenmod-12-0-t2967940
New Build from @sbrissen :
Rom (18/12) : https://www.androidfilehost.com/?fid=95857557620393640
Changed : Fixes keyboard problem, camera issue, and wifi causing soft reboots
Gapps : https://www.androidfilehost.com/?fid=95832962473400228
A>.How To install :
use recovery philz_touch 6.48.4 or TWRP 2.8.1.0 for t0lte
1.full wipe data/factory reset, format system, wipe davilk cache.
2.flash rom + gapps
3.wipe davilk cache/data cache
reboot
B>.Work/Not work?
1.Data and service, 3G/LTE work too fine.
2.Camera work with mode front, please use camera google from CHplay (Flash SHIFT-CM12, camera work fine)
3.Video clip work full and fine, too play with Sound and picture.
4.Call Out/receive and sms/mms
5.Music.
6.sensor promixity in call need fix by flash this file (if it have issues) :
https://mega.co.nz/#!1xkSxTDJ!o8DQkNT6UvjNoxfgoxjNq2UnZz_6bO3ivYwMmvRv7dc
7.GPS, still not yet know work?maybe work
8.NFC not work.
9.Volume sound on call very low (gently press button volume down=>sound volume will normal)
and any more maybe work, if you find any issues, please contact or report @sbrissen, to him fix it.
C>.How To Enable NavBar Button Show On Screen With Rom CM12 :
Flash it with recovery : http://goo.gl/IoELzQ
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
More screenshot see here : https://plus.google.com/u/0/communities/111794388121646986594
Awesome I am going to flash this now! Thanks for the updater-script!
link to rom
Bad gateway , can you update the link
:good:Good works Man:good:
Thanks for ROM. Can you please explain how to flash file updater-script? I see two files now and not sure which one to flash and how. I have AT&T Note 2 (t0lteatt)
Update: Bootloop at Cyanogenmod icon. Not booting to device.
mr.nth.na.vn said:
First, thank to @sbrissen shared this build. and I just edited and guided a little wave to the mobile data network for every one
Original thread for him : http://forum.xda-developers.com/note-2-verizon/orig-development/rom-cyanogenmod-12-0-t2967940
Link Rom : https://www.androidfilehost.com/?fid=95832962473400226
you need replace/instead file updater-script by download file attachments below=> so, you can flash it.
Gapps : https://www.androidfilehost.com/?fid=95832962473400228
How To install :
A>use recovery philz_touch 6.48.4 or TWRP 2.8.1.0 for t0lte
1.flash rom + gapps
2.wipe davilk cache/data cache
reboot
first time, skip anyway... all setup wizard, goto Language & Input/select Curent keyboard and check Hardware to show keyboard.
Goto settings/Developer options :
Find and check select all five options : Aggressive Wi-Fi to cellular handover and Enable Wi-Fi Verbose Logging, Wireless display certification and Always allow Wi-Fi Roam Scans.
next is turn on wifi and goto Wireless & networks/... More/Cellular networks/turn on Data roaming and select options GSM/WCDMA/LTE in Preferred network type => Servicer Mobile Data Network show and work fine.
B>Work?
1.Data and service, 3G work fine
2.Camera work with mode front, please use camera google from CHplay.
3.Video clip work full and fine, too play with Sound and picture.
4.Call and sms
5.Music....
and any more, if you find any issues, please contact or report @sbrissen, to him fix it.
More screenshot see here : https://plus.google.com/u/0/communities/111794388121646986594
Click to expand...
Click to collapse
thershope said:
Thanks for ROM. Can you please explain how to flash file updater-script? I see two files now and not sure which one to flash and how. I have AT&T Note 2 (t0lteatt)
Update: Bootloop at Cyanogenmod icon. Not booting to device.
Click to expand...
Click to collapse
Nope, note att work fine, i'm sure. you need replace this file name : updater-script-t0lteXX-l900.rar
patience waiting it boot on up ok................... see screenshot, hey mate
I did wait for more than 20 mins and the device did not boot. I will try again from the beginning. Just to confirm, how to flash the .tar files? Same as .zip in CWM ?
mr.nth.na.vn said:
Nope, note att work fine, i'm sure. you need replace this file name : updater-script-t0lteXX-l900.rar
patience waiting it boot on up ok................... see screenshot, hey mate
Click to expand...
Click to collapse
thershope said:
I did wait for more than 20 mins and the device did not boot. I will try again from the beginning. Just to confirm, how to flash the .tar files? Same as .zip in CWM ?
Click to expand...
Click to collapse
nope, you need make step :
use recovery philz_touch 6.48.4 or TWRP 2.8.1.0 for t0lte
1.full wipe data/factory reset, format system, wipe davilk cache.
2.flash rom + gapps
3.wipe davilk cache/data cache
reboot
Could you explain me step by step how I have to do to replace the updater-script to flash the ROM?
Binary_File said:
Could you explain me step by step how I have to do to replace the updater-script to flash the ROM?
Click to expand...
Click to collapse
Open rom with 7zip and replace updater with modified one then exit 7zip. Now copy rom to device and flash.
Sent from my SPH-L900 using XDA Premium 4 mobile app
So this rom will work fine on t0lte international N7105? Just want to make sure before I flash it. Thanks.
Edit: Nevermind, didn't look at screenshots. Haha.
Razorbeast19 said:
So this rom will work fine on t0lte international N7105? Just want to make sure before I flash it. Thanks.
Edit: Nevermind, didn't look at screenshots. Haha.
Click to expand...
Click to collapse
Yes, I did just flash this on my n7105 and it works. Work good even. Remember to wipe dalvik and cache after install but before reboot.
mangethegamer said:
Yes, I did just flash this on my n7105 and it works. Work good even. Remember to wipe dalvik and cache after install but before reboot.
Click to expand...
Click to collapse
Great Rom!
Works: Call, SMS, data, front camera, video/sound/music, wifi + wifi AP.
Doesn't work:
back camera.
(edit: After flashing Shift CM12 kernel, camera works! But shift cm12 kernel not as smooth as the default kernel. Also baseband may have problem again.)
Keep the good work!
-----------------------------------
I changed Prefered network type to "GSM/WCDMA/LTE preferred" (under Cellular network setttings), so phone call seems working now.
wilson3q said:
Great Rom!
Works: Call, SMS, data, front camera, sound/music, wifi + wifi AP.
Doesn't work:
Video playback, back camera.
Keep the good work!
-----------------------------------
I changed Prefered network type to "GSM/WCDMA/LTE preferred" (under Cellular network setttings), so phone call seems working now.
Click to expand...
Click to collapse
back camera worked for me and so did video playback
winxuser said:
back camera worked for me and so did video playback
Click to expand...
Click to collapse
After I flashed Shift CM12 kernel, back camera works...
Videos captured by camera can play well...
kernel
wilson3q said:
After I flashed Shift CM12 kernel, back camera works...
Videos captured by camera can play well...
Click to expand...
Click to collapse
can you send me a link to the kernel
after installing a few apps, its become pretty unresponsive and wifi stopped working?? not sure if its just me tho
---------- Post added at 02:46 PM ---------- Previous post was at 02:16 PM ----------
calls don't work for me,, sms are ok
spinekiller1 said:
can you send me a link to the kernel
Click to expand...
Click to collapse
URL by @rogersb11:
https://www.dropbox.com/s/97gwv1ticia4bk7/Shift-CM12.zip?dl=0
But after flashing shift kernel, back camera works, but other things will break, e.g. baseband. Also the rom become not so responsive and stable.
Better wait for the true CM12 build from t0lte (not this device i605)...
---------- Post added at 06:04 AM ---------- Previous post was at 06:00 AM ----------
winxuser said:
after installing a few apps, its become pretty unresponsive and wifi stopped working?? not sure if its just me tho
---------- Post added at 02:46 PM ---------- Previous post was at 02:16 PM ----------
calls don't work for me,, sms are ok
Click to expand...
Click to collapse
Mine still quite responsive after installing 10+ apps...I am using the default kernel with the rom. Not shift cm12 kernel.
Change your prefered network type to the correct one for your carrier..and call will work.
wilson3q said:
URL by @rogersb11:
https://www.dropbox.com/s/97gwv1ticia4bk7/Shift-CM12.zip?dl=0
But after flashing shift kernel, back camera works, but other things will break, e.g. baseband. Also the rom become not so responsive and stable.
Better wait for the true CM12 build from t0lte (not this device i605)...
---------- Post added at 06:04 AM ---------- Previous post was at 06:00 AM ----------
Mine still quite responsive after installing 10+ apps...I am using the default kernel with the rom. Not shift cm12 kernel.
Change your prefered network type to the correct one for your carrier..and call will work.
Click to expand...
Click to collapse
ahaha woops yeah I forgot to change network type,,, but after a couple minutes on a call the line goes all static and I cant hear anything
---------- Post added at 03:22 PM ---------- Previous post was at 03:10 PM ----------
Seems like the preferred network doesn't save once it reboots it changes again
Sent from my SCH-I605 using XDA Free mobile app
hi
i follow your thread and still having the same issue. i can send an receive text messages. i can call out but i cannot receive call. the person calling me gets the ring and then to my voicemail which i receive. i replaced the script as indicated. i check the status of the cellular network state and it says Disconnected.. The model still shows as i605. i have the i317m
Suspended pending my aquiring a new device to develop with (volume down button broken no more booting into bootloader :/)
Well I have been playing with this phone for the last few weeks and found very little development on it. So I decided to create my very first custom rom for the thing. It is pre rooted debloated and updated with some pretty useful tools moved to system right now it is in the form of a TWRP backup but soon as i figure out how to make a flashable zip ill do that with it ill upload V1 soon if i get enough attension here C: oh yeah i also removed DT IGNITE! for you
A list of features? okay
-Extra apps and updated system apps
-ABP built in
-/system/etc/init.d support
-selinux set to permissive via an init.d script
-built in system app manager and updater
-HTC Sense updated to current versions
-Google apps built in and up to date
-Hangouts installed to system (took me hours to get that one to work right lol)
-Pre ODEXed for added performance
-Xposed framework built in
-And many more!
I also take feature requests but that doesnt mean i will add your request but if its a good idea and in my skill level ill prolly toss it in
And now for some legal mumbojumbo
I take no responsibility for bricked, or otherwise damaged devices after using my software solution. Your usage of my software is done without warranty, and in the likely event of a bricked device or otherwise I may or may not decide to assist you with remedying your issue/s.
This is your only warning, please proceed with caution!
XDA:DevDB Information
FoxMod, ROM for the HTC Desire
Contributors
fennectech, Fennectech
ROM OS Version: 4.4.x KitKat
ROM Firmware Required: Sunshine S-Off
Based On: Stock
Version Information
Status: Alpha
Current Stable Version: None
Stable Release Date: 2017-01-13
Created 2016-04-10
Last Updated 2016-06-22
this is where i will be putting all the files
https://goo.gl/msJuFh
Stock ROM for this thing available NOWHERE ELSE! thanks to vanilla for this!
https://goo.gl/dWIzUw
How to install:
1: unzip folder to TWRP backup folder
2: restore "foxmod" backup from twrp
3: wipe data and caches
4: reboot and enjoy!
Note: if an app crashes with "an error occored installing "blah blah blah" please uninstall the app then re install the app" you need to convert the app to a user app using the system app manager then convert it back to a system app using the same tool
For future use
Known Issues
Camera doesnt work (advice on how to fix welcome)
com.google.gapps crash on some devices (not sure why)
Future Plans
Restore AOSP settings and menu themes.
Bake in a tool to backup and restore App data and Executables
Bake in adblocking hosts file
Bake in universal GSM unlock if possable (http://www.internauta37.altervista.o...phones-android)
Changelog
V1 Initial release
V2
removed plume premium unlocker
added xposed framework
added youtube adaway (xposed module)
added dropbox
fixed photos crash
V2.9
Earley release of FoxMod with camera fix and partial featureset.
Comming in V3
fixed camera and reimplimented all features while preserving camera function
How can you help me?
help restoring AOSP menus and things would be nice
A list of apps ive built in
Adblock plus
Swiftkey
System App Manager
System Cleaner
TWRP Manager
Chrome
CCleaner
ClockSync
BuildProp Editor
Terminal Emulator
Hangouts
Messenger (facebook)
Gif keyboard
Google Play Services (latest)
Hangouts dialer (latest)
Autorun Manager
Total Commander
SuperSU
Google Play Music (latest)
Google Voice (latest)
All the htc stuff updated
you can just remove stuff you dont want using system app manager
and a butt load of other things C:
Whats going on now?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can you post how to unlock the boot loader after getting root from the sunshine app? Would be greatly appreciated as I busted my good phone and now all I have is my old desire 612 and would love to try your rom also if the boot loader is unlocked I can flash titanium backup and create a stock image if anyone needs it.
kunjunction said:
Can you post how to unlock the boot loader after getting root from the sunshine app? Would be greatly appreciated as I busted my good phone and now all I have is my old desire 612 and would love to try your rom also if the boot loader is unlocked I can flash titanium backup and create a stock image if anyone needs it.
Click to expand...
Click to collapse
you must pay 25$ to sunshine to get the bootloader unlocked just follow the prompts in the app its worth it
you can use fastboot to flash the recovery after you unlock with sunshine hold power and vol down do get into hboot and youll see what to do then go fastboot flash recovery recovery.img use the one in my mega folder
that recovery will boot on the 612 i desperately need an stock image for this device to fix the camera in my rom
before you flash my rom taake a twrp backup for me please and upload it somewhere
FoxMod HTC Desire 612 First Custom ROM
Click to expand...
Click to collapse
Umm... wrong forum?
nechko_ said:
Umm... wrong forum?
Click to expand...
Click to collapse
The 612 and the 610 are close enough for that not to matter. The only real difference is the screen type used. Which is pretty easily remedied.
ninjasinabag said:
The 612 and the 610 are close enough for that not to matter. The only real difference is the screen type used. Which is pretty easily remedied.
Click to expand...
Click to collapse
I've never been able to get firmware or recoveries from the 6:10 to work the 612
Sent from my HTC331ZLVW using XDA-Developers mobile app
fennectech said:
I've never been able to get firmware or recoveries from the 6:10 to work the 612
Sent from my HTC331ZLVW using XDA-Developers mobile app
Click to expand...
Click to collapse
I was able to get your ROM working, only issue was the screen like I had been saying. The hardware is close enough where it boots, especially when it has been ported with the 610 specifications taking priority.
My screen stays black, but my computer reads the device as active while rebranded as a 612.
ninjasinabag said:
I was able to get your ROM working, only issue was the screen like I had been saying. The hardware is close enough where it boots, especially when it has been ported with the 610 specifications taking priority.
My screen stays black, but my computer reads the device as active while rebranded as a 612.
Click to expand...
Click to collapse
The only differences in kernel source are are the touch screen and storage dts/dtb files. The files are all there for desire612 in the 610 kernel source. If I compiled a cm kernel with def_configs for the 612 you should be able to run cm on it. @fennectech you should be able to take the camera files you need from any d610 rom, same camera.
@ninjasinabag if you want to try to run this rom on a 610 all you should have to do is take a twrp backup of you stock d610 rom, factory reset, Install this foxmod rom, restore just the boot partition from your d610 backup (stock d610 kernel) and wipe dalvic and cache then reboot. I haven't tried it but it looks like it should work.
MiniBlu said:
The only differences in kernel source are are the touch screen and storage dts/dtb files. The files are all there for desire612 in the 610 kernel source. If I compiled a cm kernel with def_configs for the 612 you should be able to run cm on it. @fennectech you should be able to take the camera files you need from any d610 rom, same camera.
@ninjasinabag if you want to try to run this rom on a 610 all you should have to do is take a twrp backup of you stock d610 rom, factory reset, Install this foxmod rom, restore just the boot partition from your d610 backup (stock d610 kernel) and wipe dalvic and cache then reboot. I haven't tried it but it looks like it should work.
Click to expand...
Click to collapse
i tried pulling the camera libraries from this rom but no luck i made sure to see that it was 4.4.4 too any other files related to the camera in the rom? or otherthings that might do it?assistance getting cm11 based on kitkat running on the desire 612 would be appreciated i dont beleve we can alter the kernel on this device
<3>[ 1260.438035] c0 1556 [CAM] camera_v4l2_open : posting of NEW_SESSION event failed
<3>[ 1260.438046] c0 1556 [CAM] camera_v4l2_open : Line 575 rc -22
<3>[ 1260.969898] c0 1 init: sys_prop: permission denied uid:1013 name:camera.4k2k.enable
<3>[ 1260.970144] c0 1 init: sys_prop: permission denied uid:1013 name:camera.4k2k.enable
<6>[ 1260.973083] c0 1556 [CAM] camera_v4l2_open: E
looks like a permissions problem
some output from logcat relating to the error
E/Babel_SMS(11932): canonicalizeMccMnc: invalid mccmnc nullnull
E/mm-camera-intf( 371): mm_camera_open: opened, break out while loop
E/mm-camera-intf( 371): mm_camera_open: cannot open control fd of '/dev/video1' (Invalid argument)
E/mm-camera-intf( 371): camera_open: mm_camera_open err = -1
E/QCamera2HWI( 371): camera_open failed.
E/CameraClient( 371): Could not open camera 0: -2147483648
E/CameraClient( 371): initialize: Camera 0: unable to initialize device: Unknown error -2147483648 (-2147483648)
E/QCamera2HWI( 371): [TimeHelper] void qcamera::QCamera2HardwareInterface::TimeHelper::reset():6628, open device /dev/time_helper error!
E/QCamera2HWI( 371): [KPI Perf] int qcamera::QCamera2HardwareInterface:penCamera(hw_device_t**): E PROFILE_OPEN_CAMERA CameraID:0
E/mm-camera-intf( 371): mm_camera_open: dev name = /dev/video1, cam_idx = 1
E/mm-camera-intf( 371): mm_camera_open: open retry
bash-3.2# fuser /dev/video0
16257
bash-3.2# ps 16257
USER PID PPID VSIZE RSS WCHAN PC NAME
camera 16257 1 18252 3348 00000000 b6ea4438 R /system/bin/mm-qcamera-daemon
bash-3.2#
more information on the camera bug
Here we go CAMERA IS WORKING! ive got a stock rom!
ninjasinabag said:
I was able to get your ROM working, only issue was the screen like I had been saying. The hardware is close enough where it boots, especially when it has been ported with the 610 specifications taking priority.
My screen stays black, but my computer reads the device as active while rebranded as a 612.
Click to expand...
Click to collapse
must not work bolth ways then
Finally installed this rom but its so unstable. Google Play Services constantly crashes so I cannot do anything with this phone now. Are there any plans to make this rom work without all the crashing? Thanks.
Where is a link?
Do you have a download link for the stock Rom?
fennectech said:
Here we go CAMERA IS WORKING! ive got a stock rom!
Click to expand...
Click to collapse
ninjasinabag said:
I was able to get your ROM working, only issue was the screen like I had been saying. The hardware is close enough where it boots, especially when it has been ported with the 610 specifications taking priority.
My screen stays black, but my computer reads the device as active while rebranded as a 612.
Click to expand...
Click to collapse
android86.ad said:
Do you have a download link for the stock Rom?
Click to expand...
Click to collapse
second reply its in a 7z file C: just click the second google link and it will take you to the page C:
Unable to restore through TWRP MD5 mismatch as well as 255 error when restoring. FoxMOD 2.9
Failure of restoring FM v2.9
get error ExtractTarFork-255
Hello user space,
A couple days ago I decided to take a chance by building AOSP for my G8342 Dual, the experimentation was quite... let's call it adventurous. It all started by firing up my VM, which I currently use to build, unofficially, LineageOS for my Nexus 5. I'd set a side enough space for the VM to cover the LOS build, not remembering the amount space used I was oblivious. I then jumped on Sony dev site, just to find out the XZ1 had been added to the list of unlockable devices, sweet! I backed up my current XZ1 data not sure whether the bootloader unlock would wipe all data, after sweeping the web for more information, it was confirmed that data would be wiped. I should have known because my N5 did wipe data, which I take is a security measure.
Back on the VM, per Sony's dev site, I made sure the necessary packages were installed which was all of them minus maybe one that wasn't. After all this VM builds for another device so it should be 98% complete. With haste, I 'repo sync'd that bad boi, and 'repo_update'd and on to the 'make -j4'. Little did I know, I had space issues. Remember that space issue up there?^^ It came to haunt me later, like 78% building complete later. :/. #$%^&(* I created a new VM with more space for both N5 builds and Xperia. The build was completed successfully, 3.xx-hrs later.
AOSP was manageable on the N5 with Google proprietary vendor files, etc. But this XZ1 is just blah.. even with the sony binary(4.4). By the way, without the sony binary(fastboot flash oem *.img) the thing will not boot. I flashed an unofficial gapps package from back in Dec. 2017, which I believe is the only functional(per xda) one for Oreo. Needless to say, the gapps package works.
Here are my issues with the AOSP XZ1: Android-8.1.0_r15
-SIM2 is defunct. I selected option 48 from lunch menu. Option 48 was aosp-g8342-userdebug.
-The camera, I know, DRM is sorta still there, with limits :/.
a.) Noise reduction is nowhere to be found even under good light. This camera has a good f-stop.
b.) HDR? It's there but is it actually performing its best work? No.
c.) Camera focus at close range, under a foot? Problematic or mostly nada on screen tap.
-A minor change: screenshot capture is now Volume down + power button. Aosp style!
Non-issues:
-Its plain vanilla, flat as a soda that's been seating out open all day.
-Because I built a userdebug version, root is automagically embedded.
https://source.android.com/setup/building#choose-a-target
Code:
You take on the responsibility of your device. Backup your data because the images will wipe everything.
=============How to flash=============
Get a copy of the latest binary here: software-binaries-for-aosp-oreo-android-8-1-kernel-4-4-yoshino
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash userdata userdata.img
fastboot flash oem SW_binaries_for_Xperia_AOSP_O_MR0_4.4_<release version>_<platform>.img
====================================
===============8.1.0_r20==========================
-Grab a copy of this aosp-g8342_dual-userdebug:
AOSP_Android-8.1.0_r20_G8342_Dual.zip
-Grab a copy of this aosp-g8341_single-userdebug:
AOSP_Android-8.1.0_r20_G8341_Single.zip
===============8.1.0_r20==========================
Here are a few screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
perhaps it was a nice story to tell.... have a nice day xda.
Hello. Nice story. I have the single Sim version so I don t know if this will work, but have you had a chance to check the fingerprint sensor? Thanks
Can u build g8341 aosp?
emyjojo said:
Hello. Nice story. I have the single Sim version so I don t know if this will work, but have you had a chance to check the fingerprint sensor? Thanks
Click to expand...
Click to collapse
It will not work with single sim. Yes I have checked the fingerprint even registered two of them. I've attached some pictures for you to see.
dcrin3 said:
It will not work with single sim. Yes I have checked the fingerprint even registered two of them. I've attached some pictures for you to see.
Click to expand...
Click to collapse
That's great news, as it was not working in the previous builds. Would you have the time to build a version for the single SIM model? Would like do give it a shot.
Thank you.
AOSP_Android-8.1.0_r15_G8342_Single
emyjojo said:
That's great news, as it was not working in the previous builds. Would you have the time to build a version for the single SIM model? Would like do give it a shot.
Thank you.
Click to expand...
Click to collapse
You know I just realized that my Dual device is not listed on the Supported devices and functionality page.
The XZ Premium has a dual edition listed but not the XZ1, I wonder why.
Well that makes some sense now.
Code:
Please be aware that I've not tested this package as I do not have the device(You take on the responsibility). Backup your data because the images will wipe everything.
Here is the single version:AOSP_Android-8.1.0_r15_G8341_Single.zip
You let me know if its at least fingerprint and sim1 functional.
see ya.
dcrin3 said:
You know I just realized that my Dual device is not listed on the Supported devices and functionality page.
The XZ Premium has a dual edition listed but not the XZ1, I wonder why.
Well that makes some sense now.
Here is the single version:AOSP_Android-8.1.0_r15_G8342_Single.zip
You let me know if its at least fingerprint and sim1 functional.
see ya.
Click to expand...
Click to collapse
Hi fingerprint is working rom boots fine thank you
yoyoyed said:
Hi fingerprint is working rom boots fine thank you
Click to expand...
Click to collapse
What do you think of its vanilla-ness? its tooo plain no?
dcrin3 said:
What do you think of its vanilla-ness? its tooo plain no?
Click to expand...
Click to collapse
I like it for me perfect can you please support this and keep it updated in the future. Thanks
Hello, It works fine for me as well, but we still need to do the trick with Google Play, in order to get it to work. Will test drive this for a while. Thank you for your efforts.
I have a couple of questions.
1: Does the data activate immediately or does it take several minutes to become active upon booting?
2: Does "OK Google" work from any screen as it does on the stock ROM. (I attempted to run a previous build of AOSP on my 8341 and that feature wouldn't work properly and it drove me insane as i use it all the time.)
3: Is this package a flashable zip or do we have to install each file seperately via fastboot?
Thanks
N1ghtr08d said:
I have a couple of questions.
1: Does the data activate immediately or does it take several minutes to become active upon booting?
2: Does "OK Google" work from any screen as it does on the stock ROM. (I attempted to run a previous build of AOSP on my 8341 and that feature wouldn't work properly and it drove me insane as i use it all the time.)
3: Is this package a flashable zip or do we have to install each file seperately via fastboot?
Thanks
Click to expand...
Click to collapse
Hello,
The data activates immediately upon booting, i do not use google assistant so can't really help about the second point. It is not a flashable zip, you will need to flash each .img via fastboot.
A new thing that I've noticed, the fingerprint sensor is always on, it can unlock the device with the screen turned off.
Hope this helps.
N1ghtr08d said:
I have a couple of questions.
1: Does the data activate immediately or does it take several minutes to become active upon booting?
2: Does "OK Google" work from any screen as it does on the stock ROM. (I attempted to run a previous build of AOSP on my 8341 and that feature wouldn't work properly and it drove me insane as i use it all the time.)
3: Is this package a flashable zip or do we have to install each file seperately via fastboot?
Thanks
Click to expand...
Click to collapse
1 For me data working immidiately
2 ok google only on google app
3 package flash via fastboot
And instal gapps is no issue on this rom works fine
Thanks for the replies. The big issue for me is Google Assistant. If I can't use it from anywhere/with the screen off then it's a no go for me. I'm glad I asked this question before I flashed. Going back to stock is always time consuming.
---------- Post added at 12:08 PM ---------- Previous post was at 12:02 PM ----------
yoyoyed said:
1 For me data working immidiately
2 ok google only on google app
3 package flash via fastboot
And instal gapps is no issue on this rom works fine
Click to expand...
Click to collapse
Could you please try something for me? Delete your trained voice from the Google app then retrain it again but when saying the "ok Google" command, say each of the 3 commands from different distances from the microphone, for example the first really close to the phone, second about 1ft away, 3rd about 2ft away. After its retrained please answer back and let me know if there's any difference please.
I really rely on the Google Assistant so I'm hoping we can fix it somehow.
---------- Post added at 12:12 PM ---------- Previous post was at 12:08 PM ----------
I also found this via search...
I opened the Google App and went to Settings in main menu. Then "'OK Google' detection". Then I disabled all 3 OK Google settings ("Say 'OK Google' any time", "Trusted voice", and "While driving"). Then I re-enabled all 3 and it asked me to retrain by saying "OK Google" 3 times (which is weird because I never explicitly deleted the training data). Then "OK Google" seemed to work fine again after Oreo upgrade.
Could you try that if the first one didn't work?
It seems that it was a false positive with the fingerprint scanner, at least for me. After a Day of usage, it says no fingerprint hardware. It works briefly after a reboot, but it stops.
I figured out a partial fix for Google Assistant not working. The only caveat is that it won't work from a locked screen and unlock the phone, but it works from any screen while the screen is on.
This problem that u have can occur if the Google app is not installed as a system app .
So to fix this ,follow the next few steps -
1) Convert Google app into system app using apps like Titanium backup or anything of your preference. (I found that doing this caused a never ending process and it is fixed by simply going to Titanium Backup so permissions then force stop the app.)
2) Using any root Explorer navigate to Root > system > app and search for an app named similar to 'googlesearchbox' and cut the app from this folder.
3) Now Navigate to Root > system > priv-app and paste the app.
4) Reboot and now the problem will be gone
5) Finally go to the app permissions of the Google app then clear the cache and data then reboot.
The problem should be solved and you should be able to retrain the voice commands.
@yoyoyed
"I like it for me perfect can you please support this and keep it updated in the future. Thanks"
I will certainly entertain the idea. I need to start utilizing twrp backup now that the bootloader is unlocked.
It takes too much time to restore this beast to its working condition.
@emyjojo
"Hello, It works fine for me as well, but we still need to do the trick with Google Play, in order to get it to work. Will test drive this for a while. Thank you for your efforts."
I may have a dirty trick to pull that off. I need to spend more time in the android playground, experimenting. You're welcome @emyjojo
@N1ghtr08d
"2: Does "OK Google" work from any screen as it does on the stock ROM. (I attempted to run a previous build of AOSP on my 8341 and that feature wouldn't work properly and it drove me insane as i use it all the time.)"
That's a low possibility of it happening but along the same experimenting as above ^^^ it may come through. But I'm not promising.
"3: Is this package a flashable zip or do we have to install each file seperately via fastboot?"
That is possible with me spending more time in the playground.
@emyjojo
"It seems that it was a false positive with the fingerprint scanner, at least for me. After a Day of usage, it says no fingerprint hardware. It works briefly after a reboot, but it stops."
After testing out some of the ideas above I will opt to test the phone(AOSP) for a couple days. I want to see how the fingerprint handles on longer usage scenarios.
thank you all for testing it out.
see ya!
dcrin3 said:
@N1ghtr08d
"2: Does "OK Google" work from any screen as it does on the stock ROM. (I attempted to run a previous build of AOSP on my 8341 and that feature wouldn't work properly and it drove me insane as i use it all the time.)"
That's a low possibility of it happening but along the same experimenting as above ^^^ it may come through. But I'm not promising.
Click to expand...
Click to collapse
Bro, look at the post directly above yours. I solved the issue with Google assistant!
@dcrin3
I have a logcat of the fingerprint failure if it will help:
08:42:26.134 V/FingerprintService(952): request stop current client com.android.systemui
03-21 08:42:26.134 W/FingerprintService(952): stopAuthentication: already cancelled!
03-21 08:42:29.137 W/FingerprintService(952): Client com.android.systemui failed to respond to cancel, starting client com.android.systemui
03-21 08:42:29.138 V/FingerprintService(952): starting client AuthenticationClient(com.android.systemui), initiatedByClient = false)
03-21 08:42:29.164 W/FingerprintService(952): startAuthentication failed, result=1
03-21 08:42:29.780 E/KernelUidCpuTimeReader(952): Failed to read uid_cputime: /proc/uid_cputime/show_uid_stat (No such file or directory)
03-21 08:42:32.176 V/FingerprintService(952): stop client com.android.systemui
03-21 08:42:32.179 W/FingerprintService(952): client com.android.systemui is no longer authenticating
03-21 08:42:32.180 V/FingerprintService(952): startAuthentication(com.android.systemui)
03-21 08:42:32.182 V/FingerprintService(952): request stop current client com.android.systemui
03-21 08:42:32.182 W/FingerprintService(952): stopAuthentication: already cancelled!
03-21 08:42:35.185 W/FingerprintService(952): Client com.android.systemui failed to respond to cancel, starting client com.android.systemui
03-21 08:42:35.185 V/FingerprintService(952): starting client AuthenticationClient(com.android.systemui), initiatedByClient = false)
03-21 08:42:35.210 W/FingerprintService(952): startAuthentication failed, result=1
03-21 08:42:42.948 E/KernelUidCpuTimeReader(952): Failed to read uid_cputime: /proc/uid_cputime/show_uid_stat (No such file or directory)
03-21 08:42:48.287 E/KernelUidCpuTimeReader(952): Failed to read uid_cputime: /proc/uid_cputime/show_uid_stat (No such file or directory)
03-21 08:42:50.184 I/PowerManagerService(952): Waking up from sleep (uid=1000 reason=android.policyOWER)...
03-21 08:42:50.211 E/KernelUidCpuTimeReader(952): Failed to read uid_cputime: /proc/uid_cputime/show_uid_stat (No such file or directory)
03-21 08:42:50.218 V/FingerprintService(952): stop client com.android.systemui
03-21 08:42:50.218 I/DisplayPowerController(952): Blocking screen on until initial contents have been drawn.
03-21 08:42:50.220 W/FingerprintService(952): client com.android.systemui is no longer authenticating
03-21 08:42:50.221 V/FingerprintService(952): startAuthentication(com.android.systemui)
03-21 08:42:50.221 V/FingerprintService(952): request stop current client com.android.systemui
03-21 08:42:50.221 W/FingerprintService(952): stopAuthentication: already cancelled
Very good job, nice to see people caring about bringing stock android to the XZ1.
What about treble generic ROMs? Did u try?
Can't wait to have a official treble Ressurection Remix!