yashsingh1/xdaforums huggingface dataset:
[MDA, XDA, 1010 Software Upgrading] auburnham:
I don't want to make this any more complicated than it is, but for some programs, it just doesn't make any sense to install to the XDA memory. Most of the media players and "Misc" programs just take up too much unnecessary device memory when they would work just as well on the SD Card (if that's available).

The problem is that those huge programs require just a few small files to be placed on the device itself. So after installing a few of these types of programs, you've used up a lot of device memory from these small files, even though you installed the program to your SD Card.

Is there a way to alter the kitchen a bit to allow cooking of the necessary device files only, and allow the user to later install the program to the SD Card (being careful not to overwrite the files in ROM with files in RAM)?

For instance, with the TomTom program, if you start with a clean ROM and SD card, take a snapshot, then install the program to your SD card, then take another snapshot, you could determine what files need to be on the device, and what files don't need to be on the device, and allow users to either cook the entire program or just the necessary files in the ROM. (Note: This is a good example of a run-on sentence). Would this be a difficult feature to add to the kitchen?

Shawn
[MDA, XDA, 1010 Software Upgrading] LumpiStefan:
Maybe the esiest Option is adding a new Select Point for the kitchen like "misc", "System Tools", "Phone" ....

This means having the programs double in the kitchen, but how cares.

I don't know exactly, but when you install a program to the SD-Card, could you select the part where to place it?

If yes, this could be a big problem. Many of the programs store the path in the registry.

If no, i could also provide a ZIP-file, where the rest of the programfiles are in, hust to unzip to the Storagecard.....

Sounds good. I'm hungry all the time.... ;-)

Stefan
[MDA, XDA, 1010 Software Upgrading] auburnham:
I believe this really depends on (1) how well the program was written, and (2) if you can install the program with CabInst (i.e. has a cab installation).

For example, I try to keep my SD Card organized and tidy so if I use CabInst I install the program to an appropriate folder on the SD Card. If I have to install the program from the desktop, I install the program to the SD Card root, then try to move the program to an appropriate folder and update the shortcut. Most of the time this works without even changing any registry entries, but sometimes it doesn't. Two examples from the above list of applications are AOL Instant Messenger 2.0 and Pocketmind PocketMusic 3.0. To function correctly, they both need to be in their original installation folders on the SD Card.

But perhaps the best solution would be to have an associated .zip file to go on the SD Card, as you suggested.

Shawn
[MDA, XDA, 1010 Software Upgrading] LumpiStefan:
Now the kitchen should be up 2 date again.

Only missing is PocketConsole and the Part "Software that needs to register"

So happy cooking and again Thx a lot to all users that helped me.....

Stefan
[MDA, XDA, 1010 Software Upgrading] Marton:
A Windows-way for cooking a ROM would be great for two reasons: 1) Don't hassle your server with lots of traffic and 2) Practical. Advanced users could cook a ROM without having a PC with Unix.

For example I tried cooking the Spanish version of the ROM and not all the programs I chose were installed and the worst thing is that the boot logo was just garbage, it was showing program code on the screen as a logo :)

Regards,

Marton
[MDA, XDA, 1010 Software Upgrading] LumpiStefan:
Ok. Fixed the problem with the bootscreen.....

Tried also adding as much application, and all have been installed.

Can you tell me, what files / programs are missing?

No one else told me that there have been a problem wirth this ROM. I think it's because of the situation that most of the useres are using WM2003 ROMS....

You can also use the kitchen under "Windows" just have to set up a Cyguin environment on your system....

Also i didn't know how many Kitchen's are implemented by other users, but mine one is the only "official". You can't believe that everyone would be able to set it up.......

Stefan
[MDA, XDA, 1010 Software Upgrading] Marton:
Thanks Stefan!!!!!!

Now it seems to work but if EzWAP is selected, it throws a Log error when trying to cook...

Cheers,

Marton

P.S.: Do you know if a Spanish WM2003 exists?

Edit: This is the error:

Cannot fit files in given sections

Error splitting files
[MDA, XDA, 1010 Software Upgrading] Marton:
Just cooked a ROM... I selected the "Windows Mobile XDA" Boot Screen and now it is not garbage anymore but now it shows mirrored and upside down...

Any ideas?
[MDA, XDA, 1010 Software Upgrading] LumpiStefan:
Hello Marton.

I relaised that this is a problem with the Image.

This Image have been sent to me, and i ithink it's created wih the wrong parameters....

Stefan
[Galaxy S 4 Q&A, Help & Troubleshooting] nezhina:
I saw a youtube-clip where a guy demonstrated that u could use a pen (or other objects) to control the screen. Was going to try this in a meeting today, but the function seems to be deactivated. I have browsed through the settings and can't find the option to active this.

I have tried the setting enabling the use of phone with a glow, but it wont recognize any of my pens.

Anyone know?
[Galaxy S 4 Q&A, Help & Troubleshooting] Will T:
Any chance of a link of the YouTube clip to see? I'm pretty sure those pens would've been a capacitive type for it to work on the screen. There are even some that look like a ball point pen, but is actually capacitive.
[Galaxy S 4 Q&A, Help & Troubleshooting] nezhina:
This is one of them:

http://www.youtube.com/watch?v=eEdLhRzGi-U
[Galaxy S 4 Q&A, Help & Troubleshooting] echohack:
Under display settings all the way dow youll see a box for high touch sensitivity. Maybe that one will make it work
[Galaxy S 4 Q&A, Help & Troubleshooting] nezhina:
I have tested some more now and it seems to be able to recognize objects of metal. Dont understand how the guy could control it with a bottle then :)
[Galaxy S 4 Q&A, Help & Troubleshooting] Will T:
Wow! I stand corrected and humbled! He definitely mentioned "conductive", but all the objects he used were everyday objects! I even tried with a pen and it worked! Didn't even have to enable the extra sensitive function. Gonna get a milk bottle next to try, haha! :laugh:

Are you using any screen protectors (film or glass)?

I know on mine, it's a matte finish, but they say that gloves and capacitive pens would still work.
[Galaxy S 4 Q&A, Help & Troubleshooting] simacca:
The s4 is going to feature on Watchdog next Wednesday at 8pm on bbc1. I believe the main story is to do with the advertised 16gb not being available to the user.

I would of thought the screen smearing problems be the main thing for them to focus on after reading through these forums?

Anyway I thought this would give people a chance to contact Watchdog for next week's show and maybe they will address the screen problems too.
[Galaxy S 4 Q&A, Help & Troubleshooting] i.amtom:
If you've downloaded screen adjuster to remove the screen smearing it may be the reason for a lot of lag.

I realised it caused a lot of stuttering on the home screen, try it yourself and get back to me.

Try uninstalling the app or turning the dials of rgb to 0.

Shame we have to choose between problems :(

P.s. Please move this to troubleshooting forum, sorry.
[Galaxy S 4 Q&A, Help & Troubleshooting] btemtd:
I already mentioned this in the thread Bala.Gamer opened in regards to the smearing fix....

The trick fix is... Leave all RGB to zero and turn the contrast between -15 to -20

This fixes the lag... But anyways I removed the whole app anyway who cares about the smearing... Samsung should fix this soon Ill put up with it till then,
[Galaxy S 4 Q&A, Help & Troubleshooting] Idan73:
I just think of it as extra animation effect.

JKAY DELUXE [I9300 JB 4.1.2]
[Samsung Epic 4G Touch] Chillyz12:
I have a question.

But first I want to say thanks to: dsixda For making the Kitchen, Stryke_the_Orc , bilgerryan , and tdunham, For answering my questions when Google couldn't. and also kobridge for his hard work and contributions to our community as well. Almost forgot to mention tdunham's VERRY COOL!!! AIO mod-----> xdaforums.com/showthread.php?t=2149900.

Thanks to you guys I have Deodexed, modified, and successfully flashed my first custom rom.

My question for anyone who knows whould be how can I replace the stock touchwiz launcher with Nova launcher bfor building my working folder in to working rom? If I install Nova then uninstall touchwiz after the flash I don't have any trouble. but when I try to replace touchwiz with nova be for I compile/build the rom from my working folder. Nova fails to properly install/launch after boot up. it FC's at the desktop and does not restart. leaving me with an inoperable rom.
[Samsung Epic 4G Touch] Chillyz12:
Any one?
[Samsung Epic 4G Touch] hlxanthus:
All the custom ROMs I have made have been for other devices. On them I just deleted the stock launcher and copied in the one I wanted into /system/app. I have never done it on a TW ROM though. Might want to find a ROM that does it, then download it and see how THEY did it :D

Most I have learned about ROM structure has been learned that way.
[Samsung Epic 4G Touch] Chillyz12:
Thank you for your input. Yes I originally removed the touchwiz launcher from system/app and replaced it with the Nova launcher before building the rom and flashing it. All of the other apk's I added to the phone during the build process installed during the flash and operate just fine. Nova however FC's as soon as I finish the initial setup and reach the home screen. When I leave TW installed, then download nova from the market. it works just fine. even after I freeze and uninstall TW.

Maybe I should have posted in the Kitchen thread. I didn't because he has stated in his op that he no longer officially supports the kitchen. So I thought I would not bother him with my problems. Maybe a moderator could move this to the kitchen thread please? Thank you in advance.
[Samsung Epic 4G Touch] Stryke_the_Orc:
Actually, you can do this outside of kitchen. Use 7zip to drag your new launcher into the zip archive under /system/app you'll also need any lib files associated with the launcher. You can get these (if there are any) using root explorer after installing the launcher on what you're running. Just copy them to your sd card and transfer to PC, then drag them into /system/lib folder

You're good to go after that:thumbup::beer:

Slithering from the nether regions of a twisted mind and tarnished soul
[One (M7) Q&A, Help & Troubleshooting] aaroh:
hi i managed to relock my bootloader on my h&c one cannot flash any recovery cwn or stock.

it displays tampered ''relocked''

the phone is on 3 uk is there a stock ruu floating around.

i have no access to recovery i cannot flash it for what so ever reason.

it all happened when i flashed the odexed stock recovery through cwm which went fine.then i tried to flash stock recovery after which it went all haywire.

i have no root access just a stock rom bit stuck here

any help?
[One (M7) Q&A, Help & Troubleshooting] matt95:
you can't flash any recovery because your bootloader is locked, unlock it again to be able to flash them again
[One (M7) Q&A, Help & Troubleshooting] aaroh:
hey thanks so i guess i will have to go through the same process again can i use the same bin file? also is there any link to hasoons all in one toolkit as it seems the link on his post is broken ?
[One (M7) Q&A, Help & Troubleshooting] matt95:
yes, unlock it with the same bin file and then you'll be ready to go... i don't know about the toolkit but i can help you with commands if you need them ;)
[One (M7) Q&A, Help & Troubleshooting] aaroh:
hey thanks very much will appreciate it, you dont have to do it ill look around for it but grateful nonetheless,

really helpful!!!
[One (M7) Q&A, Help & Troubleshooting] matt95:
if you need help just ask ;)
[One (M7) Q&A, Help & Troubleshooting] jaythenut:
heres the link for tool kit

http://xdaforums.com/showthread.php?t=2183942
[Android Themes] thomassafca:
TouchWiz 5.0 for CM11/CM10.2/CM10.1/CM10/CM9/AOKP Theme Chooser

If you like my work feel free to press the thanks button or buy me a beer or buy any of my themes in the Play Store :)

There are quite some differences in the S4 theme:

- Most of the app launcher icons are updated

- New Settings icons

- New camera ui

- New statusbar icons

- New dialer

- More Galaxy S4 icons trough out the entire system

​
[Android Themes] Yeti12:
Thank you!! :good:
[Android Themes] deedscreen:
Great Theme, But One Issue...

This is a great theme!

If I may make a suggestion, please fix the status bar to the usual TouchWiz 5.0 Status Bar Color as shown below in this screenshot:

Image is Very Large (Hence the Show/Hide Option):

I hope it makes an addition to the theme... :fingers-crossed:
[Android Themes] zeetwo-raj:
Make a spinners exactly like s3 den it will look awesome

M using this theme its awesome good
[Android Themes] adamuadamu:
+1 for original touchwiz spinner

the rest is great! thanks for the theme
[Android Themes] thomassafca:
Version with CM10.2 support has been uploaded to the Play Store, will appear soon! :)
[Android Themes] thomassafca:
Version with CM11 support has been uploaded to the Play Store, will appear soon!
[Android Themes] Strongholder_21:
Compatibility Request

Great Work, Sir. But, can you do a optimized versión for HD+ screens, please?, for all the users like me using a 8"+ Tablet (in my case, Samsung Galaxy Note 10.1" - 160 DPI) with CM 10+, using this version in a large screen looks blurred and weird (Even the CM Theme Manager warns me the theme will be incomplete because of the screen size). Thanks for your work. Hope you read this.
[Android Themes] karambir singh:
in your latest s4 paid theme the battery icon is quite smaller than latest touchwiz free theme.

please fix this issue otherwise the theme is perfect
[Android Themes] thomassafca:
Uploaded a new version with some CM11 fixes! :)
[Android Themes] Pawprints1986:
Im just doing some research before setting aside a rom to try.

Is there any way possible to make the notification bar content appear as touchwiz as well? (meaning, buttons for controls like wifi, airplane mode, etc. and notifications all in the same area)??
[Nexus 7 Q&A, Help & Troubleshooting] NexusCrazy:
That's funny as I put my 16gig nexus 7 on charge a couple of hours ago and just went to pick it up and it was on the bootloader screen, but I managed to reboot and everything is fine, its funny cos I've had similar experience with galaxy s3 but that was dead after a night on charge. I've sent the s3 of for repair under warranty thinking it was the sudden death syndrome on the s3, but now I'm worried the charger might be at fault.

Has anyone heard of a charger frying an android phone or putting nexus 7 in bootloader mode? Or is it just a coincidence?
[Nexus 7 Q&A, Help & Troubleshooting] BlackFire27:
As last user said, if you have any nandroids you could restore them. And honestly it'd be so much easier to just boot an img. Not that hard.

Sent from my Motorola XPRT
[Nexus 7 Q&A, Help & Troubleshooting] FitAmp:
Defibrillator...
[Nexus 7 Q&A, Help & Troubleshooting] Dr Asqueroso:
[MENTION=2341536]bftb0[/MENTION]

Thanks for the response and I’m going to follow your advice… I have done the command line root method twice with this my phones the HTC Desire and the then Sensation so I have experience in the dark art… it was just I couldn’t see a way of enabling the ADB drivers so my PC and 7 could look at/see each other but I have found the following http://forums.androidcentral.com/ne...1477-guide-nexus-7-factory-image-restore.html

and this goes over what I need to do so I’ll give this a try and see how it goes. Like I say I don’t really need the data, I only used the 7 as a media hub and social media tool so I don’t mind putting the music and films back on it and the few apps and games is no big deal.

[MENTION=4554955]FitAmp[/MENTION] if this don’t work I may be taking your advice hahahahahaha!!!
[Nexus 7 Q&A, Help & Troubleshooting] slybunda:
bricked
[Nexus 7 Q&A, Help & Troubleshooting] Dr Asqueroso:
[MENTION=2556761]slybunda[/MENTION] May I ask why you say bricked?
[Nexus 7 Q&A, Help & Troubleshooting] khaytsus:
Another case where the N7 seems to overly discharge the battery and not be able to recharge it. I've heard of this several times, it just won't charge the battery once it gets too low.

I bet if you can get the battery to charge it'll be fine. Or failing all else, this place has the battery for $30.

http://www.portatronics.com/product...oogle-Asus-Nexus-7-Original-Battery-Part.html

It is NOT bricked.
[Nexus 7 Q&A, Help & Troubleshooting] GedBlake:
Hi, Dr Asqueroso...

'Bricked' is a certainly a bit pre-emptive... if the BOOTLOADER is still good (and from your description, it sounds like it still is), then you have a very good chance of resurrecting your tablet.

The thing is, from your description, you're only 'bootlooping'... which is trivial to get out of... if you have a recent NANDROID backup (or for that matter, a flashable ROM .zip), on your internel storage and you know how to FASTBOOT FLASH a CUSTOM RECOVERY.

Your options are threefold...

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

1) Use the STOCK FACTORY recovery to perform a factory reset. (As detailed by bftb0, earlier).

2) FASTBOOT FLASH a custom recovery (CWM or TWRP).

--

http://www.teamw.in/project/twrp2/103

--

http://www.clockworkmod.com/rommanager

I note you used CWM previously, so fastboot flash this recovery, and restore your last NANDROID backup. If you didn't make any NANDROIDs, then flash some other CUSTOM ROM. Or better still, use the 'wipe data' option in your Custom Recovery. I've had 'bootloops' and other weird egregious behavior myself, and this usually fixes it. (Sometimes, even wiping 'CACHE' and 'DALVIK' can make mysterious problems vanish!:).)

3) Restore back to FACTORY stock.

--

http://developers.google.com/android/nexus/images

(You need the 'nakasi' version for your 'grouper' tablet).

This last option carries some risk, because it reflashes the BOOTLOADER, which is always a risky procedure (a corrupt flash will hardbrick the tablet). So, ABSOLUTELY make sure your tablet is fully charged AND you have a good USB connection to your PC.

I note you're still on bootloader v4.13, so you could edit the 'flash-all.*' script from Factory Stock JellyBean 4.1.2 (JZO54K) to remove the command to flash the bootloader. Flash as normal (by running the script), and then take the OTA update to 4.2.2 (JDQ39) over WiFi... this will still update the bootloader (to v4.18), but because of the way OTAs work, the risk is significantly reduced.

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

But before you contemplate doing any of this... you need to ascertain if your battery is in good shape.

Here's what I would recommend if the battery is failing to charge correctly...

1. Plug the Nexus 7 into a wall charger.

2. Immediately press Volume Down and Power at the same time to reach the Bootloader

3. From the Bootloader menu, press Volume Down until you see “Power Off Device.”

4. Press the Power button to select the "Power Off Device" option.

5. Once your device is off, unplug the charger and then plug it back into the device.

If you see a large white battery shaped logo, that is flashing nearly all white, then you have a good level of charge... if it's flashing nearly all black (with only a bit of white), then the charge level is low... and fastboot flashing anything is not recommended.

Good luck... and hope this helps.

Rgrds,

Ged.
[Nexus 7 Q&A, Help & Troubleshooting] Dr Asqueroso:
First of all a massive Thank You all so much for the advice...

I think I've got it in the respects of each step but I'm just stuck with getting the drivers to work. I've installed the Java Dev Kit, the latest SDK from the Android site and successfully installed both the Tools and the Google USB Drivers. I also got the Asus drivers for the 7 and I have unziped the stock recovery JZO54K which ready to go. However can't get my 7 to show up in CMD Prompt via ADB devices string but if add my sensation it pops up everytime...

I've tried this process on a Windows 8 machine and a XP install too and the 7 is never picked up.

Does this mean the 7 is dead and stuck in the factory boot menu? What am I doing wrong?

This is killing me... :crying:
[Nexus 7 Q&A, Help & Troubleshooting] GedBlake:
No... it just means you're stuck in what is ubiquitously called 'driver hell'. Windows has always been a pain in the arse when it comes to drivers.

If you have a Windows XP box, you could try the following...

Download my copy of the FASTBOOT/ADB files for XP...

http://dl.dropboxusercontent.com/u/...orXP-MD5_8e02ab9b4b8463b9ee5c2063477b01ec.zip

Unzip to a folder on the Windows Desktop.

Unzip and copy the files from nakasi-jzo54k into the same folder.

You should now have a folder with the following files in it...

adb.exe

fastboot.exe

AdbWinApi.dll

AdbWinUsbApi.dll

bootloader-grouper-3.41.img

image-nakasi-jzo54k.zip

flash-all.bat

flash-all.sh

flash-base.sh

Delete 'bootloader-grouper-3.41.img' and edit 'flash-all.bat' to reflect this... that is to say, remove the line...

fastboot flash bootloader bootloader-grouper-3.41.img.

This is to avoid unnecessarily flashing the BOOTLOADER partition, and which in any event will only downgrade your current BOOTLOADER.

-----

Boot your Nexus 7 into BOOTLOADER mode, by pressing Vol. Down (& hold) and the Power Button.

Connect your Nexus 7 to your Windows XP PC, via a USB cable (preferably the one that shipped with the N7 originally).

Open a command prompt window on the folder into which you have copied all of the aforementioned files, and type...

fastboot devices

It should return a SERIAL NUMBER... if it does, you have a working FASTBOOT connection, and you're free to run flash-all.bat

This should restore JellyBean 4.1.2... and upon a successful reboot and a WiFi connection, an OTA upgrade will be proffered.

Allow this, and your Nexus will be upgraded to JellyBean 4.2.2 (JDQ39).

Good luck.

Rgrds,

Ged.
[Nexus 7 Q&A, Help & Troubleshooting] Dr Asqueroso:
Okay so I have a folder with the following

adb.exe

fastboot.exe

AdbWinApi.dll

AdbWinUsbApi.dll

bootloader-grouper-3.41.img

image-nakasi-jzo54k.zip

flash-all.bat

flash-all.sh

flash-base.sh

But I'm stuck on the edit line?? sorry for being a pain can you explain this bit.. how do you edit the flash-all.bat??

Delete 'bootloader-grouper-3.41.img' and edit 'flash-all.bat' to reflect this... that is to say, remove the line...

fastboot flash bootloader bootloader-grouper-3.41.img.

This is to avoid unnecessarily flashing the BOOTLOADER partition, and which in any event will only downgrade your current BOOTLOADER.
[Nexus 7 Q&A, Help & Troubleshooting] Pirateghost:
Open the bat file in notepad.

Sent from my Galaxy Nexus
[Nexus 7 Q&A, Help & Troubleshooting] Dr Asqueroso:
Done the edit and ran the flash-all.bat... The serial number has appeared after the fastboot command but now I seem stuck on the sending system command of 446268 been like this for 20+ minutes and somehow my bootloader is showing 3.41 on the tablet.

What next?