yashsingh1/xdaforums huggingface dataset:
[TouchPad Development] johnsmith33584:
Like the way NT always makes us think a little harder. :good: Actually, as long as the name of the file for TPtoolbox includes uImage, Moboot includes in the menu. So a new Moboot should not be needed unless Mr. Sullins puts the toolbox file in a different location than /boot. That will probably require a slight modification so Moboot knows where to find it.
[TouchPad Development] johnsmith33584:
[MENTION=4788115]synchron50[/MENTION],

Don't know if you want to play lab rat on this, but here is an idea. Run ACMEUninstaller. Use the toolbox to install TWRP, CM10.1 and Gapps. Use TWRP to to make a quick Nandroid backup of what you already have installed. Now copy the backup you saved on your PC to the serial number folder that making the backup created. BTW, which TWRP did you use to make this backup, the new on or an older one. Whichever TWRP you used, use that to restore the backup.

Same thing goes for trying to restore your CM11 backup. After CM11 is installed with the toolbox, run TWRP so the serial number folder is created by TWRP. Place the backup in that s/n folder and restore the whole thing. Use CWM to flash the new TWRP or you can use a root enabled browser to replace the old TWRP with the new one, same thing for CWM.
[TouchPad Development] synchron50:
I think I'm done for now (and TWRP) and will continue to make backups in CWM now that I don't have to rely on the buttons and can touch the screen.. The fact that the newer 2.7 version is having difficulty in finding backup paths that are clearly there and it won't mount USB means that TeamWin needs to spend more development time and fix these issues. A recovery better be able to be backwards compatible with previous versions and the new CWM seems to fit the bill.

However, I do recommend that in a future Toolbox, to auto create the backups/<SN> folder if possible. That's a damn long serial number to write down and create manually.
[TouchPad Development] johnsmith33584:
That was my point in suggesting making the quick backup and let TWRP make the s/n folder for you. I'm thinking that if you had done it that way, TWRP would have found the backup. No point copying that long number, let TWRP do the work for you. And I perfer Touch CWM myself, that there are those steadfast TWRP users who need to know the pitfalls of using it and if it can be made to behave. Older versions of it did not seem to have that problem, can't imagine the newer one went that far off the rails. However, I would recommend sticking with Flintman's version of TWRP. Mpgrimm's thread does mention that it can see both SD cards and cannot mount USB, so that did carry over to the newer version.
[TouchPad Development] jcsullins:
First, I don't think there is any official version of TWRP 2.7 for the Touchpad provided by TeamWin, so please be very careful about laying blame on them for problems that you may find in unofficial versions that I or others provide.

Second, there is more than one (unofficial) build of TWRP 2.7 out there for the Touchpad, so you need to mention exactly which build you are using. Post #3 of this thread has download links (3 download links to same file) for the only build of TWRP that may be used with tptoolbox at this time. I modified the TWRP source so that it will show the version as "v2.7.0.0 (jcs 2014-05-12)" so you can easily verify if you are using the correct build.

Third, I just tested TWRP ("v2.7.0.0 (jcs 2014-05-12)" linked from post #3 of this thread) now for the issues that you mentioned and was unable to reproduce them. The "Mount USB Storage" worked as expected and it listed a backup that I copied from my PC. I suspect "Mount USB Storage" didn't work for you because you were using some other build of TWRP. I suspect it didn't list the backup because you didn't create the directory structure for it properly. It needs to be TWRP/BACKUPS/<SN>/<backup name>/<backup files> (not TWRP/BACKUPS/<SN>/<backup files> for instance) and the SN is case-sensitive.

Also, tptoolbox does not create the TWRP folder, TWRP does.

The build of TWRP that I link in post #3 of this thread is the only build of TWRP that tptoolbox (currently) supports. I would appreciate it if you did not suggest that people use recoveries that tptoolbox does not support in the tptoolbox thread.

I've spent a considerable amount of time putting together the recoveries to be used with tptoolbox. Back in March I released builds of CWM and Philz-CWM. At the time, people were curious why I was releasing recoveries "all of sudden" (this was before I released by CM11 build). I was putting them together to be used with tptoolbox.

It took me longer to get a solid build of TWRP put together. Like the CWM and Philz-CWM builds above, it sees both SD cards and can 'mount the USB'. Not sure why it isn't listed in Mpgrimm's thread. I guess since it was 'released' along with tptoolbox in this thread, it didn't get noticed like Philz and CWM above.

Oh, BTW, since we're on the subject of recoveries... there will be 6 (six) new recovery builds released with the next version of tptoolbox. :)
[TouchPad Development] jcsullins:
Some of you have noticed that the next version of TPToolbox has taken longer than I originally stated. I had originally planned for it to be more of a minor update. However, for various reasons, it's not turning out that way.

TPToolbox is designed to prevent errors (as much as possible) before they happen. Using the wrong version of GApps for the ROM is one of the errors it tries to prevent. Using the wrong type of recovery (i.e. datamedia vs non-datamedia, in particular) is another. So TPToolbox needs to know the versions of the ROM, GAaps and Recovery to know if they are compatible. TPToolbox also needs to know what type of ROM (i.e. datamedia vs non-datamedia) you are installing so it can resize the volumes appropriately, if needed.

Currently, it determines all this information based on the zip file names. There's been a bit of discussion recently about which versions of ROMs, GApps, etc. TPToolbox supports. What it currently supports is clearly stated in POST #3 of this thread. The use of filename-based detection and the inherent limitations of using such was always intended to be temporary.

I've been working hard to replace this filename-based detection system with a more flexible system that inspects the contents of the zip file to determine the information TPToolbox needs. Based on my testing, this new system should allow you to install anything from ICS to KitKat with TPToolbox. This new system will be in the next version.
[TouchPad Development] johnsmith33584:
Sorry, my bad. I didn't catch the fact that the version of TWRP in post 3 was a custom version built by you. Can't wait to see your next version of touchpad toolbox. Excellent work!
[TouchPad Development] synchron50:
My, apologies. I didn't want to put down TeamWin, rather, to praise Philz/your CWM.

Yes, I was definitely using the version from post #3. When I first used tptoolbox without CDR and keeping WebOS, after the installation 2.7.0.0 TWRP I did see TWRP backups on Sdcard1 but not Sdcard. So, maybe johnsmith has a point in that the TWRP app itself has to create these folders. Is it a Linux permissions thing?

As I explained, Philz/your CWM recovery easily saw my CM11 backup after I created /BACKUPS/<SN> under the TWRP folder. I did this on the fresh install of CM11 in USB MTP mode. As far as 'Mount USB Storage' issue, I have no clues but when I get the next chance, I will look into adding it to the boot menu and see if its repeatable. I will also try the last known version that mounted USB with no issues which is 2.6.3. Also, on the same subject, even the mount feature in tptoolbox only shows the much smaller Sdcard1 volume which only contains the zips from ttinstall and an Android/data folder with a handful of other empty folders starting with 'com.' I'm very new (and slowly learning) to this new data-media concept but so far under CM11 I only see both volumes with the USB MTP method, not the USB Mass storage method which treats each volume as a drive letter on the W7PC. The file xfer rate is also much higher using the latter method so that's one good thing I miss from WebOS.

---------- Post added at 10:02 AM ---------- Previous post was at 09:56 AM ----------

This is excellent news! Great job and thanks for your continued support of the HP Touchpad! I'm already starting to see on ebay used TP's with no WebOS on them. If you ask me, for each one sold, you should get a residual (like at least 15%, LOL).
[TouchPad Development] Moody66:
Someneselling links to it as well. This should be illegal.http://www.ebay.com/itm/NEW-HP-Touc...ablet_eReader_Accessories&hash=item233bea6db9
[TouchPad Development] vqstaphbeard:
That's pretty darn low! "My instructions will explain..." They probably just copied Roland's instructions :(
[TouchPad Development] Moody66:
I agree. Devs need to report it to eBay. They have policy on selling such things. I flagged it to eBay myself. And told the guy it was BS as well.
[General Questions and Answers] androidthx:
Hello!

I own Measy Android TV Dongle (U2A) with Jelly Bean inside.

Is there any way to force this device to display screen in portrait mode? I purchased it to display the content of specific website, which would be much better displayed if TV is hang vertically.

I have tried many apps available in Google Play store, but without any success, so maybe after rooting this device I shall be able to switch into portrait mode?

Thank you for your help in advance.
[Galaxy Note 3 Themes and Apps] alex00006:
what????????????????????
[Galaxy Note 3 Themes and Apps] dudu7559:
It was a launcher, indeed.......... it didn't launch anything at all lmao
[Galaxy Note 3 Themes and Apps] Er. Aditya:
if you need subscription for this thread lemme know
[Galaxy Note 3 Themes and Apps] GuestK0079:
I rated this thread 5 stars.

Sent from my N9005
[Galaxy Note 3 Themes and Apps] eddielopezusa:
Oops sorry i forgot to put the launcher
[Galaxy Note 3 Themes and Apps] 4l3gU:
Link is down...please a mirror on dropbox or mega.?

!rorrim eht morf klatapat htiw detsoP
[Galaxy Note 3 Themes and Apps] coelho_:
:banghead:
[HTC Pico (Explorer)] [DEV]:
I am using CM9..GTA 3 gives force close error i have flashed cm7 lib but the problem is still not solved..i also tried using chain fire but no use any who knows how to fix??? help:confused:
[HTC Pico (Explorer)] rantinasha:
Well GTA on HTC possible at first?? m still thinking..:confused:
[Galaxy S II Q&A, Help & Troubleshooting] ansariaamir_leo:
I have recently rooted my phone and using MIUI and Siyah-s2-v6.0b4 Kernel. I followed steps from a tutorial. It was working fine until yesterday. I was on Instagram when the phone froze on that screen. I left it as it is. It stayed like that for some time and then it rebooted automatically. The phone shows initial Samsung Galaxy S2 screen and after that it goes blank. The boot animation doesn't load. If the press the Home Key 4 times, it shows a bright white screen continuously and stays like that. And the screen turns off when I press the home screen 4 times. Nothing else happens. When I try to get into recovery mode it gives me error Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. The phone worked perfectly and suddenly this happened. I had tried updating when I got the MIUI update notification. It downloaded the update, rebooted the phone automatically and phone started normally and I got the update notification again. Please help me fix my phone. I need it as soon as possible. And sorry if I posted in the wrong section.
[Galaxy S II Q&A, Help & Troubleshooting] MistahBungle:
Download stock rom for country/carrier from Samfirmware, boot into download mode, flash with Odin following instructions in thread stickied near top of Q&A titled 'Flash stock firmware', problems with flash = find Hopper8's 'Odin troubleshooting' thread stickied in General, it has all the info you need to get a successful flash.

Once you've done that, re-root your phone & restore nandroid backup or re-flash custom rom/kernel & start again.

But frankly, you should already know this stuff if you're modding your phone. Not knowing how to recover when things go wrong (and they do for everyone sooner or later) potentially leaves you without a working phone for hours (at least), especially given S2 Q&A doesn't get as many posters or people answering other people's questions as it used to.
[Galaxy S II Q&A, Help & Troubleshooting] ansariaamir_leo:
Have downloaded the stock ROM, tried flashing it but it got stuck on

<ID:0/009> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> I9100XWLST_I9100ODDLSE_I9100DDLS9_HOME.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/009> Odin v.3 engine (ID:9)..

<ID:0/009> File analysis..

<ID:0/009> SetupConnection..

<ID:0/009> Initialzation..

<ID:0/009> Get PIT for mapping..

<ID:0/009> Firmware update start..

<ID:0/009> boot.bin

<ID:0/009> NAND Write Start!!

No progress after this point.
[Galaxy S II Q&A, Help & Troubleshooting] Hopper8:
Did you even read what my thread said? Or what MistahBungle wrote?

The whole purpose of my thread is to troubleshoot Odin flashing errors. Time to read it and do what it says. As MistahBungle says, there's nothing missed out in that thread. If, after trying everything in that thread multiple times, you don't get it to 'take' a flash, then time for a service centre/new motherboard.
[Galaxy S II Q&A, Help & Troubleshooting] MistahBungle:
OK...

You're obviously not someone who pays attention to the help they're given, so I'm going to repeat what I said in my last post once, and then I'm not posting to this thread again...

'Problems with flash = find Hopper8's 'Odin troubleshooting' thread stickied in General, it has all the info you need to get a successful flash'.

If you want your phone fixed, you go through as many of the troubleshooting steps in Hopper's thread as many times as you need to.

You are the only person who can fix it. We can't fix it for you. I've given you the tools to fix it, go fix it. Or not. I don't care. But I can guarantee you one thing, if all you do is post 'But it won't work !' to this thread when I've given you the tools to get it fixed, your phone will probably still be busted this time tomorrow.
[8125, K-JAM, P4300, MDA Vario General] LEROI:
I have done some searching but feel free to slap me a round a little if I should have been able to find this.

Does anyone know how to prevent Goodlink 4.9 from autostarting?

At times I want to keep the memory free and would rather start it manually when I need to..

Thanks!
[8125, K-JAM, P4300, MDA Vario General] Bratag:
\windows\startup - remove the link to goodlink?
[8125, K-JAM, P4300, MDA Vario General] LEROI:
There is no link in the Startup Folder...

Anyone else? Registry perhaps?

Thanks...
[8125, K-JAM, P4300, MDA Vario General] LEROI:
Anyone? :)
[8125, K-JAM, P4300, MDA Vario General] elorimer:
I have 4.8.1.14. It doesn't autostart. I know that isn't much help.
[8125, K-JAM, P4300, MDA Vario General] LEROI:
It starts after a few minutes, correct?
[8125, K-JAM, P4300, MDA Vario General] fordcan:
Look at the notification que with memmaid or sktools or search for in this forum for notification clear or something like that. That might help
[Android Apps and Games] mikereidis:
Usage:

If a boot loop would ruin your day, please see warnings at top of post #1 and don't install this app until more mature.

Disclaimer: Please understand that this is the first public release of this app. Although I endeavour to make my apps as safe as possible, one never knows whether or not some silly bug or unusual interaction might pop a speaker, headset or whatever. I have over 20 devices that I use for testing my apps and I try to "torture test" as much as possible. So if something goes pop, I'll be very sorry and do everything I can to analyze and fix any problems. If you're "not sure", just wait and more adventurous people will do the early testing needed to help ensure nothing breaks.

By it's very nature, any app that can boost volume creates risk for audio output devices as well as your ears.

To select output volume or input gain, swipe left or right or use the tabs. The primary/left screen is for output volume.

Set the enable switch to ON to enable volume/gain adjustments.

The Left and Right indicators are logarithmic/DB audio level indicators, updated every 0.1 seconds with the peak audio level. These show the signal level before amplification. If they are VERY near the full width of the screen, there is little amplification that can be reasonably done. (But 80-90% leaves some room, given the exponential nature.)

For no boost, IE an amplification factor of 1.0, the Coarse and Fine controls should both be set to 0 at centre.

Setting Fine all the way right to +6 dB doubles audio power, setting to -6 dB halves audio power.

Setting Coarse to +30 dB creates an amp factor of 32, assuming Fine is set to 0. Setting -30 dB is about 0.03.

Note that an amp factor of 32 is very high, unless you are dealing with very low input signals.

The Shim detects when the signal will overload, and reduces the amp factor as needed to prevent overload/distortion. To raise it again, use the UI to reset.

There are some "streams" for which amplification will not work. I will support as many stream flags (such as Fast) as I can; remains to be seen; this is still kind of a "research project" at this stage.

At present, all streams are amplified the same amount. Per stream or stream type amp factors will be supported.
[Android Apps and Games] mikereidis:
Just go to post #11 on next page.
[Android Apps and Games] mikereidis:
Nothing to see here, move along.
[Android Apps and Games] mikereidis:
Technical info to fill in later.

Pay no attention...
[Android Apps and Games] mikereidis:
... to the man behind the curtain...
[Android Apps and Games] mikereidis:
8 is lucky 7 + 1; even better.
[Android Apps and Games] mikereidis:
Trouble-shooting info.
[Android Apps and Games] mikereidis:
#10 is always "Future". :)
[Android Apps and Games] mikereidis:
Comments and questions start here. :)
[Android Apps and Games] Rinoceros:
Volume control?

Hi Mike,

You are making me curious about this new project of you.

I bought a long time ago this app for level control. It is doing his job, but has lack of storing the settings and sometimes still adjust (unwanted) the volume.

Count me in for testing :fingers-crossed:

Edit: get an error parsing the apk :crying:
[Android Apps and Games] mikereidis:
Welcome to my new thread and app. :)

AFAICT, that app mostly just manipulates standard Android volume levels, which is fine, but not much different than the standard volume control.

I just downloaded my new app linked http://d-h.st/plb myself (7 downloads in first 2 hours now), and it installs fine on my One M7, and matches bit for bit the 1.0 version installed on my test phones.

So you're on stock based InsertCoin ROM ?

As long as it's Android 4.4 KitKat (API Level: 19), it SHOULD parse and install OK.

The binaries are for ARM devices only (ie 99+% of Android devices). Intel x86 or MIPs can't work (at present.)

I can't think of any other reason it won't parse, unless your copy is corrupted. This is the MD5 I get:

md5sum ~/Downloads/av-release.apk

2c8328e8cbe1f585f3b1634e36200c8f /home/mike/Downloads/av-release.apk

I'm happy to hear anyone else's stories of success or failure, but I'll need a good 7 hours of sleep first.

------------

Happy Victoria Day to all fellow Canadians & CommonWealther's, and Good Long Weekend to all those with a day off of work this Monday. Finally nice weather here lately... :)
[Android Apps and Games] Rinoceros:
Aha, here might be my problem. My InsertCoin is still the good old JellyBean 4.3 (I am happy with this version and had nearly no problems and all the stuff is working on this one. So if it ain't broke; don't fix it ;))

Got the same MD5: 2C8328E8CBE1F585F3B1634E36200C8F

I am confused or it doesn't work on 4.3

Sleep well!
[Android Apps and Games] Draw Em!:
4.4

Does it work on Android below 4.4?
[Android Apps and Games] Lagkage:
Can't wait to try it. Your work with Spirit was amazing, so I am sure this is too.
[Android Apps and Games] pilgrim011:
Thanks for the effort, but it ain't working on i9100, cm 11/kk 4.4.2. Tried to increase volume a little (level was about 3, but as you know, first written value is 5), there was a very strange noise as I tried to.increase volume via volume buttons while listening music via headphones. It was a crackling noise, looked to me like the phone is going to get damaged, so I removed HAL and uninstalled your app.
[Android Apps and Games] mikereidis:
:)

Here's a v1.0.2 test release that will install on Android 2.2+: http://d-h.st/QfV
[Android Apps and Games] mikereidis:
It may. Here's a 2.2+ test release: http://d-h.st/QfV

Chances are lower the lower the Android version. I'd recommend 4.1+, but it may work on some Android 4.0 as well. Android 2.3 GB and older used a "legacy HAL API" which won't work.

At this time it's a "bleading edge" release, and most people comfortable with that have been running 4.4 the last 6 months, I'd think.
[Android Apps and Games] mikereidis:
It sounds like it was working then, as it does for me on my 9100 with CM11.

In many circumstances audio amplitude will already be maxed out, and trying to increase volume will only result in the automatic gain control kicking in with a different value many times per second, thus leading to distortion and other audio "artifacts".

This solution is more helpful when, for some reason, the audio source material doesn't use the full 16 bits of amplitude. If the VU indicators in the app are showing peaks around 80-90% of the screen width, when the normal volume control is maxed, then amplitude is probably above 16,000 and could be near the absolute peak around 32,000.

For example, some audio may have been recorded that only peaks around 4,000 - 8,000, and for this, and amp factor of 4 may be useful. Another possible solution for this scenario is to enable Compression in DSP Manager or whatever. As with everything, this has pros and cons.

In many circumstances, when possible, it's better to raise analog gain, like Voodoo sound does on the Galaxy S GT-I9000. I'm going to look into this, but this sort of solution is very audio chip dependent.
[Android Apps and Games] Rinoceros:
Hi Mike,

Thanks for the effort, but it is not working on my InsertCoin 4.3

It is not booting at all.

You are replacing the HAL but if it is not working, you are not able to copy the original back (at least in my case).

Had to restore the nandroid backup.

Keep up the good work!