[ROM+Kernel][CM-11.0][4.4.4][OS2SD/internal][f2fs]bigsuperROM-thunderc-4.4.4

[bigsupersquid]

Hey guys, first of all let me say I'm absolutely amazed to still find support for this device. My GS3 took a crap on me and I had to pull this sucker out as a backup, big props to everyone involved. Now onto my issue..

I'm trying to get the internal version to work since the os2sd version seems a little laggy, even with crossbreeder (I have to constantly pause while typing on the phone to let it catch up) Unsure if running the internal version would actually fix it but I thought I'd give it a shot. I'm constantly getting the Setup Wizard has stopped error, I tried a clean flash and booting without flashing skinny gapps and that didn't work. Any advice or suggestions would be much appreciated.

didn't realize setup wizrd was in there. internal should fix your speed problem, sd card is probably too slow.
mount /system in twrp-internal mode, open advanced>file manager, go to /system/app (or maybe /system/priv-app) and delete setupwizard.apk (onetimeinitializer too if it's in there.)
then reboot.

 

[photonik]

didn't realize setup wizrd was in there. internal should fix your speed problem, sd card is probably too slow.
mount /system in twrp-internal mode, open advanced>file manager, go to /system/app (or maybe /system/priv-app) and delete setupwizard.apk (onetimeinitializer too if it's in there.)
then reboot.

I'm actually not finding either of those apk's which makes this a bit strange, right? I'm using cm-11-20141014-EXPERIMENTAL-internal_bigsuperROM-thunderc with Skinny_4.4_Gapps_new_internal. Have tried completely wiping the device a few times and starting from scratch with no luck. Am I potentially missing an abnormal step if coming from the os2sd build?

 

[kameron c]

I flashed the os2sd version on my Virgin Mobile Optimus V this past weekend. Now, I can run many of the most basic apps that I couldn't run with the Virgin Mobile stock ROM. Thanks, bigsupersquid!

I have a few problems with the new ROM, and I am hoping that someone here can help me debug them:
1) Camera cannot focus. I can take photos with the stock camera app but the photos are fuzzy. With the Barcode Scanner app by ZXing, the screen freezes after about 10 seconds unless I uncheck "autofocus" in the settings. HSBC app also cannot take photos. The shutter button on screen doesn't work, and the screen freezes after about 10 seconds. When the screen freezes due to camera problem, I can get always get out of the app by pressing the physical home button. I can even get back to the app by holding the home button for recent apps. Then, I have about 10 seconds before the screen freezes again. The point is, neither the phone nor the app freezes. It is just the camera screen of the apps.
2) Video recording does not work. With the stock camera app I can take photos and panorama but when I switch to video mode, it crashes and says "Unfortunately, Camera has stopped."
3) Sometimes, the phone struggles to wake up after the screen is turned off. When I press the power button or any of the four physical buttons, it takes anywhere from 1 to 30 seconds for the screen to turn on.
4) Mobile data gets disconnected when I don't use the phone for a few hours. Mobile data comes back after I place a call. For now, the workaround is to call my voicemail and hang up.
5) The clock can lead or lag so the alarm is not very reliable. This may be related to problem 4.

I backed up my apps using Titanium Backup before I flashed the new ROM. I also made a nandroid backup using TWRP.
Following the instruction on the 3rd post, I flashed the following using TWRP2.7.1.0_multi_v4:
cm-11-20141030-EXPERIMENTAL-ext4_os2sd_bigsuperROM-thunderc.zip
pa_gapps-modular-pico-4.4.4-20150117-signed.zip
pa_facilitator-pico-4.4.4-20141114-signed.zip

I have some programming experience but none with Android. Please let me know what debug info I can provide to help solve these problems.

Thanks again!

 

[kameron c]

Oh, there's one more problem I forgot to mention. It's more of a nuisance but maybe it's a symptom of a more serious problem.

6) The phone turns itself on when I plug the charger into a turned-off phone. I get the LG screen followed by the Cyanogenmod spin like a normal boot. I don't get the battery charging screen I used to get with the Virgin Mobile stock ROM.

 

[syguyice]

Hi Kameron, most of your issues are covered in earlier posts. I'll try to help before bigsupersquid returns:

1) Camera has a known issue with focus, where it crashes/freezes. Bigsupersquid disabled autofocus as a workaround so photos would still work with infinite distance.

2) I'm running 9/6 build and my video camera works, however I've heard reports the video camera has been broken since in a later build. I am staying with 9/6 for now as I'd like a working camera.

3) When this happens to me, I press and hold the back button for a few seconds. This often dismisses/kills whatever that held the screen and wakes to the lock screen. You may need to turn on the kill option in settings first for this to work.

4) I don't use mobiledata, although I believe this could be a power saving feature. You may be able to use a Tasker or Llama automation script to auto-cycle the mobiledata connection. (which is what I do for my Wifi connection)

5) I've heard clock lag is bad with cell connection. I'm on wifi and have not seen this issue. Having an automation script to wake up the phone every half hour or so and to keep mobile connected may help.

6) Screen-on charging is a side-effect of this particular ROM, and according to bigsupersquid this behavior would stay for the foreseeable future.

Hope this helps.

 

[bigsupersquid]

The only issue not covered there,
the setupwizard.
the internal boot.img isn't flashing and needs extracted to /sdcard then in twrp
Advanced - terminal command
navigate to sdcard and select
Then type
flash_image boot boot.img

Bad updater-script. Would fix and reupload if I had working pc.

 

[dradzanowski]

Alright, got to play with the audio policy file in etc. it worked to change the default to "audio_out_earpiece" then reboot. I'm going to further experiment, and see if I can get a wired headset to work as well. (headset itself is wrong connection-3conductor, though if you have a 4 conductor headset, should work).

UPDATE:
Well, played with the GPS, it seems like between the Google Setting and the normal phone settings both are "on" and if you turn one of them on, it switches the other on as well. So, Gsetting and phone setting agree, it's on. It's just none of my apps say that the GPS is on "go to settings to turn them on"-I go to setting, it says it's on. Though the "assisted" gps working through wifi works, doesn't help a lot for excercise running or driving though. Updated the GPs.config file, using various files, some from online general north america, southwest America (Arizona included), and the config file listed previously. Nothing will really take. Seems like the apps aren't correctly communicating with the GPS. If anyone has some direction or thoughts, I'll play in that direction.

 

[skinbark]

I just came back to kit kat after running CAI ICS for a while, and I'm very happy that I did! Many thanks squiddie for the awesome work you've done with this rom. The 10-25 build is running smoothly for me. It lagged a bit until I switched from a class 10 sdcard to a class 4, that made a big difference. I'm getting FCs when I select Settings>Storage, and I haven't been able to get tethering to work, but other than that everything seems fine. I'm just amazed that this old phone could still be running so well after all these years. It's truly better then ever thanks to you and everyone else who's contributed (and participated).

 

[skinbark]

Also, I never used to be able to get videos to play worth a **** on this phone. I installed MX Player with the armv6 vfp codec and videos are working great!

 

[rockinmusicgv]

First, let me say THANKS to everyone who has worked so hard on continuing to update a device that until yesterday I thought was hopelessly out of date.

I'm in a situation where my Optinmus V might become my daily driver. Is this CM11 ready for life in the primetime? I saw in the thread there are a few things that don't quite work (like the camera). I'm sure I missed a few things that might have been fixed (mms?). Is the phone actually responsive using KitKat?

 

[dradzanowski]

This ROM I would say is a comfortable daily driver. I think of it like a car analogy. This ROM takes a Ford Pinto (The Opti s/v) and makes it feel like a 08 Fusion. It's still not a Mustang GT, but it's pretty nice.
Or if you don't like domestic, it takes a 89 Toyota Camry and makes it feel like a 14 Corolla. Still not a Lexus, but a lot better.

There is a "native copy" Camera app available in the Play store, that works just fine (I've used it). I don't think the video camera works though, haven't tried lately. MMS hasn't worked really ever for me. Across a lot of ROMs.

Aside from that, this ROM is sweet. The 10-25 build runs really well, you have to get OS2SD, you have to get a good SD card. But if you do, the setup makes me feel like I'm on almost equal footing with the new Galaxy S4. Aside from the physical limits (CPU being single), this ROM is great.

 

[skinbark]

bigsupersquid, do you know what cluster size twrp is using when it partitions sd cards?

 

[bigsupersquid]

nope , all i got is
"parted -s " + Device + " mklabel msdos"
so i guess whatever parted uses by default.

 

[kameron c]

I tried to have Llama cycle the mobile data connection periodically per syguyice's suggestion but it did not work reliably because Llama relies on the clock. Sometimes, the clock lags a lot when the screen is off so Llama doesn't think that the next schedule cycle time has been reached. When I turn on the screen, the three clocks (lock screen, status bar top right, drawer bar top left) jump to three new times so Llama never triggers.

Installing Voice Search from Google Play allows Waze's voice command to work but the mic icon from the Android AOSP keyboard does not launch the Google voice input. I am using paid Swype's Dragon Dictation for voice input at the moment.

Video related:
MX Player with the armv6 vfp codec also work well on my phone. Video camera is still broken. I tried Google Camera app from Google Play a couple weeks ago. It was totally broken. I had to do a nandroid restore to get back the Gapps camera which at least took still photos.

Chromecast related:
Working: casting from YouTube app, changing backdrop from Chromecast app
Not working: registering new Chromecast device (fails but no crash), cast screen from the phone (crash)

Recently, I get two to three "Unfortunately, Google Play services has stopped" pop-up messages when I boot up the phone and a random one every now and then when I am not running any app actively. I am not sure what has changed to cause this problem, and I am not aware of any app not working because of this. Is there a way to find out what is causing these pop-up messages?

What are the main differences between the 20141025 build and the 20141030 build?

 

[dradzanowski]

Hey Kameron,
I test like, 15 different camera apps.
This is the only one that worked.
https://forums.androidcentral.com/e...=photo.android.hd.camera&hl=en&token=LLEKrJ4Z
Got to take a panoramic shot with it. Pretty fun.

I have the free Touchpal keyboard, and it does connect to the voice correctly, but the voice app is broken. I want to get in sometime and see about other apks for the voice input.

I've gotten the play services message as well. I uninstalled GPservices, and I'm going to try a different apk for it. I found this one:
com.google.android.gms-6.7.76_(1745988-012)-6776012-minAPI9
It's coded correct for my phone (012), I did a little research on it. It's more updated, I think. I'd be interested as well in figuring out why Google play services isn't working.

BIG UPDATE ON GPS:
This is bizzaro. When I was fiddling with the keyboard calling for the voice input app, a box popped up and said "In a previous version of Android, you disabled app permission to use GPS. Would you like to enable it now?" Stunning. It apparently remembered at some point denying permission to apps. That may have been what broke my GPS. Going to test once I get Play services back up.

 

[bigsupersquid]

Re: [ROM+Kernel][CM-11.0][4.4.2]OV-KitKat (JBC based)

oh, looky there. I fried my Evo with dd.
gotta unsolder the internal sd or something and get mmcblk0p1 back together (/boot is at mmcblk0p21) dang terminal.

so it's back to the Optimus for me again. will encourage me to sort out glitches.

those google persistent permissions are beastly sometimes. and xda usually has the latest/greatest play services, just pull the 160dpi armeabi version (or generic armeabi if they're too fresh for that -012, but never ever armeabi-v7a.)
//those gservices fcd at me too. multiple reboots seem to have fixed it.

 

[omgitsMATT]

Sorry about your Evo.

I left my phone in my pocket while working and a brick crushed the glass and lcd making it to expensive for me to fix so I'm back too

 

[bigsupersquid]

It's always the expensive hardware, right?

my bad lexar 16Gb card runs dog-nasty on any os2sd.
my nice sandisk evo 64Gb media card runs great on the same backups from either my 10-25 or 9-06.
View attachment 01cache.zip
Note: Shinkenred verified with terminal that the 10-25 build doesn't mount /cache which causes some of the fc's.
unpack attached zip (not flashable,) put content in /etc/init.d and chmod 755 (rwxr-xr-x) and it'll be ok on reboot and after.

 

[syguyice]

Hi Kameron,

I also had a lot of popups from googleplay stopping for about 3 months, and had put up with it until 2 weeks ago, when I inadvertently uninstalled all updates to googleplay store & googleplay services (from Settings -> Apps). Afterwards, not only did the popups go away, but I found that the phone sped up a bit as I can have more than 140mb free memory now, when before I never got above 70mb (usually hovering around 28mb free). The factory googleplay store still works, however each time I run it, the auto-self-update would reinstall the bloated latest version again, causing all the popups all over (possibly due to low free mem). So my workaround is to get everything I want from google store, uninstall updates, then disable googleplay store from Settings -> Apps. Since I don't update my apps nor browse around the store often, this leaves my phone speedy in between app installs. If I ever have to launch play store again, then I would re-enable store, and repeat the same procedure after I'm done installing.

Sorry about the Llama issues; it's my fault for not realizing that could be a problem, without experiencing clock lag myself. I haven't had to use this as a result, but within Llama settings there's a Cell Polling Mode, which you can enable to have Llama actively wake the phone up to check time and cell towers, instead of passively waiting for timer to hit (which could be never when phone goes into deep sleep, until you wake it). It will use a bit more battery power like it says, although perhaps the tradeoff would be worth it for you to consider the phone usable. You can control the exact behavior of Cell Polling under Cell polling settings, for which I recommend you to have it wake and turn on screen every minute for 1 second. If that works for a day, then try again after scaling back the frequency and disabling screen-on, until you find an acceptable level of battery consumption that still works.

Hope this helps.

 

[bigsupersquid]

I've been experimenting with clock lag today.
was pretty bad until I tried a new gimmick.
since network time protocol seems to have something to do with the problem...

after commenting out all the beginning NTP lines in the US gps.conf, I have gone since about noon (8.5 hours //edit over 19 //23 Hours, Lockscreen Clock Wrong Once But Everything Corrected When UnlockEd, ) without a single time glitch. before editing that file the statusbar clock and others were nearly constantly out of sync.
testers? see attachment. unzip, put file in /etc, chmod 644 (rw-r--r--) and reboot.
View attachment gps.conf.zip