Related
Hi.
First of all, thanks for all you great people for working and developing for these phones.
Today, for the first time, I flashed my phone. Having android on Wave 2 feels great!
I installed CarbonRom but I'm not entirely satisfied with it and wanted to try to install some other ROM (like ZenDroKat, I heard good things about that one) and run into a problem. I noticed that my PC doesn't see the phone at all! There is no reaction, not sound when connecting the phone. I tried the front and the back usb-ports, and on our family laptop. The multiloader doesn't find the port either.
Although it did react in recovery mode (TWRP) and installed drivers for "Android Composite ADB Interface", whatever that is.
Or could I install a new ROM without trying to fix this?
Once i had a problem detecting my phone , i was so frustrated : what worked with me , maybe this sound silly but :
Does your phone charge with the USB cable :
if yes in mini USB port there is a tongue inside , trying raising it a little with a sharp metal
if no , maybe your cable is the problem .
between that and this , probable you can install Omni rom , by copying the rom to sdcard if you have external card reader , since you have already TWRP installed.
Thanks.
I did figure it out. Well, I didn't fix it on CarbonRom but I managed to install another ROM. The USB worked in Download Mode, so I just re-installed Bada and then installed ZenDroKat ROM. For now it seems to work fine.
Now, is there a way to delete your own threads?
I have Windows 8 on my computer, when I update my windows with connected phone it shows Acer updates in Microsoft update menu. I update all, and after my computer didn't recognize my phone. Then I delete Acer drivers and it recognize again
Sent from my GT-I9000 using XDA Free mobile app
DkayBlack said:
Thanks.
I did figure it out. Well, I didn't fix it on CarbonRom but I managed to install another ROM. The USB worked in Download Mode, so I just re-installed Bada and then installed ZenDroKat ROM. For now it seems to work fine.
Now, is there a way to delete your own threads?
Click to expand...
Click to collapse
i think Omni is better ,and stable ,try it
ice_ice said:
i think Omni is better ,and stable ,try it
Click to expand...
Click to collapse
Yeah, I'm having issues with ZenDroKat. Namely, it often refuses it go out of sleep mode, I missed phone call due to that.
I'm going to try Omni then, thanks for advice. There are so many roms, it is hard to determine which one is better at a first glance.
DkayBlack said:
Yeah, I'm having issues with ZenDroKat. Namely, it often refuses it go out of sleep mode, I missed phone call due to that.
I'm going to try Omni then, thanks for advice. There are so many roms, it is hard to determine which one is better at a first glance.
Click to expand...
Click to collapse
Short development history: by Rebellos
The project has been started by Oleg in March 2011 - development progress has been made rapidly by him, however, he had been using JTAG Riff Box to make Wave oneNAND memory organisation the same like in Samsung Galaxy S (SGS) I9000 - phone with very similiar hardware to Wave. The problem is it's very expensive and advanced stuff. In the meantime mijoma found security hole in Wave's Bootloader3 (BL3) FOTA loading code and made PoC-exploit for that. That allowed me to create, with help of srg.mstr, mijoma and b.kubica, simple Badadroid bootloader, loading kernel zImage from moviNAND flash memory - this is where port has been made bootable on literally any Wave phone. However, oneNAND layout still remains untouched and by default kernel is configured to use SGS oneNAND partitions. So nbates66 and anghelyi put all their efforts into making this method of booting operatible. It succeed after few days and ShadowAS1 had released unofficial tutorial explaining how to bring up pre-alpha Android into S8500 device. The problem was that only 1 bootloader version was supported this time, mijoma came up with idea of making our FOTA bootloader capable of supporting alot of bootloaders - he created "BL Univ Boot FOTA". Oleg became very busy with his real life stuff so kernel development practically stopped. Currently I'm the most active kernel developer, altough I'm not so experienced as Oleg is and I'm learning from scratch so it goes very, very slow.
December 2011 - KB_Jetdroid contacted me and we started to work on Jet&Wave modem driver.
April 2012 - mikegapinski has joined the project to get things together and make first really working ROM.
9 April 2012 - Mike got ICS platform booting.
Mike has stopped maintaining platform so I took it over.
Oleg has finally got S8530 in his hands and made SCLCD driver for it. Praise him!
Both S8500 and S8530 versions are semi operatible. The most complicated, annyoing, and needed driver is Modemctl+RIL.
March 2013 - World's first working non-AT commands based RIL for non-Android phone has been released. Most of the implementation was done by KB_Jetdroid, me and Volk204, basing on opensource Replicant's RIL for Samsung Galaxy S.
April 2013 I finally fixed S8530 display driver.
September 2013 - we've got working microphone recording, and shortly after Tigrouzen found a proper patch fixing voice communication during calls.
22 September 2013 - we released first version capable of multicalls.
~~October 2013 - GPRS connections are working
Currently most of the core work is done.
We are working hard with Volk204 on RIL interface, doing small progress day by day.
en very brief : there was one team , that did all the work since the start ,"the Badadroid team" , Badaroid developed by Rebellos and Volk204 was a base for Omnirom ported by volk204 which he is the main developer now , and all those rom you see is basically noob roms , they copy the work of Volk204 , they are actually no developers in the first place, if Volk204 doesn't fix the bugs in his roms , their roms has them . i would recommend
Nand - use Omni rom http://forum.xda-developers.com/showthread.php?t=2800014
u wanna keep bada - Badadroid 4.4 http://forum.xda-developers.com/showthread.php?t=2609560
Hero355 is also a good one but he has own bugs and he isn't around much this days , work on it stopped http://forum.xda-developers.com/samsung-tizen/bada-android/rom-carbonrom-s8500-s8530-t2840174
read this thread http://forum.xda-developers.com/showthread.php?t=1459391
Thanks, that's quite interesting.
It's amazing that you people are still developing for these phones. They are so outdated that I wouldn't have guessed that anyone bothered with them.
ice_ice said:
u wanna keep bada - Badadroid 4.4 http://forum.xda-developers.com/showthread.php?t=2609560
Click to expand...
Click to collapse
Why would anyone want to keep bada? Isn't the main reason to install android-based ROM to get rid of that awful system? :laugh:
DkayBlack said:
Thanks, that's quite interesting.
It's amazing that you people are still developing for these phones. They are so outdated that I wouldn't have guessed that anyone bothered with them.
Why would anyone want to keep bada? Isn't the main reason to install android-based ROM to get rid of that awful system? :laugh:
Click to expand...
Click to collapse
THIS IS AN ALPHA, RELEASED FOR YOU TO PLAY WITH AND GET A SENSE OF WHAT’S TO COME. AND SOME THINGS DOESN’T WORK. REALLY. IF YOU ARE EXPECTING ANYTHING CLOSE TO PERFECTION, WALK AWAY FROM YOUR COMPUTER, LOWER YOUR EXPECTATIONS FOR AN HOUR OR SO, THEN COME BACK. MORE EXCITING DISCLAIMERS/WARNINGS IN ALL CAPITAL LETTERS CAN BE FOUND BELOW. READ THEM.
KNOWN BUGS (what doesn't work):
- Modem in 2G mode work incorrect(Network registration don't work with some SIM cards, permanent full signal straight, problem is with audio in calls)
With 3G all is OK, Use this: Settings -> More.. in "wireless&network" category -> Mobile Network -> Preferred Network type -> 3G only
- Conference Calls
- Some problems with audio codec settings, but generally it should
For me : Call diverting , not working
GPS not fully working
Roms is amazing , fast , but not so fast when installing Gapps ,(i did install them , but i disable all of it)
Battery life
don't get me wrong Omni is my daily rom , but this could be a problem if talk to much on phone , battery drop out fast , with average use it won't last 10 hours
Hi,
Anybody has any information about this --> http://www.cmxlog.com/13/lt03lte/ ??
OMG.
Oh man, i am envious on p605, now. I hope p600 will also get official support with working camera and screen mirroring...
Issues
itsita said:
Hi,
Anybody has any information about this --> http://www.cmxlog.com/13/lt03lte/ ??
OMG.
Click to expand...
Click to collapse
It is great news.
I tried 25.03.2016 nightly as I wanted to have some themes on my Tablet. Here are some issues I encountered.
Sim card was not recognized.
Gapps setup failed to start and showed error.
Others I could not test as I was unable to move forward from setup error.
I am back on AOSP 6.01. Works great, rarely display driver fails.
Will try in fortnight time, may be remaining bugs will squashed by then!
drchohan said:
It is great news.
I tried 25.03.2016 nightly as I wanted to have some themes on my Tablet. Here are some issues I encountered.
Sim card was not recognized.
Gapps setup failed to start and showed error.
Others I could not test as I was unable to move forward from setup error.
I am back on AOSP 6.01. Works great, rarely display driver fails.
Will try in fortnight time, may be remaining bugs will squashed by then!
Click to expand...
Click to collapse
Thanks for testing!
The gapps issue is known for all CM devices right now so hopefully it will be fixed soon.
For the sim issue i saw some ril patches merged today so again i guess it's not device specific
I looked through the git of the developer who merged our device and it looks promising... he merged all the sources from the last p607 5.1.1
Wish we could thank him!
Sent from my SM-P605 using Tapatalk
CM13 2016.03.30 Nightly Test
itsita said:
Thanks for testing!
The gapps issue is known for all CM devices right now so hopefully it will be fixed soon.
For the sim issue i saw some ril patches merged today so again i guess it's not device specific
I looked through the git of the developer who merged our device and it looks promising... he merged all the sources from the last p607 5.1.1
Wish we could thank him!
Sent from my SM-P605 using Tapatalk
Click to expand...
Click to collapse
Experience of latest Nightly 30.03.2016
Sim Card does not get recognized.
I got the Gapps working by following this method http://forum.xda-developers.com/showpost.php?p=66094943&postcount=207
Gapps used were http://forum.xda-developers.com/android/general/gapps-gapps-6-0-1-minimal-t3276606
OpenGapps does NOT work.
Super User and Xposed Works well.
Themes work.
I am using it for last few hours. ROM is stable and just works except telephony.
Looking forward to have working Telephony!
Thanks to CM for supporting our Note.
Awesome, i will start to test soon as possible
Experience on Update 04.04.2016
Telephony is still working for me. (sim card is not recognized).
I have reverted back to AOSP Rom P605 http://forum.xda-developers.com/galaxy-note-10-2014/development/rom-android-6-marshmallow-t3254901
I wanted themes on my tablet, so tried this Layers Manager https://play.google.com/store/apps/details?id=com.lovejoy777.rroandlayersmanager
It works well on tablet. But before Layers Manager is installed Tablet has to rooted and Busy Box installed. I used this busybox application. https://play.google.com/store/apps/details?id=me.timos.busyboxonrails
Layer themes can be seen here http://forum.xda-developers.com/android/themes/0-themes-official-mega-rro-themes-t3011075
Hope it helps.
For time being I think I would be staying on AOSP.
I hope it helps!
SIM does not work
I install CM 13 on my P605 but my SIM card is death and I lost my IMEI
As we all are encountering the same problem with the SIM card I guess I can conclude it's not because of some stupid mistake of mine
But where can one report bugs in the nightlies? The cyanogenmod JIRA says very clearly that no Nightlies bug reports are to be added to the CYAN project and the NIGHTLIES projects only accepts regressions from the last snapshot... So where to report bugs like ours?
Does cm13 support ntfs filesystem for micro sd-cards?
Yesterday install the version of 13th and I was surprised functioning for good , is the rom less lag 've had in this tablet.Parece the rom progresses quickly , I hope that is compatible soon with Screen Mirroring, S Pen, SIM card and SD Card as it will be the best ROM by far above the rest ...
No choice but to wait a little longer , sorry for my English and because there is already an official thread at XDA ? ...
SL2
Any news about the SIM card issue? Is anybody here using the LTE successfully his/her lt03lte with CM13?
OlafLostViking said:
Any news about the SIM card issue? Is anybody here using the LTE successfully his/her lt03lte with CM13?
Click to expand...
Click to collapse
I installed it yesterday - it was working surprisingly well. From what I could tell, it was working except for the following issues:
1. Can't remap the 'menu' hardware button
2. Camera not working/installed
3. Sim card not working
External SD card, wifi, google apps etc all working nicely.
OlafLostViking said:
Any news about the SIM card issue? Is anybody here using the LTE successfully his/her lt03lte with CM13?
Click to expand...
Click to collapse
I did a clean install of the cm-13.0-20160426-NIGHTLY-lt03lte.zip build but unfortunately the SIM card is still not recognised [emoji22]
Had a brief play and found it running smoothly but I need the SIM to work so it's back to AOSP 6.0.1 for now.
Sent from my SM-P605 using XDA-Developers mobile app
Tried a clean install of the 20160429 Nightly... still no SIM card detection chaps... wonder if @Schischu has committed any of his RIL work to their builds?
I have tried this ROM (cm-13.020160501-NIGHTLY) nothing majorly wrong with it except:
1. I don't have a sim card to test 4g/3g connectivity, so can't test phone/message/GPS functions as well. So these parts are unknown.
2. The quick view drawer (in home screen when you hold from top and swipe down to bring out system/profile/recent notification drawer), it display nothing except basic information like time/date profile head bubble. It will not display ANY notifications even you have new email etc. It always display "No notifications"
3. No lock screen, at all. So you can't preview any information like above. When you press home button it brings up your home screen straight away. If you have pattern lock / pin lock, yes you will have a lock screen normally, however again it will not have any notifications even you have new ones.
4. No USB connection option. On my Oneplus One (bacon) with CM13, when you connect USB cable to the PC, you can choose USB function from "charging" to something like "data transfer" etc. However, on my P605 (lt03lte) it displays nothing (since it can't display any notification). Even after enable USB debugging mode (which is called Android debugging in CM13), enable Debugging notify, changing "Select USB configuration" from "charging" to any other modes, none of above work. This is huge problem for me because this simply means I can't transfer any files from my PC to tablet and the mirco sd card.
5. For some reason all data from my micro sd card are not accessible, or I should say are not naturally supported. When you try to view eg. photos from micro sd card, and open "Gallery" provided, it will shows "0 images/videos available". However, it can be accessed when you go to Settings>Storage & USB>Portable Storage and you will see the micro sd card there. So you can copy files from system storage to micro sd.
6. It takes longer time to boot up compared to my Oneplus One and will have completely black screen (scary long waiting time, estimated about 15 seconds long) when you downloaded and flashed newer ROM. So be patient if you are updating. I experienced that "black screen" every time when I update my ROM or reinstalling through TWRP.
7. Camera not working, not a big issue for me but maybe for some people.
All processes I never experienced any softbrick.
I am not sure if it is just me or everyone is experiencing the same things. I will be glad if someone could point me the right direction to fix any of the above issues...
Other than above it is an awesome ROM, definitely cleaner compared to stock ROM.
If you wish to update to Marshmallow on your P605, I strongly recommend Schischu's Marshmallow ROM from xda-developers. (Google search: p605 marshmallow) It is very stable for me and seems no faults.
I am currently still sticking with "cm-13.020160501-NIGHTLY" ROM and hoping it will fix above issues when updates,
Feel free to ask me any questions,
im finding that i lose root when i upgrade everytime. and when that happens, if i charge with the device and switch it off, the battery icon stays there without disappearing
Ikaruga 斑鳩 said:
If you wish to update to Marshmallow on your P605, I strongly recommend Schischu's Marshmallow ROM from xda-developers. (Google search: p605 marshmallow) It is very stable for me and seems no faults.
Click to expand...
Click to collapse
While I agree that Schischu did good work you should mention that some things aren't working with his ROM, either. My main problem is encryption, for example. The CM is the very first custom ROM I found that is capable of encrypting the tablet (mandatory for a mobile device with personal data of me and other people, in my opinion).
With this rate of updates, soon we will have the best and final rom for our tabletas.He tested rom Schischu , but CM works much the better.You you need to solve the SIM , SD card and S Pen.Solo have to wait , yours would that opened in an official XDA thread to be attentive to feedback from users who are testing ...
SL2
Edit:
This is our maintainer! @Rashed97
Hi Rashed, above are some observations regarding a few bugs in the ROM, which i guess you are aware of.
Thank you for your work!
Hi everyone!
This is just my corner where I drop the builds of Lineage-15.1 that I personally use. They do contain a few smaller customisations, like a custom kernel and other goodies that I personally need. I'm posting this here in case somebody finds them to be useful.
Nooby Disclaimer:
I'm not a developer and just because I've got a thread here, doesn't mean I fully know what I'm doing when modding or building ROMs. What I publish is used by myself personally and thereby tested as daily driver. If something still breaks and your phone doesn't survive the smoke test, that's your problem and not mine.
Builds will mostly cater towards my needs if I have any special wishes with the hopes that the changes are useful or interesting for someone else as well (won't be too deep changes I think).
Some info/bugs specific to this build:
SELinux defaults to permissive
Make sure you tell OpenGapps to keep LineageOS Snap installed, Google Camera crashes.
Fails SafetyNet Test, don't use if you need that to verify.
OTA Support (Can somebody confirm that it works?.). The Updater should notify you of a new version.
Other than that, there's not much to say about it. It's LineageOS 15.1, what more could you wish for?
Download link:
http://tf2glados.dynv6.net:8080/
(It's in the LineageOTA folder)
Sources:
http://github.com/LineageOS
http://github.com/LineageOS/android_device_nextbit_ether
http://github.com/LineageOS/android_kernel_nextbit_msm8992
https://github.com/linckandrea/Pop-kernel-ether-LOS14.1-15.1
http://review.lineageos.org/
Mine mineminemineminemineminemine
Another one
It's kind of impressive you managed to miss that I post 15.1 unofficials in the 14.1 thread.
javelinanddart said:
It's kind of impressive you managed to miss that I post 15.1 unofficials in the 14.1 thread.
Click to expand...
Click to collapse
I'm going to ignore the passive-aggressiveness and just go ahead and argue that with time that my builds will deviate a tiny bit from vanilla Lineage here and there, be it only tiny tweaks and goodies like Pixel Navbar, kernel with Kali Nethunter support and OTA support. Besides, I wouldn't expect a 14.1 thread to contain Lineage15.1, now would I? Fss.
Alexandroid99 said:
I'm going to ignore the passive-aggressiveness and just go ahead and argue that with time that my builds will deviate a tiny bit from vanilla Lineage here and there, be it only tiny tweaks and goodies like Pixel Navbar, kernel with Kali Nethunter support and OTA support. Besides, I wouldn't expect a 14.1 thread to contain Lineage15.1, now would I? Fss.
Click to expand...
Click to collapse
No need to get snippy. Just commenting that I've been running builds for weeks now bringing up 15.1, and there's 40+ people in the hangouts group I made. I can't stop you from releasing builds or building from my sources (and nor do I care to), just letting you know that it's incorrect to say nobody's been building unofficials.
Sorry, I do apologise, but your comment did sound passive-aggressive even after reading over it multiple times. My point still stands though.
working like a champ but having issue with the figer print
karthikpl said:
working like a champ but having issue with the figer print
Click to expand...
Click to collapse
Working for me just fine. Just a tiny bit inaccurate as always.
http://tf2glados.dynv6.net:8080/LineageOTA/builds/full/lineage-15.1-20180401-NIGHTLY-ether.zip
Hello. I installed the UNOFFICIAL version. But the Nighly version is not. How do I install the Night version?
kinhkinhls said:
Hello. I installed the UNOFFICIAL version. But the Nighly version is not. How do I install the Night version?
Click to expand...
Click to collapse
Not sure what you are asking, but I had to override the build type branding to NIGHTLY in order to have the OTA server working. Just flash it over the old version. If you're using twrp and it doesn't want to flash, I'll have a Lineage recovery here, flashing that and then flashing the update using the lineage recovery always worked for me. http://tf2glados.dynv6net:8080/LineageRecovery/
Otherwise, just update TWRP. I tried it with the latest TWRP version just now and it works.
Download link is not working
Link is not working bro. Send me link
Quick note:-
OP is away at the moment and shall update the links upon return. :good:
Edit :- Download links are up an running.
Hello, thank you for working on this.
I flashed it yesterday and had an issue with mounting USB to my windows computer.
It worked on the first boot, and I was able to pull down the notification bar and tell it to transfer files. However on subsequent boots it did not give me such an option, although rebooting to recovery with the cable plugged in the same way mounted the device in my computer.
batp said:
Hello, thank you for working on this.
I flashed it yesterday and had an issue with mounting USB to my windows computer.
It worked on the first boot, and I was able to pull down the notification bar and tell it to transfer files. However on subsequent boots it did not give me such an option, although rebooting to recovery with the cable plugged in the same way mounted the device in my computer.
Click to expand...
Click to collapse
I haven't had any issues with that and I wouldn't consider it a build-specific bug, but I might be able to help you anyway. Plug in the phone, go to developer options and tap on "Select USB Configuration" and set it to MTP. That mostly fixes hiccups with USB modes for me. Otherwise, try replacing the cable if you're using the original Nextbit one that came with it. Mine became really unreliable soon after buying the phone, so I replaced it with a better (USB 3.1, even) cable and now it just works.
batp said:
Hello, thank you for working on this.
I flashed it yesterday and had an issue with mounting USB to my windows computer.
It worked on the first boot, and I was able to pull down the notification bar and tell it to transfer files. However on subsequent boots it did not give me such an option, although rebooting to recovery with the cable plugged in the same way mounted the device in my computer.
Click to expand...
Click to collapse
I might have found the technical reason behind it.
https://github.com/LineageOS/androi...mmit/99a8ea97e55cc7f9e28a2b7009325647110dc638
I'll rebuild when I get home, so that will include this fix.
Short note here, my Raspi server died on me again, so sorry for the dead links again. Buuut I'll be home soon, so I can get around fixing the Pi and the downloads will be up again just in time for a new build.
Enjoying the new build so far! Pretty good for me.
http://tf2glados.dynv6.net:8080/LineageOTA/builds/full/lineage-15.1-20180605-NIGHTLY-ether.zip
Its working on the s5 klte and s7 herolte. I was able to get 8.1 to run on our s6e+ and note 5. So now i will try 9.0. The stuff is syncing now. It will be a moddified lineage rom of some sort, so not original development.
Update, there is an alpha floating around here on xda, but despite loading, bluetooth and the launcher crash non stop and i cant do anything. I took the zip apart to play with and see if i can stabilize it.
Ok so, What I have done so far was I used the kernel from the alpha rom, took the s6 nexus os 9.0 rom, swapped the kernel around, changed the updater script, removed the Bluetooth files because they did not work, and I am still tinkering with other Bluetooth files from other roms and android versions, maybe 8.1 files will work? not sure yet. what I can say is that I have 9.0 running on my s6e+ with no Bluetooth, no call audio, and a working camera, no need to flash any other zips besides gapps, I have not played with it much but it works, it does not reboot randomly or crash, the apps ive used work. play store works. if anyone is interested let me know. I can put up a zip for a couple of devices to try it out, but be warned this is not any sort of official release, nor is it really my own work, more of something where I looked at a couple of different projects others had going on and found a way to combine it all to work for my device, without having to go through numerous steps to get the rom to boot. If I am going to put a zip up for people I will need to edit my first post and credit the people whose work I used and whatnot, then use my mega account to upload zips. this should work on the note 5 also, but I do not own that device. I have spent all day doing this, and normally I have to do school and work, plus my kids, I can not spent tons of time on this, does anyone want to help me figure out the call audio and Bluetooth? If not I will work on it by myself but it wont be a quick fix.
zenlte:
https://mega.nz/#F!Peo0FAjL!_eknpYZl8Ih-x2Hr9vSysg
no bluetooth, no call audio. needs testing. 9.0 pie
Call audio works now. No BT, camera buggy.
Bumping for interest.
Oh yeah. I'll add a T-Mobile zip tomorrow. Its been updated to Nov 5th patch
https://forum.xda-developers.com/s6-edge-plus/development/android-p-9-0-s6e-beta-t3858167
This is the link to main thread. Zenltetmo, zenlte, zenltecan, noblelte all with November security update.
Has anyone managed to get Android Auto to connect to their vehicle on their whyred?
I bought a new car last week and have been unable to get it to connect. Meanwhile my friends Blackberry KeyOne and iPhone both activated AA/Carplay immediately like they were supposed to.
I'm running Lineage 17.1 latest build, but I did see folks were having trouble with it a couple years ago. I was just hoping the situation had improved since then. I just updated the fw files from the Xiaomi firmware project and will try it again, but sadly I'm not hopeful.
If it does work for some of you, what rom are you using?
Thanks!
mik101 said:
Has anyone managed to get Android Auto to connect to their vehicle on their whyred?
I bought a new car last week and have been unable to get it to connect. Meanwhile my friends Blackberry KeyOne and iPhone both activated AA/Carplay immediately like they were supposed to.
I'm running Lineage 17.1 latest build, but I did see folks were having trouble with it a couple years ago. I was just hoping the situation had improved since then. I just updated the fw files from the Xiaomi firmware project and will try it again, but sadly I'm not hopeful.
If it does work for some of you, what rom are you using?
Thanks!
Click to expand...
Click to collapse
Problems with GAPPS I guess. Update both, car HUR and phone (gapps, Androidauto, play store,etc).
It's suppose to work normaly.. you can test it with MIUI ROM. You will need to delete LOS anyway if you wanna update FW the correct way (latest Fastboot MIUI ROM using PC).
Good luck and stay safe.
P.S.: I don't use gapps, to much troubles, and not privacy friendly and battery/data eater.
drnightshadow said:
Problems with GAPPS I guess. Update both, car HUR and phone (gapps, Androidauto, play store,etc).
It's suppose to work normaly.. you can test it with MIUI ROM. You will need to delete LOS anyway if you wanna update FW the correct way (latest Fastboot MIUI ROM using PC).
Good luck and stay safe.
P.S.: I don't use gapps, to much troubles, and not privacy friendly and battery/data eater.
Click to expand...
Click to collapse
What is the vendor security date of your device? (Unless its newer than Nov 1 2018 I'm already running the newest available vendor update and firmware.) The xiaomi firmware project updates the exact same files that the MIUI builds would.
Latest open gapps, android auto, etc are all installed. Headunit is updated to the latest version of Entune 3.0. The problem isn't the head unit. It's the phone. Old reports on here suggest it never worked with MIUI either. I was just curious if anyone has tried recently to see if the situation changed. I have zero desire to run that mess that is MIUI. It was bad enough using it long enough to get my bootloader unlock key. When you plug in the device you're presented with a menu on LOS that doesn't exist on other devices. (File Transfer, PTP, MIDI, Do Nothing). None of them do anything, so it appears that the MTP built into lineage doesn't know what to do with the connection.
mik101 said:
What is the vendor security date of your device? (Unless its newer than Nov 1 2018 I'm already running the newest available vendor update and firmware.) The xiaomi firmware project updates the exact same files that the MIUI builds would.
Latest open gapps, android auto, etc are all installed. Headunit is updated to the latest version of Entune 3.0. The problem isn't the head unit. It's the phone. Old reports on here suggest it never worked with MIUI either. I was just curious if anyone has tried recently to see if the situation changed. I have zero desire to run that mess that is MIUI. It was bad enough using it long enough to get my bootloader unlock key. When you plug in the device you're presented with a menu on LOS that doesn't exist on other devices. (File Transfer, PTP, MIDI, Do Nothing). None of them do anything, so it appears that the MTP built into lineage doesn't know what to do with the connection.
Click to expand...
Click to collapse
It's not LOS fault, it's car HUR or GAPPS(androidauto,..) fault.
Something is wrong in communication. I have 2nd device with LOS + GAPPS and all is working in my car HUR.
God luck and stay safe!
drnightshadow said:
It's not LOS fault, it's car HUR or GAPPS(androidauto,..) fault.
Something is wrong in communication. I have 2nd device with LOS + GAPPS and all is working in my car HUR.
God luck and stay safe!
Click to expand...
Click to collapse
You're leaving out a lot of necessary information, like your build of gapps and what your second device actually is. I have no doubt LOS works fine with Android auto on other devices, but I have yet to see any proof of it working on any whyred anywhere. You're just making assumptions and jumping to defend LOS without any proof whatsoever. You're ignoring the part where every post regarding AA on whyred posted on this forum in the past refers to it not working. It may not be LOS' fault in particular but it very well could be the device firmware never working with AA at all.
mik101 said:
You're leaving out a lot of necessary information, like your build of gapps and what your second device actually is. I have no doubt LOS works fine with Android auto on other devices, but I have yet to see any proof of it working on any whyred anywhere. You're just making assumptions and jumping to defend LOS without any proof whatsoever. You're ignoring the part where every post regarding AA on whyred posted on this forum in the past refers to it not working. It may not be LOS' fault in particular but it very well could be the device firmware never working with AA at all.
Click to expand...
Click to collapse
Ok ok I have 2 whyred devices(2nd has smashed screen, i leave it connected in car)...hope that makes sense now
Let me simplified this... whyred and android auto is working! Yeah you need to hasel a bit but its working, at least in my Nissan OEM HUR from 2019. You just need to find right GAPPS version. I think its from feb. 2020, anythig newer breaks androidauto. Than just freeze all google stuff or it will update and breaks again. I cant remember all details couse it's too long ago I did it. Sorry, but you'll need to experiment by yourself.
Ahh almost forget...my FW is 10.0.3 I think. Not the latest.
Good luck and stay safe.
It's a big gapps problem and not about the devices. I am on redmi note 4x and have the same problem. My whyred have too. All original devices work. And my mido work before too. Its all about gapps.
I am very much thankful for all developers here but please don't talk its fixed. Its not especially on android 11 builds. There is non fully working gapps out just betas talk work but not. I have many devices. I flash and hundreds of others cellphones.
For all people search. Help to develop or wait for a right gapps build and report to all.