[Q] Testing/Bug Tracking - Ubuntu Touch Q&A, Help & Troubleshooting

Hello,
I'd like to support but I don't want to flash 'the official way'. Wanna use the zip files like I always do.
Now I'm concerned about two things:
does it matter whether I install over recovery or by script? Does the quality suffer so bug reports don't make sense? Don't think so..
and second I like to know where I can find the version/build number, so bug reports won't get messed up because I tested the wrong version.
BR
Michael
## edit ##
ok, there's something about an ubuntu_stamp..

Well, for bug track, if not related to non official images, you can report here:
https://launchpad.net/touch-preview-images

Please post in Q&A section next time. The Ubuntu Touch threads are already a mess :/.
Sent from my Galaxy Nexus using Tapatalk 2

It should not make a difference for the bug reports if you install manually instead of using the phablet-flash tool. However, I'd strongly recommend doing the manual install as described on the installation instructions:
Check out wiki.ubuntu.com/Touch/Install#Manual_Installation

Related

[ROM] CyanogenMod 7.0.3 ALPHA3 - 5/11/11

Got bored again, this time I merged my device tree and fixes into CM7 Gingerbread ROM is built from the newest CM7 source code, and has been merged with the majority of my device specific fixes from previous ROMs. I love open source, so of course source code is available for everything, here (ROM), here (kernel), and here (initramfs). If you would like to follow the changes I make, check my github rss feed here.
*** WORKING ***
RIL (calls/sms/3g data)
WiFi
GPS
sdcard and USB mass storage
rotation and proximity sensors
screen on/off animation
haptic feedback
*** NOT WORKING ***
Camera/Camcorder
MMS
BT
most video codecs - Youtube playback (LQ & HQ) is broken for example - youtube does work from a browser if you use a desktop user-agent
Voodoo lagfix conversions
There are still plenty of bugs! and there likely will be until we have a true GB leak or official release to work off of.
PLEASE READ
It is considerably difficult for me to stumble upon every issue out there, and even more difficult to narrow these issues down, let alone fix them. That said, PLEASE do not clutter this thread with "thank you" or "X/Y/Z doesn't work" or "I'd love to flash this if..." type posts. I APPRECIATE THE THANKS AND THE FEEDBACK!!! Don't get me wrong. But these posts are not at all helpful in moving this ROM forward, and simply add more clutter to the forum. If you make such a post, don't expect a response.
If you experience a bug, PLEASE GET LOGS! I can't fix something simply by knowing that it does not work. A bug report without significant details is a useless post, it just is what it is. Logs help identify the code affected, and thereby help facilitate the fixes that we all love. PLEASE share your issues if you can provide helpful data in fixing them
THANKS FOR READING
The ROM package currently includes the base CM7 ROM, and a compatible kernel. Flash gapps from the package linked below. DO NOT FLASH ANY OTHER GAPPS OR KERNEL PACKAGES! The ROM package uses edify scripting, so it is flashable with any iteration of ClockworkMod recovery.
ALSO: devs and noobs alike please take notice : this ROM uses ClockworkMod recovery 3.x. I will no longer be supporting older recoveries!
Much thanks to the EpicCM and teamhacksung folks for code and ideas, and of course props to the CM team for all they do, it's their ROM after all.
If you appreciate the time and effort I have put into this ROM please click the "Thanks" or "Donate" buttons. Either one is fine by me
***** Update 4/26 - ALPHA2 *****
fixed USB mass storage
fixed haptic feedback
fixed TiBu 'whoami' bug
update to 3.x ClockworkMod recovery
sync'd with latest CM code
updated to latest Market
stubbed the camera (yes, I know it takes pictures of nothing but a green android )
** package still includes gapps and kernel **
** changed to new kernel that can be used with BOTH rfs AND ext4 - but it does not include the Voodoo lagfix code, so no conversions! **
** Make sure to wipe data even if coming from the previous alpha! **
***** Update 5/11 - ALPHA3 *****
updated to latest CM7 code (7.0.3)
enabled recent CM code to prevent "ring only once" bug (lightly tested)
made one of my sms hacks "optional" for easy editing by the mesmerize/showcase users (simply remove "ro.sms.padding=1" from build.prop to fix sms on these devices)
fixed some memory settings in kernel - should fix the lag experienced when using previous versions
added other tweaks to kernel for speed improvement (increased sdcard readahead cache/lowmemkiller/etc)
included punk-kaos' recent camera changes into kernel (cam not working, but getting there)
unstubbed camera (no more pics of a green android )
cleaned up my build tree a bit for a smaller download for people building themselves
removed gapps from ROM package, download from link below (kernel still included in ROM package)
ROM package will no longer flash a recovery
switched to bmlwrite for flashing kernel (screen will no longer wig out during kernel flashes)
Instructions:
flash with Clockwordmod recovery
flash ROM first then flash gapps package
WIPE DATA! if coming from ANY other ROM
Don't worry about disabling lagfix or any of that nonsense, ROM will work whether you are using ext4 or rfs
ALPHA3
http://www.mediafire.com/?ziawa7ot8dhdq4k
GAPPS
http://www.mediafire.com/?ogylu5w024148lt
Enjoy and remember: If your phone breaks after flashing, YOU broke it! Not ME!
You work pretty quickly for someone who gets bored.
This may peg my level of knowledge but here goes. . .What logs would be most beneficial? Assuming alogcat is the standard method, there are a lot of different options of logs in there. Any specific ones that would be the most helpful in tracking down a bug?
Not trying to clutter, hopefully avoiding more in the future
dw77x said:
This may peg my level of knowledge but here goes. . .What logs would be most beneficial? Assuming alogcat is the standard method, there are a lot of different options of logs in there. Any specific ones that would be the most helpful in tracking down a bug?
Not trying to clutter, hopefully avoiding more in the future
Click to expand...
Click to collapse
any random bugs can usually be picked up from the main log. anything having to do with the radio (call issues/sms issues/etc) need the radio specific log
I'm not familiar with alogcat (market app right?), but the logs can be dumped using adb from a pc. ex:
adb logcat > logcat.txt
will dump the main log
adb logcat -b radio > radio.txt
will dump the radio log
thank you for your concern
Hey JT, I was talking to you on twitter today (@ScottColeBCS). I sent my email addy, I don't know if you got it. Let me know if you figure out a way for me to do that for you. Thanks Bro.
EDIT: Nevermind bro. I'm stupid. I just checked my email and saw that you sent the info I needed. Be expecting it.
I need to clean my keyboard...great job jt!!
Sent from my SCH-I500 using XDA Premium App
Thank you JT. You are a boon to this community. Have a beer on me.
Thanks Jt....good stuff
Sent from my SCH-I500 using Tapatalk
Sweet. So what are the chances this will bebe compatible with the Mesmerize eventually? I assume it is not currently.
Sent from my MIUI SCH-i500
What's the difference between this and the one you released on Twitter last night?
Hey JT, I know there are many thread junkies (like myself) who are constantly checking for bug fixes and updates. I also read in the OP that you said there will plenty of bugs still until we get an official leak. Does this mean that with what you have available to you at the moment the functionality will remain as is, or are you still plugging away at some of these issues? I ask this simply to see if we should be checking for updates. Not complaining one bit! I love this rom so far. Thanks a ton!!
running great
Sent from my SCH-I500 using XDA App
kidserious said:
Hey JT, I know there are many thread junkies (like myself) who are constantly checking for bug fixes and updates. I also read in the OP that you said there will plenty of bugs still until we get an official leak. Does this mean that with what you have available to you at the moment the functionality will remain as is, or are you still plugging away at some of these issues? I ask this simply to see if we should be checking for updates. Not complaining one bit! I love this rom so far. Thanks a ton!!
Click to expand...
Click to collapse
I will still make do with what we have. As far as what that entails, who knows. One thing I'm relatively sure of is the fate of the camera. It's likely to remain non-functional until we have a GB base to work with.
You are the man, man! Thank you so much that you do for us. You guys are awesome! Thank you again!
Sent from my SCH-I500 using XDA Premium App
jt1134 said:
I will still make do with what we have. As far as what that entails, who knows. One thing I'm relatively sure of is the fate of the camera. It's likely to remain non-functional until we have a GB base to work with.
Click to expand...
Click to collapse
Ok, Well I will take that as there is a definite possibility you will be able to fix some of the non-camera bugs. It lets me know that fixes for these issues are not out of the realm of possibility with current sources. JT, your new name is Mr. Fascinate (with a thunderbolt) Lol. Keep doing what you do brother, you're making a lot of people happy.
Did Punk.kaos stop working on CM7 too? If not, why don't you guy help each other?
What will be different between This rom and the Kaoscinate?
Sent from my SCH-I500 using XDA App
deaffob said:
Did Punk.kaos stop working on CM7 too? If not, why don't you guy help each other?
Click to expand...
Click to collapse
Apparently kaos has been MIA for quite a while now.
kallell said:
Apparently kaos has been MIA for quite a while now.
Click to expand...
Click to collapse
maybe he just likes the thunderbolt people better
Works damn good for an alpha.

[MOD] I9100 ROM Hellraiser for I777 (Alpha 0.3.1, 12/3/2011) [BUGS/DEV ONLY]

This thread is now for bug reports/development only. Do not post in this thread any more until you have fully read the first four posts of this thread, and the first two posts of the Q&A Thread. If you post in this thread and it is clear that you have not read the posts indicated above, your post will be reported. For other discussion and "Is this a bug?" type questions, go to the Q&A Thread
Heeeeere we go! As LinuxBozo, one of the most talented developers in the Infuse community said, "Welcome to a new and sick, twisted world!"
Over in the Infuse community, we had an oddball device that had little in common with anything else. As a result, it was not easy to port ROMs from the I9000/Captivate. However, after LOTS of work, LinuxBozo pulled it off and came up with an automatic porting package that could get most I9000/Captivate ROMs running on the Infuse. As a result, it opened the Infuse community up to a massive variety of ROMs.
For the month since the I777 came out, people keep asking about I9100 ROMs. In general, the answer has been, "It should be possible, but no one other than designgears has done it yet." - I didn't have the time as I had too much kernel work to do. However, as the kernel is at a fairly mature and stable state, when someone asked for SensatioN to be ported, I figured it was time for a challenge.
I was successful, but encountered a few glitches. Tethering was broken, fortunately the Infuse community had the same issue and the same fix worked. Mic in calls was broken, just like CM7 - I finally got atinm's list of the blobs to swap out. As a result, nearly all of the challenges in porting an I9100 ROM to the I777 have been identified.
This is a package that should automatically port most I9100 ROMs to the I777. It has been tested by myself as follows:
SensatioN 1.8 by Crysis21 has been manually "Hellraised", and was the basis on which this package was developed. Do note that the author of this ROM tends to be unresponsive to porters. I asked for permission to release a ported ROM but never heard back.
VillainROM 3.0 was the first ROM to be tested with the attached package - it seems to work, if there are any problems, it is likely because I missed something in the permissions settings of the updater script. - Also, I have tested JKay's Deluxe Themes on VillainROM successfully - his thread is at http://forum.xda-developers.com/showthread.php?t=1154278 - You need to use the XXKI3 theme packages.
In general, XXKI3-based ROMs work. XXKI4-based ROMs may have issues with WiFi (see Known Issues below). I am working on compiling a more complete list in the Q&A Thread.
Please don't report bugs with ROMs to the upstream author of the ROM in the event that the bug was caused by Hellraising - unfortunately, it is going to be very difficult to identify when Hellraising caused a bug and when the ROM itself has a bug.
Instructions for the package:
Download an I9100 ROM to be Hellraised - must be CWM-flashable Gingerbread (ICS will NOT happen until after kernel source code becomes available, and if you spam me with 10000 "did you see this" links when it does I'll just go watch some TV. You have been warned.), and must be Samsung-derived (not CM7/MIUI/AOSP-based), ROMs distributed as Odin .tar files like Litening won't work. (I've tried...)
Download the package above
Unzip the ROM, check to make sure it does not have bootloaders. If it has Sbl.bin or param.lfs in it, RUN AWAY. No ROM developer should EVER include a bootloader without explicit warnings of this, if a ROM includes a bootloader it's a sign that it'll be **** in almost all cases. Similarly, param.lfs corruption can lead to a device that won't boot and I believe it can even break download mode. ROMs shouldn't be messing with this either without warning users.
Once you've done your safety check, put the ROM zip and the Hellraiser zip onto your SD card
Enter CWM
You should probably do a Nandroid backup here...
Wipe Data/Factory Reset - Some ROMs write apps to /data and you'll lose these if you wipe afterwards
Flash the ROM, DO NOT REBOOT, STAY IN CWM
Flash the Hellraiser package
Reboot and enjoy!
Known issues:
NFC files are included, but enabling NFC requires smali modifications to Settings.apk on some ROMs. (Starting to look like this is only for I777 stock-derived ROMs - VillainROM doesn't actually need any smali.)
Touching an NFC tag containing NDEF data will cause the NFC service to crash due to being unable to obtain STOP_APP_SWITCH permissions
Wifi tethering settings are not persistent and keep resetting themselves (At least on SensatioN and VillainROM) - Workaround for now: Enable tethering, THEN set the SSID and password, OR see http://forum.xda-developers.com/showthread.php?t=1335377&page=24
When initially setting up the ROM, it claims that network time is not available, and takes you to Settings - where you can check it to enable it and it works fine... Infuse Hellraiser had the same issue. Happens only once per flash so it's a very low priority.
When flashing other ROMs that do device compatibility checks (such as CM7), they will think you have an I9100 instead of I777. You need to flash an I777 ROM first.
Download links have been moved to the ChangeLog post (Post #2 below)!
Alpha 0.3.1 Release, 12/3/2011:
Download: http://www.multiupload.com/NUV8KDF9OZ or http://dev-host.org/4up if MultiUpload never comes back
Changes:
Only one - actually include Daily Driver 12/1/2011. People who flashed 0.3.0 only need to reflash Daily Driver from my kernel thread, no need for a full flash of Hellraiser.
Alpha 0.3.0 Release, 12/1/2011:
Download: PULLED, BAD RELEASE: Use 0.3.1 instead. If you already flashed 0.3.0, flash the 12/1 release of Daily Driver
Changes:
Update to some random kernel pulled from the wrong location on my hard drive
Overwrite /system/etc/apns-conf.xml with a "known good" one
Overwrite the CSC with a "known good" one
Home button haptic fix, courtesy of LinuxBozo of Infuse Hellraiser. Thanks to amtrakcn for pointing out that LinuxBozo's fix works on our device
Alpha 0.2.2 Release, 11/10/2011:
Download: http://www.multiupload.com/C1W5S6XW0R
Changes: Update to Daily Driver 11/10/2011 kernel (disables autoroot which broke root for a bunch of people), tiny installer script cleanups.
If root is working well for you, it is not worth flashing this
If root is broken for you, I recommend installing Daily Driver 11/10 and flashing ChainsDD's latest su package (linked from the DD thread's first post now). If you flash this it will remain broken, this only fixes new installs
Alpha 0.2.1 Release, 11/08/2011:
Download http://www.multiupload.com/ORQESFHVBT
Changes: Only one, replace Nfc.apk with the correct one. Fixes NFC service force closes.
Alpha 0.2 Release, 11/07/2011:
Download - PULLED due to excessive fail. Use 0.2.1 instead!
Changes:
Should now flash without the mount workaround trick after ROMs that unmount /system
Added NFC files from the I777 and one permissions XML - These combined with a small mod to Settings.apk will allow NFC to work. Will post details for ROM devs on making these mods soon. NOTE: Right now this only supports reading tags! Google Wallet support requires a LOT more work, if even possible! (Edit: I'm fairly certain it'll only be possible in CM7 - but I think I also know what's needed for the CM7 guys to get the rest of the way there.
Initial release, 11/06/2011:
Version - Alpha 0.1
Download - http://www.multiupload.com/9RJKKSBFZ0
How it works
Here's the details of how this package works.
1) This package replaces the modem with a known good I777 modem
2) It also replaces the kernel with an I777 kernel (Right now, Daily Driver 11/03 release) - This is half of the keymap fix. Also, DD 11/3 contains a fix that allows wifi tethering to work on both I777-derived ROMs and I9100-derived ROMs
3) It replaces two of the keymap files in /system/usr/keylayout/ - see http://forum.xda-developers.com/showthread.php?t=1313050&page=56 for details - thanks to MikeyMike01 and Dungeon47 for this one
4) It replaces most of the audio library files to fix the issue with outgoing mic audio in calls - this is the same fix used by Cyanogenmod 7 - see https://github.com/koush/proprietar...12f711197665edeb28522386a77a62da24bab#diff-28 for details, thank atinm for this one
Attached:
Hacked settings APK for VillainROM 3.0 - This, along with Alpha 0.2.1, should allow you to turn on NFC. May work on other XXKI3-based ROMs
For ROM Authors:
To get NFC to show in Settings, baksmali the Settings APK and open WirelessSettings.smali
Look for the line below:
Code:
invoke-static {p0}, Landroid/nfc/NfcAdapter;->getDefaultAdapter(Landroid/content/Context;)Landroid/nfc/NfcAdapter;
Delete the next two instances of lines that contain the word removePreference
NFC should then show in Wireless settings
Great work! I can't wait to try this out when I have some free time.
well aren't you awesome bro. Thanks a lot. This opens the door to a lot of good things.
this looks awesome i have to find a rom i want to try from their forums though since lite'ening doesnt work
Dude you freaking rock! Thanks so much for this! What is your donate link?
Sent from my SAMSUNG-SGH-I777 using xda premium
jgrimberg1979 said:
What is your donate link?
Click to expand...
Click to collapse
Under his Thanks Meter.
THANKS!!!
about to test it out with the sensation rom! Really appreciate the effort you have been putting in lately!
Entropy
What about Roms that have a different version of cwm recovery, for ex some of them have 4.x cmwr. Does your kernal that you including relash cwr 5.x?
Sent from my SAMSUNG-SGH-I777 using xda premium
Awesome, just awesome entropy
Let the flashing and testing begin! You are a genius sir.
Sent from my SAMSUNG-SGH-I777 using XDA App
jgrimberg1979 said:
Entropy
What about Roms that have a different version of cwm recovery, for ex some of them have 4.x cmwr. Does your kernal that you including relash cwr 5.x?
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
CWM is in the kernel, and this replaces the kernel.
Entropy512 said:
CWM is in the kernel, and this replaces the kernel.
Click to expand...
Click to collapse
Awesome, what would be some of the reason why this would not work with some roms, since the package addresses most of the differences between the two phones? Is there something we should look for besides bootloader, that may stick out as a possible incompatibility?
Sent from my SAMSUNG-SGH-I777 using xda premium
jgrimberg1979 said:
Awesome, what would be some of the reason why this would not work with some roms, since the package addresses most of the differences between the two phones? Is there something we should look for besides bootloader, that may stick out as a possible incompatibility?
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
Unsure yet - most likely any remaining issues will be common.
The one thing might be if the ROM has a special unusual kernel dependency. I'm not too far from Ninphetamine, but there might be some wacky kernels out there that have wacky ROMs paired with them. Such ROMs would even have problems with other I9100 kernels on the I9100.
I don't expect anything to be blatantly obvious at this point... My biggest worry is that I botched the permissions in the updater script.
Thank you Entropy, can I use this with i9100 MIUI rom as well?
Sent from my SGH-I777 using xda premium
Entropy512 said:
Unsure yet - most likely any remaining issues will be common.
The one thing might be if the ROM has a special unusual kernel dependency. I'm not too far from Ninphetamine, but there might be some wacky kernels out there that have wacky ROMs paired with them. Such ROMs would even have problems with other I9100 kernels on the I9100.
I don't expect anything to be blatantly obvious at this point... My biggest worry is that I botched the permissions in the updater script.
Click to expand...
Click to collapse
Home button is not working. I've went and flashed sensation twice, following your steps of course. Did you have the same issue?
Sent from my SAMSUNG-SGH-I777 using xda premium
jivy26 said:
Home button is not working. I've went and flashed sensation twice, following your steps of course. Did you have the same issue?
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
You need to map the keys correctly...
Sent from my GT-I9100 using xda premium
Entropy512 said:
Unsure yet - most likely any remaining issues will be common.
The one thing might be if the ROM has a special unusual kernel dependency. I'm not too far from Ninphetamine, but there might be some wacky kernels out there that have wacky ROMs paired with them. Such ROMs would even have problems with other I9100 kernels on the I9100.
I don't expect anything to be blatantly obvious at this point... My biggest worry is that I botched the permissions in the updater script.
Click to expand...
Click to collapse
Still not workin
Edit; to clarify audio issue on the sensation rom is still there
Sent from my GT-I9100 using xda premium

[how to] **v6 supercharger script**

I decided that since enough people asked about it, then it probably deserves it's own thread. This thread contains information on how to set up the V6 super charger script on the galaxy note.
**PLEASE FOLLOW ALL INSTRUCTIONS TO ENSURE SUCCESSFUL INSTALLATION/OPERATION OF SCRIPT**
CREDITS:
**ZeppelinRox** Creator of V6 and many great scripts!
WHAT YOU WILL NEED:
A. Rooted phone (duh)
B. Busybox 1.81.1 DOWNLOAD Via GOOGLE PLAY app - **BUSYBOX INSTALLER** https://play.google.com/store/apps/d...N0YWxsZXIiXQ.. (Thanks Capite for the link)
C. (optional) Root Explorer (to mount /system to r/w) can use script manager too
D. V6 supercharger PDF file... which is linked below
*****ICE CREAM SANDWICH USERS**** don't forget to first supercharge your SERVICES.JAR via website....http://android.mimic.ca**********
Flash in Clockwork...... Cache Wipe X2 - Wipe Dalvik - Flash Zip.
Installation Instructions:
Please follow ZEPPELINROX thread here: http://forum.xda-developers.com/showthread.php?t=991276 -
Per his request, i will not create installation instructions...... But if you have questions i will try to help you out since i have used it forever.
________________________ zOOm zOOm _______________________________________
*
*
*
*
SCRIPTS
MOST SCRIPTS CAN BE FOUND HERE: http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021
Hey just a quick heads up...zeppelin is very clear in his thread that he does not want those files posted up in other threads and to link back to his thread. Did you talk to him about creating this thread?
Sent from my SAMSUNG-SGH-I717 using XDA App
00mred00 said:
Hey just a quick heads up...zeppelin is very clear in his thread that he does not want those files posted up in other threads and to link back to his thread. Did you talk to him about creating this thread?
Sent from my SAMSUNG-SGH-I717 using XDA App
Click to expand...
Click to collapse
hmm... no i didn't read up .. i'll check it out and delete if that's the case. i been helping a lot of ppl install because they cannot - def. not taking credit for his work.
edit: he says not to duplicate his install instructions, but he is okay with sharing. so i guess i'll just share and help with questions.
Its not so much that but by going to the original thread it ensures the user gets the most up to date script. The how to is an excellent idea but some of your steps conflict his steps
Another note....#5 suggests we get a paid app via warez....that I know is against the rules you might remove that
BigBison420 said:
hmm... no i didn't read up .. i'll check it out and delete if that's the case. i been helping a lot of ppl install because they cannot - def. not taking credit for his work.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I717 using XDA App
well, i believe it's a free app... or maybe i meant "file explorer" i forget. but my market is jacked up because of a ROM issue. (can't access market)
00mred00 said:
Its not so much that but by going to the original thread it ensures the user gets the most up to date script. The how to is an excellent idea but some of your steps conflict his steps
Another note....#5 suggests we get a paid app via warez....that I know is against the rules you might remove that
Sent from my SAMSUNG-SGH-I717 using XDA App
Click to expand...
Click to collapse
Hi,
Since RC7 does not work.
What version should be used?
V6_SuperCharger_for_Android-Update9_RC6.9.sh.pdf ?
Thanks
Is anyone else really confused about the options in the script and what each one brings? I'm sitting looking at a menu, unsure what to pick :/
BigBison420 said:
ATTACHMENTS - updates/scripts FROM **ZeppelinRox**
**removed attachement update9_RC7 because it was not working on my Gnote**
MOST SCRIPTS CAN BE FOUND HERE: http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021
Click to expand...
Click to collapse
What's wrong with RC7? I installed it successfully on my phone, and it runs. Can't tell much of a difference though.
Is there something specific installation error that you are running into, or do you have a way to check if the script is running correctly? If I try to run /data/99Supercharger.sh again, it tells me the my phone is already supercharged and to verify that "Ran_Supercharger" exists in /data, which it does.
After installing Balance 3, I see no difference in the Go Launcher. LauncherPro is better than ever, and my battery life is now really good.
So... it sort of worked.
re
hey guys,
well i'm just trying to help galaxy note users out (apparently a lot of you are new to this scripting thing).
what personally works for me i recommend. That would be option 13 (bulletproof launcher) and also 768+hp settings.
keilbaca said:
After installing Balance 3, I see no difference in the Go Launcher. LauncherPro is better than ever, and my battery life is now really good.
So... it sort of worked.
Click to expand...
Click to collapse
I use go launcher and the new 2.85 Beta is available. There is a noticable increase in optimization. Lag has lessened a bit. and i'm running SauROM with Da_G's OC kernel.
BigBison420 said:
I use go launcher and the new 2.85 Beta is available. There is a noticable increase in optimization. Lag has lessened a bit. and i'm running SauROM with Da_G's OC kernel.
Click to expand...
Click to collapse
I got the latest script to run on my Note, on stock.
I seen no difference at all.
I'm throwing SauROM on it tonight, because I am having other issues too that the rom should fix, I hope. Citrix wants to auto delete the first thing it sees in Active Directory. I don't think my work would appreciate me if I deleted the entire Servers column in AD.
I would love to install this. But.your instructions differ greatly..you suggest a busting install along withal file explorer install.. He suggests script manager.
And there is some question as to which pdt we should be using.
I have a seperate thread with his install instructions linked. I referenced file explorer because i didn't realize u could mount rw. If your THAT confused u should probably not install it.
Sent from my SAMSUNG-SGH-I717 using XDA
In not confused. To the contrary, i understand almost wholly. But what isnt clear, is whether his instructions are sufficient or that they work with out note.
Its not clear which version of the script we need...or which set of instructions we should use.
Listing a set of instructions in a note specific forum (ones that differ from those elsewhere) implies that the others wont work on our device....or that something could be easier or go wrong.
Thank you for pointig the supercharger mod out. I was unaware of it. With that said, id still like to install it.
Which PDF do we use?
Jamesyboy said:
In not confused. To the contrary, i understand almost wholly. But what isnt clear, is whether his instructions are sufficient or that they work with out note.
Its not clear which version of the script we need...or which set of instructions we should use.
Listing a set of instructions in a note specific forum (ones that differ from those elsewhere) implies that the others wont work on our device....or that something could be easier or go wrong.
Thank you for pointig the supercharger mod out. I was unaware of it. With that said, id still like to install it.
Which PDF do we use?
Click to expand...
Click to collapse
i got u completely - i just listed my walkthrough because some people truly need step by step instructions lol. but the DEV's instructions are plenty IMO
my thread was designed to link instuctions for setup and also discuss which scripts are working for the Gnote (case and point, my experience with update 9RC7 which isn't working for me, but does for another user). for me update 9rc6 works fine.... i would try RC7 too - lot of nice features
keilbaca said:
After installing Balance 3, I see no difference in the Go Launcher. LauncherPro is better than ever, and my battery life is now really good.
So... it sort of worked.
Click to expand...
Click to collapse
IN GoLauncher ---> make sure you set icons to "Default Size" because using LARGE or CUSTOM is one of the main Culprits to lag.... also get the 2.85 version
I have no lag.
Anyone tried this on the ICS leak builds?
Super charger us the best mod to improve speeded etc. however this is my second phone that after super charging my phone doesn't shut down all the way. If i power off then plug it in., it reboots. Also wifi constantly looses data connection. Both issues are related to one of the supercharger tweaks just not sure which one is causing it. Maybe home bullet proof.
Sent from my SAMSUNG-SGH-I717 using xda premium

[ROM] CyanogenMod 9 / August 18 / Stable!?!

August 16
Quick note on the OP
My apologies for neglecting the original post for nearly a month! I'm a kindergarten teacher, and I've been super busy preparing for the approaching school year.
I think the OP is mostly just a tool for newcomers (especially now that support for the 201 kinda slowed down - I'm sure most of you don't need a guide to flash your daily dose of CM, and don't need an OP!).
That said, I still think it's an important tool, because there are always newcomers. The OP could just get erased entirely and this thread/the discussion would survive, but I don't think newcomers would be as likely to start using CM without a handy OP. Whether or not that matters is up to you. Personally, I like seeing CyanogenMod grow (that's what she said?), and I think a larger install base = a better CM (that's what she said?), but to each their own.
For the nxet few months, I will try to keep up with the updates, but my guess is that I'll update about twice a month. That leaves a few options: 1) just let the OP updates be infrequent, 2) start a new thread, or 3) hand over the reigns to someone else.
option 1: Not my favorite. Like I said, I think a somewhat up-to-date OP is a good thing.
option 2: Not my favorite, UNLESS a mod can merge the new thread with the old thread. Many questions and answers are in these pages, and it's nice to search within a single thread and not the entire board
option 3: My favorite! If someone else wants to take over, it's cool with me. You can even have all of the "thanks," which some people care about so deeply. I only ask that you keep it classy - like CyanogenMod - and flash the updates yourself before posting.
I know from asking the mods before that people can't "share" OPs, I know from experience that nobody wants to do a google docs OP (*sniff*), but maybe someone can take over full ownership? if not, then I push for option two, but I'd like to see this old thread live on! Yes, it's an unofficial thread, but some of the devs have posted here, and I even got dalingrin's blessing in a PM, which is enough in itself to make this thread special!
So if you want to be the OP, just ask me, and we'll ask a mod to do some voodoo. failing that, maybe I could just give you my account...? But I'm not a huge fan of that idea, because I'm still going to use XDA.
Why does this thread exist?
​TL;DR answer:
It exists so that the thread title will say something like "[ROM] CyanogenMod 9 / Updated April 3," the OP will have relevant information, and people will have a place to discuss CM9 on XDA.
It does NOT exist because I want thanks (I do not) or because I want to scam people for donations (I have no donation link).
Long answer:
Right before the CyanogenMod team began posting nightlies for the TF201, theeggman posted his own build. In his thread, he stated: "Once official nightly builds are downloadable and confirmed useable, I will no longer regularly update this build." True to his word, his build (and the OP) is no longer updated. Despite the fact that the [KANG] label does not apply to the official nightlies, and the OP is not up to date, CM 9 users like myself are still posting on that thread.
There are two small problems with using that thread: 1) CM 9 users need to check CyanogenMod to see if new builds are available, because the thread title is never updated 2) The OP does not reflect the current offerings from CyanogenMod; unless you read the thread, you wouldn't even know that nightlies exist. I posted my concerns about this yesterday, and asked if anyone would object to a new thread devoted to the official CM nightlies (and stable builds, when/if they become available). Almost 24 hours have passed, and nobody has posted any objections, so I went ahead and created this thread.
Update:
I hoped that this could become a collaborative OP, but I asked Mr. Clown, and he said that it is not possible to share editing rights for posts. However, I really think it could be helpful to collaborate on things that change frequently, especially when considering the fact that we all use our tablet differently. With this in mind, I suggested a Google docs collaboration that could get periodically copied and pasted into the OP. If you're a regular CM user interested in helping, send me your gmail and I'll add you to the doc's list of editors.
Moving on!​
CyanogenMod 9 for the TF201!​I am not affiliated with CyanogenMod in any way, shape, or form. Please direct your thanks and donations to the CyanogenMod team, or consider donating to some of the other fine TF201 ROM developers on XDA.
Alert! CyanogenMod 9 may irreversibly break your TF201. Also, you need to unlock your bootloader to install CM 9, which completely voids your TF201's warranty. You assume ALL responsibility for any damage. Use CyanogenMod at your own risk. If you are not willing to accept these risks, then do not proceed.
Features: There are dozens of websites - including the official CyanogenMod website, found below - that describe the features of CyanogenMod, so describing them here would be superfluous. If a new feature premieres on a build for the TF201, it will be noted on the build list. In a nutshell, it has a very stock AOSP/vanilla/Nexus feel, but with performance tweaks and added tools/abilities.
Screens can be found here and changelog can be found here. (thanks paddycr)​​
Some fun news about CyanogenMod 9 (and ten!)
CM10 (running Jelly Bean!) will probably come our way!
Interesting presentation by CyanogenMod founder, neat stuff, not overtly technical. Check it out for some opinions, history, knowledge of how CyanogenMod works as an organization.
Latest Nightly
Released August 16
Size: 132.79 MB
MD5: cc1621b630e54a32cea024ef8fce5444
Latest Release Candidate (RC)
Released July 19
Size: 132.49 MB
MD5: 484e9cb7318e484c84a1434921cb6de7
Latest Stable build
Released August 10
Size: 132.79 MB
MD5: 62bebfdf39cfa91a93676e363b6442c6
Known Issues​
Remember, this thread is not maintained by a CyanogenMod developer, so these issues are not necessarily going to be addressed; this is just information for people considering using this ROM.
Toggling WiFi on/off can, in certain situations, freeze and reboot the tablet (WiFi issues seem to be completely fixed!)
Screen wakes upon closing tablet dock
External SD does not support NTFS
Battery Stats usage not available (only bar graph, no apps)
CyanogenMod custom setting to skip to next/previous track using volume keys when screen is off works poorly; one track can be skipped, but the volume keys turn the screen on, reverting the volume keys to their volume behaviors. Device is NOT set to wake with volume keys.
These issues are (hopefully) compiled collaboratively by other forum members on a Google doc. If you use CyanogenMod on your Prime, your help with the list would be very appreciated!
Installation instructions​
Prior to installation, please make sure you have read and understand the red "Alert!" above.
So your tablet is unlocked has root access? Time to install a custom recovery. When your tablet has root access (helpful) and is unlocked (mandatory), installing a custom recovery is easy, thanks to some amazing apps that are freely available on the android market. If this is your first time flashing a ROM, there are a few different ways to proceed, but I would suggest downloading either "ROM Manager" or "GooManager" from the Play market: they are probably the easiest ways to install a custom recovery. Both are very user-friendly. ROM Manager will help you set up ClockWork Mod (CWM, not to be confused with CM), GooManager will help you set up TWRP.
I get a lot of questions about this, so put another way: The free apps ROM Manager and GooManager can help you install custom recovery ClockWork Mod or TWRP, respectively. You need a custom recovery to install CyanogenMod. Although incredibly helpful, you do not need need ROM Manager or GooManager, but they can help you install a custom recovery. If you're not sure which one to use, just read their threads and see what appeals to you. I'm inclined to suggest ROM Manager / CWM because they have been around for a super long time and it's included with CyanogenMod, but I have used CWM and TWRP with CM9 and they both work great.
If using CWM: You MUST use Clockwork recovery 5.8.2.0 or higher. If you have an older version of clockwork installed, you will run into problems. If you made a nandroid with an older version, make a new nandroid. I think the easiest way to update is to use the ROM Manager app, available on the market.
Update: In fact, use 5.8.2.0 specifically, which can be found in ROM Manager under the heading "all CWM recoveries" (or something) near the bottom of the list. ROM Manager may make you install the latest version of CWM before allowing you to install the alternate versions, but don't let that scare you; just flash the latest, and then flash 5.8.2.0. Apparently the latest CWM update brought some problems for the TF201? someone correct me if I'm wrong.
Have you been using Root Keeper? Great app, but it doesn't play nice with the alternate recoveries (and now that you have an unlocked bootloader, you don't need it anymore anyway - CM9 is already rooted, turn it on/off in the settings). Delete the root backup, uninstall the app, and delete any backups (like TiBu backups) you have made of Root Keeper, as well as any nandroids that include Root Keeper.
The following instructions assume that your bootloader is unlocked and you installed a custom recovery like CWM or TWRP:
1) Download CyanogenMod 9 (below) Be sure to make note of the MD5 checksum. After the download finishes, make sure the MD5 on the download page matches the MD5 on your downloaded file (there are many apps that calculate MD5 freely available on the market). Your ROM file will probably be in your downloads folder.
2) Turn off your prime
3) If docked, remove your prime from the dock
4) Holding the volume down button, turn your prime back on. When you see the white text appear in the top left, press volume up.
5) Make a nandroid backup
6) New to CyanogenMod? Wipe data/factory reset, wipe cache, and wipe dalvik cache. If you're updating from an older nightly, that step is probably not necessary.
7) Install .zip from SD card, and chose the file you downloaded earlier
8) (optional) Install .zip from SD card, and chose the gApps
9) Reboot!
ALSO: Thanks to disturb3d1, you can watch his how-to-install-CM video here. Unlock, root, custom recovery install, and all sorts of other how-to videos are also available.
Download CM 9
As this ROM is build from stock CM sources the GPL parts can be found in the official CM repo (thanks Diamondback)
Download gApps
The gApps link is for April 29, 2012.
http://www.cyanogenmod.com/​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
No need for disclaimer. Warranty is voided once you unlock your bootloader.
Thanks jdeoxys
Itaintrite said:
No need for disclaimer. Warranty is voided once you unlock your bootloader.
Click to expand...
Click to collapse
It seems like other ROMs that need bootloader unlocked to install still have some kind of warning. I'll take it off if you're sure, though.
Thanks for the thread. I don't think I will flash CM9 again until some more features are added, but its great to keep tabs on.
Transformer Prime/Galaxy Nexus CDMA
It's not the ROM that voids warranty but unlocking the bootloader.
As long as you can restore your device at initial factory state your warranty is preserved. For example on my phone I just have to use nvflash to restore a full stock ROM and to have a brand new factory device.. because on LG phones bootloader is open.
So you can remove those warnings, and people know what cyanogen is, even if I'm surprised by the proportion of total Android noobs here (seems like the prime is the first Android device of many here).
Itaintrite said:
No need for disclaimer. Warranty is voided once you unlock your bootloader.
Click to expand...
Click to collapse
Brave man to do that. I would expect that a noob could make a reasonable case for arguing that he assumed you'd thoroughly tested the rom before posting links to it.....
Remember also, users from different jurisdictions read these forums. Having a general disclaimer is unlikely to be a bad idea.
IMHO.
Sent from my Transformer Prime TF201 using xda premium
tangiers said:
Brave man to do that. I would expect that a noob could make a reasonable case for arguing that he assumed you'd thoroughly tested the rom before posting links to it.....
Remember also, users from different jurisdictions read these forums. Having a general disclaimer is unlikely to be a bad idea.
IMHO.
Sent from my Transformer Prime TF201 using xda premium
Click to expand...
Click to collapse
+1
Sent from my Transformer Prime TF201 using xda premium
although file size seems 119.30mb, the download file size is 59.3mb
can you check please?
ayk33 said:
although file size seems 119.30mb, the download file size is 59.3mb
can you check please?
Click to expand...
Click to collapse
There is nothing to check, he doesn't maintain the server, which is cyanogen one.
And he mentioned in OP that there is an issue with latest nightly download.
Try to report directly to Cyanogen or wait for a new build.
I thought the same thing when i was downloading the file i did it twice but didnt make no sence from 59mb and then sometimes a 79mb n looking at the right 119mb no wonder i was updating it on my table n said it was a bad file SMH LOL
Sent from my Transformer Prime CM9 using XDA Premium App
tangiers said:
Brave man to do that. I would expect that a noob could make a reasonable case for arguing that he assumed you'd thoroughly tested the rom before posting links to it.....
Remember also, users from different jurisdictions read these forums. Having a general disclaimer is unlikely to be a bad idea.
IMHO.
Sent from my Transformer Prime TF201 using xda premium
Click to expand...
Click to collapse
+1 10 char
OP
Thanks for the thread . If someone doesn't like it, then just don't read it.
if you want to add this link, it's the changelog for the prime that includes what has been added to the nightly and what's in the works for the next one.
http://cm-nightlies.appspot.com/?device=tf201
So far what I can see there are the general Cyanogenmod changes, nothing specific for our Prime.
apascual89 said:
OP
Thanks for the thread . If someone doesn't like it, then just don't read it.
if you want to add this link, it's the changelog for the prime that includes what has been added to the nightly and what's in the works for the next one.
http://cm-nightlies.appspot.com/?device=tf201
So far what I can see there are the general Cyanogenmod changes, nothing specific for our Prime.
Click to expand...
Click to collapse
Wow, nice! That's awesome, I never saw that before. Adding now!
The direct DL for the nightly is bad for some reason, but the BT link works just fine and is the full file too.
EDIT: Won't be flashing
Yes, there is something weird with all the direct HTTP download mirrors for the TF201 (yes, all)... as @hakarune said, use the torrent link... it works and so does CM9... been using this since the previous nightly and loving it so far!!! That said, can't wait for more features like notification power widgets...
hakarune said:
The direct DL for the nightly is bad for some reason, but the BT link works just fine and is the full file too.
EDIT: Won't be flashing
Click to expand...
Click to collapse
It seems like the build bot has been having some trouble. The Galaxy Nexus nightlies have been iffy at best lately.
hakarune said:
The direct DL for the nightly is bad for some reason, but the BT link works just fine and is the full file too.
EDIT: Won't be flashing
Click to expand...
Click to collapse
Sorry, do you mean that you won't be flashing because it doesn't interest you, or are you running into an error when flashing? I ask because the file size does not match the size (about 125 MB) does not match what is listed on the CM download page. In the past, I downloaded directly from the URL or within ROM manager, not BT, is it normal for the .zip file to differ in size?
And thanks for pointing out the BT option, I tried searching for a torrent, but always ended up at the CM download page... I didn't realize that the torrent link was right there!
This is why I wish the OP could be collaborative... I can update what other people post, but it would get updated so much more quickly if others could edit the OP. How about I make a google docs file, give the link to people interested in helping, you can edit whenever, and I'll just periodically copy and paste the google doc into the OP?
I don't have time to try this right now, but I can't wait to try the April 3 nightly!
Komodo Rogue said:
Sorry, do you mean that you won't be flashing because it doesn't interest you, or are you running into an error when flashing? I ask because the file size does not match the size (about 125 MB) does not match what is listed on the CM download page. In the past, I downloaded directly from the URL or within ROM manager, not BT, is it normal for the .zip file to differ in size?
Click to expand...
Click to collapse
Download sizes do vary, but not by that much. The size deviation should be somewhere around 2-5mb. That's a guess. If the file size is much different, there is a problem. Basically each nightly is the same with minor changes that shouldn't amount to much more than a couple of megs.
Edit: I should add that, in my experience, if the nightly is bad CWM won't flash it at all.
Fan of Cyan..
Ok so being a Fan of Cyanogenmod, Hell my Evo shift still runs a modded form, Is the 125mb torrent flashable? or not? i would love to get this on my prime, Anyone?

[KERNEL] The SickKernel

Welcome One X+ users, this is the SickKernel. What you can expect over time is more and more features.
Changelog:
Code:
11-20-12
Removed userspace govenor
set ondemand govenor default
used newer toolchain
Directions to flash
Code:
Go to fastboot, from android type adb reboot bootloader
download the image
cd to your downloads folder
issue the following command
fastboot flash boot sickkernel-0_0_1.img
Source ->
Bugreports go
Note,
If WiFi doesn't work let me know about it. I am trying a new method of kernel packaging which may backfire. If this happens, there is an easy fix. Enjoy! Also I don't own the device. I have some testers, but if a kernel doesn't boot I have no way of knowing sometimes. Don't be afraid to tell me issues
MOD Edit: Removed DL-Links as OP isn't xda-member anymore
I'd recommend you saying that this is for the Int'l model and not the AT&T model.
Well, it won't cause bricks to flash it wrongly. Besides no one knows if the devices have a definitive difference that prevents it from booting. On a side note, this currently uploaded boot.img has the ramdisk of a cm10 ROM. There for it will bootloop sense
Sent from my PK7630000 using Tapatalk 2
nice to see another one working on this Are the AT&T versions of phone totally different ?? (Other SOC, or something else that prevents it from boot ) ??
n3ocort3x said:
nice to see another one working on this Are the AT&T versions of phone totally different ?? (Other SOC, or something else that prevents it from boot ) ??
Click to expand...
Click to collapse
a totally different base yes not phone, lots of bricks trying to flash international HOX+ software
Look up my kernel release, I think I pretty much nailed down module embedding. There's a total filesize limit it seems on the boot.img but it works.
I can release the framework I'm using, all scripted out to 2 simple commands if you want.
Hi sir could you add call recorder feature into your kernel in such a way we can record calls with the Bluetooth audio ear phone connected....hopefully this can help you
http://forum.xda-developers.com/showthread.php?t=1971302
Just a hope sir
Rgrds
I think you should specify on the top of the OP that this is not for ATT. Hopefully they will split forums for the HOX+ development and add a seperate ATT forum, but until then there will be plenty of havoc over all of these dev threads that are not specific on which device they are for.
Dont mean to bust balls, but Noobs are noobs.
Okay, so gonna do some catchup here. I accadently threw the wrong ramdisk in this kernel (my bad) This will be fixed soon after the holidays. Next terms of buisness, the module is inside the boot.img but i dont have the device so I cant test it. Next, kernels are kernels. The very nature is compatability. How many people bricked there PC trying to install a new kernel. None, would be the answer. When ATT source is released, I will merge the two together, and build one compressed kernel that boots on both. Next line of buisness, features will be slow.. Im helping lloir with something currently.
And finally, because some people are total idiots, and cant use common sense the source is at
github.com/simonsimons34/htc_enrc2b_kernel
simonsimons34 said:
Okay, so gonna do some catchup here. I accadently threw the wrong ramdisk in this kernel (my bad) This will be fixed soon after the holidays. Next terms of buisness, the module is inside the boot.img but i dont have the device so I cant test it. Next, kernels are kernels. The very nature is compatability. How many people bricked there PC trying to install a new kernel. None, would be the answer. When ATT source is released, I will merge the two together, and build one compressed kernel that boots on both. Next line of buisness, features will be slow.. Im helping lloir with something currently.
And finally, because some people are total idiots, and cant use common sense the source is at
github.com/simonsimons34/htc_enrc2b_kernel
Click to expand...
Click to collapse
Simple edit to help solve a simple misunderstanding. Your thread, your rules, though.
Hi, how about sweep 2 Wake?
Sent from my GT-N8000 using Tapatalk 2
Thread closed
As the OP had a wrong assumption about the consequences of breaking xda rules, and preferred to withdraw from xda subsequently, I closed this thread.

Categories

Resources