Related
Can't seem to get GPS to function with LTBv2.3 & MR2.5 radio.
I've followed the directions from the following thread to a tee and get the same results.
http://forum.xda-developers.com/showpost.php?p=9576852&postcount=108
... yes I've verified the removal of the entry mentioned in the db.
Haven't been able to find much else to try out.
Try this:
1) Download GPS Status from the market
2) Run GPS Status hit Menu > Tools > Manage A-GPS State > Download
3) Wait for it to download and for the GPS Status to get a lock (The bottom portion of the screen will fill up with tons of information)
4) Go to Manage Applications > Maps > Clear Data
5) Go to Maps again and see if you get a better lock.
For best results do all of these steps outside.
Used to fix issues back when everyone was on Froyo
Folks were using the same fix as cm7, create a nandroid backup, flash sense rom of your choice, get GPS lock, boot into recovery, restrore previous nandroid backup.
Thunderbolt CM7 Kang Bang
Tried GPS Status. The GPS receiver is apparently working, however maps is not able to find my location. So I've at least established that my GPS _is_ working; maps is just unable to use it for whatever reason.
I've tried a fresh wipe as suggested with the same results.
Was incorrect, there is no GPS lock at all. I've installed GPSFix and GPS Essentials and both indicate the device is not finding any satellites.
I know everything works with Froyo, but I'm enjoying Gingerbread and would love to be able to stay with it. Any other ideas floating out there?
I Fixed it. Installed OMFGB & used GPSFix and it was able to get a lock. I installed LTB over without wiping and everything functioned correctly.
With any of the LTB installs I tried using MR2 and MR2.5 I was unable to get a lock using the GPSFix tool. Probably just an odd quirk. Either way, GPSFix seemed to do the best job out of all the available options I tried for Gingerbread.
CyanogenMod is a free, community built distribution of Android 2.3.7 (Gingerbread) which greatly extends the capabilities of your phone.
Code:
** These CyanogenMod builds are highly experimental and unsupported.
**
** Please refrain from submitting bug reports for any issues
** you may encounter while running one of these builds.
**
** Submitting bug reports on nightly builds is the leading
** cause of male impotence.
Warning : Not for new users, flash this build only if you know what you are doing !!!
What is CyanogenMod (in less terse form - by mad-murdock)?
since i am a bit idle right now, i try to answer this.
cyanogenmod is the only open source rom, that runs on 40+ different devices. we got around 45 devs (people who really write code and tweak things to make it work better - in contrast to cooks, who only use winzip to exchange this vs. that binary thingie) constantly making cyanogenmod better.
as background, you might wanna know, that google usually releases the sourcecode to their products (where honeycomb is the first exception, but thats another matter, ICS will be open source again). but when google releases their source code, you cannot compile it for ANY phone and it runs on it. thats the first part, we jump it - make it compatible with all the phones we support.
once it basicly runs, its time for what we call "cm extras" - we modify a lot on the gui and the system to make it run better. some stuff you as a user will never see involving tweaking libs and kernels, and some stuff you as a user will see a lot, like including theme manager, dsp manager, cm settings (cm settings are about as huge as the normal settings are). those settings range from simple "dont display clock in status bar" to complex profiles (as known from old nokia phones) or remapping of some keys (long press home, remapp search button behavior)
its way to much to list it all here, but i can assure you, cm is fast, usually stable on most devices and VERY VERY customizable - both in grafical ways as also in behavior way.
Click to expand...
Click to collapse
Please visit the CyanogenMod Wiki for step-by-step installation walkthroughs and tons of other useful information.
Installation instructions:
in following post - will move moved to Q&A Forum when that is up.
teamhacksung:
atin - http://gplus.to/atinm
codeworkx - http://gplus.to/codeworkx
coolya - http://gplus.to/coolya
unhelpful - http://twitter.com/unhelpfulone
Changelog:
Generic Changelog CMSRC Twitter
Device specific Changelog by igor.tonky
Modems:
TBD
Thank you to EVERYONE involved in helping with testing, coding, debugging and documenting! Enjoy!
CyanogenMod 7 (w/ Gingerbread 2.3.7) for AT&T Galaxy SII
The only rule of CyanogenMod: you don't ask for ETAs. You install, your warranty is void.
Warning : Not for new users, flash this build only if you know what you are doing !!!
FAQ (Please Read!!)
What is CyanogenMod (by mad-murdock)?
CyanogenMod is the only open source rom, that runs on 40+ different devices. we got around 45 devs (people who really write code and tweak things to make it work better - in contrast to cooks, who only use winzip to exchange this vs. that binary thingie) constantly making cyanogenmod better.
as background, you might wanna know, that google usually releases the sourcecode to their products (where honeycomb is the first exception, but thats another matter, ICS will be open source again). but when google releases their source code, you cannot compile it for ANY phone and it runs on it. thats the first part, we jump it - make it compatible with all the phones we support.
once it basicly runs, its time for what we call "cm extras" - we modify a lot on the gui and the system to make it run better. some stuff you as a user will never see involving tweaking libs and kernels, and some stuff you as a user will see a lot, like including theme manager, dsp manager, cm settings (cm settings are about as huge as the normal settings are). those settings range from simple "dont display clock in status bar" to complex profiles (as known from old nokia phones) or remapping of some keys (long press home, remapp search button behavior)
its way to much to list it all here, but i can assure you, cm is fast, usually stable on most devices and VERY VERY customizable - both in grafical ways as also in behavior way.
Click to expand...
Click to collapse
Q: How do I install this?
A:
Latest version:
Temporarily while buildbot is down:
You can get it from ROM Manager (look for teamhacksung builds for Galaxy SII AT&T) or
http://www.multiupload.com/RT29P7AOFS (md5: c8115d0a01d0a47b286ff5c9cc504175)
Previous kang: http://www.multiupload.com/A30J9DZN37 (md5: a23d1b99ff73da31e5d0421ec18e15e3)
Normally: http://download.cyanogenmod.com/?type=nightly&device=galaxys2att
Check the md5sum if you want to be sure that the download worked (different OSes have different programs that do md5, on ubuntu it is md5sum that you run against the zip you download and compare to the md5sum number shown on the download website). ROMManager does this automatically for ROMs you download via ROMManager.
- First time flashing CM 7 to your Galaxy S2 (or coming from another ROM)?
Note: You may need to flash twice back to back if the first one goes by too quickly - the actual flash takes a little time and sometimes the first flash doesn't "stick".
Install via ClockworkMod recovery (do not use ROMManager for initial install):
Make sure you're running a rooted device.
Root your device and install ClockworkMod Recovery (http://forum.xda-developers.com/showthread.php?t=1118693)
Do a Nandroid backup!
WIPE (wipe data/factory reset + wipe cache partition) - do it for real.
Install the ROM from internal sdcard using ClockworkMod Recovery.
Do not reboot! We mean it - do nothing except choose zip and continue next step (if you come back to us with permission issues in install, we will know you did not read the directions and will call you an idiot). If it just plain hangs, reboot directly back into ClockworkMod recovery and continue at the next step.
Install the ROM from internal sdcard using ClockworkMod Recovery, again (due to a bug in the install).
Reboot
Install the Google Addon through ROMManager which is easiest, but you can
download the gapps.zip and install via ClockworkMod recovery instead.
- Upgrading from earlier CM7?
ROM Manager method:
Install ROMManager Premium.
Flash ClockworkMod Recovery. Pick Samsung AT&T Galaxy S2.
Choose Download ROMs.
Pick the CyanogenMod Nightlies.
Check the Google Apps addon.
Check Backup current ROM!
Check wipe cache, dalvik cache.
Let ROMManager finish the installation.
Clockwork Mod method:
Download and push the ROM zip file to the sdcard.
Reboot into recovery.
Do a Nandroid Backup!
Install the ROM zip from sdcard (your Google apps will be backed up automatically)
There are no Google Apps bundled with CM ROMs, because Google asked Cyanogen to remove copyrighted apps. After flashing the rom, don't forget to flash Google Addon package if you want it. ROM Manager will allow you to flash it if you just go into it and after flashing the ClockworkMod recovery for AT&T Samsung Galaxy S2, choose Download ROMs, and pick Google Apps. Or download and push the gapps zip for CM7 from http://wiki.cyanogenmod.com/index.php?title=Latest_Version#Google_Apps to the sdcard and flash it via ClockworkMod recovery.
- Going to another ROM from CM7?
You can go back and forth freely between CM7 and other ROMs via ClockworkMod recovery as the file systems are the same and nandroid backup/restore works to go between ROMs.
Q: What are the known issues?
A: Issues that I can remember:
- Video playback - some formats are not recognized, use an alternative app for video playback
- Camera - some video and still modes don't work
- TVout, MHL
- Dock
Q: Where do I see the Changelogs?
A: http://cm-nightlies.appspot.com/?device=galaxys2att - this shows all the changes that have gone into a nightly, including anything that is device specific to Galaxy S2 and anything that has gone into common code that is also included on Galaxy S2. If you see another device sometimes in the Galaxy S2 changelog, it is because the changes were done to common code and the repository is also included on the Galaxy S2.
Q: Can I flash over a previous version of CM7?
A: If updating from an already CM7 running SGSII phone, just flash the latest update zip file as it contains all the fixes from previous updates.
Q: I just installed and I don't see the Marketplace, cannot see GMail, cannot sync Contacts.
Q: I just installed and I don't see any Google Apps.
A: You need to install the Google apps. They are available in ROMManager. ROMManager also asks you if you want to install the Google Apps addon when you install via ROMManager.
Q: Can I run Samsung Applications like Kies, Phone, Email, AllShare?
A: No. Any applications that use special calls into the Samsung TouchWiz framework will not work.
Q: I cannot find my media files that are on my external sd card
A: Look under /mnt/emmc as that is where CM7 mounts the external sd card as opposed to /mnt/sdcard/external_sd that Samsung ROMs use.
Q: My phone is running too hot, my phone is not going into deep sleep
A: Try to isolate which application is using too much CPU. The first thing to try is to remove your media (video, music etc) files. Files recorded using Samsung camera, but other files as well, can frequently cause the stock Media Scanner to fail and go into an infinite loop. Then try to isolate which files are causing problems, and report them to us. If it isn't media, then it is some other application. Try to remove that application if it is a third-party application (and report a bug to them).
Q: I restored from Titanium Backup but my applications are not working
A: Do not restore system data, only restore application+user data. CM7 uses new system data and if you restore on top of it, things will not work.
Q: Your notification toggles are different than mine, how can I change them?
A: Go into Settings, CyanogenMod Settings, Interface, Notification power widget, Widget buttons
Q: I really miss the accurate battery mods, can I flash these?
A: No, but you can go into Settings, CyanogenMod Settings, Interface, Status bar tweaks, "Battery percentage"
Q: Where can I get themes for this?
A: A quick search for "theme engine" on the market will produce a number of results, but there are some in the general Android Themes section
Q: My Status bar Sound widget does not toggle through the options.
A: Settings > CyanogenMod Settings > Interface > Notification Power Widgets > Widget Buttons > Sound Modes and set the modes you want it to toggle through.
Q: Can I use the video player/music player/contacts/phone/launcher from a Samsung ROM?
A: No, anything hooking into Samsung's framework will not work on this ROM, there are plenty of alternatives in the market.
Q: Where can I get the Nexus S drivers?
A: Download and install the Android SDK here then download "Google USB Driver package, revision 4"
Once downloaded, right click on "Computer", "Manage", "Device Manager", "Nexus S", "Update Driver Software", and point it to wherever you installed the SDK
Q: How do I go back to a Samsung stock ROM?
A: Just use ClockworkMod or ROM Manager backup/restore facility to go back and forth between stock (or any other ROM) and CM7.
Q: Can I use ROM Manager to install or back up this ROM?
A: Yes.
Q: Why do I not see the nightlies in ROM Manager?
A: Nightly builds are only visible in the premium version of ROM Manager. Nightly builds should up in ROM Manager when the CyanogenMod buildbot builds the nightly successfully. Every new device needs to also get added to the ROM Manager manifest before it is available. But, the same files are also available at http://download.cyanogenmod.com when the buildbot successfully builds a nightly.
Q: Why can't I play .avi or .mkv files? They worked fine with Samsung's ROM.
A: Due to codec licensing issues, this can't be provided out of the box. Several apps from the marketplace should be able to replicate this feature (such as RockPlayer). We will also try to put these enhancements into CM7 ourselves.
Q: I encountered a bug, how do I find out if it's known and where can I report it?
A: Try to get the logcat output and last_kmsg to your report by:
Code:
desktop$ adb logcat > logcat.txt
desktop$ adb shell
# cat /proc/last_kmsg > /sdcard/last_kmsg (only if you had crash/reboot)
# dmesg > /sdcard/dmesg.txt
# exit
desktop$ adb pull /sdcard/last_kmsg .
desktop$ adb pull /sdcard/dmesg.txt .
Attach the logcat.txt and last_kmsg files to the bug report. Of course, you need to have the android SDK installed to do this.
And one more.
Running very smooth on the sgs2 keep up the great work.
AT&T SGS2 running CM7.
Codeworkx just put up a test build (http://codeworkx.de/download/galaxys2att/cm7-galaxys2att-KANG.zip) - it should work, but right now none of us has an AT&T SGS2, so need someone else to try it. Install it via ClockworkMod recovery as explained in the second post.
Let us know if it basically works.
Yea I've been running that for about an hour no issues.
AT&T SGS2 rooted!
Another Phone gets the best Android ROM ever!!! ;-)
jivy26 said:
Yea I've been running that for about an hour no issues.
AT&T SGS2 rooted!
Click to expand...
Click to collapse
Thanks - excellent! Change your signature to say "AT&T SGS2 CyanogenMod 7!"
Lol already did
Phone: AT&T SGS2
Running: CM7
getting signature verification failed. and yes, i am already rooted.
LOL seriously...already cm7 is here?? Can't wait to get home and throw this on here
Sent from my SAMSUNG-SGH-I777 using xda premium
jivy26 said:
Lol already did
Phone: AT&T SGS2
Running: CM7
Click to expand...
Click to collapse
Are you running the version of CM7 that codeworkx sent to you? No problems with installation?
atinm said:
Are you running the version of CM7 that codeworkx sent to you? No problems with installation?
Click to expand...
Click to collapse
Yea just had to install cm7 let it reboot it won't load passed galaxy s2. Pull battery goo into cwm install again gtg
Sent from my SGH-I777 using xda premium
seattleboi1982 said:
getting signature verification failed. and yes, i am already rooted.
Click to expand...
Click to collapse
Did you follow the instructions in the second post in the thread? As in, did you use the "Harder way" - flash ClockworkMod recovery etc?
I flashed before this thread was started so flashed using Odin and kernel codework released for cwm. Used super one click to root Then flash cm7 in cwm like I posted earlier
Sent from my SGH-I777 using xda premium
jivy26 said:
I flashed before this thread was started so flashed using Odin and kernel codework released for cwm. Then flash cm7 in cwm like I posted earlier
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Ok, great - the "harder way" (and only way at the moment!). Thanks!
Tried MIUI and CM7...
Obvious bugs are the back button not working.
But the major one is I can't hear anyone on a call and they can't hear me. Complete silence...both MIUI and CM7. Kernel issue? Known issue?
My order is in, should be seeing my Galaxy S II very soon, stoked!
I'll be testing just about everything pushed out once its here, I'll be reporting back as much as possible can't wait!
Drew489 said:
Tried MIUI and CM7...
Obvious bugs are the back button not working.
But the major one is I can't hear anyone on a call and they can't hear me. Complete silence...both MIUI and CM7. Kernel issue? Known issue?
Click to expand...
Click to collapse
I didn't even know there was a MIUI for AT&T Samsung Galaxy SII yet. As far as no sound - we haven't been able to test anything ourselves as we don't have a device to test on yet (maybe in a couple of days). The code itself hasn't changed much, but it is possible you're seeing something valid that we'll have to fix.
jivy26 said:
Running very smooth on the sgs2 keep up the great work.
AT&T SGS2 running CM7.
Click to expand...
Click to collapse
Did you test voice calls? Can you report back?
hello guys let me fill you in on what ive done here....
ive taken turl's cm9 for the atrix forund here: http://forum.xda-developers.com/showthread.php?t=1500535 {thank you turl for such great work}
and transplanted the photons info into it.....
not going to post an incredible amount of info on it since it is cm9 and by now you guys should know what common issues are across the board with cm9
i am in no way suggesting this build is in anyway better than joker's cm9 i am simply providing the mopho community with more options and activity... dont ask me which is better or how is this different..... i will not answer you.... you will have to try and see for yourself....thanks guys
not working:
mms in stock use gosms or similar...or
open voice dialer say apns... then make sure that it is set properly like so:
first delete the cdma0 then click on cdma1 and fill out like below click save, then click on uscc and fill out like below click save and then back out and reboot you should have working mms now
1st one:
Name: CDMA
APN:1
MMSC: http://mms.sprintpcs.com
MCC: 310
MNC: 120
APN type: mms
APN protocol: IPv4/IPv6
APN roaming protocol: IPv4/IPv6
2nd:
Name: USCC
APN:internet
Port: 80
MMSC: http://mmsc1.uscc.net/mmsc/MMS
MMS port: 80
MCC: 310
MNC: 120
Authentication type: PAP or CHAP
APN type: mms
APN protocol: IPv4/IPv6
APN roaming protocol: IPv4/IPv6
Reboot after saving and setting up Both of them.
USCC apns: [thanks byte]
for mms to work with USCC
you need to enter username and password.
username is [email protected]
password is min
replace min with your actual min
min is usually your phone number..
delete all other apns
and you should be good to go
you tell us!
install instructions
V10 instructions for fresh flash:
use th3bills wipe all zip: http://www.mediafire.com/download.php?09s7943ps87rwed or...............
format system, cache, data,
flash rom, flash rom a second time, flash gapps, reboot
V10 instructions for flash over:
use th3bills wipe cache zip: http://www.mediafire.com/download.php?t0ctb4am6ftbw42 or....
wipe cache, dalvick cache flash rom, flash rom a second time, flash gapps, then reboot
V9 instructions for fresh flash:
use th3bills wipe all zip [link provided above] or....
format system, data, cache
flash rom, flash gapps and reboot
V9 instructions for flash over:
use th3bills wipe cache zip [link provided above] or.....
wipe cache, wipe dalvick cache, flash rom, flash gapps and reboot
*if a few fc's reboot to recovery wipe dalvick cache and fix permissions reboot and enjoy CM9
TurlCM9_V10_PhotonB2:
file size: 120.34 MB
md5: 5b9265df6c8def56afd2b10108dd824e
devhost: http://d-h.st/8ZR
TurlCM9_V10_GSM_PhotonB2:
file size: 120.34 MB
md5: 40f02ca9980f78bcd97b3fda5a2676e1
devhost: http://d-h.st/EeY
gapps:
http://goo.im/gapps/gapps-ics-20120317-signed.zip
blueesleep_fix: [ thanks oleg! ]
devhost: http://d-h.st/3sY
*A bug(?) this ROM and Jokersax's have this symptom. If your SIM has a lock, the phone loads, but doesn't ask you for the lock code. It behaves as if there is no SIM lock. As a result, you can't connect to the network. Work around. Go into settings and uncheck the SIM lock. It of course asks you for the lock to your SIM. You reboot and now the phone can access the network. If you don't do this, you can't access the network and APN doesn't work.[THANKS COOLQF!]
Previous Builds:
Turlcm9_V9_Photon:
file size: 116.50 MB
md5: e9ce85838f2ba6181b98cbe074776491
mediafire: http://www.mediafire.com/download.php?l5esylr2w9w75i7
devhost: http://d-h.st/JQa
Turlcm9_V9_GSM_Photon:
filesize: 116.35 MB
md5: 861062f005ed5334b73466e4e59adad6
mediafire: http://www.mediafire.com/download.php?7hhwnehkhrxqt2z
devhost: http://d-h.st/zRb
please report any and everything and as with any flash make a backup of your current rom and apps....happy flashes
big thanks to everyone making our phones better this includes testers original rom bases file diggers EVERYONE
THANKS!
*brought to you by the same group who brought you miui for the photon
Does GSM work on this version?
Sent from my Photon
coolqf said:
Does GSM work on this version?
Sent from my Photon
Click to expand...
Click to collapse
i can make one or you can change :
# Default network type.
# 0 -> WCDMA preferred
ro.telephony.default_network=7
take the 7 make it a 0 then reboot should make it run on gsm
* yeah what bill said ill edit it myself and post a gsm version for you guys since we know how to do it now there is no excuse...lol
*edited and uping now guys will be called turlcm9_v9_GSM_photon will drop link as soon as its done
spleef said:
i can make one or you can change :
# Default network type.
# 0 -> WCDMA preferred
ro.telephony.default_network=7
take the 7 make it a 0 then reboot should make it run on gsm
Click to expand...
Click to collapse
Do before flash....after flash, it's hit or miss as to whether it works...most people say no
this is actually older than last jokersax ROM, so it may have some small issues joker doesnt have. still, have better battery life time and almost everything works
please moderator dont delete my post... i may be just sleep answering!
Th3Bill said:
Do before flash....after flash, it's hit or miss as to whether it works...most people say no
Click to expand...
Click to collapse
First of, Th3Bill and spleef, thank you so much! Thank your also for uploading the file. I'm also very eager to learn. This is all a little new to me, but i'm a quick learner and actually googled instructions. I don't quite understand how to do it BEFORE flashing. Here's what I know from reading:
1) Install ROM (phone is rooted and unlocked of course)
2) Load ES File Explorer
3) Go into /System
4) Back up build.prop
5) Open build.prop
6) Make the following changes to reflect the following:
# Default network type.
# 0 -> WCDMA preferred
ro.telephony.default_network=0
7) Save build.prop
8) Reboot phone
What step do I add/change?
coolqf said:
First of, Th3Bill and spleef, thank you so much! Thank your also for uploading the file. I'm also very eager to learn. This is all a little new to me, but i'm a quick learner and actually googled instructions. I don't quite understand how to do it BEFORE flashing. Here's what I know from reading:
1) Install ROM (phone is rooted and unlocked of course)
2) Load ES File Explorer
3) Go into /System
4) Back up build.prop
5) Open build.prop
6) Make the following changes to reflect the following:
# Default network type.
# 0 -> WCDMA preferred
ro.telephony.default_network=0
7) Save build.prop
8) Reboot phone
What step do I add/change?
Click to expand...
Click to collapse
That works...(as long as ES has that level of capability. I use Root Explorer...like it's functionality better) but like I said before, the way that I know people have really had it working was to edit that file before flashing. It's the correct procedure to change that file on the phone.
coolqf said:
First of, Th3Bill and spleef, thank you so much! Thank your also for uploading the file. I'm also very eager to learn. This is all a little new to me, but i'm a quick learner and actually googled instructions. I don't quite understand how to do it BEFORE flashing. Here's what I know from reading:
1) Install ROM (phone is rooted and unlocked of course)
2) Load ES File Explorer
3) Go into /System
4) Back up build.prop
5) Open build.prop
6) Make the following changes to reflect the following:
# Default network type.
# 0 -> WCDMA preferred
ro.telephony.default_network=0
7) Save build.prop
8) Reboot phone
What step do I add/change?
Click to expand...
Click to collapse
in your buildprop
you will see this line;
# Default network type.
# 0 -> WCDMA preferred
ro.telephony.default_network=7
make the 7 a 0 save and reboot its almost done so i will be adding the link you should be able to flash over the gsm and it should overwrite making the change just wipe cache and dalvick cache then flash or....
use my man th3bill's wipe cache zip: http://www.mediafire.com/download.php?t0ctb4am6ftbw42
then flash...lol
GSM version is up please let me know if it is working as i have no way of testing it... thanks
spleef said:
in your buildprop
you will see this line;
# Default network type.
# 0 -> WCDMA preferred
ro.telephony.default_network=7
make the 7 a 0 save and reboot its almost done so i will be adding the link you should be able to flash over the gsm and it should overwrite making the change just wipe cache and dalvick cache then flash or....
use my man th3bill's wipe cache zip: http://www.mediafire.com/download.php?t0ctb4am6ftbw42
then flash...lol
GSM version is up please let me know if it is working as i have no way of testing it... thanks
Click to expand...
Click to collapse
Downloading now! I'm also downloading MIUI by you and Th3Bill. So it's going a lil slower. 30min wait... =/
coolqf said:
Downloading now! I'm also downloading MIUI by you and Th3Bill. So it's going a lil slower. 30min wait... =/
Click to expand...
Click to collapse
cool which version....lol we have two one based on turl one based on joker all the fixes work on both.... JuSt be sure if you need help to mention which version since they are based on different cm9's.... Thanks man enjoy
MIUI/ICS for the Photon
http://forum.xda-developers.com/showthread.php?t=1536161
spleef said:
cool which version....lol we have two one based on turl one based on joker all the fixes work on both.... JuSt be sure if you need help to mention which version since they are based on different cm9's.... Thanks man enjoy
MIUI/ICS for the Photon
http://forum.xda-developers.com/showthread.php?t=1536161
Click to expand...
Click to collapse
Very true on that!
I love this rom, everything is working smooth! But i would like to go to miui for now...
Installed GSM version you just posted.
Here's what I did:
1)Installed Jokersax's recover V3
2) Did a recovery reboot
3) Wiped partition, cache, and dalvik
4) Did a recovery reboot
5) Installed your ROM
6) Did a recovery reboot
7) Installed ROM again
8) Rebooted system
9) Installed GAPPS
-Camera works, holding the camera horizontal and vertical. Jokersax's would crash on me if I attempted to load it right after the phone loaded. I don't have that problem with this ROM. Takes pictures fine.
-Keyboard works. If you type too quickly sometimes the haptic doesn't work. (I always turn this off, so no biggie) Same problem in Jokersax's.
-Swiping through the apps is pretty smooth. You have to create longer swipes than on CM7, or else it might tap, but no biggie.
-It feels like you need to put more pressure against the screen for swipes and key taps to be recognized when compared to CM7.2
-Connected to my wifi without a problem. Works as expected.
-Enabled built-in sdcard. Works fine, can access data.
-Automatically loaded my APN settings after rebooting the phone. No need to enter them manually. (had to remove my SIM's lock though).
-Connects to EDGE and 3G (GSM) fine
-Restoring apps through MyBackup root was faster
-The only restore that was slower, SMS. On CM7.2 this took less than a minute. On CM9, it took closer to 5minutes. It was a total of 1101 SMS.
-Google Play works. apps that needed updating were updated without a hitch. It quickly recognized my restored apps after a reboot (normally this took about 10 min on CM7.2)
-Auto dim works when phone not being used for a couple of seconds
-WhatApp, linkedin, Skype & twitter loads and syncs.
-Facebook app can't sync contacts <--Problem with all ICS(the app works) (I use friendcaster for syncing, it's better anyway)
-Google maps works.
-Gmail works fine. It's at version 4.0, which is better. Something odd, the app was preinstalled, but couldn't see it in Google Play. I had to do a restore of gmail, and then it showed up in Play.
-Google Maps, it wasn't in the phone or in Google Play. Restoring it from a backup allowed it to update and show up on my phone, and in Google Play.
-All the other small things worked fine, recent calls, contacts (merged contacts w/o a hitch)
-Pattern unlock doesn't work too well. I had to disable it. It behaves as if I lift my finger some times....
A bug(?) this ROM and Jokersax's have this symptom. If your SIM has a lock, the phone loads, but doesn't ask you for the lock code. It behaves as if there is no SIM lock. As a result, you can't connect to the network. Work around. Go into settings and uncheck the SIM lock. It of course asks you for the lock to your SIM. You reboot and now the phone can access the network. If you don't do this, you can't access the network and APN doesn't work.
I hope this helps. Overall, I love the ROM and will keep using it and test it out =D
coolqf said:
Installed GSM version you just posted.
Here's what I did:
1)Installed Jokersax's recover V3
2) Did a recovery reboot
3) Wiped partition, cache, and dalvik
4) Did a recovery reboot
5) Installed your ROM
6) Did a recovery reboot
7) Installed ROM again
8) Rebooted system
-Camera works, holding the camera horizontal and vertical. Jokersax's would crash on me if I attempted to load it right after the phone loaded. I don't have that problem with this ROM.
-Keyboard works. If you type too quickly sometimes the haptic doesn't work. (I always turn this off, so no biggie) Same problem in Jokersax's.
-Swiping through the apps is pretty smooth. You have to create longer swipes than on CM7, or else it might tap, but no biggie.
-It feels like you need to put more pressure against the screen for swipes and key taps to be recognized when compared to CM7.2
-Connected to my wifi without a problem. Works as expected.
-Enabled built-in sdcard. Works, can access data.
-Automatically loaded my APN settings after rebooting the phone. No need to enter them manually. (had to remove my SIM's lock though).
-Connects to EDGE and 3G (GSM) fine
-Restoring apps through MyBackup root was faster
-The only restore that was significantly slow, SMS. On CM7.2 this took less than a minute. On CM9, it took closer to 5minutes. It was a total of 1101 SMS.
-Google Play works. apps that needed updating were updated without a hitch. It quickly recognized my restored apps after a reboot (normally this took about 10 min on CM7.2)
-Auto dim works when phone not being used for a couple of seconds
-WhatApp loads and syncs.
-Facebook contacts can't sync (the app works) (Suggestions on workaround?)
-Google maps works. Although sometime the google maps screen would just be a cream color. Only way to the the map again is by backing out of the app and loading it again.
I installed the GAPPS from jokersax, version 11. I've logged into my account and it seems to work. (I didn't have the one from this thread in my SDCARD, oops).
A bug(?) this ROM and Jokersax's have this symptom. If your SIM has a lock, the phone loads, but doesn't ask you for the lock code. It behaves as if there is no SIM lock. As a result, you can't connect to the network. Work around. Go into settings and uncheck the SIM lock. It of course asks you for the lock to your SIM. You reboot and now the phone can access the network. If you don't do this, you can't access the network and APN doesn't work.
I hope this helps. Overall, I love the ROM and will keep using it and test it out =D
Click to expand...
Click to collapse
thank you very good review and report....very much appreciated...i will add your workaround to op about sim lock
also the double flash isnt necessary but you can if you feel like you need it..
the gapps might be why some things arent working right.... idk for sure.... i think joker mods his gapps the gapps package i have is the one from goo unaltered..
the facebook im not sure i think cm9 did away with it at one point....again not entirely 100% on that ill look into it though and see if it was removed and if i can add it back
maps im not sure i will look into it.. but thanks again for running it and please do report the more you find
can also try to wipe dalvick and fix permissions might help with maps idk..can also try uninstalling maps and reinstalling it
spleef said:
thank you very good review and report....very much appreciated...i will add your workaround to op about sim lock
also the double flash isnt necessary but you can if you feel like you need it..
the gapps might be why some things arent working right.... idk for sure.... i think joker mods his gapps the gapps package i have is the one from goo unaltered..
the facebook im not sure i think cm9 did away with it at one point....again not entirely 100% on that ill look into it though and see if it was removed and if i can add it back
maps im not sure i will look into it.. but thanks again for running it and please do report the more you find
can also try to wipe dalvick and fix permissions might help with maps idk..can also try uninstalling maps and reinstalling it
Click to expand...
Click to collapse
Reinstalled fresh again. This time using the GAAPS in this thread. Let's see how things go =D Read up on facebook. Apparently Google is redoing the API and for this reason Facebook and ICS (by default) currently don't play nice for contacts.
coolqf said:
installed gsm version you just posted.
Here's what i did:
1)installed jokersax's recover v3
2) did a recovery reboot
3) wiped partition, cache, and dalvik
4) did a recovery reboot
5) installed your rom
6) did a recovery reboot
7) installed rom again
8) rebooted system
-camera works, holding the camera horizontal and vertical. Jokersax's would crash on me if i attempted to load it right after the phone loaded. I don't have that problem with this rom.
-keyboard works. If you type too quickly sometimes the haptic doesn't work. (i always turn this off, so no biggie) same problem in jokersax's.
-swiping through the apps is pretty smooth. You have to create longer swipes than on cm7, or else it might tap, but no biggie.
-it feels like you need to put more pressure against the screen for swipes and key taps to be recognized when compared to cm7.2
-connected to my wifi without a problem. Works as expected.
-enabled built-in sdcard. Works, can access data.
-automatically loaded my apn settings after rebooting the phone. No need to enter them manually. (had to remove my sim's lock though).
-connects to edge and 3g (gsm) fine
-restoring apps through mybackup root was faster
-the only restore that was significantly slow, sms. On cm7.2 this took less than a minute. On cm9, it took closer to 5minutes. It was a total of 1101 sms.
-google play works. Apps that needed updating were updated without a hitch. It quickly recognized my restored apps after a reboot (normally this took about 10 min on cm7.2)
-auto dim works when phone not being used for a couple of seconds
-whatapp loads and syncs.
-facebook app can't sync contacts (the app works) (i use friendcaster for syncing)
-google maps works. Although sometime the google maps screen would just be a cream color. Only way to the the map again is by backing out of the app and loading it again.
I installed the gapps from jokersax, version 11. I've logged into my account and it seems to work. (i didn't have the one from this thread in my sdcard, oops).
A bug(?) this rom and jokersax's have this symptom. If your sim has a lock, the phone loads, but doesn't ask you for the lock code. It behaves as if there is no sim lock. As a result, you can't connect to the network. Work around. Go into settings and uncheck the sim lock. It of course asks you for the lock to your sim. You reboot and now the phone can access the network. If you don't do this, you can't access the network and apn doesn't work.
I hope this helps. Overall, i love the rom and will keep using it and test it out =d
Click to expand...
Click to collapse
now this is a proper, helpful review! Need more like this on every rom out there....including joker's. Just putting "x doesn't work" doesn't help. Telling dev exactly what you were doing and how you were doing when x didn't work and the way it didn't work is the right way. Great review!
I am so confused!!!! Now I have so many ROM options I don't know which one to pick. Lol (On CM7.2 now but was on Jokers CM9 prior)
You guys do great work and been a huge help for me with issues I have had so I wanted to thank you.
Sent from my MB855 using Tapatalk
netengineer said:
I am so confused!!!! Now I have so many ROM options I don't know which one to pick. Lol (On CM7.2 now but was on Jokers CM9 prior)
You guys do great work and been a huge help for me with issues I have had so I wanted to thank you.
Sent from my MB855 using Tapatalk
Click to expand...
Click to collapse
No problem. That's what this is all about....sharing information so that we can make all our "toys' work WAAYYY better
Th3Bill said:
now this is a proper, helpful review! Need more like this on every rom out there....including joker's. Just putting "x doesn't work" doesn't help. Telling dev exactly what you were doing and how you were doing when x didn't work and the way it didn't work is the right way. Great review!
Click to expand...
Click to collapse
yep was perfect well wrote thank you it even will hepl others coming who are curious in knowing what to kind expect but as always guys YMMV.... thanks again
With this and other GSM capable roms, is it a "either/or" situation, where if you install the GSM rom you can't connect CDMA, or is it just like an additional feature, so you could use cdma by default and roam on gsm?
GEEWIZ 4.5 SCH-I500 JDQ39 JELLY BEAN 4.2.2 ROM/KERNEL
FOR GEEWIZ MEDIA 4.5 (WI-FI ONLY VERSION) SEE THE SECOND POST
GeeWiz 4 is a ROM for the Samsung Fascinate, based on AOSP Jelly Bean 4.2. Like it's predecessors of the same name, GeeWiz doesn't aim to provide a lot of bells and whistles or incorporate all of the latest and greatest tweaks and enhancements developed by the community; the aim is to provide a basic, stable, functional device.
GeeWiz 4 uses a modified version of the Samsung EH03 Gingerbread (Linux 2.6) kernel with a number of very specific tweaks/hacks in order to continue to support the proprietary Samsung RFS file system and other features I wanted to carry over. As a result, this ROM may not be used in conjunction with any other Kernel, and this Kernel cannot be used in conjunction with any other ROM. Please consider it a "matched set", and they will always be updated/distributed together. XDA community developed enhancements to the ROM or Kernel are encouraged, and will be given prominent feature status in this post.
Your device needs to be set up as stock or stock-like (e.g. GeeWiz 2.x/3.x) before installing this ROM/Kernel. If you are currently running with an MTD-based platform, the device must be reverted back to the original OEM volume format. Please refer to the forum/thread were you acquired your current ROM for guidance on how to revert the device as necessary.
Installing this ROM/Kernel or any other provided component(s) will void your device's warranty, and I cannot be held responsible for any damages of any kind (including data loss) that are incurred either directly or indirectly by these packages and components. What you do to your device is ultimately your problem!
FEATURES
Android Jelly Bean AOSP build JDQ39 (android-4.2.2_r1)
All devices (GPS, compass, orientation, camera, flash) are functional
Wifi (WPA/WPA2) and Bluetooth Tethering support
Supports OEM DBDATA volume to keep performance reasonable
Supports both RFS and EXT4 formatting on all volumes
OEM USB modes (CD-ROM/Kies/MTP) replaced with standard Android Mass Storage
Advanced Battery Settings: Maximum Charge, Automatic Recharge Point
Advanced CPU Settings: Maximum/Minimum Clock Speed, Governor Selection
Advanced In-Call Volume Boost Selection
Advanced Telephony APN Editor Setting
Advanced Vibration Intensity Setting
Backlight Notifications built into system, controlled by the OS
Supercurio Voodoo Sound 10
Fascinate Dock audio simulates a USB audio device for seamless output path switching
Custom Dock options - Enable BLN, Stay Awake, Enable audio output, Override A2DP audio
Quick Settings for Wifi and Bluetooth modified to work as toggles -- long-press to access Settings
Custom "ICS Clock" Daydream that mimics the Android 4.0/4.1 Desk Clock screensaver
Custom Notification Panel Header controls: Brightness Slider and Volume Slider
WHAT'S NEW IN GEEWIZ 4.5
All optional Google Apps available from the Play Store removed from the base ROM (See GEEWIZ PREINSTALL below)
GeeWiz Preinstall support (see GEEWIZ PREINSTALL below)
Enables support for all available AOSP languages
Audio stream volumes (Media/Notification/Alarm) are no longer linked together and can be individually set
Fixes issue with low headphone/headset output volume
Port of CyanogenMod Volume Rocker Seek to skip tracks when screen is off; enable in Settings/Advanced
Removes headphone volume safety level warnings in regions/countries that required it to be shown
GEEWIZ PREINSTALL
As of GeeWiz 4.5, the original PREINSTALL volume of the device can be used to supply a set of application APKs that will be automatically installed when the device is executing it's initial setup (after a Factory Reset or ODIN session). The applications will be installed as they normally would be through the Play Store or side-loading, therefore they are not considered system applications and can be uninstalled.
The DOWNLOADS section below contains a base set of PREINSTALL files that can be flashed to the device alongside the standard ROM to enable this functionality. The base set contains the basic Nexus Google applications and updates current through the date indicated. This file can be modified to your liking to add/remove APKs of your choosing; please post a question to this thread and I can explain how the PREINSTALL volume files should be laid out in your .zip file.
The GeeWiz "Full Wipe" ODIN package includes the PREINSTALL files by default. Upon the initial reboot after the ODIN session the applications will be installed automatically. This was done in a non-optional way because the PREINSTALL volume data cannot be flashed separately via ODIN, it must be flashed in conjunction with the main user data volume.
PAGEPLUS CELLULAR MMS SETTINGS
Users that are on the PagePlus Cellular network will not be able to send/receive MMS without changing an APN setting:
Open Settings/Advanced/APNs
Tap the top entry - "Verizon (internet)"
Scroll down to and tap on "MMS port"
Enter a value of 80 and tap OK
Close Settings
KNOWN ISSUES
PRL update via *228 option 2 will appear to not work
As of GeeWiz 4.4, the dialer keypad is available during a *228 call allowing you to choose option 2 and update the Preferred Roaming List (PRL). When the call automatically ends, Android will mistakenly inform you that "activation failed" and you may also lose voice/3G temporarily. Either reboot the phone or enable/disable airplane mode to restore phone/3G capabilities. The PRL update operation in and of itself seems to work and will persist, this can be verified by checking Settings/About Phone/Status/PRL Version before and after the update.
Settings/Advanced/APNs does not bring up the APN preferences
This issue was fixed in GeeWiz Patch 4.5.2, available below in the DOWNLOADS section.
FIRST-TIME INSTALLATION RECOMMENDATION
This ROM performs significantly better when the device uses the EXT4 file system. Unfortunately, using ODIN will always format the device with the RFS file system. The "Full Wipe" ODIN package provided here has been modified so that it will format the data volumes (DATA, DBDATA, CACHE) with the EXT4 file system. This is the recommended installation method for first-time installation to insure the best overall performance.
If the "Full Wipe" ODIN package is not used, please note that your data must be wiped manually if coming from another ROM to avoid problems, and I strongly recommend converting, at minimum, the data volumes of the device (DATA, DBDATA, CACHE) to the EXT4 file system.
DOWNLOADS
EDIFY Update-Zip (ClockworkMod / GeeWiz Recovery) Compatible Downloads
GeeWiz 4.5 ROM/Kernel (EDIFY Update-Zip)
http://www.mediafire.com/download/u97cpe0ylo92oou/geewiz-4.5-syskernel-20130913.zip
MD5: a0b755d81bf874e636bc8ede7192b146
GeeWiz Preinstall Binaries 10.12.2013 (EDIFY Update-Zip)
http://www.mediafire.com/download/fl4hchmgg0dv4r8/geewiz-preinstall-20131012.zip
MD5: f8f6f48ac9816eddd70b15331de12d88
GeeWiz 4.5.2 Patch (EDIFY Update-Zip)
http://www.mediafire.com/download/73sidh42x11x1a7/geewiz-4.5.2-patch-20130926.zip
- Note: Supercedes patch v4.5.1
- Fixes Settings/Advanced/APNs so that the APN editor will be activated
- Adds new "Never" option to Settings/Advanced/Backlight Timeout
MD5: d8efc5975b89aa1921d7fac023718842
GeeWiz Recovery 2.9 (EDIFY Update-Zip)
http://www.mediafire.com/download/2j27d27m9w3mdym/geewiz-recovery-2.9-20130305.zip
MD5: 0da5e767ecde176828d2bab5a58c2d19
ODIN Compatible Downloads
GeeWiz 4.5 ROM/Kernel/Modem/Recovery/Data Wipe Full Update (ODIN)
This will delete all user data from your device, replace your RECOVERY with GeeWiz Recovery as well as replace your modem with the EH03 revision. Your data volumes will be formatted with EXT4 on the first boot
http://www.mediafire.com/download/uvicb41l9qj2fn1/geewiz-4.5-fullwipe-20130913.tar.md5
MD5: ee07cabb4f659af0e510e008ad2e005c
GeeWiz 4.5 ROM/Kernel (ODIN)
http://www.mediafire.com/download/vuhc54i1ak1r79c/geewiz-4.5-syskernel-20130913.tar.md5
MD5: 34a4275d9ee7758bef15eaf062e86a0a
GeeWiz 2.9 Recovery (ODIN)
http://www.mediafire.com/file/9sfufsugg7f27gg/geewiz-recovery-2.9-20130305.tar.md5
MD5: 9526a67d2359ccc82dd652fddccd9a73
THEMES, BATTERY METERS, ETC
I do not currently create or directly support any themes, battery meter modifications, or any other graphical enhancements for GeeWiz. By nature, these types of modifications can never fully satisfy everyone, as look and feel is always a personal and very individual preference. I encourage and will support as best I can third party themes and graphical modification projects, I am just not currently willing to participate in the creative process.
Battery Meter (and perhaps other) modifications to GeeWiz can be created manually via the UOT Kitchen. I highly recommend using this service to apply custom battery meters or other graphical UI element changes to GeeWiz. Instructions are available at the UOT Kitchen site, and you are welcome to ask questions in this thread for other users to see and potentially answer.
SOURCE CODEThe entire baseline for GeeWiz is available on github: https://www.github.com/djp952.
Device repo: android-platform-device-samsung-atlas3g (branch android-4.2.2_r1)
Kernel repo: android-kernel-atlas (branch android-4.2.2_r1)
GEEWIZ MEDIA 4.5 SCH-I500 JDQ39 JELLY BEAN 4.2.2 ROM/KERNEL
FOR GEEWIZ 4.5 (PHONE/MOBILE DATA VERSION) SEE THE FIRST POST
GeeWiz Media 4 is a Wifi-only ROM for the Samsung Fascinate, based on AOSP Jelly Bean 4.2. The goal of GeeWiz Media is to allow the Samsung Fascinate device to continue to be used as a media player-like device after it has been disconnected from cellular service. There is no support for cellular voice/data communication present in this ROM. Like it's predecessors, GeeWiz Media 4 doesn't aim to provide a lot of bells and whistles or incorporate all of the latest and greatest tweaks and enhancements developed by the community; the aim is to provide a basic, stable, functional device.
GeeWiz Media 4 uses a modified version of the Samsung EH03 Gingerbread (Linux 2.6) kernel with a number of very specific tweaks/hacks in order to continue to support the proprietary Samsung RFS file system and other features I wanted to carry over. As a result, this ROM may not be used in conjunction with any other Kernel, and this Kernel cannot be used in conjunction with any other ROM. Please consider it a "matched set", and they will always be updated/distributed together.
Your device needs to be set up as stock or stock-like (e.g. GeeWiz 2.x/3.x) before installing this ROM/Kernel. If you are currently running with an MTD-based platform, the device must be reverted back to the original OEM volume format. Please refer to the forum/thread were you acquired your current ROM for guidance on how to revert the device as necessary.
Installing this ROM/Kernel or any other provided component(s) will void your device's warranty, and I cannot be held responsible for any damages of any kind (including data loss) that are incurred either directly or indirectly by these packages and components. What you do to your device is ultimately your problem!
FEATURES
Android Jelly Bean AOSP build JDQ39 (android-4.2.2_r1)
Wifi-Only, no support for Voice/Mobile Data
All devices (GPS, compass, orientation, camera, flash) are functional
Supports both RFS and EXT4 formatting on all volumes
OEM USB modes (CD-ROM/Kies/MTP) replaced with standard Android Mass Storage
Advanced Battery Settings: Maximum Charge, Automatic Recharge Point
Advanced CPU Settings: Maximum/Minimum Clock Speed, Governor Selection
Advanced Vibration Intensity Setting
Backlight Notifications built into system, controlled by the OS
Supercurio Voodoo Sound 10
Fascinate Dock audio simulates a USB audio device for seamless output path switching
Custom Dock options - Enable BLN, Stay Awake, Enable audio output, Maximize volume, Override A2DP audio
Quick Settings for Wifi and Bluetooth modified to work as toggles -- long-press to access Settings
Custom "ICS Clock" Daydream that mimics the Android 4.0/4.1 Desk Clock screensaver
Bluetooth Tethering support
Custom Notification Panel Header Brightness and Volume Slider controls
WHAT'S NEW IN GEEWIZ MEDIA 4.5
All optional Google Apps available from the Play Store removed from the base ROM (See GEEWIZ PREINSTALL below)
GeeWiz Preinstall support (see GEEWIZ PREINSTALL below)
Enables support for all available AOSP languages
Audio stream volumes (Media/Notification/Alarm) are no longer linked together and can be individually set
Re-enables the Notification Panel "Volume Slider" control selection in Settings/Advanced/Notification Panel Header
Fixes issue with low headphone/headset output volume
Automatic network date/time option enabled by default during setup wizard
Port of CyanogenMod Volume Rocker Seek to skip tracks when screen is off; enable in Settings/Advanced
Removes headphone volume safety level warnings in regions/countries that required it to be shown
GEEWIZ PREINSTALL
As of GeeWiz 4.5, the original PREINSTALL volume of the device can be used to supply a set of application APKs that will be automatically installed when the device is executing it's initial setup (after a Factory Reset or ODIN session). The applications will be installed as they normally would be through the Play Store or side-loading, therefore they are not considered system applications and can be uninstalled.
The DOWNLOADS section below contains a base set of PREINSTALL files that can be flashed to the device alongside the standard ROM to enable this functionality. The base set contains the basic Nexus Google applications and updates current through the date indicated. This file can be modified to your liking to add/remove APKs of your choosing; please post a question to this thread and I can explain how the PREINSTALL volume files should be laid out in your .zip file.
The GeeWiz "Full Wipe" ODIN package includes the PREINSTALL files by default. Upon the initial reboot after the ODIN session the applications will be installed automatically. This was done in a non-optional way because the PREINSTALL volume data cannot be flashed separately via ODIN, it must be flashed in conjunction with the main user data volume.
FIRST-TIME INSTALLATION RECOMMENDATION
This ROM performs significantly better when the device uses the EXT4 file system. Unfortunately, using ODIN will always format the device with the RFS file system. The "Full Wipe" ODIN package provided here has been modified so that it will format the data volumes (DATA, DBDATA, CACHE) with the EXT4 file system. This is the recommended installation method for first-time installation to insure the best overall performance.
If the "Full Wipe" ODIN package is not used, please note that your data must be wiped manually if coming from another ROM to avoid problems, and I strongly recommend converting, at minimum, the data volumes of the device (DATA, DBDATA, CACHE) to the EXT4 file system.
DOWNLOADS
EDIFY Update-Zip (ClockworkMod / GeeWiz Recovery) Compatible Downloads
GeeWiz Media 4.5 ROM/Kernel (EDIFY Update-Zip)
http://www.mediafire.com/download/eebtnvl2wb40h74/geewiz-media-4.5-syskernel-20130913.zip
MD5: e23dfa3eee62c67d7b15996b762981ba
GeeWiz Media Preinstall Binaries 10.12.2013 (EDIFY Update-Zip)
http://www.mediafire.com/download/ktqiy9tmmi6147u/geewiz-preinstall-20131012.zip
MD5: f8f6f48ac9816eddd70b15331de12d88
GeeWiz Media 4.5.2 Patch (EDIFY Update-Zip)
http://www.mediafire.com/download/bk0wbz0kk0ihc03/geewiz-media-4.5.2-patch-20130926.zip
- Note: Supercedes Patch v4.5.1
- Adds new "Never" option to Settings/Advanced/Backlight Timeout
MD5: 4265d7bc862e1e5ead36900fe824b76e
GeeWiz 2.9 Recovery (EDIFY Update-Zip)
http://www.mediafire.com/file/5hr57ddndd99s2r/geewiz-recovery-2.9-20130305.zip
MD5: 0da5e767ecde176828d2bab5a58c2d19
ODIN Compatible Downloads
GeeWiz Media 4.5 ROM/Kernel/Modem/Recovery/Data Wipe Full Update (ODIN)
This will delete all user data from your device, replace your RECOVERY with GeeWiz Recovery as well as replace your modem with the EH03 revision. Your data volumes will be formatted with EXT4 on the first boot
http://www.mediafire.com/download/0l8pefgl1h48xan/geewiz-media-4.5-fullwipe-20130913.tar.md5
MD5: a657abef82fb87d7a8cf7fcd27b974e4
GeeWiz Media 4.5 ROM/Kernel (ODIN)
http://www.mediafire.com/download/yh2q5i7elw124ov/geewiz-media-4.5-syskernel-20130913.tar.md5
MD5: 8a360bfce37ee2254493e51ef69bc0cf
GeeWiz 2.9 Recovery (ODIN)
http://www.mediafire.com/file/wfbi4rswnqzfo0q/geewiz-recovery-2.9-20130305.tar.md5
MD5:9526a67d2359ccc82dd652fddccd9a73
THEMES, BATTERY METERS, ETC
I do not currently create or directly support any themes, battery meter modifications, or any other graphical enhancements for GeeWiz Media. By nature, these types of modifications can never fully satisfy everyone, as look and feel is always a personal and very individual preference. I encourage and will support as best I can third party themes and graphical modification projects, I am just not currently willing to participate in the creative process.
Battery Meter (and perhaps other) modifications to GeeWiz Media can be created manually via the UOT Kitchen. I highly recommend using this service to apply custom battery meters or other graphical UI element changes to GeeWiz. Instructions are available at the UOT Kitchen site, and you are welcome to ask questions in this thread for other users to see and potentially answer.
SOURCE CODEThe entire baseline for GeeWiz Media is available on github: https://www.github.com/djp952.
Device repo: android-platform-device-samsung-atlas (branch android-4.2.2_r1)
Kernel repo: android-kernel-atlas (branch android-4.2.2_r1)
RETURN-TO-STOCK FILES
ODIN v1.3 / Windows Drivers / Partition File (Microsoft Windows)
http://www.mediafire.com/file/hr5g7a6qny3vyhv/odin-for-fascinate.zip
MD5: 28d796dbba45543e26cbaed2fb3164ee
Samsung Official EH03 Complete Stock ODIN Package (ODIN Flash Package)
http://www.mediafire.com/file/qq12w58o0fqxixs/CI500_VZW_EH03_GB_CM.tar.md5
MD5:89045064cf45ccd85f8ad746911b6e28
reserved 3
As you probably noticed, I opted to increment the version number for GeeWiz with the Android 4.2.1 release. I hope this won't cause too much confusion or annoy the other Fascinate devs since that gives me 5 active GeeWiz threads now (sorry other devs!), but I intend to continue to support and maintain the Android 4.1-based GeeWiz 3 for a while, and it's needs and issues will be different than this new Android 4.2-based version. On the "GeeWiz Media" side of the house, I even posted a note that I prefer the older version for personal use, but that doesn't necessarily apply here. Overall, I think GeeWiz 4 came out fairly well, and certainly more timely than GeeWiz 3. As of this posting, GeeWiz is using the latest released version of Android!!
I was unable to get Bluetooth Tethering to work under 4.2 in time for this first release, and I have a few known issues that I've posted above, but overall I think the ROM is pretty solid ... I'm counting on you guys to tell me where it isn't so solid There isn't much to say about it, really, other than the version of Superuser I've included was source-built by me from ChainsDD's latest code. It's newer than what you'll find on the Google Play Store, but thanks to ChainsDD being kind enough to make his keys public, it appears to link with the Play Store just fine so when and if he updates Superuser beyond the included version, I believe it will update seamlessly. If not, I'll of course fix it for ya.
As it was with my first AOSP-based release, GeeWiz 4 is rather light in the "mod" department. The main new modifications involve the 4.2 Quick Settings. I've changed the Wifi and Bluetooth tiles to act as on/off toggles instead of linking you to settings. You can long-press them to get to the settings (and no, I didn't steal this from Cyanogenmod, but I really should have looked there first and saved some time - LOL). I am open to suggestions for more LIGHT modifications that I could include for you guys. Please, nothing heavy-duty, I hate saying no.
I'm sure there will be some new problems that I haven't discovered (please read the KNOWN ISSUES above before installing!!), and I have some additional work to do on this as well as the other various things named "GeeWiz" floating about here at XDA, but I hope that anyone that has been waiting for an Android 4.2 GeeWiz will be happy with what I've hobbled together. I don't know how long we can keep the Fascinate working, but as the proud owner of more than a few of them .. I'm hoping it's a while yet!
Oh, and when you finally decide to dump your Fascinate, please check out my "GeeWiz Media" ROMs here at XDA before you throw it out or trade it in. GeeWiz Media is the same build as this, just without any concept of 3G/cellular service, so you can keep using your Fascinate alive as a media player, browser, clock/radio, game system .. whatever you want. It changes the Fascinate into a very small and somewhat outdated Android tablet :silly:
Enjoy!
edit: I'll get around to moving the "How to compile" post from GeeWiz 3 over here in a day or two. Essentially the same process, but it does need some minor updates.
And I thought you were crazy for even bothering with this. Lol. Excellent sir, excellent.
Sent from my SCH-I500 using Tapatalk 2
wow. I've been very happy with the cm10.1 builds as my daily driver, but I figured that with you devoting all of this time into building GeeWiz 4, the least I could do is flash it and offer some feedback...
I'm still getting things setup, but so far I'm really impressed with the operation and smooth performance.
First, I used Odin to go directly from the cm10 fascinatemtd partition layout to GeeWiz 4. iow, I skipped going to stock by flashing the pit and GeeWiz "full wipe" at the same time.
on first boot, I let Google restore all my active apps before rebooting to GeeWiz recovery and attempting to convert the file system to ext4 (I used the top menu option). this eventually appeared to work, but the device the failed to boot (getting stuck at the Samsung logo).
I went back to Odin and this time on booting GeeWiz I skipped the setup wizard and immediately rebooted to convert the system to ext4.
anyway, I'm now preparing for a day with GeeWiz 4... TiBu complained that it can't get root, so it looks like that issue is back and I'll research it later.
so far it seems like performance and operation will be fine, but I find myself missing some of the cm features... a battery meter that shows the percentage, profiles, quiet hours, etc.
thanks again, more later.
Sent from my SCH-I500 using xda premium
bmeek said:
... TiBu complained that it can't get root, so it looks like that issue is back and I'll research it later.
so far it seems like performance and operation will be fine, but I find myself missing some of the cm features... a battery meter that shows the percentage, profiles, quiet hours, etc.
thanks again, more later.
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
Hey, thanks for giving it a go! The Superuser I'm using here is one I built myself from ChainsDD's latest code, so I can probably be more useful for a change on these types of issues. I suppose I should finally break down and buy Titanium Backup, huh? My primary "test root" apps are Root Explorer and My Backup Pro, you'd think I would be the type of person that needed root for lots of things, but ironically, I barely ever need it
I'll have a look at some of the things CyanogenMod has done to see if any can be "ported" (aka stolen). That doesn't sound too difficult on the surface.
I'm going to be putting together an ODIN guide at some point, knowing that you don't necessarily HAVE to revert to complete stock is very useful to know, thank you. I thought the MTD ROMs modify one of the boot loaders? Yet another case where I really need to sit down and actually use something other than my own stuff!
I'm also very happy and impressed with this so far. My TiBu works just fine.
Would like maybe to see a way to add or subtract stuff in pull down menu, and maybe some options for lock screen. But I'm fine if don't have those
Sent from my SCH-I500 using xda app-developers app
icemanwbs said:
I'm also very happy and impressed with this so far. My TiBu works just fine.
Would like maybe to see a way to add or subtract stuff in pull down menu, and maybe some options for lock screen. But I'm fine if don't have those
Sent from my SCH-I500 using xda app-developers app
Click to expand...
Click to collapse
Thanks!!
One thing at a time I'm resting on laurels tonight ... I'm adding a simple "Legacy Clock" Daydream since I hate the new clock so much and would like to use this instead of the Android 4.1 build for the Fascinate that sits in a dock next to the HTPC in the living room and is essentially just a clock since the Mrs. doesn't like having to use it to control things yet :silly: Back to bug fixes and requests later -- it's *me* time! LOL. Wife Acceptance Factor is a very very important feature in my house. (You have no idea ... no really, you have no idea) :crying:
I think the highest priority bug is probably the ringtone/alarm/notification selection issue. I would really like to squash that one, and I have a good feeling that it's resolution will solve the occasional Force Closes with the Google Apps too. Just a hunch, not 100% certain yet. The data usage graph bug should be easy, and I bought "Titanium Backup PRO * root" tonight so I can play around with that and see if I can break Superuser ... $6.50 seemed a bit high, no wonder I never bought it! LOL.
Lol....ya that is high. I use the free version. I also noticed none of my custom made ringtones are listed. Odd.
Sent from my SCH-I500 using xda app-developers app
djp952 said:
...
I suppose I should finally break down and buy Titanium Backup, huh? My primary "test root" apps are Root Explorer and My Backup Pro, you'd think I would be the type of person that needed root for lots of things, but ironically, I barely ever need it
Click to expand...
Click to collapse
fwiw, I'm using the free flavor of titanium backup.
On the mtd partition layout, I'm not clear on all the details but I can say that they use the stock bootloader. I have a fairly old fascinate that came with éclair, and it was only in recent months that I learned of the recommendation to upgrade the bootloader to an updated version that shipped with vzw's GB release. This "GBbootloader" does persist as i flash between GeeWiz 4 and cm10.
Sent from my SCH-I500 using xda premium
I finished my "ICS Clock" Daydream so now I can get back to real work. I won't issue an entire patch just for this silly change, but it will be in whatever 4.0.1 becomes :laugh: Obviously this was FAR more critical than figuring out why the ringtones list is empty half the time or reading my PMs (I'll get to the PMs next, if anyone is waiting on a response)
I've been looking into the Ringtone/Notification/Alarm issue tonight and I have changed the issue description as well as provided a workaround that so far appears to be functional:
Ringtones/Alarms/Notification Tones may not appear in Settings
Under investigation. There seems to actually be two problems here, one where the ringtone/notification/alarm tones will not appear when you first open Settings/Sounds and will appear later, and another where they were completely omitted from the database and will never show up.
WORKAROUND: Clear data on the "Media Storage" app in Settings and immediately reboot. This seems to alleviate the problem and allows all the tones to show up properly for now.
I apologize for this continuing issue, doubly so since it exists in GeeWiz 3 and I failed to test it properly. I've changed my mind on a root cause here, and I'm spending as much time as I can to rectify it once and for all. Please try the WORKAROUND to see if it restores all of the built-in tones as well as any that you have present on your SD card. Please let me know if after clearing that app's data you still do not see all of the built-in tones in Settings.
Ringtone issue is being tested today, after I dug in enough to figure out what was happening, I was able to find that it's a problem others have had and fixed. It also explains the occasional problems with Google Apps that access media databases. My hat's off to the EpicMTD team for posting a thorough explanation and making the fix public: The "workaround" I posted last night didn't actually work, it turned out to just cause temporary relief, the database would rather quickly get screwed up again.
Ringtones/Alarms/Notification Tones do not appear in Settings
Updated: The problem here is that the Media Scanner is deleting the media database any time it runs due to a change on the external SD card. As it turns out, this happens more than you might expect thanks to Google+. After discovering that the media database stays intact provided you do not install an SD card, and that it will be deleted if you insert one, I had enough information to head to Google and this is not an uncommon problem. The EpicMTD team provided the original solution, which has since been merged into Cyanogenmod (http://epiccm.blogspot.com/2012/03/details-on-disappearing-sd-media-issue.html). I've taken a look at the CM 10.1 baseline and am testing the changes. So far they look good and I expect to release a patch on 1/12. This also appears to resolve the previously listed issue "Google Apps may Force Close", which has been removed. Each of the Google Apps that were crashing access the media databases (Gallery, Music, Google+), which were being deleted/corrupted by the Media Scanner.
I'm going to look at the Wifi data being reported when it shouldn't be and try to duplicate the "Calcuating..." issue in Settings/Storage now that I have a 32GB SD card, in an attempt to include them in the 4.0.1 patch. If they aren't easy, 4.0.1 will include the ringtone fix and the new ICS Clock Daydream only
GeeWiz 4.0.1 Patch has been posted to the DOWNLOADS section:
GeeWiz 4.0.1 Patch (EDIFY Update-Zip)
- Addresses issue where ringtone/notification/alarm selection lists are emptied out and will only display the default values
- Addresses issue with certain Google Apps (Music/Gallery/Google+) Force Closing due to missing media database files
- Addresses issue where Settings/Data Usage is only reporting Wifi usage rather than reporting mobile usage with Wifi usage as an optional tab
- Adds "ICS Clock" Daydream that mimics Android 4.0/4.1 Desk Clock screensaver
http://www.mediafire.com/file/c9667m25u4z1j2c/geewiz-4.0.1-patch-01122013.zip
MD5: d0de81c75d53cc67dc759cdabf2f7bff
Hopefully this is the end of the disappearing ringtones. Let me know if you still continue to have issues, and I'll do what I can!
I really appreciate your great work on fascinate.
The fascinate is much more stable and power-saving with the kernel built on stock kernel source.
But I strongly recommand that you can reuse some kernel-independent packages(framework-base, settings, systemui,etc) source in CyanogenMod, which will be good for saving much time on development and avoiding some bug that CyanogenMod had fixed.
Thanks for your work again, and sorry for my bad English.
Installed 4.0 and the patch this morning. Looking good so far. Of all my devices, the Fascinate is the only one with the current version of Android on it, ever! You rock, thanks.
seriously, this rom looks freakin' sweet! it definitely makes me want to install it to test it all out! <--- in which I may very well do! I'm definitely kinda surprised that you wanted to update geewiz, but at the same time I'm glad to see a different rom out there that is pretty much stock AOSP, but with the fascinates stock flavors trickled into it as well
so as I dub my adieu, I just want to say thanks for an awesome creation and keep it up cause this is honestly the bees knees. :thumbup::thumbup::thumbup:
netqer said:
I really appreciate your great work on fascinate.
The fascinate is much more stable and power-saving with the kernel built on stock kernel source.
But I strongly recommand that you can reuse some kernel-independent packages(framework-base, settings, systemui,etc) source in CyanogenMod, which will be good for saving much time on development and avoiding some bug that CyanogenMod had fixed.
Thanks for your work again, and sorry for my bad English.
Click to expand...
Click to collapse
Thanks to you and everyone else as well for the kind comments! I'm very glad it's finding an audience ... it keeps me wanting to try and fix the things that still need to be fixed! :silly:
(This is where I get all long-winded, you can tune out now - LOL)
Early on I considered just doing another CM port, but figured there wouldn't be any value in that since jt1134 (and others!) does an excellent job of keeping the CM baseline working for the ol' Fascinate. The history here is that all I originally intended to do was what became "GeeWiz Media" (apologies for the crappy name - lol), so I could keep using my Fascinate around the house and in the car without service. I really like the basicness of my Galaxy Nexus, so that's what I shot for .. a "Nexus Fascinate", if you will. There were a few "must have" changes like the enhanced power button menu, but the general plan was to limit the number of AOSP changes to a minimum, and make sure they apply to both the Fascinate and the Galaxy Nexus.
In order to get things to work I've cherry-picked from CM, jt1134 and others more than a few times (and have made at least one truly useful contribution in return), but I've not had aspirations to stray far from AOSP. I know it's disappointing to some folks that it's so vanilla, and maybe once I run out of actual problems to try and solve I can tackle a few more aggressive enhancements, but I really don't want to steal features that define other people's work. I know the code is made public for a reason, but at some point I think it starts stepping on other people's toes as well as shows a lack of effort on my part
Great suggestion, though, and you're right ... it would save a ton of time! It just wouldn't feel right to me to use somebody else's baseline for anything more than a reference when I'm stuck
Updated and revised, 11-29-20
In this post I am presenting a way to slightly extend the practical range of the 8 gb Nook Tablet by using microG for Google Services Framework spoofing rather than the resource-hogging GApps. Although I have tested these ROMs thoroughly on the BNTV250a, they would all likely run just fine with GApps on the 16 gb model (I currently run AOSP 7.0 with microG on my 16 gb tablet), while only CM 11 runs acceptably on the 8 gb model with GApps. Let's get that simple setup out of the way first.
I selected the unofficial CM 11 ROM with the final security patches by Chris Hoffmann [https://www.mediafire.com/?gq1y21uz11lr1c0]. It is serviceable for me. The main drawback is the old WebView (which cannot be updated) resulting in the inability of browsers to display many sites properly, including the current default skin for XDA. Despite this, I've come to feel that it's perhaps the best option, with or without GApps. Installing this ROM is easy. Flash with the recovery listed in post #2, reboot, then flash a pico GApps package from Open GApps. To run the ROM without GApps, read on.
I made a quick tour of CM 12.1, CM 13, AOSP 6.0 and AOSP 7.0, and Lineage 14.1. In the following post I'll lay out some pros, cons and hints based on my experiences. I flashed each ROM several times, trying different things, building the system from scratch each time rather than restoring apps from backup. That gave me a chance to work with each OS and see how it would perform not only during setup, but also during a shakedown/tweaking phase. What I can say about all of these ROMs is that GApps effectively kills each and every one on the BNTV250a.
Life without GApps
I, of course, tried side-loading apps without GApps. Easy, right? I thought so until I came to a few that whined about requiring Google Play Services to run. Even mundane things like the NPR News app, my local newspaper and MX Player are "GSF dependent" (Google Services Framework). Then I tried another app that would not install at all. Turns out it did a license verification check (it's free!) and saw no Google anything, so forget it. This was sort of news to me I suppose because even my lowly NST had GApps installed once upon a time, so I never encountered this issue before. You can hunt around for apps elsewhere but if you pick up an app that happens to be featured in the PlayStore, you may be out of luck no matter where you got it from. Or maybe not.
There is a project called microG by XDA member @MaR-V-iN. It consists of a lightweight set of apps (two at minimum, a third if you want location services) which provide the needed authentication to Google servers and/or inquisitive apps. There is a catch: the ROM must support "signature spoofing".
These ROMs do not have that option. You can Google "signature spoofing" to read the pros and cons. This is just information. Caveat emptor, etc. There is an Xposed module called FakeGapps which enables signature spoofing. I tried this on a few ROMs and found it worked fine. At the time I started this there was no official Xposed update for Android 7.0 and as that was one of my targets, I started looking for something else [note: Xposed has since been updated to include Android 7.0 and beyond]. That led me to Tingle by XDA member @ale5000. This is a Python/ADB based method of automatically patching framework.jar to enable signature spoofing. This seemed to me a more direct and elegant approach. Although I was intimidated by it at first, I eventually just dove in. The only thing I didn't already have was Python and that was easy enough to install. The process is basically automatic once it gets going. Unfortunately it does not work for ROMs that are odexed or deodexed. The AOSP 7.0 ROM turned out to fall in that category. Xposed must be used there.
OK, what can all this do for you? It can get you a spoof of Google Services Framework without GApps. Period. There are a few simple additions to allow for location services. It used to be that you could also enable Calendar and Contacts syncing. No more. As for PlayStore access, this is possible running microG with CM 11, but not beyond. It's just too resource intensive. For ROMs beyond CM 11 I found the Aurora Store (F-Droid) to work OK, although not always in the same way. On some ROMs you can use the anonymous Aurora Store login, on others you need to supply a Google account (email). Trial and error.
The General Process
If you have never "flashed" anything before that you can talk about at work, then you need some basic instructions for creating an SD card that will allow you to try out these procedures. The excellent instructions by @digixmax here will get you started with the SD card. You need to follow steps 1-2 to prepare the card, although the version of TWRP you use will depend on the ROM you want to try out (see second post for links). Also, the ROM itself will vary (see second post for links) and you will not want GApps (unless you are just installing CM 11 with GApps). The remainder of the steps (3-10, skipping 9) also describe the general process of flashing a ROM (or other "flashable" files like Xposed, etc.) using the SD card.
1. Flash the ROM using an appropriate recovery (I have listed the ones I used in the following post)
2. First boot, enable root, USB debugging and ADB
EITHER
3. Connect tablet to PC via USB and access via ADB ("adb devices"--some of these ROMs require that you approve PC access to the tablet via ADB, so check the tablet screen to approve that option if needed)
4. Open a command window on the PC and navigate to your Python installation directory. Because I was not sure what I was doing I just dumped the entire contents of Tingle into the Python directory. That simplified path issues for me. Type "python main.py" and select option 1. Wait for the "all done", hit CTRL-c and kill ADB server. Disconnect tablet from USB and reboot.
OR
3. Flash appropriate Xposed for the OS; reboot
4. Install Xposed installer app and FakeGApps.apk; use Xposed installer app to enable FakeGapps (signature spoofing); reboot
5. Install root file manager of choice if desired (the CM stock file managers are totally capable of the following operations if given root access; the stock file explorers of the AOSP and Lineage ROMs may allow the same, although I have had mixed results. You can always install a root file manager via ADB before continuing if all else fails) A copy of ES File Explorer is attached below.
for CM 11 without GApps but with the PlayStore:
6. Move Phonesky.apk--i.e. the PlayStore-- (old, lightweight version from a KitKat ROM: http://www.mediafire.com/file/1c2f0n3k3cwsln7/Phonesky.apk/file) into /system/priv-app; set apk file permissions to rwx-r-r.
7. Move microG component apks into /system/priv-app; set apk file permissions to rw-r-r (you need a minimum of Services Core, Services Framework Proxy for this step)
8. Reboot
9. Check microG Settings to be sure spoofing is enabled and other permissions are given; set to enable Google device registration; add an account. This process can be slow. Be patient. If you end up at a black screen, reboot and try again or see if the account is already established.
10. Open the PlayStore. Do some searching. You want to give it time to auto-update (this process may be completely silent). Exit. Check Settings>Apps>Downloaded to see if PlayStore has shown up there. If it has, then it may be updated. You can check yourself to see if the version number is higher. If there is no update, access the PlayStore again and check again. Once you have an update, you're good to go.
OR, for ROMs beyond CM 11:
6. Use root file manager to create the folder "Phonesky" in /system/priv-app. Set folder permissions to rwx-rx-rx. Use root file manager to move "FakeStore" apk into /system/priv-app/Phonesky and set apk file permissions to rw-r-r.
7. Move microG component apks into /system/priv-app; set apk file permissions to rw-r-r (you need a minimum of Services Core, Services Framework Proxy for this step)
8. Reboot
9. Check microG Settings to be sure spoofing is enabled and other permissions are given.
It's a lot, but if I could do it many times over you could do it once
In the end you'll have a tablet spoofing Google Services Framework so most apps will run without whining, but without the crushing weight of the PlayStore or the full GApps.
Contacts and Location
Life without GApps doesn't mean you have to give up these services. Just keep in mind that running background services can compromise a system that is already on the edge.
I tested the instructions that follow on a BNTV250a, using the stock Contacts and Calendar apps.
1. Contacts
There are some places in "on-line land" that describe a method for enabling contacts sync. I have not found the various methods to work any longer. It is possible to sync Contacts using DavDroid. There is only one version that will run on CM 11 and the same app will run on the other ROMs as well (attached below). However, you are adding more overhead to a device that is already pushing the limits. In the end I opted to export my contacts in vcard format and read them in as a local file. The more socially active may find this unacceptable, but it works for me.
2. Location
To enable location you will need to install an app which coordinates WiFi triangulation (something usually handled by GApps). There are two possibilities. You can get a Unified NLP apk from the microG download page. After installing the app you can check your microG settings to see if everything is OK. Then you can check Settings>Location and set it up the way you want.
If you want to use Maps you will also need to flash a maps.zip file from microG. This contains a couple of library files for Maps. As far as the Maps app itself, I have never had good performance from any version of Google Maps on my devices--until now. That's because I went fishing for an older, less bloated version that would run on the BNTV250a. It works beautifully on all my devices from KitKat to Nougat and allows pre-cache of map areas which don't expire. I've attached a copy of the apk file below.
Email
The stock Email client works great (at least for GMail accounts) and looks a lot like GMail (no surprise there). If you have your heart set on GMail, version 4.5.2--from GApps for Jellybean--seems to run just fine with a footprint of about 11 MB. I've attached a copy below.
The ROMs
Updated and revised 2-5-23
Generally I disabled any stock stuff I could that I would not use. Anything past CM 11 has a maddening issue I call "peek-a-boo keyboard", most noticeable when using the browsers. The keyboard drops out while you are typing or simply refuses to open without a struggle. You can solve this problem in CM 12 and minimize it in CM 13 by installing Simple Keyboard.
CM 11 is beginning to show expired certificates and SSL issues. You can try replacing or adding new certificates, but it's not easy and you're left with warning artifacts in the status bar. Ditto with CM 12 and CM 13, but they are not nearly as bad--for now. The stock browsers, fortunately, allow you to "ignore" security warnings which makes browsing more pleasant. You may not feel that's a great idea, but the reality is that browsing is the Achilles Heel for all these ROMS, and it's worse the higher you go. The stock browsers may give the best overall performance, whatever their shortcomings.
Because of the SSL issues, I don't recommend CM 11 any longer unless you are not going to do much in the way of internet stuff.
Note: I have noticed that both my Nook Tablets (8 and 16 GB) run better if they've been on for a bit. If yours is cranky when it gets up in the morning, pouring coffee on it won't help, but a little siesta after boot may be just the thing
CM 11 (but with issues as described above)
https://www.mediafire.com/?gq1y21uz11lr1c0
Flashed with SD-based TWRP 2.8.6.0, enabled signature spoofing with Tingle
This is arguably the best choice for the BNTV250a if you want something other than the stock B&N ROM. It runs smoothly enough that you could even keep the PlayStore app on it and it would still behave reasonably. It's even better without it. The only drawback with this ROM is that Android Webview cannot be updated. This means that some websites will not display properly or may simply crash, regardless of what browser you choose to use. I found the antique stock browser to be surprisingly good, but Via also works well. Also, the SSL is in need of updating, so you will run into issues with some websites and apps like OverDrive.
The lesson that this ROM taught me is that these tablets are for casual use. You can't just load them up with apps and expect them to run well. Think about what you really would like to use the tablet for. Consider older versions of apps that will probably still have more features than you will ever want but are less taxing to the system. You can see from the attached screenshot how I eventually pared my choices down. I should probably pare it down even more. Most of the apps are older versions and I've kept the total count low, certainly less than on my 16 GB tablet and other devices. You don't want to exceed about half of the internal storage capacity.
CM 12.1 (potential WiFi issue as described below)
http://www.mediafire.com/file/7zxc2e...K6-acclaim.zip
Flashed with SD-based TWRP 2.8.6.0, enabled signature spoofing with Tingle
Edit 9-30-22: I recently booted this up to find that it would no longer connect to my fairly new ATT router. Puzzled, I took the tablet to my local library and had no difficulty connecting there (open network, though). Next I started restoring backups of each of the other ROMs in this list and each one had no trouble with WiFi at home. I installed a fresh copy of the CM 12.1 ROM. It also refused to connect to the router. I scrounged around the web and found two more versions of CM 12.1. Neither would connect to my router. So...I'm not sure if there is some additional security ATT has built into their WPA2 authentication or what, but I mention this just to alert you that this might be a problem. I was even able to connect to a mobile hotspot generated by my Windows 10 machine (password needed). Why this new(?) problem for the 12.1 ROM only, I have no idea.
Before you start installing apps the behavior is sprightly, even on the BNTV250a. As the internal space decreases and RAM use increases, it becomes a little less so. Even so, when running well I think it comes close to CM 11 (with GApps), albeit with more lag.
The stock browser seems like the best bet (I tried many), though it can be slow.
For me this ROM has two major issues. When it is unhappy, it will simply shut down the tablet, literally turning it off. This used to sometimes happen when I ran it on my 16 GB model, so it's not the fault of the BNTV250a. The other issue is problems for apps writing to the external SD card. For a tablet with precious little internal space, you just don't want apps downloading into internal space or storing lots of data there. There is an edit to the file /system/etc/permissions/platform.xml which corrects this issue for some apps. Find the section of platform.xml below and add the last line:
Code:
<permission name=”android.permission.WRITE_EXTERNAL_STORAGE” >
<group gid=”sdcard_r” />
<group gid=”sdcard_rw” />
<group gid=”media_rw” />
This change enabled OverDrive and Kodi, for example, to download files to the external SD card. It might work for others.
Not as fluid as CM 11, but WebView issues are gone and you can access most up-to-date content (if slowly).
CM 13
https://archive.org/download/cmarchive_snapshots/cm-13.0-20160819-SNAPSHOT-ZNH5YAO0IN-acclaim.zip
Flashed with SD-based TWRP 2.8.6.0, enabled signature spoofing with Tingle
Never having tried this ROM on my 16 GB tablet, I was actually pleasantly surprised by its behavior on the BNTV250a. There's a funny WiFi thing where if you leave WiFi on when you shut down and then boot up again, it will not automatically connect (unless the lockscreen has come on, which is pretty fast after booting, so no biggie). Otherwise it's pretty much like CM 12 although maybe a little more stable--if you don't overdo it. The Sound Recorder app is somehow broken on the CM 13 ROM. If this is something you'd like, you can replace the broken version in /system/app/SoundRecorder with the one attached below. Make sure the permissions are rw-r-r and reboot.
Some apps can't write to the SD card (as portable storage). Kodi is an example, I'm sorry to say. I've tried many "solutions" to this problem but the only one that worked for me is to edit /data/system/packages.xml, adding the permission for each specific app you want. This is a long file and I did this using the editor from the CM File Manager. There are probably easier ways. After locating the app you want in the xml file, add this line anywhere between the <perms> and </perms> tags:
Code:
<item name="android.permission.WRITE_MEDIA_STORAGE" granted="true" flags="0" />
This change will be overwritten if the app updates, so you might want to keep that in mind.
This is the ROM I've settled on for my BNTV250a (screenshot of home screen below)
AOSP 6.01 "Marshmallow"
Box
notredame.app.box.com
(you want aosp_acclaim-ota-MOB30Z.160820.zip)
Flashed with emmc-based TWRP 3.0.2-0, enabled signature spoofing with Tingle
This is one of the ROMs built by @amaces. The AOSP builds are very lean compared to CM ROMs so I was hoping this might perform somewhat better than CM 13. But I don't think it does.
The first big hurdle is enabling root. My thanks to @digixmax for pointing out the right tool. After first boot (or maybe even before, but I did it after) you need to flash UPDATE-SuperSU-v2.46.zip. Works perfectly.
The stock launcher is, well, funky. I replaced it with Nova Launcher but after installing a few other apps it was clear the system was under great stress. Lots of black screens and crashes. Not a good option for the BNTV250a.
AOSP 7.0
https://www.mediafire.com/?5vcw8l603d3r5sc
Flashed with emmc-based TWRP 3.0.2-0, enabled signature spoofing with Xposed
This is another ROM by @amaces and what I run on my 16 GB tablet. On that device it is virtually flawless. I really wanted to say the same for the BNTV250a, but I can't.
Enabling root for the ROM is achieved with Magisk.
The ROM appears to be odexed to Tingle and so you must flash the correct Xposed (for 7.0 and Magisk) and install the installer app along with the FakeGapps app as described in the previous post.
The stock launcher is pitiful and you need to install a root file manager to get anything done. The system is laggy and video is not smooth. Not even a potential option for the BNTV250a.
Lineage 14.1
Box
notredame.app.box.com
(there are many versions of this ROM. The link takes you to the "obsolete" folder where you need to hunt down lnos_acclaim-ota-NJH47F.180211.zip. This seems to be the only version without the shut-down bug)
Edit 2-5-23: Well...no, it does not have the classic shut-down bug (tablet reboots right after it "shuts down"). Instead, it often shuts down just fine, but occasionally locks up during shut down and has to be forced off with the power button.
Flashed with emmc-based TWRP 3.0.2-0, enabled signature spoofing with Tingle
This is a third ROM built by @amaces (his most recent for the NT). I didn't have much hope for this because if 7.0 was an issue, I didn't expect 7.1 to perform well.
The only native root capability is for ADB. To enable full root, you need to flash addonsu-14.1-arm.zip (attached below). I did that after first boot but perhaps it can be done along with the ROM.
Not surprisingly the ROM has the feel of CM. There appears to be a file manager but it is only a partial reflection of the native file explorer and is useless for the manipulations that need to be done, so you need to adb install a root file manager as described in the previous post.
The stock browser is complete rubbish. It looks to be Gello(?) but it is the most infuriating collection of electrons I have ever encountered. There are no navigational buttons, no bookmark button--no buttons at all! I really tried. I used gestures (some rude), I tried magic words (many of which do not appear in children's books). Nada. When I finally managed to reach my test site it was like wading through, well, Jello! So....attached below is the nice lightweight stock browser from AOSP 7.0. Navigate to /system/app/Browser and there you will find Browser2.apk. Rename it to something else and copy in the Browser2.apk attached below, setting file permissions to rwx-r-r. Reboot. If you are successful, you can delete the old, useless browser apk. To enable bookmarks, navigate to /system/app/BookmarkProvider and inside you will find the apk file. Tap to install. I don't know why this needs to be done, but it does even on AOSP 7.0. Reboot and you've got a functioning browser (rife with "peek-a-boo keyboard")
The ROM hates Kodi, crashing constantly. Video from other apps is not smooth. Not a viable choice for the BNTV250a.
For a lark I tried it on the 16 GB model and it's actually not bad, but then I saw that embedded browser videos (like YouTube, for example) were funky colors, so... It may be that later versions corrected this, but those likely have the shut-down bug. In any event, a terrible choice for the 8 GB model.
Took a bit of trial and error to get the perfect version of playstore to not give an error, but I got it working. Thank you a lot for this write-up!
Yes I am breathing life back into a BN Nook in 2020 (quarantine will do funny things to a guy). Thanks for the comprehensive guide. I had installed CM11 years ago and it kinda sucks as is, so looking forward to seeing how this shakes out. I have to re-educate myself on all the various steps like adb, installing root file manager etc, it has been a long while since I played around with android's innards!
denmalley said:
Yes I am breathing life back into a BN Nook in 2020 (quarantine will do funny things to a guy). Thanks for the comprehensive guide. I had installed CM11 years ago and it kinda sucks as is, so looking forward to seeing how this shakes out. I have to re-educate myself on all the various steps like adb, installing root file manager etc, it has been a long while since I played around with android's innards!
Click to expand...
Click to collapse
While you're becoming familiar again with the procedures, give me a day or two to update the post. I recently redid my BNTV250a with CM 13 to try some things and then finally went back to CM 11 using the MicroG components rather than GApps. I'm really happy with it, but I have to say that the tablet (just like my BNTV250 with AOSP 7) behaves better if it's been on for awhile. It can be really cranky if you try to start using it right after boot.
So I'll update the post title to include CM 11 and add some details about CM 11 to the second post in a few days.
Hey thanks for keeping up with this thread! I installed CM11 as suggested but hitting a snag with tingle. I just dumped the tingl directory into the python folder as you did and ran main.py. This was the output.
C:\Python27>python main.py
MENU
1 - Patch file from a device (adb)
2 - Patch file from the input folder
> 1 adb
ERROR: Missing adb => ['adb']
NOTE: Only one binary per type is required
ERROR CODE: 65
Not sure what I'm doing wrong
denmalley said:
Hey thanks for keeping up with this thread! I installed CM11 as suggested but hitting a snag with tingle. I just dumped the tingl directory into the python folder as you did and ran main.py. This was the output.
C:\Python27>python main.py
MENU
1 - Patch file from a device (adb)
2 - Patch file from the input folder
> 1 adb
ERROR: Missing adb => ['adb']
NOTE: Only one binary per type is required
ERROR CODE: 65
Not sure what I'm doing wrong
Click to expand...
Click to collapse
I don't remember seeing the "adb" after "> 1", but I may just not remember. So, just in case and to be really clear (in case I wasn't before):
1. I assume you have adb working on your PC or you wouldn't have gotten to the Python step. Did you ever set the PATH for adb? I confess I never bothered until I tried this procedure. But you have to be able to access adb from the Python folder for this to work. If you're not sure, just cd to the Python folder and try starting adb. If it doesn't work then the PATH needs to be set. Here's a good description for Windows (scroll down to "Step 2"): https://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
2. When I said I dumped the contents of Tingle into the Python folder, I meant that literally. There is no "Tingle" folder in my Python folder,but there are a bunch of extra files that are "Tingle". Just want to be sure.
Those are my only ideas at present. I hope one of them does the trick!
Ah yes path variable did the trick! On to the next steps, I'll keep you posted!
Ok, now i am at the play store step - keep getting error "unfortunately google play store has stopped." Over and over again when attempting to open. After reboot too.
denmalley said:
Ok, now i am at the play store step - keep getting error "unfortunately google play store has stopped." Over and over again when attempting to open. After reboot too.
Click to expand...
Click to collapse
Did you
1. Check microG settings to be sure everything is OK?
2. Sign in to your Google account from the microG settings (add account)?
3. Then try the PlayStore (check permissions on Phonesky folder and app)
One part I'm not clear on. I placed all of the apks where you say to (steps 6-8), once I reboot, is play store supposed to just appear? When I do self-check in microg everything is checked except playstore and the bottom two (location). I got the impression from your instructions that I'm supposed to wait for some background processes to appear.
denmalley said:
One part I'm not clear on. I placed all of the apks where you say to (steps 6-8), once I reboot, is play store supposed to just appear? When I do self-check in microg everything is checked except playstore and the bottom two (location). I got the impression from your instructions that I'm supposed to wait for some background processes to appear.
Click to expand...
Click to collapse
Yes, the PlayStore icon should appear--admittedly a very old and funky one with this old version.
The Playstore automatically updates. I wish it did not, but there is no way to stop it. But to have that happen you have to access the Playstore at least once, maybe even download an app, and leave wifi on awhile.
On my main microG settings screen I show Google device registration ON. On the self-check screen, everything is checked except the last box. I have the location stuff installed.
So if PlayStore is unchecked, something is not right. Perhaps the app got corrupted when I uploaded it. I am shut down right now but can reup tomorrow. Or you can just get another app from Apkpure or similar. I used to use something around 8.02 to get started.
I am very much stuck at this point (unless I guess I continue with regular gapps which goes against the whole point of this approach). I tried nuking and redoing the whole process with the same result. Attached screenshots of all relevant screens to show permissions/settings/etc.
Also I can't find a "phonesky.apk" anywhere, only full-blown google store apks which are much larger than the phonesky.apk you provided and so I must assume are not the correct thing.
denmalley said:
I am very much stuck at this point (unless I guess I continue with regular gapps which goes against the whole point of this approach). I tried nuking and redoing the whole process with the same result. Attached screenshots of all relevant screens to show permissions/settings/etc.
Also I can't find a "phonesky.apk" anywhere, only full-blown google store apks which are much larger than the phonesky.apk you provided and so I must assume are not the correct thing.
Click to expand...
Click to collapse
Phonesky=PlayStore, just renamed--microG expects to see Phonesky
Something is not right with the app. I have to run, but here is a link to v. 8.02 which I have used in the past:
https://www.apkmirror.com/apk/google-inc/google-play-store/google-play-store-8-0-23-release/
Rename to Phonesky before using. It will be a little more cranky but it will work to get you going. I hope.
Edit: or, if you prefer, go to OpenGapps and download a KitKat pico GApps. Extract from that zip the Phonesky app and use it.
Edit, Edit: yeah, I tried reupping a copy of the Phonesky app but when I downloaded it the file size did not match. So I changed the first post and inserted a link to a copy on my mediafire account. That downloads with the right file size.
Well, I think I'm giving up. I've redone the process three times now. I used your new Phonesky.apk this last time and I still can't get the play store to show up. Only other thing I can think to ask - if I add a google account through microg settings, is it supposed to change to indicate that account is now added? Because if I go in there it will still say "add acount" even though I can see in the regular settings under accounts that a google account is present.
edit
The only other thing I haven't yet tried is redownloading everything and maybe even using a different PC. Ah heck who am I kidding, like I've got anything better to do. I'll keep cracking at it.
denmalley said:
Well, I think I'm giving up. I've redone the process three times now. I used your new Phonesky.apk this last time and I still can't get the play store to show up. Only other thing I can think to ask - if I add a google account through microg settings, is it supposed to change to indicate that account is now added? Because if I go in there it will still say "add acount" even though I can see in the regular settings under accounts that a google account is present.
Click to expand...
Click to collapse
I'm really baffled by this behavior. When you add a Google account via microG nothing changes on the microG settings page, but the account should show up in the CM11 settings under "accounts".
When you prepare the system for flashing, do you do an Advanced Wipe? I'm a little AR about this sort of thing, especially as my devices have been flashed with different OS's many times. I start with an Advanced Wipe, clearing out everything except, of course, the microSD card, and then I follow that by a regular wipe. Then I start flashing.
If you are still having trouble, let me know and I'll wipe my current system (I have a backup) and start again from scratch, downloading copies of the files I have posted to see if I can duplicate what is happening to you. Maybe Google has changed something in the time since I did my newest configuration and the microG folks have not caught up with it yet. This appears to be true for Contacts because I cannot get them to sync up or even see my Google contacts. This was not the case in the past. There is chatter about it on the microG site, but none of the "solutions" go anything beyond what I have already related and some of the conclusions are like "and it just started working..."
I did not do the advanced wipe, so let me try that. I'm also going to redownload everything and give it another go. No need to wipe your device just yet - you've already done WAY more than I expected to help! I will do this over the next few days and keep you posted.
Well I tried six different ways, full wipe, change the "group" set for the group permissions to "root" (it had been set to sdcard), redownloaded every last bit of software used in this process, used a different computer, etc etc etc. Nothing is working. Still no play store. Everything else seems to be fine except that.
So anyway, I finally just did a full wipe, flashed the CM11 unofficial that you provided in second post, and grabbed a kk gapps package and flashed that. Switched from trebuchet to nova and I've got a tablet I can live with! Working much better then the cm10 rom I had on there before (like swipe to unlock screen, wait 5 seconds....touch app drawer, wait 5-10 seconds....touch an app, wait 30 seconds....slooooooow).
Thanks for pushing me along in this direction, before I started back into this process I had completely forgotten all the little intricacies which would have gotten me hung up and possibly bricked. And all the of the other guides out there have broken links, outdated info, etc. So I'm happy with where I landed and very much appreciate the help, even if we didn't quite get there with your proposed improvements! I now have a capable e-book, backup songbook for gigs, and a spare digital mixer controller that I can clean up the personal stuff from and hand off to an assistant.
denmalley said:
Thanks for pushing me along in this direction, before I started back into this process I had completely forgotten all the little intricacies which would have gotten me hung up and possibly bricked. And all the of the other guides out there have broken links, outdated info, etc. So I'm happy with where I landed and very much appreciate the help, even if we didn't quite get there with your proposed improvements! I now have a capable e-book, backup songbook for gigs, and a spare digital mixer controller that I can clean up the personal stuff from and hand off to an assistant.
Click to expand...
Click to collapse
I'm glad you reached a point where you feel good about the outcome but sorry that you had to waste so much time.
I will run through the procedure again in the next few days. Maybe there's something that got garbled in the updating of the post. In any case I'd feel better if my instructions actually achieved the intended result.
nmyshkin said:
I will run through the procedure again in the next few days. Maybe there's something that got garbled in the updating of the post. In any case I'd feel better if my instructions actually achieved the intended result.
Click to expand...
Click to collapse
Well.....I'm not sure how the error crept in, but it looks like the creation of the Phonesky folder was the issue. This is needed for ROMs beyond CM11, but there are no folders in /system/app or /system/priv-app for CM11. Thus for CM11 only, the files like Phonesky.apk are simply dropped into /system/priv-app and the permissions set as described, Then everything works as it should.
I've corrected the instructions. My apologies.