Related
Hi.
I'm running SyndicateROM Frozen 1.1.1, and I've observed several bugs. I need to know if the bugs are the fault of the ROM (and thus something I should take up with the ACS developers) or if they're my fault due to something I'm doing wrong.
1) I use folders on my LauncherPro* homescreens to organize apps. For this example, I'll use my Games folder. In it, all the games except 1 are installed onto my microSD card. After I drag the icons to the folder the first time, they are fine. However, after a reboot, the icons of the apps installed to my microSD card that are in folders change to the generic Android green/white icon. The apps still load properly, and the icons appear fine in the App drawer.
*LauncherPro is included as the only homescreen in this ROM.
2) I'm having an odd issue with Plants vs. Zombies. It loads to the main screen, and I can manage the player names, but after I click to start the adventure, it locks up with the Adventure button depressed. The main screen music also dies. No FC/wait dialog appears. I have to press the Home button to get out of it. PvZ is unplayable in this condition. Rebooting does not help, nor does formatting /cache or Dalvik-cache in custom recovery.
3) JuiceDefender Ultimate tells me in the log that it cannot toggle 2G/3G data, and that this is likely to be a kernel issue. As far as I know, this reduces the effectiveness of JD.
4) In ClockwodMod Recovery 3.0.0.6, I cannot mount my microSD card for the PC to read/write it. I get "E:Unable to open ums lunfile (no such file or directory)". I've seen posts that indicate this is a bug that was corrected in later versions, but I don't know if the custom ROM I am running is compatible with later versions,or where to find later versions. EDIT: I found CWM 3.0.2.5, and flashed it. It still reports the same error when attempting mount my microSD card for my PC to work with.
5) When I connect the phone's cable to my PC and get the the "Charging/Mass Storage/Tethered" popup and click Mass Storage, and then click "Turn On" at the next screen, it appears to work fine, except that my PC shows no new removable media drives. Sometimes, even though I touched the "Turn On" button, nothing happens. The button does not turn into a spinning wait indicator, nothing.
6) I found a post (that I've since lost track of) that purported to provide instructions to see if journaling was enabled. (I'm already formatted as EXT4). The instructions errored out, apparently because I have the wrong version of tune2fs. I'm not sure how to copy the correct version over, so I flashed the "Journaling On" zip shortly after I re-flashed this ROM. Does EXT4 and journaling stick between ROM re-flashes?
SweetBearCub said:
Hi.
I'm running SyndicateROM Frozen 1.1.1, and I've observed several bugs. I need to know if the bugs are the fault of the ROM (and thus something I should take up with the ACS developers) or if they're my fault due to something I'm doing wrong.
1) I use folders on my LauncherPro* homescreens to organize apps. For this example, I'll use my Games folder. In it, all the games except 1 are installed onto my microSD card. After I drag the icons to the folder the first time, they are fine. However, after a reboot, the icons of the apps installed to my microSD card that are in folders change to the generic Android green/white icon. The apps still load properly, and the icons appear fine in the App drawer.
*LauncherPro is included as the only homescreen in this ROM.
2) I'm having an odd issue with Plants vs. Zombies. It loads to the main screen, and I can manage the player names, but after I click to start the adventure, it locks up with the Adventure button depressed. The main screen music also dies. No FC/wait dialog appears. I have to press the Home button to get out of it. PvZ is unplayable in this condition. Rebooting does not help, nor does formatting /cache or Dalvik-cache in custom recovery.
3) JuiceDefender Ultimate tells me in the log that it cannot toggle 2G/3G data, and that this is likely to be a kernel issue. As far as I know, this reduces the effectiveness of JD.
4) In ClockwodMod Recovery 3.0.0.6, I cannot mount my microSD card for the PC to read/write it. I get "E:Unable to open ums lunfile (no such file or directory)". I've seen posts that indicate this is a bug that was corrected in later versions, but I don't know if the custom ROM I am running is compatible with later versions,or where to find later versions. EDIT: I found CWM 3.0.2.5, and flashed it. It still reports the same error when attempting mount my microSD card for my PC to work with.
5) When I connect the phone's cable to my PC and get the the "Charging/Mass Storage/Tethered" popup and click Mass Storage, and then click "Turn On" at the next screen, it appears to work fine, except that my PC shows no new removable media drives. Sometimes, even though I touched the "Turn On" button, nothing happens. The button does not turn into a spinning wait indicator, nothing.
6) I found a post (that I've since lost track of) that purported to provide instructions to see if journaling was enabled. (I'm already formatted as EXT4). The instructions errored out, apparently because I have the wrong version of tune2fs. I'm not sure how to copy the correct version over, so I flashed the "Journaling On" zip shortly after I re-flashed this ROM. Does EXT4 and journaling stick between ROM re-flashes?
Click to expand...
Click to collapse
OK can only answer some of these. I heard Launcher Pro can take a little while to read icons from the sd card. You may want to download and try Zeam launcher.
The Plants v Zombies may be a result of overclocking/undervolting. Try it again with no undervolting and your speed set to 1Ghz max and 200 Mhz min.
Not sure why you are mounting the sd card in clockwork. Sounds like either your cable is flaky or you need to reinstall the Samsung drivers to connect your USB. Also try different USB ports and turn USB debugging on. I had to reinstall the drivers for each port on my laptop as it would only recognize my phone in one of them originally.
No, journaling does not carry through other ROM flashes. If you flash a no-journaling ROM, you will have no journal unless you turn it back on. Some can be turned on simply be making a nand backup then immediately restoring it. Others work fine with the journal on flash. And some are more special and need a specific script like Bonsai.
Hope some of this helps.
SweetBearCub said:
Hi.
I'm running SyndicateROM Frozen 1.1.1, and I've observed several bugs. I need to know if the bugs are the fault of the ROM (and thus something I should take up with the ACS developers) or if they're my fault due to something I'm doing wrong.
1) I use folders on my LauncherPro* homescreens to organize apps. For this example, I'll use my Games folder. In it, all the games except 1 are installed onto my microSD card. After I drag the icons to the folder the first time, they are fine. However, after a reboot, the icons of the apps installed to my microSD card that are in folders change to the generic Android green/white icon. The apps still load properly, and the icons appear fine in the App drawer.
*LauncherPro is included as the only homescreen in this ROM.
2) I'm having an odd issue with Plants vs. Zombies. It loads to the main screen, and I can manage the player names, but after I click to start the adventure, it locks up with the Adventure button depressed. The main screen music also dies. No FC/wait dialog appears. I have to press the Home button to get out of it. PvZ is unplayable in this condition. Rebooting does not help, nor does formatting /cache or Dalvik-cache in custom recovery.
3) JuiceDefender Ultimate tells me in the log that it cannot toggle 2G/3G data, and that this is likely to be a kernel issue. As far as I know, this reduces the effectiveness of JD.
4) In ClockwodMod Recovery 3.0.0.6, I cannot mount my microSD card for the PC to read/write it. I get "E:Unable to open ums lunfile (no such file or directory)". I've seen posts that indicate this is a bug that was corrected in later versions, but I don't know if the custom ROM I am running is compatible with later versions,or where to find later versions. EDIT: I found CWM 3.0.2.5, and flashed it. It still reports the same error when attempting mount my microSD card for my PC to work with.
5) When I connect the phone's cable to my PC and get the the "Charging/Mass Storage/Tethered" popup and click Mass Storage, and then click "Turn On" at the next screen, it appears to work fine, except that my PC shows no new removable media drives. Sometimes, even though I touched the "Turn On" button, nothing happens. The button does not turn into a spinning wait indicator, nothing.
6) I found a post (that I've since lost track of) that purported to provide instructions to see if journaling was enabled. (I'm already formatted as EXT4). The instructions errored out, apparently because I have the wrong version of tune2fs. I'm not sure how to copy the correct version over, so I flashed the "Journaling On" zip shortly after I re-flashed this ROM. Does EXT4 and journaling stick between ROM re-flashes?
Click to expand...
Click to collapse
1) you can get a different launcher from the market. I've never had any luck with pushing apps to sd.
2) that's a issue with the game. Try changing your max and min cpu.clocks. If you uved you may be to low.
3)jd is a pos and you don't need it. I go on average of 12-16hrs a day with 3+ hours of screen on. And a synce interval of every hour
4) no versions of cwm on the epic has allowed you to mount your sd to pc for the epic. Cwm was ported to the epic and not created by koush him self so some things are broken.
5) try a different cable and usb ports. This is a known problem even while on a stock rom
6) yes it sticks unless the rom your flashing changes it.
Sent from my SPH-D700 using Tapatalk
Thanks Mystery for validating my advice...LOL. Would like to see you around here more.
cwm 3.1.0.1 allows mounting the sd card to pc in recovery..
chris41g said:
cwm 3.1.0.1 allows mounting the sd card to pc in recovery..
Click to expand...
Click to collapse
I forgot they fixed that. But anything before that don't allow this
Sent from my SPH-D700 using Tapatalk
kennyglass123 said:
Thanks Mystery for validating my advice...LOL. Would like to see you around here more.
Click to expand...
Click to collapse
I'm knee deep on working on sfr1.2
Sent from my SPH-D700 using Tapatalk
Hi All,
I'm new here but have been reading the threads since I got a Nook Color last month.
I'm booting from a 16GB microSD card: [CM7.2-RC0] MiRaGe - KANG build of CyanogenMod ("encore_CM72-MiRaGe-12122011") and also installed "gapps-gb-20110828-signed"
I ran the Battery Calibration tool just yesterday when it was plugged in and at 100%
I installed the Nook Color USB Mass Storage utility so that I could access the SD card from my computer
I also followed the thread's advice on installing V6 Supercharger (http://forum.xda-developers.com/showthread.php?t=1344873):
Nook Color with its large kernel with many features consumes the RAM rapidly and low memory becomes an issue where V6 Supercharger becomes useful.
Here is how I install, it takes only one minute.
- Download update 8 to sdcard root directory.
- Start Terminal Emulator and do the followings
- su
- cd /sdcard
- sh V6*
- choose option 0 (fastest scroll)
- choose 9
- choose option 16 to reboot
I have a couple questions that I can't ask in the dev threads since I just registered here.
How do you check if V6 Supercharger is working? I didn't install BusyBox or Script Manager like the original V6 Supercharger thread suggested...so is there a way to do this through the Terminal Emulator?
What do you recommend overclocking your CPU settings in CyanogenMod settings to? I have mine currently set to Conservative, Min: 300 MHz, Max: 1100 MHz, and Set on boot. Would 1200 MHz be pushing it too much?
I've read some questions and threads on here regarding the Wi-Fi turning off when it goes to sleep. When you press the side power button to turn off the screen, is that also putting the device to sleep? Is there a solution to the problem of the Wi-Fi turning off on its own when the screen is off?
Thanks in advance to any advice or answers! And of course, if you have any suggestions on other things I should be installing/uninstalling I'd greatly appreciate it!
AngelWings8 said:
I have a couple questions that I can't ask in the dev threads since I just registered here.
How do you check if V6 Supercharger is working? I didn't install BusyBox or Script Manager like the original V6 Supercharger thread suggested...so is there a way to do this through the Terminal Emulator?
What do you recommend overclocking your CPU settings in CyanogenMod settings to? I have mine currently set to Conservative, Min: 300 MHz, Max: 1100 MHz, and Set on boot. Would 1200 MHz be pushing it too much?
I've read some questions and threads on here regarding the Wi-Fi turning off when it goes to sleep. When you press the side power button to turn off the screen, is that also putting the device to sleep? Is there a solution to the problem of the Wi-Fi turning off on its own when the screen is off?
Click to expand...
Click to collapse
1. Open your app drawer, flick the screen, if it scrolls instead of stuttering then V6 is working.
2. OC as much or as little as you want. 1200 is safe but some people say that the increased battery drain isn't worth the slight increase in speed. You have to decide for yourself.
3. Yes, that is putting the device to sleep, yes, that will turn off your wifi. Most people prefer sleep to just screen off because it saves your battery. The old CM7.0.3 and earlier didn't have sleep mode and you lost 1-3% of battery per hour of standby. If you're ok with that then:
wireless & network settings > wi-fi settings > menu > advanced > wi-fi sleep policy>never
Thanks a bunch! I was wondering why there wasn't an "Advanced" option when I went to Wi-Fi settings...didn't even think to press the menu button! I chose to set the sleep policy to "Never when plugged in" and we'll see if that works for me. Is the default "When screen turns off"?
yup, it's been the default on every android device i've used. It allows you to put your device to sleep and then turn it back on when you need it without having to wait for android to boot. I can tell when an app kept my nook from sleeping because my battery is dead.
I installed the Nook Color USB Mass Storage utility so that I could access the SD card from my computer
Click to expand...
Click to collapse
I don't think you (we) need this step since I believe the feature has been integrated into the latest CM7 builds, assuming MiRaGe the same.
1. Open your app drawer, flick the screen, if it scrolls instead of stuttering then V6 is working.
Click to expand...
Click to collapse
Without even installing V6 Supercharger, I don't believe that I ever experience the stuttering. If that's the case, how do I know the V6 script is working/running/better performance?
votinh said:
Without even installing V6 Supercharger, I don't believe that I ever experience the stuttering. If that's the case, how do I know the V6 script is working/running/better performance?
Click to expand...
Click to collapse
You can tell it's installed Ok by running it again and using option 1 to show the status.
Not so easy to tell its immediate benefit as its real job is trying to ensure that the memory is kept free, so you have to compare operation over time as more apps get used / loaded.
You know, I'm not sure if I ever experienced the stuttering either. I'll have to check later today.
If I just used the Terminal Emulator, would I essentially do these steps?
- su
- cd /sdcard
- sh V6*
- choose option 0 (fastest scroll)
- choose 1 (to show status)
- choose option 16 to reboot
Also, just want to confirm that you need to keep the V6 file in the sdcard root directory right? I'm assuming if you ever delete or move the V6 file, V6 Supercharger would stop working?
By definition, "root directory" of the bootable CM7 uSD card is the one that has 117MB where ROM/GApp zip files used to be. If that, I don't believe that we (or NC) can access that partition. If it does, I want to know too.
With CM7 runs off eMMC, root directory of "normal" uSD card is ......... ehh, not in any sub-folder.
Can someone who actually do run V6 script chip in for some info?
Big thanks
Oh I'm sorry, when I wrote "sdcard root directory", I mean the root directory of what you can access when you plug it in via USB and not the partition where you're booting CM7 from. It's essentially where I save all my folders of wallpapers/music/videos/etc.
AngelWings8 said:
Oh I'm sorry, when I wrote "sdcard root directory", I mean the root directory of what you can access when you plug it in via USB and not the partition where you're booting CM7 from. It's essentially where I save all my folders of wallpapers/music/videos/etc.
Click to expand...
Click to collapse
Oh, ok.
Did you run the script yet? How was it?
No offense to the person that suggested checking V6 by flicking the app drawer, but there are a couple more reliable options.
I am no expert, by any means, but from looking over the program, it looks like all it really does is prioritize your apps by whether they are foreground or back, a launcher or hidden and so on, then allocate memory to the apps following that priority. I think any response check would wholly depend on how many apps you have running (or being killed by the V6 task killer)
Either way, even if it turns out that I wholly misunderstood the program, I can tell you how to see if it is installed and running for sure.
This will work if you have already installed the V6 or not. the following are directions for terminals, if you are running the dev's Scripter app, I would imagine it is similar, if not automatic.
Open a terminal.
su
cd sdcard/
sh V6*
the menu then scrolls. option 0 is often recommended here, but that is just a value for the scrolling speed of theV6 script itself. you can increase this number if you errant to spend a little time looking over what you're running.
f you think you have already ran the V6 look below the 17 options to current minfrees. If you want option 9 (Mirage Kang's recommendation) the current minfrees should read 6, 12, 75,100,125,150 mb. if it does, then you are supercharged. if not, go ahead and select option 9.
Now before you reboot, I would recommend that you run option 15 if you are not using Scripter. that will run V6 through the terminal emulator. That way, should you ever want to check your values or mess with the options, you can open terminal, su, then bash V6, and it will run.
Even if you don't think you will ever want to readjust the supercharger again, it had the added benefit of yelling you your "installation was INCREDIBLY SUCCESSFUL" which is bound to make you feel supercharged.
Run option 16 to reboot and now you can feel secure, without relying on a subjective flick of the app drawer.
Thanks everyone! I'm going to try uninstalling the USB Mass Storage app I downloaded then, if I don't actually need it with the CM7.2 version.
I did run Terminal Emulator to see what the minfrees were and it was the same as option 9. I didn't even think of running option 15, but I've done so now. After I rebooted, I opened up the Terminal Emulator again and typed "su" and then "bash V6" and it says "bash: V6: No such file or directory". Am I doing something incredibly stupid or wrong?
Also, do I have to leave the V6 txt file on the sdcard or can you delete it after you've run it?
I would bet it was a problem with case. bash v6 and bash V6 are two different things. Capital V should fix the issue.
Save the txt file, it is the actual script that is being ran. Without it, nothing happens.
I used bash V6 (and tried bash v6 just to see if anything would happen) and I got the same message. I thought maybe I just didn't do it right first time around, so I went back in, checked the minfrees and entered option 15 and then 16 to reboot, but when it did, it booted to the stock Nook Color OS. I just shut down and turned it back on and it went into Cyanogenmod with no problem...but is that strange that it didn't boot into CM? And once I got into CM again, I checked the overclock settings and it was back down to 800 GHz (even though I set it on boot at 1200 GHz).
votinh said:
By definition, "root directory" of the bootable CM7 uSD card is the one that has 117MB where ROM/GApp zip files used to be. If that, I don't believe that we (or NC) can access that partition. If it does, I want to know too.
With CM7 runs off eMMC, root directory of "normal" uSD card is ......... ehh, not in any sub-folder.
Can someone who actually do run V6 script chip in for some info?
Big thanks
Click to expand...
Click to collapse
That's a partition, not a directory. Every partition has a separate root directory.
With emmc, it's simpler because there's only one partition on the sd card so there's only one root directory. You can copy it over using usb or a sd card reader and it'll end up in the same place.
If you are running off the uSD, transferring files via USB places them on the "SDcard" partition on the uSD. That way, CF3D can find the files.
**I have a ton of apps, which may be the cause of my app drawer stuttering on flick (where you try to swipe to the bottom of your app list in one flick).
Thanks for all the useful replies! I uninstalled Nook Color USB Mass Storage app, and it seems to be working fine!
I saw that there is a new build for [CM7.2-RC0] MiRaGe - KANG and was wondering if you guys could kind of walk me through doing my first update. I downloaded both of these files listed in his first post:
- ROM - 01132012 build: MD5sum: 41676325569e773340378ba886dd6bf6
- transparency theme with circular battery indicator for 01132012 build. MD5sum: 9fb6a03e91f01c162a2f8f37cfe8ac77 Flash this theme after booting once with the new ROM. Do not use this theme with earlier or later builds.
For installation, it says "Just follow the official CM7.1 installation via recovery guide (stable or nightly). The removed components will be retained on your NC from the previous ROM if you do not uninstall those (Titanium recommended) or do a clean wipe."
I do have Titanium and I backed up using the "all user apps and system data" option. Is that adequate or is there a different option I should be using? Also, since he mentions that the removed components will be retained on the NC if you don't uninstall those...how do you know which ones and how do you go about uninstalling those? I never actually used the uNooter or ROM Manager...so I'm trying to figure out how to make it work with the method I used the first time around (VeryGreen's: http://forum.xda-developers.com/showthread.php?t=1000957) What I've done is just renamed "encore_CM72-MiRaGe-01132012" with "update-" in the beginning, put it on the boot partition, and rebooted into recovery.
wrong button click, LOL
Anyway, that should be it.
Yeah, my NC seems to be working fine after just renaming it to "update-" in the beginning of the files and booting it into recovery, but the transparent battery indicator theme didn't seem to do anything
Also, this is a random question, but do your NCs' volume rocker thing seem kind of loose? I was just wondering if that's normal because mine you can move left and right (you can kind of wiggle the button itself).
AngelWings8 said:
Yeah, my NC seems to be working fine after just renaming it to "update-" in the beginning of the files and booting it into recovery, but the transparent battery indicator theme didn't seem to do anything
Also, this is a random question, but do your NCs' volume rocker thing seem kind of loose? I was just wondering if that's normal because mine you can move left and right (you can kind of wiggle the button itself).
Click to expand...
Click to collapse
My volume button does that too.
Oh good, I was hoping it wasn't some sort of issue with the button being broken or something.
Also, I asked this earlier, but could someone explain to me what to do since after updating a new [CM7.2-RC0] MiRaGe - KANG build, he says "The removed components will be retained on your NC from the previous ROM if you do not uninstall those (Titanium recommended) or do a clean wipe. If you don't need a clean wipe, i.e. current ROM is CM7.1, instead of step 5 in the guide, do wipe dalvik-cache only."
Is that what I should be doing? How do I go about it using VeryGreen's method (without using ROM Manager or ClockworkMod Recovery?)
I'm sorry if I just sound like a complete noob, but I'm trying to learn!
Putting the sob story behind, I pulled this Bravo out of the closet and really miss some of the more advanced android features, so here I am.
Reading through the forums I think I need a ROM with at least Android 2.3.x. Stability is key, and I need everything to work (use camera everyday), so cutting edge ROMs are out for me.
Being a total noob, can someone advise which ROM is current, and point to some directions/links that worked for you? There is an abundance of information, and I have information overload.
So far, I rooted with superoneclick. Being a noob, that was a milestone! lol.
Thanks
Kilbert said:
Putting the sob story behind, I pulled this Bravo out of the closet and really miss some of the more advanced android features, so here I am.
Reading through the forums I think I need a ROM with at least Android 2.3.x. Stability is key, and I need everything to work (use camera everyday), so cutting edge ROMs are out for me.
Being a total noob, can someone advise which ROM is current, and point to some directions/links that worked for you? There is an abundance of information, and I have information overload.
So far, I rooted with superoneclick. Being a noob, that was a milestone! lol.
Thanks
Click to expand...
Click to collapse
That's a good start. What you need to do next is install 2ndinit recovery using the app to do so. Found here: http://forum.xda-developers.com/showthread.php?t=1032212 I'm using the latest version and it works just fine.
But before that, you may want to install titanium backup to back up all of your apps.
For roms, my suggestion is to start with skeevy420's cm7 kang, which runs android 2.3.7. It's stable, really fast, and reliable. It's my current and every day rom. It's found here: http://forum.xda-developers.com/showthread.php?t=1755200 There are plenty of rom flashing tutorials out there if you do a little searching. Good luck! If you have any questions, just ask.
This may seem like a noobish question, but how do you install 2ndinit?
I downloaded SndInitDefy_2.3.apk - (4.16 MB)
Do I put it on the SD card?
Do I need a root explorer?
Gapp?
Thanks
JOhn
Check "allow applications from unknown sources" in settings. Put the .apk on the SD card, open a file explorer and select it to install the app. Then follow the instructions on the thread.
Sent from my Amazon Kindle Fire using xda app-developers app
Kilbert said:
This may seem like a noobish question, but how do you install 2ndinit?
I downloaded SndInitDefy_2.3.apk - (4.16 MB)
Do I put it on the SD card?
Do I need a root explorer?
Gapp?
Thanks
JOhn
Click to expand...
Click to collapse
You might have to download the bravo sideload enabler from the market first.
Pardon the novel....
EDIT: This is the step by step that worked for me, a totally novice user. Compiled from all over these forums, and this thread. Thanks to Dr. Orange and Skeevy420 for helping me when I was totally stuck. I also suggest using directory Aa as suggested in skeevy420's post below, & having a full charge battery.
First, thanks for helping me. Pardon the wall of text, here is my plan (compiled from many places), I have completed up to and including step 14. I want to make sure I am on the correct path. I feel good until 18. I browsed the .zip archive of the kang download, I do not see the " gapp. file. "Where do I get it from? Thanks.
1) Factory reformat phone:
From the main home screen
tap menu
tap Settings
tap Privacy
tap Factory data reset
tap Reset phone
tap Erase everything. Confirm
2) On boot disable Motoblur by:
Press menu key (4 squares in lower left corner) and hold until keyboard pops up.
tap ?123
* tap ALT
* tap ABC
* tap e
* tap 123
* tap ALT
* tap ABC
* tap e
* tap b
* tap l
* tap u
* tap r
* tap o
* tap f
* tap f
3) Turn on USB debug
From the main home screen
* * * tap Applications
* * * tap Development
* * * tap USB Debugging (make green check)
4) Download/install Bravo drivers
http://www.motorola.com
5) Download/install superoneclick:
http://shortfuse.org/?page_id=2
6) Next connect phone via USB port with the computer
7) From Notifications pane on phone, change USB mode from Motorla Phone Portal (default) to USB mass storage.
8) In superoneclick:
Click Root button.
Phone will reboot twice.
You need wait for a while while the process completes.
9) Click Allow Non Market Apps:
Success is when you see a "1" value after checking NMA #1 & 2? (I assume - as this is where mine stopped for 1 1/2 hrs)
10) Verify @ Froyo (2.2.x):
Tap Settings
Tap About Phone
Want to see: Android Version 2.2.x
11) Download 2init & Gingerbread apps
http://forum.xda-developers.com/show....php?t=1032212
http://goo.im/gapps/gapps-gb-20110828-signed.zip
12) Download Kang
http://www.mediafire.com/?s531o2ikkbquakd
13) Place files on SD card. [CM-7.2-Kang-2012-07-13.zip] [gapps-gb-20110828-signed] & [SndinitDefy 2.3.apk]
Use windows explorer/Dolphin to copy (I made a directory called ROM with kang/gapps & another 2init)
Connect via usb
Put the .apk & .zip on the SD card in correct directories,
Disconnect USB
14) Install 2 init:
Check that "allow applications from unknown sources" is on in settings.
Use phone file manager to browse where you put sndinint (in 13 above) and select sndinit to install the app.
Find app in phones installed apps list
read instructions, install
Green light will be on, but will turn off after a while.
15) (Re)boot into 2ndInit recovery by
make sure the usb unplugged from computer .
Shut-down/reboot.
While booting watch for blue led to flash during boot, hit volume down once it flashes blue.(about 8-10 seconds in)
If done properly, you will see 2ndinit menu.
16) From 2ndinit menu:
Select Recovery
Select Custom Recovery
Select Wipe Data and Factory Reset
Select Yes -- delete all user data
Go to "Install zip from sdcard"
Choose zip from sdcard
Locate the zip and select it*
Select Yes
Go to "Install zip from sdcard"
Locate Gapps and select it
Select Yes
Select Go Back
Select Reboot -- You're done and using a custom rom
reboot takes a while- do not give up.
Make sure to wipe cache as well on 16. Sometimes it causes problems if you don't.
Here's the link for the gapps you'll need for CM7.
http://goo.im/gapps/gapps-gb-20110828-signed.zip
To save posts, I'll start on an updated CM7 tomorrow. There's been brown-outs and thunderstorms lately and one happed to happen as I was updating two weeks ago and the power outage wiped my android build partition; so I just shut my pc down and have only been on for maybe 30 minutes in the past two weeks. I don't want to risk damaging my 8 year old pc due to crappy weather combined with an over used power grid during 105F temps. Hope ya'll understand.
Luckily the temps down to around 95F and the power hasn't cut out for two days. Still hot and humid, but much better than the past few weeks. I normally don't say this, but I hope Louisiana or Texas gets slammed with a hurricane so we can get some good rain here in Arkansas.
I am on step 15. I can boot into 2ndinit.
SO close. Thanks a lot guys!
I am confused now. Do I choose Boot> 2nd init now? and reboot? or something else?
Will I then be able to see the wipe menus?
Kilbert said:
I am on step 15. I can boot into 2ndinit.
SO close. Thanks a lot guys!
I am confused now. Do I choose Boot> 2nd init now? and reboot? or something else?
Will I then be able to see the wipe menus?
Click to expand...
Click to collapse
Once your in the 2nd-Init bootmenu, do this.
Select Recovery
Select Custom Recovery
Select Wipe Data and Factory Reset
Select Yes -- delete all user data
Go to "Install zip from sdcard"
Choose zip from sdcard
Locate the zip and select it*
Select Yes
Go to "Install zip from sdcard"
Locate Gapps and select it
Select Yes
Reboot -- You're done and using a custom rom
*I put all my zips in a folder called "Aa". "Aa" happens to be the first folder on my sdcard and its less wear on the volume rocker than to find the zips when they're in places like Downloads or as a single file on the root directory of the card. Its also faster since you can access all you're zips in a literal second (flash hundreds of roms and you'll see what I mean).
THANKS! WOOOHOOO! 1 more ? please?
ITS ALIVE!!!!
THANKS skeevy420 & Dr. Orange for your time explaining this to a noob. I never expected to get this level of help from a developer forum.
If I can get one more answer- How do I enable or obtain the voice recognition keyboard that I used in my old phone? (I have a VERY difficult time typing)
Thanks
Kilbert said:
ITS ALIVE!!!!
THANKS skeevy420 & Dr. Orange for your time explaining this to a noob. I never expected to get this level of help from a developer forum.
If I can get one more answer- How do I enable or obtain the voice recognition keyboard that I used in my old phone? (I have a VERY difficult time typing)
Thanks
Click to expand...
Click to collapse
Try downloading voice search from the market. It might add the microphone button to your keyboard. I'm not certain though.
Kilbert said:
ITS ALIVE!!!!
THANKS skeevy420 & Dr. Orange for your time explaining this to a noob. I never expected to get this level of help from a developer forum.
If I can get one more answer- How do I enable or obtain the voice recognition keyboard that I used in my old phone? (I have a VERY difficult time typing)
Thanks
Click to expand...
Click to collapse
Definitely install Google voice search, but try installing an aftermarket keyboard. I use swiftkey 3, works amazing on the small bravo screen and it has build in voice typing.
Sent from my Amazon Kindle Fire using xda app-developers app
SD cared swap?
Google voice keyboard is working, and I will try that alternative keyboard thanks,
Does anyone know how difficult it is to swap sd cards? I forgot to put my large sd in, and have a small 2gb in there now.
Do I just put the card in, format it, and put the roms back on?
thansk
avr-Illithian said:
Definitely install Google voice search, but try installing an aftermarket keyboard. I use swiftkey 3, works amazing on the small bravo screen and it has build in voice typing.
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
+1 for SwiftKey 3. I got it on the 10 year anniversary for $0.10 usd. It's amazing. There's a swiftkey free, which would basically convince you to purchase the full version.
---------- Post added at 01:35 PM ---------- Previous post was at 01:31 PM ----------
Kilbert said:
Google voice keyboard is working, and I will try that alternative keyboard thanks,
Does anyone know how difficult it is to swap sd cards? I forgot to put my large sd in, and have a small 2gb in there now.
Do I just put the card in, format it, and put the roms back on?
thansk
Click to expand...
Click to collapse
You can use your computer and just copy the contents from one card and paste it on the other with no issues. You might need an sd card adapter for the other microsd card you'll be copying the data to. I've done this twice from the stock 2gb card to a 4gb, then to a 16gb. It's nice that it is so simple, as it shoulf be.
Just did the copy from one sd to another- worked perfectly.
I used "show hidden files" so I was sure to get everything.
Thank you!
Kilbert said:
Just did the copy from one sd to another- worked perfectly.
I used "show hidden files" so I was sure to get everything.
Thank you!
Click to expand...
Click to collapse
I had a Bravo, it was my first Android.
I think it's time to flash the little thing!
Thank you so much for the comprehensive to do list. I flashed my note, so I have some exposure, but your list should def help me stay on track. Thank you once again!
It should work fine, I edited it after I completed each step (so others could follow it- including me if I needed to at a later time). The only step that left me with a huge question was #9- allow non market apps. The software did not give any indication it was completed or successful.
These guys in the thread (Skeevy420, Dr. Orange, avr-Illithian) really helped me out when I had issues. The reading and conflicting information/dead links etc.. was overwhelming.
Good Luck. I am really happy with the new ROM. I have had no issues with it.
** DoPa5 v1.0 (AOSP v5.0.2_r1 - Lollipop) is now available for US/UK/AU users **
If you would like to upgrade from the stock ROM, see this post for downloads and installation details
Click to expand...
Click to collapse
DoPa v2.0 is an enhanced version of the stock ROM that features a custom-built kernel. It is based on Hisense's August, 2013 update (build P756.6.02.20) and is intended for US (8gb) versions of this tablet. It does not support the 32gb models sold in the UK and Australia. See Post 2 below for packages to root this tablet and install CWM Touch recovery.
This ROM de-bloats the original, roots it using SuperSU, and adds several useful apps, among them: Apex Launcher and ES File Explorer. It also includes several Xposed Installer modules to tweak your system, including GravityBox and my Phab7 UI switcher. For the hackers amongst us, ADB always runs as root.
The kernel is built from Hisense's source and offers enhancements and bug fixes. Most notably, it provides USB-OTG support so you can connect USB storage devices (e.g. thumb-drives) to your tablet using an OTG cable. It comes in two flavors, a non-overclocked version included in the main package, and a separate overclocked version that can be installed (and uninstalled) independently.
Installation
Having CWM installed is a prerequisite; if you haven't installed it yet, see Post 2. This ROM is intended to function as an update, preserving your apps and data. Unless you want to start from scratch, do NOT wipe or clear anything - the install script will do what's needed.
copy the file(s) to your internal or external SD card
reboot into CWM, then select "install zip"
I recommend you select "toggle signature verification"; enabling this will confirm the file hasn't gotten corrupted (if you get a verification error, stop, then copy the file to a different SD card)
choose the menu entry corresponding to where you put the file(s), then select "sero7pro-bld60220-dopa-v2.0.zip" from the list
after confirming your selection, the update will display what it's doing; you should NOT see any error messages
if you'd like to install the overclocked kernel, you can do so once the main package is in place, or at some later time
reboot
Notes
when you attach a drive using the USB-OTG feature, it is automatically mounted at '/usbdisk'. Be aware there is no easy way to unmount it - you may have to use adb or a terminal app to ensure a clean unmount. This should only be an issue if you write to the disk; if you're only reading, it may be safe to just pull the plug.
the overclocked version of the kernel runs the processor at 1.5ghz rather than the standard 1.3ghz. Using it may result in a significant loss of stability on some systems. You may want to install one of the many apps that let you control the maximum speed to regain stability and reduce power consumption.
much of the app-bloat this ROM tries to eliminate (such as Sams Club or Playstore Magazines) may still be present if you've ever gotten updates for any of these apps. To get rid of them permanently, uninstall them using Settings->Apps->Downloaded. For "system" apps like the Google stuff, select "Uninstall updates", then "OK" when it asks if you want to revert to the factory-installed version (which doesn't exist anymore). The apps will be gone for good.
to enable the many tweaks offered by GravityBox and Phab7, open the Xposed Installer app and enable it via the "Framework" option but don't reboot yet. Back out and choose "Modules", then tap directly on the checkbox to the left of each module's icon (not on the icon or text). Now, reboot to activate their features.
Note: GravityBox's Quick Settings tiles and statusbar mods only work with the Phone or Phablet UIs (i.e. not Tablet UI). To get the full effect from Tablet UI, open Apex Launcher's settings and select "Homescreen settings->Use tablet UI mode"
Geek Alert: with the addition of DriveDroid (not included), this kernel lets your tablet emulate a USB CD drive that can be used to boot your PC. See the app's description for details.
Credits
xboxexpert - for getting things going
randomblame - for many of the patches used in this kernel
Files
new and improved:
sero7pro-bld60220-dopa-v2.0.zip - the DoPa v2.0 ROM with the standard kernel
sero7pro-boot-dopa0oc-v2.0.zip - the overclocked kernel
sero7pro-boot-dopa0-v2.0.zip - the standard kernel (in case you want to reinstall it)
old and tired: (do not use with v2.0)
sero7pro-bld60220-dopa-v1.1.zip - the DoPa v1.1 ROM
sero7pro-usbotg-dopa-v1.1.zip - USB-OTG add-on
sero7pro-macfix-dopa-v1.1.zip - random MAC address fix
sero7pro-sysui-dopa-v1.1.zip - removes screenshot button
miscellaneous:
sero7pro-bld60220-removed.zip - files that were removed from the DoPa ROMS (note: unlike the other files here, this is not a flashable zip. Unzip it, copy the apps you want to your SD card, then install them from there)
stock-v60220-full-update.zip - the complete 6.02.20 update from Hisense - this is the closest you'll get to the original stock ROM
GPL Notice: the source code for this kernel is available at https://github.com/dolorespark/android_kernel_hisense_m470bsa on the 'master' branch.
DoPa
XDA:DevDB Information
Sero 7 Pro (US) - DoPa v2.0 Modified Stock ROM, ROM for the Android General
Contributors
dolorespark
ROM OS Version: 4.2.x Jelly Bean
ROM Kernel: Linux 3.1.x
Based On: Stock ROM
Version Information
Status: No Longer Updated
Current Stable Version: 2.0
Stable Release Date: 2014-01-22
Created 2015-01-26
Last Updated 2015-01-27
Root/CWM packages
These packages will root and install CWM Touch recovery on the US (8gb) model of the Sero 7 Pro. There are separate versions for Windows and Linux. They have been tested under Win XP, Win 8, and Ubuntu, and should avoid problems encountered with other root/recovery packages.
The packages are modular so that you can run some or all of the functions as-needed. They consist of 4 scripts:
step0-DoItAll - displays some setup info then runs all 3 of the following
step1-adb - enables ADB ("Android Debug Bridge") to locate the tablet
step2-root - roots the tablet and installs the SuperSU app
step3-cwm - installs CWM Touch Recovery v6.0.3.2
Versions of ADB for each OS are included, so no other packages or downloads are needed. Usage should be fairly simple: unzip the package into a convenient directory, doubleclick on step0-DoItAll, then follow the (minimal) instructions. Alternately (and better), open a command prompt/bash shell, change to the directory where you unzipped everything, then run the script(s) from there.
Avoiding Frustration
If you haven't rooted an Android device before, please read the following because there are a few "gotcha"s. If you have but things aren't going as expected, review the following in case you missed/forgot something.
Developer options must be visible in the Settings app. If they aren't, select "About tablet", then tap on "Build number" 7 times. A small popup will tell you that you're now a developer. Back out to the list of settings categories - you should now see "Developer options".
USB debugging must be enabled under "Developer options". Please be sure it is. If it isn't, select it then tap OK when a warning popup appears.
Both Windows and Linux require extra files to be in place before ADB can communicate with your tablet. Click on the button for your OS to see the ugly details.
Windows
Windows requires USB drivers to be installed. Drivers that will work with the Sero7Pro (and possibly any Android device) are included in the package.
After enabling "USB debugging" and connecting your tablet, a wizard may pop up to guide you through the steps. If not, force it to appear by opening Device Manager. Look under "Other devices" where you should see something like "Android phone". Doubleclick on it, then select the "Install driver" button on the window that appears.
When the wizard pops up, tell it you'll select the drivers, then choose the option that tells it where to look. Click the "Browse" button and navigate to the directory where you unzipped the package. Select the usb_driver folder, press "OK", then "Next" - the drivers should install without any problems.
Notes: On Windows XP, the first wizard to pop up may want to install drivers for "MTP" which XP doesn't support. If so, cancel out of that, then wait for the "Andoid Phone" wizard to appear. On later versions of Windows, you may get a popup warning that the drivers aren't signed properly; if so, select "Install driver anyway". On Win 8-64bit, driver installation will fail unless you started the current session with "Driver signature enforcement" disabled.
Linux
Linux (or at least Ubuntu) doesn't allow user programs to access USB devices directly without the appropriate permissions in place. This package includes a file named 99-android.rules which provides those permissions
If you've never provided access to other USB devices, just copy the file to /etc/udev/rules.d. Otherwise, you can either copy it or merge its contents with the .rules file containing your other USB entries.
Note: both the rules.d directory and its contents are owned by root. You will probably have to use the sudo command to gain access. For example, from a bash shell whose current directory is the one where you unzipped the package, you'd enter "sudo cp 99-android.rules /etc/udev/rules.d". Also, be sure the file's permissions match the others in that directory. If not, run "chmod 644 /etc/udev/rules.d/99-android.rules".
Notes
When you're done, open the SuperSU app to enable it. It will ask to update the su binary. After selecting OK, the app will be enabled and will popup warnings whenever an app requests root access for the first time.
The Linux script is actually designed for both Linux and Mac OS X. However, I haven't fully tested it yet so I don't want to make any incorrect claims of support. You may have to correct some file permissions and will almost certainly have to run it from the Terminal app.
Files
sero7pro-root-win-dopa.zip - Windows
sero7pro-root-unix-dopa.zip - Linux
[Obsolete] Remove Screenshot Button / Add Instant UI Switcher
The mod originally described in this posting is now obsolete with the release of the DoPa v2.0 ROM which has both features built in.
If you are running an older version of that ROM, or XBoxExpert's ROM, or even the stock ROM, you can still remove the screenshot button using this CWM-installable package: sero7pro-sysui-dopa-v1.1.zip.
If you'd like to try Phab7, an on-the-fly UI switcher that lets you select Phone, Phablet, or Tablet UI modes, see this thread. Note: you must install the SystemUI mod to switch to Phone UI - without it, SystemUI will force-close when you do.
Good work. Hope to see more devs and more Roms
Really good. I'm using it right now. Keep going with the good work
Good Job! Looking forward to more posts!
Thanks for the nice work and good instructions. I'm using your stock ((build P756.6.02.20) rooted now and plan to try the ROM soon without Link2SD operational to keep all my apps.
Thanks again, I have updated my Sero to this ROM. Everything seems to be working perfectly. I look forward to many updates!
Thank you. Your ROM runs smooth and fast.
Great work man, downloading it now! Thanks!
Antutu result for this ROM
12979 is my antutu result for this ROM while my previous stock ROM result was 11948 while 12339 was result of XE ROM. Thank you!
Installed and working. Thanks.
taba4real said:
12979 is my antutu result for this ROM while my previous stock ROM result was 11948 while 12339 was result of XE ROM. Thank you!
Click to expand...
Click to collapse
I'm getting 13861 on this ROM, 11249 on the previous XE ROM.
Ran it twice, results were very close. I did leave all the 'tweeks' in from Xbox's post, not sure if that makes any difference.
Larry
Sent from my Nexus 7 using xda app-developers app
larryf said:
I'm getting 13861 on this ROM, 11249 on the previous XE ROM.
Ran it twice, results were very close. I did leave all the 'tweeks' in from Xbox's post, not sure if that makes any difference.
Larry
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Why am I getting 10500 on this ROM then?
Does this root and cwm change kernel like xbox's?
lordroy said:
Why am I getting 10500 on this ROM then?
Click to expand...
Click to collapse
Did you run it with the raw system? What I mean, is did you run it after the ROM settled out and after a few reboots or did you flash and then run the benchmark? It is probably over kill but I like to let the ROM sit for awhile and then do a couple of reboots before I run bench marks. My first score was very close to larryf's score (13,800) the first time I ran it, but after I added live wallpaper, Nova launcher, Xposed, etc. my last score was 11395. I assume any benchmark program would shutdown all non essential programs before running but that may not be the case.
EDIT: Wow, I rebooted right after I type this and ran AnTuTu again and it scored 14,425.
https://www.dropbox.com/s/kmwd7jgjpcw233y/Screenshot_2013-10-07-22-38-57.png
Cooter007 said:
Did you run it with the raw system? What I mean, is did you run it after the ROM settled out and after a few reboots or did you flash and then run the benchmark? It is probably over kill but I like to let the ROM sit for awhile and then do a couple of reboots before I run bench marks. My first score was very close to larryf's score (13,800) the first time I ran it, but after I added live wallpaper, Nova launcher, Xposed, etc. my last score was 11395. I assume any benchmark program would shutdown all non essential programs before running but that may not be the case.
EDIT: Wow, I rebooted right after I type this and ran AnTuTu again and it scored 14,425.
https://www.dropbox.com/s/kmwd7jgjpcw233y/Screenshot_2013-10-07-22-38-57.png
Click to expand...
Click to collapse
I flashed it days ago with this ROM, lots of reboots etc. Not sure what I am doing wrong or why my score is so low.
lordroy said:
I flashed it days ago with this ROM, lots of reboots etc. Not sure what I am doing wrong or why my score is so low.
Click to expand...
Click to collapse
It may have something to do with my minimal approach to this tablet. I bought this tablet to use in the car. After setting up Nova Launcher, I'm pretty much down to two addition; ODB2 and CoPolit.
My HomeScreen ----- https://www.dropbox.com/s/rsdp9oskbhtg9jp/Screenshot_2013-10-07-23-05-38.png
Cooter007 said:
It may have something to do with my minimal approach to this tablet. I bought this tablet to use in the car. After setting up Nova Launcher, I'm pretty much down to two addition; ODB2 and CoPolit.
My desktop ----- https://www.dropbox.com/s/rsdp9oskbhtg9jp/Screenshot_2013-10-07-23-05-38.png
Click to expand...
Click to collapse
Of course as soon as I mention something, my Sero decides to play nice.
Just got a score of 13861. I didnt change anything, it just decided to score better for some reason.
lordroy said:
Why am I getting 10500 on this ROM then?
Click to expand...
Click to collapse
Sir i used to get this with Power Saving mode instead of Perfromance priority mode....... =):good:
This is just an initial ROM for a project i'm starting with this device. This is the stock rom but cleaned up and tweaked a little. Removed all the junk from the rom and replaced the keyboards with Null Keyboard. Added a few apps for convenience. Keep an eye out, I will be updating frequently. Requests are welcome. Thanks for looking.
ADDED:
AdAway
ES File Explorer
Reboot App
Writer
Just flash with rockchip batch tool and enjoy!
can't post links so copy and paste in url box and remove the spaces:
h ttps://w ww.drop box. com/s/2x6qp0s56hqkyu3/timingpowercfw.img
nothing there
misk8er said:
This is just an initial ROM for a project i'm starting with this device. This is the stock rom but cleaned up and tweaked a little. Removed all the junk from the rom and replaced the keyboards with Null Keyboard. Added a few apps for convenience. Keep an eye out, I will be updating frequently. Requests are welcome. Thanks for looking.
ADDED:
AdAway
ES File Explorer
Reboot App
Writer
Just flash with rockchip batch tool and enjoy!
can't post links so copy and paste in url box and remove the spaces:
h ttps://w ww.drop box. com/s/2x6qp0s56hqkyu3/timingpowercfw.img
Click to expand...
Click to collapse
Please repost the ROM. When attempting to download it, this is what I get:
"Nothing Here
The file you're looking for has been deleted or moved."
Thanks!
As of now I'm using latest firmware 20131103.
I only use this device for Plex it's perfect for DTS, bluetooth audio/video is in perfect sync but MKV's with AC-3 stereo audio & video is out of sync big delay of some sort.
Anyone else experiencing this issue?
I can't try other ROMs because not sure which other ROMs can be flashed with this device. Any pointers or advice would be much appreciated.
Hello,
Just a curious question.
Does wireless display work on this ROM?
I have an CX-919 and flashed 4 different ROMS already (finless 15, 16b, kitkat, NZ something) and non off them work.
Wifi display is connected with my galaxy S4 or Asus ME302C tablet, but mirroring does not start.
It worked with my S4 one time with finless kitkat, but that was it.
I really want to get it working because i have all pictures etc. om my phone and tablet.
PS: if anyone reads this and has problems to get into flash mode, the solution is very simple.
Do not use the USB cable that comes with your stick.
Use an USB cable form your phone or tablet.
I use my Samsung USB cable and that works flawlesly, althoug the blue LED stays on (in opposite of what everyone says) after plugging it in the PC with the button held.
All flash tools i used see the stick everytime and no problems flashing whatsoever.