FYI: Bionic can run Lineage 14.1 (Android 7 Nougat)

FYI: Bionic can run Lineage 14.1 (Android 7 Nougat) - Motorola Droid Bionic

Thanks to these wonderful people http://droid.cs.fau.de/ . Those of us still using the bionic can keep pace with the rest of the world.
I just did a fresh install of Lineage 14.1, OpenGapps 7.1 nano, and data restore from my backup. So far everything looks good. I will update if I find any major problems.

Update: So far everything is seems to be working except tethering. I try a total clean install and a dirty flash.
Update 2: dirty flash works but still no tethering.
Update 3: total clean install works, still no tethering and the GPS did not won't to lock on.
This appears to be a school project so i don't know how long they will keep it going. They seem to release once a week so i will check for a new one on the 18th.

No update as of yet. I did find out this is Stargo's work from the Droid4 . https://forum.xda-developers.com/droid-4/development/rom-cm14-1-nougat-t3499338. I did upate to CM14.1 (dirty) and it works really well. I tried to dirty flash to Lineage14.1 and everything seems to work except teathering. Thanks Stargo.

Curious, have you had any luck rooting Lineage 14.1 on the Bionic? I'm on the official 13.0 builds and no root method (tried flashing SuperSU, Magisk, and Lineage's root add-on; even tried Kingroot) seems to be working so far. SafeStrap just gives me a "Failed" message whenever I flash any root package.

Been running Lineage 14.1 on my Bionic since late April, replacing a DroidX as my daily WiFi-only pocket Android device, as I'm still one of those hold-outs with an aaaancient Palm Centro for just making calls and texts.
Aside from some minor slowdowns in regards to thumbnail generation (especially while selecting multiple images in Discord's new image upload mechanism introduced a couple months ago) and some other interesting color funkiness when opening and using OpenCamera over the stock camera app (preferential choice, YMMV) it has been quite the amazing experience to use Android 7.x on a phone made in 2011.
Found that introducing L Speed into the equation and Greenify does help with some battery chugging issues I experienced at first. one of the cheap ~4000mAh nonamebrand extended packs available from eBay/Amazon now seems to last me a solid 20-something hours before it's time to plug in if I haven't used it much. changing the font using FontFix to Roboto Condensed over stock seems to have also helped with some real-estate issues, again strictly preferential. There's also the normal occurrence of the MTP Host process hanging and killing itself on occasion, but not too much of a worry really for me.
Also still not quite understanding of how the filesystem is partitioned in regards to Safestrap too well, especially with how limiting it is on disk space inside the partition per slot.
J-Lindo said:
Curious, have you had any luck rooting Lineage 14.1 on the Bionic? I'm on the official 13.0 builds and no root method (tried flashing SuperSU, Magisk, and Lineage's root add-on; even tried Kingroot) seems to be working so far. SafeStrap just gives me a "Failed" message whenever I flash any root package.
Click to expand...
Click to collapse
for the unofficial 14.1 ROM there's already a method in the settings to allow root to any app that requests it in the same way that apps must now ask for permission to record audio/access files and whatnot, but I believe this is something you need to go into the security settings and turn on.
EDIT: The way to get in and do it is to enable the Developer Options menu and modify the Root Access setting in there. Privacy Guard should then take over and allow for apps to request Root and allow it as necessary based on your input.
{
"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"
}

Sudosftw said:
for the unofficial 14.1 ROM there's already a method in the settings to allow root to any app that requests it in the same way that apps must now ask for permission to record audio/access files and whatnot, but I believe this is something you need to go into the security settings and turn on.
EDIT: The way to get in and do it is to enable the Developer Options menu and modify the Root Access setting in there. Privacy Guard should then take over and allow for apps to request Root and allow it as necessary based on your input.
Click to expand...
Click to collapse
Huh, it's just there in the unofficial version? Interesting. It isn't there in official 13.0 (only for ADB). But hey, looks like 14.1 is official now, so I'll break out the old Bionic and try my luck at it. I'll edit this later with my results.
Edit: Official 14.1 yields same results when trying to flash any su add-on, including SuperSU and Lineage's. However, you said on the new thread that it is working, so I'll try it out again when I can.

I'm using CM13 on my Droid Bionic, and in Developer Options, there is a "Root Access" option, and it does have the choices of "Disabled", "Apps Only", "ADB Only", and "Apps and ADB".

Erratic WiFi issues...
Sort of a follow-up. with the June 10th build I notice that if the phone is on for more than a few days at a time, the WiFi radio becomes erratic. shutting it off for a bit and turning it back on fixes this, but it also continues, as has happened in previous 14.1 builds, to start behaving erratically at random when the phone is disconnected from the previously-connected AP from range loss and then travels with me. it can be as far as just across town, or further, or a shorter distance, depending on where I'm going. the distance matters not, and result is the same: loss of connectivity and in no way can I get it back unless I perform a hard-reboot of the phone.
It can get very annoying very quickly depending on where I am and how badly I need a WiFi connection. I'm wondering if this a WLAN driver issue of some kind or if this is just an erratic bug that manifests itself over time-- the network selection screen also becomes erratic like the selected network is having a seizure. this seems to happen the most on xfinitywifi hotspots more than others, but that's just the norm of what I'm connecting to most of the time. it does it more when it's in a lower range, but it also does it if I'm right on top of the hotspot sometimes, as well.
If anyone else is noticing this sort of erratic behavior, I'd love to hear about it and if anyone's figured out any sort of solid solution aside from just rebooting the phone. There's a good chance that within the coming month I might finally be able to do a clean switch from my current ancient Palm Centro and up to this glorious piece of work, and all the trials and tribulations that come with it.
I'm also curious to know if this bug exists on the official 14.1 builds from 2017-06-16 and 2017-06-23 respectively, and with the 13.0 builds... Depending on how things work out, one of these ROM builds is going to have to be stable enough to keep the WiFi from going nuts on me, and I'm going to have to use it, depending on where I am phone-wise within the next month.
Edit: the WiFi issues have been fixed in the official builds. there is now a thread for the official LineageOS ROM over here on the Android Development subforum.
(Edit 2: Phone was my daily from June 27 until August 19th. I've since retired it for a Droid Razr, same family spec but faster CPU (1.2GHz over 1GHz). over the course of the time I was using it the Lineage builds only made things better. recently the ART cache was increased to 192MB for 1GB RAM devices (AKA this, the Razr, Droid 4, etc. of the same family spec) and I'm not sure if it was that or some other change but battery life on the Razr certainly went up (2d ~ish per charge), I'd have to expect this would be the same deal with the Bionic but your mileage may vary depending on battery age and usage scenario.
the Bionic doesn't have nearly as many users stats-wise on Lineage over the Razr/Droid 4/etc. and I think that's why it seems to be a bit low key for support, but there's enough of the other phones and a lot of the hardware is the same to keep everything running. my only hope is that support for this device continues as long as the others are and isn't dropped for reasons of low interest in the port. it's a great phone-- and as the first 4G LTE dual-core device for Verizon in the US, it's still holding strong against all that came after it. )

I had a Bionic I used recently. Actually it's still being used by a friend. I tried the Lineage 14 Nougat when it first came out. I found it intolerably slow. I'm willing to try it again though. What I'm really looking for is an old CM10 or 11 ROM for the Targa. I can find lots of dead links but so far haven't found an actual copy

equitube said:
I had a Bionic I used recently. Actually it's still being used by a friend. I tried the Lineage 14 Nougat when it first came out. I found it intolerably slow. I'm willing to try it again though. What I'm really looking for is an old CM10 or 11 ROM for the Targa. I can find lots of dead links but so far haven't found an actual copy
Click to expand...
Click to collapse
http://web.archive.org/web/20170112212548/http://download.cyanogenmod.org/?device=targa
Web Archive is a free site, not meant to be file host, so if you download, please try to reupload to android file host or or other, and consider donating to both
Sent from my XT1254 using XDA Labs

sd_shadow said:
http://web.archive.org/web/20170112212548/http://download.cyanogenmod.org/?device=targa
Web Archive is a free site, not meant to be file host, so if you download, please try to reupload to android file host or or other, and consider donating to both
Sent from my XT1254 using XDA Labs
Click to expand...
Click to collapse
Thanks,
I had forgotten about web archive. It turns out a little more digging here brought up a link to a copy of CM12 which I put on the device today. Originally the phone had one of my first efforts at a custom ROM so a lot of bugs.
I'd given it to a friend who was using it but complained about the bugs and sluggishness. He thought it had a virus. I told him that it was clean for viruses and malware but because he'd surfed so much porn it had an electronic STD.

Should I use a specific filesystem? or is it locked to the rom? There are options for FS2S, EXT4, but it seems the default is EXT3. Those others would be speedier.

3of12 said:
Should I use a specific filesystem? or is it locked to the rom? There are options for FS2S, EXT4, but it seems the default is EXT3. Those others would be speedier.
Click to expand...
Click to collapse
Agreed. I've tried formatting System (and Data, I think—it's been a while) to EXT4, but alas, it stubbornly stays on EXT3. I figure there's some technical explanation somewhere :silly:

Overclocking
J-Lindo said:
Agreed. I've tried formatting System (and Data, I think—it's been a while) to EXT4, but alas, it stubbornly stays on EXT3. I figure there's some technical explanation somewhere :silly:
Click to expand...
Click to collapse
Yeah I remember exactly that being a thing. Also we need overclocking info for all new roms. 1.3 and 1.4GHz make a huge difference. I used to use CM13.1 and there was a custom kernel for that.

Related

[FEEDBACK] Droid3 KEXEC kernel ROM thread

This thread should be used for specific feedback relating to KEXEC based ROMs (CM10/AOKP).
DOWNLOAD ROMS:
http://goo.im/devs/Hashcode/solana
I know many users don't have enough posts to add to the development thread.
RULES: Please read through the thread and make sure you aren't posting a duplicate issue or one that's been answered.
CURRENT NOTES (Gathered from feedback):
BUGS FIXED:
Better stability, everyone agrees very few random crash/lockups
KNOWN ISSUES:
Still considerable battery drain. This is due to several hardware components not sleeping correctly: CPU1, MPU and others. More work needed.
HW decoding is currently being revamped to use less memory (see YouTubeHD / netflix)
No camera function (at all). This will be a long-term fix with a new kernel driver for each camera sensor.
** MMS is a work-in-progress on *ALL* of our Jellybean ROMs. We are using a brand-new telephony-common .jar via Google "master" branch to solve our multiple radio / international switching issues. The downside is that Google hasn't decided how to handle MMS on this branch.
For now use GoSMS from the market.
DEVICES TESTED:
Verizon Droid 3 (XT862):
STOCK-RADIO:
*should* be mostly working (where noted) using the .zip files from me.
CHINESE-RADIO FOR US GSM:
Needs build.prop edits found here:
http://forum.xda-developers.com/showpost.php?p=33102553&postcount=422
China Telco XT883:
?? Might need specific patch to boot.
Canada XT860:
Can boot, but no 3g and warm cpu due to cycling services. Dev needed w/ a device to create a patch for full function.

Ok here goes:
Been running JB CM10 1103 for more than a full day.
- I'm using Strict memory settings from ROM toolbox and disabled HW overlays, and nova launcher from AOPK
Good:
- 0 crashes but 1 reboot
- Pretty fast, no really hangs. In fact it might be even faster than mavrom 4.5 for me
Bugs: (apart from the known like proximity sensor etc.)
- I've noticed that when sliding the keyboard out before unlocking the phone, the screen sometimes doesn't rotate to landscape properly. I have to unlock and close/open the keyboard to get it in landscape.
- I fixed the bug where it shows 1% battery in JB by charging to 100% in my stock ROM, and then wiping stats with battery calibration app.
It does return after reboot
Battery
- Used phone all day normally, in fact more than usual I think. It's not bad but I have a 1900mAh battery so should be better. Idle seems OK for some reason.
{
"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"
}

Long time user, first time poster
First and foremost, HASHCODE- You are amazing and so is your work. Thank you from the bottoms of my feet. (Heart isnt low enough for what you do.)
Now on to some actual feed back.
I am about to load up your 11-04 build, but my question is does WI-FI TETHER work and what do I need to use? I've tried the built in version and 3rd party apps to no avail. I have seen conflicting answers to others' request on the matter but haven't had solid answers that have worked. I have VERIZON X862. Thank you ahead of time for any other future advancements you will bring us.

just adding:
on hard keyboard alt keys do not work

Mms on vzw 862 not working either still...
Sent from my XT862 using xda app-developers app

aokp
been using aokp since i got ss3 and was able to test jb,cm10 and aokp. i stayed on aokp the screen sometimes goes out and is very dim also enough lag to crash the phone or i just have to wait hopefully not a repeat i could see how this would tie in with crashes. still enjoy it very much thank you so much hash

Hashcode: US GSM networks work perfectly on the XT883 radio using the build.prop I made based on your 10-18 CM10 Kexec (and works on latest as well.) Info and uploaded here; http://forum.xda-developers.com/showpost.php?p=33102553&postcount=422 I get HSPA 14.4Mbps (actual speeds around 5.5 on att in my area) and it shows an H instead of 3g Wish mavrom did that.
For others needing info, read the thread in dev section for unlocking for att/tmobile, I post my findings there. Including (awhile back) of getting somewhat dual mode on us vze/gsm without radio swap. I was able to receive sms, calls, and 3g data on vzw with xt883 radio, couldn't call out or send sms (could use google voice for sms and grooveip for calls over data though). Then swap to gsm mode for my sim.
Back on subject, built in tether works on xt883 gsm fine, mms, etc. Only issues are known issues, all radio aspects work.

Skreelink said:
Hashcode: US GSM networks work perfectly on the XT883 radio using the build.prop I made based on your 10-18 CM10 Kexec (and works on latest as well.) Info and uploaded here; http://forum.xda-developers.com/showpost.php?p=33102553&postcount=422 I get HSPA 14.4Mbps (actual speeds around 5.5 on att in my area) and it shows an H instead of 3g Wish mavrom did that.
For others needing info, read the thread in dev section for unlocking for att/tmobile, I post my findings there. Including (awhile back) of getting somewhat dual mode on us vze/gsm without radio swap. I was able to receive sms, calls, and 3g data on vzw with xt883 radio, couldn't call out or send sms (could use google voice for sms and grooveip for calls over data though). Then swap to gsm mode for my sim.
Back on subject, built in tether works on xt883 gsm fine, mms, etc. Only issues are known issues, all radio aspects work.
Click to expand...
Click to collapse
Thank you so much for pointing this out. I'm not sure how I missed this. I have a TMO SIM in my D3 for testing and I haven't had a chance to get the phone working in quite a while.
Updating OP.

ovelayer said:
just adding:
on hard keyboard alt keys do not work
Click to expand...
Click to collapse
It works for me. Except the @ launching the e-mail app instead of writing @
Oh, and for me the lockscreen unlocker on CM10 is way out of place while in AOPK it's correct

general feedback
I am on Vodafone NZ running cm10 20121018
Simply unticked the 2 options under Settings, More...(default ones can not recall name now sorry) and after this the phone sorted out it's own APN settings and instantly started working on 3G / HSPA?.
Can honestly say I do not notice ANY battery use worse than stock ROM, seems the same to me? clocked CPU at 1008Mhz
+1 for reception on 3G in general, this is honestly better than it has ever been and I would know given on stock ROM unless standing by lounge window (with one eye closed, tippy toes and poking out tongue) it was not possible to get 3G, now it appears 80% of the time anywhere in the house it is on 3G !!
Occasional freeze, only times for me is when typing a text with on-screen keyboard and other times about to type an e-mail in K9 Mail.
Other than that running all round amazing in my opinion, motivated me to buy a replacement screen / digitizer !
Thanks for your work Hash, this phone would have long been ditched had it not been for your committment and skills.

just had my first random reboot. immediately my battery jumped ffrom 75 to 35. i havent swapped roms or been into ss3 since install.. gotta go back into gb now to charge to 100. btw as you can see altkeys dont work for me here but they do work in whatsapp

A +1 from the land of OZ as well. With 'alt telephony' off and world mode on, every thing I need seems to work i.e. I can make and receive phone calls and 3G/HSDPA data seems to work. The 1018 build wouldn't receive phone calls - phone.app would crash in response to an incoming call.
The phone worked out the APN for my carrier by itself once the right settings for mode were selected.
Power consumption doesn't seem that different from the old CM9 I was running or stock.
It would be nice to have a working camera, but thanks to SS3 I can swap to 'stock' if I find I need a camera and I don't have my DSLR handy.
I have had what appear to be random UI freezes where the phone wouldn't respond. But things were obviously working in the background as I got a new email notification while the UI was frozen in one instance.
Also a couple of instances where the UI didn't rotate to follow the orientation of the phone and after a while it appeared to unstick itself.
But since I can send/receive emails and make/receive phone calls, the ROM does what I need of it.
(I've not tried SMS or an MMS, SMS isn't something I use a lot with a phone that does email).

I saw a while back a statement about "sensors" not working properly so I assume what I'm posting is known, but GPS doesn't seem to work for me.

Phone app crash
Not sure if this is a known issue or not, and it only happened once, but when i was on a call and the other party disconnected unexpectedly, the phone app just crashed.

X_Jezreel said:
I saw a while back a statement about "sensors" not working properly so I assume what I'm posting is known, but GPS doesn't seem to work for me.
Click to expand...
Click to collapse
The gps works fine in 3rd party apps, but does not work in maps/navigation. Gps status & toolbox gets a fix quickly, shows accurate speed, etc like it should, but navigation sticks at searching for location, although the statusbar icon stops blinking and gets a fix. Maps just can't access it, permission issue?

gps was flaky for me when I first installed the rom..
I used gpsfix and now my gps works just fine..

Well, with a quick test, I can verify the problem is with maps. 3rd party nav app Sygic works as expected, fix in about 4 seconds for me. Maps will get course location from network, just not the gps module. I personally do not use network location.

Bluetooth access point doesn't work.
It pairs with my laptop but then doesn't install any drivers.
(but these things would be my last concern )

minimalist text?
Not sure about this one, but in 2 different launchers my minimalist text widgets don't ever actually load, they just say "loading", could be something stupid i'm doing, but this is the first trouble i've had with it.

I downloaded and am running the KEXEC-cm-10-20121103-UNOFFICIAL-solana on my D3 on Verizon and I noticed a small issue with Bluetooth. When I am in my car, and the device is paired up, I can't stream audio if my phone is plugged into the car mount or in car mode. However, if the phone is not in the mount or car mode it streams audio perfectly. Is there a known issue with dock audio in this build? Regardless of this small issue, I just wanted to say thanks to Hashcode for all of his awesome work supporting the D3! You ROCK sir!!!!

[Q] CyanogenMod & WiFi Hotspot/Tethering

Dear XDA HTC Desire C Users,
Let me start off by saying I know that this question has been asked before. I've lurked these forums since 2010, I've flashed many devices with many custom roms and kernels. I just want to know what the deal with CyanogenMod is.
I've recently come into possession of a HTC Desire C. It's a great little phone, not what I was expecting at all when I bought it off a bloke at work for £30. Started it up and it was bogged down with all the normal crap you get when someone has a lock stocked phone. Decided to check out XDA once again, and found that there was a port of my favourite rom; CyanogenMod.
I've previously used CM on my Galaxy Europa, Galaxy S 3, Galaxy S4, Nexus 7 and Xperia Play. Using my phone as a WiFi Hotspot/for Wifi Tethering (however you want to say it) was only ever a problem on the Xperia Play (and possibly the Nexus 7, I haven't actually tried). The checkbox would tick, the writing would say "Turning on wireless..." and then that would be it. It would never complete the action. USB tethering has never been an issue, and I never really needed wireless tethering until I got a Nexus 7 around Xmas. Funnily enough, my Xperia Play broke at the same time, and I went back to using the old Europa (CM7, working wifi tether).
Now I've loaded this Desire C up with CM10 with NOPE Kernel v2.6, tried this wifi fix that a lot of people seem to enjoy linking to (granted, it does make WiFi work, but not tethering). Some other suggestions were to use Barnacle WiFi Tethering app, but it creates an ad-hoc connection which a Nexus 7 can't connect to.
I guess it's really a few questions, which I can summarise here for those of you unwilling to read the above text :
- Why does CM have working WiFi hotspot/tether settings on most of my previous devices and not the HTC Desire C?
- Has anyone actually ever got their Desire C to tether with CM10 (any version for the HTC Desire C)? If so, how?
- Are all JellyBean roms having this issue?
- I've read that Sense based ROMs are the only ones that have functional wifi tethering settings. If so, that means I'd have to use an ICS ROM to be able to use wifi tethering?
- Am I doing something wrong? The past few years I've had to relearn how to do all this stuff to a different device each time, I may have missed something that's more prevalent to someone who is immersed in this regularly. My process was as follows -
1) Downloaded CM10 Build 3, TWRP 2.4.2.0, GApps & Nope Kernel v 2.6 (700mhz)
2) Flashed TWRP 2.4.2.0 as recovery (fastboot flash boot recovery.img)
3) Rebooted into Recovery
4) Backed up, wiped & flashed (Factory Reset, Cache, Dalvik, System)
5) Installed CM10 and Gapps (install .zip from sd)
6) Rebooted to Bootloader, flashed NOPE Kernel (fastboot flash boot boot.img)
7) Rebooted to Recovery, wiped Cache/Dalvik Cache
8) Started phone, set up, tried WiFi Tethering.....nothing happened.
As far as I can see, I've probably missed one detail that is affecting the entire process. I assumed that since this was cute_princes v3 marked as "wifi fix", that I wouldn't have to put the folder I linked to earlier onto my phone (the file contatining p2p_supplicant_overlay, wpa_supplicant and wpa_supplicant_overlay).
To confirm, I tried the boot.img that came with CM10, it was some form of Prometheus and that didn't work either. I have tried MiniCM10 as well, same results there. I have flashed NOPE Kernel v2.6 on both CM10 and MiniCM10, to no avail. I also tried the boot.img that was packed with MiniCM10, same result.
Sorry for the long post, but I feel that it's better to over-explain yourself, rather than leaving people guessing. If anyone could shed some light onto this, I'd be very grateful. It's something that made me curious enough to post after 4 years of silence and lurking in the background. The fact that I've managed to root and flash all the previous devices I've owned without ever having to make a post shows that all the information is available to me on this site, and that XDA is such a great place that this information is readily available for me. But in this case, I can't find what I need, so I call to you for help.
Thanks in advance,
Gordon Freeman

It's a cm10 bug.... I don't know if too many people have looked into this....
Sent from my HTC Desire C using XDA Premium 4 mobile app

rudi_j7 said:
It's a cm10 bug.... I don't know if too many people have looked into this....
Sent from my HTC Desire C using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That's the answer that I hear the most, and I never hear anything more than that. What kind of bug prevents it on certain phones? Why do Sense roms (apparently) have working wifi hotspot?
All my other questions are still open, plus a lot more for discussion. I am only a couple of months away from buying a Nexus 5 anyway, but I need this phone to wifi hotspot in the meanwhile.

Sense ROMs have working Wi-Fi hotspot as they are sort of a modified stock ROM....
Sent from my HTC Desire C using XDA Premium 4 mobile app

rudi_j7 said:
Sense ROMs have working Wi-Fi hotspot as they are sort of a modified stock ROM....
Sent from my HTC Desire C using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So you're saying that I have to use an Ice Cream Sandwich ROM if I want to be able to use wireless hotspot/tethering? I'm assuming that if there are no JellyBean ROMs that have working wifi tethering/hotspot, then it has something to do with the phones hardware being unable to work with a newer Android OS. But I'm pretty sure I've read people having success with tethering on JB ROMs.
Maybe someone could point me in the direction of having CM10/any JB ROM with working wifi hotspot/tethering, I'd be grateful.

THIS has been such a deal-breaker for me with the CM10 ROMs. But... Fear not!
The recent MiniCM10 by warrior1208 has fully functional USB and WiFi hotspot tethering! Yippeee! Definitely give the guy/girl credit.

beanaroo said:
THIS has been such a deal-breaker for me with the CM10 ROMs. But... Fear not!
The recent MiniCM10 by warrior1208 has fully functional USB and WiFi hotspot tethering! Yippeee! Definitely give the guy/girl credit.
Click to expand...
Click to collapse
Are you sure that wireless tether is working in Mini CM10? I've flashed this ROM with the provided boot .img and Nope 2.6, and tether did not work. I'm pretty sure I applied that Wifi Fix as well, and nothing seemed to work for me.
Is anyone using a Jellybean ROM with tethering working? I just need to replicate as many possible working combinations of ROM and kernels,so any suggestions of combos would be awesome.

I'm posting this message via WiFi Hotspot. MiniCM10 V3, N.O.P.E. v2.6 850Mhz. No wifi fix applied apart from the WiFi keepalive app (Enabled workaround 2, reselect Always On). USB tether works too, as I use it to install Arch Linux before setting up laptop wireless drivers.
I haven't tried V4 yet. I have a Desire C non-NFC.

beanaroo said:
THIS has been such a deal-breaker for me with the CM10 ROMs. But... Fear not!
The recent MiniCM10 by warrior1208 has fully functional USB and WiFi hotspot tethering! Yippeee! Definitely give the guy/girl credit.
Click to expand...
Click to collapse
First of all, I am a boy! xD...
And yes USB tether works for me...but I didn't try wifi hotspot...
If you can post a screenshot on MINICM 10 forum, then it would be great, so that all people having problems with other also roms come to know...
Thanks!

beanaroo said:
I'm posting this message via WiFi Hotspot. MiniCM10 V3, N.O.P.E. v2.6 850Mhz. No wifi fix applied apart from the WiFi keepalive app (Enabled workaround 2, reselect Always On). USB tether works too, as I use it to install Arch Linux before setting up laptop wireless drivers.
I haven't tried V4 yet. I have a Desire C non-NFC.
Click to expand...
Click to collapse
Thank you for your contribution to the thread. I only have the latest MiniCM10 (V4), but I am also using Nope 2.6, just a lower frequency (700mhz, i have no need for a large OC). I've just clean flashed it back onto my Desire C, and the same results as before. Here are a few screenshots, sometimes screenshots help :
Kernel Version
{
"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"
}
ROM Version
WiFi Working (Worked after turning it on then rebooted phone. WiFi was on once rebooted)
Wireless Tether NOT Working
On the last picture, if I back out into the previous menu then re-select to go back into the tethering sub-menu, the "Turning on WiFi..." message disappears and the checkbox is ticked, yet there is still no hotspot being produced.
So I must be doing something wrong still?
EDIT : So I've just flashed on the same kernel and CMMini version as you've said has worked for you. I've installed the "WiFi KeepAlive" app, but I am yet to launch it, as the description of the app (which is very vague) does not seem to mend the ailment that I am having.
I'm providing screenshots of the latest and current installation on my phone. I am not sure if anything in these is out of the ordinary, but maybe someone can tell me if I've done something wrong by looking at my "About Phone" section. Once again, I've provided screenshots of the wifi tether not turning on correctly :
About Phone 1 (Kernel and Baseband Version)
About Phone 2 (CM Version, Build Date and Build Number)
WiFi Tether (Unresponsive, stuck on screen until pressing Back)
WiFi Tether (Shows after exiting and entering again, produces no hotspot visible to other devices)
Working WiFi (After switching on then rebooting, wifi becomes available, but no hotspot)
So if anyone has anything to add, I'd be grateful once more.
Thanks

So after messing around for a while, I've managed to make a slight amount of progress. I feel like I'm almost there now.
I renamed my hotspot "testet" (meant to type "tested", never changed it) and set up WiFi KeepAlive. Using Workaround 2 and Always Keep Wifi On, I managed to get my Nexus 7 to see the hotspot. That's as far as I got, as trying to connect breeds a varying set of results. Whilst it can see the hotspot, it can never fully authenticate. It will hover on "Obtaining IP Address..." and "Authenticating..." before giving me "Saved, secured with WPA2" but not actually connecting to the Internet, or it will say "Avoided poor Internet connection" (or something to that effect). It's frustrating being so close, yet so far. Here are some more screenshots to demonstrate my finds :
Nexus 7 Wifi Screenshots (Various)
The "Turning on Wifi" thing disappeared on my phone and gave me a solid checkbox ticked for once, without having to back out then back in to the menu
See the edit to my previous post to get up to speed on where I am with kernels/ROMs installed.
Thanks again.

So I guess that no one really has any clue about this? Out of the +1,000 views of this thread, only a couple of people could actually contribute?
@warrior1208 , you ported this version of CyanogenMod, and you seemed to think that wifi tether works. Maybe you could shed some light on what I might be doing wrong? I won't have answers such as "It's a known bug", you've pulled the ROM apart and put it back together again, surely you must have some idea about what's going on? I will try to help as much as I can.
@beanaroo have you seen my responses? I have replicated the same setup as you, and had no success at getting this to work. Since you have confirmed that it works, maybe you could give me some advice on what I may be doing wrong?
Failing that, recommend me a JellyBean ROM for this troublesome little phone that has wireless tethering working. I know the common response would be "look through them yourself", but obviously some ROMs claim to have working wifi tether and they do not seem to work when I try them, so if I could get a recommendation then I wouldn't have to trawl through all the "broken" ones and find one that actually works.
No offence to anyones ROMs, it's just that wifi tether is paramount in my use of a phone, and I really wouldn't like to go back to the childish looking ICS ROMs. I don't want to discard this phone either, it's a nifty little thing and I'm quite fond of it.
Thanks again,
Gordon Freeman

Gordon Freeman said:
So I guess that no one really has any clue about this? Out of the +1,000 views of this thread, only a couple of people could actually contribute?
@warrior1208 , you ported this version of CyanogenMod, and you seemed to think that wifi tether works. Maybe you could shed some light on what I might be doing wrong? I won't have answers such as "It's a known bug", you've pulled the ROM apart and put it back together again, surely you must have some idea about what's going on? I will try to help as much as I can.
@beanaroo have you seen my responses? I have replicated the same setup as you, and had no success at getting this to work. Since you have confirmed that it works, maybe you could give me some advice on what I may be doing wrong?
Failing that, recommend me a JellyBean ROM for this troublesome little phone that has wireless tethering working. I know the common response would be "look through them yourself", but obviously some ROMs claim to have working wifi tether and they do not seem to work when I try them, so if I could get a recommendation then I wouldn't have to trawl through all the "broken" ones and find one that actually works.
No offence to anyones ROMs, it's just that wifi tether is paramount in my use of a phone, and I really wouldn't like to go back to the childish looking ICS ROMs. I don't want to discard this phone either, it's a nifty little thing and I'm quite fond of it.
Thanks again,
Gordon Freeman
Click to expand...
Click to collapse
USB Tethering works flawlessly on MINICM10, whereas, for a working wifi hotspot(which is a CYANOGENMOD BUG), we would have to correct the wifi hotspot modules in the github source, and then produce a new build...
So, since we are not working for achieving that, we would never get wifi hotspot on aosp cm based roms...
I hope this information may clear up your doubts...
Here is a screenshot to prove that usb tether works in my ROM...

Unless someone makes a new build WiFi hotspot won't work and since most of the developers are now focusing on building cm11, it is highly unlikely that someone will create a cm10 build 4. You could try using Bluetooth hotspot as an alternative maybe?
Sent from my HTC Desire C using XDA Premium 4 mobile app

rudi_j7 said:
Unless someone makes a new build WiFi hotspot won't work and since most of the developers are now focusing on building cm11, it is highly unlikely that someone will create a cm10 build 4. You could try using Bluetooth hotspot as an alternative maybe?
Sent from my HTC Desire C using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have been using Bluetooth tethering, but it's far from what I require. It's quite slow, and Bluetooth drains battery pretty quick. The range is also very limited. Fair enough, I keep hearing the same "it's a known bug in CM10", so what about JB ROMs that aren't made from CM10?
warrior1208 said:
USB Tethering works flawlessly on MINICM10, whereas, for a working wifi hotspot(which is a CYANOGENMOD BUG), we would have to correct the wifi hotspot modules in the github source, and then produce a new build...
So, since we are not working for achieving that, we would never get wifi hotspot on aosp cm based roms...
I hope this information may clear up your doubts...
Here is a screenshot to prove that usb tether works in my ROM...
Click to expand...
Click to collapse
I'm fully aware that USB Tethering works on your build, if you had read any of my posts you'd realise that I already knew that. There was never a dispute as to whether USB Tethering was working. My problem is that @beanaroo claims that he has WiFi Tethering working with your ROM, and you seemed to acknowledge the fact that he had it working. So how can one user make something work that you (the builder of this ROM) claim doesn't work? Unless he is lying, then it must work?
So, other JB ROM alternatives to CM10 then?
EDIT : @warrior1208 I just noticed that your screenshot of your phone shows that Portable WiFi Hotspot is ticked. I know you can select it, go back in the menu and then go forwards again and it remains a solid tick, but why would you include that if you just admitted that it doesn't work? Strange.

Since the only source built jb ROM is cm10, all other ROMs are ported using cm10. That's why the bugs of cm10 are there in every ROM. If someone fixes the tethering and makes a patch or something then it would work. But so far no one has really taken it onto themselves to fix the bug..... So maybe if you could do something......
Sent from my HTC Desire C using XDA Premium 4 mobile app

rudi_j7 said:
Since the only source built jb ROM is cm10, all other ROMs are ported using cm10. That's why the bugs of cm10 are there in every ROM. If someone fixes the tethering and makes a patch or something then it would work. But so far no one has really taken it onto themselves to fix the bug..... So maybe if you could do something......
Sent from my HTC Desire C using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Point me in the direction of a ROM building tutorial and I'll happily try my hardest to get it working. I'm not a pro in this kind of thing, but I've been using computers for a couple of decades now so I'm sure I could give it a try. Plus it gives me a reason to get into Android development, as I love Android. I'm totally willing to put some effort into fixing this issue, even if it's just for me. If you could give me pointers on where to look, then I'll give it a shot, although if the CM guys can't do it then I really doubt I'll have a chance.
After all of this, I'm guessing that @beanaroo was lying about his ability to wifi tether on this ROM then?

Gordon Freeman said:
I have been using Bluetooth tethering, but it's far from what I require. It's quite slow, and Bluetooth drains battery pretty quick. The range is also very limited. Fair enough, I keep hearing the same "it's a known bug in CM10", so what about JB ROMs that aren't made from CM10?
I'm fully aware that USB Tethering works on your build, if you had read any of my posts you'd realise that I already knew that. There was never a dispute as to whether USB Tethering was working. My problem is that @beanaroo claims that he has WiFi Tethering working with your ROM, and you seemed to acknowledge the fact that he had it working. So how can one user make something work that you (the builder of this ROM) claim doesn't work? Unless he is lying, then it must work?
So, other JB ROM alternatives to CM10 then?
EDIT : @warrior1208 I just noticed that your screenshot of your phone shows that Portable WiFi Hotspot is ticked. I know you can select it, go back in the menu and then go forwards again and it remains a solid tick, but why would you include that if you just admitted that it doesn't work? Strange.
Click to expand...
Click to collapse
I never mentioned that wifi hotspot works in my ROM...You may ask @beanaroo how he got that working...and yes I was trying in my screenshot to make hotspot stable...But it won't work in any of the Jelly Bean ROMs...So if you want it, you may revert back to a sense ROM as, the sense roms are based on stock rom and hence have everything working...Whereas, all the JB roms for our device have been ported taking cm 10 build 3 as base...I hope this clears up your doubt that YOU CANNOT USE WIFI HOTSPOT ON ANY JELLY BEAN ROM, REVERT BACK TO STOCK OR SENSE BASED ROMS FOR ACHIEVING THAT

You can Google up a 'how to build a ROM from source guide' there are plenty of good ones.
Sent from my HTC Desire C using XDA Premium 4 mobile app

Well I've started looking into some guides now, and once I've installed Ubuntu I'll see what I can do. I think I made some progress, I managed to get the phone to broadcast a signal, there was just a problem with authenticating when connecting. I think once I manage to work out what that problem was, I could make a bit of progress.
In the mean time, I've downloaded a few Sense ROMs which I'll be flashing on to the Desire C until I buy my Nexus 5 next week, which means I'll have the Desire C available for multiple flashes and messing around without having to put my phone out of action for a long time.
Anyway, thanks for the (limited) help. I realised about halfway through that no one really cares enough to try and make it work, I thought people would be up for a crack at this. The lack of enthusiasm was probably down to people not fully reading my posts and checking out all the info I provided, but that's fine. If I get anywhere, I'll let you know.

[Q&A] [ROM][4.4.4] Unofficial CM 11.0 for Samsung Galaxy Music (all variants)

Q&A for [ROM][4.4.4] Unofficial CM 11.0 for Samsung Galaxy Music (all variants)
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][4.4.4] Unofficial CM 11.0 for Samsung Galaxy Music (all variants). 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!

support
This excellent but lacks optimization, install CM version 10.1 and was doing an analysis with AnTuTu and pulled out a punctuation 10,580, but with CM 11 pulled a punctuation of something well below 5,382 but I understand it is the first RC and include leading what a great process of working 3 Rom at the same time. Ojuala early exit at RC2 Greetings :laugh:

Tried antutu and gave me similar to you. Then tried disabling ksm and gave me normal values
{
"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"
}
I think ksm give stabilty issues maybe should warn about it in the first porst. But still, thanks for the feedback. I will see if I can improve perfomance on next releases

Thank's to developer!
I would like to thank developer for the beautiful work that has been done to present us with this RC2 rom. The only thing that not works is dual sim and internet 3g. The rest is perfect ... My phone is s6012b, Brazil variant. Thank's! (Excuse me for my English translator).

3g
my phone is a 1SIM say without service. Make calls and receive messages but will not connect to 3g (data not read). How I can solve it. Willing to try rom leaving

stevens19 said:
my phone is a 1SIM say without service. Make calls and receive messages but will not connect to 3g (data not read). How I can solve it. Willing to try rom leaving
Click to expand...
Click to collapse
Hmm try disabling dual sim mode with the instructions from the first post

3g
Indeed, the 3G function only works with the dual sim option disabled. I disabled the dual sim entering the command in the terminal, and my 3g worked.

Wifi tether works? I need it
Sent from my GT-S6012B using XDA Free mobile app

doubt
Hi, Well I have a question according to art was watching mode is available in Kit Kat, and CyanogenMod 11 I wonder if is enabled on this rom, is a doubt
Another thing is that I would like him to focus more Gaming since eh I had several errors, slowness
Temple Run and install Angry Bird GO not start me something if it worked in 10.1, Sorry for the inconvenience. I wonder if Nameless Rom is based more on Thank games.

I installed the latest Rom [HIDEhttp://click.xda-developers.com/api/click?format=go&jsonp=vglnk_14210630763659&key=f0a7f91912ae2b52e0700f73990eb321&libId=2b2dd6c1-b685-4ddc-8d5e-8f0032906551&loc=http%3A%2F%2Fforum.xda-developers.com%2Fandroid%2Fdevelopment%2From-unoficcial-cm-11-0-samsung-galaxy-t2897839%2Fpage3&v=1&out=https%3A%2F%2Fwww.dropbox.com%2Fs%2Ff9a2bzag3cttot5%2Fcm-11-20141231-UNOFFICIAL-corsica.zip%3Fdl%3D0&ref=http%3A%2F%2Fforum.xda-developers.com%2Fandroid%2Fdevelopment%2From-unoficcial-cm-11-0-samsung-galaxy-t2897839&title=%5BROM%5D%5B4.4.4%5D%20Unofficial%20CM%2011.0%20for%20Samsung%20%E2%80%A6%20-%20Pg.%203%20%7C%20Android%20Development%20and%20Hacking%20%7C%20XDA%20Forums&txt=https%3A%2F%2Fwww.dropbox.com%2Fs%2Ff9a2bzag3c...rsica.zip%3Fdl%3D0][/HIDE], I found that the dual sim works (finally), but other things do not work, such as Wifi, phone calls (restarts to make any phone calls), network manual search, Bluetooth and Wifi theter.
There are plans to make the Rom Nameless? I really liked this version ...
I believe this is the way, thanks for your hard work!

rdandroid said:
Hi, Well I have a question according to art was watching mode is available in Kit Kat, and CyanogenMod 11 I wonder if is enabled on this rom, is a doubt
Another thing is that I would like him to focus more Gaming since eh I had several errors, slowness
Temple Run and install Angry Bird GO not start me something if it worked in 10.1, Sorry for the inconvenience. I wonder if Nameless Rom is based more on Thank games.
Click to expand...
Click to collapse
Yeah, kitkat has art but cyanogenmod doesn't support it so it may cause bugs. I already tried to enable it but it just caused a bootloop. And I don't think nameless will be better because some games closes inmediatly :-/ .The slowness problems could be hard to fix to me if you don't need dual sim, maybe you should stick with cm 10.1 and if I ever manage to fix bluetooth, I would release another version of CM 10.1
Pedro Gomes said:
I installed the latest Rom [HIDEhttp://click.xda-developers.com/api/click?format=go&jsonp=vglnk_14210630763659&key=f0a7f91912ae2b52e0700f73990eb321&libId=2b2dd6c1-b685-4ddc-8d5e-8f0032906551&loc=http%3A%2F%2Fforum.xda-developers.com%2Fandroid%2Fdevelopment%2From-unoficcial-cm-11-0-samsung-galaxy-t2897839%2Fpage3&v=1&out=https%3A%2F%2Fwww.dropbox.com%2Fs%2Ff9a2bzag3cttot5%2Fcm-11-20141231-UNOFFICIAL-corsica.zip%3Fdl%3D0&ref=http%3A%2F%2Fforum.xda-developers.com%2Fandroid%2Fdevelopment%2From-unoficcial-cm-11-0-samsung-galaxy-t2897839&title=%5BROM%5D%5B4.4.4%5D%20Unofficial%20CM%2011.0%20for%20Samsung%20%E2%80%A6%20-%20Pg.%203%20%7C%20Android%20Development%20and%20Hacking%20%7C%20XDA%20Forums&txt=https%3A%2F%2Fwww.dropbox.com%2Fs%2Ff9a2bzag3c...rsica.zip%3Fdl%3D0][/HIDE], I found that the dual sim works (finally), but other things do not work, such as Wifi, phone calls (restarts to make any phone calls), network manual search, Bluetooth and Wifi theter.
There are plans to make the Rom Nameless? I really liked this version ...
I believe this is the way, thanks for your hard work!
Click to expand...
Click to collapse
It was expectable that the test would have many bugs but thanks for letting me know that dual sim works there, now I have to discover what made dual sim to work there and apply it to our cm 11.
And namelessrom is based on cm 11 so is easy to apply the same changes so when I release a cm 11, I release a namelessrom too, however I think it's kinda buggy since it cause some games not to work and dual sim problem on namelese it's worse but yeah, there will be a next release too. Also I was trying to bring AOSB but faced some compilation problems

Thank you so much
Thank you, you've made a great work with this ROM. I only noticed a couple of things: Too much battery-draining when it works with Cellular Network and no Wi-Fi. Also, it has a bug on charging when phone is off, it tries to load the animation, then it shuts down, vibrate and restart again making impossible to charge when phone is off. Have you noticed that bug when charging?

chapmancarlos said:
Thank you, you've made a great work with this ROM. I only noticed a couple of things: Too much battery-draining when it works with Cellular Network and no Wi-Fi. Also, it has a bug on charging when phone is off, it tries to load the animation, then it shuts down, vibrate and restart again making impossible to charge when phone is off. Have you noticed that bug when charging?
Click to expand...
Click to collapse
hmm I can't do too much about the battery drain, maybe you should try changing governor or some other perfomance settings. And Wi-Fi not working? what version are you using? Also about the charging thing, I tought my charger had something because it happened me too well... I will have to figure out how to fix it
EDIT: hi I think I've figured out the dual sim thing, just to make sure, I need someone to test two testing versions from this folder. If in both version works dual sim, then the RC 3 will come soon with dual sim working :laugh:

I tested the second test version, and came to the following conclusions: Dual Sim: Works! Wifi: Works! Phone calls: Works!
3G: Works! Not tested: Wifi Thether, and Bluetooth...
My cell version: gt s6012b
Nice work! can be released RC3 ... Thanks...

Pedro Gomes said:
I tested the second test version, and came to the following conclusions: Dual Sim: Works! Wifi: Works! Phone calls: Works!
3G: Works! Not tested: Wifi Thether, and Bluetooth...
My cell version: gt s6012b
Nice work! can be released RC3 ... Thanks...
Click to expand...
Click to collapse
Thanks for the testing, released now RC 3, link is on the first post. Bluetooth isn't still fixed. Also RC 3 had some source updates, but those are changes that are hard to notice

Man, thanks very much for fix Wifi tether
Sent from my GT-S6012B using XDA Free mobile app

Alonso1398 said:
Thanks for the testing, released now RC 3, link is on the first post. Bluetooth isn't still fixed. Also RC 3 had some source updates, but those are changes that are hard to notice
Click to expand...
Click to collapse
Installed RC3 today, dual sim working great, wifi working out of the box, performance is great especially since there is no garbage like the kind included with the stock ROM, haven't tested thoroughly e.g., skyper/viber, but so far so good. no complaints whatsoever.
Thank you for doing a great job! :good:

Dual sim is working on latest RC3 build. Will check out wifi and games soon. BTW, my device is GT-S6012.

Alonso1398 said:
Thanks for the testing, released now RC 3, link is on the first post. Bluetooth isn't still fixed. Also RC 3 had some source updates, but those are changes that are hard to notice
Click to expand...
Click to collapse
Alonso, while dual SIM is working beautifully, the phone is not going to sleep. Wakelock Detector shows the RILJ service (which I believe is the GSM radio) is keeping the phone awake almost 100% of the time. The only thing installed on the phone is Gapps and Wakelock Detector. No other apps installed.

rahimali said:
Alonso, while dual SIM is working beautifully, the phone is not going to sleep. Wakelock Detector shows the RILJ service (which I believe is the GSM radio) is keeping the phone awake almost 100% of the time. The only thing installed on the phone is Gapps and Wakelock Detector. No other apps installed.
Click to expand...
Click to collapse
I searched a little about it on google and found it could be a Google Maps issue, I think disabling GPS can fix it or freezing Maps, however I'm no sure it that's your case

Confused with Lollipop builds! Please help me select..

Hi. Currently I am on jcsullins CM11-20141002 Kitkat build. I plan on upgrading to Lollipop but I am confused between the 3 builds (invisiblek-cm12, flintman-evervolv and milaq-cm12).
I frequently use the browser, YouTube and Skype (audio only) on my TP, amongst other apps. Could someone please help me select the right build? TIA.

Bump..

abhi.eternal said:
Hi. Currently I am on jcsullins CM11-20141002 Kitkat build. I plan on upgrading to Lollipop but I am confused between the 3 builds (invisiblek-cm12, flintman-evervolv and milaq-cm12).
I frequently use the browser, YouTube and Skype (audio only) on my TP, amongst other apps. Could someone please help me select the right build? TIA.
Click to expand...
Click to collapse
I am using a recently installed Evervolv build in which everything I have tried on mine seems to be working. I have used the browser a bit. Skype runs but I haven't used it on the TP yet. On my machine it seems fine but slower that the early Jan build I put in before.
I did a friends machine with the default partitions, he did not have the OEM USB and use a thinner aftermarket he had. It installed but there were various problems.
- no camera detected
- Google play does not offer updates to the core apps (as it did on mine) as it should
- Gmail won't launch at all
I don't know if its a partition issue or corruption from the cable used. It was a complete reset and wipe of the system with WebOS gone. I didn't have time to do it all again and will look at it another time I ma down.

@Tripple-c Thanks. I think I'll go with invisiblek's CM12 build as by his post only the camera is broken. I can live with that for now. I need the mic to work which is still not 100% in Evervolv going by flintman's post.

Tripple-c said:
I am using a recently installed Evervolv build in which everything I have tried on mine seems to be working. I have used the browser a bit. Skype runs but I haven't used it on the TP yet. On my machine it seems fine but slower that the early Jan build I put in before.
I did a friends machine with the default partitions, he did not have the OEM USB and use a thinner aftermarket he had. It installed but there were various problems.
- no camera detected
- Google play does not offer updates to the core apps (as it did on mine) as it should
- Gmail won't launch at all
I don't know if its a partition issue or corruption from the cable used. It was a complete reset and wipe of the system with WebOS gone. I didn't have time to do it all again and will look at it another time I ma down.
Click to expand...
Click to collapse
That issue you discribed above would only happen if you did a dirty install and didn't install gapps. The newer version backs up gapps so you only have to install. I recommend a clean install(factory reset and format system) to get the camera to detect the only way and then reinstall with gapps use the newest nightly.

abhi.eternal said:
@Tripple-c Thanks. I think I'll go with invisiblek's CM12 build as by his post only the camera is broken. I can live with that for now. I need the mic to work which is still not 100% in Evervolv going by flintman's post.
Click to expand...
Click to collapse
Is there a reason to update to Lollipop besides wanting to test it out? I think Lollipop itself has a lot of issues lingering that Google still needs to fix.

pekcle said:
Is there a reason to update to Lollipop besides wanting to test it out? I think Lollipop itself has a lot of issues lingering that Google still needs to fix.
Click to expand...
Click to collapse
Well, if you look at it that way.. There was no reason for me to upgrade to KitKat! I think I just like my devices to be updated

abhi.eternal said:
Well, if you look at it that way.. There was no reason for me to upgrade to KitKat! I think I just like my devices to be updated
Click to expand...
Click to collapse
It's all cool. There's no harm in that. But Android 4.1 to 4.4 was fairly mild and incremental. Lollipop was a hefty change in concept and usage. I tried it on my N7 2013, and it was just harder to use. Buttons were smaller and closer together, more taps and swipes just to do something, etc. It feels like they compromised ease of use just to adhere to the material design. Seriously made me consider going to an Apple product. No joke!

Bluetooth Metadata issues after Nougat Upgrade

Hi guys,
For those that have Bluetooth in your cars and use apps like SoundCloud, Pandora, etc., have you had issues with track information being displayed correctly?
Ever since I upgraded my Nexus 6 to nougat, the track information seems to be routed differently by the phones Bluetooth to my car's aftermarket Bluetooth receiver. Same has happened with my wife's Nexus 6 after she upgraded last week.
Both phones were working fine when on marshmallow using the same apps...Nothing else different other than upgrading to Nougat.
The only app that shows the metadata correctly on the main screen is the Play Music app. For all other 3rd part apps, I have to select "Channel List" and then I can see the track name. That was not the case with Marshmallow. All apps showed the metadata at the main screen where now it just displays some random numbers.
I know it's not the 3rd party music apps because they all display the metadata correctly when I have my work iPhone connected to my car.
Had the same problem on stock as well as Pure and Nitrogen. It's so frustrating because I don't have the slightest of clue on how I can go about figuring out what, if anything, has changed with the Bluetooth profile.
Any help or feedback would be greatly appreciated!

zelendel said:
Ok first you need to understand a few things.
1. Just because it works on an Iphone doesnt mean anything when talking about android apps. They are completely different OSs as well as completely different apps. Built completely separately with different SDK
2. Just because it worked on the last update doesnt mean it will work on this.
As google play music works, that says they changed something in the 7.x update that broke the other apps. They will need to be updated to work with the change in the code.
Click to expand...
Click to collapse
Appreciate the feedback, thanks!
Yup... Definitely understand that iOS and Android are 2 complete different bases...I tested with the iPhone to make sure that the aftermarket Bluetooth receiver in the car was not the problem.
I do believe it's something that Google has changed and I'm starting to realize that the only option I may have is to wait and see.
One point I want to add is that the Nougat update did not break anything when it comes to connecting to my wife's Acura with built in Bluetooth. The track info continues to work fine..
I was hoping someone with more in depth knowledge of the Android systems maybe be able to chime in on what could have changed...I know the 3rd party apps i use have gone through multiple updates since Nougat came out so if they were gonna update something due to compatibility with Nougat, it would've happened already.

aerohp said:
Hi guys,
For those that have Bluetooth in your cars and use apps like SoundCloud, Pandora, etc., have you had issues with track information being displayed correctly?
Ever since I upgraded my Nexus 6 to nougat, the track information seems to be routed differently by the phones Bluetooth to my car's aftermarket Bluetooth receiver. Same has happened with my wife's Nexus 6 after she upgraded last week.
Both phones were working fine when on marshmallow using the same apps...Nothing else different other than upgrading to Nougat.
The only app that shows the metadata correctly on the main screen is the Play Music app. For all other 3rd part apps, I have to select "Channel List" and then I can see the track name. That was not the case with Marshmallow. All apps showed the metadata at the main screen where now it just displays some random numbers.
I know it's not the 3rd party music apps because they all display the metadata correctly when I have my work iPhone connected to my car.
Had the same problem on stock as well as Pure and Nitrogen. It's so frustrating because I don't have the slightest of clue on how I can go about figuring out what, if anything, has changed with the Bluetooth profile.
Any help or feedback would be greatly appreciated!
Click to expand...
Click to collapse
Exactly same issue here in my '15 Civic Si with Shamu, Victara, and Titan, Bluetooth metadata breaks after the first pairing/connection. Once Bluetooth is interrupted, either by shutting off car or disconnecting Bluetooth, metadata never displays again until I either clean flash ROM anew or delete the bluedroid folder contents and do the whole unpair and re-pair both audio device. Quite a pain of a workaround, and it doesn't stick either, breaks as soon as Bluetooth is interrupted again.
Since you're on Shamu, I can recommend Cyanide ROM and SIX ROM, also Pure Nexus (not sure why yours didn't work with it), I've tested a few updates of each of the three ROMs, and Bluetooth metadata worked fine. Nitrogen never worked for me either. AICP, CM, LOS, Resurrection Remix, Dirty Unicorns, Emotion OS, all break on this feature for now. Not sure how Google's own OS is running in this department, but I've seen quite a number of complaints on this issue with the 5x, 6p, both pixels, but not so much with Shamu. I've not ran Google's nougat since developer preview 5 of 7.0, and back then it was working, can definitely confirm. I just hopped on the custom ROM train ever since DU released their flavor of Nougat, and just can't or want to go back to stock vendor OS. But do try out Cyanide and SIX ROMs, they both worked flawlessly on this device. Both are packed with extra goodies too. If battery is more important, go with SIX ROM, it's by far the most fine tuned nougat ROM I've tested. You won't find it on XDA, look for it on G+ under "Frankie T (R3DS)" community. It's posted with all the direct links for proper installation. Cyanide is another amazing ROM, also another fine tuned ROM, comes with built in black theme, and good battery life (if you set the governor to interactiveX), but really smooth experience overall. SIX, by the way, uses Pure Nexus as a base platform, so just a heads up there. Personally I've used the last two pure Nexus ROM updates and had zero issues with song data displaying via Bluetooth. Make sure you clean flash the ROM, wipe dalvik cache, cache, date, and system. Leave the internal storage unchecked. If the issue persists, then backup your internal storage files/folders to an external drive/device and format the whole internal storage of your Shamu, then throw everything back on and try clean flashing, pure Nexus should work thereafter. I've even restored it as a nandroid backup a few times and had no issues. SIX ROM is pretty much a refined Pure Nexus with extra features. Give these a shot, well worth it. Let me know how it goes for you.

Syndrome666 said:
Exactly same issue here in my '15 Civic Si with Shamu, Victara, and Titan, Bluetooth metadata breaks after the first pairing/connection. Once Bluetooth is interrupted, either by shutting off car or disconnecting Bluetooth, metadata never displays again until I either clean flash ROM anew or delete the bluedroid folder contents and do the whole unpair and re-pair both audio device. Quite a pain of a workaround, and it doesn't stick either, breaks as soon as Bluetooth is interrupted again.
Since you're on Shamu, I can recommend Cyanide ROM and SIX ROM, also Pure Nexus (not sure why yours didn't work with it), I've tested a few updates of each of the three ROMs, and Bluetooth metadata worked fine. Nitrogen never worked for me either. AICP, CM, LOS, Resurrection Remix, Dirty Unicorns, Emotion OS, all break on this feature for now. Not sure how Google's own OS is running in this department, but I've seen quite a number of complaints on this issue with the 5x, 6p, both pixels, but not so much with Shamu. I've not ran Google's nougat since developer preview 5 of 7.0, and back then it was working, can definitely confirm. I just hopped on the custom ROM train ever since DU released their flavor of Nougat, and just can't or want to go back to stock vendor OS. But do try out Cyanide and SIX ROMs, they both worked flawlessly on this device. Both are packed with extra goodies too. If battery is more important, go with SIX ROM, it's by far the most fine tuned nougat ROM I've tested. You won't find it on XDA, look for it on G+ under "Frankie T (R3DS)" community. It's posted with all the direct links for proper installation. Cyanide is another amazing ROM, also another fine tuned ROM, comes with built in black theme, and good battery life (if you set the governor to interactiveX), but really smooth experience overall. SIX, by the way, uses Pure Nexus as a base platform, so just a heads up there. Personally I've used the last two pure Nexus ROM updates and had zero issues with song data displaying via Bluetooth. Make sure you clean flash the ROM, wipe dalvik cache, cache, date, and system. Leave the internal storage unchecked. If the issue persists, then backup your internal storage files/folders to an external drive/device and format the whole internal storage of your Shamu, then throw everything back on and try clean flashing, pure Nexus should work thereafter. I've even restored it as a nandroid backup a few times and had no issues. SIX ROM is pretty much a refined Pure Nexus with extra features. Give these a shot, well worth it. Let me know how it goes for you.
Click to expand...
Click to collapse
Wow! Thank you for the detailed feedback! Does your Si have factory nav?
Anyway, I can't tell you how many things I've tried to get this thing figured out...I also have active communication with the manufacturer of the Bluetooth unit to see if we can troubleshoot the issue..So far nothing.
This is the first time I'm hearing of SIX ROM so I'm gonna do some reading and then flash it later on in the week. I'll reply back with updates.
Thanks again!

aerohp said:
Wow! Thank you for the detailed feedback! Does your Si have factory nav?
Anyway, I can't tell you how many things I've tried to get this thing figured out...I also have active communication with the manufacturer of the Bluetooth unit to see if we can troubleshoot the issue..So far nothing.
This is the first time I'm hearing of SIX ROM so I'm gonna do some reading and then flash it later on in the week. I'll reply back with updates.
Thanks again!
Click to expand...
Click to collapse
Happy to help. No my Si doesn't have the navigation option, I just use my Shamu for that. I've finally got the attention of AICP moderator and developer at AICP G+ community, so it's looking like the Bluetooth metadata issue is a CM/LOS issue so far, they're going to look into it. I captured a logcat and pictures which are posted there under bugs+logcat. It's under AICP G+ community if you want to look at it, posted under my main Google account as Andrey K, you can check it out here: https://plus.google.com/112643646080294190790/posts/4FRbAonGT55.
As for you never hearing about SIX ROM, that's because the dev doesn't participate on XDA forums. It's a really stable nougat ROM all around, and now supports phh's root, which if paired with Magisk app, allows to hide root access from apps like Android pay and Pokemon go.
The most a manufacturer would offer is to replace the device, possibly for a fee, that won't solve your problem. Most nougat ROMs are currently experiencing this bug. Cyanide, SIX, and Pure Nexus do not have this problem, at least not on Shamu.

anyone ever come across a fix for this?

nerdyone255 said:
anyone ever come across a fix for this?
Click to expand...
Click to collapse
Nah, still struggling with it...I keep hoping that a new Android update will fix it but so far no luck. It used to work fine for me in Lollipop but nothing since I've upgraded to Nougat. I'm on Nexus 6. Wife has a pixel XL and had the same issue when she was on Nougat so it's not the phone. She did get the Oreo update this week so I'll try again to see if it works. If not, then this must be a compatibility issue that the adapter manufacturer may need to look at...
The annoying thing is that the metadata transfer is fine when using my work iPhone. But I hate the iPhone/Apple so I only touch that thing when I absolutely have to (work calls, work emails, etc)

Any solutions so far?
My S2 worked perfect with the Civic (only it did not import the whole phonebook). With S8 I have the whole phonebook but no metadata on tracks (still plays and controls work)
---------- Post added at 01:31 AM ---------- Previous post was at 01:31 AM ----------
Any solutions so far?
My S2 worked perfect with the Civic (only it did not import the whole phonebook). With S8 I have the whole phonebook but no metadata on tracks (still plays and controls work)

Database Develop

welcome