Database Develop

[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] Losing GSM and WiFi signal

I was running CM 11 (maclaw's) then for about a month or so I was having incredible slowness on WiFi. After some hours on stand-by, I don't know what happens to my device, the WiFi get super slow. This is what a normal connection looks like:
{
"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"
}
and this is how a stricken one looks like: (note the ping value)
Then I jumped ship to CarbonROM (also maclaw's). The WiFi problem didn't go away but now I also have a GSM signal cut off problem!:
Like the WiFi problem, after some hours on stand-by the GSM signal cuts off, persists that way until I boot my device.
What could be causing my connection problems? Do you think it's the ROMs? I really need help. I can deal with the super slow WiFi issue but GSM cut off is really serious. (I was apparently called for an interview but couldn't receive the call!)

wtx1033 said:
I was running CM 11 (maclaw's) then for about a month or so I was having incredible slowness on WiFi. After some hours on stand-by, I don't know what happens to my device, the WiFi get super slow. This is what a normal connection looks like:
and this is how a stricken one looks like: (note the ping value)
Then I jumped ship to CarbonROM (also maclaw's). The WiFi problem didn't go away but now I also have a GSM signal cut off problem!:
Like the WiFi problem, after some hours on stand-by the GSM signal cuts off, persists that way until I boot my device.
What could be causing my connection problems? Do you think it's the ROMs? I really need help. I can deal with the super slow WiFi issue but GSM cut off is really serious. (I was apparently called for an interview but couldn't receive the call!)
Click to expand...
Click to collapse
Install some other rom (not novafusion's) to see if the problem persists (don't forget to make a Nandroid backup first and to change the f2fs to ext4) and update your baseband(from here: http://forum.xda-developers.com/showthread.php?t=2526831).
I use Android-Andi's SlimKat with none of your problems.

i am using f2fs. do you think the file system has something to do with it?!

wtx1033 said:
i am using f2fs. do you think the file system has something to do with it?!
Click to expand...
Click to collapse
I don't think so. I have none of your issues (with CM11, f2fs, system, data & cache). Anyway, you can always try & report your results

mauam said:
I don't think so. I have none of your issues (with CM11, f2fs, system, data & cache). Anyway, you can always try & report your results
Click to expand...
Click to collapse
like this?
this also doesn't work the dialogue comes up, but been waiting for 15 minutes and nothing happened. maybe sends in the background?!

wtx1033 said:
like this?
this also doesn't work the dialogue comes up, but been waiting for 15 minutes and nothing happened. maybe sends in the background?!
Click to expand...
Click to collapse
Everything work just fine for me. Do a clean flash, if doesn't work forget it or try with other rom

i did a clean install (while installing the latest carbonrom). same thing. bug report still doesn't work. never mind that. i still have problems with the wifi speed dropping significantly after some hours on standby. at least the GSM signal issue seems to be gone―which was the worst bug of all!

jstath1972 said:
Install some other rom (not novafusion's) to see if the problem persists (don't forget to make a Nandroid backup first and to change the f2fs to ext4) and update your baseband(from here: http://forum.xda-developers.com/showthread.php?t=2526831).
I use Android-Andi's SlimKat with none of your problems.
Click to expand...
Click to collapse
does the baseband actually effect WiFI? I thought it was for GSM comm.

wtx1033 said:
does the baseband actually effect WiFI? I thought it was for GSM comm.
Click to expand...
Click to collapse
Baseband doesn't effect WiFi (it only effect GSM and radio) but the kernel effect WiFi

As xXPR0T0TYPEXx says baseband doesn't affect WiFi but only the GSM and radio (problem to CarbonROM).

jstath1972 said:
As xXPR0T0TYPEXx says baseband doesn't affect WiFi but only the GSM and radio (problem to CarbonROM).
Click to expand...
Click to collapse
the GSM problem seems to be gone after I clean installed carbon 20141012 release. but the goddamn wifi issue persists.

wtx1033 said:
the GSM problem seems to be gone after I clean installed carbon 20141012 release. but the goddamn wifi issue persists.
Click to expand...
Click to collapse
Install some other rom (not novafusion's) to see if the problem persists like i said before.

jstath1972 said:
Install some other rom (not novafusion's) to see if the problem persists like i said before.
Click to expand...
Click to collapse
unfortunately it does. i tried slimkat. the wifi problem persists.
then i installed maclaw's AOSPA. surprise, surprise(!) the problem is still there.
it's really annoying because when the problem starts, the wifi indicator happily indicates that it is getting full signal. but i am not getting any notifications or i am getting them with a massive delay, because my bandwidth has dropped below 1 mbps with humongous ping value.
i also didn't tinker with my router for a year. it runs the same firmware and same settings.

according here, -i guess- it seems to be a bug with android 4.4.4 :crying:

okay, i tried keeping gps on to see if there was any change...and there indeed was! this time the wifi speed didn't drop (but there was a cut off!):
so i am guessing it's a nasty bug that involves gps: in the absence of gps, wifi speed somehow decides to drop to creeping levels.
then i either have to keep gps on and sacrifice battery life or keep it off and manually on/off wifi every couple of hours :S

[Q&A] [ROM][UNOFFICIAL][i9305] CyanogenMod 12 UNOFFICIAL BUILDS FOR I9305

Q&A for [ROM][UNOFFICIAL][i9305] CyanogenMod 12 UNOFFICIAL BUILDS FOR I9305
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][UNOFFICIAL][i9305] CyanogenMod 12 UNOFFICIAL BUILDS FOR I9305. 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!

achrafi9305 said:
Very Very sorry guys for waiting ! but a good build us under developement now !
but my pc is having strange problem (this rom is unlucky) ! gonna try to fix pc and finish the build and upload!
Thanks
Click to expand...
Click to collapse
Hello, the next build will be experimental, alpha nightly or stable version ?
When will be upload ? I'm waiting for the rom

RayaneGti said:
Hello, the next build will be experimental, alpha nightly or stable version ?
When will be upload ? I'm waiting for the rom
Click to expand...
Click to collapse
Hi ! I cant answer your question because the next build isstill under development and needs to be tested to see how stable it is! and sorry for waiting ! I am still a new (developer) in addition to having technical problems!

No soucy
achrafi9305 said:
Hi ! I cant answer your question because the next build isstill under development and needs to be tested to see how stable it is! and sorry for waiting ! I am still a new (developer) in addition to having technical problems!
Click to expand...
Click to collapse
No soucy, congrulations for your project, i'm waiting for and i'm with you !!!

Test
+
1.Booting
2.Works
3.Looks like there is no glitches in Google Chrome
4.Stable 3G
-
1.Battery discharges even it is plugged to charger
2.No 4g( Maybe it is my provider problem
3.Signal is unstable

Hello
I'm currently testing this CM12 build of yours, and it seems to work great in general - but i do have some troubles with my data connection.
I can see that i'm not the only one, and for me it's a crucial that I have my data connection available when I'm not able to connect to a wi-fi.
I use LTE and sometimes it just disappears, and show an ! in the signal-icon - and then sometimes it reappears (as of right now, it just reappeared and started working, for no apparent reason)
I'm not sure what causes this, but i will look into possible reasons in the next coouple of days.
keep up the good work!
chrisroed

xposed
Could you test Xposed also on this rom?

tried installing the latest build (20150213) from winxusers website - now my unit wont go past the startup logo... did not try to wipe first though, wil ltry that now.

3g ist not working
Hallo thanks for this beatiful ROM.
3G is not working

3g no work the last update
Even without works 3g not understand why they say this repaired -.-

hello again
I did a full wipe and installed the 20150217 update. my device booted from that one, and is working somewhat ok. data connection (LTE) is still very dodgy, and will sometimes stop working without warning. I cannot replicate the error on purpose, and thus, I cannot tell you what the error is, exactly.
It might be when i move around and change connection to other antennas in my area - but I'm not certain.

3g is not working on the i9305n and someone also mentioned it not working in the UK

agni kernel
AGNI PureCM kernel is not working in this rom. . :/

Hello again
I've been using the latest build for some days now, seem to work quite good, but still have some issues.
Data connection is still not working 100%, I still lose the connection from time to time, with no apparent reason behind it. although I usually use LTE, I will try to test if manually setting it to 3G will help.
Video playback is awful. Colors are all wrong and the playback is laggy and slow to load. Sound seems ok though.
gps seems to work fine, it accurately found my position within a few seconds.
Nothing more from me, this time.
Keep up the good work!
chrisroed

For me, not working 3g with anyone config

3G does not work and some please tell that annoying andreazimba idiot to stop telling people that it does. There are people in various European countries stating the same thing. 3G does not function!

ash29k said:
3G does not work and some please tell that annoying andreazimba idiot to stop telling people that it does. There are people in various European countries stating the same thing. 3G does not function!
Click to expand...
Click to collapse
I agree ! We just loosing our time.

kanarex1 said:
I agree ! We just loosing our time.
Click to expand...
Click to collapse
Agreed, this annoying little 15yr old is slowing down the good work being done by devs by prompting them to avoid the main issue with this rom which is the non functional 3G.

ash29k said:
Agreed, this annoying little 15yr old is slowing down the good work being done by devs by prompting them to avoid the main issue with this rom which is the non functional 3G.
Click to expand...
Click to collapse
im sorry unfortunatly i cant seem to fix the 3g issue but there is some people saing if you set it to 3g only then it seems to work,, i dont know why some people have working 3g like me and others dont. but unfortuneatly theres no fix just yet

For me, absolutely no problem for 3G even if I stay on LTE prefered.

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

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.